This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
understand that this is working as designed, but there seems to be inconsistency across applications.
The ordering of a user's assigned roles reflects their relative priority. When behavior is configured for multiple roles, the process framework will execute the behavior associated with the user's highest priority role. Priority doesn't affect permissions; the process runtime will allow the user to perform actions granted to any of their assigned roles."For example:-
User A has the roles assigned in this order,
Change Owner
Change Coordinator
Reviewer
EditorUser B has the roles assigned in this order
Change Owner
Change Coordinator
Editor
ReviewerAnd if there is operational behaviour defined for Reviewer role, which has a pre condition that Summary and Filed Against are read only attributes for Change proposal WI type
Editor role has a pre condition set for Reviewer WI type but not Change proposalUser A wont be able to save Change Proposal WI with summary and filed against modified as the operational behaviour of Reviewer role takes affect as it has high priority over editor role
User B will be able to save Change Proposal WI with summary and filed against as the operational behaviour of Editor role takes affect as it has high priority over Reviewer rolePermissions set directly on a role actually do not act in priority order - if any role grants permissions, then the user is allowed to do the action. But permissions set on roles via actions and behaviours will only look at the first role and will not fall through. This is the case even if you do not have a behaviour or action set on the role above. It only ever looks at the top role and doesn't even evaluate roles that appear after in the list - leaving a behaviour off doesn't cause it to fall through.
RM project areas allow you to assign permissions on roles by work item (Artifact types) and state. I understand both are different applications, but there is no consistency across applications.
The ask is for EWM to have same consistency for role permissions like ERM
Idea priority | Low |
Needed By | Not sure -- Just thought it was cool |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.