Users cannot see Business Process Flow stages in case of conditions attached to the main process

[gauburtin]

Hi,

We faced the same kind of issue as this one

I have a custom business process flow for an entity and also custom security roles assigned to my users, the users can start a process but not see all the stages (or go forward in the process).

https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Users-cannot-see-Business-Process-Flow-stage...

But tuning the security role has no effect.

Previously, all users with all roles could see all stages. We had conditions that broke the process in two separate parts.

Now, as we changed these conditions (see screenshot) and re-attached them to the main process, users can not see the steps inside the condition

But users with Admin or System customizer roles can see the steps

Any help will be appreciated.

Regards,

Gautier

[gauburtin · Accepted solution]

Well, My Collegue found the solution on a separate blog

https://debajmecrm.com/business-process-flow-not-appearing-on-dynamics-365-cds-form-although-the-use...

I set Organization level for Cutomizations/Process/Read privilege

Now it's Ok !

[Anonymous]

I got the same issue with branching condition, and followed the same steps. still not showing the stages based on condition = true.

Edit - solved it - looks like the user has another role which prevents it.

[GLUX]

Just in case someone is still getting this error, I just had it and the "Read Process / Org level" didnt solve it.

After some testing I come to this conclusion:
There is a hidden privilege that some roles have and some don't (have encountered such a phenomen several times in the past). 
I had an user with this issue and tried that:
-> assigning "Sales Person" -> Didn't work
-> assigning "Sales Manager" -> worked - so I removed it again to test further
-> assigning "Project Owner" -> worked -> since this is a rather low-security role, i copied this one, called it "MTR" (My Test Role) and assigned this one -> worked.
Then i started removing all privileges from "MTR" one by one until there was not a single privilege assigned to the role.
Still this role made the difference between the user seeing or not seeing the BPF-Process stages beyond the condition. (Also, the user will only see the BPF after creating a record AND refreshing the page, while the BPF should already by there in the create form).

So, in conclusion, there is a hidden privilege in some roles, e.g. "Project Owner", that solves this issue. 
copy the role, remove all unwanted privileges and assign it to the users having issues.
Or, use a copy of this role as a new starting point for a new base role, if you wanna do the works.