Import and export for processes or save as a copy to other customers
M
Micha W.
We create global processes as templates, which we adapt for our customers. This creates linked copies, but these remain dependent on the original global process. This poses several challenges:
Dependencies:
When you delete a global process, all processes created from it are also deleted for customers. This leads to data loss and poses a threat to our work processes.
Confusion in global processes:
In order to reuse processes or adapt them for other customers, we are forced to leave them as global processes. Over time, this creates a confusing structure.
Limited reusability:
We lack a function to move processes as independent, detached copies between customers or to export and import them as standalone templates.
Feature request:
Independent copies: Processes should be able to be moved or exported/imported as standalone copies between customers, without dependencies on the original global process.
Archiving: Global processes should not have to be permanently deleted, but should be able to be archived as an option to improve the overview.
Flexibility: The combination of templates and derived processes should be optional to enable individual adjustments.