search cancel

Error: CMN-0009 When creating Project from Template in New UX in 16.0.1 'status' has invalid lookup value '1'

book

Article ID: 237589

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

Error: CMN-0009 When creating Project from Template in New UX in 16.0.1 'status' has invalid lookup value '1'

STEPS TO REPRODUCE: 

  1. Take any project template and set status field on the template to "Approved" in MUX
  2. Create basic user and assign below Global rights:
    • Project - Benefit Plan - Edit All
    • Project - Cost Plan - Edit All
    • Project - Create and Create from Template
    • Project - Edit Assigned Tasks - All
    • Project - Risk, Issue, Change Request - Create
    • Project - Risk, Issue, Change Request - Edit - All
    • Project - Schedule In Browser
    • Project Management - Tiles Navigate
    • Project Management - Navigate
    • Projects - Navigate
    • Instance right: Project - View (Instance right to the template) 
  3. Attempt to login as user from step 2 and create project using a template
  4. Notice error CMN-0009: Attribute 'status' has invalid Lookup Value '1' 

Expected Results: It should allow user to create project from template. 

Actual Results: It does not allow user to create project from template. 

Note: This exact same setup was working fine in 16.0 version.  

Workaround: Assign Project-Approve- All global right or change status field on the template to be something else other then "Approved".

 

Cause

DE64499 

Environment

Release : 16.0.1

Component : Clarity MUX UI Usability

Resolution

DE64499, As per design.

The Engineering team have reviewed this defect and the issue this is because of the changes done for the another defect DE63096 (V16.0.1). As part of this defect we ensured that create/update will go through the right check. So with this change every update/create that is involving Status field has to have Project Approve - All right along with other rights like create and create from Template rights.

This is an intentional change and Users cannot create an investment with status as Approved, if user is not having Project Approve - All.

In 16.0.3 we changed the functionality only while Create From Template. So if the template has the Status set as Approved, and while creating Project From Template the user has not modified the status field there will be no Project Approve All right check. We don't check the "Project - Approve All" access right if the user is just "copying" via create from template and isn't trying to change the Status during the create action.
If a user tries to change the Status field (because it is on the create screen and not secured via FLS) during create from template, then we will check for the "Project - Approve All" access right.
This new behavior is only applicable in Modern UX, and Classic will continue to work the same way.

 

Additional Information

For the details of DE63096, reference the following article: