View this page in the latest version of Appian. Upgrade DocCenter Share Share via LinkedIn Reddit Email Copy Link Print On This Page The capabilities described on this page are included in Appian's advanced and premium capability tiers. Usage limits may apply. Note: To ensure smooth upgrade processes, avoid customizing the DocCenter application itself. Any customizations have the potential to be overwritten during upgrades. If you haven't customized the application, you can contact Appian Support for a simpler upgrade. Upgrade the DocCenter application Note: DocCenter plug-in versions must match the DocCenter app version you are installing or upgrading to. Always upgrade the app and its required plug-ins together. Mismatched versions cause DocCenter functionality to break. To manually upgrade DocCenter or if you have made changes to the application: Download the newest version of the application from Forum. For tracking purposes, add the DocCenter design objects that you've modified to a package named Modified Objects. Run the correct /sql/<db vendor>/*.sql files to upgrade the database schema. Deploy the application/*.zip file to upgrade to the application objects. Check the Modified Objects package to see if any of your previously modified objects were updated. Using the comparison tool, merge your customizations with the updated object. Tip: Before installing or upgrading DocCenter, Appian recommends administrators enable a currently supported model and select an inference profile on the AI Services page. Version-specific upgrade guidance Upgrading to DocCenter 4.4 DocCenter 4.4 introduces processing versions for extraction and classification models. Existing model versions keep their current processing version on upgrade—nothing changes automatically. When a newer processing version is available, a banner appears on the model version Summary tab. See Upgrade a processing version. Remove deprecated record types DocCenter 4.4 deprecates the following record types, and the 4.4 upgrade scripts remove their backing database tables: AIA Extraction Bounding Boxes AIA Extraction Instance Section Record type deprecation applies only to upgrades. Fresh installs of DocCenter 4.4 don't include these record types. If nightly sync remains active on either record type after you upgrade, sync fails with the error "The configured database table is invalid. The […] table does not exist in the configured data source." DocCenter no longer uses these record types, so the failed sync doesn't affect DocCenter functionality. However, sync failure notification emails continue until you stop the sync. After upgrading to DocCenter 4.4, take one of the following actions to stop the sync errors: Delete the AIA Extraction Bounding Boxes and AIA Extraction Instance Section record types. Turn off the nightly sync schedule on both record types. Upgrading to DocCenter 4.3 DocCenter 4.3 requires updated versions of the following required plug-ins: PDF Tools DocCenter Component DocCenter Suite Upgrade all three plug-ins to their latest versions before importing DocCenter 4.3. No new plug-in dependencies were introduced in this release. Upgrading to DocCenter 4.2 To ensure your entire document catalog is organized and searchable, DocCenter 4.2 includes a utility process model that automatically updates missing document names for past instances. To populate these missing document names, you need to manually start the process model in Appian Designer. Open the AIA UPGRADE v4.2 Migration Process process model. Select File > Start Process for Debugging. Upgrading to DocCenter 4.0 DocCenter 4.0 introduces Autoscale support and requires Appian 26.1+. Autoscale is not required to use DocCenter, but the application works seamlessly with it. To upgrade to DocCenter 4.0: Upgrade Appian platform to 26.1+. Verify plugin compatibility: Ensure all required plugins are installed and whitelisted. Additional plugins may need whitelisting for Autoscale. Import DocCenter 4.0 solution packages. Configure Long Running Mode for AI Skill smart services (default as of 4.1; manual configuration needed for 4.0): Open the AIA Generic Prompt process model. Edit all Execute Generative AI Skill smart services. Enable Long Running Mode on each smart service. Save and publish the process model. Test existing models in the new environment. Model configurations should carry forward. If using Autoscale, verify compatibility for your process models, particularly any custom wrapper processes that call DocCenter processes. If using a wrapper application around DocCenter, update it to work with the new version. You don't need to rebuild any extraction, classification, or verification models. Existing model configurations (prompts, fields, sections, rules) should carry forward during the upgrade. However, we recommend that you: Re-run test cases and test suites, including verification test suites, to verify accuracy is maintained Check release notes for any deprecated features or changed behaviors Test the full extraction pipeline end-to-end in a non-production environment Upgrading from v2.x to v3.x DocCenter 3.0 introduced significant architectural changes. DocCenter 3.0 and higher use a single generic process model for running all extractions, instead of creating new design objects per model. Replace all usages of automatically generated process models with the following: For classification: Use: AIA Classification Run Model Version Parameters required: modelKey (Text) — Key for the model document (Document) — The document to process For extraction: Use: AIA Extraction Run Model Version Parameters required: modelKey (Text) — Key for the model document (Document) — The document to process Database migration steps: Back up your database before upgrading. Review the release notes for any manual migration steps. Run the solution import in a test environment first. Verify all models and configurations after upgrade. Recommendations for common upgrade issues Syncing errors Issue: "Syncing Errors" or missing table errors during deployment. Cause: Missing database mappings, deleted backend folders, or record types not synced. Resolution: Check if backend folders were accidentally deleted. Verify database mappings are correct. Ensure all required tables exist in the data source. Reinstall the latest solution packages to realign database scripts and objects. Verify records sync after reinstallation. Note: If the sync error affects the AIA Extraction Bounding Boxes or AIA Extraction Instance Section record type after an upgrade to DocCenter 4.4, the failure is expected. Both record types are deprecated in DocCenter 4.4. See Remove deprecated record types. inputText column sync error (v2.x to v3.x) Issue: Error related to inputText column exceeding 64,000 character limit during upgrade. Cause: Legacy data from old extraction models exceeds the record type field limit. Plugin compatibility Issue: DocCenter functionality breaks after upgrade. Cause: Plugin versions incompatible with new platform or DocCenter version. Resolution: Check DocCenter release notes for plugin version requirements. Verify all plugins are compatible with the new platform version. Update any incompatible plugins before deploying DocCenter. Test in a non-production environment first. For Autoscale deployments, work with Support to verify plugins are on the allow list. Feedback Was this page helpful? SHARE FEEDBACK Loading...