Parameterized lookup not working for Risks / Issues using PK_ID in New UX

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Parameterized Lookups in the Risk object using Lookup Parameter Mapping: ID to PK_ ID doesn't work properly in the New User Experience (UX). You see a warning message: One or more parameters 'param_id' are not API-enabled. You may see unexpected results.

This issue is reproduced for RISKS and ISSUES.

STEPS TO REPRODUCE: 

1. Create a custom object 
2. Create some instances of the custom object 
3. Create a dynamic lookup that retrieves the instances of the custom object 
4. Go to the Project Object and create a new attribute using the new dynamic lookup and place the lookup on the properties page (PrjLookup1) 
5. Create a parameterized dynamic lookup 
6. Go to the Risk Object and create a new attribute using the new parameterized dynamic lookup
   • Set the Parameter Mapping to the PK_ID
   • Add the attribute to the Risk properties page (RiskLookup1) 
7. Create Project X and select values from the 'PrjLookup1' field 
8. Create Project Y and select values from the 'PrjLookup1' field 
9. Go to Project X and create a new RISK 
10. Browse in the Risk parameterized lookup field 'RiskLookup1' 
11. Values displayed in the browse should only show ones based on the parameter for this project. It works fine in the Classic UI.
12. API enable the attribute RiskLookup1 on the Risk object, to have it also available on the New UX.
13. In the New UX, Go to Project X and click on the RISKS module.
14. Add the field RiskLookup1, from the Column Panel.
15. Select the field to display/modify the values on the existing Risk.

Expected Results: Values displayed for the field should only show ones based on the parameter for this project. 

Actual Results: Values for all projects are displayed in the browse. 
A Warning is triggered with the message "One or more parameters 'param_id' are not API-enabled. You may see unexpected results."

Cause

This is investigated as Defect DE54414.

Environment

Clarity PPM 15.x

Resolution

This is fixed in Clarity 15.9

Additional Information

See also: Lookups master KB for Clarity