Presented by James Mueller – Graceland University June , 9:30am #441 – Delivering Login Specific Data in Cognos

The Secret Ingredient Cognos Session Parameters Cognos Session Parameters – How Cognos knows who is logged in – Information from the Authentication Provider – Can be expanded – Can be used in reports Macro Functions – Help information in Framework Manager – Can be blind-used in Report Studio

User logs in with AD AD gives Cognos the user’s account information (ID) User logs in with AD AD gives Cognos the user’s account information (ID) Sends SQL request to DB filtered by user’s ID Gathers only the data associated to user’s ID User is presented with their report How It Works COGNOS/AD COGNOS DB COGNOS

Benefits User only sees their information – Helps secure information in shared tables like emptime_rec (CX) – Removes steps (less prompt questions) like adm_rec (CX) – Reduces errors (users mis-answering a prompt) Speeds reports – Only relevant information is pulled Tracking Report output after printing – “Who posted this report on the bulletin board?”

Example: student schedule report Note: accessible to all Faculty and Staff with access to Faculty Tab or direct URL

Example: student schedule report Note: Graceland uses role_rec to contain ALL ROLES a user has

Example: supervisee time chart report Note: Lists only the employee and anyone they supervise (and those people supervise)

So, how do you do this? There’s a help document! _id=c173fa6c bec c38ab0 Gives basic overview How to capture the user’s ID – Two methods How to put them into Cognos Then let your imagination run wild!

GU Group Wiki Lists The Ending Stuff