In a workflow context, if the alias's definition of a tasks is set via variables
The global resolution of this/these variables has length that is smaller than 200 characters.
the activation report of the JOBP will contain similar
2023-08-18 16:43:58 - U00020408 KITEKAT.SNICKERS.TUTTIFRUTTI.PIZZAMARE
2023-08-18 16:43:58 - U00007061 Alias for task 'JOBS.BOPB.BOPB.1' (Lnr: '00002') is too long and gets trimmed.
2023-08-18 16:43:58 - U00007061 Alias for task 'SCRI.BOPB.001' (Lnr: '00003') is too long and gets trimmed.
2023-08-18 16:43:58 - U00007000 'JOBS.UNIX.BOPB.1' activated with RunID '0001419006'.
2023-08-18 16:43:59 - U00007000 'SCRI.BOPB.001' activated with RunID '0001419007'.
U00020408 is a printout of the alias, its length is shorter than 200 chars.
If the alias name is hard corded as in the message U00020408 the problem does not occur.
To reproduce the problem:
Create a Workflow
In the Process declare variable as follows
:set &DOMAIN#='SNICKERS'
:set &Application#='TUTTIFRUTTI'
:set &USER#='PIZZAMARE'
:set &WORT1#='KITEKAT.&DOMAIN#.&Application#.&USERS#'
:p &WORT1#
Insert 2 tasks
Under alias for each tasks set &WORT1#
If this workflow gets executed the U00007061 messages will be present in the activation report of the Workflow.
This has no impact on the execution, in Process Monitoring the alias will be displayed entirely!
Automation Engine up to version 21.0.9
This is a defect of the Automation Engine
This bug is fixed in version 21.0.10 of the Automation Engine.
Resolution : A problem has been solved where the error message U00007061 was written to the activation report, when variables where used in tasks alias. There was no other functional impact.
Bug ID: AE-33307
Bug Title: U00007061 Alias for task ... is too long and gets trimmed.