WorkflowGen 8.2.2

Announcements Release Notes & Downloads
1

General

Workflow Engine

  • Bug (#3839): Fixed a regression issue (introduced in version 8) where an exception error was raised when starting a legacy ASP.NET XML Web Service workflow application without WSDL as a SOAP Web Service application type.

Auth v3.0.12 (Node.js app)

  • Security (#3850): OIDC authentication: Added the SameSite flag with the Lax value to some WorkflowGen session cookies.

Webhooks v6.1.5 (Node.js app)

  • Updated Node.js vulnerable dependencies.

Notes

Installation Packs

WorkflowGen 8.2.2 (Upgrade)
WorkflowGen 8.2.2 (Clean Install - PowerShell)
WorkflowGen 8.2.2 (Clean Install - manual)

Documentation

WorkflowGen 8.2.2 Upgrade Guide: English - Français
WorkflowGen 8.2 PowerShell Installation: English - Français
WorkflowGen 8.2 Manual Installation: English - Français
WorkflowGen 8.2 Technical Guide: English - Français
WorkflowGen 8.2 Administration Guide: English - Français
WorkflowGen 8.2 User Portal Guide: English - Français
WorkflowGen 8.2 Integration Guide: English
WorkflowGen 8.2 for Azure: English - Français
WorkflowGen 8.x for Docker: English - Français
WorkflowGen Documentation: English - Français

3

GraphQL does not work when I upgrade node to 18.18.2.

It works if I revert back to 14.21.2 even with WorkflowGen v8.2.2.

4

Any GraphQL error messages after the upgrade?

Have you attempted to restart your server?

Ensure that you overwrite the entire “/wfgen/graphql” folder.

5

No error. The request return code 500.

I restarted the server and overwrote the entire folder and it still does not work.

It works if I change the version of node to 14.21.2.

Is it working for you?

6

iisnode encountered an error when processing the request.

HRESULT: 0x2
HTTP status: 500
HTTP subStatus: 1002
HTTP reason: Internal Server Error

You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is ‘true’.

7

Thanks, I’ll look into upgrading an existing WorkflowGen tomorrow.

8

Hello,

We just made a test upgrade from version 8.0.8 using node.js version 14.16.1 LTS to version 8.2.2 using the node.js version 18.18.2 LTS with no issue while using GraphQL.

Kindly open a ticket in our Helpdesk system and we’ll investigate possible solutions.

Regards,
Lynn

9

Thank you.

There must have been an issue with nvm. I use nvm to handle multiple versions of nodejs.

After reinstalling NVM, it worked.

Thanks for your help