Skip to main content

2.6 Version Control

Questions about versions control of entities in Rekonnect

Updated over 7 months ago

Version control in Rekonnect is a core feature that ensures training content, documents, and other user-facing materials are accurate, consistent, and compliant. By maintaining a clear history of changes and controlling what is publicly visible, version control supports both traceability and quality assurance in MedTech training and communication.


What is version control?

Version Control is the process of managing different iterations of a content item, such as a product, training package, course, or document over time.

Only one version of any item can be published (live) at any given time. All previously published versions are archived but still stored for reference and audit purposes.


Why version control matters in MedTech:

  • Ensures regulatory compliance by keeping track of what has been published

  • Prevents users from accessing outdated or unapproved content

  • Supports internal review processes with approval and publishing workflows

  • Maintains a historical record for auditability and quality control


Content version types:

  • Major Version: Significant updates or structural changes to content (e.g., from v1.0 to v2.0)

  • Minor Version: Small updates, typo fixes, or minor content changes (e.g., from v1.1 to v1.2)

Each version is clearly numbered and stored in the system.


Editing flow and version selection

When an admin clicks Edit on a product (or training package, course, or document) that has already been published, a modal window appears asking them to select whether the upcoming changes should result in a minor or major version.

  • Minor Version: Ideal for quick corrections or small updates that do not fundamentally change the meaning or structure of the content.

  • Major Version: Used when making substantial changes (e.g., new sections, restructured content, new training logic). This choice creates a duplicate of the original item, so version 1.0 remains archived and unchanged while version 2.0 becomes the editable draft.

This mechanism ensures clarity in version history and supports parallel review or comparison of old vs. new content.


Publishing workflow and version states:

Content can exist in the following states:

  1. Creating – The draft phase where new content is authored

  2. Waiting for Approval – The content is submitted for review by an authorized approver

  3. Updating – The draft is undergoing changes after review

  4. Approved – The content is cleared for release

  5. Published – The content is live and accessible to users

  6. Archived – The content has been superseded or deprecated

Only one version of an item can be published at a time. Publishing a new version automatically archives the previous one.


Version control applies to:

  • Products

  • Training Packages

  • Courses

  • Documents

  • Forms

Each of these content types is subject to the same versioning and publishing discipline to ensure consistency.

Did this answer your question?