Enable historical versioning of an itinerary
Jason Bragg
Problem statement
As a User I want Tourwriter to save versions of an itinerary so I can refer to an older version at a later date and compare/explain changes
Background
This concept introduces a completely new feature, 'Versioning,' designed explicitly to keep a historical record of an itinerary without cluttering up the database with duplicate records. This would allow users to record the current state of a 'live' itinerary before making changes, ensuring a historical record is retained within the same itinerary.
- A new action (e.g., 'Save Version') would save the current state of the itinerary, creating a read-only historical record. All subsequent changes would apply to the live itinerary.
- Historical versions remain linked to the single main itinerary and are read-only.
This solution would prevent the need to create multiple separate documents for the same client and trip, leading to cleaner data management and a clearer audit trail of changes.
R
Right Penguin
good idea.
At the moment, i have to create several separate itineries for the same client...in case the client finally want the first version.
"a read-only historical record."
But how is working if an oldest version have been selected by the traveler ?
the itinerary can't stay "read-only".
We should have the choice to "re activate" this itinerary.
Jason Bragg
Right Penguin: Great questions.
The use case you explain above relates more to this request i think. https://tourwriter.canny.io/feature-requests/p/duplication-feature-needs-more-include-exclude-fields-when-duplicating
When providing duplicate versions of an itinerary to a prospect you want to keep the chosen version active and then archive the Closed Lost versions once the prospect has confirmed. Historical versioning has a slightly different use case, hence the 2 different posts.
We plan to solve both requests with different feature but want to be sure we arent missing anything so thanks for your comments.