Feature Request: Flexible BOE Versioning and Change Tracking
Summary:
Introduce flexible BOE versioning that allows users to manually create versions at any point in the workflow, automatically create a final version at the end of the workflow, revert to prior versions as needed, and track changes within text fields between versions.
Problem Statement:
Today, BOE versioning is constrained to the final step in the workflow, limiting users’ ability to checkpoint their work as they progress. If users need to experiment, branch, or make significant edits mid-process, there is no reliable way to preserve intermediate states or roll back to a known-good version. Additionally, change visibility across versions is limited, making it hard to understand what has changed in the narrative or text sections of a BOE. This increases the risk of errors, rework, and confusion for reviewers and approvers.
Proposed Solution:
Enable manual BOE version creation at any point in the workflow (e.g., via a “+ New Version” or similar control), not only at the final step.
Automatically generate a version when the BOE reaches the final workflow step to capture the authoritative baseline.
Provide the ability to view a list of all versions, including metadata such as creator, timestamp, workflow state, and an optional version label or comment.
Allow users to revert an active BOE to any prior version, restoring both structured data and text content from that version.
Implement change tracking or highlighting for text fields (e.g., descriptions, justifications) between selected versions, clearly calling out additions, deletions, and modifications.
Respect existing workflow rules and permissions so that only authorized users can create, revert, or compare versions.
Benefits:
Reduces risk by letting users safely experiment and rollback to stable versions when needed.
Improves auditability and review by making it clear what has changed between versions, especially in narrative text.
Enhances workflow flexibility, as users can create logical checkpoints throughout the process rather than only at completion.
Speeds reviews and approvals by providing clear version history and text change visibility, reducing back-and-forth clarification.
Increases user confidence and satisfaction by giving them finer control over BOE versioning and change tracking.