I was under the impression that if a Phase 3 action on a submit filter met with ARERR error, then the submitted record will still be present on the form , will not get deleted or rolled back. However, I observed quite the contrary on ARS 8.1.02. Have you come across this before and how did you overcome?
I have a custom form on ITSM 8.1.02. Another system creates records into the custom form by consuming Remedy’s web service [USER: webservices.user]. A filter on submit on the custom form has a Run process action that executes a batch file. The batch file uses BMC javadataimport utility to import status into the same record that was just submitted [User: import.user]. Merge filters fire when that particular status value is set. One of the merge filters met with ARERR. After that the record submitted also got deleted ! Is this expected behavior?
> 1: Push Fields -> "SRM:SMI:InboundTxn_inbound-notify-ack`!" (ARERR 286)
<FLTR> <TID: 0000011628> <RPC ID: 0002073827> <Queue: Fast > <Client-RPC: 390620 > <USER: import.user > <Overlay-Group: 1 > **** Error while performing filter action: Error 286
<FLTR> <TID: 0000011628> <RPC ID: 0002073827> <Queue: Fast > <Client-RPC: 390620 > <USER: import.user > <Overlay-Group: 1 > **** Filter "SRM:SMI:InboundTxn_inbound-notify-ack`!": No enabled error handler
End of filter processing (phase 1) -- Operation - MERGE on SRM:SMI:StagingForm - TSF000013524329
*/DELETE FROM T3636 WHERE C1 = 'TSF000013524329'