Hello EAH Developers - The below enhancements are included in this month's EAH Release.
Keep up with our future enhancements here: EAH Bugs and Enhancements In Progress
Learn more about the Employee Activity Hub in the EAH Quick Start Guides.
Table of Contents
Table of Contents |
---|
Schedule
Thursday, October 10: release enhancements to User Acceptance Testing
Thursday, October 17 end of day: release enhancement to Production
Friday, October 18, end of day: delete QA models
Thank You Report Developers!
Special thanks to the report developers who submitted enhancement requests.
- Rehan Ahmed
- Kacy Cashatt
- Jonathan Matsen
- John Porter
- Shawn Pappelbaum
- Daniel Redfern
- Heather Sears
New View
EAH-HRLocation-View
BIA and the UC Path Reporting team are excited to release the EAH-HRLocation-View. This view contains all of the possible active locations in UC Path.
This view will be part of the EAH Core views but have no row level security. This view will be going to Production in October 2024.
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
SNOW tickets addressed: CS2120862
Fields include:
- HR Location
- HR Location Address Line 1
- HR Location Address Line 2
- HR Location Address Line 3
- HR Location Building Code
- HR Location City
- HR Location Code
- HR Location Country
- HR Location Country Code
- HR Location County
- HR Location Effective Date
- HR Location End Effective Date
- HR Location Floor Code
- HR Location Postal Code
- HR Location Set Code
- HR Location State
- HR Location State Code
View Your Requested Enhancements
Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report.
EAH-ApprovalDirectRetroDetail-View & EAH-ApprovalSalaryCostTransferDetail-View
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
SNOW ticket(s) addressed: CS2149909
Added the following new fields:
- LL Salary Posted to Financials Count
- LL Salary Posted to Financials Flag = When DR number has at least one line in LL Salary with a "LL_Salary_In_Process_Code" = 'M', then Y, else N
EAH-GradTuitionEligibility-View
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
SNOW ticket(s) addressed: CS2088169, CS2184930
Added the following new fields:
- Graduate Advanced to Candidacy in a Masters Program Count
- Graduate Advanced to Candidacy in a Masters Program Flag
- Graduate Advanced to PHD Candidacy Non-Resident Waiver Count
- Graduate Advanced to PHD Candidacy Non-Resident Waiver Count Current
- Graduate Advanced to PHD Candidacy Non-Resident Waiver Flag
- Graduate Advanced to PHD Candidacy Non-Resident Waiver Flag Current
- Medical Primary Major Department
- Medical Primary Major Department Code
- Medical Primary Major Department Code Current
- Medical Primary Major Department Current
- Pharmacy Primary Major Department
- Pharmacy Primary Major Department Code
- Pharmacy Primary Major Department Code Current
- Pharmacy Primary Major Department Current
- Student Residency Status
- Student Residency Status Code
- Student Residency Status Code Current
- Student Residency Status Current
- Student Residency Status End Term Code
- Student Residency Status Start Term Code
- UG Primary Major Department
- UG Primary Major Department Code
- UG Primary Major Department Code Current
- UG Primary Major Department Current
EAH-GradWorkPeriodDetail-View
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
SNOW ticket(s) addressed: CS2088169, CS2184930
Added the following new fields:
- Graduate Advanced to Candidacy in a Masters Program Count
- Graduate Advanced to Candidacy in a Masters Program Flag
- Medical Primary Major Department
- Medical Primary Major Department Code
- Medical Primary Major Department Code Current
- Medical Primary Major Department Current
- Pharmacy Primary Major Department
- Pharmacy Primary Major Department Code
- Pharmacy Primary Major Department Code Current
- Pharmacy Primary Major Department Current
- Student Residency Status Code Current
- Student Residency Status Current
- UG Primary Major Department
- UG Primary Major Department Code
- UG Primary Major Department Code Current
- UG Primary Major Department Current
EAH-LLFringeDetail-View, EAH-LLSalaryDetail-View and EAH-LLSalaryFringeDetail-View
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
SNOW ticket(s) addressed: CS2114043, CS2199451
Added the following new fields:
- Most Recent Reports To Department Code
- Most Recent Reports To Employee ID
- Most Recent Reports To Employee Record
- Most Recent Reports To Employee Status Code
- Most Recent Reports To Identity Active Directory ID Current
- Most Recent Reports To Job Code
- Most Recent Reports To Organizational Relationship
- Most Recent Reports To Position
- Most Recent Reports To Position Number
- Most Recent Reports To Work Email Address
- Most Recent Reports To Employee
- Project Nickname
EAH-PositionBudgetComparisonSummary-View
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
SNOW ticket(s) addressed: CS2161857
Added the following new fields:
CBO is requesting a logic update for EPBCS Budget Data loaded to HANA for EAH. Records exist within the EPBCS load file without a Position Budget Type assigned when certain conditions are met (details below). We need all records to have a Position Budget Type of Recurring or One-Time in the PositionBudgetComparisonSummary-View.
CASE 1: [Position Budget Type] = ‘#missing’ for [Employee] = ‘PooledEmp’ when: [Period] = ‘Jul-Jun’ [Scenario] = ‘Base_Bugt’ or ‘BudgetRequest’
CASE 2: [Position Budget Type] = ‘#missing’ for [Employee] = ‘VacancyNew’ when: [Period] = ‘Jul-Jun’ [Scenario] = ‘Dist_Bud_Req’
EPBCS only assigns a Position Budget Type when [Period] = ‘BegBal’. The Position Budget Type value for [Period] = Jul-Jun records should be either ‘One-Time’ or ‘Recurring’ based on the [Period] = BegBal row for the same FinU-Fund-Function-Project-Position intersection.
UAT - Customer Service Reminder
Warning |
---|
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 User Acceptance Testing (UAT) Steps
Tip |
---|
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.
If you find an issue, please include in your email to busintel@ucsd.edu the following:
Reminder: QA data sources will be deleted the Friday after the enhancements are migrated to Production. |