Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 9 Using Event Steps : Suspending the Flow of a Case

Suspending the Flow of a Case
A case can be suspended by linking to the left of an Event from the release action (i.e. the right hand side) of a Step. When the Step is released this branch of the case is suspended, and an entry is written to the Audit Trail to show that an event is outstanding.
To restart the case, an external process must send a trigger to iProcess, causing the ‘release’ actions defined on the event step to be processed.
The trigger is sent by calling the SWDIR\bin\swutil utility. If required, fields may be updated by including an abox file in the event command line - see Externally Updating Field Data in a Case for more information.
Note that in the example shown above, if the Event is never triggered, that branch of the case will be suspended indefinitely.
To avoid this scenario, consider the alternative shown in the following diagram. In this scenario, if the Event (S2) is not triggered by the external program within the defined deadline period, the case will proceed to the S4 step (a reminder, escalation step) when the deadline expires.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved