The platform includes two built-in helper Processes for cloning existing configuration: Clone Process and Clone Screen. Both are available from the Processes module in the Configuration application.
Cloning is useful when you need to create something similar to an existing configuration and want to avoid rebuilding inputs, outputs, and other components from scratch. It is a starting point, not a finished result — always review and modify the cloned configuration before using it in production.
Clone a Process
Clone Process copies an existing Process record and its associated configuration — including Process Inputs, Outputs, Parameters, and other components — to a new name.
Important: the Process Logic workbook is not copied. You must upload or configure the workbook separately after cloning.
Open the Configuration application and navigate to Processes.
Locate Clone Process in the process list and click Run.
When prompted, select the source Process from the list.
Enter a name for the new Process.
Click Run.
When the clone completes, navigate to Process Configuration \> Processes, locate the new Process, and:
Upload the required Process Logic workbook.
Review and modify all Inputs, Outputs, Parameters, and other settings as needed.
Enter an Audit Comment on any changes and save.
Do not assume the cloned configuration is correct for the new Process without reviewing it. Object references, filter assignments, and output mappings may need updating.
Clone a Screen
Clone Screen copies an existing screen configuration — including its layout, object editor settings, and filters — to a new name.
Open the Configuration application and navigate to Processes.
Locate Clone Screen in the process list and click Run.
When prompted, select the source screen.
Enter a name for the new screen.
Click Run.
When the clone completes, navigate to the Layout module, locate the new screen, and edit the layout, filters, and configuration as required.
Design guidance
Cloning is most useful when creating a variation of something that already works — for example, a Process that calculates for a different entity type, or a screen that displays similar data with different filters. It saves time on repetitive configuration.
Name cloned items clearly and immediately. A cloned Process with a default or copied name is easy to confuse with its source. Rename it to reflect its actual purpose as the first step after cloning.