WorkflowEngine/CHANGELOG and WorkflowEngine Releases

All Versions

Latest Version

5.2.2

Avg Release Cycle

Latest Release

Changelog History

Page 2

v3.5 Changes
- 🚚 Moving the canvas (in the Move mode) with arrows was added to the designer.
- Explicit passing of CultureInfo was added to methods GetInitialCommands, GetInitialState, GetCurrentState and GetAvailableCommands of the WorkflowRuntime class
- 🌐 Full samples (Vacation request approval) for all supported databases for ASP.NET Core and ASP.NET MVC. Full samples for MSSQL, Postgres and Oracle database for Web Forms.
v3.4 Changes
- ➕ Added automatic size increase for background in designer.
- ➕ Added designer localization files for German, French, Spanish, Italian, Portuguese, Turkish, and Russian languages.
- 📦 .NET Core NuGet packages come with .NET Standard 1.6 and .NET Standard 2.0 libraries. This allows you to use these packages with any .NET Core version, including 2.1.
- 0️⃣ The OptimaJet.Workflow.Core.Logging.ILogger interface was added; it can be initializes with your own logger in the WorkflowRuntime object. It is used to integrate with the Workflow Server logging system, but you can use it to integrate with your own system. Bear in mind that the logger in the WorkflowRuntime object is not initialized by anything by default.
v3.3 Changes
- MongoDB provider for Workflow Engine .NET Core was added.
- ⚡️ MongoDB driver was updated to version 2.7. You can now connect to CosmosDB through a MongoDB connection.
- The following hotkeys were added to the Workflow Designer:
  - Ctrl + A - Select all
  - Ctrl + C - Copy selected items
  - Ctrl + E - New Activity
  - Ctrl + I - Extended info
  - Ctrl + Y - Redo
  - Ctrl + Z - Undo
  - Arrows - Move selected items
  - Delete - Delete
  - Alt + Enter - Full-screen mode
  - Ctrl + M - Move mode
⬆️ The following additional actions must be taken to upgrade to Workflow Engine 3.3 if you are using MongoDB:
- ⚡️ Only for MongoDB users: it is necessary to apply the update_3_2_to_3_3.js script to your database.
v3.2 Changes
- ➕ Added providers for MySQL and Oracle, running under .NET Core
- ➕ Added class AggregatingRuleProvider, designed to combine several IWorkflowRuleProvider into one IWorkflowRuleProvider.
- ➕ Added class AggregatingActionProvider, designed to combine several IWorkflowActionProvider into one IWorkflowActionProvider.
v3.1 Changes
- ⚡️ Workflow Engine's relational database storage system has been optimized. Additional indices have been built; obsolete indices have been removed; the size of some columns has been changed. Generally, these changes should result in the improvement of Workflow Engine's performance, especially for Microsoft SQL Server. All these changes have already been included into installation scripts; use the update_3_1.sql script to update the existing databases.
- BulkCreateInstance now works for Microsoft SQL Server and .NET Core (version >= 2).
⚠ Warning

⚡️ The update_3_1.sql script contains a change of index and size of certain columns. Be particularly careful when applying it to the production database.
v3.0 Changes
- The interface of Workflow Designer has been revamped to improve usability
  - The look and feel of the scheme has been changed
  - The library that renders popup windows and controls has been changed from jQuery UI to Semantic-UI. jQuery UI has been removed from the project completely. Autocomplete for lists has been implemented with jQuery-autoComplete
  - The Konva.js version has been updated to 2.0.2
  - The 'Extended Info' mode has been added to provide additional information needed when creating a workflow scheme
  - Undo and redo have been added
  - Current activity of subprocesses is now highlighted
  - Global CodeActions have been simplified
  - Scheme legend has been added
- 🏗 Builds for .NET Core 2.0 and .NET Standard 2.0 have been included to .NET Core packages
- 0️⃣ The order of search for Action, Condition and Rule in Code Actions and IWorkflowActionProvider(IWorkflowRuleProvider) has been changed. Earlier on, the order was as follows (highest to lowest priority): Global CodeAction, CodeAction in the scheme, IWorkflowActionProvider(IWorkflowRuleProvider). Now this order is the following by default: CodeAction in the scheme, Global CodeAction, IWorkflowActionProvider(IWorkflowRuleProvider). Thus, CodeAction in the scheme has the highest priority. Search priority can be set with the runtime.SetExecutionSearchOrder(ExecutionSearchOrder order) setting.
- 🏗 Parameter type names used to be stored as an assembly qualified name (by specifying the version of the build and the public key token), which resulted in troubles when migrating schemes from the .NET Framework environment to the .NET Core environment. Now a simplified type name - the one that is displayed in Designer - is stored in the scheme. Old schemes are loaded without changes; type names will be replaced after the first save of the scheme in the Designer.
- 🛠 Errors that occur when there's a '-' in CodeAction names have been fixed.
The following additional actions must be taken to uprgade to Workflow Engine 3.0:
- ⚡️ It is not necessary to update to the new version of the Designer; however, we strongly advise it. The old version of the Designer shall work with the new versions of the Workflow Engine at least within the next half a year. If you are updating to the new version of the Designer, introduce the following changes to the pages where Designer is displayed.
  - Delete links to jquery-ui.min.css and jquery-ui.js html <link href="/Content/themes/base/jquery-ui.min.css" rel="stylesheet" type="text/css"/> <script src="/Scripts/jquery-ui.js" type="text/javascript"/> ``` - Add links to **semantic.min.css**, **semantic.min.js**, **jquery.auto-complete.min.js** ```html <link href="/Content/semantic.min.css" rel="stylesheet" type="text/css"/> <script src="/Scripts/semantic.min.js" type="text/javascript"/> <script src="/Scripts/jquery.auto-complete.min.js" type="text/javascript"/>
- If the new order of search for Action, Condition and Rule does not suit you, change it with the following setting:
```
runtime = runtime.SetExecutionSearchOrder(ExecutionSearchOrder.GlobalLocalProvider);
```
Then, everything shall work the same way it did in the previous versions.
- 👻 Workflow Engine's reaction to the scenario where it could not find an Action, Condition or Rule in CodeActions or IWorkflowActionProvider(IWorkflowRuleProvider) has been changed. Earlier on, Workflow Engine ignored this scenario which made it difficult to debug schemes. Now, the NotImplementedException exception is thrown, specifying the name of the object which was not found. If this behavior does not suit you, use the following setting:
```
runtime = runtime.SetIgnoreMissingExecutionItems(true);
```
v2.3 Changes
- A 'Refresh' button and its functionality have been added to Designer
- A 'Full Screen' button and its functionality have been added to Designer
- 🐎 BulkCreateInstance and TimerManager performance has been enhanced
- Scroll-based scaling has been added to Designer
v2.2 Changes
- Now it is possible to create asynchronous Actions and Conditions. You can call asynchronous methods from Actions and Conditions using the await keyword. Such methods will be the most effective if you use asynchronous methods of the WorkflowRuntime object, for example, ExecuteCommandAsync instead of ExecuteCommand, or SetStateAsync instead of SetState, etc. You can create asynchronous Actions in Designer. To do that you simply need to check the Async checkbox in the Action or Condition where you're going to call asynchronous methods from. If you use IWorkflowActionProvider, then you will need to implement 4 additional methods. bool IsActionAsync(string name) and bool IsConditionAsync(string name) should return true so that the Action or Condition are called asynchronously. The execution of an asynchronous Action or Condition is done in the Task ExecuteActionAsync(string name, ProcessInstance processInstance, WorkflowRuntime runtime, string actionParameter, CancellationToken token) and Task<bool> ExecuteConditionAsync(string name, ProcessInstance processInstance, WorkflowRuntime runtime, string actionParameter, CancellationToken token) methods.
- Parameters conveyed to the process with the command no longer need to be described as command parameters. Iа such a parameter is described in the scheme, it will be a Temporary or a Persistence one, depending on which Purpose is specified in the scheme. If the parameter is not described in the scheme, it will be a Temporary one.
- The ExecuteCommand and ExecuteCommandAsync methods return information on whether the command has been executed (it may not be executed under certain conditions) and the ProcessInstance state after the execution of a command.
The following additional actions must be taken to uprgade to Workflow Engine 2.2:
- If you use IWorkflowActionProvider, you will need to add 4 new methods to it: IsActionAsync, IsConditionAsync, ExecuteActionAsync, ExecuteConditionAsync. If you do not yet intend to use asynchronous Actions, then the IsActionAsync and IsConditionAsync methods should always return false, whereas ExecuteActionAsync and ExecuteConditionAsync can throw a NotImplementedException.
```
public bool IsActionAsync(string name)
{
    return false;
}

public bool IsConditionAsync(string name)
{
    return false;
}

public async Task ExecuteActionAsync(string name, ProcessInstance processInstance, WorkflowRuntime runtime, string actionParameter, CancellationToken token)
{
    throw new NotImplementedException();
}

 public async Task<bool> ExecuteConditionAsync(string name, ProcessInstance processInstance, WorkflowRuntime runtime, string actionParameter, CancellationToken token)
{
    throw new NotImplementedException();
}
```
v2.1 Changes
- 🚀 Workflow Engine for .NET Core App 1.1 is released. All Workflow Engine functions are supported. This version will be updated simultaneously along the .NET Framework version. 2 persistence providers are currently supported: MS SQL Server and PostgreSQL. Links to NuGet packages and samples can be found here.
- Workflow Engine scheme import/export to/from BPMN2 has been added.
- 👍 Bulk process creation has been added. Now you can create a large amount of processes (100 - 100,000) in significantly less time than when using the CreateInstance method. Use the _runtime.BulkCreateInstance(..) method to do that. Currently, the feature is available in the .NET Framework version of Workflow Engine and supports only MS SQL Server. The list of supported databases will be expanded.
v2.0 Changes
- 💻 Designer UI has been improved, transitions are now linear for better usability
- Scheme rendering library KineticJS has been replaced with Konva.js
- 🚚 WorkflowDesigner.readonlymode(), WorkflowDesigner.printablemode() and WorkflowDesigner.ediatblemode() methods have been added to WorkflowDesigner object in the client. readonlymode makes Designer uneditable. printablemode removes the toolbar, the grid and all controls, zooming designer so that the scheme occupies the entire canvas. This mode can be used to print Designer's viewport to a PDF within a browser. editablemode makes Designer editable.
- Designer now allows users to make an autocomplete list for the following fields: Actor.Value, Activity.Implementation.Action parameter, Transition.Condition.ActionParameter. The autocomplete list is being populated server-side via the IDesignerAutocompleteProvider interface and by transferring implementation to the WorkflowRuntime object via _runtime.WithDesignerAutocompleteProvider(provider).
- The GetConditions method has been added to the IWorkflowActionProvider interface. Now, the choice of conditions and actions in Designer can be split.
- 🖨 Parameters of any type not mentioned in the scheme can now be used in Actions' code. The type should be serialized in JSON. Three methods are available: _processInstance.SetParameter("parameterName",parameterValue,ParameterPurpose.Persistence), _processInstance.GetParameter<ParameterType>("parameterName") and _processInstance.RemoveParameter("parameterName").
- Ability to create Timers with a value which is undefined at the time of creation of a process has been added. Timer.Value == -1 means that the current transition will not be executed until the respective timer has a defined value. Timer.Value == 0 means that in case the timer connected to a transition does not have a value, this transition shall be processed automatically. Initial value of a timer can be set with the _runtime.NeedTimerValue event.
- ⚙ Ability to modify execution time for timers in running processes has been added. Use methods _runtime.SetTimerValue(processId,timerName,newValue) and _runtime.ResetTimerValue(processId, timerName) to change and reset timer values outside the process. Use methods _runtime.SetTimerValue(processInstance,timerName,newValue) and _runtime.ResetTimerValue(processInstance, timerName) to change and reset timer values from within your Actions.
- 🆕 Newtonsoft.Json version has been changed from 7.0.1 to 9.0.0.
The following additional actions must be taken to uprgade to Workflow Engine 2.0:
- 📦 Replace the link to KineticJS with the link to konva.min.js. Konva.js library is included in the ZIP archive and in nuget package WorkflowEngine.NET-Designer.
- ⚡️ Update Newtonsoft.Json.dll to 9.0.0. The library is included in the ZIP archive and in nuget package WorkflowEngine.NET-Core.
- If you use implementation of IWorkflowActionProvider you should add a public List<string> GetConditions() method to it. It is advisable that the GetActions returns only the list of available Actions, whereas the GetConditions method should return the list of available Conditions. In this case they should be filtered properly in the Designer. However, if you do not want to modify your code, make sure that the GetConditions method throws a NotImplementedException. In this case, everything should work as it used to.
- IF you use Oracle, you should run an update_1_5_to_2_0.sql script from the Oracle provider ZIP archive or a NuGet package.

WorkflowEngine changelog

WorkflowEngine.NET - component that adds workflow in your application. It can be fully integrated into your application, or be in the form of a specific service (such as a web service).

Changelog History

Page 2

v3.5 Changes

v3.4 Changes

v3.3 Changes

v3.2 Changes

v3.1 Changes

v3.0 Changes

v2.3 Changes

v2.2 Changes

v2.1 Changes

v2.0 Changes

WorkflowEngine changelog

WorkflowEngine.NET - component that adds workflow in your application. It can be fully integrated into your application, or be in the form of a specific service (such as a web service).

Changelog History Page 2

Changelog History

Page 2