Issue

Legacy out-of-the-box (OOTB) user reference properties are not available for selection when authoring Pega Constellation Views despite being marked as relevant. 

 Examples properties are pyUserIdentifier, pxStatusStartOperator, and pxStatusCompleteOperator. 

Symptoms and Impact

Steps to reproduce

1. Open a Constellation application that contains a legacy OOTB user reference property. 
   • Examples include: 
     1. pyUserIdentifier 
     2. pxStatusStartOperator 
     3. pxStatusCompleteOperator 
2. Mark the property as Relevant. 
3. Configure a Table View or List View. 
4. Attempt to add the user reference property as a column. 
5. Observe that the property does not appear in the authoring interface. 

Root Cause 

This is a product defect.  Constellation uses additional validation logic that checks for required associations before user reference properties are exposed in authoring.  Similarly, legacy OOTB user reference properties may not satisfy all the configuration requirements expected by Constellation.   

As a result, the properties are excluded from authoring even when they have been marked as relevant. 

The exact configuration requirements can vary between properties. In some cases, updating the UI control is required. In other cases, the issue is resolved through association configuration and property qualifiers.  

 Configuration requirements expected by Constellation:   

• User reference properties are supported only with pxDropdown or pxAutoComplete controls. 

• User reference properties must be backed by an association with Data-Admin-Operator-ID. 

• Required association metadata must be configured under property qualifiers. 

• The association name is required to match the property name. 

 Additionally, runtime components contain safeguards to resolve usernames, but as we have seen, the authoring layer performs association validation before exposing the property. 

Solution 

For any affected legacy OOTB user reference property follow the steps below: 

1. Open the property rule. 
2. Review the configured UI control. 
3. If the property uses pxTextInput, update the control to: 
   • pxDropdown, or 
   • pxAutoComplete 
4. Create or verify the required association with Data-Admin-Operator-ID. 
5. Add the required association under the property qualifiers. 
6. Verify that the association name matches the property name where required. 
7. If a Report Definition is used as the source of the Data Page, verify that the required report columns are optimized for reporting. 
8. Save the configuration changes. 
9. Reopen the Constellation authoring experience and verify that the property is available for selection. 

Local change specific to pyUserIdentifier 

The following configuration will fix scenarios encountered with pyUserIdentifier: 

1. Create an association rule named UserIdentifier. 
2. Open the pyUserIdentifier property rule. 
3. On the Advanced tab, add the pxSimpleAssociation qualifier. 
4. Set the qualifier value to UserIdentifier. 
5. Ensure the association rule name matches the property configuration. 
6. Save the changes. 
7. Reopen the Constellation authoring experience. 
8. Verify that pyUserIdentifier appears as an available field. 
9. Add the property to the view and verify that User ID values are displayed. 

Local change specific to pxStatusStartOperator and pxStatusCompleteOperator 

The following configuration will fix scenarios encountered with pxStatusStartOperator and pxStatusCompleteOperator: 

1. Open the property rule.  

2. On the General tab change the UI control from pxTextInput to pxDropdown or pxAutoComplete. 

3. Create the required association with Data-Admin-Operator-ID. 

4. On the General tab add the association under the property qualifiers. 

5. Save the configuration. 

6. Revalidate authoring visibility and runtime population. 

These changes restore visibility of the properties in authoring. 

This issue is planned to be addressed in a future Pega Platform™ release. This section will be updated with release details when the fix for this issue is available. 

References

Introduction to reference fields 

Configuring a user reference field