Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to send signals #6

Open
stephanpelikan opened this issue Nov 8, 2024 · 0 comments
Open

Add ability to send signals #6

stephanpelikan opened this issue Nov 8, 2024 · 0 comments

Comments

@stephanpelikan
Copy link
Contributor

As a user of VanillaBP SPI I want to use Signals to start workflows or to correlate workflows waiting for a Signal.

  1. There is a method ProcessService<WA>#broadcastSignal(String signal) to send Signals.
  2. 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.
  3. 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.
  4. 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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant