I´ve a problem because I cannt save my process model. I was looking for a solution, but I didnt find it. Any suggestion?
- The Rules (name and inputs) and process variables are using correctly.
- The escalations in Tasks (I dont use escalations).
- Interfaces. Check the number and type of variables.
NOTE: I´ve more versions of the process model, but it always show the same message.. "The Process Model is invalid."
Thanks for your time,
I've had this before. From memory I think one of the expression rules I was calling had an extra comma in that although the expression editor didn't complain about was being picked up in the process model - so might be worth checking expression rules again.
This could happen if there are deleted process variables still getting used somewhere in the process. So please check the nodes in detail.
Can you try to keep deleting nodes and attempt to save again each time you delete one? There is likely something in one of the nodes - I've mostly seen it with a reference to a process variable or activity class parameter that has been deleted. Eventually, you should delete one node that will then allow you to save it.
Also before you do this, I'd recommend copying all the nodes to another process (it can be an empty one), because then you can copy any nodes back after making your changes.
I found the script that was giving problems, deleting node to node. I removed a node and tried to save, until it worked. After this, I created the script again. Thanks for your help! And for your appian video tutorials, I started learning appian with them!
If you have extensive script embedded in your Script Tasks you can mitigate this by encapsulating in a rule and calling that (it doesn't remove the risk but it does reduce it dramatically). It's also best practice because you can test your script independently of the process where you use it.
Peter Lewis said:Also before you do this, I'd recommend copying all the nodes to another process (it can be an empty one), because then you can copy any nodes back
There's a small but severe caveat to this - if any node has an output expression that takes up multiple lines (i.e. has any linebreaks at all), and it's copied into a process model where that expression's output PV doesn't exist, everything after the first line of the expression will be cleared upon pasting. This is an issue that I'd be happy if Appian fixed, though I have no reasonable expectation of that happening anytime soon, as it's been around for years as far as I've seen.
Yes i do see this behavior most of times with copy nodes from one process model to other or from older version.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.