This section contains instructions for clients upgrading from versions 7.22.15 and earlier. Follow the instructions in this section, then return to the to complete the procedure.
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 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.
You must remove the xmlns attribute from the web configuration file regardless of the version from which you're upgrading. See for instructions on how to do this.
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.
The first number in the PortalFrameSetHeight value is the height of the banner. If your website is configured to display a banner, enter its height in pixels here. The other default values should not be changed.
The ApplicationSmtpDeliveryMethod parameter defines the notification delivery method. By default, it uses the SMTP server, but you can change the SMTP delivery method to Pickup directory in the Administration Module Configuration Panel.
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:
<add key="SendHttpPostLogLevel" value="n" />
When upgrading from version 6.6.0 and earlier
Remove the following deprecated parameters from <appSettings>:
As of WorkflowGen 7.22.0, the log level values for the existing GETUSERSFROMDIR, MERGEFORM, SENDHTTPPOST, and RESTAPICLIENT workflow applications have changed to 0 for no logs (default), 2 for information, and 3 for debugging. You can set (or reset) the log levels by updating the values of the following parameters accordingly:
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:
Oracle database is no longer supported as of WorkflowGen 7.16.0.
MS SQL Server
For versions 5.1.9 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-2-0.sql database update script in your SQL Server Management Studio tool.
For versions 5.2.x and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-3-0.sql database update script in your SQL Server Management Studio tool.
For versions 5.3.x, 5.4.0 (alpha, beta 1 and beta 2) and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-4-0.sql database update script in your SQL Server Management Studio tool.
For versions 5.4.x official and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-0.sql database update script in your SQL Server Management Studio tool.
For versions 5.5.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-1.sqldatabase update script in your SQL Server Management Studio tool.
For versions 5.5.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-2.sql database update script in your SQL Server Management Studio tool.
For versions 5.5.4 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-5-5.sql database update script in your SQL Server Management Studio tool.
For versions 5.5.5 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-0.sql database update script in your SQL Server Management Studio tool.
For versions 5.6.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-2.sql database update script in your SQL Server Management Studio tool.
For versions 5.6.2 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-3.sql database update script in your SQL Server Management Studio tool.
For versions 5.6.3 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-6-4.sql database update script in your SQL Server Management Studio tool.
For versions 5.7.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-7-1.sql database update script in your SQL Server Management Studio tool.
For versions 5.7.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V5-7-2.sql database update script in your SQL Server Management Studio tool.
For versions 5.7.4 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V6-0-0.sql database update script in your SQL Server Management Studio tool.
For versions 6.0.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V6-1-0.sql database update script in your SQL Server Management Studio tool.
For versions 6.1.2 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V6-1-3.sql database update script in your SQL Server Management Studio tool.
For versions 6.1.3 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V6-1-4.sql database update script in your SQL Server Management Studio tool.
For versions 6.1.6 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V6-2-0.sql database update script in your SQL Server Management Studio tool.
For versions 6.4.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V6-5-0.sql database update script in your SQL Server Management Studio tool.
For versions 6.5.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V6-6-0.sql database update script in your SQL Server Management Studio tool.
For versions 6.6.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-0-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.1.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-1-1.sql database update script in your SQL Server Management Studio tool.
For versions 7.1.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-2-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.2.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-3-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.5.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-6-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.9.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-10-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.10.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-11-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.11.2 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-12-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.12.2 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-13-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.13.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-14-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.14.7 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-15-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.15.1 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-15-2.sql database update script in your SQL Server Management Studio tool.
For versions 7.15.5 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-16-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.16.5 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-17-0.sql database update script in your SQL Server Management Studio tool.
For versions 7.21.0 and earlier
Launch the Update\Databases\MsSQLServer\Update_WFG-V7-22-0.sql database update script in your SQL Server Management Studio tool.
For all 7.x.x and earlier versions
Launch the Update\Databases\MsSQLServer\Update_WFG-V8-0-0.sql database update script in your SQL Server Management Studio tool.
Update the Directory Synchronization configuration file
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:
Update the WorkflowGen Engine Service configuration file
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.
WorkflowGen.My and WorkflowGen.My.Web.UI.WebControls (WorkflowFileUpload) version 3.0 or later are required in all your Visual Studio Web Forms if the ApplicationSecurityEnableWebAppsSecureMode security feature is enabled. For more information, see the WorkflowGen Knowledge Base article.
If you're using folders for GraphQL and/or incoming webhooks file operations (such as sending a file action parameter), you must update the values of the GraphqlInputFileAllowedFolders and HooksInputFileAllowedFolders parameters. See the and sections in the for more information.
If you're using HTTP URLs for GraphQL and/or incoming webhooks file operations (such as sending a file action parameter), you must update the values of the GraphqlInputFileAllowedHttpUrls and HooksInputFileAllowedHttpUrls parameters. See the and sections in the for more information.
As of version 7.15.5, the optional BACKURL_SUBMIT and BACKURL_CANCEL HTTP parameters used in custom WorkflowGen URLs (for example, ) 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').
If you want to configure CORS to allow GraphQL API access from a third-party application, you must now follow the instructions in the section in the .
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.