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.

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

Export

  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.
  3. A JSON file named DPF.json is downloaded to your local system.

Import

  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. The imported DPF retains metadata such as creation and modification date/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 will be imported seamlessly.
  • If the target tenant already contains the same DPF, the existing one will be 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 will be 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 will be appended to the target tenant.
  • If the target tenant has v1 as Active and the source tenant has v2 as Active, the import updates the DPF status to match the source tenant, making v2 Active in the target tenant.
  • 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.