Project Template - Staff tab shows blank Investment Name (MUX)

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

In Clarity Modern UX - 'Projects' -> 'STAFF' Module, 'Investment Name' is BLANK for Project Templates. Investment Name does display ok for Non-Template projects. 

 

 

---

There are two issues:

USE CASE #A: 

In Clarity Modern UX, Projects, STAFF Module, the Investment Name is BLANK for Project Templates. The Investment Name is displaying for Non-Template projects. 

Steps to Reproduce:

1. 1. Go to the Modern UX, Projects Grid page 
   2. Open any Project that is a Template (Filter: Template = Yes) 
   3. Navigate to the STAFF Module
   4. Add Investment ID and Investment Name to the column layout 

Expected Results: Investment ID and Name is populated. 

Actual Results: Investment Name is BLANK.  

USE CASE #B: 

The field is not read-only; it allows users to select other Investment names which results in an error: API-1006 : The value 'xxxxxxxxx' for Attribute 'Investment' is not in expected format of is invalid. 

Steps to Reproduce: 

1. 1. Go to the Modern UX, Projects Grid page
   2. Open any Project that is a Template (Filter: Template = Yes)
   3. Navigate to the STAFF Module
   4. Add Investment ID and Investment Name to the column layout 
   5. Click into the Investment Name field on a row - you will see the lookup appears with a list of investments you have access to  
   6. Open any Project that is NOT a Template (Filter: Template = No) 
   7. Click into the Investment Name field on a row - you will see the lookup appears with a list of investments you have access to 

Expected Results: Investment Name field should be Read-Only and you should not be able to click into the field to see a list of investments. 

Actual Results: Investment Name field is NOT Read-Only and it allows the user to click into the field and see a list of investments. 

Environment

Release : 15.8.1, 15.9.1, 15.9.2, 15.9.3 

Component : CA PPM PROJECT MANAGEMENT

Cause

DE61486 

Resolution

Fixed in Release 16.0.0