Version Tracking of Deployments

Oracle Retail Xstore Office creates and tracks version numbers for each set of configurations that are deployed at the Master Profile (Global) level, at a more granular Profile Group/Profile Element level, or at a Store-Specific level.

  1. When a configuration change is saved to a profile (this could be Master/Default, a specific profile element, or a store-specific profile), a version number is assigned to the change.

    1. Version numbers start at 1 and increment by 1. 1 is the first version for a profile element, 2 is the second version, and so on.

    2. Additional changes made to the same profile will continue to accumulate with the same version number until deployment for the profile is scheduled.

  2. When deployment for a profile is scheduled, the current profile version is "locked" to ensure that no new changes can be made to the version.

  3. After a profile version is locked, new changes made to the profile will use a new version number. If version 3 of a profile was locked, new changes will be assigned to version 4 up until the point where deployment for profile version 4 is scheduled.