2022-01-20 SAH UAT Release Notes

Owned by Saparnell
Last updated: Jan 20, 2022
9 min read

Hello SAH Developers - The below enhancements are available for you in Hana QA now.  If you find an issue, please email busintel@ucsd.edu prior to end of day Wednesday, January 26 so we can address it before the Thursday, January 27 release.

Keep up with our future enhancements here: SAH Bugs and Enhancements In Progress. 

For access to the Student Activity Hub (SAH) you must be pre-approved by the registrar's office.  Please reach out to them directly.


P4 - High Security Level Fields

Each Activity Hub Field has a security level associated with it.  Security levels are defined by the University Of California Office of the President (UCOP) and assigned Data Stewards.  For more information visit the Policies section under System Information Security on the UCOP webpage, ucop.edu. Security Levels can be found under Protection Level Classification.  A full list of P4 fields can be found below in the SAH-Demographics-View and SAH-StudentStatsPerTerm-View.

To access P4 fields as a report developer or report consumer you must be a member of a P4 Active Directory Group for that Activity Hub and/or data source.  As P4 fields are added to Activity Hubs new Service Now request forms will be created to request access.  This access is separate from access to run reports, view reports or build reports.

Report developers are responsible for the content they add to their reports and the audience they share the report with.  Active Directory (AD) Groups are used at multiple levels: (1) at the SAH data source / package level, (2) at the report folder and (3) at the P4 field.  The table below show the expectations of what reports developers and report consumers should expect to see. 

UserCognosTableau
Report Consumer in a P4 AD GroupWill see the P4 fields and values in the reports they can run.Will see the P4 fields and values in the reports they can run.
Report Consumer outside a P4 AD GroupWill see an error message.Will see the P4 fields, all values will be null.
Report Developer in a P4 AD GroupWill see the P4 fields and values.Will see the P4 fields and values.
Report Developer outside a P4 AD GroupWill not see any P4 fields.Will see the P4 fields, all values will be null.

More information can be found in the Analytics Community of Practice collab.

Renaming and Deprecating

As we've adapted the SAH views to your needs, we have found changing field names is painful for both report developers and our team due to the name change breaking reports, data integrations and packages / data sources.  In an effort to avoid this pain, we are going to introduce a new name change strategy. 

  1. ITS-BIA will release new fields with the revised field name in the views that contain the field to be renamed, or where a view is to be renamed ITS-BIA will release as a new view the view with the revised name.

  2. ITS-BIA will allow a transition period for report developers to repoint their reports at the new fields / views.

  3. ITS-BIA will remove the data from the old fields / views and allow a second transition period.  This will not break the report but will highlight where the fields / views are still in use as they will become blank.

  4. ITS-BIA will deprecate the fields / views.  Any reports the have not transitioned by this point will break.

We'll be using this new strategy on the following items that require name changes.  In a previous release we set the old fields to null, this release we will be deleting the out-going fields.

  • Permanent Address Country Code

  • Permanent Address Country Name

  • Permanent Address State

  • Permanent Address Zip

  • Pell Awarded Date

  • Pell This Term Count

  • Pell This Term Flag

  • Pell This Term or Past Term Count

  • Pell This Term or Past Term Flag


Your Requested Enhancements!

Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report.



Customer Service Reminder

Data in UAT is not ready to be shared with end customers, is not considered completely validated and can change suddenly.  For optimal customer satisfaction, do not connect your production solutions to packages / data sources that are in UAT.  If you choose to share UAT items with end customer, be explicit that the data and report is in UAT and can change suddenly or be broken by UAT changes.

Follow our Enhancement Testing Steps

Use this UAT time to adjust your reports as needed prior to the Production release where your customers will be able to see any issues these enhancements cause. 
  • Cognos: Use the packages in Cognos DEV > Student Activity Hub > Student Activity Hub Packages UAT to build your report and select Hana QA.  Do not select Hana Prod as the report will fail.  Using Hana QA will allow you to see the below enhancements with Production data. 
  • Tableau: Sign into Tableau on your Tableau desktop tool and open your report.  Add a new data source with the same name and -QA at the end of the title.  Using this data source will allow you to see the below enhancements with Production data.
  • Hana QA:  SAH data in Hana QA is production data loaded daily, just like in Hana PROD.

If you find an issue, please include in your email to busintel@ucsd.edu the following:

  • What browser are you using?
  • What environment are you using?  Cognos DEV, QA or PROD?  Or Tableau?
  • What data source / package are you using?
  • What results were you expecting?Â