Scenario: roll back to an earlier version
Lesson 22 of 25 5 min read
Go back to an earlier version safely, given that an archived version can never be published again.
Sooner or later a version you publish will be wrong. Supply Lens has no "republish v3" button, on purpose: every change is a new version, so the history stays honest. Rolling back means making a new version that contains the old body. This lesson walks through it.
Hilltop's parse map loses tracking numbers
On Tuesday you published v6 of Hilltop Coffee's Northbank shipment parse map. By Wednesday Hilltop reports that Shipments are arriving without tracking numbers. v5 was fine. You need Hilltop back on v5's behaviour now, and a proper fix later.
Step 1: confirm what changed
Open the parse map and select Versions. Select v5 (Before), then v6 (After). The differences show the tracking number path changed in v6. That confirms the cause and tells you v5's body is the one you want.
Step 2: start a new version from live
Open the live version (v6) and select Edit. This starts a new draft, v7.
Step 3: copy the earlier body in
Copy the body of v5 from the version history and paste it into the editor, replacing the draft's body.
Step 4: validate, save and publish
- Select Validate. Expect Nothing to report., since v5 was published before. If a rule has tightened since, fix what it reports.
- Select Save.
- Select Changes to compare your draft with live v6. The differences should be the reverse of what you saw in step 1.
- Select Publish. A parse map is also checked against the document model at publish.
- When Version 7 is live. shows, select Done.
Step 5: confirm
Run What actually runs for Parse map, Northbank WMS and shipments. It should show v7. Ask Hilltop to watch the next despatch file.
Why not just archive v6?
Archiving v6 puts nothing in its place. Hilltop would fall back to a shared base if there were one, and there is not, so Shipments would fail entirely. Rolling forward to a copy of v5 is the safe route.
Write it down
Put "v7 is a rollback to v5's body" in the Description, or in your ticket. Anyone reading the version history later will see v7 and v5 are identical and wonder why.
Recap
- You cannot publish an archived version again.
- To roll back: compare versions, Edit the live version, paste the earlier body, validate, save and publish.
- Use Changes to confirm you are reversing exactly the bad change.
- Archiving is not a rollback: nothing takes the archived version's place.
- Record that the new version is a rollback.
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.