Configuration Snapshots
A configuration snapshot is everything you have set up in Xchange, recorded at one point in time: all connections, all routes with their steps, triggers and mappings, all value tables. The whole set, in one piece, with a version number.
What runs in operation is what was activated last; what was edited last waits in the draft.
Two snapshots at the same time
Xchange keeps at most two:
| Snapshot | What it is |
|---|---|
| Active Configuration | Xchange works by it in ongoing operation. Exactly one. |
| Draft | it collects your changes as long as they are not yet activated. At most one; in operation it takes effect only after the activation. |
In the example: active is version 7, activated on Friday, October 2, 2026, at 4:40 PM by
M. Brandt. Next to it is draft version 8, created on October 8, 2026, at 8:57 AM by A. Vogt. The
difference is one row in a value table — applepay is to go to the payment method KK from now
on. Until the activation, every order keeps running by version 7.
Both versions appear in the header, on every screen: Active v7 and next to it Draft v8 with its validation status. So you can already see there whether a draft exists, before opening Configuration Snapshots.
The way of a snapshot
A draft comes into being on its own. As soon as you change something anywhere — a field in a route, a row in a value table — Xchange creates it, and every further change goes into the same one. Importing a configuration creates one, too.
Validate tells you before the activation whether the draft is complete: a route without a step, a target field that is missing in the target system, a dispatch rule that points to nothing. The result appears as a status on the draft — Not Validated, Validated, Contains Errors or Validation Outdated. The last one means: you continued working after the validation, and the result is out of date.
Activate makes the draft the active configuration. From this moment on, Xchange works by it.
Archiving happens on its own along the way. The previously active snapshot moves into the archive — with its version number, the point in time and the person who activated it back then.
Restoring works from this archive: you select an earlier version and make it the active one again. The snapshot that was active until then is archived in turn — so everything is kept, and you can go back that step again. An existing draft stays untouched.
A draft survives the reset. If the system is reset while a draft is open, the draft is parked instead of discarded. It is then available as a parked draft and can be restored as soon as no other draft is open.
Every entry is saved on its own
On Connections, Routes and Value Tables, every entry goes into the draft shortly after the last keystroke. The bar at the bottom shows Saving… and then Saved. The Settings also save on their own, as soon as you leave a field, but are outside the snapshots: a changed setting applies immediately.
In the example: in the value table "Zahlungsarten Webshop", A. Vogt enters the value KK for
applepay. A moment later Saved appears at the bottom, and the row is part of draft v8.
Ctrl+Z undoes the last change, Ctrl+Shift+Z or Ctrl+Y restores it. This applies to the object that is currently open. If you open another one, the sequence starts over. Undone changes also land in the draft.
The bar shows three cases separately:
| The bar shows | What happened | What you do |
|---|---|---|
| Error saving — Retry | The change failed when saving. | Click Retry. |
| Waiting for Service Layer — Retry | The Service Layer is unreachable right now. The change is still in the form; Xchange retries every 30 seconds. If it gives up, the bar changes to Error saving; the change is still in the form. | Stay on the page or click Retry. |
| This record was modified by …, with Reload and Save anyway | Someone else has saved the same object in the meantime. | Two editors on the same object describes both ways. |
If you leave the page in the first two cases, you are asked. The message Unsaved changes offers Discard changes and Stay on page. Only Discard changes gives up the entry.
Validating and activating needs a permission of its own
Editing and activating are two different permissions in Xchange. Validating and activating require the permission Activation; only with it do the two buttons appear.
In the example: A. Vogt finishes building version 8; on Vogt's page, Validate and Activate are missing. M. Brandt sees the same page and has both.
More on this: Permissions.
What happens to what is already running
If you activate while something is running, what is running stays as it is. A run finishes with the snapshot under which it started.
So you can activate at any time, without waiting for a quiet minute or halting anything. In the example: the run from 9:10 AM picked up four orders and processes all four by version 7 — even though version 8 becomes active at 9:12 AM. Both halves of a run are always handled the same way.
The next run then takes the new snapshot.
Take along and import
A configuration snapshot can be exported as a file and imported again elsewhere — that way, what you built on a test system reaches the production system without retyping. You can export the active configuration or the draft.
Two things you should know:
- Credentials stay behind. Passwords and tokens of the connections are missing from the file. After the import, you enter them anew on the target system — only then do the routes reach their counterpart.
- An import always goes into a draft. You see beforehand which objects are new, which collide with existing ones and which are identical, and decide per object. The result becomes active only once you validate and activate it — like any other draft.
See also
- Configuration Snapshots (reference) — every field of the screen, the comparison of two snapshots and the import dialog
- The basic model (core concept) — how connection, route and configuration snapshot fit together
- Permissions (core concept) — who may build and who may activate
- Routes (core concept) — what is in a snapshot