Hello RAH Report Developers - The below enhancements are included in this month's RAH Release.
Keep up with our future enhancements here: RAH Bugs and Enhancements In Progress.
Learn more about the Research Activity Hub in the RAH Quick Start Guides.
Table of Contents |
---|
Schedule
Thursday, January 19, end of day: release enhancements to User Acceptance Testing
Thursday, January 25, end of day: release enhancement to Production
Friday, January 26, end of day: delete QA models
Thank You Report Developers!
Special thanks to the report developers who submitted enhancement requests.
- Rehan Ahmed
- Ernesto Donate
- Cheryl Kettnich
Mail List Change
This month BIA will start migrating our mail lists out of Emma and into Google Groups. Our goal is to improve our communication efficiency and allow you all to benefit from announcements made by source systems when relevant. This will require us to manually add everyone from the current list to the new Google Group. You will all receive a notification that you have been added. If you are member of multiple BIA mail lists then you will be notified as you are added to each new one. We apologize for the extra email notifications.
Using Google Groups you will still be able to leave and join our mail lists. We will be adding instructions to our collab site.
New View: RAH-PDProposalPersonDetail-View
BIA and OCGA are excited to release the RAH-PDProposalPersonDetail-View. This new view has more details than the RAH-PD-View but less details than the RAH-PDDetail-View. Per report developer request, this view will allow reports to run faster as removing questionnaire data creates a smaller data set. Per our standard release process this view will remain in UAT until our next standard release in January 2024.
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Enhancements will address the following SNOW tickets: CS1745029 and CS1755478
Fields included in this view: Same fields as RAH-PDDetail-View less the Proposal Questionnaire fields.
Your Requested Enhancements!
Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report.
Financial Unit Fields
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Enhancements will address the following SNOW tickets: CS1779352
Added the following fields:
Financial Unit
Financial Unit Code
Financial Unit Code and Name
Financial Unit Effective End Date
Financial Unit Effective Start Date
Financial Unit Is Current Count
Financial Unit Is Current Flag
Financial Unit L1
Financial Unit L1 Code
Financial Unit L1 Code and Name
Financial Unit L2
Financial Unit L2 Code
Financial Unit L2 Code and Name
Financial Unit L3
Financial Unit L3 Code
Financial Unit L3 Code and Name
Financial Unit L4
Financial Unit L4 Code
Financial Unit L4 Code and Name
Impacted Views:
- RAH-Award-View
- RAH-AwardDetail-View
- RAH-IP-View
- RAH-IPDetail-View
- RAH-PD-View
- RAH-PDDetail-View
- RAH-PDProposalPersonDetail-View
RAH-Subaward-View
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Enhancements will address the following SNOW tickets: CS1854825
Added the following fields:
Subaward Version Updated Date
Subaward Version Updated DateTime
RAH-SubawardInvoice-View
Epic:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Enhancements will address the following SNOW tickets: CS1854825
Added the following fields:
Subaward Invoice Status Update Date
Subaward Version Updated Date
Subaward Version Updated DateTime
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. |
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 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. |