We've observed that if you apply field level security on fields that are marked as Required on Business Process Flows, users who don't have Edit privileges to those fields are no longer required to update those fields before being able to progress a record to the next stage. In short, field level security conflicts with stage gating. Organizations should be able to enforce both field level security and stage gating without resorting to customization to make it work.
Comments
Thank you for your feedback. This behavior is by design as conceptually, field level security and stage gating in the process are two entirely different concepts that are independent of each other. In business process flows, the use of these two concepts in conjunction with one another is enable to allow for role-based approval scenarios where only certain users may update the value of a required step. This is ideally suited for processes that involve mandatory reviews. Regards, Karan
Category: Account, Contact, Calendar and Activity Management
Thanks for the comment. I'm not sure I understand though, if the two concepts are supposed to work in conjunction, then why don't they? As I'd mentioned in the original description, if a user does not have edit privileges to a "secured" field on the process flow, that field is by default considered as filled out, allowing the users to by-pass any mandatory steps in the process making it difficult to enforce the role based approval scenarios. But according to the Microsoft CRM documentation and your comment, that should not happen and we should be able to use field security and stage gating together.
Category: Account, Contact, Calendar and Activity Management