Upgrading IDP

Introduction

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.

Step 1: Deploy the Execute Stored Procedure plug-in

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):

  1. In your Appian environment, log in as a system administrator.
  2. Go to > Admin Console.
  3. On the left side of the console, click Plug-ins.
  4. Click DEPLOY NEW PLUG-INS.
  5. Search for and click the Execute Stored Procedure plug-in.
  6. Click DEPLOY.

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.

Step 2: Download software package

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.

  • IntelligentDocumentProcessing(IDP)v1.4.0SQLPatch.sql: SQL script to update the database tables for the newest version of IDP.
  • IntelligentDocumentProcessing(IDP)v1.4.0Patch.zip: Application patch to import into Appian.

If you're upgrading from IDP 1.0 to 1.4, you'll need to apply the patches in order. You won't be able to upgrade directly from IDP 1.0 to 1.4.

Note that you must be registered with your company on Community to download this file.

Step 3: Note objects to merge

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:

  • Expression rule DU_returnDataTypeForChoiceIndex
  • Expression rule DU_returnDataStoreEntityForChoiceIndex
  • Data store DU Data Store
  • Contents of database table dudoctype

Step 4: Run the DDL script

In order to update your database tables to work with the latest release of the IDP application, you will need to run the DDL script in your database.

To run the DDL script:

The DDL file is meant to be used for MySQL databases. If you use a different database you may need to modify the database commands.

Step 5: Import the patch

The final step is to import the patch into your Appian environment.

  1. In your Appian environment, log in as a system administrator.
  2. Go to > Appian Designer.
  3. Open the Intelligent Document Processing (IDP) application.
  4. Click IMPORT PATCH.
  5. Click UPLOAD and select the IntelligentDocumentProcessing(IDP)v1.4.0Patch.zip file.
  6. Click INSPECT.
  7. Review the inspection results. If there are no issues, click IMPORT PACKAGE.

Step 6: Merge document type objects

If any document types already exist in the application, merge the contents of the following objects based on the notes from step 3:

  • Expression rule DU_returnDataTypeForChoiceIndex
  • Expression rule DU_returnDataStoreEntityForChoiceIndex
  • Data store DU Data Store
  • Contents of database table dudoctype
Open in Github Built: Fri, Nov 04, 2022 (07:10:52 PM)

On This Page

FEEDBACK