Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Within Unified Service Desk (USD) Agent Scripts you can flag one (or more) scripts as being start tasks. But what does this mean?
In previous posts I have explained how to create Agent Scripts and dynamically load them using the “GoTo” action.
Another method to launch an agent script is to use the start task feature. Whenever a session starts, if you have any scripts flagged as start scripts that script will load.
When creating an agent script you simply set the start task field ot “Yes”.
In my example below I have flagged two scripts as start tasks, this has the effect of triggering a “special” menu that allows the user to pick the script they would like to follow. In my example I wrote two scripts, one on how to greet potential customers and another for existing customers. My “menu” is also shown below;
Having selected the script I wish to follow the screen changes to display that script. So in my simple example, clicking “Start Script – Customers” the following script was shown.
I think this approach of using start tasks may work well if you need to have a generic script which is common to all types of sessions.
Business Applications communities