After the 3DEXPERIENCE Platform determines that a user’s person definition and the policy allows the user to perform a task for an object’s current state, the software then checks to see if any rules prevent the user from performing the task. A policy controls the tasks users can perform for each state of an object. In contrast, a rule controls the tasks users can perform regardless of the object. The tasks that rules apply to are limited to only those involving attributes, relationships, forms, and programs. For example, a policy might allow all users in the Engineering group to modify the properties of Design Specification objects when the objects are in the Planning state. But you could create a rule to prevent those users from changing a particular attribute of Design Specifications, such as the Due Date. In such a case, Engineering group users would be unable to modify the Due Date attribute, no matter what type of object the attribute is attached to. When you create a rule, you define access using the three general categories used for assigning access in policies: public, owner, and user (specific person, key, group, role, or association). For more information, see Policies. The owner access does not apply to rules that govern relationships because relationships do not have owners. | |||||||