Commit Graph

9 Commits

Author SHA1 Message Date
burnettk b9fd9279e0
Merge commit '7db152f01049e0b788ccbfd3ce2358987df67cdc' 2023-08-09 16:14:32 -04:00
burnettk 4e6da23728
Merge commit 'a1c7cecf59b6f9aa0824f360a1a8879edb9f28b8' 2023-05-29 17:31:40 -04:00
Dan e9a8ccd1a0 Merge commit '1be006811bffa292cbecba02e99161ac94b96c8a' into main 2023-03-03 14:31:23 -05:00
Dan 8c673c4fb6 BPMN.io -- Just show the message names not the ids - to assure we are only exposing the names.
SpiffWorkflow -
    - start_messages function should return message names, not ids.
    - don't catch external thrown messages within the same workflow process
    - add an expected value to the Correlation Property Model so we can use this well defined class as an external communication tool (rather than building an arbitrary dictionary)
    - Added a "get_awaiting_correlations" to an event, so we can get a list of the correlation properties related to the workflows currently defined correlation values.
    - workflows.waiting_events() function now returns the above awaiting correlations as the value on returned message events
 Backend
    - Dropping MessageModel and MessageCorrelationProperties - at least for now.  We don't need them to send / receive messages though we may eventually want to track the messages and correlations defined across the system - these things (which are ever changing) should not be directly connected to the Messages which may be in flux - and the cross relationships between the tables could cause unexpected and unceissary errors.  Commented out the caching logic so we can turn this back on later.
    - Slight improvement to API Errors
    - MessageInstances are no longer in a many-to-many relationship with Correlations - Each message instance has a unique set of message correlations specific to the instance.
    - Message Instances have users, and can be linked through a "counterpart_id" so you can see what send is connected to what recieve.
    - Message Correlations are connected to  recieving message instances.  It is not to a process instance, and not to a message model.  They now include the expected value and retrieval expression required to validate an incoming message.
    - A process instance is not connected to message correlations.
    - Message Instances are not always tied to a process instance (for example, a Send Message from an API)
    - API calls to create a message use the same logic as all other message catching code.
    - Make use of the new waiting_events() method to check for any new recieve messages in the workflow (much easier than
    churning through all of the tasks)
    - One giant mother of a migration.
2023-02-23 13:53:03 -05:00
Dan d7c4273c76 minor fixes to the Bpmn-js-subworkflow spec. 2022-11-16 16:31:47 -05:00
Dan 48da265837 Fixing a bug in the Call Activity's handing of an update. 2022-11-14 12:23:22 -05:00
Dan 96c26af365 Merge commit '9213cea140508842d4ae3cc30cc2eee58e4f9efe' into main 2022-11-07 14:35:53 -05:00
burnettk bc625233db Merge commit '29020904199084a2307736fa2f1b56bcea389bd8' 2022-10-31 17:02:34 -04:00
Jon Herron 3d67643a57 Merge commit '1d3a4921792fc2a39facbb1c6aa0b6aa05539baf' as 'bpmn-js-spiffworkflow' 2022-10-12 10:21:19 -04:00