Hierarchy Managers and Stakeholders fields cannot be added to a blueprint
search cancel

Hierarchy Managers and Stakeholders fields cannot be added to a blueprint


Article ID: 244929


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


The two attributes on the Hierarchy object; Managers and Stakeholders do not have an API Alias and ones cannot be added.
The attributes are not available in the MUX.  What is their purpose?

Steps to Reproduce: 

  1. In MUX hierarchies try to add either column, 'Managers' or 'Stakeholders' 
    • Observe that neither field is available 
  2. Open the Hierarchy Object in Studio - go to the Attributes tab
    • Observe the two fields do not have an API alias 
  3. Try to add an API Alias and Save the record  

Expected Results: Either the attributes should show in MUX already or you can add an API alias to make them available in MUX. 

Actual Results: Attributes are not in shown in MUX and when you try to add an API alias the values get removed when the page is saved. 


Release : 15.9.x, 16.0.0, 16.0.1, 16.0.2  

Component : Clarity Studio 


DE65662  -

  • The fields were originally added to studio with plans to be used as part of the security model for Hierarchies. 
  • The API alias for these fields was not initially added to the object during the development of the functionality. 


Create custom fields for 'Managers' or 'Stakeholders' as a Multi-Valued Lookup using 'Browse Resource' (ID=BROWSE_PRJMGR). 

  • Product Management decided not the pursue the use of these stock fields for any built-in functionality. 
  • These fields are removed from the object in 16.0.3.