Page Comparison

...

1. Check the ESR SIS Report Inventory to see if your report is included in the ESR SIS Report Remediation project.

   1. If yes then no further action.

   2. If no then continue to #2.

2. Identify the SAH Report Developer who will be rebuilding the report (it may be you).

3. Compare the fields in the report with the current fields in SAH via the Activity Hub Field List report.

   1. Note, this report is available to everyone and contains all of the fields in all of the Activity Hubs so it takes a minute to initially load.

4. The SAH Report Developer emails busintel@ucsd.edu asking to have their list of missing ISIS fields added to SAH.

   1. This will open a SNOW ticket with the BIA team. BIA will keep you updated via this SNOW ticket.

   2. Please include the original source location from ISIS.

   3. If the source is not ISIS please check the Long Term Solution - Adding Data to Activity Hub data source list to see if your source has been requested.full list of /wiki/spaces/SAH/pages/18350895 that BIA is aware of.

      1. If your source is not on that list, email busintel@ucsd.edu to request that it be added.

      2. You can explore Interim and Short Term reporting solutions here: Adding New Data for Blending in Cognos or Tableau .

Steps for the BIA Team to address SAH Report Developer request

5. The BIA team meets with Jonathan Whitman’s technical team to talk about the missing field.

   1. The field may not from ISIS. If so, the field is evaluated for it’s impact to the ESR SIS Report Remediation project.

   2. The field may be calculated in the DW. If so, the calculation is investigated.

   3. The field may be in ISIS, but nobody has asked for it yet.

   4. BIA will update the customer’s SNOW ticket with information found and if the field can be included in the SIS Remediation project.

      1. If the field is not from SIS then it will customer will need to wait until the SIS Remediation is complete or request an exception to the freeze.

6. The BIA team bring the ISIS field to the /wiki/spaces/SAH/pages/18354378.

   1. The field may no longer be in use. If so, the ESR SIS Report Remediation project manager is notified.

   2. If the field is in use, a field name and description is identified, and the data source is confirmed.

   3. BIA will update the customer’s SNOW ticket with information found and if the field can be included in the SIS Remediation project.

      1. If the field is not from SIS then it will customer will need to wait until the SIS Remediation is complete or request an exception to the freeze.

7. Then the new field is added to SAH Enhancement Monthly Release.

   1. If the field is not yet in SAH then it will need data integration and will not be scheduled for a SAH enhancement release until the data integration is complete.

   2. If the field is already in SAH but not viable to customers the field will be added to the next SAH enhancement release.

   3. BIA will update the customer’s SNOW ticket with the expected release date.

8. Once the missing fields have been added to SAH the SAH Report Developer can then rebuild the report in Cognos or Tableau.

   1. BIA will update and close the customer’s SNOW ticket once the field is in Production.

To see a list of SAH Enhancements In Progress visit SAH Bugs and Enhancements In Progress .

...