Important known issues
An object reference error was raised when replacing an existing process with an XPDL file via the import function. This issue (bug #2348) has been fixed in the release 7.14.5.
Bug (#2049): Fixed a SQL exception error that would be thrown in the advanced search supervisor mode when a data name filter contained an invalid data name value.
Bug (#2050): Fixed a SQL exception error that would be thrown in statistics data reports when the selected data name filter contained invalid data name values.
Directory synchronization service (WorkflowGenDirSyncService)
- Bug (#2073): Fixed a regression issue (since version 7.10.0) that caused the synchronization connection to fail at the beginning in the directory synchronization Windows service with the Active Directory and LDAP connectors when the directory used a login configured with the password management mode in
AES (FIPS compliant)or
Version 5 (Legacy)with an
All of the Node.js modules (
Auth v1.0.0-beta.9, and
SCIM v1.0.0-beta.3) now require Node.js version
npm install --productioncommand is required on each of the modules (
\wfgen\scim) after the upgrade.
Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 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 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.