Endevor Webhooks - Return code processing

Products

• Endevor

Issue/Introduction

Batch job got RC 12 due to the following error: 
C1G0168E  ELEMENT CANNOT BE ADDED BECAUSE IT IS NOT IN "SIGNED-OUT" STATUS IN ATEST/SYSTEST"

Endevor Webhook was created with a actionreturncode of 0000

{                                        
"actiontype":"ELM",                      
"action":"ADD",                          
"actiondate":"20200617",                 
"actiontime":"09584232",                 
"actionuserid":"<user ID>",                
"actionccid":"<ccid>",               
"actioncomment":"test",                  
"actionpackageid":"<package ID>",    
"processorgroup":"<processor group>",               
"lastprocessor":"*NOPROC*",              
"versionlevel":"0100",                   
"lastleveldate":"20200414",              
"lastleveltime":"11315710",              
"fingerprint":"<fingerprint>",        
"sitename":"<site name>", 
"elementname":"<element name>",                
"toenvironment":"<endevor environment>",                 
"tosystem":"<endevor system>",    
"tosubsystem":"<endevor subsystem>",   
"totype":"<element type>",     
"tostageID":"1",         
"actionreturncode":"0000"
}

Environment

Release : 18.0

Component : CA Endevor Software Change Manager

Resolution

APPLY PTF SO13803

PROBLEM DESCRIPTION:                                                         
Exit 3 is called for failed SISO check, causing invalid E-2-E logging.       
                                                                             
SYMPTOMS:                                                                    
On an ADD, UPD, GEN, RET, DEL and ALTER action when the signout check fails, 
the action is still logged to end to end logging even though the action      
was not initiated.