Is there a way to disable nodes in a process model for testing purposes? At the moment I just disconnect the nodes from the process model, but Appian doesn't seem to like that. I would like to be able to do some equivalent of commenting them out, if there's anything like that.
Discussion posts and replies are publicly visible
Can you go a little bit more into your use case? If it's a node you need to have permanently in place but will usually need to bypass for testing purposes, the standard method is to have an XOR gateway prior to the node that checks the value of either a PV or a constant, to see whether it's in "testing mode" let's say, and executes accordingly.
Hmmm... that seems a little inefficient and heavy on setup for what I had in mind.
This would be while building a process model. For example. I have 10 nodes and know that the first 9 nodes work fine, but am still getting the 10th node to work, is there no way to just ignore the first 9 nodes? If they are forms, for example, it could be a hassle filling out each one individually to see if that 10th node does what it's supposed to do. Or maybe one of the nodes isn't working properly and I want to isolate it to figure out where exactly in the process model that's happening without rewiring everything.
In normal coding, you can just comment out all the parts you don't want to deal with. Is there no equivalent in an appian process model?
Marco said:In normal coding, you can just comment out all the parts you don't want to deal with.
Not really in a process model. My own personal technique for dealing with such a thing in a dev environment is to get a single instance to that node, then edit the instance and restart the node as needed until it's working, then copy that change back over to the model. that way you don't have to, for instance, fill out the forms for 10 user input tasks before a final node that does processing, you just get that far once and then try that node as many times as needed.
Not ideal, but I guess it is what it is. Thanks!
Mike Schmitt said:Not really in a process model. My own personal technique for dealing with such a thing in a dev environment is to get a single instance to that node, then edit the instance and restart the node as needed until it's working,
i do absolutly the same there. As of now, its the most practical approach so far besides testing your rules, interfaces, integrations or what ever in advance, if this is possible