Dynamics CRM 2016 Update 1 – Updated Service Level Agreement

One of the features of Dynamics CRM 2016 Update 1 release is the updated Service Level Agreement (SLA).

In the previous versions, SLA is only limited to case entity. This means, the KPI measures is limited to case.

In the current release and now available in trial instance, SLA can now be enable or use in other entities.

These are the things that you need to know about the “updated SLA”.

SLA can be associated to other entities (out-of-the-box or custom) other than case entity.

This opens broad amount possibilities in terms of providing a KPI for other entities.

How to implement?

  1. Enable from entity level

    **NOTE** You can enable/disable this feature per entity.

    All entities where SLA is enabled can only use “enhanced” SLA. Only case has an option to use either “standard/enhanced”.

    Enhanced SLA has the capability to pause/resume its timer while Standard is not. The status can dictate whether the timer is in pause or active state. You can select the list of status under System Settings -> SLA.

  2. Define KPI field for the entity. Only Case entity has a defined KPI.
    1. Data Type: Lookup
    2. Target Record Type: SLA KPI Instance

  3. Create your SLA for Account.
    1. Go to Settings -> Service Management -> Service Level Agreement

    2. Click New. Modal dialog is displayed.

    3. Select Account
    4. Click Ok. SLA form is displayed.

    5. Notice that SLA Type is “lock” with “Enhanced”.

      This applies to all entities and only the case entity has an option to have either Standard or Enhanced SLA type.

    6. Click Save. SLA Item form is displayed.

    7. Check the SLA KPI, this is the field we created at step 3.
      1. Maximum of 5 KPI Instance field per entity.
    8. Set Applicable When conditions
    9. Set the Success Criteria
    10. Success Actions
    11. SLA Item Failure action
    12. SLA Item Warning action

What are the limitations?

  • Max of 7 entities with 7 enabled SLA.
  • Max of KPI fields per entity is 5.

Conclusions

This new feature has been requested by some of my peers to provide KPI features to custom entities. Seems like they are heard.

It just opens up a broad possibilities of features/capabilities when delivering/designing a project particularly to the business users.

When using this feature, just be aware of the limitations mentioned that should be taken to consideration during the design phase.

Leave a comment