Open topic with navigation

TIBCO Business Studio™ - BPM Edition 5.4.0

# Throw and Catch Signal Events

With throw/catch signal events, an in-flow signal event broadcasts a signal, and if there is an active task with a signal event on the task boundary, that event "catches" the signal, and generally follows the exception path.

Signal events can be local or global.

Local signal events can be used for triggering event handlers, task cancellations and to halt and resume parallel flows.

Global signal events are thrown and caught across process instances allowing processes to collaborate with each other. They are only available for an event sub-process/handler.

- You can drag-and-drop a global signal onto a process to create throw / catch events.
- A catch signal can cancel the task it is attached to or, for user tasks, can allow the task to continue. If they are set to "continue" they cannot have an outgoing flow but they can map data into the task that they are attached to and also reschedule timers attached to the same task.

A Signal is transient: when it is thrown, if there is nothing to catch it at that moment, it is discarded. It is not stored for later use.

You might specify a signal name with a throw signal event. With a catch signal event, a signal name is optional:

- If a catch signal event has no signal name specified, it catches any thrown signals in the process (while the task it is attached to is active).
- If a catch signal event has a signal name specified, it only catches signal events that throw the named signal.

  When you specify signal names in the Properties view for signal events, you can use content assist. This means for example, that if you have entered SIGNAL1 for a throw signal event, when you specify the signal name for the catch signal event you can press Ctrl+Space and the available signal names are displayed from which you can select one.

You can define whether you want to update a scheduled work item from a non-cancelling signal event. Select from a pair of radio buttons directly beneath the signal name from the Properties view of a catch signal event attached to a task boundary:

- Cancel task when signal caught
- Continue task when signal caught

  Use the Map from Signal tab to map from the throw-signal's payload data (listed in its interface tab) to the data associated with the attached user task.

  See the example in Incoming Request/Global Signal Event Handlers in Business Processes which demonstrates the use of event handlers and non-cancelling signal events to update work item data.

A signal end event functions like any other inflow signal event, except that when one fires, if there are more tasks that need to complete as the result of an exception flow, the outstanding tasks complete; if there are no more tasks that need to be completed, the process ends.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Business Studio™ - BPM Edition

Copyright © 2015-2023. Cloud Software Group, Inc. All Rights Reserved.