ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

AWA: Script elements sys_act_top_nr/sys_act_top_name produce incorrect values in a nested workflow.

book

Article ID: 145740

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

When using the script element SYS_ACT_TOP_NR and SYS_ACT_TOP_NAME in a nested workflow where a task involved in the chain is inactive, these elements do not provide the correct returns:

For Example:
Workflow JOBP.MAIN 
|__> Workflow JOBP.SUB1 
|__>Script WAIT.1SEC 
         |__> Workflow JOBP.SUB2 
                 |__> Script SCRI.NEW.3 
 
In SCRI.NEW.3 the following script is defined:
:set &TOP_NR# = sys_act_top_nr()
:set &TOPNAME = sys_act_top_name()
:print 'Top-Object: <&TOPNAME>  &TOP_NR#'
 
If the 'Active' flag on script element WAIT.1SEC is NOT ticked the incorrect value is returned:
U00020408 Top-Object  : <JOBP.SUB1> 
 
If the 'Active' flag on script element WAIT.1SEC is ticked the correct value is returned:
U00020408 Top-Object: <JOBP.MAIN> 
 

Cause

This is due to improper handling of inactive objects in a workflow

Environment

Release : 12

Component : AUTOMATION ENGINE

Resolution

This has been fixed in the following versions:
Automation.Engine 12.0.10
Automation.Engine 12.1.8 
Automation.Engine 12.2.5
Automation.Engine 12.3.2