...
Date | Revision | Author | Description | Approved By |
|---|---|---|---|---|
2023-06-12 | 32 | Add Clickstream to Prod | ||
2023-05-11 | 29 | Add Human Resources views and role needed. | ||
2023-05-03 | 24 | Add Class Enrollment views and role needed | ||
2023-04-18 | 22 | Updated Admissions view to use the new roles that were added | ||
2023-04-06 | 19 | Add scheduler job for Research Technology | ||
2023-04-06 | 18 | Updated Admissions view: some field names to use gs_ when specific to GSAS school | ||
2023-03-28 | 17 | Add Read Permissions with Dependencies | ||
2023-03-24 | 15 | Adds Admissions - Application Submitted view that is accessable by asg-admissions-read group | ||
2023-03-23 | 14 | Updates Oracle DW Connection to include failover via connection string | ||
2023-02-22 | 12 | Adds clickstream base view in student_lifecycle VDP and sets up for denodo-mkt AD group roles |
...
Create a revision. All revisions should use DEV as their source environment.
Select your revision elements
If making role changes, be sure to include all objects in any VDB associated with that so the necessary VQL for permissions updates is generated
DO NOT promote the dev role when promoting to STAGE or PROD. This will ensure that all VDB’s/Object are read only.
Give revision a name and description and save
Create a row in the Revision Tracker below for your revision
Deploy revision to STAGE
Have a peer review the revision and add their name under the Approved By column in the Revision Tracker once approved.
Deploy the revision to PROD