SHAZAM Core Services - SHAZAM | Financial Services and ...€¦ · SHAZAM Core Services Developer User Guide . Cardinal Insight . CONFIDENTIAL – For Client Use Only . Last Modified

SHAZAM Core Services Developer User Guide

Cardinal Insight CONFIDENTIAL – For Client Use Only

Last Modified 5/5/2020

Cardinal Insight – Develop User Guide, 2020

SHAZAM Core Services Documentation iii ©2020 ITS, Inc. All Rights Reserved.

Revision/Approval History Date Description Author

2/4/2016 Original – Beta Version Moser, Steven 11/12/2019 Updated Mary Latiolais 4/13/2020 Updated Header & Footer Information Lanisha Lomax 5/5/2020 Approval from IP Counsel Lanisha Lomax


SHAZAM Core Services Documentation v ©2020 ITS, Inc. All Rights Reserved.

Table of Contents Preface ..............................................................................................................................................1

Purpose of Document ......................................................................................................................... 1

Who Should Read This Document ...................................................................................................... 1

Objective ............................................................................................................................................. 1

Printing This Document....................................................................................................................... 1

Trademark Attributions ...................................................................................................................... 1

Where to Go for More Help ................................................................................................................ 2

Components of Cardinal Insight ..........................................................................................................3

Types of Cardinal Insight Users ........................................................................................................... 4

Reports and Other Items..................................................................................................................... 4

Item Types ............................................................................................................................................. 4

Output Types ......................................................................................................................................... 5

Components Involved in Generating a Report .....................................................................................7

Before Developing Reports .................................................................................................................8

Determine Whether to Customize a Standard Report or Create a New Report .................................. 8

Plan the Contents of the New Report ................................................................................................... 8

Set User Preferences ............................................................................................................................. 8

Tutorial: Customizing a Standard Report .............................................................................................9

Copying a Standard Report and Launching InfoAssist (1 of 7) ............................................................ 9

Components of InfoAssist ................................................................................................................... 10

Finding Fields to Present in the Report (2 of 7) ................................................................................ 12

Adding Fields to a Report and Testing the Report for the First Time (3 of 7) ................................... 15

Other Ways to Add Fields to a Report ................................................................................................ 18

Calculating New Values from Data in the Source Library (4 of 7) ..................................................... 19

Creating a Temporary Field ................................................................................................................. 19

Customizing the Appearance of Column Headings and Data (5 of 7) ............................................... 21

Selectively Including Records by Applying Filters (6 of 7) ................................................................. 25

Allowing Run-Time Users to Set Filter Conditions .............................................................................. 27

Customizing the Appearance of Data (7 of 7) ................................................................................... 28

Tutorial Conclusion ........................................................................................................................... 30


SHAZAM Core Services Documentation vi ©2020 ITS, Inc. All Rights Reserved.

Where to Go Next ............................................................................................................................. 30

Creating a New Report ..................................................................................................................... 31

Planning for a New Report ................................................................................................................ 31

Determining on Which SQL View to Base a Report .......................................................................... 33

Acting on the Spreadsheet’s Results ................................................................................................... 35

Types of Formats for Date Fields ........................................................................................................ 36

Creating a New Report ...................................................................................................................... 36

Where to Go Next ............................................................................................................................. 39

Instructions for Additional Development Tasks ................................................................................. 40

Defining Document- and Page-Level Headers and Footers ................................................................. 41

Hiding Repeated Values in Adjacent Cells ......................................................................................... 43

Filtering Based on a Dynamic Value in a Field .................................................................................... 44

Creating Advanced Filters using Expressions, Groups, Filters ............................................................. 46

Creating Parameters for Users to Configure When They Run a Report ............................................... 48

Creating a Dynamic Prompt .............................................................................................................. 49

Creating a Static Prompt ................................................................................................................... 50

Creating a Simple Prompt ................................................................................................................. 52

Selecting the Format in Which Users Can Output a Report ................................................................ 53

User Experience When Allowing Users to Select an Output Type .................................................... 54

User Experience When a User Runs an InfoMini .............................................................................. 54

Sorting a Report by a Measure Field ................................................................................................. 55

Customizing the Layout of a Report in Output Documents ................................................................ 56

Grouping Results and Displaying Their Subtotals ............................................................................... 57

Hiding Fields That Are Presented in a Sub-Header ........................................................................... 61

Starting a New Page or Line When a Field Changes Value .................................................................. 62

Enabling Page or Line Breaks ............................................................................................................ 62

Example of Page Breaks .................................................................................................................... 62

Example of Line Breaks ..................................................................................................................... 63

Applying Mathematical Functions to Numeric, Measure Fields .......................................................... 64

Applying Mathematical Functions on a Field-By-Field Basis............................................................. 64

Displaying Numeric Totals at the Ends of Columns and Rows............................................................. 66


SHAZAM Core Services Documentation vii ©2020 ITS, Inc. All Rights Reserved.

Adding Fields from a Second View .................................................................................................... 68

Presenting a Report as a Configurable Application (InfoMini) ............................................................ 70

What is an InfoMini? ......................................................................................................................... 70

InfoMinis versus Filter Parameters ................................................................................................... 70

Features of an InfoMini ..................................................................................................................... 70

Creating an InfoMini ......................................................................................................................... 70

Reordering or Deleting a Slicer Group .............................................................................................. 73

Changing an InfoMini to a Regular Report ........................................................................................ 74

Allowing Further Processing of Report Results .................................................................................. 75

Case Study: Multi-Step Reports ........................................................................................................ 75

Designing a Multi-Step Report .......................................................................................................... 77

1. Developing the Base Report and Creating the Intermediate Report .............................................. 77

2. Developing the Intermediate Report and Creating the End-User Report (Part 2 of 3) .................. 79

3. Developing the End-User Report .................................................................................................... 81

Linking from Report Results to another Report ................................................................................. 82

Naming Convention for Built-In Reports with Drill-Downs ............................................................... 82

Implementing Drill-Downs ................................................................................................................ 83

1. Adding Hyperlinks to Fields ........................................................................................................... 83

2. Enabling the Target Report to Apply a Filter................................................................................. 84

Troubleshooting When Lower-Level Results Do Not Filter Correctly ................................................. 85

Distributing Reports to a Cardinal Core Distribution Point ................................................................. 86

Before Beginning ............................................................................................................................... 86

1. Preparing a Report for Distribution .............................................................................................. 86

2. Defining the Report within the Information Distribution System ................................................ 87

3. Adding a Report to a Distribution Point ........................................................................................ 90

Looking Up Error Codes .................................................................................................................... 96

Appendix A: Aggregation Functions for Numeric Fields ..................................................................... 97

Report-Level Aggregations Functions ............................................................................................... 97

Sum ..................................................................................................................................................... 97

Print ..................................................................................................................................................... 97

Count ................................................................................................................................................... 97


SHAZAM Core Services Documentation viii ©2020 ITS, Inc. All Rights Reserved.

List ....................................................................................................................................................... 97

Behavior When a Row Cannot Be Summed ........................................................................................ 98

Field-Level Aggregations Functions .................................................................................................. 98

Appendix B: Overview of Temporary Fields ..................................................................................... 100

Types of Temporary Fields ................................................................................................................ 100


SHAZAM Core Services Documentation 1 ©2020 ITS, Inc. All Rights Reserved.

Preface

Purpose of Document This document explains how to perform tasks that are common in developing reports in InfoAssist. The document provides brief overviews of useful InfoAssist functionality and step-by-step instructions for performing tasks. Although InfoAssist provides many features for writing reports and creating charts and dashboards, this document is not intended to comprehensively document every InfoAssist feature.

Who Should Read This Document • Cardinal Insight Report Developers

• SHAZAM Core Services Personnel

Objective Upon completing this document, learners will be able to accomplish the following goals:

• Copying a standard report or create a new, blank report

• Defining which records a report includes and/or providing end users with the ability to filter records

• Dividing results into groups, complete with subtotals and sub headers/footers

• Customizing the visual appearance of a report

• Implementing various data-analysis features

Printing This Document This document has been formatted for double-sided printing. Printing this document using a single sided print option, will produce blank pages in the introduction sections.

Trademark Attributions The following trademarks are referenced in this document:

• ITS, Inc. has registered trademarks at the United States Patent and Trademark Office which include SHAZAM® and the SHAZAM logo.

• Compass XD™ is a trademark of ITS, Inc. • IBM® iSeries™, IBM iSeries Access™ for Windows®, IBM iAccess Client Solutions™ for Windows®,

IBM iAccess Client Express™ for Windows®, iSeries Operation Navigator™, AS/400 NetServer™, and DB2® are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

• Microsoft®, Windows®, Windows NT®, and Microsoft® Word™ are trademarks of Microsoft Corporation, registered in the United States, other countries, or both.

• Java® is a registered trademark of Oracle and/or its affiliates. Other names may be trademarks of their respective owners, registered in the United States, other countries, or both.



• Seagull Software® and J Walk® are trademarks of Rocket Software, Inc., registered in the United States, other countries, or both.

Where to Go for More Help For more information, refer to the following table to determine where to get more help.

Subject of Question

Where to Go

DB2 Web Query 1. Refer to the Cardinal Insight Runtime User Guide posted at SHAZAM.net > Core Client Login > Documentation.

2. Click the Help link at the top-right of Web Query user interface to launch the IBM DB2 Web Query Online Help. This documentation provides more comprehensive information about the components and tools used to run, view, create, and edit reports.

3. Contact SHAZAM Core Services Support.

InfoAssist 1. Click the Help button at the top-right of the InfoAssist environment to launch the InfoAssist Help.

2. Contact SHAZAM Core Services Support.

• Standard reports

• SQL views

Contact SHAZAM Core Services Support.

http://www.shazam.net/




Components of Cardinal Insight The following illustration lists the components that make up the Cardinal Insight product.

IBM DB2 Web Query

The web-based tool for browsing, running, and publishing reports.

If users are not yet familiar with navigating WebQuery and running reports, refer to the Cardinal Insight Run-Time User Guide posted at SHAZAM.net > Core Client Login > Documentation

IBM InfoAssist

The web-based tool for creating and editing reports. Users with InfoAssist permission can perform the following report-development tasks, including the following tasks:

• Adding additional fields to a standard Cardinal Insight report • Adjusting filters that users can apply to selectively include or exclude

records • Creating new reports from scratch

For more information about developing reports, refer to Cardinal Insight Developer Guide posted at SHAZAM.net > Core Client Login > Documentation.

Cardinal Core SQL views

SQL views provide reports with access to sets of related data fields that are stored in the bank’s Cardinal Core databases. These views link tables so users can typically find the data needed by loading a single view rather than browsing multiple tables.

Cardinal Insight standard reports

These ready-to-run reports include frequently used Cardinal Core RPG reports. Users cannot edit standard reports, but can copy and customize a standard report.

For a complete list of standard reports, refer to the Standard Report Listing posted at SHAZAM.net > Core Client Login > Documentation.

Integration with Compass XD

This feature allows users to run a report and view its results directly from Compass XD. Currently, users running reports from the Web Query user interface.







Types of Cardinal Insight Users SHAZAM Core Services developed Cardinal Insight with the following types of users in mind:

• Run-Time Users—The end users of reports who can browse for and run reports in the Web Query folders that they have permission to access. These users can manipulate report results to the extent that the report’s output format allows. However, these users cannot edit the report design without access to InfoAssist.

• Report Developers—Users with permission to launch Info Assist from the Web Query interface to create new reports and modify existing reports. These users also can copy, paste, retitle, and delete reports in Web Query. This document is intended for this type of user.

• System Administrators—Administrators grant permission to users to create and edit reports. For example, run-time users must be given permission to see particular folders in order to run the reports in them. Report developers must be given write access to edit reports in a folder.

Reports and Other Items Before creating, view, and distribute reports, get familiar with the following concepts:

• Item Types—Web Query and InfoAssist provide features for creating a few different types of documents that present the bank’s data. The next section briefly describes each item type. However, this user guide focuses only on developing reports and InfoMinis, which function similarly.

• Output Types—Cardinal Insight can generate item types in a variety of output formats, including as PDF files, HTML pages, and spreadsheet files.

Item Types The following table describes and compares item output types.

Report Type Description

Report Reports present data in a tabular layout. Reports can have headers, footers, column and row totals. Users may group rows and present sub-totals of their values.

InfoMini An InfoMini is an application built from a report that provides users with the ability to configure developer-defined filters when they run the report. This is useful for non-technical users who want the flexibility to perform data analysis on reports but who do not have access to InfoAssist.

Chart Several types of supported charts can help show data in a bar, pie, line, or other type of chart rather than in the tabular form of a report. This might be useful to show the patterns, trends, and shape of the data.



Documents and

dashboards

Documents and dashboards consist of text, images, active form controls, reports, and charts to create documents that can be used to generate presentation-ready reports based on data.

This type of dashboard is different from a personal dashboard, which even run-time users can create. Creating personal dashboards is documented in the Cardinal Insight Run-Time User Guide posted at SHAZAM.net > Core Client Login > Documentation.

Output Types The following table describes and compares output types.

Output Type Use Cases Requirements

PDF • Easy to print and distributable to others in a consistent format.

• PDF reader tools allows users to markup content with highlighting and comments.

Adobe® Reader®

HTML Intended for on-screen viewing in a web browser, which provides the following advantages over PDFs:

• Users can scroll horizontally without the same constraints on row length as in PDFs.

• Developers can implement hyperlinks that allow end users to browse to related documents.

• Does not require Internet access to load.

Mozilla® Firefox®

Internet Explorer® (preferred)

Active Report Provides the same advantages as HTML output, plus the following features that are built into the HTML page via ActiveX controls:

• Sorting rows by a particular column

• Filtering rows according to conditions

• Hiding columns to not see or print

• Generating charts and pivot tables

• Applying calculations such as sum, min, max, average, count and count

Note: Active reports support up to 20,000 rows of data. If users are using the Mozilla Firefox

browser, we recommend that using only up to 15,000 rows of data. If using an Internet Explorer browser, use only 5,000 rows of data.

Mozilla Firefox

Internet Explorer (preferred)

Active Flash The same advantages as an Active Report but developed as a Flash-based report.

Mozilla Firefox





Internet Explorer

Excel 2000/Excel 2007

Generates a .xls or .xlsx file that contains the static values of calculated fields instead of the underlying formulas.

Microsoft® Excel®

Excel Formula/Excel 2007 Formula

Outputs the report using native Excel formulas for totals and computed values.

Microsoft Excel

PowerPoint Generates a .ppt file. Microsoft® PowerPoint®

PowerPoint 2007

Generates a .pptx file. Microsoft PowerPoint

Web Query Reports versus RPG Reports The standard reports shipped in Cardinal Insight are intended to replace reports that are built into Cardinal Core and that the iSeries machine generates as RPG reports.

• Web Query advantages:

o Choose to generate reports in several output formats, including as PDFs, HTML pages, and spreadsheets.

o PDF reports are easy to print and distribute.

o HTML and active reports are more usable for viewing onscreen.

• RPG report advantage—These reports, generated by Cardinal Core, can stack fields when rows would otherwise be too wide in the horizontal direction to print on one page. Cardinal Insight does not support stacked fields, but its PDF reports are designed to wrap long rows across multiple pages so that the row can be reassembled when printed. For an example of this behavior, refer to the Analyzing PDF Reports section of the Cardinal Insight Runtime User Guide posted at SHAZAM.net > Core Client Login > Documentation.




Components Involved in Generating a Report SHAZAM Core Services designed standard reports to be flexible in that they can pull data from any data library, include data fields from multiple SQL views, and be generated in multiple output formats. The following illustration and the bullets that follow explain this design.

• Report—Reports specify which fields in a SQL view that they include, and Web Query returns the data in those fields from whichever data library is active. This behavior allows reports to be agnostic to the data library from which Web Query pulls records.

• SQL views with fields—SQL views map reports to data in Cardinal Core data libraries.

• Data libraries—One Cardinal Core data library is always active in Web Query. When a run-time user runs a report, Web Query pulls records from the active library.

• Output types—Developers can allow run-time users to generate a report in any format, such as the types shown above, or they can restrict the report to a single format.



Before Developing Reports

Determine Whether to Customize a Standard Report or Create a New Report The standard reports shipped in Cardinal Insight can be used as-is, or users may create and modify them instead of creating a new report from scratch. Customizing a standard report rather than creating a new report is appropriate when changes are limited in scope. Consider the following examples:

• Adding or replace a field.

• Filtering records differently.

• The data in the bank’s library does not fit in the formatting that SHAZAM Core Services implemented, and the user just need to resize fields.

To browse for instructions for performing common tasks in an existing report, refer to the following sections of this document:

• Tutorial: Customizing a Standard Report

• Instructions for Additional Report-Development Tasks

For instructions and guidelines for creating a new brand report, refer to Creating a New Report.

Plan the Contents of the New Report The first step in creating a new report is to select the SQL view that contains the fields to present in the report. After selecting an initial view, it cannot be removed. Therefore, carefully think through all the fields that will be needed in some way, including for the following purposes:

• To present a field’s values in the report as-is

• To filter displayed records based on their values in a field but not show the values in the report

• To present values that are calculated from a field’s values

Changes cannot be made to the SQL view originally select. However, additional views can be joined to present fields from them.

Set User Preferences To reduce the number of settings users must configure when developing new reports, consider configuring the preferences within the InfoAssist environment. Users can configure several default behaviors in the Options dialog box that displays, such as whether to launch report instances in new browser tabs or windows and whether to format reports in portrait or landscape orientation.

To access the Options dialog box, click the InfoAssist main-menu button at the top-left of the UI and select Options.



Tutorial: Customizing a Standard Report The following tutorial introduces several frequently used InfoAssist features. The procedures in the tutorial build on one another, and the steps assume users are performing the tutorial from start to finish. To perform one of the procedures outside the context of this tutorial, users typically must extrapolate the instructions to the unique development goals.

Copying a Standard Report and Launching InfoAssist (1 of 7) Users should complete this procedure to become familiar with the following features:

• Creating a copy of a standard report

• Renaming a report to indicate its purpose to run-time users

• Launching InfoAssist to modify a report

Step Action

1 In Web Query, click the Reporting tab selector to display the Repository tree.

Note: For information about the types of folders in the Repository tree, refer to the Cardinal Insight Runtime User Guide posted at SHAZAM.net > Core Client Login >

Documentation.

2 Browse to and expand the Base Reports - Deposits folder.

3 Right-click the ID5330 standard report and select Copy.

Note: If the shortcut menu for the report does not contain Edit/Cut/Copy/Paste options, the account does not have permission to edit the contents of the folder. Ask

an administrator at the bank for permission to access this folder.

4 Browse to the bank’s Deposits folder at the top level of the Repository tree. Users must copy a report to the bank’s folder for the application to which the report belongs. For





example, copy a report from Base Reports - Deposits to the bank’s Deposits folder or a subfolder within it. Otherwise, the report does not have access to the SQL views it requires.

5 Right-click the bank’s Deposits folder and select Paste.

Tip: If a user prefers not to add clutter to the bank’s folder, consider creating a new sub-folder in the bank’s folder. To create a new sub-folder, right-click the parent

folder and select New > Folder.

The copy of the ID5330 report appears with its name in plain text, which means it is unpublished and visible only to the user.

6 Right-click the ID5330 copy and select Change Title. Enter a title that indicates the report is

based on the ID5330 standard report, such as Custom ID5330.

7 Right-click the report again and select Edit.

Result: InfoAssist launches with the copy of the ID5330 report open. This means the fields that provide data to the report appear in the Query pane, the SQL view that contains these fields is loaded, and a preview of the report appears in the Live Preview window.

Components of InfoAssist The following screenshot calls out and briefly explains the major components of the InfoAssist user interface. Continuing through this tutorial, users will gain experience using these components.



The Application button provides access to the same functions on the toolbar (New, Open, Run, etc.) and a dialog box for setting user preferences.

The ribbon houses tabs (e.g. Home, Insert) that contain report and field configuration options.

The Data pane provides access to each field presented in a report. This pane lists the fields in the SQL view on which the report is based.

The Filter pane organizes both types of filters that determine whether to include or exclude records: developer-defined filters and parameter filters that Web Query prompts users to set.

The Query pane contains and categorizes fields added to the report.

The Navigation taskbar displays a tab for the Live Preview window and tabs for each instance of the report run so users can switch between them.

The Status bar contains menus for switching between open reports when multiple reports are open; selecting a different output format; and choosing whether to open report instances in InfoAssist tabs or in browser windows.

The Live Preview window is always loaded and previews the report with actual data. This window also provides access to report-development features such as filters, breaks, and formatting options.

The Run button creates a new instance of the report that models how run-time users will see the report. When interacting with a report instance, users do not have access to the same tools that are available in the Live Preview window.



Finding Fields to Present in the Report (2 of 7) Complete this procedure to become familiar with the following features:

• Switching between views of the Data pane to find fields more efficiently

• Previewing details about fields to decide whether to add them

Step Action

1 Observe that the report in the Live Preview window consists of a table in which each row represents an account with NSF charges on the current day.

Notice that the third column shows the count of NSFs on the current day but not the dollar amount of those NSFs. The goal is to add this information to the report.

2 To find the field that stores the amounts of NSF transactions posted per account, browse in the Data pane at the top left of InfoAssist. Recall that this pane lists the fields in the SQL view on which the report is based.

The contents of the Data pane appear in one of three ways, as the following table describes.

Logical List Structured

Categorizes alphanumeric fields as Dimensions and numeric/date fields as Measures/Properties.

Displays every property of each field in a sortable table.

Lists fields in the order they appear in the file. This is useful if users are very familiar with the contents of files.

3 Click the View tab on the ribbon. The Data Panel section shows these three options for organizing the Data pane.



4 Select Structured.

5 Complete the following steps to switch between viewing different field properties in the Data pane while the Structured view is active:

A. Click the drop-down arrow beside the Structured button and select Title. Spelled-out, descriptive field names display in the Data pane.

B. Click the drop-down arrow again and select Field. The actual names of fields

within the view display.

Note: Users can perform these same steps when the Logical and List views are active.

6 Hover over a field in the Data pane. Web Query displays every property for the field in a tooltip. This is useful because users can see the descriptive and actual names without manually switching the visible property as in step 5.



Tooltips are available in all three views.

7 Notice that different icons appear beside fields to indicate the format of the data they store. The following icons are common within Cardinal Insight views:

Text or Alpha Field

Date or Date and Time Field

Numeric Field

Calculated Text Field

Calculated Date Field

Calculated Numeric Field

8 Back on the View ribbon tab, click the button for the List view.

9 Click the Title column header to sort the table rows in alphabetical order by their descriptive titles.

10 Begin typing AMOUNT. The active table row jumps to the Amount Of,NSFs Today field.

Users can also type a field name, like AMTOFNSFSTODAY.

In the next section of this tutorial, users will add this field to the report to display the dollar amounts of NSF transactions posted per account.

Note: By switching between Data pane views, sorting List columns, and viewing field tooltips, users can find fields of interest in whichever way is most efficient for the bank.



Adding Fields to a Report and Testing the Report for the First Time (3 of 7) Complete this procedure to become familiar with the following features:

• Adding a field as a column in the report

• Running the report to see the results in a particular output format

Step Action

1 Click and drag the AMTOFNSFSTODAY/Amount Of NSFs Today field from the Data pane to the Query pane at the bottom-left corner of InfoAssist. Drop the field between the Account Number and Short Name fields, as shown.

The field appears in the Live Preview window in the same position where the user added it to the Query pane, between the Account Number and Short Name columns.

2 In the Query pane, click and drag the Amount Of NSFs Today field below the Short

Name field. Web Query reflects the change in the Live Preview window by moving the field to the right of the Short Name column.

3 Scroll to the bottom of the report. Notice that the new column does not contain a total

value like the columns to the right.



The total is missing because the user added the field under the By node in the Query pane, which indicates the user wanted to sort the report by that column but not aggregate the values in the column.

4 In the Query pane, click and drag the Amount Of NSFs Today field from under the By node to directly under the Sum node.

Web Query begins displaying a summed total for this column at the bottom of the report.

Tip: Instead of summing, the user can apply other functions to fields organized under the Sum node. Users can also apply functions on a field-by-field basis. For instructions

for performing these tasks, refer to Applying Mathematical Functions to Numeric, Measure Fields.

Query Pane Nodes for Categorizing Fields

As step 1 of this procedure shows, the Query pane contains three nodes under which fields can be placed. Read the following definitions to choose the appropriate node:

• Sum: Aggregates and displays numeric fields.

• By: Vertically sorts non-numeric or date fields

• Across: Horizontally sorts non-numeric or date fields

5 Click the Run button in the InfoAssist menu bar. The report prompts the user to choose the output type in which to display the report.



Note: The Parameters section displays because this report, like most standard reports, is configured to allow users to choose the output type. However, users can

change this behavior. Refer to the Selecting the Format in Which Users Can Output a Report section for more information.

6 Select HTML, place a checkmark in the Run in a new window checkbox, and click Run to open the report in a new browser window or tab.

Tip: Running a report in a new window rather than InfoAssist provides more screen area for the user to view the report.

7 When finished browsing the report, close the browser window or tab to return to InfoAssist. Notice that the report instance that displayed in step 6 when the report was ran is still visible.

Users can close the report instance or leave it active while switching to the Live Preview window by clicking the selector at the bottom-left of InfoAssist.

Tip: Users may want to close the report instance window as soon as finished viewing the report. This report instance will not reflect any new changes made to the report



in Info Assist, so if users run the report again from this instance, it appears as though the changes did not take effect.

Result: The report now presents the dollar amount of NSFs that was received for each customer and the dollar total of all NSFs items.

Other Ways to Add Fields to a Report Users can add a field to a report in several other ways, described as follows. However, these methods require more configuration than when dragged directly to the Query pane.

• Double-click a field in the Data pane to add it to the end of the report.

• Right-click a field in the Data pane and select Sum, Sort, or Across to add the field to the end of the report

• Click a field in the Data pane and drag it to the Live Preview window to the position where to display the new field.



Calculating New Values from Data in the Source Library (4 of 7) Instead of presenting a field in a view exactly as-is, users can create temporary fields whose values are based on an existing field in a record. A temporary field is a field whose values are not stored in a data library, but instead is derived one of the following ways:

• By calculating its values from data in the view. For example, consider a field that calculates the month-to-month percent change in an account’s balance. The temporary field might calculate this value from existing fields that store the account’s past two month-end balances.

• By assigning constant values. For example, consider a field that displays the text Overdue when the current date is more than 5 days past an account’s next review date. Another use case might be a field that displays a full description in place of less-readable code. For example, the user might consider a field to display Business Rate when the existing Product Code field contains BUS. Users could then omit the Product Code field from the report.

For a detailed explanation of temporary fields and when to use each type, refer to Appendix B: Overview of Temporary Fields. SHAZAM Core Services recommends familiarizing oneself with these concepts before proceeding.

Creating a Temporary Field Complete this procedure to become familiar with the following features:

• Creating a define field that is calculated for every row

• Creating a compute field that is calculated for records that have been aggregated

Step Action

1 In the Data pane, browse to the NETCHG field. This field is one of the Sum fields and is presented in the report under the column heading Change Amount.

2 Right-click NETCHG and select Edit. The Detail Field dialog box displays. Become familiar with the following features that are used to create both define and compute fields.



Each temporary field requires a unique name to identify it throughout InfoAssist.

An expression, which can include fields, constants, and operators, defines how Web Query calculates the field’s values.

Buttons populate the expression textbox with numbers and common operators and commands so it is not necessary to type them. Use the buttons to help avoid syntax errors that can be difficult to troubleshoot.

Set the format in which the resulting values appear, such as whether they are an alphanumeric value, integer, or decimal value and whether dollar or percent signs appear with values.

Double-click a field in this table to populate the expression textbox with its ID. This table contains the same fields as the Data pane in the InfoAssist environment.

Switch between the same views in which can display the Data pane in the InfoAssist UI: Logical, Structured, and List. The previous screenshot shows the List view.

3 Click Cancel to exit this dialog box without changing the NETCHG field. Proceed to the next step to use the knowledge from step 2 to create a compute field. As mentioned previously, use the same features to create both compute and define fields.

4 On the Data ribbon tab in InfoAssist, click the Summary (Compute) button.

5 Enter AvgNSFAmt in the Field textbox.

6 Click the Format button and configure the following options so the values calculated for the field appear as dollar amounts:

A. Ensure the Field type is set to Decimal.

B. Enable Floating Currency.

C. Click OK.



7 Complete the following steps to define the expression that Web Query will use to calculate the new field’s values:

A. In the field list at the right side of the dialog box, double-click the Amount of NSFs Today field to add it to the expression textbox.

B. Click the / (divide) button below the expression textbox.

C. Browse to and double-click the Number of NSFs Today field to add it to the expression.

The Summary Field dialog box appears as follows.

8 Click OK.

Result:

• In the Live Preview window, the new field appears as the rightmost column in the report. The new field displays the average dollar amount of each customer’s NSF items on the current day by dividing the total amount of NSFs by the number of NSFs on the current day.

• In the Query pane, the field appears under the Sum node.

To edit a compute field, right-click it in the Query pane and select Edit Compute.

Note: The new AvgNSFAmt field is not available in the Data pane because compute fields do not appear in the Data pane. Recall that the NETCHG field was in the Data pane because it is a

define field.

Customizing the Appearance of Column Headings and Data (5 of 7) Complete this procedure to become familiar with the following features:

• Change the text in column headers



• Change the visual format of numeric data

• Change font and color settings for a column’s values

Step Action

1 Right-click anywhere in the Number of NSFs Today column and select Change Title. Web Query displays the current title in a dialog box.

Users might want to change a column title to take up less space or use different terminology than the field’s title.

When the actual field name, as shown above, appears, Web Query will automatically substitute the title of the field, which in this case is Number of NSFs Today.

2 Enter the following text: # NSFs,Today and click OK. Entering a comma in a column title specifies to break to a new line. As the following screenshot shows, the comma does not appear in the header.

3 Right-click the Amount Of NSFs Today field in the Query pane and select Edit Format.

The field-format dialog box displays.



Note: Users can only format fields that are categorized under the Sum node, not fields under the By node.

4 Place a checkmark in the Suppress Comma checkbox.

5 Place a checkmark in the Non floating dollar checkbox.

6 Click OK.

The Amount of NSFs Today column displays the dollar sign in its first row. Also, values greater than $1,000 no longer contain commas to mark the thousands place.

7 When returning to the InfoAssist environment, note that the Field tab on the ribbon (1)

became visible when right-clicked the field.

Users may access some of the same formatting options directly on this tab, in the Format section (2). To open the field-format dialog box again, click the format drop-down menu and select, select More options.

8 Also notice the Style section on the Field ribbon tab. Use these options to change the visual appearance of the values in the selected column.



Tip: To change font and color settings for every field in the report at the same time, browse to the Home tab on the ribbon and click the Style button.

Result: The column is renamed to take up less horizontal space, changed the formatting of numeric values, and learned where to apply font and color settings at the column and report levels.



Selectively Including Records by Applying Filters (6 of 7) Complete this procedure to become familiar with the following features:

• Showing only records in the data library that meet some condition

• Updating page headers to reflect the report’s new scope

Step Action

1 To limit the records a report contains to only those records that meet a particular condition, create a filter.

In the Query pane, drag the Amount of NSFs Today field to the Filter pane. The Filter dialog box displays.

2 Select Greater than in the drop-down menu.

3 Enter 100.00 in the Add field to specify that the report contain only those records whose Amount of NSFs Today field is greater than $100.00.

4 Click the Add button and then click OK.

The Live Preview window automatically updates to include only records that meet this condition (Amount of NSFs Today > 100.00).

5 The filter created evaluates a field that is presented in the report (Amount of NSFs Today).

However, users can filter records according to fields that are in the SQL view but not presented in the report.

In the Data pane, start typing PRODTYPE to locate the field with that name.



6 Drag the Product Type field to the Filter pane. The Filter dialog box displays as in step 3.

7 Set the condition to Equal to. Users can filter based on an exact value because the Product Type field in data libraries accepts only the predefined values the bank uses to identify products.

8 Click the Values button at the top of the dialog box ( ) and select Fetch All Values from Source. The bottom of the dialog box displays each unique Product Type value that is present in the data library ( ).

9 Complete one of the following steps to instruct Web Query to include records with a

particular Product Type in the report:

• Enter a Product Type value surrounded by single-quotation marks in the Add field ( in the previous screenshot), and then click the Add button ( ).

• Double-click a value in the fetched list ( ).

The Selection Values list ( ) displays the values that, when present in a record, will cause the report to include that record.

10 Click the OK button at the top of the dialog box to apply the filter.

11 On the Home ribbon tab, click the drop-down arrow beside Header & Footer and select Page Header.

Retitle the report to reflect the report’s new, more specific purpose. For example, users might prepend the following text to the original NSF Fees Changed in Online Reentry line: BUS/CHG When Amt > $100. The following screenshot and callouts explain features of the Header & Footer dialog box.



To switch between editing page and report headers and footers, click the appropriate button at the top of this dialog box.

Preformatted values, which begin with an ampersand (&), indicate the system will insert an actual value when the report runs. For example, the system will replace &MR_FULL_FEXNAME with the report’s full title and &DATE with today’s date.

Field names, which begin with an angle bracket, are replaced with the field’s value when the report runs. To add a field name, drag the field from the Data pane into this dialog box.

To add preformatted values (2) to a report, select the value of interest from this drop-down menu.

12 Click OK to apply the updated page header.

Result: Two filters were added to the newly renamed report:

• One filter examines numeric values in a field the report includes.

• One filter examines alphanumeric values in a field the report does not actually include.

Allowing Run-Time Users to Set Filter Conditions

In the previous procedure, users fully configured both filters, and Web Query automatically applies them when it runs the report. However, run-time users often want to see a report’s results filtered according to the value of one or more parameters that they set. For example, they might desire the NSF report in this tutorial but at different times they might require it to show records in which the NSF amount is greater than $250, $500, and $1,000. Instead of creating three separate copies of the report, each with a different hard-coded filter on the NSF amount field, consider prompting the user to set the desired amount as a parameter prior to running the report.

For step-by-step instructions for setting up parameter, refer to Creating Parameters for Users to Configure When They Run a Report.



Customizing the Appearance of Data (7 of 7) Complete this procedure to become familiar with the following features:

• Highlighting cells with a different color when their value meets some condition

• Visually contrasting the amounts in a numeric field, similar to a bar chart

Step Action

1 In the Live Preview window, select the Short Name column.

Instead of filtering out records like in the previous procedure, users can configure a report to visually highlight values in a particular field that meet a particular condition. InfoAssist’s feature for this task is referred to as traffic lights. Users will apply the traffic-light formatting to cells in the Short Name column.

2 On the Field ribbon tab, click the Traffic Lights button in the Display section.

3 Click New.

4 In the field drop-down menu ( ), select the Amount of NSFs Today field.

The traffic-light condition will evaluate values in this field. In other words, Web Query evaluates values in this field to determine whether to apply formatting to the Short Name field selected in step 1.

5 Select Greater than in the condition drop-down menu ( in the previous screenshot).



6 Click the value drop-down menu ( ) and enter 500.00 in the Value field ( ). Click OK. This specifies that the report will apply formatting to the Short Name field in any rows where the Amount of NSFs Today is greater than $500.00.

Tip: To first review all the values that the Amount of NSFs Today field currently contains in the active data library, click the Get Values button. This allows users to

make an informed choice without returning to the Live Preview window to examine the records.

7 Click the Style button at the top of the dialog box to display the visual-formatting options.

8 Click the Background Color button and select a bright orange or yellow color.

9 Click OK in both dialog boxes to commit the changes and return to the Live Preview window.

InfoAssist applies the traffic-light formatting to any records whose Amount of NSFs Today value is greater than $500.00.

10 Select the Change Amount column to display the Field ribbon tab.



11 In the Display section, click the Data Bars button. Web Query displays horizontal bars beside each cell in the Change Amount column. As the following screenshot shows, the length of bars visually indicates the percentage of the greatest value that each cell’s value represents. For example, the length of bars for 25.00 records is slightly under 25% of the length for the 110.00 bar.

Result: The report calls attention to records with high NSFs amounts by applying background color to their short name cells. The data bars allow users to quickly compare numeric values relative to the other values in the same column.

Tutorial Conclusion After completing this tutorial, users will have accomplished the following tasks to customize a copy of a standard report:

• Adding fields to a report to display and/or aggregate their values in data-library records

• Running the report to create a report instance like a run-time user at the bank.

• Defining new, temporary fields and including them in the report

• Changing column heading text, numeric formats, and font properties

• Filtering records to include only records of interest

Where to Go Next InfoAssist provides many other features that are useful when modifying a standard report or create a new report from scratch. The remainder of this document contains two major sections where users can learn more about these features:

• For instructions and best practices for creating a new report, refer to the Creating a New Report section.

• To continue learning about ways to customize existing reports, refer to the Instructions for Additional Development Tasks section.



Creating a New Report This section presents considerations to help users plan for a new report and instructions for creating a new report. After creating a report, users can browse the other sections of this document for instructions for performing specific development tasks.

Planning for a New Report The following checklist prompts users to consider several design decisions. Users might review this checklist with a report’s end users to form business requirements. Making these decisions prior to creating the report can help develop reports more consistently and reduce the amount of rework to perform.

Enumerate the fields whose data the user wants to present in the report or use as the basis for logic. Use this list to identify a SQL view that contains all or most of these fields.

Details

The first step in creating a new report is to select the SQL view that contains the fields users will want to use in the report. After selecting an initial view, it cannot be removed. Therefore, carefully think through all the fields needed to use in some way.

Note: Users cannot change the SQL view originally selected. However, users can join additional views to present fields from them.

Categorize fields the user wants to present according to their role within the report.

Details

The steps taken to include a field in a report varies according to the field’s role. For each field, categorize its role as one of the following:

• The report will present the field’s values as-is. If this is the case, further categorize the fields between the following groups:

o The field is numeric and the report will aggregate its values, such as by summing and presenting its values in column totals.

o The field stores non-numeric or date values and

o Horizontally sorts non-numeric or date fields

• The report will filter each record according to the value in this field.

• The report will calculate additional values based on the value of this field. For example, a report might add the values from two fields in each record to calculate a combined value that is not represented by any field in Cardinal Core data libraries.

Become familiar with design decisions that SHAZAM Core Services applies in standard reports.

Details

When developing new reports, users might want to emulate the appearance of the standard reports to create a consistent look and feel across all the reports the bank uses. The following list describes formatting options applied in standard reports:



Dollar amounts are not prefixed with dollar signs

Negative values are surrounded by brackets but not dashes.

Report and page headers present the following metadata:

o Report header: Bank name

o Page headers: Report title and description, current date, name of user who ran the report, and the number of the current page out of the total number of pages.

Think of a title that helps users understand the purpose and contents of a report. An intuitive title saves users time because they can recognize a report without first running it.

Details

Think of a descriptive title that, when viewed in the Repository tree of Web Query, will help run-time users know whether they want to run it. If a report is sorted according to a particular field or filtered to include only a subset of entries, consider calling out that behavior in the title.

Tip: Consider including similar text in report or page headers within the report to help users identify that a generated report corresponds to a particular entry in Web Query.

Decide in which output formats to allow users to generate the report, such as HTML, PDF, or spreadsheet.

Details

Depending on a report’s audience and purpose, users might want to allow a user to choose any output format, or users might restrict users to generating only one particular format.

Plan whether to allow the user to filter the report’s results, and if so, which field’s values they can filter on.

Details

Users can develop a report to prompt a user to set one or more filters on report results. This is useful for creating a single report that satisfies multiple use cases. For example, a particular department might require a report of accounts with large balances, but different employees might want it to show only accounts with balances greater than $10,000, $50,000, and $100,000. Instead of creating three copies of the report, each with a different hard-coded filter, consider prompting the user to set the filter condition (account balance) prior to their running a report.



Determining on Which SQL View to Base a Report When users have a list of the fields whose data is needed to present or otherwise use in the report, use the list to identify a SQL view that contains all or most of these fields. Users cannot change the SQL view originally selected, so it is important to select a suitable primary view.

Complete the following steps to look up the most appropriate SQL view for the report based on the fields to include in the report.

Before Beginning: Download or ensure access is available to the latest version of the Cardinal Insight Catalog spreadsheet posted at SHAZAM.net > Core Client Login > Documentation.

Step Action

1 Open the Cardinal Insight Catalog.xlsx spreadsheet.

2 Open the Universe with Fields worksheet in the spreadsheet. This worksheet contains the following sections:

#TODO

Lists the filenames of SQL views that contain a set of fields to include in a report.

Lists the names of fields as they exist in Cardinal Core files.

Lists corresponding new names for the Core fields. SHAZAM Core Services has renamed these fields in the Cardinal Insight SQL views to be more consistent and readable.

3 Use the following table to proceed.

If… Then…

Users know the names of fields as they exist in Cardinal Core files

Click the drop-down arrow beside the Old Field Name cell.

Users want to browse longer, more intuitive names assigned to fields

Click the drop-down arrow beside the New Field Name cell.




4 In the search box, enter all or part of the name of a field in Cardinal Core to include in the

report. For example, for fields that store account numbers, users might enter ACCT. Find the field desired, scrolling down if necessary, and proceed to step 5.

Tip: SQL views typically provide fields that store dates in a few different formats. For information to help choose the appropriate format, refer to Types of Formats for Date

Fields.

The following screenshot shows how the list updates to show only fields that match the characters entered.

5 Remove the checkmark beside the (Select All Search Results) option.

6 Place a checkmark beside the field found in step 4 and click OK to return to the spreadsheet.

The spreadsheet shows only those SQL views that contain a Cardinal Core field with the same name selected.

7 Click the filter icon beside whichever column header just filtered: Old Field Name or New Field Name.

8 Search for a second field to include in the report.

9 Remove the checkmark beside the (Select All Search Results) option to deselect every option.

10 Place a checkmark beside the field found in step 8.

The spreadsheet shows only those SQL views that contain both Cardinal Core fields added to the filter.



11 Place a checkmark in the Add current selection to filter checkbox and click OK.

12 Repeat steps 7-11 until all fields that will be used in some manner have been added in the

report to the filter.

Result: The spreadsheet shows only SQL views that contain all of the fields added to the filter. The following screenshot shows the spreadsheet with its list of SQL views filtered to show only those that contain the following Old Field Name values: ACCTNO and ACTYPE.

Acting on the Spreadsheet’s Results If a view in the File Name column contains every field needed, use that view to build the report. If users require more than one view to provide the report with all of the fields, choose a primary view to start and then join an additional view or views. For instructions on joining views, refer to Adding Fields from a Second View.



Types of Formats for Date Fields In SQL views, fields that store dates do so in one of three different formats:

• A date field whose name ends in 6, like STMD6, is a numeric field in MMDDYY format. This numeric value is not actually a date field that can be used for comparisons.

• A date field name that ends in a 7 is a Julian date.

• A date field that does not end with 6 or 7 is in a date format suitable for comparing dates. Use this format in the reports.

Some date fields are also broken down in other helpful forms, such as Year, Quarter and Year, Month and Year. These fields show as functions and can be used in reports.

Creating a New Report Complete the following steps to create a new, blank report.

Before Beginning:

• Determine on which SQL view the report will be based.

• Determine in which Web Query folder to store the report. If preferred, to not add clutter to the bank’s top-level folder, considering creating a new sub-folder in the bank’s folder.

Step Action

1 In Web Query, click the Reporting tab selector to display the Repository tree.

2 Browse to the bank’s folder at the top level of the Repository tree. The name and location of

this folder varies by bank.

3 (Optional) To create a new sub-folder to store the report, right-click the parent folder and select New » Folder.

4 Right-click the bank’s folder and select New » Report from the shortcut menu. InfoAssist launches.



Note: If the shortcut menu does not contain this option, the account does not have permission to edit the contents of the folder. Ask an administrator at the bank for

permission to access this folder.

5 When prompted to select a data source, browse to and select the SQL view that contains all or many of the fields to include in the report.

Each view has one of three scopes, which is indicated by the first two letters of its description:

FV: Full views provide access to every field in a file, like the Loan application master file/LNMAST.

PV: Partial views provide access to fields in a file that SHAZAM Core Services intentionally included because we expect the fields to be commonly used.

JV: Joined views provide access to fields from multiple files. SHAZAM Core Services joined these files because we expect the fields to be used together in a particular type of report.

6 Click the application menu button at the top-left corner and select Save As. The Save As dialog box indicates that the report will be saved in the same folder selected in step 4.



7 In the Title textbox, enter the title to be displayed by run-time users to see in Web Query

when they browse for reports to run. Consider including details that will help a user identify the report’s purpose.

8 Click Save.

Result: InfoAssist opens a blank report, shown below. For descriptions of the components in the InfoAssist user interface, refer to the Components of InfoAssist section in the report-development tutorial.



Where to Go Next • For instructions for several fundamental report-development tasks, refer to the tutorial for

customizing a standard report, but begin in the second section, Finding Fields to Present in the Report. To perform many of the tutorial’s steps in the new report, users typically must extrapolate the instructions to their own unique development goals.

• For instructions for additional ways users can customize existing reports, refer to the Instructions for Additional Development Tasks section.



Instructions for Additional Development Tasks The following sections contain instructions for accomplishing several common report-development tasks in InfoAssist.

Finding Data Sources

Accessing fields from more than one SQL view

Grouping Records

• Displaying column and row totals

• Dividing a report into sections with subtotals

• Starting new pages or lines to divide records

• Displaying sub headers and sub footers when a section, page, or line breaks

Acting on Data Values

• Sorting a report by a measure field

• Filtering based on the value of another field

• Displaying more advanced calculations on numeric data

Customizing the Output Users See and Generate

• Defining document- and page-level headers and footers

• Allowing users to filter records

• Presenting a report as a configurable application

• Setting in which output types users can generate a report

• Setting document-production properties

• Hiding repeated values in adjacent cells



Defining Document- and Page-Level Headers and Footers Complete the following steps to set the text that appears in the headers and footers throughout the report.

Step Action

1 Browse to the Home ribbon tab.

2 Click the drop-down arrow beside the Header & Footer button and select which header or footer to set:

• Report Header: Appears at the top of page 1 only

• Page Header: Appears at the top of every page

• Page Footer: Appears at the bottom of every page

• Report Footer: Appears at the bottom of the final page

3 The Header & Footer dialog box displays. This dialog box contains the features shown and described below.

To switch between editing page and report headers and footers, click the appropriate button at the top of this dialog box.

Preformatted values, which begin with an ampersand (&), indicate the system will insert an actual value when the report runs. For example, the system will replace &MR_FULL_FEXNAME with the report’s full title and &DATE with today’s date.

Field names, which begin with an angle bracket, are replaced with the field’s value when the report runs. To add a field name, drag the field from the Data pane into this dialog box.

To add preformatted values ( ) to a report, select the field of interest from this drop-down menu.

The following screenshot calls out where these features appear within a multi-page report.



Report header

Page headers

Page footers

Report footer



Hiding Repeated Values in Adjacent Cells Complete the following steps to display a value that repeats down a column only a single time. In the following example, in the Account Type column, D and S repeat in adjacent cells.

Step Action

1 Browse to the Format ribbon tab.

2 Click to disable the Repeat Sort Value button in the Features section.

Result: The report continues to sort the report by account type without repeating the same value multiple times.



Filtering Based on a Dynamic Value in a Field A simple filter includes records in a report by comparing a particular field in each record to a constant, hard-coded value. (See Selectively Including Records by Applying Filters for more information.) However, some reports require comparison to a dynamic value stored in a field rather than to a constant value. For example, consider a report that must include only accounts with activity during the past calendar month. Contrast the following ways that users can implement a filter to achieve this requirement:

• A simple filter can compare dates of last activity to a constant value, such as Month of Last Activity = 01/16. This requires users to update the date to 02/16, 03/16, and so on whenever the month changes.

• An advanced filter can compare dates of last activity to a field that stores the current calendar month. The system automatically updates the field value when the month changes, so the filter will always compare to the current month without requiring any ongoing maintenance.

Complete the following steps to create an advanced filter.

Step Action

1 Click the Data ribbon tab.

2 Click the Advanced Filter button. The Create a filtering condition dialog box displays and lists any filters already applied to the report, including simple filters.

3 Click the New Filter button. A new WHERE statement appears in the body of the dialog box.

4 In the first drop-down menu, shown above, select the field whose value to compare to

another field.

Tip: Use the buttons above the field list to change the display style:



5 In the second menu, select the comparison operation to perform. Users might need to double-click that area of the dialog box to make the menu active. In the previous screenshot, the operation is set to Equal to.

6 Double-click the final menu. In the Type menu, select Field.

Note: Although this menu also contains Constant and Parameter options, users can compare against constants and parameters by performing simpler procedures unless

users require the use of expressions. Refer to the steps for creating a simple filter for constants and for creating parameter-based filters, respectively.

7 Select the field to compare against.

8 Click OK to return to InfoAssist.

Result: As the following screenshot shows, the advanced filter appears in the Filter pane at the left side of InfoAssist. Notice that unlike a simple filter, such as the first filter shown, the advanced filter does not contain any hard-coded values because it compares dynamic values from two fields.



Creating Advanced Filters using Expressions, Groups, Filters Sometimes filter conditions need to be grouped together with either and/or OR if/then statements are needed in an expression to create the filter.

Complete the following steps to create an advanced filter that contains an OR statement.

Step Action

1 Click the Data ribbon tab.

2 Click the Advanced Filter button. The Create a filtering condition dialog box displays and lists any filters already applied to the report, including simple filters.

3 Select the last filter expression so that it is grey. Click Insert After.

4 This will add an expression and bring up a selection box for the first field. Click OR to choose

AND/OR.

5 In the first drop-down menu select the field whose value to compare to another field.

Tip: Use the buttons above the field list to change the display style:

6 Select the comparison for the filter. Users might need to double-click that area of the dialog

box to make the menu active. In this example this is set to Missing. When Missing is chosen,



there is no longer an option to select Value.

7 There may be times where filters must be grouped in order to produce the desired results.

The image below shows an example of a grouped filter. The grouped filters are enclosed in parentheses.

8 Click OK to return to InfoAssist.



Creating Parameters for Users to Configure When They Run a Report Run-time users often want to see a report’s results filtered according to the value of one or more parameters that they set. For example, a particular department might require a report of accounts with large balances, but different employees might want it to include accounts with balances greater than $10,000, $50,000, and $100,000. Instead of creating three copies of the report, each with a different hard-coded filter on the balance field, consider prompting the user to set the balance amount as a parameter prior to running the report.

To present users with a configurable parameter, create a filter with a prompt. When a user runs a report with a filter prompt, Web Query displays a Parameters screen, shown as follows.

Complete the following steps to create a filter with a prompt.

Note: Extrapolate these general steps to the unique report and development goals. These general steps are not intended to result in a functional filter.

Step Action

1 Determine which field the filter will evaluate in each record to determine whether to include that record. In either the Data or Query pane, click and drag that field to the Filter pane.

The Filter dialog box displays.

2 Click the Prompt button in the menu bar and use the following table to choose from the following values in the drop-down menu.

If… Then…

Users want the user to choose from a menu of every data

1. Select Prompt using Data Values (Dynamic). Dynamic refers to the fact that the menu



value that records contain in the data library

automatically populates with the current values in records.

2. Complete the steps for creating a dynamic prompt.

This behavior is useful because the report developer does not need to know and enumerate every possible value a user might want to filter on.

If users want the user to select from a set of pre-defined values

1. Select Prompt using Selection (Static). Static refers to the fact that users hard code the items that appear in the menu.

2. Complete the steps for creating a static prompt.

This is useful to restrict a user to selecting from only approved values. If a user selects a value that is not in any records, Web Query report does not return any records.

If users want the user to enter free-form values or text.

1. Select Prompt Using Text Input (Simple).

2. Complete the steps for creating a simple prompt.

This is useful if the report developer cannot anticipate the values in the field when developing the report and users who run reports will know which values are valid.

Creating a Dynamic Prompt Complete the following steps to prompt users with a parameter they configure by selecting from a drop-down menu of values in source records.

Before Beginning: This procedure assumes users have just completed the steps in Creating Parameters for Users to Configure When They Run a Report.

Step Action

1 Configure the following fields on the Filter dialog box.

Field Description



Operator menu Choose how Web Query compares the field’s values to the filter value(s) the user selects when prompted.

Variable The field that Web Query evaluates when filtering records. InfoAssist populates this field.

Prompt The text the user will see above the drop-down menu of values.

End users might require tips for selecting values for parameters correctly, so users can use this text to provide helpful information.

Allow Multiple Values for Prompt

Click to enable or disable the user’s ability to select multiple values for the prompt.

2 Click OK.

Result: The report appears as follows when the user runs it.

To edit an existing filter, right-click the filter in InfoAssist’s Filter pane and select Open » Simple Filter.

Creating a Static Prompt Complete the following steps to present users with a filter they configure by selecting from a set of pre-defined values.




Step Action

1 In the Add field, enter a value for users to be able to select when they run the report.

2 Click the Add button to commit the value.

3 Configure the following fields on this dialog box.

Field Description

Operator menu Choose the type of comparison Web Query performs between the field’s values and the value the user selects when running the report.

Variable The field that Web Query evaluates when filtering records. InfoAssist populates this field.

Prompt The text available for the user to see above the drop-down box. End users might require tips for selecting values for parameters correctly, so users can use this text to provide helpful information.

Allow Multiple Values for Prompt

Click to enable or disable the user’s ability to select multiple values for the prompt.

4 Click OK.




Creating a Simple Prompt Complete the following steps to present users with a textbox in which they can enter free-form values.


Step Action

1 Configure the following fields on this dialog box.

Field Description

Operator menu

Choose the type of comparison Web Query performs between the field’s values and the value(s) the user selects when running the report.

Variable The field that Web Query evaluates when filtering records. InfoAssist populates this value.

Prompt The text available for the user to see above the drop-down box. End users might require tips for selecting values for parameters correctly, so users can use this text to provide helpful information.

Tip: Because users can enter any characters, users might want to suggest a format. For example, it might append (MM/DD/YYY) to

the Prompt text to communicate the format in which to enter dates.

2 Complete the remainder of the procedure for creating a parameter. Click to return

3 Click OK.




Selecting the Format in Which Users Can Output a Report Depending on a report’s audience and purpose, users might want to allow or restrict the output type in which a report generates. Choose from the following options for controlling the output format.

If… Then…

Users want users to be able to select the output type they desire each time they run the report

On the Format ribbon tab, enable the User Selection button.

When a user runs the report, they can choose to generate the report in any of the available report types. See this behavior

Users want to set a default format that users can switch between as often as desired after they run a report

Complete these steps to display the report as an InfoMini:

1. On the Format ribbon tab, disable the User Selection button in the Output Types section.

2. Enable the InfoMini button in the Destination section of the Format ribbon tab.

3. Enable the button in the Output Types section that corresponds to the default format users want to generate.

The report automatically runs in the default format set by the developer. However, users can switch between formats. See this behavior

Note: In addition to allowing users to switch between output types, InfoMinis provide several other features.

For a full explanation, refer to the Presenting a Report as a Configurable Application (InfoMini) section.

Users want other users to view a report in only the format chosen

Complete these steps to set a single, required output type:

1. On the Format ribbon tab, disable the User Selection button in the Output Types section.

2. Enable the button in the Output Types section that corresponds to the format users must generate.



User Experience When Allowing Users to Select an Output Type When User Selection is enabled, Web Query presents users with the Parameters screen and a drop-down menu in which they select the type of output to generate.

User Experience When a User Runs an InfoMini When a user runs an InfoMini, the report automatically runs in the default format set by the developer. However, users can change the format by selecting the desired output format (2) on the Format tab (1) and rerunning the report (3).

For more information about InfoMinis, refer to Presenting a Report as a Configurable Application (InfoMini).



Sorting a Report by a Measure Field Records in reports typically sort according to the fields nested under the By node in the Query pane, which are typically non-numeric and date fields. However, users can complete the following steps to instead sort the records in a report according to the numeric values in a Sum/measure field.

Step Action

1 With the report open in InfoAssist, select the numeric field whose values users want to use to sort records. Users can select the field in the Query pane or select the field’s column in the Live Preview window.

The Field tab on the ribbon displays.

2 On the Field ribbon tab, click the Up button to sort values from smallest to largest or click Down to sort from largest to smallest.

Result: The Live Preview window re-sorts records according to the type of sort applied. In the following example, notice that the report is sorted according to the LTD Overdraft Fees field rather than Customer ID. Web Query would typically sort the report by Customer ID because it is the only non-numeric/non-measure field.

In the Query pane, InfoAssist indicates that the report is being sorted by values in a numeric measure field by displaying that field’s name under the By node with a sort glyph, shown as follows. Notice that this field also remains under the Sum/measure node.



Customizing the Layout of a Report in Output Documents As in other document-production software, Users can customize how Web Query lays out reports when it generates them as documents. Complete the following steps to set the margins, orientation, and other settings that apply when a report is produced as an HTML page, PDF file, or any other output type.

Step Action

1 Click the Layout tab on the ribbon.

2 Use the options on this tab to customize document-production settings.

Note: For more information about the options on the Layout tab, launch the InfoAssist Help by

clicking the Help button at the top-right of the window and browsing to the topic at InfoAssist » Navigating the InfoAssist Interface » Layout Tab in the table of contents.



Grouping Results and Displaying Their Subtotals Users can group a report’s results to summarize information for particular categories of records. For example, rather than reporting a single list of all overdraft accounts and a single grand total of all their balances, users might want to group and visually separate overdraft deposit accounts from overdraft savings accounts and display a subtotal for each section. This functionality is referred to creating a break.

Users can create a break that starts a new page or inserts a dividing line between sections, or users can create a break that does not apply any special formatting. For all three types of breaks, users can present subtotals and/or sub-headers and footers within each group.

Complete the following steps to implement breaks with subtotals and sub-headers and footers.

Step Action

1 In Web Query, create and open a copy of the ID5358 standard report located in the Base Reports - Deposits folder.

2 In InfoAssist, observe the role that breaks play in this report. The following screenshot and callouts explain how break-related features affect the report’s appearance.

Note: The report might appear differently depending on the data in the library loaded in WebQuery. For example, if the library does not contain any overdraft savings

accounts, the report will not display a group for them.

The records in this report are divided into two groups, one for demand deposit accounts and one for savings accounts. The two rows called out with ( ) are sub-headers, and they begin each group.

Each group ends with the sum of the Current Bal fields in that group’s records. The two rows called out with ( ) are subtotal lines.

Each group has a sub-footer row ( ) that displays the number of accounts in the group.

The grand total at the bottom of the report sums the value of all the Current Bal field in each record in the report regardless of which group contains it.



3 In the Data pane, browse for and add the Available Bal/DDAVAILABLEBAL field to the report as a measure field under the Sum node in the Query pane.

Tip: It’s useful to learn how to configure multiple subtotals, so this procedure has users arbitrarily adding Available Bal as a second measure field (Current Bal is the first).

4 In the Query pane, select the Account Type field under the By node to display the Field tab on the ribbon. Recall from the step 2 screenshot that the report is grouped into groups based on account type.

Notice that although Account Type was listed in the Query pane, this field does not appear in the report as a column. For information about this design decision, refer to Hiding Fields That Users Present in a Sub-Header.

Note: Users can divide a report based only on fields that are categorized under the By node in the Query pane. In other words, users can only divide a report on sort fields

and not measure fields like Current Bal whose values are summed or otherwise aggregated.

5 In the Break section of the Field ribbon tab, notice that the Subtotal button is enabled.

Because subtotals are enabled, lines such as the following appear after each group in the report.

6 Click the drop-down arrow beside the Subtotal button and select More Options. The

Subtotal dialog box displays. Notice in the table that the default setting is to subtotal both measure fields in the report.

7 To gain control over the individual measure fields, remove the checkmark from the Subtotal

all fields checkbox.

8 Place a checkmark in the Current Bal checkbox.



9 Click the Current Bal row’s cell in the Prefix column so it becomes a dropdown menu. Select Average. This menu lists the ways the subtotal line can summarize a field’s values in each group.

10 In the Subtotal Text section at the right of the dialog box, replace the current text with Avg

OD Bal for Account Type:

Tip: This example text ends with a colon (:) because subtotal lines automatically append the value of the break field to the label. For example, the original subtotal text

of Total OD Accounts-type: displays as Total OD Accounts-type: D for the deposit-account group because D is the value of the break field (Account Type).

11 Click OK. The subtotal line now displays the average of the Current Bal field for the records in each group but does not display a subtotal for the Available Bal field because it was disabled in step 8.

12 On the Field tab in the ribbon, click the Sub Header button.

The previous steps focused only on the subtotal rows in groups. The remainder of this procedure explains how to configure sub-header and footer rows for groups.

13 The Sub Header & Sub Footer dialog box contains the features shown and described below.



Hard-coded text appears in each sub-header row exactly as it was entered.

Field names, which are preceded by angle brackets, specify that Web Query will insert the actual value of that field. For example, Web Query inserts D for the group that contains deposit accounts.

<AcctTypeDescr is a calculated field and does not reside in a SQL view, so its field name is not preceded by the name of a SQL view like the name for DDAACCTTYPE.

Tip: Click the Sub Footer button at the top of the dialog box to switch between configuring the sub-header and sub-footer rows.

14 At the end of the current sub-header text, enter the word at followed by a space.

15 Without closing the Sub Header & Sub Footer dialog box, browse in the InfoAssist Data pane for the Bank Name/BANKNAME field. Click and drag the Bank Name field to the end of the sub-header text so it appears as follows, and then click OK.

Account Type: <VDDMAST_FULL.VDDMAST_FULL.DDACCTTYPE <AcctTypeDescr at <VDDMAST_FULL.VDDMAST_FULL.BANKNAME

Result: Above each group of records, a sub-header row (highlighted below) displays the combination of hard-coded and dynamic text that was entered, including the dynamically populated bank name.

As in step 11, the subtotal row displays the average current balance of overdraft accounts. Also shown below is a sub-footer row, which users would configure the same way it was configured the sub-header row in steps 12-15.



Hiding Fields That Are Presented in a Sub-Header If group sub-headers present the value of a field, consider hiding that field within the report by right-clicking the field in the Query pane and selecting Visibility » Hide.

The following report breaks based on the Account Type field. The sub-header at the start of the group displays this field’s value (Account Type: D), but this field does not appear in the report as a column.

This report intentionally hides the Account Type field because also displaying it as a column would be redundant.



Starting a New Page or Line When a Field Changes Value To separate records with different values in a field, users can force a report to break to a new page or line:

• A page break causes Web Query to stop printing on the current page and to move to the next page.

• A line break causes Web Query to display a thick horizontal line between groups of records with different values in a particular field.

Enabling Page or Line Breaks Complete the following steps to enable page or line breaks that take effect when a particular field has different values from record to record.

Step Action

1 In the Query pane, select the field whose value Web Query evaluates for changes in value. The Field ribbon tab displays.

2 Click the Page Break or Line Break buttons to enable the feature to implement.

3 (Optional) Implement subtotals, sub-headers, or sub-footers to present explanatory details at the beginning or end of each group of records created by a break. For step-by-step instructions for implementing these features, refer to the procedure for grouping records.

Result: InfoAssist begins dividing groups across pages or with horizontal lines, depending on which feature was enabled. The following examples show how each feature appears in a report.

Example of Page Breaks In the following report, page breaks are enabled on the Product Description field. This means page 1 ends when the report has no more Charge off checking accounts to print even though the page will have a large amount of empty space. Page 2 ends when the report has no more Commercial Checking accounts to print.



Example of Line Breaks In the following example, line breaks are enabled on the Product Description field, so a thick horizontal line separates Regular Checking records from Statement Savings records.



Applying Mathematical Functions to Numeric, Measure Fields Numeric fields are organized under the measure node in the Query pane allow their values to be aggregated in some way. By default, this node is labeled Sum and fields nested beneath it have their values summed and displayed in a column-total row at the end of the report. To apply a different function, right-click the node and choose from the options shown in the following screenshot. For descriptions and examples of each option, refer to Report-Level Aggregation Functions.

Applying Mathematical Functions on a Field-By-Field Basis Instead of applying the primary function, such as Sum, to every field under the measure node, users can apply a function to one or more fields. For example, users can display a particular field’s values as a count while other fields are expressed as amounts and summed. The following report snippet shows the Account Number field with the count function applied and the Curr Bal field being summed with the Sum function applied.

Complete the following steps to apply a function to a measure field that is different from the primary function.

Step Action

1 Right-click the measure field to apply the new function.

2 Select More » Aggregation Functions and choose from the available options in the shortcut menu. For a list of the options, refer to Field-Level Aggregation Functions.

Result: The following screenshot shows how this behavior is configured in the Query pane. The primary function is Sum, but the Account Number field has the Count function applied as indicated by the CNT prefix on that field’s name.



Note: If users change the Query pane node from Sum to Print, Count, or List, it overrides all assigned aggregation type values at the field level.



Displaying Numeric Totals at the Ends of Columns and Rows Before Beginning: This procedure assumes users have access to a report that contains at least two numeric fields that are nested under the Sum/measure node in the Query pane. For the sake of this example, the report contains the amounts of overdraft and return fees that customers have been assessed during the time they have been customers.

Complete the following steps to implement column and row totals.

Note: Extrapolate these general steps to the unique report and development goals.

Step Action

1 To display grand totals of both fee columns, click the Home tab in the ribbon.

2 Click the Column Totals button. A grand total row appears at the bottom of the report.

3 Click the drop-down arrow beside the Columns Totals button and select More Options to

display a dialog box where users can customize the column-total row. The following screenshot calls out and explains the following customizable options in the dialog box.

By default, the report will display totals for both measure fields. To gain control over individual fields, remove the checkmark from the Total all fields checkbox.



In the Prefix column, users can change how Web Query expresses the values in the total row. For example, instead of summing the values in a column, users can display the average of all the values in the column.

In the Total Text section at the right of the dialog box, enter the text to display as the label for the column-total row.

4 Click OK to apply the changes to the column-total row at the end of the report.

5 Back on the Home ribbon tab in the InfoAssist environment, click the Row Totals button to display a new column at the right of the report that sums the numeric values in each row. The following screenshot shows this example report with both a column-total row and a row-total column.



Adding Fields from a Second View Cardinal Insight’s views are designed to contain the fields typically used together in a report. However, if users need to use fields from multiple views, add a join between the original view and the additional view. A join identifies a field that both views contain and allows the data in each view to be synchronized.

Before Beginning: All fields in a view are available for users to join on. Therefore, ensure users are familiar enough with the views to ensure the fields selected are appropriate matches.

Complete the following steps to add a join between two views.

Step Action

1 In InfoAssist, open the Data tab and click Join. InfoAssist displays the fields in the view that was selected when the report was originally created.

2 Click Add New at the top of the dialog box.

3 When prompted, browse for and select the view whose fields users need to access. InfoAssist displays the two views side-by-side.

4 Notice that InfoAssist typically creates a join between the two views. If this happens and the join is not on the desired fields, select the join (indicated with the arrow shown below) and click the Remove button.

5 Browse for a field that both views share and then click and drag the field in the primary view

to the same field in the new view.

Tip: Click the Name column header to sort fields alphabetically and make them easier to find.

The following example shows two views joined on their account-number fields. Notice that although the fields have slightly different names, they do represent the same data in the data library.



6 To select the type of join, click the join arrow to make it active/red and then click the Edit

button. In the Edit Join dialog box, configure the following fields:

• Instances: Select Single if there is a one-to-one ratio between the records in the first view and the records in the second view. Select Multiple if for every record in the first view, there are multiple records in the second view.

• Type: Select Inner to return rows when there is a match in both tables. Select Left Outer to return returns all rows from the left table, even if there are no matches in the right table.

Tip: If the drop-down menus do not open, log out of Web Query completely and then sign back in. Re-try the action desired. If users continue to experience issues with the

drop-down menus, considering creating joins using Internet Explorer.

7 Click OK to save the join. The fields in the new view will now be available in the Data pane.

Tip: If users want the report to include the shared field that appears in both views, SHAZAM Core Services recommends that users use field located in the primary view rather than the field in the

joined view. This way, if users later decide not to use fields from the joined view, they can remove the join without affecting the shared field in the report.



Presenting a Report as a Configurable Application (InfoMini) An InfoMini is an application built from a report that provides run-time users with a subset of InfoAssist functionality when they run the report. This is useful for non-technical users who want the flexibility to perform data analysis on reports but who do not have access to InfoAssist.

What is an InfoMini? An InfoMini works like an application skin around reports that have been generated as output, such as PDF and HTML output. This format works like an application in that it exposes configuration options with which users can dynamically refine the report. In other words, users can perform the following workflow all without exiting the report instance:

1. Run a report an initial time

2. Set initial parameters

3. See the report output

4. Update the report parameters

5. Re-turn the report in the same InfoMini application instance

6. Watch the output change in response to the new parameter values

InfoMinis versus Filter Parameters The configurable options exposed to users in an InfoMini work similarly to filters that prompt users to set them at run time. However, whereas users can configure filter prompts only a single time prior to running a report, they can configure and reconfigure InfoMini options any time and re-run the report without closing the InfoMini window.

Features of an InfoMini InfoMinis expose report options on a ribbon, similar to the ribbon in InfoAssist. This ribbon contains the following tabs:

• The Format tab allows the user to switch between the output type in which the report displays, such as HTML, PDF, and so on.

• The Slicers tab exposes menus from which users select criteria on which to filter records.

Creating an InfoMini Complete the following steps to create an InfoMini.

Note: Extrapolate these general steps to the unique report and development goals. These general steps are not intended to result in a functional InfoMini.

Step Action

1 Open a report in InfoAssist.



1 Configure the following options on the Format ribbon tab to configure a report as an InfoMini:

A. In the Destination section, enable the InfoMini button.

B. In the Output Types section, disable the User Selection button.

C. In the Output Types section, enable the button that corresponds to the default output type, such as HTML or PDF, that users want to generate when a user runs the InfoMini.

2 Click the Slicers ribbon tab. By default, the Slicers tab contains one empty group, shown as follows.

Note: A slicer is an option in a group that users configure to filter, or “slice,” the records that Web Query returns. A slicer group is a collection of these options visually

organized between two vertical lines, such as Record Limit in the following screenshot.

3 In the Data pane, browse to the ACCTTYPE/Account Type field.

4 Click and drag the field to the Group 1 section on the ribbon to create a slicer based on this field. The slicer appears as an empty drop-down menu.

5 Toggle the operator button to set whether Web Query returns only records whose Account

Type field contains the user-selected value ( ) or only records that do not contain that value

( ).

6 Click the slicer’s drop-down arrow to set a default value that appears in the slicer when a user runs the InfoMini. Users can also leave the slicer empty.

Tip: To select multiple values on which to filter, <Ctrl>-click the values in the value-select dialog box.

7 In the Data pane, click and drag the PRODTYPE/Product Type field to the Group 1 group. The two slicers appear side-by-side.



8 Click the configuration glyph at the bottom-right corner of the Group 1 group to display

the Edit Slicers dialog box. The following screenshot and callouts explain the features for configuring how users interact with the slicers added.

Switch between the available slicer groups to configure the slicers in that group and the group’s label.

Enter a user-friendly description to serve as a label on the slicer group.

Select a slicer and use the buttons above the table to change its horizontal position on the ribbon or to delete the slicer.

Select whether users are required to configure a particular slicer before the report runs. When users mark a slicer as required, the InfoMini will display an asterisk beside its label to indicate to users that they must configure it:

9 Click OK to commit the changes.

10 (Optional) To see the InfoMini as users will see it, click the Run button in the InfoAssist menu bar.

Result: The report displays as an InfoMini. The following screenshot shows and explains how users interact with an InfoMini.



Users can configure options on both tabs:

• Format—Switch between the output type in which the report displays, such as HTML, PDF, and so on.

• Slicers—Select the criteria that records must meet to be included in the report.

Users have access to the slicers but not to the slicer-configuration dialog box, so they cannot move or delete slicers.

After setting new options, users can re-run the report to see the corresponding results.

Reordering or Deleting a Slicer Group Complete the following steps to change a slicer group

Step Action

1 On the Slicers ribbon tab, click the configuration glyph at the bottom-right corner of the

Options group to display the Edit Slicers dialog box. This is the same dialog box used to configure and delete slicers within a group.



2 With the General group selected at the left side of the dialog box, select a slicer group and use

the buttons above the table to change the horizontal position of a group, hide a group, or delete a group.

3 Click the Update Preview button to refresh the Live Preview window.

Changing an InfoMini to a Regular Report Complete the following steps to return an InfoMini report to a regular report.

Step Action

1 Configure the following options on the Format ribbon tab to configure an InfoMini as a regular report:

A. In the Destination section, disable the InfoMini button.

B. In the Output Types section, enable the User Selection button.

C. In the Output Types section, enable the button that corresponds to the default output type, such as HTML or PDF, that users want to generate.

2 On the Slicers ribbon tab, clear the values in each slicer. If users do not intend to ever use the report as an InfoMini again, delete any slicer groups.

Note: If users complete step 1 but leave slicers configured, the Live Preview window might continue to filter based on their default values.

3 On the Slicers ribbon tab, click the Update Preview button to refresh the Live Preview window.

Result: When a user runs the report, the Parameters screen prompts them to select an output type. The generated report does not display within the InfoMini application skin.



Allowing Further Processing of Report Results After an end user runs a report, he or she typically cannot perform additional processing on its results. To perform processing on report results, users must perform the following tasks in InfoAssist:

• Configure the report to save its results to file

• Develop a new report that loads and presents the results as desired. Some use cases might require creating multiple new reports that function like a multi-step report.

The following illustration shows how the results of two reports might be consumed and further processed when users run a third report.

Case Study: Multi-Step Reports To become familiar with a use case for multi-step reports, consider the following report that displays one row per account, including for the highlighted customer who holds multiple accounts.

Assume that the goal is to allow end users to filter this report so it includes only customers whose combined Current Balance exceeds a user-defined threshold. Web Query cannot filter these results that way because rows cannot be combined for a customer without altering the report significantly. To allow end users to filter combined balances, users must instead combine the balances in a second report.

Note: A later section provides instructions for saving the original results and processing them in another report. Continue reading to learn more important concepts about multi-step reports.



The following simple example of a consumer/processor report sums the Current Balance fields from the first report and displays the total for each Customer ID. The highlighted row calls out the same customer who has multiple records in the original report.

Current Balance summed by Customer ID Current Balance field is to be summed

The summed Current Balance values appear able to be filtered. However, Web Query cannot filter them as desired because they are still composed of multiple records. This behavior is more evident if users change the measure field in the Query pane from Sum to List because the Current Balance column again displays each of the customer’s accounts as separate records.

If users apply a filter to the Current Balance field, Web Query filters the value of each individual balance, just as in the original report. Therefore, the second report’s Current Balance results are also incapable of being processed as desired. Because this second report presents the combined balance per customer ID, its results can be consumed by a third report and be filtered by end users. The following illustration shows how the results from the original, or base, report are transformed from report to report until end users can filter them in the final report. In this example, assume the threshold is $500.

The number of reports users must create depends on the state of the results in the base report and how users want to transform them.



Designing a Multi-Step Report To make a report’s results accessible outside of that report, such as by another report, save its results in a temporary hold file. A hold file stores the output of a report in a file that users can use as input to another Web Query report. The following sections guide users through implementing the use of hold files to accomplish the goal described in the previous section: to allow end users to filter a report of account balances so that it includes only customers whose combined Current Balance exceeds a threshold.

Note: Extrapolate these general steps to the unique report and development goals. These general steps are not intended to result in a functional filter.

1. Developing the Base Report and Creating the Intermediate Report Complete the following steps to configure a report’s results to serve as the source of data for another report.

Before Beginning: If an existing report already produces results that users want to further process, create a copy of the report and open the copy.

Step Action

1 Prepare a report that contains all fields to include in the report that end users will run. For example, if users plan to include fields in headers or footers within the final report, such as the bank’s name, add those fields to this base report.

The following screenshot shows an example of a base report that displays one row per account, even for a customer who holds multiple accounts. End users will not see the base report, so its appearance is not important.

2 (Optional) Add any filters that needed to apply to the results from the data library.

Filtering out unwanted records before other reports consume the results reduces the amount of data that Web Query needs to save to and load from file.

3 On the Home tab, click File & Printer in the Format group.

4 Select File in the Destination drop-down menu.



5 Enter a name for the file that will store the report’s results ( ).

Note: SHAZAM Core Services recommends that users leave Temporary ( ) selected in the pane at the left rather than saving hold files in a folder. A temporary hold file is

deleted after its results are processed, which ensures that the bank’s data remains secure and that users always use the latest data available rather than stale data from a previous run.

6 Enter a name for the file that will store the report’s results.

7 Click Save to return to the File & Printer Options dialog box, and then click OK. The

following menu appears at the bottom of the Live Preview window:

8 Select Create Report. InfoAssist creates a new, blank report whose data source is the hold file saved in this procedure. In this tutorial, this new report will serve as the intermediate report.

9 Save the report with a new filename.

Result: Onscreen is the starting point for an intermediate or end-user report. The base report is configured to send its results to a hold file instead of returning them to Web Query.

As the following screenshot shows, the Data pane contains only fields that are in the base report.

This is sufficient if the new report requires only those same fields. However, if the report requires additional fields, users can add an additional data source or join the hold file to another file and then use fields from either source.



Note: To access this functionality, browse to the Data ribbon tab, where Data Source section contains Add and Switch options. For instructions about joining files, refer to Adding Fields

from a Second View.

The Query pane contains a cylindrical data icon with the name of the hold file (ZCustDetSteve) followed by the SQL view assigned to the base report (VLOAN_MONTHEND).

Users can right-click the hold file name to edit, delete, or preview the file. Be cautious when editing a hold file. For example, do not remove a field from the hold file that the new report depends on.

2. Developing the Intermediate Report and Creating the End-User Report (Part 2 of 3) Complete the following steps to process the results of the base report. This report exists solely for processing and is not intended for end users to run. If the processing users do in the base-level report is sufficient, proceed to the part 3 procedure.

Before Beginning: These steps assume users completed the part 1 procedure to develop the base report and create a blank intermediate report.

Step Action

1 Add any fields whose values needed to process in the intermediate report.

The following example processes the results from the base report by summing the account balances for each customer ID. Recall that by default, the hold file users created in the previous procedure is the data source for this report.

2 On the Home tab, click File & Printer in the Format group.

3 Select File in the Destination drop-down menu.

4 Click Browse beside the File Name field.



5 Enter a name for the file that will store the report’s results ( ).

Note: SHAZAM Core Services recommends that users leave Temporary ( ) selected in the pane at the left rather than saving hold files in a folder. A temporary hold file is

deleted after its results are processed, which ensures that the bank’s data remains secure and that users always use the latest data available rather than stale data from a previous run.

6 Click Save to return to the File & Printer Options dialog box, and then click OK. The following menu appears at the bottom of the Live Preview window:

7 Select Create Report.

8 Save the report with a new filename.

Result: Onscreen is the starting point for an end-user report. The intermediate report is configured to send its results to a hold file instead of returning them to Web Query.

Observe the following features of the InfoAssist user interface.

The Data pane contains the fields in the report that was open when this new report was created.

The Query pane’s Files node lists the hold files to which the base and/or or intermediate reports have their results saved.



3. Developing the End-User Report Complete the following steps to process and present the results of a base and/or intermediate report in a report that end users can run.

Before Beginning: These steps assume users completed the part 1 and/or 2 procedures and have a new, blank report whose data source is a hold file users created while performing those procedures.

Step Action

1 If users need to access fields from the base report that are not in the intermediate report, complete the procedure for joining SQL views, but join the two hold files rather than Cardinal Insight views.

Note: When users join the intermediate hold file to the base report’s hold file, users must decide whether to implement a multiple link or single link. A single link is most

appropriate for the following reasons:

• The Customer Balance field is part of the intermediate hold file, so there is one record for each customer in the Left file.

• The base report’s results (the Right file) have multiple records for each customer ID.

Therefore, adding fields to the end-user report that have multiple values in the base hold file will inflate the numbers. This means a Single link is most appropriate.

2 Add the fields to display to end users. Notice that when a field exists in both hold files, the Data pane contains two instances of that field: the intermediate report’s field, which has values that have been processed, and the base report’s field, which has original, unprocessed values. Refer to the Filename or Segment properties to identify which hold file is the source of a field.

3 Finish developing the report according to end-user requirements.

Result: When an end user runs the final report, Web Query performs the following actions to generate fully processed results for the end user.



Linking from Report Results to another Report To allow end users to more easily navigate from one report to another report that contains related information, users can implement hyperlinks in the first report. Users can also configure links to open the second report as-is or even open the second report with its results automatically filtered. Consider the following example and illustration of how the latter behavior is useful:

• A high-level report, ILN5726L, lists the combined balances of loans that fall under each regulatory report code. For example, five loans fall under code 1B00, which is highlighted in the following illustration.

• When an end user clicks the linked Reporting Description for the 1B00 record, a more detailed report opens, ILN5726HL, and is automatically filtered to include only loans with the 1B00 code.

These links are referred to as drill-downs because they allow end users to navigate from a higher-level report down to a lower-level report about a value of interest. In this example, the summaries of each regulatory report code are high-level, while details about loans with code 1B00 are low-level.

Note: Users can implement simpler links, such as links to a web page or to an unfiltered report. Although the instructions that follow briefly note how to implement simple links, it focuses on

implementing drill-down links.

Naming Convention for Built-In Reports with Drill-Downs In Cardinal Insight’s built-in reports, a report number suffixed with the letter L, such as LN5726L, indicates the report contains links. A report number with an HL suffix indicate that another report links to it.



Implementing Drill-Downs When users click a drill-down link, Web Query automatic filters the low-level report by passing a value from the clicked record to the low-level report as a parameter value. To implement this behavior, users perform a two-part process:

1. In the high-level report, add hyperlinks and identify which field serves as the parameter.

2. In the low-level report, users must enable the report to receive a parameter value so its results can be filtered according to that value. The following sections provide instructions for this process.

1. Adding Hyperlinks to Fields Complete the following steps to implement drill-down links to a lower-level report.

Before Beginning: These steps assume that the lower-level report already exists, and that both reports contain the field whose values users want to filter when an end user opens the lower-level report via link.

Step Action

1 In the Query pane or Live Preview window, select the field to which to apply links. The Field tab displays in the ribbon.

2 In the Links group on the ribbon, click the Hyperlink button. The Drill Down dialog box displays.

3 Select the Report radio button.

Note: If users want to link values in the field selected to a web page rather than a report, select the Web Page radio button and enter the URL.

4 Click the Browse button beside the Report field and browse the Repository tree structure

to the report to which users want to link. Select that report and click Open.



5 In the Target menu, select New Window to open the second report in a new browser window or Same Window to leave the first report for the second.

Note: If users want the links to open the lower-level report without automatically filtering its results, users can stop here. It is not necessary to perform the remaining

steps in this procedure or in part 2 of the drill-down process.

6 Above the Parameters table, click the Add Parameter button . The Drill Down Parameter dialog box displays.

7 Enter a unique name in the Parameter Name field. Later, in the lower-level report’s definition, users must reenter this exact name so the report can receive parameter values from the higher-level report.

8 In the menu below the Field radio button, select the field whose value to pass to the lower-

level report as the parameter value. The lower-level report must also contain this field so the report results can be filtered by the field’s value in the clicked record.

Note: This can be the same field to which users are adding links, or it can be a different field. In the introduction to drill-downs, the example shows the code

description field containing links, while the code field is the drill-down parameter whose value passes to the lower-level report.

9 Click OK to exit the Drill Down Parameter dialog box, and then click OK to exit the Drill Down dialog box.

Result: Values for the field now contain links. These links will launch the lower-level report, but the results will not be filtered because that report is not yet configured to apply parameter values.

2. Enabling the Target Report to Apply a Filter Complete the following steps to configure the lower-level target report to apply parameter values from the higher-level report.

Before Beginning: Users must complete the first part of this procedure, Adding Hyperlinks to Fields.

Step Action

1 Open the report users selected as the link destination in step 4 of the previous procedure.



2 Ensure the Query pane contains the same field that was configured as the drill-down parameter for the higher-level report. Users performed this task in step 8 of the previous procedure.

3 Click and drag the field to the Filter pane. The Filter dialog box displays.

4 Click the Prompt button in the menu bar.

5 Select Prompt using Data Values (Dynamic).

6 In the Variable field, enter the same name that was entered as the drill-down parameter name in step 7 of the previous procedure. This name is case-sensitive.

7 In the Prompt field, users can enter a label for the menu of parameter values. However, the menu and label will be visible to end users only if they run the lower-level report independently of the higher-level report.

8 Click OK and then save the lower-level report.

Result: When users run the higher-level report, links appear on values in the column where they were added. When users select a link, results for the lower-level report display. These results are filtered according to the parameter value that corresponds to the link clicked in the higher-level report.

Note: If the lower-level report contains parameters other than the drill-down parameter, Web Query prompts users to set those parameters but not the drill-down parameter.

Troubleshooting When Lower-Level Results Do Not Filter Correctly If Web Query prompts users to set the drill-down parameter rather than automatically applying its value, ensure that users entered the drill-down parameter’s name in step 6 exactly as it was entered it when users defined the drill-down parameter. The name is case-sensitive.



Distributing Reports to a Cardinal Core Distribution Point Users can distribute Cardinal Insight reports to bank employees or to a cold-storage system via the Cardinal Core information distribution system, also referred to as report distribution. Whenever an end user runs a report in Web Query that is configured to be distributed, its results are available in the distribution point(s) to which it is assigned. Supported types of distribution points include printers, output queues on the iSeries machine, integrated file system (IFS) directories on the iSeries machine, and email.

For a general, more-detailed introduction to report distribution, refer to the Distributing Reports and Other Documents document posted at SHAZAM.net > Core Client Login > Documentation.

Before Beginning The process of configuring a report to be distributed differs for Cardinal Insight standard reports and for the bank’s custom reports. Use the following table to proceed.

If… Then…

Users want to distribute a standard report to a distribution point

Complete only the third task, Adding a Report to a Distribution Point, because standard reports are already prepared for distribution and defined to Cardinal Core.

Users want to distribute one of the bank’s custom reports

Complete each of the tasks that follow.

1. Preparing a Report for Distribution For a report to be distributed, users must first remove any user-configurable prompts and identify the Web Query outque to which the report is sent.

Complete the following steps in Web Query to create a version of a custom report that is suitable for distribution.

Step Action

1 In the Repository tree, right-click the report to distribute and select Edit. The report loads in InfoAssist.

2 Select File » Save As and save a copy of the original report to the Rpt Dist folder within the same top-level folder as the report edited. It might be helpful to reuse the same report name so that other users can identify the distributed report’s relationship to the original report.

Caution: Be aware of the following length restrictions when saving the report copy. The length of the report name, such as ID5330 NSF Fees Changed in

Online Reentry, must not exceed 60 characters. The combined length of names of folders the report resides in must not exceed 40 characters.

3 Review each item in the Filter pane. For any filter that is configured to prompt the user for input, right-click the item in the Filter pane and select Exclude.




4 On the Format tab in the ribbon, ensure the User Selection option is toggled off to disable output-type prompt.

5 On the Home ribbon tab, select File & Printer » Set location and format.

6 Select Printer in the Destination drop-down menu.

7 In the Printer Name textbox, enter the following value: WQOUTQ

8 Save the report.

Result: Each time a user manually runs the report, its results are sent to the outque. Users can continue to run the original report with prompts, if desired, and the original report’s results are not distributed.

Note: Remember that any changes users make to the original report do not apply to the new version just created, and vice versa. Therefore, if users want the reports to function identically, it

might be necessary to make the same change to both reports.

2. Defining the Report within the Information Distribution System Complete the following steps in Compass XD to define a Cardinal Insight report to Core so that it can be distributed to an outque.

Step Action

1 Select Parameter Maintenance.

2 Select the following:

• Module Name: Bank

• Parameter File: BKRPGM (Report Distribution Programs/Reports)



3 Select Submit.

4 Reports will be listed in alphabetical order.

Enter the report name directly in the Search field.

5 Complete the following Information.

Field Description



Report program name

The name keyed in the Search field will populate here.

Report Alternate Title

Can be left blank.

Application Code The ID for the application to which this report belongs. Enter the ID from the following list that corresponds to the report’s Web Query folder:

• CS Customer Information • BK Bank • DD Deposits • LN Loans • MS Miscellaneous • GL General Ledger • SH Shareholders • IN Investments • SB Safe Deposit Box

Selection code text

Leave this field blank.

Word processing document

Set this field to N because the report program is not a Microsoft® Word® or Office Vision document.

Number of Word copies

Leave this field blank.

Insight Report Path

Return to Web Query.

• Right-click the report in the Rpt Dist folder and select Show Path.

• Press <Ctrl-C> to copy the path.

• Return to Compass XD and paste the path in the Insight Report Path field.

Report Description The text portion of a report’s name from Web Query. It might be helpful to reuse the same report name so that other users can identify the distributed report’s relationship to the report in Web Query.

Form Type Ensure this field contains *STD

Use selection code Ensure this field contains N.

Print file name The numeric portion of a report’s Web Query name, followed by the letter P. For example, ID5300P for a report in Web Query whose name begins with ID5300.

Query Report Select I (Insight) to indicate this report is a Cardinal Insight report.



Allow view of spool file

Whether a report should be viewed through Display Print programs BK8505, BK8506, and BK8507. For example, users might want to set this field to N for a general ledger report that contains sensitive information that should not be accessible by any user. If this field is set to N, give access to a specific user via insider codes.

6 Select Submit.

All changes will be saved and can now be added the report to a Distribution Point.

3. Adding a Report to a Distribution Point Complete the following steps to add a standard or custom Cardinal Insight report to a distribution point, such as a printer or list of email addresses.

Before Beginning: This procedure assumes that users want to add a report to an existing distribution point. For instructions for adding and configuring a new distribution point, refer to the Distributing Reports and Other Documents document posted at SHAZAM.net > Core Client Login > Documentation.

Step Action

1 Select Parameter Maintenance.

2 Select the following:

• Module Name: Bank

• Parameter File: BKRDST (Distribution Points)




3

Select the Edit button for the Distribution Point.

4 Select the Report Selection tab. Select Add.

5 The Report Add window will display.



6 To add a report:

Select the checkbox next to the report being added.

Repeat these steps for each report being added to the distribution point.

Select Submit.

7 Added reports will be displayed in the Report Selection window.

8 The reports are set by default to print daily.



9 To change the print of a report:

• Select the Report Selection tab.

• Select the Edit button for the report to be changed



10 Complete the following table for report printing: Example below details report printing at month end.

• Print Daily: Defaulted. This box will need to be unchecked to change the times for printing.

• Number of Copies: Enter the number of copies to be printed.

• Next Date: Enter the next day for print.

• Day of Month: Enter the Day of the month (EX: 31 to print each end of month)

• Freq: Enter the frequency for the report.

• Freq Code: Enter the frequency code – M = Monthly, D = Daily

• Print Before/After Closed: Enter if the report needs to be printed prior to Closed status. This flag looks at the calendar of the Bank and Nightly Processing.

B = Before, A = After

11 Select Submit to complete the edit changes to the print selection.

12 Select Submit to complete the adding of reports.

13 (Optional) Check whether the distribution point also has an RPG report with similar contents enabled and consider disabling it. For example, the DD5330 RPG report and the ID5330 Web Query report both present a list of NSF fees changed in online NSF reentry, so distributing both reports is redundant and might confuse recipients of the reports.

Note: If a user runs a report from the Rpt Dist folder, the report is sent to the distribution point to which it was added. Web Query displays the following message to the user because the results were

Note: If the report needs to print on the last business day of the month, the user should always select B= Before. By using this option, when the calendar day of the month falls on a

weekend the report will print on the day expected.



sent to the distribution point, as the second statement explains (italics for emphasis). This behavior is expected.

Your request did not return any output to display. Possible causes: - No data rows matched the specified selection criteria. - Output was directed to a destination such as a file or printer. - An error occurred during the parsing or running of the request.



Looking Up Error Codes As users develop and test reports, InfoAssist might display error messages or numeric error codes. Complete the following steps to find more information about a particular error code.

Step Action

1 Record the numeric code that Web Query displays.

2 Return to Web Query.

3 Click the Tools item in the menu bar and select FOC Message Lookup.

4 Enter the code in the FOC Error Code textbox.

5 Click the Lookup button.

6 A description of the error appears in the FOC Error Text field.



Appendix A: Aggregation Functions for Numeric Fields

Report-Level Aggregations Functions The measure node in the Query pane, labeled Sum by default, organizes numeric fields whose values are aggregated in some way. Although the default calculation is to sum each field’s values, users can right-click the node and choose from the aggregation functions describes in the following sections.

Sum Consolidates the records by summing them and displaying a grand total row at the bottom of the report. In the following report, the measure node applies the Sum function to the Curr Bal field.

Print Creates a detailed report with one row for each selected record. In other words, while the Sum function shows one row for a customer w/ two records, the Print function shows each record in its own row. In the following report, the measure node applies the Print function to the Curr Bal field. Notice that the final two rows apply to the same customer, but the individual records display on separate rows.

Count Displays the total number of records in summed groupings. In the following report, the measure node applies the Count function to the Curr Bal field. Notice that the final row groups a customer’s two records.

List Adds a sequential number to each record in the group which shows how many records each group contains. In the following report, the measure node applies the List function to the Curr Bal field.



Behavior When a Row Cannot Be Summed Note that if users add a field and two or more grouped records have unique values in that field, the report must display a row for each record because it cannot reconcile the unique values in a single cell. For example, when users add the Account Number field to the report, the report can no longer combine the final two rows because they have unique account numbers.

Field-Level Aggregations Functions Instead of applying the same function, such as Sum, to every field, users can apply a function to one or more fields that is different from the primary function. The following example, where the Account Number field is prefixed with CNT, shows that this field will display a count of the accounts the customer holds that meet the report’s criteria, while the Current Balance field displays a sum of all balances.

The resulting report appears as follows.



Notice the final row shows that this customer holds two accounts. Because the Account Number field has the Count function applied, the report combines the current balance of both accounts in a single row.

The following field-specific functions are available:

• Sum

• Average

• Count

• Count Distinct

• Percent of Count

• Distinct Values

• First Value

• Last Value

• Maximum

• Minimum

• Total

• Percent

• Row Percent

• Median

• Average Square

Note: If users change the Query pane node from Sum to Print, Count, or List, it overrides all assigned aggregation type values at the field level.



Appendix B: Overview of Temporary Fields A temporary field takes up no storage space in the data source and is created only when needed.

Types of Temporary Fields There are two types of temporary fields in Web Query, each of which has a distinct purpose:

• Define field—Web Query evaluates the value of a define field as it retrieves records from the SQL view. These values are calculated for every row in the query. In other words, if the report contains 5 rows, Web Query calculates 5 distinct values. The result of the expression is treated as though it were in a real field stored in the view.

• Compute field—Web Query evaluates compute fields only after all the data that meets the selection criteria is retrieved, sorted, and summed. In other words, the calculation is performed using the aggregated values of fields.

Example: Define Versus Compute Fields Consider the following example where Assessed Charge and Actual Charge are fields in the report and users want to compute the percentage difference between the charge originally assessed and the actual charge. Assume Change Percent is a define field with the following expression:

Change Percent = (Assessed Charge – Actual Charge / Assessed Charge) * 100

NSF Record Assessed Charge Actual Charge Change Percent

A $10.00 $5.00 50%

B $10.00 $7.50 25%

In this example, where the report displays each NSF record on a separate line, the Change Percent define field produces the correct value for each row.

Now assume that users want to aggregate the rows to present only their sums. The following table shows the resulting report.

NSF Records Assessed Charge Actual Charge Change Percent

A + B $20.00 $12.50 75%

Notice that the Change Percent define field continues to be calculated at the row level even though the rows are aggregated, so its value is the sum of the two rows’ calculations (50% + 25%). The result of 75% is incorrect because the calculation was not performed on the two records after they were aggregated.

If users instead create the Change Percent field as a compute field, Web Query computes the same expression a single time after the Assessed Charge and Actual Charge fields have been summed. The following table shows the correct result derived by the compute field.

NSF Records Assessed Charge Actual Charge Change Percent

A, B $20.00 $12.50 37.5%



Tip: If a calculation only needs to be performed a single time, using compute fields also requires less system resources.

Note: If users want to sort or filter based on a calculated field, then a Define field must be created. Compute fields can only be Sum/Measure fields.