Overview

You must be administrator of the web server. You must know:

• The physical path on the web server where WorkflowGen web application is installed.

• The physical path on the web server where WorkflowGen Windows Services are installed.

• The URL of the web server where WorkflowGen is installed.

• MS SQL Server database:

  • The name of the MS SQL server.

  • The credentials of the SA account.

You'll need to perform the following actions:

• Update the web application files.

• Update the Windows Services files.

• Update the web configuration file.

If you're upgrading from WorkflowGen version 5, you must request a new license (trial, unlimited, or per user) and a new serial number for each of your WorkflowGen servers.

• The new license file must be copied to the \wfgen\bin folder.

• Define the new serial number in the \wfgen\web.config file (e.g. <add key="ApplicationSerialNumber" value="WFG-ENT-XXXXX-XXXXX-XXXX-XXXX" />).

This upgrade guide covers all of the procedures involved in upgrading WorkflowGen to version 9.2.5. It's aimed at system administrators who'll be updating the existing application.

Remote Approval

Remote Approval is now an integrated feature in WorkflowGen, and is no longer a separate module.

For instructions on configuring Remote Approval, see the Remote Approval section in the WorkflowGen Administration Guide.

If you have the former Remote Approval module configured, you can keep using it, but if you want to migrate to the new integrated feature, you must perform the following steps.

1. Uninstall the Remote Approval module (it's recommended that you make a backup of all previous Remote Approval files and folders beforehand):

   1. Open the Windows Services list and stop the Remote Approval service, usually named WorkflowGen RemoteApproval or WorkflowGen EmailListener.

   2. Delete the DRIVE:\Program Files (x86)\Advantys\WorkflowGen\RemApp\ folder.

   3. Delete the \wfgen\bin\RemoteApprovalConfig.dll and \wfgen\admin\RemoteApprovalConfig.aspx files.

2. In \wfgen\App_Data\CustomMenus\admin.xml, remove the Remote Approval menuItem node (you can delete the file entirely if it contains only this node).

3. Check Activate on the Remote Approval tab in the Administration Module Configuration panel.

The following workflow applications have been integrated as built-in or assembly applications. The corresponding web applications can be disabled and removed in IIS and file system folders since they're no longer used.

• EFORMASPX: \wfgen\WfApps\WebApps\EFormASPX

• GETUSERSFROMDIR: \wfgen\WfApps\WebServices\GetUsersFromDir

• RAISEEXCEPTION: \wfgen\WfApps\WebServices\RaiseException

To create a clean WorkflowGen database, you must use the full WorkflowGen manual installation pack, which is available at .

Update .NET version

WorkflowGen 9.2.5 requires .NET Framework 4.8, so you must install it before proceeding with this upgrade.

Update the root web.config file's URL rewrite rules

As of WorkflowGen 9.2.0, you MUST update your site's root web.config file with the new URL rewrite rules, based on how your WorkflowGen URL is configured. For instructions on how to do this, see the Update the root web configuration file section.

Using BACKURL_SUBMIT and BACKURL_CANCEL parameters in custom WorkflowGen URLs

As of version 7.15.5, the optional BACKURL_SUBMIT and BACKURL_CANCEL HTTP parameters used in custom WorkflowGen URLs (for example, when launching a new request and starting the first action within another website) now ONLY support absolute URLs (starting with http:// or https://), relative URLs (starting with /), or URLs defined in the PortalRedirectAllowedHttpUrls configuration parameter (e.g. value='blank.htm, myPage.htm').

As of version 7.15.0, the SMTP server account and Remote Approval incoming server account passwords are no longer encrypted in the web.config file.

Before upgrading an existing WorkflowGen server, you must manually reset the passwords in cleartext for the ApplicationSmtpPassword and RemoteApprovalIncomingServerPassword parameters in the web.config. Alternatively, you can use the provided convert-web-config-pwd.ps1 PowerShell script in \wfgen to decrypt and convert the passwords in the web.config.

Microsoft SQL Server 2008, 2012, and 2014 are no longer supported. While these versions will still be compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008, 2012, or 2014 will no longer be provided.

For clients currently hosting WorkflowGen on a database server older than MS SQL Server 2016, we highly recommend upgrading to the latest MS SQL Server version for the best performance.

To do this, launch the Update\Databases\MsSQLServer\Update_WFG-V7-0_SQL_Triggers_2012.sql database update script in your SQL Server Management Studio tool.

Oracle database is no longer supported as of WorkflowGen 7.16.0.

The Node.js modules include the GraphQL API, webhooks, SCIM, and Auth. For instructions on how to enable them, see the section.

Upgrade Node.js to version 18.20.7 LTS (see ).

As of WorkflowGen version 7.10.0, if you're using incoming webhooks or GraphQL to upload files when starting a new request or completing an action, you must set the GraphqlFileInputAllowedFolders, HooksFileInputAllowedFolders, GraphqlMaxInputFileContentSize, and HooksMaxInputFileContentSize configuration parameters with the appropriate values (see the section).

• GraphqlFileInputAllowedFolders and HooksFileInputAllowedFolders: These parameters should contain the physical paths of folders that contain files used in uploads.

• GraphqlMaxInputFileContentSize and HooksMaxInputFileContentSize: These parameters should contain the maximum file size in kilobytes when uploading files using the file content method.

The following dependencies have been updated as of WorkflowGen version 8:

• jQuery v1.7.2 or 1.10.12 → 3.5.1

• jQuery UI v1.8.20 or 1.10.3 → 1.12.1

• jQuery Colorbox v1.4.33 → 1.6.4

If you're using custom web forms configured in .NET 2.0, you can keep using them in .NET 2.0 or migrate them to .NET 4.

1. Use WorkflowGen.My.dll in version 2.x.

2. Use a .NET 2.0 application pool.

3. Disable Web apps secure mode in the Security section on the General tab in the Configuration Panel.

1. Use WorkflowGen.My.dll in version 8.x.x or later.

2. Use a .NET 4 application pool.

3. Define or update the following nodes in the web form’s web.config:

The WorkflowGen.My and Workflow Web Controls assemblies are no longer strong-named in order to allow non-specific version dependency when referenced by other applications such as custom assembly SDK Workflow applications in WorkflowGen.

This simplifies the deployment procedure of an assembly SDK Workflow application to WorkflowGen 6.2.0 and later, and allows upgrading WorkflowGen to a newer version without having to rebuild the application's assembly that was referencing an older version of WorkflowGen.My.

There are some considerations when deploying a custom assembly SDK workflow application in WorkflowGen, namely the assembly location, the reference to WorkflowGen.My, and the reference to other software libraries.

There are two ways of deploying an assembly file in WorkflowGen.

The assembly file must be copied to the three \bin folders containing the WorkflowGen executable files: \wfgen\bin, \wfgen\ws\bin, and DRIVE:\Program Files\Advantys\WorkflowGen\Services\bin.

The assembly file can be copied to a custom folder such as DRIVE:\MyWorkflowApps\Assembly.dll, and then use that specific path in the workflow application's definition.

WorkflowGen.My versions 3.1.0 and earlier are strong-named, which means your assembly must be built with and use the same version as your target WorkflowGen. This requires recompiling your assembly whenever you upgrade WorkflowGen to a newer version.

You can use one of the following workarounds to overcome this requirement:

1. Install the required WorkflowGen.My version in the system's Global Assembly Cache (GAC). For instructions on how to do this, see .

   OR

2. Add a delegate to handle the assembly resolve event in order to load the current WorkflowGen.My version. For instructions on how to do this, see the WorkflowGen Knowledge Base article.

   OR

As of version 3.2.0, WorkflowGen.My is no longer strong-named in order to allow non-specific version dependency when referenced by your assembly. You can simply deploy your assembly file using one of the two methods in the section above in WorkflowGen version 6.2.0 and later.

If your assembly uses third-party libraries, then these must also be deployed into the three WorkflowGen executable \bin folders. Alternatively, they can be installed into the system's Global Assembly Cache (GAC) if they are strong-named assemblies.

WorkflowGen is FIPS compliant as of version 7.10.0. If you want to enable FIPS compliance in your Windows environment, you have to configure the configuration password management and user password management modes beforehand.

In the Security section on the Configuration Panel General tab, set Configuration password management mode to AES (FIPS Compliant) and enter a 32-character encryption key. When you click Save, the application passwords will automatically be converted to the new symmetric encryption mode.

In the Authentication section on the Configuration Panel General tab, set Password management mode to One-way Hashing (SHA256 FIPS Compliant) mode.

• If you're using Applicative authentication in Version 5 (Legacy) password management mode, users' passwords will automatically be converted into One-way Hashing (SHA256 FIPS Compliant) the next time they log into WorkflowGen.

• If you're using Applicative authentication in One-way Hashing (SHA256) password management mode:

  1. Select IIS authentication mode.

WorkflowGen no longer supports Internet Explorer, Windows XP, Windows 7, Windows 8, or Windows Server 2003 or 2008.

MS SQL Server 2005 is no longer supported as of WorkflowGen version 6.2.0, MS SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0, and MS SQL Server 2012 is no longer supported as of WorkflowGen version 8.2.0.

Oracle database is no longer supported as of WorkflowGen 7.16.0.

The following applications are deprecated and are no longer provided as of WorkflowGen version 6:

• EFORMPDF

• DOCAPPROVAL

• DOCUPLOAD

However, if any of your processes still use these workflow applications, you can keep them declared under the WorkflowGen website as in version 5.

The following software is distributed with WorkflowGen (Apache 2.0, BSD, MIT, and other compatible licenses):

• bluebird (see )

• busboy (see )

• body-parser (see )

• change-case (see

It's important to clear your browser cache before connecting to the upgraded WorkflowGen website. This will remove the CSS, JavaScript, and image files used in previous versions of WorkflowGen.

Use the following URLs with the wfgen_admin user account:

• User Portal: http://[yoursite]/wfgen

Update configuration files

Apply the changes to the web configuration file based on the version from which you're upgrading. Once you've applied these changes, return to the Update configuration files section in the main upgrade section and continue with the changes there.

📌 Examples

• When upgrading from version 6.5.0, apply the changes in the When upgrading from version 6.5.0 section to the When upgrading from all 7.x.x versions and earlier section.

• When upgrading from version 7.22.1, apply the changes in the When upgrading from all 7.x.x versions and earlier section only.

When upgrading from version 5.7.4 and earlier

Check the following parameters in your \wfgen\web.config and add them if they aren't already there.

Remove the following deprecated parameters from <appSettings>:

Define the following nodes in <configuration>:

Define or update the following node in <configuration>/<system.web>:

Add the following new parameters to <appSettings>:

Add the following new parameter to <appSettings>:

Add or modify the AdministrationFormDataProviderName parameter as follows:

Add the following new parameters to <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameter to <appSettings> to configure the SENDHTTPPOST workflow application log file, replacing the value n with 0 to disable logging, 1 for simple logs, or 2 for debug logs:

Remove the following deprecated parameters from <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameter to <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameter to <appSettings>:

Add the following new parameters to <appSettings>:

Remove the following deprecated parameters from <appSettings>:

1. Add the following nodes after the existing <location> nodes in \wfgen\web.config:

2. Remove the node below from \wfgen\auth\web.config, \wfgen\hooks\web.config, and \wfgen\scim\web.config, if present:

Add the following new parameter to <appSettings>:

1. Add the following node after the existing <location> nodes in \wfgen\web.config:

2. Change the default value of RestApiClientRequestTimeout from 3000 to 30000 milliseconds.

Add the following new parameters to <appSettings>:

Add the following new parameter to <appSettings>:

Add the following new parameter to <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameter to <appSettings>:

Remove the existing Access-Control-Allow-* custom header nodes from location path="graphql" (as shown below), since they are deprecated as of version 7.22.1:

1. Add the following new parameters to <appSettings>:

2. Remove the following parameters from <appSettings>:

Run the SQL scripts listed below in order, starting with your current version of WorkflowGen, then continue running the scripts in the section in the main upgrade chapter.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-2-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-3-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-4-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-1.sqldatabase update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-2.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-5.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-2.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-3.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-4.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-7-1.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V5-7-2.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V6-0-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V6-1-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V6-1-3.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V6-1-4.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V6-2-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V6-5-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V6-6-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-0-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-1-1.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-2-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-3-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-6-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-10-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-11-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-12-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-13-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-14-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-15-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-15-2.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-16-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-17-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V7-22-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V8-0-0.sql database update script in your SQL Server Management Studio tool.

A new configuration parameter is required when upgrading from version 5.1.5 and earlier. This parameter allows you to provide a unique service name to the WorkflowGen Directory Synchronization service should you have multiple instances of WorkflowGen installed on a single server.

Add the following parameter to DRIVE:\Program Files\Advantys\WorkflowGen\Services\bin\WfgDirectoriesSyncService.exe.config:

A new configuration parameter is required when upgrading from version 5.1.5 or earlier. This parameter allows you to provide a unique service name to the WorkflowGen Engine service should you have multiple instances of WorkflowGen installed on a single server.

Add the following parameter to DRIVE:\Program Files\Advantys\WorkflowGen\Services\bin\WfgWorkflowEngineService.exe.config:

If you're upgrading from version 5.7.4 or earlier, copy the Transactions.xml file from \wfgen\WfApps\WebServices\XmlToDatabase\App_Data to \wfgen\App_Data\Files\XmlToDatabase.

As of WorkflowGen version 7, you must remove the xmlns attribute from these configuration files:

To do this, change <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> to <configuration>.

Overview

The following procedures apply to the WorkflowGen 9.2.5 upgrade pack, available at https://github.com/advantys/workflowgen-releases/releases.

Package contents

The upgrade pack is distributed as a compressed file containing the following folders:

• Inetpub: WorkflowGen web application files

• Program Files: WorkflowGen Windows Services files

• Databases: WorkflowGen database update and creation files

Stop the IIS server (or at least your WorkflowGen web applications) if other websites are using the same IIS server.

Stop the WorkflowGen Directory Sync and Engine services in the Windows Services Management Console.

Back up the following folders:

• DRIVE:\Inetpub\wwwroot\wfgen

• DRIVE:\Program Files\Advantys\WorkflowGen

If the file storage path isn't the standard DRIVE:\Inetpub\wwwroot\wfgen\App_Data path, then you have to back up the corresponding folder.

Perform a standard database backup using your DBMS tools.

Verify if the following deprecated files and folders used by Node.js-based applications still exist in your \wfgen folder, and delete them if they do.

1. Delete the following files and folders from the \wfgen\graphql folder:

   • \controllers

   • \models

Delete the following deprecated assembly .dll files from the \wfgen\bin, \wfgen\ws\bin, and \Program Files\Advantys\WorkflowGen\services\bin folders:

• Advantys.Directories

• Advantys.Directories.Web.UI.Administration

• Advantys.Web.UI.Charting

Copy and overwrite the upgrade content from Update\Inetpub\wwwroot\wfgen to your WorkflowGen web application folder. By default, the suggested physical path is DRIVE:\Inetpub\wwwroot\wfgen.

Delete the deprecated DRIVE:\Program Files\Advantys\WorkflowGen\Services\bin\EAGetMail40.dll file.

Overwrite the contents of your WorkflowGen Windows Services folder with the contents of Update\Program Files\Advantys\WorkflowGen. By default, the suggested physical path is DRIVE:\Program Files\Advantys\WorkflowGen.

Copy node.exe.config and trace.config (located in Update\Program Files\nodejs) to DRIVE:\Program Files\nodejs.

This section contains configuration parameter changes you need to apply, based on the version of WorkflowGen from which you're upgrading.

• When upgrading to version 9.2.5 from version 9.0.1 Beta, apply the changes in the When upgrading from version 9.0.1 Beta (v9 Beta 2) and earlier, When upgrading from version 9.0.2 Beta (v9 Beta 3), When upgrading from version 9.0.7 and earlier, and When upgrading from version 9.1.0 and earlier sections.

• When upgrading to version 9.2.5 from version 9.2.0 Beta 1, 9.2.1 Beta 2, 9.2.2 Beta 3, or 9.2.3 Beta 4, there are no changes to make to the web configuration file.

1. Add the following new parameters to <appSettings>:

2. Remove the following deprecated parameter from <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameters to <appSettings>:

1. Add the following new parameter to <appSettings> :

2. Update the value of the EngineServiceTimeoutSystemActionFrequency parameter to 120000 as follows:

Add the following new parameter to <appSettings> :

1. Update the value of the following parameter in <appSettings>:

2. Remove the following parameters from <appSettings> from version 8.1.0 Beta only:

Add the following new parameters to <appSettings> :

1. Add the following new parameters to <appSettings>:

2. Update the bindingRedirect node in all of the affected configuration files (listed below) from <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0" /> to <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />

1. Add the following new parameter to <appSettings>:

2. Update the value of the following parameter in <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameters to <appSettings>:

Add the following new parameter to <appSettings>:

1. Rename the following parameters in <appSettings>:

   as

2. Add the following new parameter to <appSettings>:

If you want to enable default HTTP error handling by WorkflowGen, replace the following parameter in <appSettings>:

with the following:

You must update your site's root web.config file with the new URL Rewrite rules.

First, make sure the tool is installed on your WorkflowGen server.

There are two sample files provided in the installation pack.

• If your WorkflowGen site uses the /wfgen path in its URL (e.g. https://yoursite/wfgen), refer to the Inetpub\wwwroot\web.config (in the manual installation pack) or Inetpub\wwwroot\web.config.sample sample file (in the update pack) for the new rules.

• If your WorkflowGen site does NOT use the /wfgen path in its URL (e.g. https://yoursite

As of WorkflowGen 9.2.0, If you're using custom form authentication with a login page created based on the provided /wfgen/login.aspx sample template, you need to update the login page file. To do this:

1. Open your WorkflowGen site's /wfgen/login.aspx file (which might have been renamed).

2. Replace the redirectToUrl = "/wfgen/show.aspx?QUERY=WELCOME"; line with redirectToUrl = "/wfgen/dashboard";.

As of WorkflowGen version 8, the WorkflowGen.My.Web.UI.WebControls.dll assembly has been merged into WorkflowGen.My.dll. This breaking change impacts webforms created in the Form Designer and the webforms' \bin folders, so you must perform one of the following procedures:

Run the \update\configuration\update-webforms-wfg-my-assembly.ps1 script in PowerShell inside the \wfgen\wfapps\webforms\ folder. This will automatically update your ASPX webforms and delete deprecated files and folders.

1. Delete the following files and folders from the\wfgen\wfapps\webforms\bin\ folder:

   • WorkflowGen.My.Web.UI.WebControls.dll

   • WorkflowGen.My.Web.Handlers.dll

In the \wfgen\graphql\web.config and \wfgen\hooks\web.config files, add the following to <system.webServer>:

Run the SQL scripts listed below in order, starting with your current version of WorkflowGen.

Launch the Update\Databases\MsSQLServer\Update_WFG-V8-0-2.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V8-0-3.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V8-1-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V8-2-0.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V9-0-1.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V9-0-2.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V9-0-3.sql database update script in your SQL Server Management Studio tool.

Launch the Update\Databases\MsSQLServer\Update_WFG-V9-1-0.sql database update script in your SQL Server Management Studio tool.

There is no database update script to run.

The WorkflowGen website and web applications must now use an application pool in .NET 4. If this hasn't already been configured, do the following:

1. Install .NET Framework 4 on the server, if it's not already installed.

2. Update the existing application pool or create a new application pool using .NET Framework 4 for:

   • the WorkflowGen website

To use the GraphQL, incoming webhooks, OpenID Connect Auth, and SCIM APIs, you must first install the following requirements:

1. In IIS, convert /wfgen/graphql to an application with a .NET 4 application pool (integrated pipeline).

2. Configure the GraphQL application authentication mode:

   • For Basic authentication: Enable Basic authentication.

1. Update the WorkflowGen web.config file with the following parameters used by incoming webhooks:

2. In IIS, convert /wfgen/hooks to an application with a .NET 4 application pool (integrated pipeline), and configure the hook application in Anonymous authentication mode.

In IIS, convert /wfgen/scim to an application with a .NET 4 application pool (integrated pipeline), and configure the application in Anonymous authentication mode.

In IIS, convert /wfgen/auth to an application with a .NET 4 application pool (integrated pipeline), and configure the application in Anonymous authentication mode.

Reboot your WorkflowGen web server.

The following workflow applications store their files in these new locations:

• EFORMASPX: \wfgen\App_Data\Files\EFormAspx

• XMLTODATABASE: \wfgen\App_Data\LogFiles\XmlToDatabase

• XMLTRANS: \wfgen\App_Data\Files\XmlTrans