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 March 8” so we can address it prior to the Thursday, March 9, 2023 release to Production.
Keep up with our future enhancements here: EAH Bugs and Enhancements In Progress
Table of Contents
| Table of Contents |
|---|
Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report.
Thank You Report Developers!
Special thanks to the report developers who submitted enhancement requests.
- Brian Lorentz
- David Mandell
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.
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.
ITS-BIA will allow a transition period for report developers to repoint their reports at the new fields / views.
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.
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 - Fields to be retired.
- Employee Preferred Name fields. Employee Preferred Name will continue to show in the Employee Name fields with the Employee Legal Name showing where no preferred name has been indicated. Anyone using the Employee Preferred Name fields should use the Employee Name fields.
Employee Preferred Display Name AsOf replace with Employee Display Name AsOf
Employee Preferred Display Name Current replace with Employee Display Name Current
Employee Preferred First Name AsOf replace with Employee First Name AsOf
Employee Preferred First Name Current replace with Employee First Name Current
Employee Preferred Last Name AsOf replace with Employee Last Name AsOf
Employee Preferred Last Name Current replace with Employee Last Name Current
Employee Preferred Middle Name AsOf replace with Employee Middle Name AsOf
Employee Preferred Middle Name Current replace with Employee Middle Name Current
Employee Preferred Name AsOf replace with Employee Name AsOf
Employee Preferred Name Current replace with Employee Name Current
Employee Preferred Name Prefix AsOf replace with Employee Name Prefix AsOf
Employee Preferred Name Prefix Current replace with Employee Name Prefix Current
Employee Preferred Name Suffix Code AsOf replace with Employee Name Suffix Code AsOf
Employee Preferred Name Suffix Code Current replace with Employee Name Suffix Code Current
Step 4 - Field retirement.
- Employee Phone Number Current will be replaced by Employee Home Phone Number Current
- Employee Phone Number AsOf will be replaced by Employee Home Phone Number AsOf
| Ui expand | ||
|---|---|---|
| ||
Coming Soon: EAH-UCLC-PersonTraining-View
BIA and the UCPath Reporting Project Team are excited to release a new view that will allow reporting around employee required UC Learning training. This will allow automated verification of training compliance and allow automated removed of access when employee certification has expired.
New View Going to Production March 9: EAH-ApprovalDirectRetroDetail-View
BIA and the UCPath Reporting Project Team are excited to release a new view that will allow reporting around the details of approval direct retro transactions. This view shows approval status, requester identity, direct retro transaction number, direct retro CCOA fields, direct retro earnings amounts and more.
Per our regular release for new views, EAH-ApprovalDirectRetroDetail-View will remain in UAT for an extended period and go to Production in our March release in order to provide additional UAT time.
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
EAH-ApprovalDirectRetroDetail-ViewEpic:
SNOW ticket(s) addressed: UCPath Reporting Added the following new fields:
|
View Your Requested Enhancements
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
EAH-JobCodeSalaryPlan-ViewEpic:
SNOW ticket(s) addressed: Added the following new fields: CS1358549
|
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
EAH-JobEarnsDist-ViewEpic:
SNOW ticket(s) addressed: CS1262966 Added the following new fields:
|
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. |
| Warning |
|---|
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.
|
Follow our Enhancement Testing Steps
| Tip |
|---|
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.
If you find an issue, please include in your email to busintel@ucsd.edu the following:
|