Skip to main content

Workflow differences in MS AX Versions


AX 2009
AX 2012


> Separate workflow component have to be installed  > Requires IIS and .NET Business Connector > Requires additional security setup
> Simplify workflow deployment and installation > Host the .NET Workflow runtime in AOS   > Separate installation no longer required.
> Workflow server components need to be installed on a web server running Internet Information Services (IIS).
>  Workflow server components are now automatically installed when installing the Microsoft Dynamics AX AOS. This new deployment significantly simplifies the administrative effort required to set up the workflow infrastructure.
> Forward only, sequential workflows.  > Only interactive elements (tasks and approvals)  > Support for sub-workflows
>  Expand workflow capabilities by providing broader applicability   > Introduce branching   > Introduce automated tasks  > Introduce line-item workflow support   > Introduce line-item workflow support  > Introduce parallelism
> Business user configures workflows using a Microsoft Dynamics AX client form
> Improve the workflow editing experience and usability  > Introduce a graphical workflow editor  > Support for “drag-and-drop” of workflow elements  > Familiar property editing experience
No Flow-Control Elements
 > Several new elements were added to help you design workflows. These elements will help create workflows that have alternate branches or branches that run at the same time. These elements include the following:   1.) Conditional decision: A point at which a workflow divides into two branches. The system will decide which branch to use by evaluating the submitted document to determine whether it meets a specified condition. 2.) Manual decision: A point at which a workflow divides into two branches. A user must take an action, and the action taken will determine which branch is used to process the submitted document. 3.) Parallel activity: A workflow element that includes two or more branches that run at the same time.
> No advanced workflow controls
> Workflow for Microsoft Dynamics AX 2012 supports advanced workflow flow controls. They include starting and ending elements, manual and conditional decisions, parallel activity and parallel branches, automated tasks, and sequence flows. Business users can now author workflows that correspond more closely to real life business processes using graphical elements that help them to better visualize the process flow.
> No Automated Task
> An automated task is a type of workflow element that does not involve human interaction. For example, an automated task can perform a credit check, run a report, or update a record. The purpose of an automated task is to execute business logic as part of a workflow that is implemented to automate a business process.
> No Line-Item Workflows
> Workflows for line items on a document can be implemented. By providing support for line-item workflows, workflow now supports more business process scenarios. For example, you might define a workflow for timesheets where each line item on the timesheet is approved by a specific project manager.   > A line-item workflow is configured and instantiated for different types of line item records that are related to a header. A header-line workflow can be configured to pause until other workflows are run on any number of line records.



Comments