Process importing

Nutrient Workflow Automation supports the ability to import an entire process definition from one installation of Workflow Automation to a separate installation of Workflow Automation. You can import the process itself, any forms that are part of the process, and any custom JavaScript that was added.

When a process is imported into Workflow Automation, it will be a mirrored image of the process and will contain everything you built for that process in the other Workflow Automation installation.

The only exceptions are that any files attached to the process and any task type that requires templates (PDF and Excel task types) aren’t included in a process export. Those attachments and templates will need to be added to the imported process, and the task will need to be reconfigured.

Importing a process

To import a process into Workflow Automation, navigate to the Processes section under the Administration menu. Select the dropdown arrow under Add Process.

When selected, you’ll be prompted with the following dialog.

You’ll be required to enter the following:

  1. Name — The name of the process.
  2. Category — Select the category where the process will be placed.
  3. Import File — Attach the JSON export file that was generated by Workflow Automation when the process was exported. Note that while we still support the importing of the old IPML format, any incompatible task types won’t be brought in — specifically form tasks.
  4. Create New IDs (optional) — If you select this option, the import procedure will generate new IDs for the process and all tasks. If left unchecked, the import procedure will use the process ID and task IDs as defined in the export file.

Select Import when the required items have been completed.

After Workflow Automation imports the process in the system, it’ll open the process definition for that newly imported process.

Additionally, any forms associated with the process will be stored in the same category you selected when importing. The form name will also be appended with the name of the process you defined.

Static recipients (users and groups) of tasks will not be imported. You’ll need to redefine the recipients of tasks, which also may require revisiting task rules that are dependent on recipients.