Upgrade

Overview

The following procedures apply to the WorkflowGen 10.4.0 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

IIS server

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

WorkflowGen Windows Services

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

Backup

Application and data files

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.

Database

Perform a standard database backup using your DBMS tools.

Update WorkflowGen web application files

Delete deprecated Node.js application files and folders

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

   • \node_modules

   • \services

   • \utils

   • config.js

   • config.production.js

   • server.js

2. Delete the following files and folders from the \wfgen\hooks folder:

   • \controllers

   • \models

   • \node_modules

   • \services

   • \test

   • \utils

   • config.js

   • config.production.js

   • server.js

   • upload.js

3. Delete the following files and folders from the \wfgen\auth folder:

   • \controllers

   • \models

   • \node_modules

   • \static

   • \utils

   • config.js

   • config.production.js

   • server.js

4. Delete the following files and folders from the \wfgen\scim folder:

   • \controllers

   • \models

   • \node_modules

   • \services

   • \utils

   • config.js

   • config.production.js

   • server.js

5. Delete the \node_modules folder from the \wfgen\mcp folder.

Delete deprecated assembly files

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

• Advantys.Workflow.Applications.ExecSql

• Advantys.Workflow.Applications.GetUsersFromDir

• Advantys.Workflow.Applications.MergeForm

• Advantys.Workflow.Applications.RestApiClient

• Advantys.Workflow.Applications.SendMessage

• Advantys.Workflow.Applications.XmlToDatabase

• Advantys.Workflow.Applications.XmlTrans

• Advantys.Workflow.Reports

• Advantys.Workflow.Web.UI.Reports

Copy the upgrade pack content

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.

• Domain users and the Windows accounts used to run the WorkflowGen IIS application pool and Engine service must have read and write permissions for the \wfgen\App_Data folder.

• Do NOT copy and overwrite your existing DRIVE:\Inetpub\wwwroot\wfgen\web.config file if you want to keep your current WorkflowGen configuration settings and database connection information.

• It’s possible that the following default CSS files have been updated in this release and could overwrite any changes you had made in your existing installation:

  • \wfgen\App_Themes\Default\portal\css\Default.css

  • \wfgen\App_Themes\Default\admin\css\Default.css

• If you've made changes to any of the default files in the following folders (e.g. *.aspx, *.css, *.resx files), make a backup of the existing files prior to the upgrade and manually re-apply these changes to the corresponding version 9.x.x files:

  • \wfgen

  • \wfgen\App_Themes

  • \wfgen\App_Data\Templates\Emails

  • \wfgen\App_Data\Templates\Forms

  • \wfgen\App_Data\Templates\Processes

Update WorkflowGen Windows Services files

Delete deprecated DLL file

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

Overwrite the WorkflowGen Windows Services folder

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.

Do NOT copy and overwrite your existing DRIVE:\Program Files\Advantys\WorkflowGen\Services\bin\*.config files.

Update Node.js program files

First, overwrite the contents of your Node.js program folder with the contents of Update\Program Files\Nodejs. By default, the suggested physical path is DRIVE:\Program Files\Nodejs.

Then, copy node.exe.config and trace.config (located in Update\Program Files\Nodejs) to DRIVE:\Program Files\Nodejs.

If there's already a node.exe.config file in the DRIVE:\Program Files\Nodejs folder, do not overwrite it. Instead, add the following to the existing file's <configuration> node:

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-6.0.3.0" newVersion="6.0.3.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.0.0.5" newVersion="8.0.0.5" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
        </dependentAssembly>
    </assemblyBinding>
</runtime>

Update configuration files

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

This section has been divided to provide a quicker reference for clients upgrading from version 8.0.0 and later. If you're upgrading from version 7.22.15 or earlier, see the Legacy Upgrade section and perform the required modifications to the configuration files based on the version from which you're upgrading, then return to this section and continue with the rest of the required modifications.

📌 Examples

• When upgrading to version 10.4.0 from version 9.5.2, apply the changes in the When upgrading from all 9.x.x versions and earlier, When upgrading from version 10.0.5 and earlier, When upgrading from version 10.1.0 and earlier, When upgrading from version 10.2.2 and earlier, and When upgrading from version 10.3.0 and earlier sections.

• When upgrading to version 10.4.0 from version 10.3.0, apply the changes in the When upgrading from version 10.3.0 and earlier section only.

When upgrading from version 8.0.0 and earlier

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

   <add key="RemoteApprovalAuthClientId" value="" />
   <add key="RemoteApprovalAuthClientSecret" value="" />
   <add key="RemoteApprovalAuthScope" value="" />
   <add key="RemoteApprovalAuthAccessTokenUri" value="" />

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

   EngineTraceMode

When upgrading from version 8.0.1 and earlier

Add the following new parameters to <appSettings>:

<!-- AdobeSign -->
<add key="AdobeSignClientId" value="" />
<add key="AdobeSignClientSecret" value="" />
<add key="AdobeSignHostServer" value="" />
<add key="AdobeSignRefreshToken" value="" />
<add key="AdobeSignSendLogLevel" value="0" />
<add key="AdobeSignCheckLogLevel" value="0" />

When upgrading from version 8.0.2 and earlier

Add the following new parameters to <appSettings>:

<add key="EngineNotificationNotifyDelegator" value="Y" />
<add key="EnginePushNotificationSendExpoApiUrl" value="https://exp.host/--/api/v2/push/send" />

<!-- Docaposte -->
<add key="DocaposteUsername" value="" />
<add key="DocapostePassword" value="" />
<add key="DocaposteHostServer" value="" />
<add key="DocaposteOfferCode" value="" />
<add key="DocaposteOrganizationalUnitCode" value="" />
<add key="DocaposteSendLogLevel" value="0" />
<add key="DocaposteCheckLogLevel" value="0" />

When upgrading from version 8.0.7 and earlier

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

   <add key="EngineServiceMaxPausedSynchroActions" value="25" />

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

   <add key="EngineServiceTimeoutSystemActionFrequency" value="120000" />

When upgrading from version 8.0.10 and earlier

Add the following new parameter to <appSettings> :

<add key="PortalReportAdvancedViewPaging" value="N" />

When upgrading from version 8.1.0 Beta and earlier

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

   <add key="PortalListPageSize" value="25" />

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

   <add key="PortalReportAdvancedViewPageSize" value="25" />
   <add key="PortalReportAdvancedViewPageSizeOptions" value="10,25,50,100,250" />

When upgrading from version 8.1.2 and earlier

Add the following new parameters to <appSettings> :

<add key="GraphqlApiKeyEnabled" value="N" />
<add key="GraphqlApiKey" value="" />

When upgrading from version 8.1.3 and earlier

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

   <add key="PortalDisplayAssignedTeamAction" value="N" />
   <add key="HooksAllowImpersonateUser" value="N" />
   <add key="HooksApiKeyEnabled" value="N" />
   <add key="HooksApiKey" value="" />

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" />:

   • \wfgen\web.config

   • \wfgen\ws\web.config

   • \Program Files\Advantys\WorkflowGen\Services\bin\WfgWorkflowEngineService.exe.config

   • \Program Files\nodejs\node.exe.config

When upgrading from version 8.2.4 and earlier

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

   <add key="ApplicationDefaultFullWidth" value="N" />

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

   <add key="PortalCommentsPopUpHeight" value="600" />

3. Remove the following deprecated parameters from <appSettings>:

   ChartServiceAvoidColorCollision
   ChartServiceMaxSliceInPie
   ReportsChartServiceUrl
   ReportsChartTemplatePath
   ReportsChartTemplateExtension

When upgrading from version 8.2.4 and earlier OR from version 9.0.0 Beta (v9 Beta 1)

Add the following new parameters to <appSettings>:

<!-- Auth: Gardian -->
<add key="ApplicationSecurityAuthAcrValues" value="" />

<add key="AdobeSignRefreshUrl" value="/oauth/v2/refresh" />

<!-- Yousign -->
<add key="YousignApiKey" value="" />
<add key="YousignHostServer" value="" />
<add key="YousignSendLogLevel" value="0" />
<add key="YousignCheckLogLevel" value="0" />

When upgrading from version 9.0.1 Beta (v9 Beta 2) and earlier

Add the following new parameters to <appSettings>:

<add key="PortalDisplayRequestListWithActionsFollowUp" value="N" />

<!-- OpenAi -->
<add key="OpenAiApiKey" value="" />
<add key="OpenAiTranscriptionLogLevel" value="0" />

When upgrading from version 9.0.2 Beta (v9 Beta 3) and earlier

Add the following new parameter to <appSettings>:

<add key="OpenAiChatLogLevel" value="0" />

When upgrading from version 9.0.7 and earlier

1. Rename the following parameters in <appSettings>:

   <!-- OpenAI -->
   OpenAiApiKey
   OpenAiTranscriptionLogLevel
   OpenAiChatLogLevel

   as

   <!-- OpenAI -->
   OpenAIApiKey
   OpenAITranscriptionLogLevel
   OpenAIChatLogLevel

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

   <!-- OpenAI -->
   <add key="OpenAIChatApiUrl" value="" />

When upgrading from version 9.1.0 and earlier

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

<customErrors mode="Off"/>

with the following:

<customErrors mode="On" defaultRedirect="default_error_page.htm">
    <error statusCode="401" redirect="401.htm" />
    <error statusCode="404" redirect="404.htm" />
    <error statusCode="500" redirect="500.htm" />
</customErrors>

When upgrading from version 9.2.9 and earlier

1. Enable ApplicationSecurityEnableWebAppsSecureMode by setting this parameter to Y, as shown here:

   <add key="ApplicationSecurityEnableWebAppsSecureMode" value="Y" />

2. Add the following new parameter and define a custom encryption key:

   <add key="ApplicationSecurityEncryptionKey" value="CUSTOM_KEY" />

• Replace CUSTOM_KEY with at least 32 characters (256 bits) for strong encryption. Use a combination of uppercase and lowercase letters, numbers, and special characters.

• Clients using custom Visual Studio webforms should be upgrading to and referencing the latest WorkflowGen.My.dll to support this update. If the webform uses its own web.config, the ApplicationSecurityEnableWebAppsSecureMode and ApplicationSecurityEncryptionKey keys should also be redefined there.

When upgrading from version 9.2.11 and earlier

Add the following new parameters to <appSettings>:

<add key="ApplicationDefaultFileUploadForbiddenExtensions" value="exe,msi,msm,bat,cmd,ps1,sh,bash,csh,php,asp,aspx,jsp" />
<add key="HooksRateLimitWindowMs" value="900000" />
<add key="HooksRateLimitMax" value="1000" />

<add key="XmlToJsonLogLevel" value="0" />

<!-- Dropbox Sign -->
<add key="DropboxSignApiKey" value="" />
<add key="DropboxSignHostServer" value="https://api.hellosign.com/v3" />
<add key="DropboxSignSendLogLevel" value="0" />
<add key="DropboxSignCheckLogLevel" value="0" />

Replace the following code in <runtime>:

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
        </dependentAssembly>
    </assemblyBinding>
</runtime>

with the following:

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.Logging" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.Tokens" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.JsonWebTokens" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
        </dependentAssembly>
    </assemblyBinding>
</runtime>

When upgrading from all 9.x.x versions and earlier

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

<add key="EngineServiceDataIndexingFrequency" value="10000" />

<!-- Chunks and Embeddings -->
<add key="GenerateChunksBatchSize" value="200" />
<add key="GenerateChunksSize" value="1000" />
<add key="GenerateChunksOverlap" value="200" />
<add key="GenerateChunksMaxCount" value="100" />
<add key="GenerateChunksLanguageCode" value="0" />
<add key="GenerateEmbeddingsApiProvider" value="openai" />
<add key="GenerateEmbeddingsApiEndpoint" value="https://api.openai.com/v1/embeddings" />
<add key="GenerateEmbeddingsApiKey" value="" />
<add key="GenerateEmbeddingsApiModel" value="text-embedding-3-small" />
<add key="GenerateEmbeddingsApiDimensions" value="384" />
<add key="GenerateEmbeddingsApiCallDelay" value="100" />
<add key="GenerateEmbeddingsApiMaxRetries" value="10" />

⚠️ Important: The default language code for full-text search (GenerateChunksLanguageCode in the web.config file and WFDATASET_CHUNK database table index) is set to 0 (Neutral). We recommend setting this to the appropriate language code that matches the primary language of your request data text and file values for better search results. For example, use 1033 for English or 1036 for French:

<add key="GenerateChunksLanguageCode" value="1033" />

You must also set the same language code in the database creation script (Create_WFG_SQL_Indexes.sql) or update script (Update_WFG-V10-0-0.sql) before running it:

CREATE FULLTEXT INDEX ON WFDATASET_CHUNK
(
    CHUNK LANGUAGE 1033 -- English
)
KEY INDEX PK_CHUNK
ON WFDATASET_CATALOG

To retrieve the full list of supported language codes, run the following SQL query in SQL Server Management Studio (SSMS):

select * from sys.fulltext_languages;

📌 Example of settings when using OpenAI embeddings API:

<add key="GenerateEmbeddingsApiProvider" value="openai" />
<add key="GenerateEmbeddingsApiEndpoint" value="https://api.openai.com/v1/embeddings" />
<add key="GenerateEmbeddingsApiKey" value="YOUR_OPENAI_API_KEY" />
<add key="GenerateEmbeddingsApiModel" value="text-embedding-3-small" />

📌 Example of settings when using Azure OpenAI embeddings API:

<add key="GenerateEmbeddingsApiProvider" value="azure-openai" />
<add key="GenerateEmbeddingsApiEndpoint" value="https://custom-domain.openai.azure.com" />
<add key="GenerateEmbeddingsApiKey" value="YOUR_AZURE_OPENAI_API_KEY" />
<add key="GenerateEmbeddingsApiModel" value="text-embedding-3-small" />

📌 Example of settings when using a local LM Studio server with a custom text embedding model:

<add key="GenerateEmbeddingsApiProvider" value="lm-studio" />
<add key="GenerateEmbeddingsApiEndpoint" value="http://localhost:1234/v1/embeddings" />
<add key="GenerateEmbeddingsApiKey" value="YOUR_LM_STUDIO_API_KEY" />
<add key="GenerateEmbeddingsApiModel" value="text-embedding-all-minilm-l6-v2-embedding" />

Step 2: Add the following new parameters to <appSettings>:

<add key="GenerateEmbeddingsApiAuthMethod" value="bearer" />
<add key="GenerateEmbeddingsApiAuthHeader" value="Authorization" />
<add key="GenerateEmbeddingsApiRetriesDelay" value="5000" />

📌 Example of settings for Azure OpenAI that uses the api-key method and header:

<add key="GenerateEmbeddingsApiAuthMethod" value="api-key" />
<add key="GenerateEmbeddingsApiAuthHeader" value="api-key" />

📌 Example of settings for OpenAI and local LM Studio server that uses the bearer method and Authorization header:

<add key="GenerateEmbeddingsApiAuthMethod" value="bearer" />
<add key="GenerateEmbeddingsApiAuthHeader" value="Authorization" />

Step 3: In these configuration files:

• \wfgen\web.config

• \Program Files\Advantys\WorkflowGen\Services\bin\WfgWorkflowEngineService.exe.config

• \Program Files\Advantys\WorkflowGen\Services\bin\WfgDirectoriesSyncService.exe.config

• \Program Files\nodejs\node.exe.config

add the following to the configuration node:

<system.data>
    <DbProviderFactories>
        <add name="Npgsql Data Provider" invariant="Npgsql" description=".Net Data Provider for PostgreSQL" type="Npgsql.NpgsqlFactory, Npgsql, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7"/>
    </DbProviderFactories>
</system.data> 

Step 4: In these configuration files:

• \wfgen\web.config

• \wfgen\ws\web.config

• \Program Files\Advantys\WorkflowGen\Services\bin\WfgWorkflowEngineService.exe.config

• \Program Files\nodejs\node.exe.config

update the <runtime> node with the following (or add it if it's not defined):

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.JsonWebTokens" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.Logging" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.Tokens" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-6.0.3.0" newVersion="6.0.3.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.0.0.5" newVersion="8.0.0.5" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
        </dependentAssembly>
    </assemblyBinding>
</runtime>

Step 5: In these configuration files:

• \wfgen\wfapps\webforms\web.config

• \Program Files\Advantys\WorkflowGen\Services\bin\WfgDirectoriesSyncService.exe.config

update the <runtime> node with the following (or add it if it's not defined):

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-6.0.3.0" newVersion="6.0.3.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-8.0.0.5" newVersion="8.0.0.5" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
        </dependentAssembly>
    </assemblyBinding>
</runtime>

When upgrading from version 10.0.5 or earlier

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

<add key="ApplicationWebFormsEnableSingleDigitPadding" value="N" />

Step 2: In <appSettings>, change the value of ApplicationSecurityAuthUsernameClaim to email as the default value. It should appear as follows:

<add key="ApplicationSecurityAuthUsernameClaim" value="email" />

If your administrator has already set another custom value, you can skip this step.

Step 3: In \wfgen\wfapps\webforms\web.config, add the following under <configuration>:

<system.web>
    <compilation>
        <assemblies>
            <add assembly="netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51"/>
            <add assembly="System.Data.Common, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
        </assemblies>
    </compilation>
</system.web>

Step 4: In \Program Files\nodejs\node.exe.config, add <probing privatePath="bin" /> to the <runtime> node. It should appear as follows:

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <probing privatePath="bin" />

When upgrading from version 10.1.0 and earlier

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

<add key="ExtractTextLogLevel" value="0" />
<add key="AdministrationGlobalListCsvDelimiter" value="," />
<add key="ReportsCsvDelimiter" value="auto" />

<!-- Mistral AI -->
<add key="MistralApiKey" value="" />
<add key="MistralChatApiUrl" value="https://api.mistral.ai/v1/chat/completions" />

<!-- Google Gemini -->
<!-- Note: Gemini uses a beta endpoint (v1beta). URL may change when the API becomes GA. -->
<add key="GeminiApiKey" value="" />
<add key="GeminiChatApiUrl" value="https://generativelanguage.googleapis.com/v1beta/openai/chat/completions" />

<!-- Anthropic -->
<add key="AnthropicApiKey" value="" />
<add key="AnthropicChatApiUrl" value="https://api.anthropic.com/v1/messages" />
<add key="AnthropicBetaHeaderName" value="anthropic-beta" />
<add key="AnthropicBetaHeaderValue" value="files-api-2025-04-14" />

Step 2: In <appSettings>, change the value of OpenAIChatApiUrl to https://api.openai.com/v1/chat/completions. It should appear as follows:

<add key="OpenAIChatApiUrl" value="https://api.openai.com/v1/chat/completions" />

Step 3: In <appSettings>, change the value of ApplicationDefaultFullWidth to Y. It should appear as follows:

<add key="ApplicationDefaultFullWidth" value="Y" />

When upgrading from version 10.2.2 and earlier

Step 1: Add the following MCP settings to <appSettings>:

<!-- OAuth Server -->
<add key="OAuthServerEnabled" value="false" />
<add key="OAuthServerKeyEncryptionKey" value="" />
<add key="OAuthServerBridgeTokenSigningSecret" value="" />
<add key="OAuthServerAccessTokenLifetimeSeconds" value="3600" />
<add key="OAuthServerAuthorizationCodeLifetimeSeconds" value="600" />
<add key="OAuthServerRefreshTokenLifetimeSeconds" value="7776000" />
<add key="OAuthServerAllowLocalhostRedirects" value="true" />

<!-- MCP -->
<add key="McpResourceUri" value="" />
<add key="McpAllowedScopes" value="mcp:read mcp:write mcp:process_admin mcp:admin" />
<add key="McpDiagnosticLogLevel" value="INFO" />
<add key="McpDevAuthBridgeMode" value="" />
<add key="McpDevAuthBridgeUsername" value="" />

• You should add or merge these MCP settings during the upgrade procedure even if you're not enabling MCP immediately.

• Set OAuthServerEnabled=true only when WorkflowGen already uses OIDC or SAML authentication, or when the deployment includes switching WorkflowGen to OIDC or SAML. Otherwise, keep OAuthServerEnabled=false.

• When enabling MCP OAuth, generate a 32-byte base64 or base64url value for OAuthServerKeyEncryptionKey, and set a strong random value for OAuthServerBridgeTokenSigningSecret. These values can be configured from the WorkflowGen Administration Module Configuration panel after the upgrade, or directly in the web.config file during scripted/manual upgrade work.

Step 2: Add the following SMTP settings to <appSettings>:

<add key="ApplicationSmtpOAuthClientId" value="" />
<add key="ApplicationSmtpOAuthClientSecret" value="" />
<add key="ApplicationSmtpOAuthScope" value="https://outlook.office365.com/.default" />
<add key="ApplicationSmtpOAuthAccessTokenUri" value="" />

When upgrading from version 10.3.0 and earlier

Step 1: In \wfgen\web.confg\, add the following new parameters to <appSettings>:

<add key="ApplicationDefaultFileUploadPdfSecurityProfile" value="Off" />
<add key="McpMaxInputFileSize" value="51200" />

ApplicationDefaultFileUploadPdfSecurityProfile configures the PDF upload security profile. Possible values:

• Compatibility: Blocks detected active content and malformed PDFs while allowing encrypted PDFs, XFA, and object streams.

• Strict: Blocks detected active content and malformed PDFs and also blocks encrypted PDFs, XFA, and object streams. Use this profile when validation must fail closed for those formats.

• Off: Disables PDF-specific validation. This is the default in the shipped configuration.

PDF validation applies to new PDFs uploaded through standard and advanced WorkflowGen form controls. It does not change API uploads, remote-launch uploads, Administration process data uploads, or previously stored attachments.

McpMaxInputFileSize is the MCP artifact input limit in KB. The maximum supported value is 51200 KB, and the configured value must be a positive integer. It applies to process XPDL artifacts and application and Global List JSON artifacts.

Step 2: In \wfgen\web.config, replace the existing <location path="mcp"> block with:

<location path="mcp" inheritInChildApplications="false">
    <system.web>
        <httpRuntime requestValidationMode="2.0" maxRequestLength="51200" targetFramework="4.8" />
    </system.web>
    <system.webServer>
        <modules>
            <remove name="ApplicationSecurityAuthenticationModule" />
        </modules>
        <security>
            <requestFiltering>
                <requestLimits maxAllowedContentLength="52428800" />
            </requestFiltering>
        </security>
    </system.webServer>
</location>

The ASP.NET maxRequestLength value is in KB. The IIS maxAllowedContentLength value is in bytes.

Step 3: In \wfgen\mcp\web.config, add the matching request limit inside <system.webServer><security><requestFiltering>, before <hiddenSegments>:

<requestLimits maxAllowedContentLength="52428800" />

The update pack supplies this change in \wfgen\mcp\web.config.sample. Do not replace the active MCP configuration file if it contains installation-specific iisnode settings.

If \wfgen\mcp\web.config does not exist because MCP was not previously enabled, copy web.config.sample to web.config when enabling the MCP child application.

Both the parent \wfgen\web.config limits and the child \wfgen\mcp\web.config limit must be merged for 50 MB MCP artifact requests.

Step 4: If MCP OAuth is already enabled, preserve these existing values exactly:

<add key="OAuthServerKeyEncryptionKey" value="CURRENT_VALUE" />
<add key="OAuthServerBridgeTokenSigningSecret" value="CURRENT_VALUE" />

Do not copy blank sample values over the deployed secrets.

Step 5: As of version 10.3.1, WorkflowGen also supports the optional McpFileUploadPath, McpInputFileAllowedFolders, McpInputFileAllowedHttpUrls, and McpInputFileDownloadTimeout artifact settings. They are not present in the shipped root sample. Add them only when the WorkflowGen Integration Guide defaults must be overridden.

By default, WorkflowGen stages artifacts under Files\MCP\Uploads in ApplicationDataPath, allows that staging folder, allows no external HTTP(S) artifact locations, and uses a 100000 millisecond download timeout. Ensure the MCP IIS application-pool identity has read and write permission on the default or customized staging folder.

Step 6: If SMTP OAuth is configured, verify that ApplicationSmtpOAuthAccessTokenUri is an absolute HTTPS URL. As of version 10.3.1, WorkflowGen will reject a missing, relative, or non-HTTPS token endpoint.

Step 7: Update the following service configuration files:

• In both WfgWorkflowEngineService.exe.config and WfgDirectoriesSyncService.exe.config, add the following block immediately after the opening <configuration> element:

  <system.data>
      <DbProviderFactories>
          <add name="Npgsql Data Provider"
               invariant="Npgsql"
               description=".Net Data Provider for PostgreSQL"
               type="Npgsql.NpgsqlFactory, Npgsql, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7" />
      </DbProviderFactories>
  </system.data>

• In WfgDirectoriesSyncService.exe.config, add the following <runtime> block immediately before the closing </configuration> element:

  <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
              <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-6.0.3.0" newVersion="6.0.3.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-8.0.0.5" newVersion="8.0.0.5" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
          </dependentAssembly>
      </assemblyBinding>
  </runtime>

• In WfgWorkflowEngineService.exe.config, replace the existing <runtime> block with the following:

  <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
              <assemblyIdentity name="Microsoft.IdentityModel.JsonWebTokens" publicKeyToken="31bf3856ad364e35" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="Microsoft.IdentityModel.Logging" publicKeyToken="31bf3856ad364e35" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="Microsoft.IdentityModel.Tokens" publicKeyToken="31bf3856ad364e35" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-8.2.0.0" newVersion="8.2.0.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-6.0.3.0" newVersion="6.0.3.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-8.0.0.5" newVersion="8.0.0.5" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
          </dependentAssembly>
          <dependentAssembly>
              <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
              <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
          </dependentAssembly>
      </assemblyBinding>
  </runtime>

When upgrading from version 10.3.1 and earlier

In \wfgen\web.confg\, add the following new parameters to <appSettings>:

<add key="ApplicationSecurityChangeEventIntegrityKey" value="" />
<add key="ApplicationChangeEventMode" value="OFF" />
<add key="ApplicationChangeEventRetentionDays" value="365" />

When upgrading from WorkflowGen version 9.7.0 or later, you must preserve the existing Change events integrity key and data if this feature was enabled. See Preserving change events configuration in the Important notes before upgrading section for more information.

Update the root web configuration file

You must update your site’s root web.config file with the new URL Rewrite rules when upgrading to version 10.2.2 or earlier. If you're upgrading from version 10.3.0 and applied the sample during the 10.3.0 upgrade, there are no changes to make to the root web configuration file.

Make sure the URL Rewrite tool is installed on your WorkflowGen server.

There are two sample files provided in the installation pack. Compare and merge the target root sample.

• 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), refer to the Inetpub\wwwroot\web.config.without-wfgen sample file for the new rules.

You can configure the redirection rules directly in the main web.config file. To do this, copy the rules found in Inetpub\wwwroot\web.config.without-wfgen to the web.config file, under <rewrite> / <rules> and right before the </configuration> closing tag:

<system.webServer>
    <rewrite>
        <rules>
            [...]
        </rules>
    </rewrite>
</system.webServer>

MCP rules

For MCP OAuth support, make sure the root web.config file includes the following URL Rewrite rules inside <system.webServer><rewrite><rules>. Place these rules near the beginning of the <rules> list, immediately after the existing dashboard rewrite rules and before the existing portal/admin route rewrite rules.

In a standard /wfgen deployment, insert them after <rule name="Rewrite to wfgen dashboard" ...> and before <rule name="Rewrite to wfgen go to view" ...>.

Keep the three MCP rules together and in the order shown below. IIS URL Rewrite evaluates rules from top to bottom, and these MCP OAuth routes should be matched before broader WorkflowGen route rules.

<rule name="Rewrite to wfgen OAuth auth bridge" stopProcessing="true">
    <match url="^wfgen/oauth-auth-bridge$" />
    <action type="Rewrite" url="/wfgen/show.aspx?qry=OAUTH_AUTH_BRIDGE" appendQueryString="true" />
</rule>
<rule name="Rewrite root OAuth protected-resource metadata for MCP" stopProcessing="true">
    <match url="^\.well-known/oauth-protected-resource/wfgen/mcp$" />
    <action type="Redirect" url="/wfgen/mcp/.well-known/oauth-protected-resource" redirectType="Temporary" />
</rule>
<rule name="Rewrite root OAuth authorization-server metadata for MCP" stopProcessing="true">
    <match url="^\.well-known/oauth-authorization-server/wfgen/mcp$" />
    <action type="Redirect" url="/wfgen/mcp/.well-known/oauth-authorization-server" redirectType="Temporary" />
</rule>

For deployments where WorkflowGen is installed at the web root and the MCP endpoint is /mcp, use the corresponding root-deployment rules instead of the /wfgen-prefixed rules.

For this web-root deployment shape, insert the rules after <rule name="Rewrite to dashboard" ...> and before <rule name="Rewrite to go to view" ...>.

<rule name="Rewrite to OAuth auth bridge" stopProcessing="true">
    <match url="^oauth-auth-bridge$" />
    <action type="Rewrite" url="/show.aspx?qry=OAUTH_AUTH_BRIDGE" appendQueryString="true" />
</rule>
<rule name="Rewrite root OAuth protected-resource metadata for MCP" stopProcessing="true">
    <match url="^\.well-known/oauth-protected-resource/mcp$" />
    <action type="Redirect" url="/mcp/.well-known/oauth-protected-resource" redirectType="Temporary" />
</rule>
<rule name="Rewrite root OAuth authorization-server metadata for MCP" stopProcessing="true">
    <match url="^\.well-known/oauth-authorization-server/mcp$" />
    <action type="Redirect" url="/mcp/.well-known/oauth-authorization-server" redirectType="Temporary" />
</rule>

Change events rules

For Change events support, make sure the root web.config file includes the three Change events URL Rewrite rules from the shipped sample configuration. Keep the rules together and in the order shown below.

For a standard /wfgen deployment, use the rules from the standard root web.config.sample file. The rules must match these URL patterns, in this order:

1. ^wfgen/admin/change-events/printable$

2. ^wfgen/admin/change-events/([0-9]+)$

3. ^wfgen/admin/change-events$

For deployments where WorkflowGen is installed at the website root, use the corresponding rules from the web.config.without-wfgen sample file. The rules must match these URL patterns, in this order:

1. ^admin/change-events/printable$

2. ^admin/change-events/([0-9]+)$

3. ^admin/change-events$

Do not change the order of these rules when adding them to the root web.config file.

Update the login.aspx sample file (custom authentication only)

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";.

Update Form Designer webforms for versions 8 and later

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:

Method 1: Use the provided PowerShell script

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.

This script requires PowerShell version 7.0 or later.

It will update all .aspx files located in the \webforms folder, including those not managed by the Form Designer. If you have custom webforms in this folder that use another version of WorkflowGen.My.dll, then you should skip the changes to these .aspx files. You can do this by moving these files to a temporary folder before running the script, and then copying them back to the original folder.

📌 Usage example

.\update-webforms-wfg-my-assembly.ps1 -Path "c:\inetpub\wwwroot\wfgen\wfapps\webforms" -Verbose

Method 2: Manually

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

   • \de

   • \fr

   • \hu

   • \pl

2. Upgrade each of your webforms created in the Form Designer, either by re-saving them or by manually replacing the <%@ Register Assembly="WorkflowGen.My.Web.UI.WebControls" ... %> tag with <%@ Register Assembly="WorkflowGen.My" ... %> inside each of your .aspx files.

Update the WorkflowGen database

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

This section has been divided to provide a quicker reference for clients upgrading from version 8.0.0 and later. If you're upgrading from version 7.22.15 or earlier, see the WorkflowGen Legacy Upgrade section and run the required database update scripts based on the version from which you're upgrading, then return to this section and continue with the rest of the required scripts.

For versions 8.0.1 and earlier

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

For versions 8.0.2 and earlier

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

For versions 8.0.x and earlier

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

For versions 8.1.3 and earlier

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

For versions 8.2.4 and earlier or version 9.0.0 Beta (v9 Beta 1)

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

For versions 9.0.1 Beta (v9 Beta 2) and earlier

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

For versions 9.0.2 Beta (v9 Beta 3) and earlier

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

For versions 9.0.7 and earlier

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

For versions 9.2.5 and earlier

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

For versions 9.2.7 and earlier

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

For versions 9.2.11 and earlier

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

For all 9.x.x versions and earlier

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

⚠️ Important: If you've changed the language code in the web.config parameter GenerateChunksLanguageCode (default is 0 for Neutral) for full-text search, you must manually update the language code in the Update_WFG-V10-0-0.sql script. If you're creating a new WorkflowGen database, update Create_WFG_SQL_Indexes.sql instead. The language code must match the new GenerateChunksLanguageCode value. For example, use 1033 for English or 1036 for French:

CREATE FULLTEXT INDEX ON WFDATASET_CHUNK
(
    CHUNK LANGUAGE 1033 -- English
)
KEY INDEX PK_CHUNK
ON WFDATASET_CATALOG

To retrieve the full list of supported language codes, run the following SQL query in SQL Server Management Studio (SSMS):

select * from sys.fulltext_languages;

For versions 10.0.0 (v10 Preview 1) and earlier

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

For versions 10.0.1 (v10 Preview 2) and earlier

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

For versions 10.0.5 and earlier

• If you're using MS SQL Server, launch the Update\Databases\MsSQLServer\Update_WFG-V10-1-0.sql database update script in your SQL Server Management Studio tool.

• If you're using PostgreSQL, launch the Update\Databases\PostgreSQL\Update_WFG-V10-1-0.sql database update script in your pgAdmin tool.

For versions 10.1.0 and earlier

• If you're using MS SQL Server, launch the Update\Databases\MsSQLServer\Update_WFG-V10-2-0.sql database update script in your SQL Server Management Studio tool.

• If you're using PostgreSQL, launch the Update\Databases\PostgreSQL\Update_WFG-V10-2-0.sql database update script in your pgAdmin tool.

For versions 10.2.2 and earlier

• If you're using MS SQL Server, launch the Update\Databases\MsSQLServer\Update_WFG-V10-3-0.sql database update script in your SQL Server Management Studio tool.

• If you're using PostgreSQL, launch the Update\Databases\PostgreSQL\Update_WFG-V10-3-0.sql database update script in your pgAdmin tool.

For versions 10.3.0 and earlier

• If you're using MS SQL Server, launch the Update\Databases\MsSQLServer\Update_WFG-V10-3-1.sql database update script in your SQL Server Management Studio tool.

• If you're using PostgreSQL, launch the Update\Databases\PostgreSQL\Update_WFG-V10-3-1.sql database update script in your pgAdmin tool.

For versions 10.3.1 and earlier

• If you're using MS SQL Server, launch the Update\Databases\MsSQLServer\Update_WFG-V10-4-0.sql database update script in your SQL Server Management Studio tool.

• If you're using PostgreSQL, launch the Update\Databases\PostgreSQL\Update_WFG-V10-4-0.sql database update script in your pgAdmin tool.

Before running the PostgreSQL script, configure the migration session so the intended WorkflowGen schema is the first effective schema for unqualified object creation. Confirm that current_schema() identifies that schema and that the existing wfprocess and users tables resolve in the same schema. A normal "$user", public search path is insufficient when the login has a private schema first, because reads can fall through to WorkflowGen while new objects are created in the private schema.

Do not hardcode public; use the installation's actual WorkflowGen schema and owner, avoid same-name shadow objects, and verify the new Change events tables and identity sequence were created beside the existing WorkflowGen tables. When access is granted object by object, grant the normal application table and identity-sequence rights on the new objects.

Configure IIS

Domain users and the Windows accounts used to run the WorkflowGen IIS application pool and Engine service must have read and write permissions for the \wfgen\app_data folder.

Update or create the application pool in .NET 4

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

   • \wfgen

   • \wfgen\wfapps\webforms (create this IIS web application if it isn’t already created)

   • \wfgen\ws

3. If your application pool is set to use Classic Managed Pipeline Mode, make sure ASP.NET v4.0.30319 is set to Allowed in the IIS manager ISAPI and CGI Restrictions list.

WorkflowGen Node.js-based web applications

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

• Node.js v24.19.0 LTS

• iisnode

• IIS URL Rewrite

• Visual C++ Redistributable ✏️ Note: This library is required if you encounter the error The specified module could not be found regarding the edge and edge-js libraries when accessing the /wfgen/graphql, /wfgen/hooks, /wfgen/scim and /wfgen/mcp web apps.

• Delete each existing Node.js-based application's node_modules folder (located under \wfgen\auth, \wfgen\graphql, \wfgen\hooks, and \wfgen\scim) before copying the files from the upgrade pack.

• After enabling GraphQL, incoming webhooks, OpenID Connect Auth, SCIM, or MCP, the WorkflowGen DLLs will be in use by Node.js, so they'll be locked from being updated. In order to update the DLLs, it's necessary to stop IIS.

To enable WorkflowGen GraphQL:

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.

   • For WorkflowGen Applicative authentication:

     • Make sure the /wfgen web application already has WorkflowGen Applicative authentication enabled.

     • Enable Anonymous authentication.

3. Update the WorkflowGen web.config file with the following parameters used by GraphQL:

   <add key="GraphqlMaxPageSize" value="100" />
   <add key="GraphqlMaxBatchSize" value="1000" />
   <add key="GraphqlDefaultPageNumber" value="1" />
   <add key="GraphqlDefaultPageSize" value="30" />
   <add key="GraphqlGraphiqlEnabled" value="N" />
   <add key="GraphqlLoadersCacheEnabled" value="Y" />
   <add key="GraphqlDebugEnabled" value="N" />
   <add key="GraphqlQueryTimeout" value="90000" />
   <add key="GraphqlOperationTimeout" value="30000" />
   <add key="GraphqlMaxOperationCount" value="10000" />
   <add key="GraphqlMaxInputFileSize" value="10240" />
   <add key="GraphqlMaxInputFileContentSize" value="0" />
   <add key="GraphqlInputFileDownloadTimeout" value="100000" />
   <add key="GraphqlInputFileAllowedFolders" value="" />
   <add key="GraphqlInputFileAllowedHttpUrls" value="" />

To enable WorkflowGen incoming webhooks:

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

   <add key="HooksDebugEnabled" value="N" />
   <add key="HooksOperationTimeout" value="30000" />
   <add key="HooksMaxInputFileSize" value="10240" />
   <add key="HooksMaxInputFileContentSize" value="0" />
   <add key="HooksInputFileDownloadTimeout" value="100000" />
   <add key="HooksInputFileAllowedFolders" value="" />
   <add key="HooksInputFileAllowedHttpUrls" value="" />

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.

If your WorkflowGen is configured to use WorkflowGen Applicative authentication or a custom authentication, you must remove the authentication module from the /hooks/web.config file as follows:

For WorkflowGen Applicative authentication:

<location path="hooks" inheritInChildApplications="false">
    <system.webServer>
        <modules>
            <remove name="ApplicationSecurityAuthenticationModule" />
        </modules>
    </system.webServer>
</location>

For Custom authentication:

<location path="hooks" inheritInChildApplications="false">
    <system.webServer>
        <modules>
            <remove name="MyCustomAuthModule" />
        </modules>
    </system.webServer>
</location>

To enable WorkflowGen SCIM:

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

If your WorkflowGen is configured to use WorkflowGen Applicative authentication or a custom authentication, you must remove the authentication module from the /scim/web.config file as follows:

For WorkflowGen Applicative authentication:

<location path="scim" inheritInChildApplications="false">
    <system.webServer>
        <modules>
            <remove name="ApplicationSecurityAuthenticationModule" />
        </modules>
    </system.webServer>
</location>

For Custom authentication:

<location path="scim" inheritInChildApplications="false">
    <system.webServer>
        <modules>
            <remove name="MyCustomAuthModule" />
        </modules>
    </system.webServer>
</location>

To enable WorkflowGen OpenID Connect Auth:

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

If your WorkflowGen is configured to use WorkflowGen Applicative authentication or a custom authentication, you must remove the authentication module from the \auth\web.config file as follows:

For WorkflowGen Applicative authentication:

<location path="auth" inheritInChildApplications="false">
    <system.webServer>
        <modules>
            <remove name="ApplicationSecurityAuthenticationModule" />
        </modules>
    </system.webServer>
</location>

For Custom authentication:

<location path="auth" inheritInChildApplications="false">
    <system.webServer>
        <modules>
            <remove name="MyCustomAuthModule" />
        </modules>
    </system.webServer>
</location>

To enable WorkflowGen MCP Server:

1. In IIS, convert /wfgen/mcp to an application with a .NET 4 application pool using integrated pipeline mode.

2. Configure the MCP application in Anonymous authentication mode.

3. Before turning on MCP OAuth, confirm that WorkflowGen is configured with OIDC or SAML authentication. Other WorkflowGen authentication modes are not supported as MCP browser login sources.

4. Configure the MCP OAuth settings in the MCP Server section on the Integration tab in the WorkflowGen Administration Module Configuration panel, or set the same OAuthServer* and Mcp* keys directly in the WorkflowGen web.config file during scripted upgrades. Set OAuthServerEnabled=true only when the OIDC/SAML requirement is met; otherwise leave it set to false.

5. When manually merging web.config, make sure the parent \wfgen\web.config file contains the default <location path="mcp"> child-application exclusion that removes ApplicationSecurityAuthenticationModule.

6. Verify the MCP health endpoint: https://<workflowgen-url>/wfgen/mcp/health.

Restart the WorkflowGen server

Reboot your WorkflowGen web server.

New location of workflow application temporary and log files

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 and \wfgen\App_Data\LogFiles\XmlTrans