Flow: Abort User Operation
The Flow: Abort User Operation action is used to allow administrators to abort a user's requested operation. The action is only available with the Message composed event trigger.
For example, using the Event Rule as defined below, when a user defines a message in the Send portal and attempts to send a file that contains a credit card number, the file is sent to the ICAP server to be scanned and then the file is blocked or redacted because of the credit card number and moved to a quarantine location.
In this case, the Abort user operation action blocks the message from being sent, the user receives a failure message, and the Workspace is not created.
-
This action cannot be configured to run asynchronously.
-
The ICAP server
-
The response code is always 403; the Advanced Property, AbortUserOperationHTTPCode can be used to set a different value.
-
The response message is derived from EFT message templates for HTTP response codes.
-
The headers sent back are the standard ones used for a normal failure situation.