Using Out-of-the-Box Field Level Security to Apply Security to Business Process Flows in Dynamics CRM 2013
Business processes in Microsoft Dynamics CRM 2013 are great out-of-the-box, but there are also a few things that we can do in terms of extending the functionality of the stages with some customizations. In this blog I'll show how to use out-of-the-box field level security to apply security to business process flows in CRM 2013.
Hiding and showing a section is a good way to limit your end users to be working with only the fields that they need access to, but we can apply out–of-the-box field level security to business process flows as well.
Let’s say you wanted to add a Boolean field called something like Progress to the first step, and only certain users could be allowed to change the value of Progress from No to Yes. What you would do is:
1. Create a new Boolean field that is enabled for field level security:
2. Create a field security profile
3. Associate users or teams with the profile
4. Add specific field permissions, Create (No), Update (No) or Read (Yes) to the profile
5. Add users who shouldn’t be able to modify the field to the field security profile
Now, only a certain subset of your end users will be able to approve moving to the next stage as the field security profile will limit all of those people who shouldn’t have access to proceed to do that.
In our example, say at a minimum, you would require that First Name, Last Name, and Address 1 are all populated before you allow progress to the next stage. You will need to add Progress as a required step as shown below:
Feel free to give me a ring if you would like additional information about Dynamics CRM 2013 and Business Process Flows.
Henry Lin, Dynamics CRM Consultant, FMT Consultants
Posted by: Jakob Bechgaard