Skip to content

@charleslevesque charleslevesque released this Mar 8, 2019

Portal

  • Bug (#2207): Fixed a file and content validation issue in the user view import function.

  • Bug (#2251): Fixed an erroneous title in the new request launch confirmation dialog in the homepage and main menu.

  • Bug (#2276): Fixed a JavaScript alert error in the advanced search gridview when grouping by the Created column.

  • Bug (#2291): Fixed an HTTP 500 error in the Quick Approval feature of the advanced search gridview when the action's form archive had a drop-down list form field that contained an apostrophe (') character in its value.

  • Bug (#2363): Fixed a visibility issue in the category group item in the menu process drop-down list.

Administration

  • Bug (#2348): Fixed an object reference error (since version 7.14.0) when replacing an existing process with an XPDL file via the import function.

Notes

  • All of the Node.js modules (GraphQL v1.1.1, Webhooks v3.4.1, Auth v1.0.0-beta.12, and SCIM v1.0.0-beta.3) now require Node.js version 8.11.3.

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Jan 11, 2019

Portal

  • Bug (#2144): Fixed a JavaScript error in the homepage Favorites list and in the New request page when the Quick View feature was disabled.

  • Bug (#1983): Fixed a login issue for non-managed Active Directory accounts when used with WorkflowGen applicative authentication.

Administration

  • Bug (#2062): Fixed a display issue in process template drop-down lists in the new process information form when WorkflowGen uses a custom application data path (web configuration parameter ApplicationDataPath).

  • Enhancement (#2054, #2006): Improved error message management for SQL query execution and Windows FIPS compliance errors.

Form designer

  • Bug (#2150): Added the missing default Empty section template for the English language.

Workflow Designer

  • Bug (#1996): Fixed an issue where action custom icon sizes (e.g. width and height) were not exported in the process definition XPDL.

Configuration panel

  • Enhancement (#2106): OpenID Connect authentication: Added a new option to enable silent session fresh using iframe (ApplicationSecurityAuthSessionRefreshEnableIFrame web configuration parameter).

    Notes:

    • If you are using AD FS authentication, some versions of AD FS do not support session refresh via an iframe. In this case, you can disable the silent session fresh using iframe option, which will then use a pop-up dialog instead.

    • When this option is enabled (default behavior), a hidden iframe will be used for the silent session refresh. Otherwise, a pop-up dialog will be used.

Auth v1.0.0-beta.12

  • Version update to 1.0.0-beta.12.

  • Enhancement (#2132, #2112): OpenID Connect authentication: Improved silent session refresh management.

  • Enhancement (#2097, #2107): OpenID Connect authentication: Support for a new silent session refresh mode that uses a pop-up dialog instead of an iframe.

  • Bug (#2111): Fixed some incorrect parameter names in the configuration files.

  • Bug (#2114): OpenID Connect authentication: Fixed a recurring authentication issue with Azure AD (v1 endpoint) when multiple accounts were previously used for login with the stay connected option.

WorkflowGen.My and WorkflowGen.My.Web.UI.WebControls

  • Version update to 4.4.0.

  • Bug (#2109): Fixed a webform submission issue in draft mode when some fields with validations (e.g. form level regular expression validations) contained invalid data.

  • Bug (#2138): Fixed a webform submission issue when a form contained two or more empty and required gridviews after calling the SaveFormData method in code behind.

Notes

  • All of the Node.js modules (GraphQL v1.1.1, Webhooks v3.4.1, Auth v1.0.0-beta.12, and SCIM v1.0.0-beta.3) now require Node.js version 8.11.3.

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Dec 5, 2018

WorkflowGen.My and WorkflowGen.My.Web.UI.WebControls

  • Version update to 4.3.0.

  • Bug (#2099): Fixed an issue in the WorkflowFileUpload web control where it would use the temporary filename of the file data's IN action parameter as the displayed attachment filename in the web form at runtime. (For example, a GUID would be displayed instead of the original filename when the file was previously uploaded via GraphQL or Webhooks using the multipart file upload feature.)

Notes

  • All of the Node.js modules (GraphQL v1.1.1, Webhooks v3.4.1, Auth v1.0.0-beta.9, and SCIM v1.0.0-beta.3) now require Node.js version 8.11.3.

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Nov 30, 2018

Configuration Panel

  • Change (#2089): The GraphQL and Webhooks Maximum input file size (kB) and Maximum input file content size (kB) fields on the Integration tab in the Configuration Panel now support numbers of up to 8 digits.

GraphQL v1.1.1

  • Version update to 1.1.1.

  • Bug (#2083): Fixed an issue in the multipart file upload feature (since version 7.14.0) where an uploaded file would incorrectly be reported as having exceeded the maximum input file size limit.

Webhooks v3.4.1

  • Version update to 3.4.1.

  • Bug (#2083): Fixed an issue in the multipart file upload feature (since version 7.14.0) where an uploaded file would incorrectly be reported as having exceeded the maximum input file size limit.

Notes

  • All of the Node.js modules (GraphQL v1.1.1, Webhooks v3.4.1, Auth v1.0.0-beta.9, and SCIM v1.0.0-beta.3) now require Node.js version 8.11.3.

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Nov 26, 2018

Portal

  • Bug (#2049): Fixed a SQL exception error that would be thrown in the advanced search supervisor mode when a data name filter contained an invalid data name value.

  • Bug (#2050): Fixed a SQL exception error that would be thrown in statistics data reports when the selected data name filter contained invalid data name values.

Directory synchronization service (WorkflowGenDirSyncService)

  • Bug (#2073): Fixed a regression issue (since version 7.10.0) that caused the synchronization connection to fail at the beginning in the directory synchronization Windows service with the Active Directory and LDAP connectors when the directory used a login configured with the password management mode in AES (FIPS compliant) or Version 5 (Legacy) with an Encryption key.

Notes

  • All of the Node.js modules (GraphQL v1.1.0, Webhooks v3.4.0, Auth v1.0.0-beta.9, and SCIM v1.0.0-beta.3) now require Node.js version 8.11.3.

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Nov 9, 2018

Important known issue

  • We have recently identified a regression bug (#2073) in this release that could affect the directory synchronization service with the Active Directory and LDAP connectors when the directory uses a login configured with AES (FIPS compliant) or Version 5 (Legacy) password management mode with an Encryption key.

    This known issue has been fixed in the latest release 7.14.1.

General

  • Bug (#1977): Fixed an issue related to file naming when downloading an attachment file from WorkflowGen.

Workflow engine service

  • Bug (#1984): Fixed an issue where the service would fail to start when the ApplicationUrl web configuration parameter contained a URI with the domain name only (e.g. https://domainname) without the webapp name like wfgen.

Remote approval service

  • Bug (#1948): Fixed an issue where some Label (SPAN) type form fields would not be pre-filled with the action's context data after the action completion.

Web services API

  • Bug (#1945, #1991): Fixed some issues with creating and deleting temporary files in the CompleteWebFormActivityInstance web method.

  • Bug (#2010): Fixed an issue in the CompleteWebFormActivityInstance web method where a form archive HTML file as IN parameter would not updated with the action's context data after the action's completion.

GraphQL v1.1.0

  • Version update to 1.1.0.

  • Feature (#1553, #1896): Added support for file uploads using multipart/form-data POST requests for the createRequest, updateRequestDataset, completeAction, and completeFormAction mutations.

  • Change / New behavior (#1756): Independent child requests (sub-process) would no longer be deleted after deleting their parent requests.

  • Bug (#1954): Fixed an issue where some queries and mutations would not raise an exception when accessing the API in delegation mode (OnBehalfOf) when the delegation feature was disabled.

  • Bug (#1945, #1991): Fixed some issues with creating and deleting temporary files in the completeFormAction mutation.

  • Bug (#2010): Fixed an issue in the completeFormAction mutation where a form archive HTML file as IN parameter would not updated with the action's context data after the action's completion.

Webhooks v3.4.0

  • Version update to 3.4.0.

  • Feature (#1553, #1902): Added support for file uploads using multipart/form-data POST requests for the createRequest, updateRequestDataset, completeAction, and completeFormAction operations.

  • Bug (#1945, #1991): Fixed some issues with creating and deleting temporary files in the completeFormAction operation.

  • Bug (#2010): Fixed an issue in the completeFormAction operation where a form archive HTML file as IN parameter would not updated with the action's context data after the action's completion.

Auth v1.0.0-beta.9

  • Version update to 1.0.0-beta.9.

  • Bug (#1994): Fixed an issue that would cause the /wfgen/auth Node.js authentication module to fail when the ApplicationUrl web configuration parameter ended with a slash (/).

SCIM v1.0.0-beta.3

  • Version update to 1.0.0-beta.3.

Notes

  • All of the Node.js modules (GraphQL v1.1.0, Webhooks v3.4.0, Auth v1.0.0-beta.9, and SCIM v1.0.0-beta.3) now require Node.js version 8.11.3.

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Oct 12, 2018 · 5 commits to master since this release

Important known issue

  • We have recently identified a regression bug (#2073) in this release that could affect the directory synchronization service with the Active Directory and LDAP connectors when the directory uses a login configured with AES (FIPS compliant) or Version 5 (Legacy) password management mode with an Encryption key.

    This known issue has been fixed in the latest release 7.14.1.

Workflow application

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

Auth v1.0.0-beta.8

  • Version update to 1.0.0-beta.8.

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

Notes

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

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2016/2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Oct 3, 2018 · 5 commits to master since this release

Important known issues

  • We have recently identified some regression bugs (#1950 and #2073) in this release that could affect the normal execution of workflow actions and the directory synchronization service with the Active Directory and LDAP connectors when the directory uses a login configured with AES (FIPS compliant) or Version 5 (Legacy) password management mode with an Encryption key.

    These known issues have already been fixed in the latest release 7.14.1.

General

  • Feature (#1911): Supports Okta identity provider as new authentication method with the OpenID Connect standard. See the WorkflowGen Technical Guide for information on how to configure this authentication method.

Portal

  • Bug (#1562): Fixed an issue in the delegate user name search containing accented characters in Internet Explorer 11.

  • Bug (#1641): Fixed a filename encoding issue when downloading an attachment file with spaces in its name from the runtime webform in Firefox.

Configuration panel

  • Feature (#1911): Added new Okta authentication mode. See the WorkflowGen Technical Guide for information on how to configure this authentication method.

Database

  • Performance (#1903): Removed duplicate NUM_WFPROCESS_INST index on WFPROCESS_INST table in MS SQL Server database.

    Note: You must run the Databases\MsSQLServer\Update_WFG-V7-13-0.sql upgrade script if your WorkflowGen is hosted on SQL Server.

GraphQL v1.0.0

  • Removed beta status in version 1.0.0.

  • Bug (#1929): Fixed a systematic exception error in the action.assignableUsers field when there were more than 100 users in the list result.

Auth v1.0.0-beta.7

  • Version update to 1.0.0-beta.7.

  • Feature (#1911): Added support for the Okta authentication provider.

Notes

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

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2016/2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Sep 24, 2018 · 5 commits to master since this release

Important known issues

  • We have recently identified some regression bugs (#1950 and #2073) in this release that could affect the normal execution of workflow actions and the directory synchronization service with the Active Directory and LDAP connectors when the directory uses a login configured with AES (FIPS compliant) or Version 5 (Legacy) password management mode with an Encryption key.

    These known issues have already been fixed in the latest release 7.14.1.

Portal

  • Bug (#1907): Fixed a sporadic System.OutOfMemoryException exception error that would be thrown when loading webforms containing list controls with databinding to global lists.

Notes

  • You must run the Databases\MsSQLServer\Update_WFG-V7-12-0.sql upgrade script if your WorkflowGen is hosted on SQL Server when upgrading from version 7.11.x or older. See the database changes in the release note of 7.12.0

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

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2016/2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5

@charleslevesque charleslevesque released this Sep 20, 2018 · 5 commits to master since this release

Important known issues

  • We have recently identified some regression bugs (#1907, #1950 and #2073) in this release that could affect the normal execution of workflow actions and the directory synchronization service with the Active Directory and LDAP connectors when the directory uses a login configured with AES (FIPS compliant) or Version 5 (Legacy) password management mode with an Encryption key.

    These known issues have already been fixed in the latest release 7.14.1.

Portal

  • Bug (#1883): Added a missing logout button in the portal navigation bar when configured with the AD FS authentication mode.

Configuration panel

  • Bug (#1835): Added support for the hyphen character (-) in the SMTP username input field.

Workflow engine

  • Bug (#1895): Fixed a regression issue that was introduced in version 7.12.0 where a data containing a null value would cause a workflow exception when used as a IN action parameter at runtime (related to #1489).

GraphQL v1.0.0-beta.8

  • Version update to 1.0.0-beta.8

Webhooks v3.3.1

  • Version update to 3.3.1

Notes

  • You must run the Databases\MsSQLServer\Update_WFG-V7-12-0.sql upgrade script if your WorkflowGen is hosted on SQL Server when upgrading from version 7.11.x or older. See the database changes in the release note of 7.12.0

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

  • Running the npm install --production command is required on each of the modules (\wfgen\graphql, \wfgen\hooks, \wfgen\auth, and \wfgen\scim) after the upgrade.

Reminders

  • Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0. We recommend migrating to Windows Server 2012 or later.

  • Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0. While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided.

    For clients currently hosting WorkflowGen on a database server older than MS SQL 2012 or Oracle 12c, we highly recommend upgrading to MS SQL server 2016/2017 or Oracle 12c for the best performance and to support JSON native data fields that will used in future WorkflowGen releases.

Assets 5
You can’t perform that action at this time.