Product adoption roadmap versioning

  • Release version: Australia
  • Updated July 26, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Product adoption roadmap versioning

    Product adoption roadmap versioning enables you to preserve snapshots of your roadmap each time you publish it, creating a complete history of changes. This feature is essential as adoption plans evolve with shifting priorities and new product introductions. It allows you to review past versions or revert to earlier plans without permanently losing your current roadmap state.

    Show full answer Show less

    How Versioning Works

    • Publishing a roadmap creates a new, read-only version record that captures JSON snapshots of the roadmap header, lanes, and items at that moment.
    • These snapshots store the entire state of the roadmap but cannot be copied or edited directly—only the version label can be updated.
    • When reverting to a previous version, the lane and item configurations are restored from the selected snapshot, while the roadmap header’s Draft or Published status remains unchanged.
    • The version label in the roadmap header updates to show the most recent published version.

    Version Record Details

    Each version record contains:

    • Version: A numeric identifier that increments with each publish (e.g., 1.0, 1.1, 1.2), customizable with a label relevant to your engagement.
    • Roadmap: The associated product adoption roadmap.
    • Previous version: Links to the prior version to track the full change history.
    • PAR snapshot: Read-only JSON of the roadmap header state at publishing.
    • Lane snapshot: Read-only JSON capturing lane configuration details.
    • Item snapshot: Read-only JSON of all items within lanes at publish time.

    Note: Visual comparisons between versions are not available in this release.

    Viewing and Managing Versions

    • The current version label is visible in the roadmap header for quick reference.
    • All published versions appear in the Versions related list on the roadmap record, displayed chronologically.
    • You can restore the roadmap to any previous version from this list to revert changes as needed.

    Practical Benefits for ServiceNow Customers

    This versioning capability provides ServiceNow customers with greater control and flexibility over their product adoption roadmaps by maintaining historical records and enabling easy rollback when strategic changes occur. It ensures adoption plans remain transparent and recoverable, supporting iterative planning and communication with stakeholders.

    Versioning preserves a snapshot of your roadmap each time you publish it, creating a complete history you can review or restore when plans change.

    Product adoption roadmaps evolve over time as priorities shift and new products are introduced. Versioning lets you preserve a snapshot of the roadmap every time you publish it, giving you a complete history of how the adoption plan has changed. If you need to go back to an earlier plan, you can revert the roadmap to any previous published version without losing the current state permanently.

    Publishing a roadmap creates a version record that stores a read-only snapshot of the roadmap header, lanes, and items at that point in time. Version records can't be copied or edited. You can update only the version label.

    How versioning works

    Publishing a roadmap creates a new version record linked to that roadmap. The version record stores snapshots of the header, lanes, and items as JSON. When you revert to a previous version, the lanes and items are restored from that version's snapshots. The roadmap header state (Draft or Published) is not affected when you revert to a previous version.

    The version label in the roadmap header reflects the most recently published version and updates whenever you publish a new version.

    Version record fields

    A version record includes the following fields:
    • Version: Identifies the version of the roadmap. By default, the first version has the format 1.0 <roadmap name>. Every time a new version is published, the version increments (1.0, 1.1, 1.2, and so on). You can edit the label to use a custom name suitable for your engagement.
    • Roadmap: The product adoption roadmap that this version belongs to.
    • Previous version: The previous version of the roadmap. This field links versions together so you can track the complete history of roadmap changes.
    • PAR snapshot: A read-only JSON snapshot of the roadmap header at the time of publishing.
    • Lane snapshot: A read-only JSON snapshot of the lane configuration at the time of publishing, including the name and details of each lane.
    • Item snapshot: A read-only JSON snapshot of all items within the lanes at the time of publishing.
    Note:
    Snapshots store the complete roadmap state as JSON. A visual comparison between versions is not available in this release.

    View version history

    The current version label is displayed in the roadmap header. To view all versions for a roadmap, open the roadmap record and scroll to the Versions related list. The list displays all published versions in chronological order.

    To restore a roadmap to an earlier state, see Revert a product adoption roadmap to a previous version.