Procedure
The dry run simulator
Walks through running a connection in simulation, so the result of a mapping is checked before live messages flow.
This page runs a connection in simulation. You feed it a message, read the result of the mapping, and confirm it before live messages flow.
What a dry run is
A dry run puts a real message through the real pipeline, the same parse, terminology, mapping and validation the live path uses, and swaps only the final write for a capture that records what would happen. The result shows exactly what the live path would produce, and the live record stays as it stands.
The live record is left as it stands
Every simulation carries the same promise. The capture step holds only what would be written and reaches no live store, the run refuses a live site, and a message marked as production traffic is flagged. A dry run runs against a sandbox site, so the live record is left exactly as it was.
Run a dry run
- 1
Open the simulator
In Westron, open a connection and start a dry run.
- 2
Choose the input
Paste a message, pick a checked-in sample, or replay a message the connection already received. The checked-in samples are synthetic, so a dry run carries only made-up patient data.
- 3
Pick the version and direction
Choose the mapping version to preview, a draft or the active one, and the direction, inbound or outbound.
- 4
Run it
Run the message and read the four panels below.
Reading the result
The result reads across four panels, each drawn from the same run.
| Panel | Shows |
|---|---|
| Parsed message | The message broken into its fields. |
| Validation | Every issue found, and the acknowledgement the live path would return. |
| Planned writes | Each write the pipeline would make, recorded without making it. |
| Routing | How the message would route, with its correlation keys. |
Fix, replay, promote
A dry run is how a mapping is fixed. Replay the message that went wrong, adjust the rule, and replay again in the sandbox, then confirm the new planned writes and routing.
A mapping reaches live traffic only after a dry run proves its output. The same samples run in a continuous check, so the result you read is the result the check asserts, and a rule change that alters an output is caught before it ships.
Common questions
Does a dry run change any live data?
A run records what would be written and leaves every live record as it stood. The capture step reaches no live store.
What can I feed a dry run?
A pasted message, a checked-in synthetic sample, or a message the connection already received, replayed read-only.
Watch a live connection once messages are flowing in monitoring a connection.