Overview

The global package functionality in Document Processor allows users to copy Document Processor flows between tenants, both within the same company and across different companies.

The primary purpose is to simplify deployment of Document Processor flows from test to production environments. Typically, flows are designed in a test tenant (TST) with document classes, activities, and prompt instructions, then refined through multiple iterations. Once verified and tested, the global package enables seamless transfer to the production tenant (PRD) within both the same and across the different companies.

To export and import through Global Packages, a global package namespace must be assigned to a Document Processor flow during creation. To assign a namespace, click the Create Document Processor Flow button. This redirects you to the Basic Info page. Then, from the Namespace list, select the namespace to assign to the global package.. Once assigned, the namespace cannot be changed.

Additionally, when creating a version of a Document Processor flow, if a namespace is assigned to one version, it cannot be modified in other versions. All versions of a flow share the same namespace.

Only flows with Active status and versions marked as Active or InActive can be exported or imported using global packages. Draft flows or Active flows containing draft versions are not supported.