In spite of the benefits that we could utilise from these new features, there are some limitations that we might need to aware of, especially in designing the best solution in terms of maintainability, performance and the time effort that need to be spent.
In designing business process there are maximum number of processes, stages, and steps:
- The maximum number of activated business process flows per entity is 10.
- The maximum number of stages in each process is 30.
- The maximum number of steps in each stage is 30.
- The maximum number of entities that can participate in the process flow is 5.
Planning synchronous workflow might be similar to planning synchronous plugin, try as much as possible eliminate the long-waiting process to be registered as synchronous one for better user experience.
With current release, as far as my trial-and-error experiment with business process, we could only have one condition and one action. So it is like a single if statement:
If [this condition]
Then do [this action]
Meanwhile, if-else or switch-case scenario is not available
If [condition is A]
Do [action A]
Else if [condition is B]
Do [action B]
Else if [condition C]
Do [action C]
Do [default action]
To achieve this, we need separate business rules and might want to check whether one rule is unique to the other rules, which is quite messy for a solution.
If [condition is A] and [not condition B] and [not condition C]
Do [action A]
And so on…
Business Rules are Entity-Bound
So far these are my findings on the limitation of the new features in Dynamics CRM 2013. In future post, I might add any additional limitations Dynamics CRM 2013 or Microsoft might release updates on these limitations to make Dynamics CRM 2013 as the best platform for xRM implementation.