2022-05-19 SAH UAT Release Notes

Owned by Saparnell
Last updated: May 20, 2022

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, May 25  so we can address it before the Thursday, May 26 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.


New Views: SAH-ClassComponentSchedule-View & SAH-ClassComponentScheduleCensus-View

ITS-BIA is excited to announce a new view focused on the details of each Class Section, regardless of class section enrollment.  While this new view does include Enrollment Count, it also include Class Sections with no enrolled student.  Details of each Class Section will be contained in Class Component fields.  New Course Code fields are also included in these new views.  These views were release to UAT during our April release and will be moving to Production during this May release.

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 strategy on the following items that require name changes.

May Step 3 - The following fields have been set to null:

  • Class Section IDs - will be replaced by Ever Enrolled Class Section IDs


May Step 4 - The following fields have been removed:

  • Class Section Enrollment Count - will be replaced by Enrolled At End of Term Count and Enrolled At Census Date Count 
  • Class Section Enrollment Flag - will be replaced by Enrolled At End of Term Flag and Enrolled At Census Date Flag
  • Earned Advanced Placement (AP) Units - will be replaced by Education Abroad Program (EAP) Passed Units Current Cumulative
  • Enrolled at Census Date Count Term - will be replaced by Enrolled At Census Date Count
  • Course Term End Date - will be replace by General Campus Term End Date
  • Course Term Start Date - will be replace by General Campus Term Start Date
  • Term End Date - will be replace by General Campus Term End Date
  • Term Start Date - will be replace by General Campus Term Start Date
  • Transfer Class Section Count - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View
  • Transfer Class Section Flag - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View
  • Transfer Entity ID - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View
  • Transfer Entity Name - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View
  • Waitlist Count Current - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View
  • Waitlist DateTime Current - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View
  • Waitlist Flag Current - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View
  • Waitlist Position Current - will be removed from SAH-EnrollmentCensus-View only as it is not needed at Census date, this field will remain available in the SAH-Enrollment-View

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?