![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
To facilitate the re-use of process components, an activity (or several activities) can call another process as a reusable sub-process. The reusable sub-process could be a process that you have already created, or you can refactor activities in your current process into a reusable sub-process (see Refactoring Sub-Processes).In this example, Run Credit Check is an embedded sub-process. This implies that running a credit check is an activity that is not needed by other processes. If you subsequently decide that you want to be able to run a credit check from within other processes, you can expose the embedded sub-process as a reusable sub-process by refactoring it. See Refactoring Sub-Processes.In this example, Run Credit Check is an embedded sub-process. This implies that running a credit check is an activity that is not needed by other processes. If you subsequently decide that you want to be able to run a credit check from within other processes, you can expose the embedded sub-process as a reusable sub-process by refactoring it. See Refactoring Sub-Processes.To create an embedded sub-process, refactor one or more objects in your process as described in Refactoring Sub-Processes.
If you want to use the chained execution resource pattern, you can do so by selecting the Chained Execution check box in the Properties view for the embedded sub-process. For more information, see Chained Execution.A sub-process (either embedded or independent) can be specified as a transaction using the Is a transaction check box. This means that the behavior of the sub-process is governed by a transaction protocol (defined in the runtime environment). This is indicated by a double-line around the activity:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |