Extending Microsoft Dynamics 365 for Operations Cookbook

There's more...

This seems to greatly simplify the workflow development. We don't need all of the event handler methods, since most of them only update the record's status. There is some thought required, if we consider the following scenario.

The workflow is cancelled by the user, which means that the status will go back to Waiting. We chose Waiting, for when the workflow task was cancelled, because the state machine will throw an error if we try to set it to the initial state. The problem is that we can't change the status to the same status; we will still get an error. The error is not just a message to the user; it will place the workflow in a failed state, which will require an administrator to cancel, resubmit, or resume it.

The problem ...