Page Comparison

...

1. Create a revision. All revisions should use DEV as their source environment.

   

   1. Select your revision elements

      1. If making role changes, be sure to include all objects in any VDB associated with that role so the necessary VQL for permissions updates is generated

      2. DO NOT promote the dev role when promoting to STAGE or PROD. Create and promote a read role instead. This will ensure that all VDB’s/Object are read only outside of the dev environment.

   2. Give revision a name and description and save

   3. Create a row in the Revision Tracker below for your revision

2. Have a peer review the revision and add their name under the Approved By column in the Revision Tracker once approved.

3. Deploy the revision to STAGE and perform smoke testing

4. If smoke testing passes, deploy to PROD

5. If smoke testing fails, investigate, then create a new revision to address the issues

...