Full Name is editable on Roles when using FLS with behavior different from Resources
book
Article ID: 404534
calendar_today
Updated On:
Products
Clarity PPM SaaSClarity PPM On Premise
Issue/Introduction
When enabling FLS on First Name and Last Name, Full Name is no longer editable on Resources and Teams, however remains editable on Roles
Note: the behavior on editable "Full Name" field is not limited to MUX and matches Classic
STEPS TO REPRODUCE:
Connect to Clarity with admin user, added to a specific Security Group you are aware of
Go to MUX – Resources
Note that you are able to modify First Name and Last Name for any resource
Now go to Administration – Attributes
Filter on Object – Resource and search for “name”
Set First Name and Last Name to Secure and Access View to the Security Group your user has access to
Now go to Resources
Try to edit the First Name and Last Name fields in Resources tab
Now try to edit Full Name
Go to Teams tab– try to edit First Name and Last name, then Full Name
Now go to Roles tab and try to edit First Name and Last name, then Full Name
Expected Results: The field to be not editable as on the other screens. Teams resource also does not have a First Name and the Full Name is blocked from editing.
Actual Results: Full Name is editable which defies the purpose of using FLS on First Name and Last Name
Environment
Clarity 16.3.2
Cause
This was reviewed as DE173291, and it's determined to be by design
Resolution
By Design.
Due to evolution of resources, roles and teams in MUX.
In Teams you have to change the name under Team Investment.
Only Resource can have first and last names
In Roles the Full Name is expected to be editable
This is an area that cannot be made consistent as it has to abide by MUX current rules and Classic legacy rules
Workaround:
Add Business Rules to Full Name field for Role
Connect to Clarity MUX - Administration - Blueprints
Find the Resource Standard Blueprint and make a copy of it
Open the new copy - click Edit
Go to Business Rules - Add a new rule with type View Page
Filter on Is Role = Yes
Action: Disable Editing for Selected Attributes
Save the rule
Publish the blueprint
Select the new blueprint and Make Default
Now go to Resource - Roles and observe that Full Name is locked
Alternatively you can also adjust user access permissions to not allow resource editing