Inconsistent UI experience for users with view-only instance-level rights

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Some pages have fields that act like they are editable, but will be reactive with an 'unauthorized' error message, while other pages completely block the user indicating the user does not have authorization to edit the field. This is inconsistent behavior.  

Steps To Reproduce: 

1. Create a user with below rights 
   • Global Rights 
     • Project Management - Navigate    
     • Resource Management - Navigate    
   • Instance Rights 
     • Project - View
     • Resource - View
2. Logged in as newly created user 
3. User will be able to see the instance right granted for Project and resource 
4. Upon trying to edit attributes specially lookup an expected error is populated " API-1007 : You are not authorized to process request. Contact your system administrator for necessary security rights." and this is expected 
5. Now on the project workspace on the List Grid open the details Flyout and configure any of the lookup attribute on the flyout, perform the same steps for the Resource Workspace too

Actual Result: Inconsistent behavior. Being a view-only instance level right user, user shouldn't be able to edit the look-up even though editing through up an error 'API-1007 : You are not authorized to process request. Contact your system administrator for necessary security rights.' However the UX in project details flyout is non editable vs Resource where its editable

Expected Result: Consistent behavior to indicate when a field can be edited. The behavior of the UI should be consistent across various workspaces. 

 

 

Environment

16.3.1

Cause

DE169867

Resolution

This is a targeted enhancement request implemented starting Clarity Version 16.3.3, specifically for the Resource Details flyout. A user with restricted access will now see read-only fields for the Resource Details flyout panel.