0.33.1

This version fixes a bug with the rendering of the drop-shadow filter in some browsers.

0.33.0

This version introduces a new restriction callback: canUnselectStep. You can now prevent a step from being unselected based on your custom logic. When an unselection is blocked, the onStepUnselectionBlocked event is triggered.

const configuration = {
  steps: {
    canUnselectStep: (step, parentSequence) => {
      return areChangesSaved() === true;
    },
  },
  // ...
};

designer.onStepUnselectionBlocked((targetStepId) => { /* ... */ });

Please note that you should NOT use window.confirm() or other blocking functions inside the canUnselectStep callback, as this callback may be invoked multiple times during drag operations. To handle this correctly, implement your own UI logic to notify the user about any required actions before unselection can proceed. Please check this example.

0.32.0

This introduces internal changes related to the dragged component.

0.31.0

This version introduces a new feature: you can now add a custom icon to placeholders that appear while dragging a step.

0.30.5

This version fixes the configuration usage in the RectPlaceholderDesignerExtension class.

0.30.4

This version exposes the RectPlaceholderDesignerExtension class.

0.30.3

This version adds a new argument to the canCreate and canShow callbacks in the placeholder configuration, providing access to the current definition.

0.30.2

This version fixes a bug related to identifying the touched element #195.

0.30.1

Added a configurable branch name resolver for the switch step component, allowing you to define custom logic for resolving branch names #193.

import { StepsDesignerExtension } from 'sequential-workflow-designer';

const extensions = [
  StepsDesignerExtension.create({
    switch: {
      branchNamesResolver: (step) => Object.keys(step.branches)
    }
  })
];

0.30.0

This version introduces a new step component: launchPad.

The launchPad step component allows you to place multiple steps along a horizontal axis. Its design suggests that any of the contained steps can be executed independently or simultaneously. You can use it as a container for parallel execution or as a trigger hub-waiting for one or more embedded trigger steps to activate the workflow.

The main goal of this addition is to enable the creation of workflows with multiple triggers in the standard version of the designer.

To see how it looks, please check out this example.