The swim lanes and annotations are missing from the process model, and the connectors between nodes are not formatted correctly. The logs have the following error message:
ERROR com.appiancorp.process.design.service.ProcessDesignServiceXmlImpl - An error occurred retrieving the model from the filesystem.
The following error message appears earlier in the logs when the process model was published:
ERROR com.appiancorp.process.design.service.ProcessDesignServiceXmlImpl - An error occurred storing the model on the filesystem. java.lang.RuntimeException: XML serialization of ACP failed: ActivityClassParameter[name=*****,it=****,v=] ... 136 more Caused by: com.appiancorp.type.xmlconversion.exceptions.ToXmlConversionException: Cannot convert internal value of type CIQ_QSTNNR (id=16712) to XML (target element qname: {http://www.appian.com/ae/types/2009}interior-expressions). Internal value: [Ljava.lang.Object;@3654c06[{,,,,,,,,,,,,,,,,,,,,,,,,}] at com.appiancorp.type.handlers.RecordHandler.convertInteriorExpressionsToXml(RecordHandler.java:706) at com.appiancorp.type.handlers.AcpBeanArrayHandler.convertInteriorExpressionsToXml(AcpBeanArrayHandler.java:292) ... 137 more Caused by: java.lang.ArrayIndexOutOfBoundsException: 25 at com.appiancorp.type.handlers.RecordHandler.convertInteriorExpressionsToXml(RecordHandler.java:690) ... 138 more
Alternatively, there may be an error like the following:
ERROR com.appiancorp.process.design.service.ProcessDesignServiceXmlImpl - An error occurred retrieving the model from the filesystem. com.appiancorp.suiteapi.common.exceptions.AppianException: Invalid Type: null (APNX-1-4047-000)
The root cause can be determined by looking at the application server log and finding the error message. In the first example above, the relevant error is:
Caused by: java.lang.ArrayIndexOutOfBoundsException
In this particular case the ArrayIndexOutOfBoundsException is thrown because the CDT was recently updated to have more fields than it originally had when this version of the process model was created.
This can happen under the following conditions:
In the second example above, the relevant error is:
com.appiancorp.suiteapi.common.exceptions.AppianException: Invalid Type: null
This indicates that a CDT that is referenced in the process model does not exist in the environment.
This has been addressed in Appian 16.1. Please upgrade to this version to take advantage of the fix.
To work around this in Appian 7.11 and earlier:
If the above does not work, perform the following:
If the process model has already been saved while it was in the incorrect state, restore it to a previous version with the following steps:
This article applies to Appian 7.11 and earlier.
Last Reviewed: January 2016