We recommend having a strategy to manage field states before building any state rules. You should consider:
•What state will the object or group occupy for most of its lifecycle? This state will be your choice for the Stage = All/Role = All combination so it becomes the general rule.
•What exceptions are there for that object in that role and stage combination? For each object, or group, specify the exceptions to the rule for specific stage and role combinations.
 |
It is recommended that initially, all fields should be set to a restricted state such as read-only, disabled or hidden and then overridden for specific stage and role combinations. This approach is much easier than looking at each stage and role combination and setting up each one. If you have large numbers of stages and roles, that approach can quickly become unmanageable. |
See also: Explanation of State Priority, Showing Field State Markers
Return to: Limiting User Access to App Fields, Designing an App
