Promptset not updated in job when editing the promptset object

Products

• CA Automic One Automation

Issue/Introduction

Under certain conditions the promptset is not updated in a job when making edits to the promptset object

1. Create promptset with text field
2.  Populate the text field
3. Add promptset to a job object
4. Run job and don't change the promptset value. Note on the report that the value is as defined in the promptset
5. Edit promptset and change the text field.
6. Run job again. Note on the report the value is not updated from the promptset

Cause

When the job is run, it looks for an entry for the job in the OPUD table using the OPUD_OH_Idnr which matches up with the object definition in the OH table using the OH_Idnr.  The OPUD table is used to store object-specific promptset information.

If it does not find an entry in the OPUD table that matches the used promptset (OPUD_PName) and the specific promptset entry (OPUD_VName), then it uses the entry from the promptset. 
However, if it does find an entry in the OPUD table that matches, it will use the OPUD info for the job object instead.  

With this defect in the product, the OPUD table was filled in when the promptset was added instead of when the prompts were changed within the job.

Resolution

This defect was fixed with 12.3.8 and 21.0.1

Workaround:
1. Remove promptset from job and re-add it back

2. Edit promptset when executing job