Error Message :
PromptSets that use a non-existing variable, generate a forced trace. Tasks using such a prompt will hang in a "Resolving Variables".status.
If, for example
Then upon execution
- Task A contains a promptset that uses a VARA.EXEC as a data reference
- This VARA.EXEC executes task B that gets values from a non-existing VARA (with GET_VAR)
- Task B will fail.
- Task A will remain in "Resolving variables" status.
- A forced trace will be generated by the Automation Engine server.
VARA.EXEC.ADDITION executes SCRI.ADDITION with &OPE1# and &VARA# as input values. &OPE1# is set with value '1' and &VARA# with 'VARA.STATIC.OPE', the name of a static variable. However this variable does not exist.
SCRI.ADDITION uses GET_VAR to read a value from &VARA# (static variable 'VARA.STATIC.OPE'):
PRPT.ADDITION contains a combo box which uses VARA.EXEC.ADDITION as a data source:
PRPT.ADDITION is nested in SCRI.PRINT.RESULT:
Expected: Upon execution of SCRI.PRINT.RESULT, the Automation Engine should return an error message stating that the variable object is missing and cannot be resolved.
Actual: Previewing VARA.EXEC.ADDITION causes errors, which is the desired behavior:
However, when running SCRI.PRINT.RESULT, it stays in 'Resolving variables' status and may not be canceled.
A forced WP trace is written by the Automation Engine server.
OS Version: N/A
Root Cause: A prompt, based on a non-existing variable results in a forced trace. The task, using the prompt, will hang in "Resolving Variables".
Update to a fix version listed below or a newer version if available.
Fix Status: Released
Component(s) : AE Server and Initialdata
Automation Engine 12.1.0 - Available
Automation Engine 12.0.3 - Available
Automation Engine 11.2.6 - Available