WorkflowGen 7.13.1

Important known issues

  • We have recently identified a regression bug (#2073) in this release that could affect 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. This known issue has been fixed in the release 7.14.1.

  • WorkflowGen OpenID Connect authentication configuration issue.

Workflow application

  • Bug (#1950): Fixed a regression issue (introduced in version 7.12.0) concerning a missing definition of the CreateDictionaryFromStringKeys method exception error that would be thrown when running a SendHttpPost workflow system action.

Auth v1.0.0-beta.8

  • Version update to 1.0.0-beta.8.

  • Bug (#1944): Fixed a failed authentication issue with the Okta authentication provider.


  • All of the Node.js modules (GraphQL v1.0.0, Webhooks v3.3.1, Auth v1.0.0-beta.8, and SCIM v1.0.0-beta.2) now require Node.js version 8.11.3.


  • 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.

Installation packs

WorkflowGen 7.13.1 (Upgrade)
WorkflowGen 7.13.1 (Clean install - PowerShell)
WorkflowGen 7.13.1 (Clean install - manual)
WorkflowGen.My 4.2.0

Docker image

WorkflowGen Docker image


WorkflowGen 7.13.1 Upgrade Guide
WorkflowGen 7.13.0 Technical Guide
WorkflowGen 7.13.0 Administration Guide
WorkflowGen 7.13.0 User Portal Guide
WorkflowGen Integration Guide

Documentation links do not appear to be working?
I receive the following message on each:

This site can’t be reached took too long to respond.



Hi Rogelio,

Seems Gitbooks had internal issues. It’s working fine on my end right now,


Hey Eddy,
Yes, all good now.

Hi Eddy,

Just wondering if you can help me out this morning (sorry for not using proper channels).

I looked through the forums and I found the following link

I would like to launch a request AND see the webform but also pass it context parameters.

I need some kind of blend of the following:


(I can pass context parameter but does not open webform, just a return value)



(I can see webform)

What would be the url to use?

Any help is much appreciated