Process Locks Field In Classic Lookup Values But Can Be Selected In Modern

Products

• Clarity PPM On Premise

Issue/Introduction

When a process is launched from Classic, the lookup field is read-only.
When clicking on the same field from the Modern, the lookup field can be clicked where values are displayed, where it should be locked.

Steps To Reproduce
1. Create a lookup with values.
2. Create a process that accesses the lookup attribute.
3. Launch a process from Classic.
4. Review the attribute field in Classic and attempt to edit the attribute field.

Actual: In Classic, the attribute field is locked and shows the lock icon
and is read-only due to the process instance, preventing access to other values, however
in the Modern, the field is visible and clickable where the lookup values can be seen, but the system prevents selection/editing by design.

Expected: In Modern, the user can click on the field and able to see other values. 
Even though it is selectable, the Modern prevents a value from being set, but does not give a message that is locked by a process.
Because of this, the user is inclined to attempt to select/edit/set the value for the field. The visual appearance suggests it was possible to edit the field.

Cause

In Modern, blueprint rules can specify if the field is locked for editing, however since the field is controlled/locked by a process launched 
from the Classic UI, the ability for the user to view and select a lookup value on the field is misleading.
It should be locked.

 

Resolution

This can be brought up as an enhancement request with Clarity Product Management for further discussion.