Created new CIT - 'Not Securable' Field not populated
search cancel

Created new CIT - 'Not Securable' Field not populated

book

Article ID: 275996

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

In 16.1.3, we have other Custom Investment Types (CITs) already pre-existing and the fields that are not allowed to be secured have the checkmark in the 'Not Securable' field in the Administration, Attributes grid. However, the newly-created CIT is not showing any checkmarks for the same Investment extension fields that are not allowed to be secured. 

Steps to Reproduce: 

  1. Go to Classic, Administration, Studio  
  2. Create a new Custom, Investment Extension Object. (Check API Enable, and select 'Investment Extension') on the initial properties page to create the object  
  3. Grant all access rights for the new object to the user  
  4. Go to MUX, Administration, Attributes  
  5. Filter for the newly created object  
  6. Add the 'Not Securable' field to the column layout 

Expected Results: To see some checkmarks for fields that are not allowed to be secured (i.e. Name, ID).  

Actual Results: No checkmarks at all in the column. 

Workaround: None. The attempt to secure a non-securable field has a reactive Toast message. 

Environment

Release 16.1.3 

Cause

DE77573 

Resolution

Resolved in Release 16.2.0