RTC 5.0.2 - Role conflict for attribute behvaviour in workflow states
2 answers
please carefully study https://jazz.net/library/article/292
1st Users can have multiple roles
2nd Everyone have the role Everyone with the lowest order.
3rd Roles have an order - from top to down. Example
- Big Boss
- Team Member
- Everyone
Operational behavior tries to find the configuration that is responsible in the context based on the roles of the user in this context starting with the top role down the list.
If it finds an operational behavior configuration lets say for "Work Item Save (Server)" e.g. for a role, it executes this operational behavior - and ONLY this operational behavior.
E.g. if it is configured for Big Boss, Team Member, Everyone in this context is is only executed for Big Boss and not for the other roles.
The design intent is that roles like Big Boss can have their own operational behavior configured to be less restrictive.
In the above example if a user with top level role Big Boss executes the operation (work item save), it would find it is configured with no preconditions and would perform the operation with no preconditions.
Comments
This is by the way independent from the state of a work item or the content of an attribute. What is important in this context is
Which operational behavior (Read Only for Type and State, Required for Type and State) is configured for the operation (Save Work Item Server) for the first role that is found in this context.
You are not meant to change the order of your roles for any operation. This order should be fixed. Only administrators or roles that have the permission to save the process are able to change the order of the role.
Permissions work different btw. as you get the permission if any of your roles grant it to you in the context. See: https://jazz.net/library/article/291
1 vote
Thanks, Ralph. That is the most concise, straight forward description of operation behavior checking I have read.
By the way, +1 on reading both of the articles linked here (on permission and operation behavior look up). Although they mention RTC 2.0, the lookup remains the same in all CLM releases to date.
Ruby
Martha (Ruby) Andrews
Jazz Foundation L3 Development Team Lead
Hello Together,
Vishnu M
Since read only and required attributes on state works with operational behavior, regardless which template you used, I can only point to my explanation above.
Thinking about it, there would be an option to look into the SDK and take the code of the existing operational behavior. You could wrap this in some code that looks at the roles the user has and set up some custom operational behavior that is configured and works the way you want it.