This article reviews the workflow system in Microsoft Dynamics 365 for Finance and Operations. It describes the changes that have been implemented since Microsoft Dynamics AX 2012 and also includes links to more information about the workflow system.
The workflow system in Finance and Operations will already be familiar to you if you've used Microsoft Dynamics AX 2012. For more information about the workflow subsystem in Dynamics AX 2012, see the following topics.
|To learn about this subject||See this topic|
|The workflow system||http://technet.microsoft.com/en-us/library/dd309672.aspx|
|Workflow types by module||http://technet.microsoft.com/EN-US/library/dd362043.aspx|
|Developing a workflow||http://msdn.microsoft.com/EN-US/library/cc967389.aspx|
|Implementing a workflow||http://msdn.microsoft.com/en-us/library/cc585061.aspx|
Primary changes to the workflow system
Here are the primary changes that have been implemented in Finance and Operations:
- Integration with the new Application State Machine feature enables workflow events to be bound to state transitions on the underlying entity's state machine. This binding enables business logic to be centralized within the state machine and also enables the workflow system to be a declarative consumer of that state machine. The workflow metadata can reference a state transition that is performed when a specific workflow event occurs. Therefore, you can do state transitions within a workflow without writing any additional code.
- The workflow editor is now a program that you click one time to download. The editor communicates with Finance and Operations by using services. Therefore, Finance and Operations can carry forward the rich, graphical workflow design experience from Dynamics AX 2012.
- Workflow development wizards have been ported into Microsoft Visual Studio.