Google has deprecated legacy versions of AutoML services, which directly impacts IDP's core functionality. Additionally, the IDP application was deprecated with Appian 23.2. Customers who wish to use the application will need to refactor plug-ins using AutoML. |
Periodically, we release updates to the Intelligent Document Processing (IDP) application that include enhanced features. Most customers will be able to take advantage of the newest features by deploying a patch to update their application.
Note that making certain changes to your environment will make upgrading more difficult. In order to take full advantage of the newest features, we suggest only making changes that are outlined in the IDP documentation on this site.
If your cloud environment is already running IDP, use this page to deploy the feature enhancements from the latest version of IDP. IDP upgrades must happen in sequence. You won't be able to skip a version of the app.
If your Appian installation includes different environments, such as development, staging, and production, we recommend following these instructions to upgrade each of your environments separately.
Starting with IDP 1.1, the Execute Stored Procedure plug-in is required. If you do not already have this plug-in deployed in your environment, you will need to deploy the plug-in by following these instructions.
To deploy plug-ins for self-managed installations, see Appian Suite Plug-Ins.
To deploy the plug-in for cloud installations (if necessary):
Note: IDP relies on a set of bundled plugins that Appian supports as part of the application. Support for use of these plugins in other scenarios is provided by the Appian community in accordance with AppMarket guidelines.
Upgrading IDP uses different files than installing the application for the first time. You will need to download the software patch that contains the following files. These files will be used in the remaining set up steps. In the list below, each file lists the target IDP version. The number may be different if you're upgrading to another version.
If you're upgrading from IDP 1.0 to 1.6, you'll need to apply the patches in order. You won't be able to upgrade directly from IDP 1.0 to 1.6.
Note that you must be registered with your company on Community to download this file.
If any document types have already been created in the environment, the upgrade patch may overwrite this content, and updates to the objects related to creating document types would be lost. To avoid this, take note of the version and contents of the following objects:
DU_returnDataTypeForChoiceIndex
DU_returnDataStoreEntityForChoiceIndex
DU Data Store
dudoctype
dudocchannel
The final step is to import the patch into your Appian environment.
Intelligent Document Processing (IDP) - IDP 1.6.2 Patch.zip
file.If any document types already exist in the application, merge the contents of the following objects based on the notes from step 3:
DU_returnDataTypeForChoiceIndex
DU_returnDataStoreEntityForChoiceIndex
DU Data Store
dudoctype
As noted above, customizing your IDP application requires you to take additional steps during upgrades. If you previously modified the DU Data Store
object to include additional document types, you'll need to recreate these customizations after you import an upgrade patch. This section describes how to upgrade IDP and maintain your document type customizations.
To use your custom document type in the DU Data Store
object after importing a patch:
DU Data Store
object. A message appears at the top of the page: A modified draft of this data store exists. Saving changes will overwrite the draft.The DU Data Store
object now contains entities from the patch as well as entities for your custom document types.
Upgrading IDP