Classic - Job parameter default value not saving correctly.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

You have configured both "Custom Extract" and "Custom Extract All" values in Data Extract Custom Object. However, when we select "Custom Extract" in the job parameters and save the job, it is automatically displayed as "Custom Extract All" instead of "Custom Extract".

 

Steps to Reproduce: 

 

1. Create Custom Object called Data Extract

2. Assign all necessary rights to Admin user to this newly created object.

3. Navigate to Home->Custom Objects->Data Extract List

4. Create couple of instances as below:

a) Name = Cust Extract 1, ID = cc_cust_extract

b) Name = Cust Extract All, ID = cc_cust_extract_all

5. Navigate to Administration->Data Administration->Reports and Jobs

6. Create new Job Definition with any name, Executable Type = Java and Executable Name = com.niku.bpm.jobs.ExecuteProcessJob

7. Click on Parameters tab and create a parameter with type = Browse and choose Data Extract Instances lookup (out of the box lookup which was created as part of custom object created in Step 1 above).

8. Select Default value for this parameter and set it to "Custom Extract", click Save.

9. Notice value gets reverted to "Custom Extract All"

 

Expected Results: it should keep the value user selected.

 

Actual Results: it reverts the value to another value.

 

Workaround: make id of the custom instances more unique.

Environment

Clarity 16.x

Cause

DE194484

Resolution

Under review by Engineering team.