WorkflowGen 7.15.2

Portal

  • Bug (#2424): Fixed an issue where a supervisor had the rights to cancel a specific process request even when the supervisor process participant Cancel requests permission was disabled.

  • Bug (#2605): Fixed an issue where a cancelled action would store the delegatee as the aborted user instead of the actual user (delegator) in delegation mode.

  • Bug (#2612): Fixed an issue where users could not access requests containing one or more actions that they cancelled previously.

Notifications

  • Enhancement (#2433): Request data numeric values are now always formatted in text using a language culture in email notifications.

  • Enhancement, Change (#2646): Macro datetime values are now displayed in the user’s timezone instead of UTC in email notifications.

    Notes:

    • All datetime macros with undefined values are now displayed in empty text.
    • The WF_SYSTEM_DATE macro value is now displayed in date format without the time information.
    • The WF_SYSTEM_TIME macro value is now displayed in time format without the date information.

Web services API

  • Enhancement (#2433): Request data numeric values are now always formatted in text using a language culture in the web method XML response.

GraphQL

  • Enhancement (#2616): Apply consistent requests and actions user access security check in all queries and mutations.

  • Bug (#2608): Fixed an issue where a delegatee could cancel another request of their delegator where the specific request was not intentionally delegated to them in delegation mode.

  • Bug (#2610): Fixed an issue where a delegatee could not access a request of their delegator in delegation mode.

  • Bug (#2624): Fixed an issue where a standard user was able to create a new request in test mode.

Webhooks

  • Enhancement (#2611): Added support for the new args.onBehalfOfUserName parameter for operations in delegation mode.

  • Enhancement (#2616): Apply consistent requests and actions user access security check in all queries and mutations.

  • Bug (#2608): Fixed an issue where a delegatee could cancel another request of their delegator where the specific request was not intentionally delegated to them in delegation mode.

  • Bug (#2610): Fixed an issue where a delegatee could not access a request of their delegator in delegation mode.

  • Bug (#2624): Fixed an issue where a standard user was able to create a new request in test mode.

Database

  • Performance (#1922): Added some new indexes on datetime columns for request and action tables.

  • Enhancement (#2541, #2618): Improved some table columns’ schemas for not null values.

Upgrade scripts

  • Change (#2598): All alter table column queries now use SQL_Latin1_General_CP1_CI_AS collation for SQL Server in our database upgrade scripts.

Notes

  • All of the Node.js modules (GraphQL v2.0.1, Webhooks v4.0.1, Auth v1.0.0, and SCIM v1.0.0) now require Node.js version 10.15.3 LTS.

  • 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 Server 2012, we highly recommend upgrading to MS SQL Server 2017 or 2019 for the best performance.

Installation Packs

WorkflowGen 7.15.2 (Upgrade)
WorkflowGen 7.15.2 (Clean Install - PowerShell)
WorkflowGen 7.15.2 (Clean Install - manual)
WorkflowGen.My

Documentation

WorkflowGen 7.15.2 Upgrade Guide
WorkflowGen 7.15.2 Technical Guide
WorkflowGen 7.15.2 Administration Guide
WorkflowGen 7.15.2 User Portal Guide
WorkflowGen 7.15.2 Integration Guide

We have just upgraded to 7.15.2 but we now get the following error when trying to export a process:
Cannot resolve the collation conflict between “Latin1_General_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the UNION operation.

Hello David,

You need to set your database collation as SQL_Latin1_General_CP1_CI_AS, you can follow the following procedure:

We just followed this procedure to change the collation but we still get the same error when trying to export a process.

You need to identify columns which provide the error and change the collation for these columns.

You can execute the following request to identify columns:

DECLARE @DatabaseCollation VARCHAR(100) = 'SQL_Latin1_General_CP1_CI_AS'

SELECT 
    t.Name 'Table Name',
    c.name 'Col Name',
    c.collation_name
FROM 
    sys.columns c 
INNER JOIN 
    sys.tables t ON c.object_id = t.object_id
INNER JOIN 
    sys.types ty ON c.system_type_id = ty.system_type_id    
WHERE 
    t.is_ms_shipped = 0
    AND 
    c.collation_name <> @DatabaseCollation