20221006 EAH Start UAT Release Notes

20221006 EAH Start UAT Release Notes

Hello EAH Developers - The below fields are now available for you in UAT.  If you find an issue, please email busintel@ucsd.edu right away with the subject line “EAH UAT due October 12” so we can address it prior to the Thursday, October 13, 2022 release to Production.

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





Thank You Report Developers!

Special thanks to the report developers who submitted enhancement requests. 

  • Rehan Ahmed

  • Wilson Cheung

  • Marcus Lazaldi



Renaming and Deprecating

As we've adapted the EAH 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.

Step 1&2 - Announcing that this field will be retired.  Step 3 - Field to be retired has been set to null.

  • Employee Display Name will be replaced by Employee Display Name Current



View Your Requested Enhancements



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.

A duty cycle has been implemented for Hana QA.  During this time, Hana QA will not be available.  Please schedule your UAT work around this duty cycle.

  • Hana QA will not be available from 7pm-5am nightly

  • Hana QA will not be available Saturday and Sunday

  • Data loads will occur from 5am-10am on weekdays