0.12.0

The designer has allowed only the validation of the steps so far. The root of the definition could be edited by the global editor, but the validation was not possible. This version adds a new type of the validator: the root validator. The new validator affects on the result of the definition validation (designer.isValid()).

Breaking Changes

• The validator property in the steps group of the configuration is deleted. Use the step property in the validator group instead.
• The step validator has a new parameter: definition.
• Added the root validator.

const configuration = {
  steps: {
    validator: /* DEPRECIATED */,
  },
  validator: {
    step: (step, parentSequence, definition) => { /* ... */ },
    root: (definition) => { /* ... */ }
  },
  // ...
};

0.11.0

Breaking Changes

• This version introduces a few changes in the customActionHandler handler:
  • the first parameter is an object now, previously it was a string. To read action type you need to read the type property from the object,
  • the step parameter is nullable now,
  • we added a context parameter that allows to notify about changes in the definition.
• Added new classes for label components: sqd-label-primary and sqd-label-secondary.

0.10.2

• Fixed the bug with moving the viewport by the scroll wheel button.
• Added a simple animation to placeholders during dragging.

0.10.1

• Fixed the bug with the auto-hide feature in the smart editor.
• Fixed the bug with rendering wide components in the sequence component.
• Fixed the bug with dragging when the designer is attached to a scrolled page.

0.10.0

Refactored the step component interface. Extracted the logic of the step validation to a separated layer called badges. This allowed to create a new type of badge: counter. The counter badge is available in the pro version.

Additionally, now it's possible manually refreshing the validation from outside of the designer. The validation is a special case of a badge. To refresh the validation you need to call the updateBadges method.

designer.updateBadges(); 

0.9.2

The sequential-workflow-designer-angular package supports Angular 12 - 15 now.

0.9.1

Fixed the bug with displaying nested placeholders in folders.

0.9.0

Breaking Changes

This version changes the main configuration. The "isHidden" properties are prohibited. To hide the control bar or other UI component you need to set false in the corresponding configuration property.

const configuration = {
  toolbox: false,
  editors: false,
  controlBar: false,
  // ...
};

To display components you need to set a proper value.

const configuration = {
  toolbox: {
    groups: [ /* ... */ ]
  },
  editors: {
    globalEditorProvider: () => { /* ... */ },
    stepEditorProvider: () => { /* ... */ },
  },
  controlBar: true,
  // ...
};

0.8.1

Changed format of bundles:

• sequential-workflow-designer to UMD, ESM and CommonJS,
• sequential-workflow-designer-react to ESM and CommonJS.

0.8.0

• This release introduces a better support for TypeScript.
• The model of the workflow definition is moved from the sequential-workflow-designer package to the sequential-workflow-model package. By this it's possible to create a common package with your workflow model and use it for the front-end and back-end applications at the same time. The sequential-workflow-designer package exports definition types as before, but these types come from the sequential-workflow-model package. You don't have to include the sequential-workflow-model package to your project if you don't need it. You can read more about this approach here.

Breaking Changes

TaskStep, SwitchStep, ContainerStep interfaces are depreciated now. Those types will be removed in the future.

🤩 We launched a new project: Sequential Workflow Machine. It's a JavaScript workflow engine for the frontend and the backend. The engine uses exactly the same data model as the Sequential Workflow Designer. It means you can use the same workflow definition for the designer and the engine. The new package is powered by the xstate library.