Promptset Date handling during restart blocks ability to restart


Article ID: 84535


Updated On:


CA Automic Workload Automation - Automation Engine


Error Message :
Java: Date: Error in object 'JOBS.WIN.NEW.1' (RunID'#######') prompt 'PRPT.NEW.1': Input '10/18/17' for Calendar 'CALE.NEW.4', keyword 'OCTOBER' is not valid.

AWI: Invalid value '171018' in property 'Default Value' of the promptset date field 'Time/Date' (expected format: 'yyyy-MM-dd HH:mm:ss'). The field will be reset to the current system datetime.

When doing a restart of a Workflow task that has a Promptset that includes a date object, the restart process can fail to populate the date object properly, and this can result in the restarted task getting stuck in "generating" state.

Manual intervention is needed to change the date from the promptset pop up. 

Error screenshot from the Java UI:

Error screenshot from the AWI:


Cause type:
Root Cause: Prompts do not set their defaults correctly when a specific date format is used. The value of the latest restart is not parsed correctly and an "invalid value" error message is shown.


Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition


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


Fix Status: In Progress

Fix Version(s):
Automation Engine 12.2.0 – Available
Automation Engine 12.1.1 -  Available
Automation Engine 12.0.5 – Available
Automation Engine 11.2.7 – Available

Additional Information

Workaround :
Manually go in and set the promptset date again.

For Java UI the user needs to click on the date picker, choose the date again, then submit the promptset. 

For Automic Web Interface (AWI) the user doesn't need to click the date picker, just submit the promptset again. 


Only use Output format of YYYY-MM-DD with promptsets.