Important known issues
We have recently identified some regression bugs (#1950 and #2073) in this release that could affect the normal execution of workflow actions and the directory synchronization service with the Active Directory and LDAP connectors when the directory uses a login configured with AES (FIPS compliant) or Version 5 (Legacy) password management mode with an Encryption key.
These known issues have already been fixed in the latest release.
If you have already upgraded your WorkflowGen to version 7.13.0 or planning to upgrade a previous version then we recommend installing version 7.14.1
- Feature (#1911): Supports
Oktaidentity provider as new authentication method with the OpenID Connect standard. See the Okta integration section in the WorkflowGen Technical Guide for information on how to configure this authentication method.
Bug (#1562): Fixed an issue in the delegate user name search containing accented characters in Internet Explorer 11.
Bug (#1641): Fixed a filename encoding issue when downloading an attachment file with spaces in its name from the runtime webform in Firefox.
- Feature (#1911): Added new
Oktaauthentication mode. See the Okta integration section in the WorkflowGen Technical Guide for information on how to configure this authentication method.
Performance (#1903): Removed duplicate
WFPROCESS_INSTtable in MS SQL Server database.
Note: You must run the
Databases\MsSQLServer\Update_WFG-V7-13-0.sqlupgrade script if your WorkflowGen is hosted on SQL Server.
betastatus in version
Bug (#1929): Fixed a systematic exception error in the
action.assignableUsersfield when there were more than 100 users in the list result.
Version update to
Feature (#1911): Added support for the
- All of the Node.js modules (
Auth v1.0.0-beta.7, and
SCIM v1.0.0-beta.2) now require Node.js version
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 Server 2012, we highly recommend upgrading to MS SQL Server 2017 or 2019 for the best performance.