I just arrived home from this year’s User Group Summit, what a great experience! So many great presenters and amazing sessions. I especially want to thank those of you who attended my own session on workspaces and personalizations. It would have been significantly less fun had you not been there – and I think we all learned a lot!!!
There were several requests for the additional presentation slides, so I am posting them here. Please feel free to download them by clicking through to SlideShare, and do share them widely.
I plan to do a series of blog posts in the upcoming weeks that will dive deeper into some of the session’s topics, so enter your email address into the subscribe box on the right if that is content you’d find of interest.
Handling rejection can be tough. Understanding D365 workflows can be tough. So understanding how rejection is handled in D365 Workflows can be, well, trickier than a freshman getting a date to senior prom.
My high school guidance counselor taught me experiencing
rejection makes us more complete people.
When setting up Dynamics AX workflows, it is important to test the approval process. But testing is not complete until the rejection process has also been examined. Testing rejections can be much more complex because workflow behavior needs to be examined for rejection and resubmission at each stage of the workflow. Below is an example of why this is important.
Let’s consider two expense report workflows below. Each uses a multi-level approval where an accounting reviewer approves for correctness (eg “Is the math right?”), and then an Expense reviewer approves for appropriateness (eg “Should this have been expensed?”). The workflows look similar, the rejection behaviors have an important distinction.
Dynamics 365 for Finance and Operations has powerful enhancements to the task recorder functionality. Particularly the ability to save task recordings specific processes in the Business Process Modeler of Lifecycle Services.
Task Recording Setup
Saving task recordings to LCS is a great
way to confirm testing of business processes, as well as create clear
documentation that is easily available to all system users through Task
recorder’s “Open from Lifecycle Services” playing functionality
To do this, however, it is first
necessary for each user’s system to be linked to LCS.