CRM – Page 77 – Nishant Rana's Weblog

My Notes on Business Process Flow in CRM 2015

In CRM 2013 we were restricted to only those Entities that were 1: n related.
In CRM 2015 we can select any entity on which Business Process Flow is enabled.
Here test is an entity which has business process flow enabled, however it is not related to Contact record i.e. our primary entity

The same restriction of having only 5 entities applies to CRM 2015 also.

The entity relationships supported are of type 1: n only and it is optional.
Each process can have maximum 30 stages.
And each stage can have maximum 30 steps.
There can only be one active process at a time.
No closed entity loop, the entity used earlier can be referenced again.

{Learning} All you might need to know on CRM 2013 App for Tablets

I spent last week or so discovering things on CRM 2013 tablet application and to be honest, it is pretty good. There are limitations but it is a good start for Dynamics CRM in tab and mobile market with having an out of box app.

Here are the series of blogs which pretty much sum all I could find on CRM 2013 Tablet application configuration, what can be done what cannot be done etc. For installation it is available in Google store for Android tabs, Windows store for Windows tabs and Apple store for IPAD tabs.

· Want to know how to configure multi entity search for CRM 2013 App. Here you go: Click here

· Want to know how to reconfigure IPAD app and options: Reconfigure vs Sign out for CRM 2013 App. Here you go: Click here

· Want to know Security Privileges required to access CRM 2013…

View original post 50 more words

Business Hours in Service Level Agreements (SLA) in CRM 2013

Hi,

Was looking into how the business hours works in SLA.

For this we a created new SLA record on CreatedOn field and which will update one of the fields on warning after one minute and some other field on failure after waiting for 5 minute.

And Applicable When -> when the Title field of Case contains “mm” text in it.

Following was the schedule

We created case record that satisfies the above condition at 3:28 P.M.

It updated one field on warning after one minute and then on 3:30 it went into wait condition and then resumed at 3:40 and showed failure at 3:43 as expected (i.e. total 5 minutes).

So it did consider the Break specified and on resuming ran for the remaining 3 minutes.

Hope it helps..