When a process flow is duplicated, all shapes are copied (so the structure of the flow is replicated entirely) however, some shapes must be reconfigured. Reconfiguration requirements depend on where the process flow is copied:
As a 'typical' user managing your own company profile, you can duplicate an existing process flow to use as a starting point for a new process flow, within your company. Please see Duplicating a process flow for the current company profile.
As a Patchworks partner/agency managing multiple company profiles, you can duplicate process flows between these profiles. In this case, there are a few variations to consider - please see Duplicating a process flow between different company profiles.
The table below summarises shape reconfiguration requirements when a process flow is duplicated within the current company profile.
| Shape | Reconfigure? | Notes |
|---|---|---|
When a process flow is duplicated between different company profiles, most reconfiguration requirements are consistent with those detailed above. Variations to consider when duplicating between company profiles are summarised below.
| Shape | Reconfigure? | Notes |
|---|---|---|
Existing trigger schedule and/or webhook settings are duplicated in full. Applies when copying to the same company or to a different company.
All settings (including instance and endpoint details) must be reconfigured. If connectors do not exist in the receiving company, they must be installed and instances must be added.
Existing settings (including instance and endpoint details) are duplicated in full.
Existing settings (including instance, endpoint, route names and conditions) are duplicated in full. All 'child' shapes for routes are also copied - standard reconfigure options apply to these.
Existing custom script selections are copied in full.
Existing manual payload content is copied in full.
Existing manual payload content is copied in full.
All existing mappings are copied in full. In most cases, transformations are also copied however, if a transformation requires a company-specific resource (such as a script or a cross reference lookup), these are not copied. In this case, the map shape displays a warning - you must recreate these resources in the receiving company and reconfigure the associated transformation(s).
Copy status depends on the cache type:
Company. All existing settings are copied in full.
Flow. The add to cache shape must be reconfigured with a new cache.
Flow run. The add to cache shape must be reconfigured with a new cache.
Copy status depends on the cache type:
Company cache. All existing settings are copied in full.
Flow cache. The load from cache shape must be reconfigured with a new cache.
Flow run cache. The load from cache shape must be reconfigured with a new cache.
Existing settings (including instance and endpoint details) are duplicated in full.
Existing settings (including instance and endpoint details) are duplicated in full.
Existing settings (including data pool and data path) are duplicated in full.
The required custom script must be created and deployed in the receiving company, then the script shape must be reconfigured.
All existing mappings and transformations are copied. However, if a transformation requires an item which does not exist in the receiving company (for example, a cross reference lookup, a script, or a map) then these items must be added to the company and the transformation(s) must be reconfigured.
The shape must be reconfigured with a new cache.
The shape must be reconfigured with a new cache.
The shape must be reconfigured with a new data pool and a new data path.