Using same PromptSet in Task within Workflow and in the Workflow results in U00003900 invalid value error

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
U00003900 Error in object '#SCRI.PRPT.1' (RunID '0001556114') prompt '#PRPT.YES.NO': Invalid value

Using the same promptset in a task in a workflow and in the workflow itself results in an error message similar to the one above.

Investigation

A simple workflow (WF) with a promptset is created, where one can chose YES or NO, the selection is stored in variable &YES_OR_NO#:
 

<Please see attached file for image>

The WF contains one script that just prints out &YES_OR_NO#, the script contains NO promptest:
 

<Please see attached file for image>

That works:
 

<Please see attached file for image>

Now the same promptest is added to the script as there is in the WF:
 

<Please see attached file for image>

The WF fails with:

U00003900 Error in object '#SCRI.PRPT.1' (RunID '0001556114') prompt '#PRPT.YES.NO': Invalid value

<Please see attached file for image>

Environment

OS Version: N/A

Cause

Cause type:
By design
Root Cause: This is standard prompt behavior. There is no value set in the Script object.

Resolution

There are 3 possible solutions to this issue:

1. Use only the second PromptSet. Set "Request User Input" for the task, so the prompt of the task will open as well.  See the documentation referenced below for additional information about the "Request User Input" option.

Automic Workload Automation 12.1 AWA Guide
User Guide > Process Assembly Perspective > Workflow Overview > General Tab

2. Set a default for the prompt of the task and the task will take the default.  For additional details see the documentation referenced below.

Automic Workload Automation 12.1 AWA Guide
User Guide > Process Assembly Perspective > Defining the Object-Specific Pages > PromptSet Activation

3. Use the variable of the workflow as a default for the task to inherit the entered value. 

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A