/
Known Issues

Known Issues

Owned by wiki
Last updated: Oct 26, 2023
9 min read

This list include an overview about known issues of the FLOWSTER Studio Version 5.3.1 / 5.3.2

Issue:

Connection to imap mailboxes via TLS1.2 is not possible.

Solution:

works only for Flowster Studio 5.3.2

  1. Download the new Activity:

2. Replace the file in the central activity stor

3. Restart the execution Agent

4. Start the Designer as Admin and activate the activity library synchronisation

Status:

solved - with with 5.4 (planned for autum 2023)

Issue:

MS Azure user get an error when they try to access Workflows on the Flowster Portal and can’t see Categories and Workflows.

Status:

solved - with with 5.4 (planned for autum 2023)

Issue:

The Output of the HTML Editor still include the variable names and not the values.

Solution:

works only for Flowster Studio 5.3.2

  1. Download the new Activity:

2. Replace the file in the central activity store

3. Restart the execution Agent

4. Start the Designer as Admin and activate the activity library synchronisation

Status:

solved - with with 5.4 (planned for autum 2023)

Issue:

The Powershell activity doesn’t, if they is located in a snippet workflow.

Solution:

Setup the central storage path of the tenant under Administrator → Settings → Manage Tenants → Select your tenant → select the Tab Central storage path and set a valid path

Status:

solved - with with 5.4 (planned for autum 2023)

Issue:

The Powershell activity is not working with scripts of over 200 lines of code. Scripts with more line of code will not work and the powershell helper process won’t terminate. The Workflow will stay in idle.

Solution:

Use the activity library and common dll of 5.3 or split the powershell scripts.

Status:

open - fix planned for June

Issue:

The Powershell activity doesn’t work anymore, by execution in the Designer. Activity return “Object reference not set to an instance of an object”.

Solution:

Execute Workflow on an execution agent.

Status:

open - fix planned for autum 2022

Issue:

Global variables of type binary shows always „no file selected“ instead of the uploaded file.

Status:

open - fix planned for autum 2022

Issue:

Workflows with active fallback flag won’t be executed by the scheduler, even if the execution agent is still available.

Status:

open - fix planned for autum 2022

Issue:

The import of workflow categories via the Administrator is not working, when windows authentication is activated. The user will see the Import workflow loader, but it doesn’t load and the import doesn’t happen.

Status:

open - fix planned for autum 2022

Issue:

The list view object shows „field is required“ message, even if all entries are selected by the „select all“ function, but the workflow can be executed.

Status:

open - fix planned for autum 2022

Issue:

Object selector dependencies are not working well on approval forms.

Status:

open - fix planned for autum 2022

Issue:

The loading of the scheduling area on the portal and administrator is slow, if many Workflows are scheduled on the whole system.

Status:

open - fix planned for autum 2022

Issue:

The loading of the Workflowarea on the portal is slow with normal users.

Status:

open - fix planned for autum 2022

Issue:

Empty parameter group pages are visible on workflow forms.

Status:

done - solved with 5.3.2

Issue:

Workflows can’t be started anymore, if the workflow form include a combobox of type list view as optinal parameter and the user doesn’t select a value.

Status:

done - solved with 5.3.2

 

This list include an overview about known issues of the FLOWSTER Studio Version 5.3.

Issue:

Global variables of type binary shows always „no file selected“ instead of the uploaded file.

Status:

open - fix planned for autum 2022

Issue:

Workflows with active fallback flag won’t be executed by the scheduler, even if the execution agent is still available.

Status:

open - fix planned for autum 2022

Issue:

The import of workflow categories via the Administrator is not working, when windows authentication is activated. The user will see the Import workflow loader, but it doesn’t load and the import doesn’t happen.

Status:

open - fix planned for autum 2022

Issue:

The list view object shows „field is required“ message, even if all entries are selected by the „select all“ function, but the workflow can be executed.

Status:

open - fix planned for autum 2022

Issue:

Object selector dependencies are not working well on approval forms.

Status:

open - fix planned for autum 2022

Issue:

The loading of the scheduling area on the portal and administrator is slow, if many Workflows are scheduled on the whole system.

Status:

open - fix planned for autum 2022

Issue:

The loading of the Workflowarea on the portal is slow with normal users.

Status:

open - fix planned for autum 2022

Issue:

The powershell script of a parameter in the edit parameter editor will be set to an old state, when you start to add a parameter dependency variable to your script.

Status:

done - solved with 5.3.1

Issue:

Parameters of type integer, on a workflow form, must always have a numeric value, even if they are optional.

Status:

done - solved with 5.3.2

Issue:

Ordering of parameters in an approval form is not possible and doesn’t match the order of the start form

Status:

done - solved with 5.3.1

Issue:

The last entry of the grid value will include all entries of the grid, if the grid is used in an approval process.

Status:

done - solved with 5.3.1

Issue:

The HTML Composer activity incorrectly resolves variables with equal parts of names.
Example:

  1. ${using:flowster} = Demo

  2. ${using:flowsterID} = 12234

  3. ${using:flowsterName} = Testing

Result:

  1. demo

  2. demoID

  3. demoName

Status:

done - solved with 5.3.1

Issue:

The main workflow doesn’t abort, if it include a snippet, which extecute the activity Terminate workflow and the start snipper condition stop on error = true.

Status:

done - solved with 5.3.1

Solution:

Use the throw activity in the snippet instead. This will throw an unhandled exception, which can be handeled by a seperate try catch in the main workflow, if needed.

Issue:

Workflows can’t show the output of the central storage path activities on the portal, if they are used in snippets. The activities are working only in main workflows.

Status:

done - solved with 5.3.1

Issue:

it can happen, that workflow forms with multiple parameter groups and visibility expressions have problems with the loading and displaying of a parameter group. The selected parameter group will be empty, but the parameters are visible, when you switch back to the parameter group before and back again.

Status:

done - solved with 5.3.1

Issue:

The MS Powershell process doesn’t detect user permission changes, if there was still a remote session before with the same user to a different server and the user got new permissions after.

Status:

done - solved with 5.3.1
Solution:

Restart the execution agent.

Issue:

Courser navigation in input fields is not possible, because the focus switch always to the navbar on the portal.

Status:

done - solved with 5.3.1

Issue:

It’s not possible to see the currently assigned certificate of a flowster component via the platform status.

Status:

done - solved with 5.3.1

Issue:

It is not possible to add a flowster administrative role, which is a subrole, to a global variable folder as permission.

Status:

done - solved with 5.3.1

Issue:

A user have administrative permissions in selected workflow categories and normal user permissions in different workflow categories for selected workflows. But the user can see all workflows of the categories where he have only normal user right and not only the selected once.

Status:

done - solved with 5.3.1

Issue:

Recurrent scheduled workflows will be executed more times as expected, if the executen agent was down during the planned execution time and the fallback flag was set to true. In this case, the system catches up not only one execution, but all missed executions.

Status:

done - solved with 5.3.1

Issue:

The scheduling accept form for activate / deactivate shows the message always in english, even if german language is set.

Status:

done - solved with 5.3.1

Issue:

Recurrent scheduled workflows will be executed more times as expected, if the executen agent was down during the planned execution time and the fallback flag was set to true. In this case, the system catches up not only one execution, but all missed executions.

Status:

done - solved with 5.3.1

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:

done - solved with 5.3.1

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:

The scheduling pdf report doesn’t show the workflow parameters correctly, if the parameter include long values.

Status:

done - solved with 5.3.1

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:

done - solved with 5.3.1

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:

It may happen that the postgre sql query activity cannot execute a query because the database takes longer to connect.

Status:

done - solved with 5.3.1

Issue:

Automatic log cleaning function throw error messages in platform logs, if no log entry needs to be cleared.

Status:

done - solved with 5.3.1

Issue:

The workflow form summary page doesn’t appear and the workflow starts diretcly, if the workflow form include many parameters.

Status:

done - solved with 5.3.1

Issue:

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

 

Status:

done - solved with 5.3.1

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:

done - solved with 5.3.1

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”, if the workflow is member of a subcategory.

Status:

done - solved with 5.3.1

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:

done - solved with 5.3.1

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:

done - solved with 5.3.1

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:

done - solved with 5.3.1

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:

done - solved with 5.3.1

Related content