FlowDecision outputs

Feedback Studio
, ,
1

I absolutely Hate the update to the FlowDecision True/False outputs. Recently updated to Studio 2024.10.5 and the FlowDecision allows you to put anything anywhere… So when opening an older project in new studio it many times wires an input and output to the same node! In addition the True/False nodes can be anywhere. Fine, IF you give us the ability to reverse T/F… Now It appears that it wires the first output as true even when dragged from the legacy False node on the right.
Flexibility is good, BUT ONLY when you have full flexibility not this.

3

Hi @FL.Duck

Would it be possible to exemplify this with some screenshots? :slight_smile:

4

Drag the activity onto an existing line.

image
image269×371 14.1 KB

Just tried to add a second line out and it showed up as True also!

A flowchart depicting a decision-making process where opening the LoanVision web page leads to exporting all companies based on a condition that results in true. (Captioned by AI)
A flowchart depicting a decision-making process where opening the LoanVision web page leads to exporting all companies based on a condition that results in true. (Captioned by AI)356×381 16.1 KB

Copy/paste the first activity, delete the first, attach new activity below the previous step. all good, then now matter what the first line out is always True. (Previously the left was true and right was false.

image
image373×373 16.1 KB

Attampted to make a second line out and when I click the activity on the yellow, or anywhere, it doesn’t allow a second line out… as below. So I try to do this with a third activity and hope this one works in some functional manner.

image
image319×377 15.2 KB

The Studio UI is extremely unreliable with FlowDecisions… The whole First line out is always the True is a pain… sometime won’t let me move the node it’s attached to so I delete the activity and start over. NEEDs the ability to swap the True/False outputs as other development tools does. Having the activity work at all is trial/error retry in almost every case.

5

Having some problem with FlowDecision in my test ladscape also. Try the attached XAML.
No idea how I achieved it :frowning: By deleting/adding the FD it starts working as expected…

A workflow diagram with a flow decision connected to two "Write Line" activities, and an error message stating, "Connection can only be from True or False branch." (Captioned by AI)
A workflow diagram with a flow decision connected to two "Write Line" activities, and an error message stating, "Connection can only be from True or False branch." (Captioned by AI)468×495 10.1 KB

Flowchart.xaml (6.7 KB)

Cheers

P.S. After “Auto arrange” there apeared small triangle not visible before. It is probably an orphan connection causing this problem…

image
image465×157 6.29 KB

P.P.S It seems to be actually a connection from FD to itself, occupying the “True” connection. I suppose connection to itself should be prohibited.

1 Like
6

Hi @FL.Duck check version you are using because i have just checked in my studio its getting me correct i am using studio version 2024.10.6

The image depicts a flowchart with a flow decision element leading to two assign operations, depending on the true or false outcome. (Captioned by AI)
The image depicts a flowchart with a flow decision element leading to two assign operations, depending on the true or false outcome. (Captioned by AI)967×456 14.2 KB

Thanks

7

Also interesting :slight_smile:

The image depicts a flowchart with a decision point labeled "Flow Decision," where both the True paths lead to "Write Line" actions. (Captioned by AI)
The image depicts a flowchart with a decision point labeled "Flow Decision," where both the True paths lead to "Write Line" actions. (Captioned by AI)572×421 10.1 KB

Flowchart2.xaml (6.8 KB)

But after reopenning it looks like this

This image depicts a flowchart with a flow decision branching into two paths labeled "True" and "False," each leading to separate "Write Line" actions. (Captioned by AI)
This image depicts a flowchart with a flow decision branching into two paths labeled "True" and "False," each leading to separate "Write Line" actions. (Captioned by AI)493×379 8.05 KB

Cheers

9

Seems the problem hapens when you drop FD at existing link between two activities.
In such case you could draw a connection from already occupied FD terminator.

The image depicts a flowchart with a decision point that branches into two "Write Line" actions based on the outcome of the decision. (Captioned by AI)
The image depicts a flowchart with a decision point that branches into two "Write Line" actions based on the outcome of the decision. (Captioned by AI)499×241 10.8 KB

10

Hi everyone,

Thank you for the feedback here. We’re currently looking into the issues mentioned here. However, I was interested to learn more on how you’d like to use the swap between outputs. Is this for having a False branch only or are there other use cases?

Many thanks,
Raluca

11

There’s times where I’m trying to have the flowchart resemble the requirements doc. This can result in using NOT in the condition so that I don’t have too many lines crossing over each other. I also have times I want to have multiple FD point the false node to the same error handling/notification routine so I’m not duplicating code. The best reasoning is so that the flow matches the requirements and I can minimize the conditions that have NOT in them. It’s sometimes easier to test for a negative.