pub.prt.CallActivityModel
WmPRT. Document type that describes the information needed to dynamically invoke one or more callable processes.
Important: This document type is used with callable processes only. If you are working with the deprecated ability to dynamically invoke a referenced processes from a call activity step, see
pub.prt.SubprocessModel for more information.
Input Parameters
WaitForCallActivity | String Flag indicating whether to wait for the child process (as done with statically invoked process), or to launch it asynchronously and not expect any return documents. Applies to all process instances started from the document type.  true — Default. Wait for the child process. false — Start the child process asynchronously and do not expect any return documents. |
CallActivityModelID | String The identifier of the callable process model in the format: Project/Process. |
OutputPipelineName | String The name of the output pipeline to be returned back from each child process. No value is needed here if a value of false is used for WaitForCallActivity. |
InputPipelines | Document list A list of instances that are to be started for the specified callable process model. For example, if you have 10 line items to process, there will be 10 documents in this list. |
Output Parameters
None.
Usage Notes
To enable successful execution of a dynamically invoked callable process, you must ensure that these values are in the process pipeline prior to any activity (for example, input data mapping) that applies to the call activity step.
Suppose you have specified OutputPipelineName and a WaitForCallActivity value of true. In this case, the Process Engine waits for all instances of the child process to complete and populates the pipeline with data from each child process instance, obtained from the returned document(s). This data is now available for use.
In another example, suppose that three instances of the child process LineItem are started, and each of these instances is expected to return an output pipeline of the name LineItemPrice. In this case, the LineItemPrice data is added to the pipeline and the data in it is available for use. The order of the documents in the list is the same as the order of invocation. This enables easy location of the data in the pipeline by using the OutputPipelineName value.