Ratakan

Informations :

Microsoft Dynamics GP 2016 –Workflow 2.0 Advanced Step Conditions

With the release of Microsoft Dynamics GP 2016 comes a few new features, one of which is some additional options as to what action to take when a workflow step's condition has not been met. There are three options underneath this new menu item, two of which are new. Previously, the workflow path would simply end.

Condition Functions

End the Workflow Path

When the instance of the step is reached in an instance of the workflow, the sequential steps following the step that do not also follow other parallel steps that do run are also not run. If there are no other parallel steps that do meet conditions for running, then the workflow is completed at that point. When the step is reached in an instance of the workflow, the step status for the instance of the step is set to No Action Needed, and a workflow history record is created for the step.

Continue to the next step

When the step is reached in an instance of the workflow, the workflow continues to any sequential steps following the step for which the condition was not met. The step status for the instance of the step is set to No Action Needed.

Reject the workflow

When the step is reached in an instance of the workflow, the step status for the instance of the step is set to Rejected, the workflow status for the document is set to Rejected, and all pending workflow user activity for all workflow steps (tasks and approvals) for the document are cancelled.
Be sure to check back to the Microsoft Dynamics GP 2016 New Feature Blog Series Schedule page to review upcoming blog posts to help you gear up for What's New in Microsoft Dynamics GP 2016 with great content, documentation and videos.

No comments