20210603 EAH UAT Start Release Notes
- Saparnell
From: Parnell, Sarah <saparnell@ucsd.edu>
To: EmployeeAnalytics-COP-l@ucsd.edu
Cc: ITS-BIA <its-bia@ucsd.edu>; ITS-DataIntergrationServices <ITS-DataIntergrationServices@AD.UCSD.EDU>; Beatrice Dormoy <bea@ucsd.edu>; Linardos, Nickolas <nlinardos@UCSD.EDU>; Lorentz, Brian <blorentz@ucsd.edu>
Subject: EAH Enhancements - UAT Start - due June 9
Hello EAH Developers - We are releasing the below Employee Activity Hub enhancements for you to test between now and end of day June 9. If you find an issue, please email busintel@ucsd.edu with a subject line "EAH UAT due June 9" right away so we can address it prior to the Thursday June 10 production release.
Keep up with our future enhancements here: EAH Bugs and Enhancements In Progress
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.
- 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 new strategy on the following items that require name changes:
- LL Project Manager Name will be replaced by Project Manager Name Full
- Position Funding Project Manager Name will be replaced by Project Manager Name Full
- Position Funding Task Manager Name will be replaced by Task Manager Name Full
| Date | Status | |
|---|---|---|
| June 3 | The following fields will be released for UAT
These fields will be migrated to production on June 10 | Completed |
| June 10 - July 8 | Report developers will repoint their reports
| Start Now |
| July 8 | The following will display blank values in Hana QA for UAT
The fields will display blank values in Production starting July 15 | |
| July 15 - August 5 | End customers will see empty fields in reports that have not yet been repointed by report developers Report developers will repoint their reports.
| |
| August 5 | The following will be deleted from Hana QA.
| |
| August 12 | The following will be deleted from PROD causing any un-touched reports to break.
|
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.
How to perform User Acceptance Testing (UAT):
- 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.
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:
- 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?
Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report.
Items marked with a double asterisk (**) will break Cognos reports only if you have these fields in your report.
| View | Enhancement | Epic |
|---|---|---|
| All views | Moved from initial UCPath UCOP files to new UCOP Reporting Instance. | |
| EAH-LLSalaryFringeDetail-View |
| EAHMAINT-1643 |
| EAH-LLSummary-View |
| EAHMAINT-1649 |
| EAH-PositionFunding-View |
| EAHMAINT-1645 |
If you cannot view the EAHMAINT links, please request access to Jira here: https://ucsdservicedesk.service-now.com/its?id=sc_cat_item&sys_id=9af5d148db514450008c9837db96190b
If you feel this email has reached you in error you can unsubscribe from this mail list by
- Enter https://mailman.ucsd.edu/mailman/options/EmployeeAnalytics-COP-l/YourEmailAddress into a browser
- Locate the Unsubscribe section on your screen and click Unsubscribe.
- You will receive an e-mail with "confirm" in the subject line. Follow the email's instructions to complete the unsubscribe process.
- For more information go here: https://blink.ucsd.edu/technology/email/services/lists/subscriber/index.html
Thanks for being awesome,
Sarah Parnell
Analytics Community of Practice Manager
Business Intelligence & Analytics | Information Technology Services | UC San Diego
https://ucsdcollab.atlassian.net/wiki/x/A4C0C
work cell: 858-354-9709
My pronouns [https://www.mypronouns.org/]: she/her/hers
“I take care of step 1 thru 3 so you can get to step 4 faster. What’s your step 1?” - Sarah