Overview

They are primarily used to promote tested resources/Document processor flows from a test tenant to a production tenant, either within the same company or across different companies.[ME1.1]

A global package can include Document Processor flows that define document classes, activities like document classification and entity extraction, entity and table header with their prompt definition and extraction prompt instructions for document processing.

To make a flow eligible for global package deployment, it must be associated with a global package namespace. The namespace is assigned during flow creation or during import into an editor tenant. After assignment, the namespace cannot be changed, and all versions of the flow must continue to use the same namespace.

Only Active document processor flows with Active and InActive versions can be exported or imported through global packages. Draft flows, or active flows that contain draft versions, are not supported.

Global Packages also control resource editability in the target tenant. In read-only mode, deployed resources cannot be modified. In editable mode, users cannot edit, copy, modify, or delete deployed Major or Minor versions, but they can create, edit, and delete patch versions in the target tenant to make customer-specific changes.