This list include an overview about known issues of the FLOWSTER Studio Version 5.3.1 / 5.3.2
| Expand |
|---|
| title | [open - fix solved - with with 5.4 (planned for autum 20222023)] 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 |
Download the new Activity:
| View file |
|---|
| name | FoundMediaSoftware.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: open - fix solved - with with 5.4 (planned for autum 20222023) |
| Expand |
|---|
| title | [open - fix solved - with with 5.4 (planned for autum 20222023)] 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: open - fix solved - with with 5.4 (planned for autum 20222023) |
| Expand |
|---|
| title | [open - fix solved - with with 5.4 (planned for autum 20222023)] 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 |
Download the new Activity:
| View file |
|---|
| name | FoundMediaSoftware.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: open - fix solved - with with 5.4 (planned for autum 20222023) |
| Expand |
|---|
| title | [open - fix solved - with with 5.4 (planned for autum 20222023)] 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: open - fix solved - with with 5.4 (planned for autum 20222023) |
| Expand |
|---|
| title | [done - 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 | [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: ${using:flowster} = Demo ${using:flowsterID} = 12234 ${using:flowsterName} = Testing
Result: demo demoID 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:
ChangeActiveWorkflowTimestamp() on n.n.n.n with guid nnnnn for tenant 1 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. |
...