Versions Compared

Version Old Version 20 New Version Current
Changes made by

wiki

wiki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Expand
title[solved - with with 5.4 (planned for autum 2023)] Connect to Mailbox doesn't work for secure connections with TLS1.2

Issue:

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

Solution:

Info

works only for Flowster Studio 5.3.2

  1. Download the new Activity:

View file
nameFoundMediaSoftware.Flowster.ActivityLibrary.Mail.dll

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)

Expand
title[solved - with with 5.4 (planned for autum 2023)] MS Azure User can't access Workflows on the Portal

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)

Expand
title[solved - with with 5.4 (planned for autum 2023)] HTML Editor doesn't resolve variables

Issue:

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

Solution:

Info

works only for Flowster Studio 5.3.2

  1. Download the new Activity:

View file
nameFoundMediaSoftware.Flowster.ActivityLibrary.Communication.dll

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)

Expand
title[solved - with with 5.4 (planned for autum 2023)] Powershell Activity doesn't work in Snippets

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)

Expand
title[open - fix planned for Junedone - solved with 5.3.2] Powershell Activity doesn't work with scripts which include more as 200 lines of code

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

Expand
title[open - fix planned for sommer autum 2022] Powershell Activity doesn't work in Designer

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Global variables of type binary shows always no file selected

Issue:

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

Status:

open - fix planned for sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Workflow scheduler fallback function is not working

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Administrator - Import Wokrflow Category is not working with windows authentication

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] List view shows warning, if select all was selected

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Object Selector dependency is not working on approval forms

Issue:

Object selector dependencies are not working well on approval forms.

Status:

open - fix planned for sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] The loading of the scheduling area takes long, if many Workflows are scheduled

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Workflows and Categories load slow on portal

Issue:

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

Status:

open - fix planned for sommer autum 2022

Expand
title[ open - fix planned Junedone - solved with 5.3.2] Empty Parameter groups are visible

Issue:

Empty parameter group pages are visible on workflow forms.

Status:open

- fix planned for Junedone - solved with 5.3.2

Expand
title[open - fix planned for Junedone - solved with 5.3.2] Workflow can't be executed, of no value was selected in a combobox of type listview

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:open

- fix planned for Junedone - solved with 5.3.2

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

Expand
title[open - fix planned for sommer autum 2022] Global variables of type binary shows always no file selected

Issue:

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

Status:

open - fix planned for sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Workflow scheduler fallback function is not working

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Administrator - Import Wokrflow Category is not working with windows authentication

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] List view shows warning, if select all was selected

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Object Selector dependency is not working on approval forms

Issue:

Object selector dependencies are not working well on approval forms.

Status:

open - fix planned for sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] The loading of the scheduling area takes long, if many Workflows are scheduled

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 sommer autum 2022

Expand
title[open - fix planned for sommer autum 2022] Workflows and Categories load slow on portal

Issue:

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

Status:

open - fix planned for sommer autum 2022

Expand
title[done - solved with 5.3.1] Edit Parameters - Powershell Script will be reset, by insert of a dependency

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

Expand
title[open - fix planned for sommer 2022done - solved with 5.3.2] Parameters of type interger must never be empty

Issue:

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

Status:open

- fix planned for sommer 2022done - solved with 5.3.2

Expand
title[done - solved with 5.3.1] Parameter order in an approval form does not match the start form

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

...

Expand
title[done - solved with 5.3.1] The activity HTML Composer incorrectly resolves variables with equal parts of names

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

...

Expand
title[done - solved with 5.3.1] Administrative user can't activate / deactivate a workflow timestamp

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

Expand
title[done - solved with 5.3.1] Workflow check-in via the designer is not successfull

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.

...