Manual export and import of a DPF

Document Processor Flows (DPFs) created in any tenant can be exported or imported with a single click. To perform this operation, the DPF must be in an Active state. Both Active and Inactive versions of an Active DPF are eligible for export. However, Draft versions of Active flow cannot be exported. Likewise, if a DPF itself is in a Draft state, it cannot be exported.

To enable manual Export or Import functionality, you must have the Admin Security role.
Note: To use this functionality, ensure that the GenAI Embedded Experience feature is enabled in SSP.

Additionally, users cannot export Base DPFs, as they are already available in every tenant where IDP is provisioned.

Exporting

  1. Select any custom active document processor flow. You can export multiple flows at a time.
  2. Click Export and confirm to proceed with the export.
    Note: 

    You can export only Active versions or Active and InActive versions.

    You cannot export Draft versions.

    You can export the extensions added to any version.

  3. A JSON file named DPF.json is downloaded to your local system.

Importing

  1. Open Infor Document Processor on the target tenant.
  2. On the DPF listing page, click Import.
  3. Upload the previously exported DPF.json file from the source tenant.
    Note: 
    • You can import a single DPF, or multiple DPFs, each containing single or multiple versions.
    • You can assign Global Package namespace only when you import a single DPF.
    The imported DPF retains metadata such as creation and modification date and time. The imported DPF will be displayed on the DPF listing page according to the timestamp information it carries.

Behavior after import on the target tenant

  • If the target tenant does not already have the DPF, it is imported.
  • If the target tenant already contains the same DPF, the existing one is overwritten.
  • If both the source and target tenants contain the same DPF versions, for example, versions v1 and v2, the corresponding versions in the target tenant are overwritten, including all flow data and flow status.
  • If a version exists in the source tenant but not in the target tenant, for example, v3, that version is appended to the target tenant.
  • The incoming Active version remains Active, and the previously Active version is moved to InActive status.
  • If the target tenant has versions v1, v2, and v3, while the source tenant contains only versions v1 and v2, then during the import process, versions v1 and v2 on the target tenant are imported and overwritten. The existing v3 version remains unchanged and is not deleted.

Behavior after assigning a namespace during import on target tenant

  • The selected namespace gets associated with the imported DPF.
  • New incoming versions are appended.
  • The incoming Active version remains Active, and the previously Active version is moved to InActive status.
  • If the DPF already exists with a namespace, a different namespace cannot be assigned.
  • The namespace code is appended as a suffix to the DPF name.
  • Existing matching versions are not overridden.