In resolving an Alert that was intermittently appearing I realized that a process model in our app did not have an XOR gateway fully configured, and I was wondering how this could have been allowed to be published in the first place? See the screenshot below to see the node configuration.
How does this entire process and sub-process work sometimes when the decision node isn't configure to move the process forward into the sub-process? It's only triggered the Alert when there are 0 instances to move into the sub-process, then we get the Alert in the other screenshot provided.
It's an easy fix, but I wanted to see if anyone knows if this is a glitch with Appian? Just curious/concerned why the model was allowed to be published with no node configuration errors. Thanks!
Discussion posts and replies are publicly visible
© 2023 Appian. All rights reserved.