* move data migration code out of bin so it can be reused in background processor
* sleep for 5 minutes and update bpmn js to pull in some fixes from elizabeth
* update spiff to pull in parser update to make it act like before
---------
Co-authored-by: burnettk <burnettk@users.noreply.github.com>
* use carbon components when adding secrets
* docker compose pull before running up w/ burnettk
* use all carbon on script task unit test modal w/ burnettk
* removed remaining references to bootstrap from frontend w/ burnettk
* updated usage of hidden to use the class instead of the bootstrap attribute w/ burnettk
* print out docker version for debugging
* docker pull with docker instead of compose
* added comment for docker pull in check docker start script
---------
Co-authored-by: jasquat <jasquat@users.noreply.github.com>
* This alters how the send_event endpoint responds - it originally responded with a process instance, it now responds with the next task, in keeping with how other task completion endpoints behave.
* I was forced to upgrade some of the bpmn-js libraries which fixes some of the linting errors on the front end.
* The "Return to home" button isn't always displayed. It will not display when it is redirecting, or when the current task is running.
.
Show the "next" task if no task is provided on the task_show api endpoint
Adding interstitial endpoint
Rename run to run_and_save
Remove repeated code from execution strategy
Adding interstital frontend page
* 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.
The same issue was happening on the ProcessInstanceListTable, and there it was being managed by a "SafelySetErrorMessage" function in one case,
but would not be addressed in all possible cases.
Reworked error handling into a context provider (APIErrorProvider) and hook (UseApiError) and removed the "(useContext as any)(ErrorContext)[1];" that felt a little off but that never was an actual problem.
1. It's not just processes, it contains the list of all DMN Decisions as well.
2. It is closely linked to the SpecReference object that can be generated by looking through all the Spec files to find the processes and decisions they contain.
3. It is a cache of information, the file system is the source of truth. Seems likely we will cache more things in the future -- so setting things up this way made sense.
burnettk
Kevin Burnett
jasquat
Dan Funk
jbirddog
jasquat
Madhurya Liyanage