Dan 5f6a61c93f * SpiffWorkflow event_definitions wanted to return a message event's correlation properties mested within correlation keys. But messages are directly related to properties, not to keys - and it forced a number of conversions that made for tricky code. So Messages now contain a dictionary of correlation properties only. ... * SpiffWorkflow did not serialize correlations - so they were lost between save and retrieve. * When comparing Correlation Property values - we are storing these values as strings in the database and can't convert them back to integers later, so I'm changing everying everywhere to compare after conversion to a string. Don't feel great about this one. * By using an SQL Alchemy join table, there is a lot of db queries we don't need to write. * A few handy fucntions on db models to make it easier to work with correlations. * Updated tests because I changed some of the BPMN models we were testing against. * Database migration to use the new constraint names with the alternate form of the join table between correlation mesages to instance messages.		2023-02-20 11:50:35 -05:00
..
data	* Re-work message tests so I could wrap my simple head around what was happening - just needed an example that made sense to me.	2023-02-18 13:09:58 -05:00
files	Merge commit '883e65384f1e36a0310f4fdcff57ac486890cd5e' as 'spiffworkflow-backend'	2022-10-12 10:22:22 -04:00
spiffworkflow_backend	* SpiffWorkflow event_definitions wanted to return a message event's correlation properties mested within correlation keys. But messages are directly related to properties, not to keys - and it forced a number of conversions that made for tricky code. So Messages now contain a dictionary of correlation properties only.	2023-02-20 11:50:35 -05:00
__init__.py	Merge commit '883e65384f1e36a0310f4fdcff57ac486890cd5e' as 'spiffworkflow-backend'	2022-10-12 10:22:22 -04:00
test_main.py	pyl is passing w/ burnettk cullerton	2022-11-18 16:45:44 -05:00