Known Issues

Issue:

If the infrastructure is separated with different Execution Agent groups, explicit Execution Group assignments of persisted workflows are not taken into account. In this case, the workflow is continued by the next best Execution Agent from the entire pool.

Status:

open

Issue:

It can happen that AD users with special dialect characters in their display name receive an error message when logging in to the portal and cannot log in.

Status:

solved - with with 5.5.0

Issue:

SSH Connection throw the error:

Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified.

Status:

solved - Hotfix available in the customer portal

Issue:

Parameters on workflow forms that have one or more parameters with a dependency on a checkbox are not loaded when the form is opened, as the dependency on the checkbox is not checked when the form is loaded. The check only takes place when the user selects the checkbox.

Status:

solved - with with 5.5.0

Issue:

The gloable "Is Persistable" flag is not automatically activated after checking in a workflow if it contains activities that require persistence. However, the workflow is still persisted if an activity requires this.

Status:

solved - with with 5.5.0

Issue:

The dropdown field in a grid, use the value from the field before, if a new row were added and no value were selected in the dropdown.

Workarround:

Show at first entry in the dropdown “Select a value”, so that the user will be forced to select a specific value from the dropdown.

Status:

solved - with with 5.5.0

Issue:

The summray shows an additional column form the second added line of the grid, which doesn't exist originally in the grid.

Hint:

This is only a visual issue.

Status:

solved - with with 5.5.0

Issue:

Persisted workflows stayed in status stopping, if a user had tried to stop them.

Status:

solved - with with 5.4.5

Issue:

The Terminate hanging Workflows function of the Scheduler had, in specific sce-narios, terminated persisted workflows as well.

Status:

solved - with with 5.4.4

Issue:

The authentication with the depricated api were not working anymore.

Status:

solved - with with 5.4.3

Issue:

Resuming of Workflows with Entra ID Accounts doesn’t work, if the Workflow were started by a different user

Status:

solved - with with 5.4.3

Issue:

Difficult to identify Entra ID Groups in the security area, when multiple Enta ID providers are setup, because only the groupname is visible in the security configuration.

Status:

solved - with with 5.4.3

Issue:

Persisted workflows get terminated on slower systemes, which have activated the terminate hanging workflows feature for the execution agent.

Status:

solved - with with 5.4.2

Issue:

Workflows with include wait for more input without delay value can’t be started anymore, because the delay parameter is required.

Status:

solved - with with 5.4.2

Issue:

The restapi methode resume workflow return an error since the update and expect more information.

Status:

solved - with with 5.4.2

Issue:

Persisted approval workflows, started with an earlier version, are not visible in the inbox anymore, after the update to 5.4

Status:

solved - with with 5.4.1 (Beta version)

Issue:

The Super Admin gets error messages on the flowster portal, after the update to 5.4, when he has already persisted workflows from an earlier version.

Status:

solved - with with 5.4.1 (Beta version)

Issue:

It’s not possible to use the update workflow list function on the flowster portal.

Solution:

Go to Administrator → Settings → Portal Appearance and change the width value from 20% to 16% for the class .navbar-inverse ul.nav li

Status:

solved - with with 5.4.1 (Beta version)

Issue:

Azure Users can’t login, if an azure group is used of a differend type than security is used and if the provider app and display name is differend as azure.

Status:

solved - with with 5.4.1 (Beta version)

Issue:

Portal user do not have access to all permitted workflow categories.

Status:

solved - with with 5.4.1 (Beta version)

Issue:

In case of hardening, is it not possible to use a unencrypted connection to a ldap server.

Status:

solved - with with 5.4.1 (Beta version)

Issue:

The workflow search on portal can't find all permitted workflows.

Status:

solved - with with 5.4.1 (Beta version)

Issue:

The main workflow doesn’t resume, if snippet workflow is completed.

Status:

solved - with with 5.4.1 (Beta version)

Issue:

Wait for more input requests stay in idle and doesn’t resume the wf, on resume event.

Status:

solved - with with 5.4.1 (Beta version)

Issue:

Tenant managers, which got permissions by an ad group, can’t access the tenant management area.

Status:

solved - with with 5.4.1 (Beta version)