{"id":24460,"date":"2020-08-21T08:00:13","date_gmt":"2020-08-21T08:00:13","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=24460"},"modified":"2020-08-21T08:00:13","modified_gmt":"2020-08-21T08:00:13","slug":"how-to-use-power-automate-in-sla-to-configure-actions","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/08\/how-to-use-power-automate-in-sla-to-configure-actions\/","title":{"rendered":"How to Use Power Automate in SLA to Configure Actions"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

When it comes to Customer Service, the SLA plays a very crucial role to track performance against Key Performance Indicators (KPIs). With the Dynamics 365 CRM web client interface, we used to configure KPIs with traditional workflow actions when SLA is violated like send an email to agents if SLA is failed or warned. As you can see in the screenshot below that on the failure of SLA Item, we have available actions in the traditional way.<\/p>\n

\"Use<\/p>\n

But these traditional workflow actions are limited to Dynamics 365 CRM since it doesn\u2019t have any provision to call\/execute external apps which means we cannot connect or do any operations outside Dynamics 365 CRM apps. Suppose, you wanted to post a message in MS Teams, you cannot do so with traditional workflow actions but with Power Automate you can do this. Here, I have given just one example with MS Teams but we can also connect\/call various applications using Power Automate like Mailchimp.<\/p>\n

Before moving ahead I would like to inform you that this feature is only available in Unified Interface where you can see the option to configure Power Automate when SLA is violated and this feature is introduced in 2020 wave 1.<\/p>\n

Below steps you can use to configure SLA:<\/p>\n

Step 1:<\/strong><\/p>\n

Open the Customer Service hub<\/strong> app and change the area to Service Management<\/strong>. Create SLA KPI<\/strong> for required the entity and activate it using the Activate button. In the below screenshot, you can see that I have selected the Case entity with \u2018First Response By KPI\u2019 KPI.<\/p>\n

\"Use<\/p>\n

Step 2:<\/strong><\/p>\n

Now, create SLA for the entity.<\/p>\n

\"Use<\/p>\n

Once you create it then you can create SLA Items. So use the \u2018+New SLA Item\u2019 button on the sub-grid of the SLA Item on the same SLA. Here, you can define SLA Applicable, Warning, Success criteria and call Power Automate actions.<\/p>\n

\"Use<\/p>\n

At the bottom of the page, you can see the option to configure Power Automate using the \u2018Configure Actions\u2019 button. Before that, save SLA item<\/strong> so that you can see the \u2018Configure Actions\u2019 button. After you click the button, it will navigate to the Power Automate site and by default triggering event and switch conditions defined. We can use these steps. Here, do not delete\/update these already defined steps as we just need to add our step\/action in the required place.<\/p>\n

\"Use<\/p>\n

As shown below, you can see the triggering event that triggers whenever SLA KPI is violated like warned, failed, succeeded. So you need to identify which event has been occurred and whether it is warned, succeeded or failed. To identify the event, we have an attribute called Status. So, in the below screenshot you will see switch condition which has already been added by default with \u2018Status\u2019 attribute:<\/p>\n

\"Use<\/p>\n

This status attribute gives integer values. Below table will help you to identify each status:<\/p>\n

\"Power<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

You can see in the below screenshot that 3 conditions have already been added by default so here we just need to add our actions inside \u2018Switch\u2019 condition wherever it satisfies.<\/p>\n

\"Use<\/p>\n

I have added two steps, one is retrieving \u2018Case Number\u2019 and another one is Connector of MS Teams (Post Action) to post a message in MS Teams. So, here whenever SLA is failed\/warned\/succeeded, a message will be posted in the MS Teams Channel with \u2018Case Number\u2019 and the agents will get to know particular Case\u2019s SLA has been violated.<\/p>\n

Note<\/strong>: Currently, MS Teams action (Post a Message V3) \u00a0is in preview mode. I just showed how to post a message on Team\u2019s Channel if SLA is violated. You can do something else as per your requirement.<\/p>\n

\"Use<\/p>\n

Once the configuration is completed, save it. Now, come back to SLA Items and save them. Then finally save the SLA and activate it. Also, set default SLA if required.<\/p>\n

\"Use<\/p>\n

Now, as per above configuration steps, if SLA gets failed\/warned\/succeded, a message will be posted in the MS Teams Channel as shown in the below screenshot:<\/p>\n

\"Use<\/p>\n

How to move Configured SLA using Power Automate from one environment to another?<\/strong><\/p>\n

It is a simple process that we can do with CRM solutions concepts. So, create a new solution in environment and add the components i.e. SLA, SLA KPI and Power Automate. Export the solution and import it into desired environment.<\/p>\n

In the screenshot below, you can see that I have added SLA, SLA KPI and Power Automate in a Solution.<\/p>\n

\"Use<\/p>\n

Conclusion<\/strong><\/h2>\n

Thus, as illustrated above, with the help of Power Automate you can configure actions in SLA.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction When it comes to Customer Service, the SLA plays a very crucial role to track performance against Key Performance Indicators (KPIs). With the Dynamics 365 CRM web client interface, we used to configure KPIs with traditional workflow actions when SLA is violated like send an email to agents if SLA is failed or warned.\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":24473,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[18,1985],"tags":[1975],"class_list":["post-24460","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dynamics-365-v9-2","category-power-automate","tag-power-automate"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/24460","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=24460"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/24460\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/24473"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=24460"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=24460"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=24460"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}