How to Implement Conditional Business Process Flows - Only Start a BPF for SOME Entities? RRS feed

  • Question

  • The way MS have implemented Business Process Flows (BPFs) is rather strange and inflexible. Once you have created a BPF for an entity, then all entities start to display this BPF regardless of the current data of the BPF.

    e.g. You create a BPF for setting up an Account record. Once the Account has been set up then the BPF is redundant. But

    a) there is no way to tell CRM only to start the BPF for new records, not existing ones

    b) There is no way to tell CRM only to start the BPF conditionally depending on the value of a field

    c) There is no way to end the BPF - once all stages are completed, CRM continues to display the BPF!

    d) There is no way to determine if the BPF has been completed (see https://social.microsoft.com/Forums/en-US/6fd7ccdb-2308-44e5-859f-3c837b318186/how-to-test-if-a-business-process-flow-is-complete?forum=crmdevelopment)

    Some of these issues can now be addressed by using JavaScript to hide the BPF, but it would be much nicer to have some facility to not have a BPF running for an entity.

    If you try removing the current BPF for an entity (I tried), then CRM just restarts the default BPF for this entity type at the beginning!

    Tuesday, December 23, 2014 9:50 AM