8cc2d56dbd
merged in main and resolved conflicts w/ burnettk
2023-04-20 14:10:23 -04:00
08271da363
store stacktrace as a json array so we can reverse it when displaying and fixed up display of errors
2023-04-20 08:31:55 -04:00
ff0202f4d4
Called elements ( #218 )
2023-04-19 18:07:15 -04:00
9254d19b74
display event errors in the frontend using errorDisplay w/ burnettk
2023-04-19 15:20:19 -04:00
320d1b4083
store process instance errors in the db w/ burnettk
2023-04-19 11:24:54 -04:00
8fe98812fc
try to make single process hash unique within full process model hash
2023-04-17 15:42:58 -04:00
fecbb3f040
added new column to bpmn process definition to store the full bpmn process hash digest w/ burnettk
2023-04-17 12:01:36 -04:00
0ae74f8f35
removed spiff step details w/ burnettk
2023-03-23 16:33:30 -04:00
bc58de809e
use task table for process instance show page. spiff steps are not working yet and neither is data w/ burnettk
2023-03-20 16:51:29 -04:00
50acac8160
some more index updates and a new migration for it w/ burnettk
2023-03-17 16:52:05 -04:00
3ca165bb94
recreated migrations to remove spiff logging w/ burnettk
2023-03-17 15:50:05 -04:00
88df3bd5c3
added process instance event table
2023-03-17 13:20:06 -04:00
363428df09
added bpmn_name columns to definition tables and added test for simple logs as well
2023-03-17 10:00:59 -04:00
d3393fc6d0
added bpmn process definition to bpmn process w/ burnettk
2023-03-16 16:59:37 -04:00
bbdac3c586
some initial code to use tasks for logs
2023-03-16 09:30:25 -04:00
bc619af0a0
check data when running main spiff test w/ burnettk
2023-03-15 15:38:58 -04:00
ceca4d1333
unit tests are passing w/ burnettk
2023-03-15 11:25:15 -04:00
764eb35d1b
Move process instance locking to new queue table ( #177 )
2023-03-14 13:12:01 -04:00
87bacbdaaf
added some timestamp fields to bpmn process tables w/ burnettk
2023-03-07 10:41:54 -05:00
96ef81af34
merged in main and resolved conflicts w/ burnettk
2023-03-06 11:15:16 -05:00
e55485bd4a
removed process instance data and serialized bpmn definition models w/ burnettk
2023-03-06 11:13:53 -05:00
2cdacfa03b
some stuff is passing but still needs the process_instance_data w/ burnettk
2023-03-03 16:51:24 -05:00
14e12645c4
get longblob on mysql, reset migrations since we are going to do that anyway in hours
2023-03-03 14:04:02 -05:00
4eef585136
recreated migration from new one in main
2023-03-03 13:08:30 -05:00
40a3515d4e
Merge remote-tracking branch 'origin/main' into feature/split_up_bpmn_json
2023-03-03 13:04:26 -05:00
b4546e86e6
Special case file data during user form submission ( #164 )
2023-03-03 12:24:18 -05:00
f7c46cd945
recreated branch migration w/ burnettk
2023-03-03 12:08:36 -05:00
8c60080663
set the collation on the db directly and not in the models w/ burnettk
2023-03-03 12:05:12 -05:00
276e6d5f37
recreate migrations to set case sensitive columns for mysql w/ burnettk
2023-03-03 11:41:34 -05:00
d7f4c8ba95
clean up bpmn process definition save code a bit w/ burnettk
2023-03-03 11:24:28 -05:00
0c6e9a63ba
unit tests are passing with the new spec tables
2023-03-03 10:08:14 -05:00
8d67e8cc87
we can save the top level spec to the database with its tasks w/ burnettk
2023-03-02 17:28:31 -05:00
716986a483
prefer the bpmn process name over the identifier on the logs list page w/ burnettk
2023-03-01 16:28:42 -05:00
6521998a54
fixed the downgrade in new migration w/ burnettk
2023-03-01 15:54:50 -05:00
59c5ed296d
removed old branch migrations and created single one for this branch w/ burnettk
2023-03-01 15:40:17 -05:00
e2891425fc
store the process instance data id on the process instance and not the other way around w/ burnettk
2023-03-01 11:39:03 -05:00
f74ce0f568
some logic to attempt to use the new bpmn json tables w/ burnettk
2023-02-28 17:46:14 -05:00
d5acd5a16d
added new table and some notes on how to get a delta w/ burnettk jbirddog
2023-02-28 16:30:52 -05:00
a5c6d262b8
slam migrations file one last-ish time, increase task_name column length
2023-02-27 22:03:42 -05:00
45feb38168
recreated all migrations to resolve postgres migration failures w/ burnettk
2023-02-27 17:27:53 -05:00
7c12709fdd
fixed conflict with db migrations w/ burnettk
2023-02-27 14:33:55 -05:00
dfac872606
Merge remote-tracking branch 'origin/main' into feature/script_get_last_user_completing_task
2023-02-27 14:28:23 -05:00
9f84564457
script to get last user completing a task is working w/ burnettk
2023-02-27 12:08:07 -05:00
e9b3ababc1
wip for get_last_user_completing_task script task
2023-02-25 23:31:23 -05:00
0dc2bc3316
# SpiffWorkflow:
...
1) Type Safe checking on correlation properties (no more str())
2) A running workflows Correlations are once again at the key level.
# Backend
1) Both send and receive messages can have correlation_keys - and we compare these to each other to quickly assure a match (if they both exist - otherwise we fall back to comparing the properties on the receive to the sending messages payload)
2) Cleaned up the migrations to just one file
2023-02-24 14:53:22 -05:00
5a3b4b8792
BPMN Parser was returning all retrieval expressions, rather than the ones specific to a correlation property, as was intended.
...
Adding a correlation cache - so we have a reference of all the messages and properties (though still lacking a description of keys)
Adding yet another migration, maybe should squash em.
2023-02-23 16:36:32 -05:00
8466d823c2
Adding Migration.
2023-02-23 14:42:00 -05:00
0030a46938
run_pyl
2023-02-23 14:17:22 -05:00
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
8e257600af
work in progress -
...
* Link between message instance and correlations is now a link table and many-to-many relationships as recommended by SQLAlchemy
* Use the correlation keys, not the process id when accepting api messages.
2023-02-17 10:45:01 -05:00
jasquat
jbirddog
burnettk
Dan