IF workflows: not saving dependencies and not propagating fails

[Carsten Schmitz]

Hi,

I've just filed a ticket on IF workflows in 12.3.

While the "Time & Dependencies" pane is displayed for the "diamond" at the end, and one can set dependencies on the objects within the "if" workflow there (such as "if task #2 is ENDED_NOT_OK, then block), these changes are not saved. And that's even though it displays a green box saying "changes saved successfully". The next time you open the object again, the tables is once void of any changes.

Additionally, I can not find any way to have an IF workflow go to ENDED_NOT_OK if one of it's contained items fails. E.g. if item #2 in the "true" branch is ENDED_NOT_OK, and item #3 has an "if item #2 is ENDED_NOT_OK, then abort" clause, the entire IF workflow is still marked "ENDED_OK" in the end, no matter what, which I think this is wrong, too?

If anyone has additional input on this, please share.

​​​​

[Carsten Schmitz]

This has been confirmed as a bug and will be passed to development.

Thus, it appears IF workflows are currently unusable if you want any degree of error testing (unless, possibly, one fiddles with script and PSET, which we didn't).

Kudos to Automic support for this one, this has been the first support case in a very long time that I can say I am happy with. We received a speedy acknowledgement as a bug, courtesy of the engineer testing this against the old Java client where the functionality works.

That such rather basic issues exists in the first place is less thrilling though, this one really should have been catched in release testing. But again, IMHO.

Best regards.