Policy versioning

When a policy is newly created, or is saved under a new name, that policy is saved as version 1.0. Each time a policy is saved under the same name, a new version number is suggested by the policy editor, with the number to the right of the period automatically incremented (1.1, 1.2, and so on). You can change this number before saving. The number to the left of the period can also be changed by the user, but is never automatically incremented. The largest number available is 9999.9999.

The policy with the largest version number is considered to be the newest version of the policy. Other factors, such as creation date, are not considered. You cannot save a policy with a version number that already exists for that policy name.

NOTE:
The numbers to the right and left of the period are both regarded as integers, and any leading zeros are ignored. This means that 0.10 is a more recent version than 0.9, and that 0.01 is identical to 0.1.

Because each saved version of a policy has a different version number, you can access any previously saved version of a policy. These older versions can be edited or deployed just as any other policy.