Open topic with navigation

TIBCO Business Studio™ - BPM Edition 5.4.0

# Event Persistence

Because a process interface does not specify the intended location of the event within the flow of the process implementation, events are considered "persistent".

As such, they can be triggered at any point in the process flow that is upstream of the event, or when the flow is paused waiting for the event to be triggered. For example:

The trigger for the intermediate event can be received while Task A or B is being processed, or when the flow is paused at the intermediate event waiting for the event to be triggered. In either case, Task C is not processed without an event trigger. If the trigger is received during processing of Task A or B, the trigger arrival is persisted, and the event is triggered immediately when it is reached in the flow.

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.