Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Is it possible to define users at run time for workflow's escalation like use of particpant for appraval ?
Thanks in advance
You can try setting up a workflow queue to achieve this. I have not done this before using an escalation. Usually it was a single person in my scenarios.
Can you give us an example of how you would see this scenario working?
Thanks for your response.
In fact when you setup an escalation you can define a specified user, generally is it possible to define this user at run time? This user or list users is memorized on the caller record of the workflow
You are unfortunately only use Heirarchy Providers on escaltion, not the normal Participant providers. These are a bit more tricky to use but could certainly accomplish what you are trying to do.
Are you basically wanting it to go to an alternate user defined on the form if the original approver didnt approve it? Is there any logic behind who this user is or is it simply a selection by the originator.
Yes there are 2 alternate users defined on the form, ther is no logic behind
I've looked at a few options inside AX and I can't come across a particularly nice way to accomplish this. Two not so nice suggentions that you could work off.
#1. Heirarchy provider: Customise a heirarchy provider to return the users that you would like to regardless of who the originator is. In your workflow configuration select your heirarchy and create a stop condition that will always evaluate to true.
#2. On your approve menu-item set a flag e.g. "User Approved" on your record to true. Create a participant provider than can return both of the custom users mentioned.
Then in your workflow config: 1. Create an escalation action of "approve" on your original approval step (if auto-approved the "User approved" checkbox will not have been set as the menu-item was never pressed. 2. Add an additional step with a pre-condition that checks if the "user approved" mark has been checked. If it has by-pass the step, if it hasn't assign to the relevant user using your participant provider.
I hope this helps a bit.
Thanks a lot Jonathan.I Will try it and inform you
Business Applications communities