Before your server will accept various saved versions of projects into the database, you must create the versions through the Admin interface. The default version of any project saved to the server is dot-published, where “dot” is a period (.) character. You may define additional versions as archived or nonarchived, the difference between the two mainly being that nonarchived versions may be edited whereas archived versions may not.
Be clear that because the published version is the system’s default version, all projects that are saved to the server are visible within the system views to the extent that their assignments have been published. You must always use the published version for reporting and tracking, as data doesn’t flow to any other version in the system. You may use versions for planning and then save an alternate nonarchived version as the new published version by overwriting the currently published version. In this way, you can leverage versions during the planning process.
Another substantial use for versions is in the Portfolio Modeler where nonarchived versions of projects are available to create portfolio models for what-if analyses. I cover the Portfolio Modeler at length in Chapter 16. Archived versions are useful for preserving historic snapshots of project plans and project templates. Maintaining current archived copies of templates is particularly important, as these are vulnerable to inadvertent changes.
To create a new version, select “Manage enterprise features” from the Admin menu, and then select Versions from the left submenu. This displays the Versions interface shown in Figure 9-19. Highlight an existing version to delete or modify it. To add a new version, click Add Version.
Figure 9-19. The Versions interface
Clicking Add Version opens the Add Version interface shown in Figure 9-20. You provide a name for the version, determine whether it’s an archive or nonarchive version, and select which Gantt Bar to use when displaying the version.
Figure 9-20. The Add Version interface