search cancel

Failed Filetransfer Object does not trigger object which is defined in Runtime tab

book

Article ID: 90219

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Failed Filetransfer Object does not trigger object which is defined in Runtime tab

Environment

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

Resolution

 FailedFiletransfer Object does not trigger object which is defined in Runtime tab

 

Steps toreproduce:

 Create anFiletransfer Job Object which runs not ENDED_OK by default

 Define inruntime tab an OS Returncode > 0 for ENDED_OK

 and choosean object to else-execute

 run the FTJob

 

=> The Objectwill never be executed because (OS) Return Code will never be different than 0

 

<Please see attached file for image>

0EMb0000000OKDW.png

 

Background:The file copy process never gets any returncode from the OS and remains 0 all time.

Affected Versions: ALL 

Alternative:

 Use filterobject, Script command PREP_PROCESS_REPORT or Script command GET_UC_OBJECT_STATUS or put the FT Object in a workflow toreact on a fail of the FT.

 

 

 

 

 

 

 

 

 

 

 

Attachments

1558693283542000090219_sktwi1f5rjvs16m4p.png get_app