Fsm Workflow Versions Save

FSM workflow (for Node.js)

v2.2.1

5 years ago

See changelog and completed issues

API changes

https://github.com/OpusCapita/fsm-workflow/commit/de432f12da3573e5d10a17476f91f0a4c14cadce

fsm-workflow-editor: added new prop

schemaConfig = {
    state: {
      availableNames: [
        'inspectionRequired',
        'approvalRequired',
        'approved'
      ]
    }
}

If availableNames are defined, Add state button in editor lets you choose a state from this predefined list via select box. Already added states cannot be added twice.

If availableNames are not defined, editor shows a text input where you can type in any state name.

v2.2.0

5 years ago

See changelog and completed issues

API changes

https://github.com/OpusCapita/fsm-workflow/commit/8328c318d63abcd5d8197275aba26dac8b18f8c8

Added new function MachineDefinition.inspectTransitions

API remains the same as before, but internals work differently: MachineDefinition.inspectTransitions produces a verbose output that can be then filtered in many ways. MachineDefinition.findAvailableTransitions calls it and filters its output.

MachineDefinition.inspectTransitions is a low-level API and can be used for debugging purposes. Shape of output:

[
  {
    transition: <transition as it is defined in schema>,
    result: {
      guards: [
        {
          condition: <guard as defined in schema>,
          result: <evaluation result, boolean>
        },
        ...
      ],
      automatic: <boolean if defined as boolean> OR [
        {
          condition: <automatic as defined in schema>,
          result: <evaluation result, boolean>
        },
        ...
      ],
    }
  }
]

So, from this point you can find out why certain transition is not available, etc.

v2.1.2

6 years ago

v2.1.1

6 years ago

v2.0.5

6 years ago

v2.0.4

6 years ago

v2.0.3

6 years ago

v2.0.2

6 years ago

v2.0.1

6 years ago

v2.0.0

6 years ago