Configuration data version labels examples
The following table shows two version labels, VersionLabel_1 and VersionLabel_2, and some samples of their associated changes and timestamps:
|Version Label||Audited Changes||Timestamp|
|Org1 is created.||5/1/2007 9:00|
|Org2 is created.||5/1/2007 9:10|
|Org1's DefaultFulfillmentType is updated from "A" to "B"||5/1/2007 9:30|
|Org1's DefaultFulfillmentType is updated from "B" to "C"||5/1/2007 9:40|
|Org2 is deleted||5/1/2007 9:50|
|Org3 is created||5/1/2007 10:00|
|Org4 is created||5/1/2007 10:20|
You can obtain the changes based on the configured version labels in the Sterling Development and Deployment WorkBench, including both forward and backward changes.
These are changes from an earlier version label to a later version label (or the latest changes).
In this case, it can be from VersionLabel_1 to VersionLabel_2 or Version Label_1 to current timestamp. This can be used in the scenario where users want to capture the certain changes from one system and deploy those changes onto another system.
Forward changes example
Using the Version Labels table as the basis for this example, if the user wants to obtain changes from VersionLabel_1 to VersionLabel_2, the following changes will be captured to be applied later on another system:
|Changes to be Applied|
|Update Org1's DefaultFulfillmentType from “A” to “C”|
These are changes from the current time to an earlier version label.
The audit data will be translated in the reverse logic as the changes to be applied later.
Backward changes example
Using the Version Labels table as the basis for this example, if a user wants to obtain all changes from the current timestamp to VersionLabel_1 so that those changes can be used in rolling back all changes modified after VersionLabel_1. The following changes will be obtained.
|Update Org1's DefaultFulfillmentType from “C” to “A”|