IBM EWM : User cannot modify workitem when during Filed against change
Hello Team,
Our setup:
1. Project area : where 2 custom attributes , which is configured ONLY to Role -> System owner, Dev ops architect.
2. Roles : Team member, System owner, Dev ops architect
3. Users are added at the project area level
Scenario: User A who has System owner role, has created a workitem and set 2 custom attributes to some values
User B who has Team member role (added at project area level with Team member role), changes the filed against and hit save
Actual Result: Error is thrown saying the user cannot modify the workitem for following action: modify for above said 2 custom attributes.
my query:
1. here in this instance, i agree that team member doesnt have modify access to 2 custom attributes but he has not modified these attributes.
why this error is still thrown when filed against changed ? can you help me to understand the behaviour
One answer
Have you set up any sort of Default value, or default value customisation, or calculated value customisation? Anything that could touch those attributes if the Filed against was changed?
I've seen this happen when there is some sort of customisation added to a field that alters it in the background
Comments
No, we do not have any customization around it.
i get this error, if the field is already filled and have data and role which do not have access try to modify the filed against.
if the field is empty and doing the filed against change will not throw any error.
i would like to understand what is happening here and also if this business as usual then we should keep all attributes to everyone then why do not have role and enable/disable around it?
That's very weird - I would log a ticket with IBM Support as this is not the normal behaviour at all. I've got clients with several hundred users where most of the fields are read only for the role and they have no problems.
Filed Against is a little bit different to other attributes as changing the Category also changes Team Ownership, and thus any Roles will be recalculated, but if the field is already filled in and doesn't change then it shouldn't trigger the permission problem.