All Versions
Latest Version
Avg Release Cycle
Latest Release

Changelog History

  • v2.6 Changes

    • πŸ“š Updated to Workflow Engine .NET 4.2
    • Support of the multi-server mode has been added. If you need to run the Workflow Server instance in multi-server mode, add the following setting to the config.json file.
        "IsMultiServer": true
    • βž• Added database logs with records search possibility.
    • Added new Workflow API methods for managing a Workflow Server instance. Start, Stop and IsActive.
    • βž• Added ability to develop the end-user forms (frontend interface) based on Vue.js. It is the beta version. Access control for these forms will be added in the next version. It is also possible in the next version the base library of controls will be changed.

    πŸš€ If you use global Code Actions and you have several servers deployed, then to apply the changes you need to restart each of them. To do this, you can use the Start method from the Workflow API.

    ⬆️ The following additional actions must be taken to upgrade to Workflow Server 2.6:

  • v2.5 Changes

    • πŸ“š Updated to Workflow Engine .NET 4.1
    • πŸ‘Œ Support for multi-tenant applications.
      • TenantId has been added to processes. When creating a process using the createinstance WorkflowAPI method, one can specify TenantId and use its value to work with the process. Also, when manipulating a process using WorkflowAPI methods, one can optionally assign TenantId; once TenantId is specified, its compliance with the initial TenantId value set at the process creation is automatically checked.
      • For schemes one can specify tags, and then, search for schemes where these tags are indicated. Tags can be set on the Workflow/Manage Schemes admin page. In the getschemelist WorkflowAPI method, one can specify a list of tags to search for schemes. The search is performed using an OR expression.
    • The possibility to set a login and a password to access the WorkflowServer admin panel has been provided. This setting is available on the Dashboard page in the Security tab.
    • The possibility to set an access token to access the WorkflowAPI methods has been provided. This setting is available on the Dashboard page in the Security tab.
    • The Basic Plugin has been connected to the WorkflowServer, it can be enabled on the Dashboard page in the Plugins tab. For a full list of methods, please, see here.
    • Using the createinstance, executecommand and get state of WorkflowAPI methods, one can pass implicit (that is, not explicitly described in the process scheme) persistent parameters. A parameter can also be a valid JSON object of any complexity. In this case, the type DynamicParameter should be applied to control such a parameter in the code.
    • The getparameter and setparameter methods to read and modify process parameters have been added to WorkflowAPI.
    • Intellisense has been added to the Code Actions editor, in schemes and in the Workflow / Global Code Actions section of the admin panel.
    • In the API / Workflow API section, forms to execute WorkflowAPI methods have been added; an example request is also generated there.

    ⬆️ The following additional actions must be taken to upgrade to Workflow Server 2.5:

    • Run the SQL script update_2_7_to_2_8.sql for all relative databases.
    • πŸ”€ IMPORTANT! Incorrect behavior was fixed when the subprocess was merged in the parent process via the set state of the parent process mechanism. Previously, the parent process parameters were OVERWRITTEN. Now, the parent process parameters won't be changed. Only new parameters from the subprocess will be written to the parent process automatically. The same way the merge via calculating conditions always works. If you consciously exploited this behavior, then the best way to get parameters from the subprocess is to use a property processInstance.MergedSubprocessParameters when merge occurs.
    • In the previous versions, implicit parameters passed by the WorkflowAPI methods were always interpreted as strings. Starting from version 2.5, the WorkflowServer converts these parameters to types (int, bool, double, DynamicParameter etc). If it’s important for you to keep the old behavior, add the following setting to the config.json file.
        "ImplicitParametersParsingType": "Legacy"
    • In the previous versions, process parameters were transferred to Callback server in the camel case. That is, the first letter of the parameter name (for example, 'Parameter1') became small ('parameter1'). Now, the parameter name will not change. If it’s important for you to keep the old behavior, add the following setting to the config.json file.
        "CallbackServerJsonSerialization": "CamelCase"
  • v2.4 Changes

    • ⚑️ Updated to Workflow Engine .NET 4.0

    ⬆️ The following additional actions must be taken to upgrade to Workflow Server 2.4:

    • Run the SQL script update_WFE_4_0.sql for all relative databases.
  • v2.3 Changes

    • βž• Added localization for German, French, Spanish, Italian, Portuguese, Turkish, and Russian languages.
    • SchemaName setting has been added to specify the database schema to which the server is connected.
    • The GetSchemeList method has been added to the server API, this method returns a list of schemes that exist on the server.
    • 🏁 The logging system has been added. Errors, debug information and informational messages are logged. Logging targets can be console, debug output or files. For windows service, logging can also be done in the Windows Event Log.
    • 🌲 The LogInfo,LogError, LogMessage methods have been added to the server API - methods for writing to the log from outside the server.
    • 🌲 The following new features are available in the WorkflowRuntime object, which is always available in standard WFE actions. runtime.Logger - returns logger, for recording messages to the log. runtime.LogError (), runtime.LogDebug (), runtime.LogInfo () are methods for writing messages to the log.
    • 🐳 The docker container was published , containing the Workflow Server with the ability to transfer all the configuration settings to it.
  • v2.2 Changes

    • πŸ‘ The MongoDB support has been added, this type of connection also works with the Cosmos DB.

  • v2.1 Changes

    • βž• Added Oracle and MySQL support
    • The ExecuteCommand method from WorkflowAPI returns information on whether the command was executed and process state after execution (including all process parameters)
    • The source code of a console application which you can connect your IWorkflowActionProvider and IWorkflowRuleProvider to and perform fine-tuning of Workflow Engine was uploaded to (GitHub)[]

  • v2.0 Changes

    • πŸš€ First release of Workflow Server 2.0