Note: This feature is available in SharpCloud versions 9.1.011 and later
Story archiving allows you to create a frozen snapshot of a story at a given point in time, providing a historic version of the story that can’t be amended. This is valuable to see previous versions of a story, allowing a comparison to take place between previous versions and the current version.
Note: Archiving a story can be performed on a story in an Enterprise Solution, but it will generate an archived story that does not exist within the Enterprise Structure, so some functionality may be lost because of this.
Creating an Archived Version of a Story
To create an archived story, you must have owner permissions on the story. Admins can view what archives have been made but will not be able to create any archived versions.
To create a story archive, open the Story Setup menu and navigate to the History tab. Click the “Archive” button as highlighted below and enter a name for your archived story in the dialog box that appears.
Once the archive is processed, you will receive an email informing you that the story is ready to view.
A Read-Only archive copy of the story is now available for viewing. If you wish to delete an archive version of a story, you can perform the delete story function as normal from within the archived copy and it will be removed from your archives.
Viewing the Archived Story
The archived story does not allow any changes to be made, but still provides the options to see the story setup, data grid and view setup.
In the archived story, you still have access to the history tab to view other archives or the most recent story.
What’s not included in the archived story?
The only information that is not carried over in a story archive is the Activity Feed and Comments. In the active story that the archive was made from, the activity feed and comments are scrollable through time so the information can always be found there.
Any Enterprise specific functionality will not function in the archived story as the archived story will not be linked into the relevant Enterprise Structure.