Knowledge Base - Smart Flows
Knowledge Base - Smart Flows
Breadcrumbs

Experlogix Documents Project-level Formats and Smart Flows Import/Export

Overview

With the introduction of formatting field and expression mappings by referencing a project-level format in Experlogix Documents, an important limitation exists when templates are transferred between projects using Experlogix Smart Flows import/export capabilities.

Until planned optimization of the import/export capabilities across Smart Flows and Experlogix Documents is available (slated for the Winter 2027 release wave), Smart Flows is not aware of all field format dependencies stored in Experlogix Documents. As a result, field format associations may not be preserved during project migration scenarios.

Impact

This limitation only affects import/export scenarios involving Fillable PDF templates that contain references to project-level formats.

When a Fillable PDF template containing project-level or mapping-level field formats is exported from one project and imported into another through Smart Flows:

  • Field format associations may be lost.

  • Formatting may revert to project defaults or system defaults.

  • Template execution continues to work, but generated output may not use the expected formatting.

Normal template design and execution within a project are not affected.

Workaround

Until the an optimized import/export solution is available, use the following process to promote packages containing fillable PDF templates:

  1. Import the package through Experlogix Smart Flows.

  2. Ensure the Overwrite existing option is enabled during import.

  3. Export the affected template from Experlogix Documents.

  4. Re-import the template into the target Experlogix Documents project using Overwrite.

  5. Verify that expected field formats are available and correctly applied.

Additional Notes

  • Smart Flows version 4.29 is expected to change the import experience so that Overwrite existing is selected by default, reducing the likelihood of user error.

  • This limitation is considered temporary and will be resolved by the planned import/export optimization feature, which will automatically transfer and recreate field format dependencies during migration.