Project Template Attribute Cannot Be Locked in MUX
search cancel

Project Template Attribute Cannot Be Locked in MUX

book

Article ID: 395293

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Project Template (boolean) attribute cannot be locked via a process in the Modern UX.

Steps to Reproduce:

  1. Create a new process with Project as its Primary Object. The process should have a single step with a System Action to lock the following attributes:
    • Project Name
    • Template [not 'Project Template']
  2. Once the process is active, run it On Demand on any existing process instance.
  3. Still in Classic UX, open the project and observe that both the Name and Template attributes are locked and cannot be edited.
  4. Navigate to the Modern UX and try to edit the values for Name and Template attributes.

Expected Results: In the Projects Grid view, a CMN-0015 error is thrown when trying to save a new value for Name or Template; in the Project Properties module, Name and Template attributes have a lock icon that prevents their values from being edited.

Actual Results: In the Projects Grid view, a CMN-0015 error is thrown when trying to save a new value for Name, but not for Template (which can be changed); in the Project Properties module, Name attribute has a lock icon that prevents its value from being edited, but Template does not have that lock icon and its value can be changed.

Environment

Clarity 16.2.1

Cause

DE169769

Resolution

This issue is fixed in Clarity 16.3.3.