Hey guys! is there any way to make this cleaner?
I have to many OR and probably there is a better way to do this, so what i need is:
OR to go to a path in case it finds a status or the other one if it doesn't find it
then i need that in both cases it goes back to the script contador that its just an index+1 and iterates
Discussion posts and replies are publicly visible
Agree with XOR vs OR, in my 13 years working with Appian I've never used an OR. You can place all of your logic in order within an XOR and I would do something like below.
First XOR can route to the terminating end event - and ONLY use non-terminating on a side path which should keep the process active when it's flow is completed. If the path should end the process, make it a terminating end node.
Then your second XOR can handle the logic to either route back to the script task, or to complete the process. The logic from the other OR (XOR) nodes will be moved in to what order you want them evaluated in the remaining ones.
Chris said:ONLY use non-terminating on a side path which should keep the process active when it's flow is completed
glad to see we're in agerement on that approach. i've gone so far as to beg Appian to allow us to make "terminate" the default setting for End Nodes, as they're what i use in roughly 90% of cases.
Mike Schmitt said:glad to see we're in agerement on that approach. i've gone so far as to beg Appian to allow us to make "terminate" the default setting for End Nodes, as they're what i use in roughly 90% of cases.
I would be on board with that!
I can't count the times we've had a process "stuck" because there was a node with an error which was restarted, without the error instance cancelled, and the process doesn't close out due to a non-terminating end node..