<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The process model is invalid 16.3</title><link>https://community.appian.com/discussions/f/process/8823/the-process-model-is-invalid-16-3</link><description>Hello all, It has come to my attention that the validation in process models has become worse than previous Appian versions. I remember when the messages were meaningful indicating real errors that needed attention. Now during designing process models</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: The process model is invalid 16.3</title><link>https://community.appian.com/thread/39286?ContentTypeID=1</link><pubDate>Mon, 14 Nov 2016 17:31:41 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:968e05dd-90b8-473a-9cf3-d8f75fd834a5</guid><dc:creator>chetany</dc:creator><description>One related point as @rodgraham mentioned - If the user input tasks are using SAIL forms, and if any of the interfaces used in those SAIL forms  have some error - the process model would not be allowed to publish. Also, tracking down such an error can be difficult and time-consuming because the error message is sometimes not very specific.&lt;br /&gt;&lt;br /&gt;I have come across a scenario where the SAIL interfaces showed no error when I created them in the Interface designer, but when I mapped them to the user input tasks in the process model, I got an error, and it took quite a long time to track it. Also, you cannot save the process model in this situation.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The process model is invalid 16.3</title><link>https://community.appian.com/thread/39224?ContentTypeID=1</link><pubDate>Thu, 10 Nov 2016 22:43:55 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:75ecedf1-b164-4017-9642-b13c0766e619</guid><dc:creator>sikhivahans</dc:creator><description>@vasilisg Not an elegant one, but might be worth reverting to previous working version (in case if the interface already has working versions) or saving the definition of interface with value as null (in case if the interface has no working versions and is being built newly) for the time-being so that you can save the PM and don't need to loose the work and then you can resume the work on last but one version of the interface post saving PM. I have seen this error at times, but I didn't check if it neglects the changes made to PM in case if the interface has got any issues.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The process model is invalid 16.3</title><link>https://community.appian.com/thread/39222?ContentTypeID=1</link><pubDate>Thu, 10 Nov 2016 20:48:49 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:8fa3973e-da2c-49f5-a495-8b207d89683b</guid><dc:creator>Bob</dc:creator><description>Most of the time I have run into this situation it has turned out to be a task escalation expression problem, so I save more often now when adding escalations.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The process model is invalid 16.3</title><link>https://community.appian.com/thread/39218?ContentTypeID=1</link><pubDate>Thu, 10 Nov 2016 19:27:56 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0bb0de05-e322-4cc9-bea7-24afd55e8100</guid><dc:creator>rodgraham</dc:creator><description>Not that I&amp;#39;m aware of. First things to check are as you sail interfaces or if you&amp;#39;ve deleted any variables. In terms of losing a days work I assume you save your process models more than once a day&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>