Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
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.
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.
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.
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.
Detailed documentation for System Features System Features VIDEO!
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.
Sorry, I meant to post on this post: community.dynamics.com/.../net-framework-errors-with-workflow-2-0
We are having a similar issue where we get the following error
dynamics gp a .net framework error occurred during execution of user-defined routine or aggregate xp nodus Decrypt nodus encryption.corruptdataexceptions the size of packed data is too small for the ind
can this be resolved using exec wfDeployCLRAssemblies
Business Applications communities