Overview

The primary purpose is to streamline deployment of Document Processor flows from test to production environments. Typically, users design Document Processor flows in a test tenant (TST) by adding document classes, activities, and prompt instructions, then refine them through multiple iterations. Once a flow is verified and tested, the local package enables seamless transfer to the production tenant (PRD) within the same company.

Only Document Processor flows with Active and flow versions with Active or InActive status can be exported and imported using local packages. Draft flows or Active flows with draft versions are not supported.

Flows can be exported in two ways:

• Local package with tags: Bundle multiple Document Processor flows under a tag and exports them together through CSSP.
• Local package without tags: Manual export of Document Processor flows in CSSP when including only a few specific resources in a package.