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

Document ID : KB000090219
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Failed Filetransfer Object does not trigger object which is defined in Runtime tab
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

 

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.