Both XPDL and iProcess procedures have XML schema formats. Each XML schema format has a version number. Inevitably, these schemas will change with later versions as new functionality is added. This means that you must understand how iProcess procedures and XPDL source is transformed when using later versions of the schemas or when using a mix of schema versions.
The version of the XPDL XML schema format that iProcess Workspace (Windows) implements is version 1.0. XPDL source to be loaded into iProcess Workspace (Windows) should conform to this XPDL XML schema format version. See
Transforming Between Different XML Schema Versions for more information about the XPDL and iProcess procedure XML schema format versions.
When you save an iProcess procedure as XPDL, the version number of the iProcess procedure XML schema format is defined in the
SchemaFormat extended attribute. This extended attribute specifies the elements that make up the iProcess procedure XPDL schema format:
If the SchemaFormat extended attribute is not present when the XPDL document is loaded then it is assumed to be compatible with the current schema format.
If you have some XPDL source that has been produced using an earlier XPDL or iProcess XPDL XML schema format, and you want to transform it into an iProcess Workspace (Windows) that uses a later version of the XPDL or iProcess XPDL XML schema format, iProcess Workspace (Windows) automatically upgrades the XPDL source to match the later schema versions.
If the SchemaFormat extended attribute is not present when the XPDL document is loaded then it is assumed to be compatible with the current schema format.
If you have some XPDL source that has been produced using a later XPDL or iProcess XPDL XML schema format, and you want to transform it into an iProcess Workspace (Windows) that uses an earlier version of the XPDL or iProcess XPDL XML schema format, then the XPDL will not load. You must re-define your XPDL so that it validates against the correct XML schema format version.
If the SchemaFormat extended attribute is not present when the XPDL document is loaded then it is assumed to be compatible with the current schema format.