Reminder

All Sessions are Recorded and saved to the OneDrive location listed above.

Open Q&A

Walkthrough of using Style Variables to hide columns on your report. High-level steps are:

1. Prompt: Create a value prompt (multi-select, checkbox, static values). The choices should list out all the columns in your report.
   Image Added

2. Variables: Create boolean (true/false) variables for each column that checks to see if the column name is in the checkbox prompt.
   Example calculation below in which “P_Report Fields” is the parameter, “Term” is one of the options in the prompt:
   ParamDisplayValue('P_Report Fields') contains 'Term'

3. Report: Set the Style Variable on each column. Set the variable conditional state to “False”, then set the “Box type” to “None” for both the header and the field.
   Image Added

4. To see the hidden field back on the report component (List) clear the conditional state.

Q: Does the user have the ability to save the report with their choices?
A: Yes. They can create a report view in their “My Content” or a to share it, create the view in a “Team Content”

Q: Data Module Error: Query Service internal error has occurred, please see the log for details.”
A: Submit a ticket to BIA (busintel@ucsd.edu)

Reminder

All Sessions are Recorded and saved to the OneDrive location listed above.

Cognos upgrade vs FP

Upgrade: has a larger impact

Fix Pack: address specific issues, must smaller impact

The reason for the FP: Qualys Vulnerability Scan is reporting all the Cognos environments running version 11.2.4 FP3 with a Level 5 vulnerability, need to update to IBM Cognos Analytics 11.2.4 FP4.

Update Cognos DEV with FP4 on Thursday 8/1 at 5pm-6pm

ETA on Cognos QA 8/7 and Cognos Prod 8/9

Performing UAT - This is the most important way to participate in AH growth

How to do UAT in Cognos

1. Logic enhancements

   1. Run the report using Hana Prod, run the report using Hana QA, compare the results

   2. Recommend using 2 browsers, one for using Hana QA and one for using Hana Prod

   3. Recommend running to Excel and use vlookup to compare, if QA = Prod then FALSE (issue found)

   4. Recommend running to Excel and put in same tab then sort same, if QA = Prod then FALSE (issue found)

2. New fields

   1. Will only exist in Hana QA so you have to use a QA/UAT package

   2. Option 1: start a new report, select Hana QA

   3. Option 2: add to an existing report that is built from 1 package, point report at UAT package, add the field, run using Hana QA

   4. Recommend - check the formatting, check the data type, check the auto-summation, check the math, does it match the original data source

Recommendation: have a list of know exceptions that you can test and some simple

AH User Acceptance Testing (UAT)

Recommend: after reports are migrated to production delete old reports or QA reports and schedules that are no longer needed

Monthly Releases

1st Thursday of each month = EAH/FINAH/FACAH enhancements go to UAT

2nd Thursday of each month = EAH/FINAH/FACAH enhancements go to Prod

3rd Thursday of each month = RAH/SAH/PAH/COMPAH enhancements go to UAT

4th Thursday of the month = RAH/SAH/PAH/COMPAH enhancements go to Prod