RAISEEXCEPTION Workflow Application
Overview
The RAISEEXCEPTION workflow application raises the cancel exceptions on specified actions, as controlled by the action cancellation workflow exception in the conditions definition panel. This workflow application can thus be called by an action to cancel one or several other actions in a running request. The application is converted as an assembly workflow to simplify configuration and improve performance.
The RAISEEXCEPTION web app in IIS and the file system folder (\wfgen\WfApps\WebServices\RaiseException
) can be disabled and removed. Authentication settings at the application level are not required.
This feature is useful when one or more actions need to be cancelled after a certain point in the workflow has been reached, even though those actions have already been activated. For example, if three parallel actions are ongoing, but one of the parallel actions is concluded ahead of the others and your workflow rules have determined that the two other actions are no longer required, you can activate RAISEEXCEPTION to cancel the other two actions and allow the workflow to continue.
Additionally, you can:
Use default parameters to cancel all open actions in a specific request.
Use optional parameters to cancel a list of action instantiations in a list of requests or to cancel on behalf of a specific user.
Use additional parameters to define multiple pairs of action references.
Default parameters
The REQUEST_ID
and ACTIVITY_NAME
parameters must always be used together.
📌 Example
In this example, the application will cancel all instances of the PENDING_ACTION
action in request 455
:
Optional parameters
The REQUEST_ID_LIST
and ACTIVITY_NAME_LIST
parameters must always be used together.
Examples
In this example, the application will cancel all the instances of the actions PENDING_ACTION1
and PENDING_ACTION2
in each of requests 445
, 446
, and 447
:
In this example, the application will cancel all the instances of the action named PENDING_ACTION
in request 445
on behalf of John Doe (jdoe
):
Additional parameters
📌 Example
In this example, the application will cancel all instances of the PENDING_ACTION1
action in request 455
and all instantiations of the PENDING_ACTION2
action in request 456
. If actions 455
and 456
have no instance then no error is raised.
Possible execution errors
The following errors can occur during the execution of the transactions:
Last updated