Synchronous and Asynchronous Sub-Process Invocations

Sub-process invocations can be performed synchronously or asynchronously in relation to the invoking process flow.

Use synchronous sub-process invocation when you want the process to wait for the sub-process to complete before the main process can proceed.

Use asynchronous sub-process invocation:
  • when you want sub-processes to run separately from the main process, and the sub-process does not need to complete for the main process to complete. The invoking process can complete faster without waiting for the sub-process.
  • when you want to run sub-processes in parallel with the main process without sacrificing migratability, and when you do not want to hold up the main process.
Note: Use asynchronous attached sub processes when you want to run sub-processes in parallel with the main process without sacrificing migratability, and when you do not want to hold up the main proces.

Choose the invocation mode of a Call Sub-Process activity from the Properties tab, by selecting General > Lifecycle > Invocation Mode):

  • Synchronous: the invoking process flow waits for completion of sub-process.
  • Asynchronous Attached: The invoking call activity completes immediately and flow continues. The sub-process will be cancelled with parent process, the parent process will not be considered complete until sub-process completes.
  • Asynchronous Detached: The invoking call activity completes immediately and flow continues. The sub-process lifecycle is independent of the invoking process.

Pageflow Processes (including Business Service, Case Action) can invoke Business Processes in asynchronous detached mode). See "Starting a Business Process from a Pageflow (Business Services)" in TIBCO Business Studio™ - BPM Implementation.