I have a use case where there are 5 stages and each stage needs to be completed either by a nominated user or a team.
As an example, a user (any) submits a request to start the process. The Finance team then enters all fields related to finance. In the next stage, a nominated manager (by the oringal requestor) enters all fields related to performance. Finally, the Management team reviews and either approves/rejects. See illsutration below:
Is it possible to assign a user/team to a stage and only allow editing of fields for the assigned user/team?
Is it also possible to prevent editing records that have been captured from a previous stage?
See illustration below
In Canvas apps, I would simply provide either a specifc user or a team access to a screen where they can enter the relevant details and they would only be given access when the record is at a specific status. This is my first time looking into Model Driven apps and I am stuggling to understand how I can dynamically restrict access to records throughout the business process flow stages. Any guidance would be greatly appreciated.
Out of the box, it is not possible to "assign" or hide a stage based on the assigned user/team without using JavaScript. However, it is possible to hide the entire business process flow based on the security profile your users have been given. You can then create multiple BPFs and set the visibility of each BPF on each security profile (one for all users, one for finance, one for management etc). In my experience however, this is cumbersome and maintenance heavy because when inevitable business process changes arise, each BPF needs to be kept in sync.
Apart from using JavaScript, you can leverage Business Rules to make specific fields read-only or hidden based on specific conditions (for example you can make a field read-only based on the output of another field.
Note you can also leverage Column Level Security to secure fields by assigning your custom security profiles against those fields.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.