Known Issues

Issue:

Administrative user with permissions bases on a admin permission template can’t activate / deactivate a workflow timestamp in the administrator.

Status:

in progress

Errormessages:

The Platformlog include following error message:

1.  ChangeActiveWorkflowTimestamp() on n.n.n.n with guid nnnnn for tenant 1

2. Exception: System.InvalidOperationException: The instance of entity type WfTimestamp cannot be tracked because another instance with the same key value for {Id} is already being tracked. When attaching existing entities, ensure that only one entity instance with a given key value is attached. Consider using DbContextOptionsBuilder.EnableSensitiveDataLogging to see the conflicting key values. StackTrace: at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.IdentityMap`1.ThrowIdentityConflict(InternalEntityEntry entry) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.IdentityMap`1.Add(TKey key, InternalEntityEntry entry, Boolean updateDuplicate) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.StartTracking(InternalEntityEntry entry) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.InternalEntityEntry.SetEntityState(EntityState oldState, EntityState newState, Boolean acceptChanges) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.EntityGraphAttacher.PaintAction(EntityEntryGraphNode node, Boolean force) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.EntityEntryGraphIterator.TraverseGraph[TState](EntityEntryGraphNode node, TState state, Func`3 handleNode) at Microsoft.EntityFrameworkCore.DbContext.SetEntityState[TEntity](TEntity entity, EntityState entityState) at FMS.Flowster.WFManagementService.WFManagementService.ChangeActiveWorkflowTimestamp(String workflowSource, Int32 timestampId, Int32 displayNameId, Boolean isDefault) in C:\Users\stoehr\Source\Repos\Flowster Studio\vNext\RestApi\WFManagementService\WFManagementService.cs:line 5962

Issue:

The workflow version and comment dialog, is not displayed during workflow check-in. This means that the workflow is not saved to the database.

Status:

in Progress

Solution:

This error occurs when the workflow tree is reloaded in Designer and the tree has not been reopened to the current workflow timestamp. If you reopen the workflow tree to the current workflow timestamp after reloading, the check-in will work as usual.

Issue:

Workflow form link shows “no active timestamp available”

Status:

open

Errormessages:

Issue:

The User displayname is not updated in flowster, if the name has changed in the active directory and the have permissions to access the portal via a group and is not directly assigned.

Status:

open

Issue:

Azure AD users with Flowster Portal permissions via an azure ad group, can’t login to the portal-

The users needs to be diretcly assigned.

Status:

open

Issue:

A different timestamp should be assigned to an existing scheduled workflow. The assignement will be done and correctly displayed on the scheudling page, but the execution logs shows an execution of the previous scheduled workflow.

The scheduling needs to be removed and created again with the needed timestamp.

Status:

open

Issue:

Workflows with a custom gui configuration in the parameter configuration needs to go into the custom gui editor and click on save, after they changed the parameter setup.

Status:

open