Currently, setting SKIP by GetUser post-script, when it is called by the Notification Server (CTSACD), causes the Notification Server sending DeleteUser event to IIQ / ISC and hence delete it from the IIQ / ISC database.
Once this fix is applied, SKIP returned by GetUser post-script when it is called by the Notification Server (CTSACD) causes the Notification Server (CTSACD) to ignore the event and not send it to IIQ / ISC.
The SKIP behavior when it is called by the Transaction Server (CTSACS) GetUser post script remains the same. Which means, if SKIP is returned, the account's record is not sent to IIQ / ISC. Currently, setting SKIP by GetUser post-script, when it is called by the Notification Server (CTSACD), causes the Notification Server sending DeleteUser event to IIQ / ISC and hence delete it from the IIQ / ISC database.
Once this fix is applied, SKIP returned by GetUser post-script when it is called by the Notification Server (CTSACD) causes the Notification Server (CTSACD) to ignore the event and not send it to IIQ / ISC.
The SKIP behavior when it is called by the Transaction Server (CTSACS) GetUser post script remains the same. Which means, if SKIP is returned, the account's record is not sent to IIQ / ISC.
