Agile Process : webMethods BPM Process Development Help : Process Engine Processing : About Document Correlation : Correlation Behavior with Non-Starting Events and Activities
Correlation Behavior with Non-Starting Events and Activities
The following components can be configured to receive a document but not start a process or subprocess:
*Catching message intermediate event.
*Catching signal intermediate event.
*Receive task.
In some cases, the document may be delivered to these components when the process or subprocess they belong to is not running. In these cases, the following behavior occurs:
For this component...
The Process Engine...
Top-level Process
Performs a correlation based on a field or service, but because the process instance is not running, the document cannot be correlated. The Process Engine rejects the document and generates an exception that causes the trigger to determine what to do with the document.
BPMN Subprocess
Performs a correlation based on a field or service (assuming the parent process is running). If the BPMN subprocess instance is not running, the Process Engine rejects the document and generates an exception that causes the trigger to determine what to do with the document.
webMethods Subprocess
Performs a correlation based on a field or service (assuming the parent process is running). If the webMethods subprocess instance is not running, the document is correlated and delivered to the subprocess when the subprocess starts running.
The available trigger options are:
*Suspend the trigger after the specified trigger retries are exhausted.
*Discard the document after the specified trigger retries are exhausted.
These are standard trigger options; for more information, see the Publish-Subscribe Developer’s Guide.
Important:  
It is the trigger properties that control this document exception behavior and not the retry step properties.
Copyright © 2017 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback