Skip to content

Process Version XML Transfer

Process developers can move a process definition between Emakin environments by exporting a process version as XML and importing that XML into another process.

Export a Version

  1. Open the process page and locate the required version.
  2. Open Operations.
  3. Select Export XML.

The browser downloads the formatted process graph as an .xml file. The exported file contains the process definition, including its pools, tasks, routes, forms, data model, scripts, and related process-level configuration.

Import as a New Version

  1. Open the destination process page.
  2. Open the process menu in the main toolbar.
  3. Select Import and choose an .xml file from the local computer.

Emakin creates the next process version number and validates the imported definition before committing it. A successful import is created as a TestMode version; it is not activated automatically. Test the version and change its state only after reviewing the definition and its dependencies.

Update an Existing Version

  1. Open the required version in the version list.
  2. Open Operations and select Update.
  3. Choose the replacement .xml file.

The update uses the normal process-version editing and commit flow. The version is locked while the change is prepared, validated, and committed. A successful update returns the version to TestMode; it does not silently activate an active version.

Compatibility and Validation

  • Use XML exported from a compatible Emakin process-definition version whenever possible.
  • The file must be a complete process graph, not a diagram-only or partial XML document.
  • The server parses the XML and deserializes the process definition before saving it.
  • Invalid XML, missing required definition data, duplicate query identifiers, and invalid pool structures can cause the import or update to fail.
  • Importing a definition does not automatically migrate external credentials, files, database infrastructure, or other environment-specific configuration. Review those dependencies in the destination environment.
  • Preserve the exported file as a deployment artifact so the change can be reviewed or restored through a subsequent import.

Permissions and Locking

Export uses process read access. Importing a new version or updating an existing version requires process write access. Another user's active edit lock prevents an update until that edit is completed or released.

Related references: