Skip to content

v2.0.0
Compare
Choose a tag to compare
@danfunk danfunk released this 16 Jun 19:23
· 228 commits to main since this release
v2.0.0
fbc4a42

What's Changed

We've done a lot of work over the last 8 months to the SpiffWorkflow library as we've developed SpiffArena, a general purpose workflow management system built on top of this library.
This has resulted in a handful of new features.
Our main focus was on making SpiffWorkflow more predictable, easier to use, and internally consistent.

Breaking Changes from 1.x:

  • We heavily refactored the way we handle multi-instance tasks internally. This will break any serialized workflows that contain multi-instance tasks.
  • Internal structure of our code, the names of some classes, and common methods have changed. Please see our [ReadTheDocs] (https://readthedocs.org/projects/spiffworkflow/) documenation for version 2.0.0.

Features and Improvements

Task States, Transitions, Hooks, and Execution

Previous to 2.0, SpiffWorklow was a little weird about its states, performing the actual execution in the on_complete() hook.
This was VERY confusing.
Tasks now have a _run() command separate from state change hooks.
The return value of the _run() command can be true (worked), false (failure), or None (not yet done).
This opens the door for better overall state management at the moment it is most critical (when the task is actually executing).
We also added new task state called "STARTED" that describes when a task was started, but hasn't finished yet, an oddly missing state in previous versions.

Improved Events

We refactored the way we handle events, making them more powerful and adaptable.
Timer events are now parsed according to the ISO 8601 standard.

Improved Multi-Instance Tasks

We refactored how Multi-instance tasks are handled internally, vastly simplifying their representation during execution and serialization.
No more 'phantom gateways.'

Improved SubProcesses

SpiffWorkflow did not previously distinguish between a Call Activity and a SubProcess, but they handle Data Objects very differently.
A SubProcess is now able to access its parent data objects, a Call Activity can not.
We also wanted the ability to execute Call Activities independently of the parent process.

  • Bugfix/subprocess access to data objects by @essweine in #296
  • start workflow while subprocess is waiting by @essweine in #302
  • use same data objects & references in subprocesses after deserialization by @essweine in #314

Improved Data Objects / Data Stores

This work will continue in subsequent releases, but we have added support for Data Stores, and it is possible to provide your own implementations.

Improved Inclusive Gateways

We added support for Inclusive Gateways.

Pre and Post Script Fixes

We previously supported adding a pre-script or post-script to any task but there were a few lingering bugs that needed fixing.

DMN Improvements

We now support a new hit policy of "COLLECT" which allows you to match on an array of items. DMN support is still limited, but
we are making headway. We would love to know if people are using these features.

BPMN Validation

We improved validation of BPMN and DMN Files to catch errors earlier.

New Serializer

There are some breaking changes in the new serializer, but it is much faster and more stable. We do attempt to upgrade
your serialized workflows to the new format, but you will definitely encounter issues if you were using multi-instance tasks.

Lightning Fast, Stable Tests

Better Errors

  • Feature/better errors by @danfunk in #283
  • Workflow Data Exceptions were broken in the previous error refactor. … by @danfunk in #287
  • added an exception for task not found w/ @burnettk by @jasquat in #310
  • give us a better error if for some reason a task does not exist by @burnettk in #311

Flexible Data Management

  • Allow for other PythonScriptEngine environments besides task data by @jbirddog in #288

Various Enhancements

Make it easier to reference SpiffWorkflow library classes from your own code.

Better Introspection

Added the ability to ask SpiffWorkflow some useful questions about a specification such as, "What call activities does this depend on?",
"What messages does this process send and receive", and "What lanes exist on this workflow specification?"

  • Parser Information about messages, correlation keys, and the presence of lanes by @danfunk in #262
  • Called elements by @jbirddog in #316

Code Cleanup

Improved Documentation

Bug Fixes

  • correct xpath for extensions by @essweine in #265
  • prevent output associations from being removed twice by @essweine in #275
  • fix for workflowspec dump by @subhakarks in #282
  • add checks for len == 0 when copying based on io spec by @essweine in #297
  • Improvement/allow duplicate subprocess names by @essweine in #321
  • Resets to tasks with Boundary Events by @danfunk in #326
  • Sub-workflow tasks should be marked as "Future" when resetting to a task before the sub-process. by @danfunk in #327

New Contributors

Full Changelog: v1.2.1...v2.0.0

Contributors

burnettk, danfunk, and 5 other contributors
Assets 2
Loading