Deploy

This topic covers how to deploy classification and extraction models to other Appian environments.

Prerequisites for deploying DocCenter models

Deploying DocCenter classification and extraction models to other Appian environments requires the following:

• Target environment setup: Each target environment must have the required plug-ins and AI skills deployed and enabled.
• Matching platform versions: The source and target environments must be on the same Appian platform version. DocCenter does not support cross-version deployments.
• DocCenter application access: You must have access to the DocCenter application in both the source and target environments.

Deploy models to other environments

1. Open the Deployment page.
2. Click MANAGE MODELS FOR DEPLOYMENT. Here you see a list of classification and extraction models, as well as their versions.

3. Select the models you want to deploy and click NEXT.

   Note:  During this step, a snapshot of the models and their most recently published version is captured in the AIA deployment document, which is included in the DocCenter application. You must include this file in the deployment. If you make additional changes that you'd like to deploy, repeat the previous steps to take a new snapshot of the models before deployment.

4. The models are added to the list to include in the next deployment. Click CLOSE to dismiss the confirmation message.
5. You can add or remove models from the deployment list by clicking MANAGE MODELS FOR DEPLOYMENT.
6. In Appian Designer, open the DocCenter application.
7. Use COMPARE AND DEPLOY to deploy your application or a package with the necessary design objects. Be sure to include the AIA deployment document from the DocCenter application in your deployment. This is the file that determines which models will be deployed.

Once deployed to the higher environment, DocCenter runs a post-deployment process model which processes the AI Deployment doc and makes the necessary database updates.

How model version numbers work across environments

DocCenter model version numbers are independent across environments. When you deploy a model to a target environment, DocCenter creates a new version in that environment rather than matching the version number from the source.

For example:

• If you deploy version 4 from your development environment to production, and production is currently on version 2, the imported model becomes version 3 in production.
• If production is on version 8, the imported model becomes version 9, regardless of the version number in the source environment.

Model version independence means you can deploy models between environments without worrying about version number conflicts. Changes made directly in the target environment (such as prompt tuning in production) won't block deployments from lower environments.

A model's processing version also travels with it on deployment. If the target environment runs a newer DocCenter package, the deployed model continues to use its stamped processing version rather than adopting the latest available. Its processing behavior does not change as a result of deployment.

Deploying manually

If you don't use Compare and Deploy and instead deploy your applications manually, then the post-deployment process model won't run automatically. To trigger the post-deployment process manually:

1. Open the DocCenter application in your target environment.
2. Open Deployment page.
3. Click RUN DEPLOYMENT.

Feedback