Skip to content

Releases: optimajet/WorkflowEngine.NET

Workflow Engine 15.0.0

25 Sep 17:39
Compare
Choose a tag to compare

Please use version 15.0.1 instead of version 15.0.0.

Breaking changes

  • Added ESM support to the Workflow Designer. The entry point for CommonJS remains unchanged.
  • Node has been updated to version 20.17.0.
  • The Angular designer package and sample have been updated to Angular 18.

Core

  • Multiple issues related to the functionality of Custom Activities have been fixed, and optimizations have been made.
  • New settings for Custom Activities have been added. You can read more about them in this article.

Designer

  • Fixed an issue in the decision table where the transition did not set the classifier when creating an activity.

Workflow Engine 14.1.0

20 Sep 14:27
Compare
Choose a tag to compare

Core

  • Fixed an issue where subprocess parameter values were being overwritten by default values of parameters defined in the schema. Now, parameters are no longer initialized with default values when creating a subprocess. If you previously relied on this behavior, you will need to update your existing schemas or set the WorkflowRuntimeSettings.ObsoleteSubprocessParametersInitializationBehavior option totrue. This setting will only affect parameters that are not copied when using the CopySpecified, IgnoreSpecified ot IgnoreAllpolicy. When using the CopyAll policy, parameters will be copied from the parent process, making initialization unnecessary. Overwriting these parameters was a bug and not considered as breaking changes.
  • The GetProcessInstancesAsync method for the MongoDB provider has been fixed. Sorting and paging now work correctly.
  • The GetSchemesAsync method has been corrected, and tag lists are now generated properly. Sorting and paging for the MongoDB provider have also been fixed.
  • The GetTopTimersToExecuteAsync method now throws an exception when the top argument is less than 0. The handling of this argument for the MongoDB provider has also been fixed.

Designer

  • webpack has been updated to version 5.94.0.
  • axios has been updated to version 1.7.4.

Workflow Engine 14.0.0

29 Aug 15:41
Compare
Choose a tag to compare

Workflow Engine Web API

Introducing a new product in the Workflow Engine ecosystem: the Workflow Engine Web API. This is a library for the ASP.NET framework that allows you to integrate a pre-built Web API into your application for managing data and processes within Workflow Engine instances. This module is easy to integrate and highly customizable, eliminating the need for routine development work to integrate Workflow Engine into your web ecosystem.

Key features:

  1. RESTful Data API: Safely interact with the Workflow Engine database without the risk of internal process disruptions.
  2. RPC API (Coming soon…): Remotely manage the Workflow Engine Runtime instance.
  3. Permission-based Security: Fine-tune access to each API endpoint and generate claims for your users.

For more information, refer to the documentation.

Unique Indexes

  • Unique indexes have been added to all database providers:
    • WorkflowGlobalParameter: Type, Name;
    • WorkflowInbox: ProcessId, IdentityId;
    • WorkflowProcessInstancePersistence: ProcessId, ParameterName;
    • WorkflowProcessTimer: ProcessId, Name.
  • In MongoDB, the index for the WorkflowScheme collection (Code) is now unique.

You can update the data schema using the built-in migration mechanism for SQL databases, or manually run the update_14.0.0.js script for MongoDB. You may also choose not to use these indexes or selectively apply some of them as needed.

Potential Breaking Changes

  • For MS SQL Server only: To add indexes, the field lengths for WorkflowProcessInstancePersistence.ParameterName and WorkflowProcessTimer.Name have been changed from NVARCHAR(max) to NVARCHAR(900). The migration script will automatically check if these fields contain data longer than 900 characters. If such data is found, the script will terminate with an error. In this case, you will need to manually shorten the data in these fields and rerun the migration. If you encounter difficulties during the upgrade process, please contact our support team.

Bug Fixes

  • Fixed an issue where calling GetInstancedStatus on MongoDB would result in an exception.

Workflow Engine 13.3.1

12 Aug 17:25
Compare
Choose a tag to compare

Designer

Workflow Engine 13.3.0

07 Aug 18:31
Compare
Choose a tag to compare

Core

  • Introduced centralized management for packages and their dependencies using Directory.Build.props and Directory.Packages.props.
  • Added a new ProcessDefinitionBuilder. For more details, refer to the documentation.
  • Upgraded Newtonsoft.Json package from version 13.0.1 to 13.0.3.
  • Added the capability to extend the Designer API.

Designer

  • Corrected a typo in the Transition Edit Form.

Plugins

  • Resolved an exception issue occurring in the RealTimeTrackingPlugin.
  • Fixed an issue with an incorrect type in HttpRequestActivity within the BasicPlugin.

Workflow Engine 13.2.2

19 Jul 16:08
Compare
Choose a tag to compare

Bug Fixes

  • Fixed an issue where adding a BuildStep with a specific ordinal number would cause an exception during the creation of the Workflow Runtime.
  • Fixed an issue where invoking Shutdown multiple times in the Real-Time Tracking Plugin caused errors.

Workflow Engine 13.2.1

25 Jun 13:23
Compare
Choose a tag to compare

Designer

  • Fixed several issues with the behavior of the CreateProcess activity.
  • Fixed a bug with SignalR connection.
  • Fixed a bug with plugin list.
  • The braces dependency has been updated from version 3.0.2 to 3.0.3.
  • Updated engine.io from version 6.5.4 to 6.5.5 in Workflow-designer-angular.
  • Updated socket.io-adapter from version 2.5.4 to 2.5.5 in Workflow-designer-angular.
  • Updated ws from version 8.16.0 to 8.17.1 in Workflow-designer-angular.

Core

  • Fixed a bug in subprocesses execution.
  • Updated Npgsql package in OptimaJet.Workflow.PostgreSQL to version 8.0.2.

Providers

  • Corrected the GetProcessHistoryCount method in the MongoDB provider.

Samples

  • Updated Microsoft.Identity.Client from version 4.60.3 to 4.61.3 in Microsoft SQL WebForm sample.
  • Updated Azure.Identity from version 1.11.3 to 1.11.4 in Microsoft SQL Sample.

Workflow Engine 13.2.0

27 May 16:44
Compare
Choose a tag to compare

Designer

  • Fixed an issue with saving custom activity.
  • Added the ability to set the schema name in the designer.

Core

  • Added functionality to retrieve a list of all migrations and a list of unapplied migrations.

Documentation

  • Updated the "Testing workflow schemes" article with corrections related to migrations.

Workflow Engine 13.1.0

13 May 20:14
Compare
Choose a tag to compare

Samples

  • Removed all .NET Framework 4.8 Samples except for the Microsoft SQL Server Sample.
  • Updated .NET Framework 4.8 Samples to WorkflowEngine 13.0.0.
  • Added Blazor integration Sample.

Providers

  • Updated Npgsql driver from version 8.0.2 to 8.0.3.

Workflow Engine 13.0.0

06 May 20:15
Compare
Choose a tag to compare

Real-Time Tracking Plugin

  • Implemented a Real-Time Tracking plugin that extends the Workflow Designer with real-time functionality, allowing live updates of process states via SignalR. For more details, refer to the documentation.

Core

  • Introduced the optional capability for automatic migration, allowing the creation and updating of the database schema without manually running scripts. This feature ensures that the Workflow Engine maintains a list of executed scripts accessible within the database.

Designer

  • The Workflow Designer can now be initiated directly from the command line using the npx @optimajet/workflow-designer $BackendUrl $SchemeCode command, which automates the fetching and execution of packages from the npm repository. For more details, refer to the documentation.
  • Added an 'About' button to the designer’s menu, displaying both the backend and designer version information to users.

Bug Fixes

  • Corrected an error related to clipboard access in the 'Instance Info' section.
  • The backend now filters events to ensure that Workflow Designer receive only pertinent data. Unknown events are currently ignored.