Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Hello SAH Developers - The below enhancements are available for you in UAT for this week.  If you find an issue, please email busintel@ucsd.edu right away with the subject line “SAH UAT due August 25” so we can address it prior to the 3pm release to Production on Thursday, August 26.  Enhancements to SAH are always released to UAT on the third Thursday of each month. 

Because we are updating fields withing SAH-Demographics-View during this release our release to Production on Thursday, August 26 will be from 3pm-9pm PT.

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.


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.

  • "Enrollment Count" will be replaced by "Enrollment Record Count"
  • "Class Section Enrollment" will be replaced by "Class Section Enrollment Count"
  • "Permanent Address Country Code" will be replaced by "Permanent Address Country Code Current"
  • "Permanent Address Country Name" will be replaced by "Permanent Address Country Name Current"
  • "Permanent Address State" will be replaced by "Permanent Address State Current"
  • "Permanent Address Zip" will be replaced by "Permanent Address Zip Current"


 Renaming and Deprecating Calendar
Date
Status
August 19

The following fields will be release for UAT

  • "Enrollment Count"
  • "Class Section Enrollment"
  • "Permanent Address Country Code"
  • "Permanent Address Country Name"
  • "Permanent Address State" "
  • "Permanent Address Zip"

These fields will be migrated to Production on August 26

Complete
August 19 - September 23

Report developers will repoint their reports

  • "Enrollment Count" will be replaced by "Enrollment Record Count"
  • "Class Section Enrollment" will be replaced by "Class Section Enrollment Count"
  • "Permanent Address Country Code" will be replaced by "Permanent Address Country Code Current"
  • "Permanent Address Country Name" will be replaced by "Permanent Address Country Name Current"
  • "Permanent Address State" will be replaced by "Permanent Address State Current"
  • "Permanent Address Zip" will be replaced by "Permanent Address Zip Current"
In Progress
September 23

The following will display blank values in Hana QA for UAT

  • "Enrollment Count"
  • "Class Section Enrollment"
  • "Permanent Address Country Code"
  • "Permanent Address Country Name"
  • "Permanent Address State" "
  • "Permanent Address Zip"

These fields will display blank values in Production starting September 30


September 23 - October 21

End customers will see empty fields in reports that have not yet been repointed by report developers

Report developers will repoint their reports

  • "Enrollment Count" will be replaced by "Enrollment Record Count"
  • "Class Section Enrollment" will be replaced by "Class Section Enrollment Count"
  • "Permanent Address Country Code" will be replaced by "Permanent Address Country Code Current"
  • "Permanent Address Country Name" will be replaced by "Permanent Address Country Name Current"
  • "Permanent Address State" will be replaced by "Permanent Address State Current"
  • "Permanent Address Zip" will be replaced by "Permanent Address Zip Current"

October 21

The following will be deleted from Hana QA

  • "Enrollment Count"
  • "Class Section Enrollment"
  • "Permanent Address Country Code"
  • "Permanent Address Country Name"
  • "Permanent Address State" "
  • "Permanent Address Zip"

October 28

The following will be deleted from PROD causing any un-touched reports to break.

  • "Enrollment Count"
  • "Class Section Enrollment"
  • "Permanent Address Country Code"
  • "Permanent Address Country Name"
  • "Permanent Address State" "
  • "Permanent Address Zip"



Test Your Requested Enhancements!

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






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 Oracle 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 ISIS Production data.
  • Hana QA:  SNAH 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? 


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.

  • No labels