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