20220609 EAH Start UAT Release Notes

Owned by Saparnell
Last updated: Jun 09, 2022

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 June 15” so we can address it prior to the Thursday, June 16, 2022 release to Production.

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


Table of Contents

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


New View Going to UAT: EAH-ApprovalWorklist-View

BIA and the UCPath Reporting team are excited to release a new view that will allow report building against the approval workflow process. 

Per our regular release for new views, EAH-ApprovalWorklist-View will remain in UAT for an extended period and go to Production in our July release.


New View Going to Production: EAH-PositionBudgetComparisonSummary-View

BIA and CBO is excited to release a new view that will allow report building against the position budgeting subsystem: https://blink.ucsd.edu/finance/budget/oracle-planning-and-budget.html

Per our regular release for new views, EAH-PositionBudgetComparisonSummary-View will remain in UAT for an extended period and go to Production in our June release.

Renaming & 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.  *Any reports or data integrations using these fields as filters or joins will break.
  4. ITS-BIA will deprecate the fields / views.  Any reports the have not transitioned by this point will break.  *Any reports or data integrations using these fields will break.

We'll be using this strategy on the following items that require name changes.  Step #3 is starting for the following fields:

  • EVerify Flag AsOf will be replaced by Employee EVerify Flag AsOf
  • EVerify Count AsOf will be replaced by Employee EVerify Count AsOf
  • EVerify Date AsOf will be replaced by Employee EVerify Date AsOf
  • EVerify Exemption Flag AsOf will be replaced by Employee EVerify Exemption Flag AsOf
  • EVerify Exemption Count AsOf will be replaced by Employee EVerify Exemption Count AsOf
  • EVerify Exemption Date AsOf will be replaced by Employee EVerify Exemption Date AsOf
  • I9 Completion Flag AsOf will be replaced by Employee I9 Completion Flag AsOf
  • I9 Completion Count AsOf will be replaced by Employee I9 Completion Count AsOf
  • I9 Completion Date AsOf will be replaced by Employee I9 Completion Date AsOf
  • Statement Of Economic Interests Date AsOf will be replaced by Employee Statement Of Economic Interests Date AsOf
  • Statement Of Economic Interests Flag AsOf will be replaced by Employee Statement Of Economic Interests Flag AsOf
  • Statement Of Economic Interests Count AsOf will be replaced by Employee Statement Of Economic Interests Count AsOf
  • EVerify Flag Current will be replaced by Employee EVerify Flag Current
  • EVerify Count Current will be replaced by Employee EVerify Count Current
  • EVerify Date Current will be replaced by Employee EVerify Date Current
  • EVerify Exemption Flag Current will be replaced by Employee EVerify Exemption Flag Current
  • EVerify Exemption Count Current will be replaced by Employee EVerify Exemption Count Current
  • EVerify Exemption Date Current will be replaced by Employee EVerify Exemption Date Current
  • I9 Completion Flag Current will be replaced by Employee I9 Completion Flag Current
  • I9 Completion Count Current will be replaced by Employee I9 Completion Count Current
  • I9 Completion Date Current will be replaced by Employee I9 Completion Date Current
  • Statement Of Economic Interests Date Current will be replaced by Employee Statement Of Economic Interests Date Current
  • Statement Of Economic Interests Flag Current will be replaced by Employee Statement Of Economic Interests Flag Current
  • Statement Of Economic Interests Count Current will be replaced by Employee Statement Of Economic Interests Count 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.

Follow our Enhancement Testing Steps

Please use this UAT time to adjust your reports as needed prior to the Production release when your customers will be able to see any issues these enhancements cause. 
  • In Cognos DEV open your report and replace the current package with the package of the same name from the Team Content > Employee Activity Hub > EAH Analytics Packages UAT folder.  Run the report and select Hana QA.  Do not select Hana Prod as the report will fail.  Using the new package from the EAH Analytics Packages UAT folder will allow you to see the below enhancement.  EAH data is the same in Hana Prod and Hana QA.
  • Sign into Tableau Prod 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.  Replace the original data source with the –QA data source.  Using the –QA data source will allow you to see the below enhancements.  EAH data is the same in Hana Prod and Hana QA. 

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? 
  • What data source / package are you using?
  • What results were you expecting?