Promptsets containing ampersands and post processing fail to evalutate correctly

book

Article ID: 84601

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
U00021719 Syntax error in object 'JOBS.AMPERSAND', line '00000'. 'U01001308 Variable 'NAME2' has not yet been defined.'.

 A Workflow contains one job (JOBS). The job contains a Prompt Set. The Prompt Set contains on input-field for text. In the task properties of the job in the workflow, this value is filled with a string containing an ampersand &:


 


The job only pints this value in its script:


In the Postscript, there is only one exclamation mark !:

 

Trying to execute this, it fails:

 

For details see problem directory, RunIds in screenshot above. The error in the JOBS is:

U00021719 Syntax error in object 'JOBS.AMPERSAND', line '00000'. 'U01001308 Variable 'NAME2' has not yet been defined.'.

As you see in the error message above, the inserted name NAME1&NAME2 was cut at the &.

If you enter the name with three & (you escape it), the behavior changes:

 

For details see problem directory, RunIds in screenshot above. It fails with:

FAULT_POST_PROCESSING - Error in post processing.

But if you remove the post processing in the JOBS

 

it works with &&&:

 

For example, a name with an & cannot be passed correctly to the job from a Prompt Set. A workaround is to escape it with &&. However, as soon there is anything in the Post Script (as you see in the example it's only an exclamation mark), the job fails.

The documentation here deals with ampersand: https://docs.automic.com/documentation/webhelp/english/AWA/12.0/DOCU/12.0/AWA%20Guides/help.htm#AE_AWA_Source/Script/ucacvb.htm. and states, a second & for escaping should be sufficient. But is shows nowhere, that in such a case three ampersands are necessary. But then it only works as long as you use no post script.

Cause

Cause type:
Defect
Root Cause: Using two ampersands (&&) characters did not work in post-process. Escaping a & character works for promptset values and can be used for normal script execution but lead to an error in post-process: "U00021719 Syntaxfehler in Objekt 'JOBS.1', Zeile '00000'. 'U01001308 Variable 'VAR' has not yet been defined.'."

Environment

Release: Automic Workload Automation
Component: Automation Engine

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Fixed

Fix Version(s):
Automation Engine 12.2.0 - Available
Automation Engine 12.1.1 - Available
Automation Engine 12.0.4 - Available
Automation Engine 11.2.7 - Available
Automation Engine 11.1.8 - Available

Additional Information

Workaround :
Use a third ampersand and no post processing.

Attachments