WorkflowGen 7.22.0

Announcements Release Notes & Downloads
1

Important known issue

  • ASP.NET webforms in AJAX mode: There is a regression behavior since 7.22.0 where the eWorld calendar picker and WorkflowFileUpload would behave unexpectedly (JavaScript error in client-side browser) after they were made visible from hidden using the field behavior hidden condition. This issue might affect other web controls in AJAX mode.

    Note: If you currently use ASP.NET webforms in AJAX mode (Form Designer with AJAX enabled), we suggest staying in version 7.21.x in the meantime until we resolve the issue in a future release.

Administration

  • Enhancement (#3265): Support for the at sign character (@) in process data names, application parameter names, and activity parameter names.

    Note: Not applicable to the EFORMASPX application and activities.

  • Bug (#3238): Global lists: Fixed an issue where item values with only spaces were trimmed to empty strings after importing the global list definition.

  • Bug (#3266): Workflow applications: Fixed an unexpected exception error displayed in the UI after deleting a parameter from the application parameter edit form.

Directory Synchronization

  • Performance (#3276): AD and LDAP synchronizations: Improved system memory usage (client caching disabled) and error management.

Workflow Applications

  • Feature (#3231): Added new EXECSQL workflow application.

    For more information about its usage, refer to the EXECSQL Workflow Application chapter in the WorkflowGen Administration Guide.

Form Designer

  • Enhancement (#3221): The Attachment field tool now supports PDF file preview in Advanced mode.

  • Bug (#3240): Webforms: Fixed an issue where some form field controls (CheckBox, CheckBoxList, RadioButton and ListBox) would lose their current values after their section containers were changed from visible to hidden and then back to visible.

    Note: The process form must be re-saved in order to fix this issue.

  • Bug (#3252): Fixed an issue where some sections’ and/or fields’ condition texts were replaced with the last saved condition when multiple condition editors were open at the same time and then saved one after the other.

Workflow APIs

  • Enhancement (#3239): The completeFormAction function used by the different APIs (GraphQL, webhooks, and SOAP) now supports and generates a file attachment download link in the form archive for the associated input file context parameter.

WorkflowGen.My v4.7.0

  • Bug (#3236): Webforms: Fixed a regression issue (introduced in version 7.19.0) where a currency form field containing a valid value would show a format validation error in the French Canada (fr-CA) culture.

  • Bug (#3243): Webforms: Fixed an issue where some form field list controls’ (RadioButtonList, CheckBoxList, DropDownList, and ListBox) default selected items were not cleared when binding with the form data.

GraphQL v4.2.0

  • Change (#3277): Node.js 14.15.1 LTS version update.

  • Bug (#3247): Fixed an authorization exception error when a viewer tries to access an action’s parameters when they are not the action’s assignee.

  • Bug (#3278): Fixed a request multipart file upload issue (HTTP 500 error code) when the operations part of the query contained one or more carriage or line return characters (e.g. \n or \n\r).

Webhooks v5.5.0

  • Change (#3277): Node.js 14.15.1 LTS version update.

Auth v2.4.0

  • Change (#3277): Node.js 14.15.1 LTS version update.

SCIM v2.1.0

  • Change (#3277): Node.js 14.15.1 LTS version update.

Notes

  • All of the Node.js modules (GraphQL v4.2.0, Webhooks v5.5.0, Auth v2.4.0, and SCIM v2.1.0) now require Node.js version 14.15.1 LTS.

Reminders

  • Oracle database is no longer supported as of WorkflowGen version 7.16.0. We recommend migrating to MS SQL Server 2017 or later.

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2016 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL Server 2012, we highly recommend upgrading to MS SQL Server 2017 or 2019 for the best performance.

Installation Packs

WorkflowGen 7.22.0 (Upgrade)
WorkflowGen 7.22.0 (Clean Install - PowerShell)
WorkflowGen 7.22.0 (Clean Install - manual)
WorkflowGen.My v4.7.0

Documentation

WorkflowGen 7.22.0 Upgrade Guide: English - Français
WorkflowGen 7.22 PowerShell Installation: English - Français
WorkflowGen 7.22 Manual Installation: English - Français
WorkflowGen 7.22 Technical Guide: English - Français
WorkflowGen 7.22 Administration Guide: English - Français
WorkflowGen 7.22 User Portal Guide: English - Français
WorkflowGen 7.22 Integration Guide: English
WorkflowGen for Azure: English - Français
WorkflowGen for Docker: English - Français
WorkflowGen documentation: English - Français