How to utilize the Parallel Workflow Block in Microsoft Dynamics: Queue-Tips
This article is related to a Parallel Workflow Block, which can be found in various workflows in Microsoft Dynamics 365 and Microsoft Dynamics AX 2012.

Before we get started, below is an example of a Parallel Block being used in a workflow. A Parallel Block has been created for Divisional Approvals in a Purchase Requisition Workflow. This is where for each Division (as specified within Dynamics 365 and AX), there will need to be Approval from a different set of approvers.


The logic used for a Parallel Workflow block is that each Branch must run and are ran simultaneously. By bearing that in mind, you can make amendments and adjustments in workflow logic according to business requirements. In this example, the requirement was to only have a Singular Divisional Approval for a Purchase Requisition dependent on the First Line. As there are more than 18 Divisions, this is the most efficient solution.
In the past, I had attempted to use Conditional Blocks for a similar solution. It slowed down the workflow, and due to the number of Conditional Blocks used in the workflow, it failed to trigger the conditional logic.
The setups for the Parallel Block are as follows:


As can be seen by the setup within each Branch, there is only a single approval block. This approval block will assign to a (Divisional) User Group of people for Approval. The User Groups can be made under the System Administration Module.

As all of the branches are run in the Parallel Workflow block, the condition was added in the Approval Block, see below:

If any of the above conditions have been met, then the approval block will trigger and in turn the Branch will require approval. Likewise, if the conditions have not been met (for the other branches), the approval block will not trigger and the branches will complete (without requiring any approval).
An example for the above workflow is a PRQ being raised where the first line has a dimension division of ‘BPC’. As the conditions, have been met for the BPC branch approval will be needed from the BPC Approvers. Simultaneously, for the Branches BUS & CEN the conditions have not been met and so the branches will complete without requiring any further approval.
This is an example of where we can utilize the Parallel Workflow block to meet multiple conditional requirements, which require different set of approvals according to each specified condition.
Contact Queue Associates
Please contact Queue Associates (a Microsoft Dynamics Gold Partner) to learn more about our services related to implementing and supporting Microsoft Dynamics 365 Finance and Operations. You can reach us by completing the form on our CONTACT page, or by calling us at the Queue office phone number for your local region (U.S. and Global locations).




