Explain differences between service versions
Ask Darcy to explain the meaningful changes between saved service versions. This turns Builder's change detail into a readable account of what changed in the journey and what needs to be checked before release.
Choose the comparison
Open the service, then identify the two saved states you want to compare. Useful requests include:
- “Explain the changes between versions 38 and 42.”
- “What changed in the saved Builder version since the version deployed to QA?”
- “Compare the current saved service with Production and highlight changes to questions, routing and notifications.”
- “Explain how this page changed in the last saved revision.”
Darcy can inspect saved history, relevant historical definitions and recorded deployment status. It uses Builder's version comparison to explain changes with their page, field or action context.
Understand saved and deployed state
| State | What it means |
|---|---|
| Current saved Builder version | The latest saved service definition. Unsaved edits in a conversation are outside this comparison. |
| Historical saved version | A particular snapshot in the service's change history. |
| Deployed version | The snapshot Builder records as deployed to a particular environment, which may differ from the current saved version. |
Version labels can repeat after restores. Darcy resolves the exact saved snapshots from history and deployment records. Include a time, author or environment when a version number is ambiguous.
Ask for an explanation that helps review
Specify your review purpose. For example, ask for changes that affect the applicant journey, field IDs used by integrations, conditional routes, validation, calculations or generated documents.
A useful comparison identifies the changed pages or settings, explains the difference from the older state to the newer state, and highlights the routes and integration outcomes to retest. Check any unfamiliar rule against the actual service configuration.
Large histories and comparisons may need several reads. If Darcy reports an incomplete comparison, ask it to continue before treating the summary as a complete release review. Missing historical definitions cannot be replaced with an assumed diff.
What a comparison changes
The comparison itself is read-only: it does not edit, restore or deploy the service. Use Service change management if you decide to restore a saved state, then test the resulting current version.
Recorded deployment status identifies published snapshots; it does not establish live runtime health. Verify integrations in QA and deploy the version you have reviewed and tested.