Replicate what works, without carrying secrets

A Solution, available from Automate, is a package of maps, flows, credential-free connectors and agent policies. Semantic versioning is proposed automatically and the export history lets you download every version identically. Import is guided: new components arrive as drafts, with a checklist of placeholders to complete and a per-component strategy, meaning link, create or skip.

Process Map packages, from Measure, carry a whole map with its flows, up to 50, with mandatory credential redaction. Import preview writes nothing and never overwrites. Flow JSON export, included in Free too, uses an open format and an all-or-nothing pre-check; detected credentials become placeholders with a redaction report.

To show a process without real data, demo data has three grades: no data, rules only or sample cases too. With rules only, numbers, invented names and a seed travel, so two installations see the same scenario. Real cases can never be exported. Process templates, such as order approval and ticket handling, start with a diagram preview and warn if they contain reserved fields.

In practice, a consultant builds the process once in their own environment, exports it as a Solution, and imports it in the client's environment. The import shows what will be created and what will be linked to elements already present, and leaves as a draft whatever needs local configuration, such as a connector or a key. No component goes to production without being reviewed by whoever owns it.

This way of working reduces differences between installations and makes rollouts repeatable. A partner can keep a reference version of the solution, release updates with semantic numbering and know exactly what each client received thanks to the export history. For internal teams the same principle applies between development, testing and production: the package is the unit of movement, not manual copying of configurations.

For those starting out, the shortest road is a process template: you pick an included example, look at its preview, adapt it to your own roles and data, and publish. When the process grows, the same flow becomes the core of a Solution. The step from template to package is gradual and requires rebuilding nothing: format, versions and redaction rules are the same.

Special care applies to secrets. When a flow contains a connector, export keeps its structure but not its credentials: whoever imports finds a placeholder and a checklist saying what to enter. Likewise agent policies travel with the Solution, but keys do not. So the package can be shared with a client, a colleague or a partner without risking handing over access.