"End If" node on INACTIVE branch remains semi-active and output variable flow port remains active

Thanks for the clear description!

You’ve encountered a limitation that we internally track as AP-15115, which was marked as ‘WON’T DO.’ I will copy the comment from our internal Jira below. The main reason we decided not to fix it is due to concerns about backward compatibility.

  • We can’t simply “fix” it because it would cause a backward compatibility issue
  • End If, Case End, etc are “Inative Branch Consumers”, which by definition in the code can’t be inactive entirely. They can have individual outputs to be inactive (like in the screenshot) but they have no control over the mickey mouse ear
  • The fix in the workflow as per screenshot is simple: Have a variable extractor attached to the data output and link that to the nodes that should be set inactive (and which are currently connected to the mickey mouse ear)

Not sure what to do with this ticket. It’s partly confusing but it’s “as designed”. It can go into “OPEN” (won’t work on this unless <don’t know what needs to happen>), INVALID or WONTDO.

In the end (September '20) we then closed it as WONTDO.

3 Likes