The user needs to archive the last five versions of a scenario for one year.
Archiving ensures there is a record of previous versions in case rollback or review is needed.
Option Analysis:
A. Save the scenario frequently:
Incorrect. While frequent saving ensures changes are not lost, it does not provide an archival mechanism for version history.
B. Download the scenario blueprints:
Correct. Downloading blueprints of the scenario allows the user to store version snapshots externally. Blueprints include the complete design and settings of the scenario, making them ideal for archival purposes.
C. Clone the scenario anytime the design changes:
Incorrect. Cloning creates duplicates of the scenario but does not inherently manage or track version history for archival purposes.
D. Find previous versions using the History tab:
Incorrect. The History tab only shows recent edits and logs but does not provide a long-term archiving solution.
Why Downloading Blueprints is Best:
External Storage: Blueprints can be downloaded and stored securely for long-term use.
Restoration: A saved blueprint can be re-imported into Fusion to restore a scenario exactly as it was.
Version Control: Allows the user to manually manage and organize multiple scenario versions over time.
Implementation Steps:
Go to the scenario in Workfront Fusion.
Use theDownload Blueprintoption to save a copy of the scenario.
Label and organize the blueprints by version and date for easy retrieval later.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit