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.

API return wrong Lnr in case of Unlinked tasks

book

Article ID: 131797

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

There can be an inconsistency between JPP_LNR in the DB and what the API command JobPlanTask.getTaskLnr() returns in case of Unlinked tasks and External Dependencies. This occurs when Tasks are added by editing the Workflow in the XML. While modifying XML is not supported, these outputs should be consistent. 

Cause

Java API returns workflow tasks in wrong order, when tasks have no connection and END object has not the biggest lnr

Environment

Release: AUTWAB99000-12.2-Automic Workload Automation-Base Edition
Component:

Resolution

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

Fix version:
Component(s): Application Interface (Java API) 

Automation Engine v12.0.8 - Available
Automation Engine v12.1.5 - Planned release 2019-05-20
Automation Engine v12.2.3 - Planned release 2019-06-04
Automation Engine v12.3.0 - Planned release 2019-06-28
Powered by Wolken Software