Often the migration service account used will have multiple privileges allowing it access to multiple BPFs for the same entity. As “Phone to Case Process” is permissible for my user (based on security role), included in the D365 Field Service app and is the 1 st active BPF in the BPF ordering, it shows up by default no matter which app I use to create the case. In the Field Service app, if you look in the Model-Drive app, you will see that both BPFs are included. Moreover, when I access the Field Service app and tries to create a case, I am still presented by default the “Phone to Case Process” BPF. Hence when I (as system administrator) creates the case in the D365 Customer Service app, I will see the “Phone to Case Process” BPF. It depends on the “Order” of the BPF and whether the relevant BPFs are included in the D365 “app” you accessed while creating the case in D365.Īs you can see in the below screenshot, the order of the BPF is set so that “Phone to Case Process” is always the first to load. What about a system administrator who does have privileges to both BPFs and can switch a case from “Phone to Case Process” to “Case to Work Order Business Process” BPF? What about Case Creation as a System Administrator? This means the system will never creates BPF entity “Case to Work Order Business Process” record. Whether you create the case natively or migrate the case using Mark Leave as the migration user account, he will never see the Field Service BPF based on the current setup. More importantly the BPF entity record is created in the background when the user creates or opens the Case. You can see this using Advanced Find.Įven if Mark were to switch process and tries to find the other BPF to switch the case to, he won’t be able to see the Field Service “Case to Work Order Business Process” BPF. Upon saving this case, the system creates an the BPF record for “Phone to Case Process”. This means all cases that Mark creates will only show the “Phone to Case Process” BPF instead of the “Case to Work Order Business Process”. For the out of the box “Customer Service Rep” security role, it has privileges for “Phone to Case Process” BPF entity but not the Field Service specific “Case to Work Order Business Process” BPF entity. It appears in the security role just like any other entities for you to assign relevant privileges. Phone to Case Process – with 3 stages: “Identify”, “Research”, and “Resolved”.Ĭase to Work Order Business Process (from Field Service app) – with 6 stages spanning 2 entities, Case and Work Order.Įach BPF in the system is actually a custom entity of the same name. If we take the Case entity as the starting point, in my trial environment which has the Customer Service app and Field Service app, we have out of the box 2 BPFs defined for the Case entity. Mark Leave (another user) is assigned the “Customer Service Representative” security role – so he can create customer and case records.Priscilla (me) is assigned the system administrator role.In my trial environment, I have 2 system users with different security roles assigned. Let us look at an example in a trial D365 environment for more details. In the latest Dynamics 365 model, the BPF that a system user can see is associated with their security role, because each BPF instance is essentially a BPF entity record that is stored in the system. It introduced the ability to have multiple instances of BPF associated with the same entity record. While Business Process Flow (BPF) was first introduced years ago in CRM 2013 (the first time I thought about BPF was from the 2013 post), the entity/security model surrounding BPF changed significantly around 2017. If you need to know the details of how it works, please see this wonderful post here. XrmToolBox provides a tool named “BPF Manager” that does exactly that. Absolutely! There’s no need to go write the code on your own. Recently, someone asked me if it is possible to programmatically set the stage of a business process flow (BPF) for a record after it has been migrated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |