You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of VanillaBP SPI I want to use Signals to start workflows or to correlate workflows waiting for a Signal.
There is a method ProcessService<WA>#broadcastSignal(String signal) to send Signals.
There is a method ProcessService<WA>#broadcastSignal<AU super WA>(AU aggregateUpdate, String signal) throws UnsupportedOperationEcxeption to send Signals. Since the workflows waiting for a Signal are selected by the underlying process-engine it is up to the specific adapter implementation to set the aggregate updated values. If a specific adapter is not able to fulfill this an UnsupportedOperationEcxeption is thrown.
Although the ProcessService bean is bound to a certain workflow aggregate WA (and therefore to BPMNs the workflow is bound to via @WorkflowServiceannotation) the Signal is not limited to the associated BPMNs.
If a Signal causes a workflow to be started (Signal start event), the aggregate's ID has to be extracted from aggregateUpdate or has to be set based on a value generated by the process-engine (checkout Signal issues in each specific adapter implemenation for details).
The text was updated successfully, but these errors were encountered:
As a user of VanillaBP SPI I want to use Signals to start workflows or to correlate workflows waiting for a Signal.
ProcessService<WA>#broadcastSignal(String signal)
to send Signals.ProcessService<WA>#broadcastSignal<AU super WA>(AU aggregateUpdate, String signal) throws UnsupportedOperationEcxeption
to send Signals. Since the workflows waiting for a Signal are selected by the underlying process-engine it is up to the specific adapter implementation to set the aggregate updated values. If a specific adapter is not able to fulfill this anUnsupportedOperationEcxeption
is thrown.WA
(and therefore to BPMNs the workflow is bound to via@WorkflowService
annotation) the Signal is not limited to the associated BPMNs.aggregateUpdate
or has to be set based on a value generated by the process-engine (checkoutSignal
issues in each specific adapter implemenation for details).The text was updated successfully, but these errors were encountered: