Hello SAH Developers - The below enhancements are available for you in Hana QA now. If you find an issue, please email busintel@ucsd.edu prior to end of day Wednesday, January 26 so we can address it before the Thursday, January 27 release.
Keep up with our future enhancements here: SAH Bugs and Enhancements In Progress.
For access to the Student Activity Hub (SAH) you must be pre-approved by the registrar's office. Please reach out to them directly.
Table of Contents
P4 - High Security Level Fields
Update: Upon further testing, BIA has determined that the Tableau column based security implementation does not meet our security standards. Therefore, BIA will be removing the P4 fields from Tableau until a new security implementation can be determined. The Cognos column based security implementation both meets our security standards and meets our customer needs, therefore it will be available in Cognos DEV (now), Cognos QA (starting Jan 27) and Cognos Production (starting Jan 27).
Each Activity Hub Field has a security level associated with it. Security levels are defined by the University Of California Office of the President (UCOP) and assigned Data Stewards. For more information visit the Policies section under System Information Security on the UCOP webpage, ucop.edu. Security Levels can be found under Protection Level Classification. A full list of P4 fields can be found below in the SAH-Demographics-View and SAH-StudentStatsPerTerm-View.
To access P4 fields as a report developer or report consumer you must be a member of a P4 Active Directory Group for that Activity Hub and/or data source. As P4 fields are added to Activity Hubs new Service Now request forms will be created to request access. This access is separate from access to run reports, view reports or build reports.
Report developers are responsible for the content they add to their reports and the audience they share the report with. Active Directory (AD) Groups are used at multiple levels: (1) at the SAH data source / package level, (2) at the report folder and (3) at the P4 field. The table below show the expectations of what reports developers and report consumers should expect to see.
| User | Cognos | Tableau |
|---|---|---|
| Report Consumer in a P4 AD Group | Will see the P4 fields and values in the reports they can run. | Will see no P4 fields. |
| Report Consumer outside a P4 AD Group | Will see an error message. | Will see no P4 fields. |
| Report Developer in a P4 AD Group | Will see the P4 fields and values. | Will see no P4 fields. |
| Report Developer outside a P4 AD Group | Will not see any P4 fields. | Will see no P4 fields. |
More information can be found in the Analytics Community of Practice collab.
Renaming and Deprecating
As we've adapted the SAH 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. In a previous release we set the old fields to null, this release we will be deleting the out-going fields.
Permanent Address Country Code
Permanent Address Country Name
Permanent Address State
Permanent Address Zip
Pell Awarded Date
Pell This Term Count
Pell This Term Flag
Pell This Term or Past Term Count
Pell This Term or Past Term Flag
Your Requested Enhancements!
Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report.
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
SAH-Admission-ViewEpic:
Added the following fields:
|
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
SAH-Demographics-View & SAH-Demographics-IR-ViewEpic:
Added the following fields:
|
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
SAH-Enrollment-View and SAH-EnrollmentCensus-ViewEpic:
Added the following fields:
|
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
SAH-StudentSchedule-ViewEpic:
Added the following fields:
|
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
SAH-StudentStatsPerTerm-View & SAH-StudentStatsPerTermCensus-ViewEpic:
Added the following fields: Ethnicity Afghan Count P4 |
| Ui expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
SAH-LMS-CB-StudentCourseStatsPerTerm-ViewEpic:
Added the following 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. |
Follow our Enhancement Testing 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:
|