Data Quality Monitor User's Guide - Information Builders1 Introduction Provides an overview and page structure information for Data Quality Monitor (DQM). 2 Functionality Overview

Develop

er Studio A

pp

lication D

evelopm

ent •G

etting

StartedVersion 7 Release 6

Developer Studio ApplicationDevelopmentGetting StartedVersion 7 Release 6

Information Builders, Inc.Two Penn PlazaNew York, NY 10121-2898

Printed on recycled paper in the U.S.A.

Data Quality Monitor User's GuideVersion 3.2 and Higher

DN3502270.0318

Active Technologies, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWaySoftware, Parlay, PC/FOCUS, RStat, Table Talk, Web390, WebFOCUS, WebFOCUS Active Technologies, and WebFOCUSMagnify are registered trademarks, and DataMigrator and Hyperstage are trademarks of Information Builders, Inc.

Adobe, the Adobe logo, Acrobat, Adobe Reader, Flash, Adobe Flash Builder, Flex, and PostScript are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Due to the nature of this material, this document refers to numerous hardware and software products by theirtrademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by theirrespective companies. It is not this publisher's intent to use any of these names generically. The reader is thereforecautioned to investigate all claimed trademark rights before using any of these names other than to refer to the productdescribed.

Copyright © 2018, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual, orparts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Help Us to Serve You Better . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

User Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

iWay Software Training and Professional Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Understanding the Layout and Page Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Data Quality Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Business Impact Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2. Functionality Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Accessing Data Quality Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Working With Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Working With Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Working With Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Viewing Trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Using Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Global Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Local Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Using Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

'Show By' Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Using Breakouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Saving State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Loader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Breadcrumbs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3. Configuring Data Quality Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Data Quality Monitor User's Guide 3

WSO2 Identity Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Administration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configuring Fields for Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Configuring Fields for Breakouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Configuring the Domain Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configuring the Sub-domain Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring Fields for 'Show By' Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuring Fields for the Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuring Fields for Trends. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Creating and Modifying Dimensions and Measures in Omni Designer . . . . . . . . . . . . . . . . . . . . . . . 67

Using the Dqconfig.xml File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Contents

4 Information Builders

Preface

This documentation provides information on how to use Data Quality Monitor (DQM).

How This Manual Is Organized

This manual includes the following chapters:

Chapter/Appendix Contents

1 Introduction Provides an overview and page structure informationfor Data Quality Monitor (DQM).

2 Functionality Overview Provides an overview of the various functions thatare used in Data Quality Monitor.

3 Configuring Data QualityMonitor

Describes how to configure Data Quality Monitor(DQM) using the WSO2 Identity Server, theAdministration menu, and the configuration files.

Documentation Conventions

The following table lists and describes the documentation conventions that are used in thismanual.

Convention Description

THIS TYPEFACE

or

this typeface

Denotes syntax that you must type exactly as shown.

this typeface Represents a placeholder (or variable), a cross-reference, or animportant term. It may also indicate a button, menu item, or dialogbox option that you can click or select.

underscore Indicates a default setting.

Key + Key Indicates keys that you must press simultaneously.

{} Indicates two or three choices. Type one of them, not the braces.

| Separates mutually exclusive choices in syntax. Type one of them,not the symbol.


Convention Description

... Indicates that you can enter a parameter multiple times. Type onlythe parameter, not the ellipsis (...).

.

.

.

Indicates that there are (or could be) intervening or additionalcommands.

Related Publications

Visit our Technical Documentation Library at http://documentation.informationbuilders.com. Youcan also contact the Publications Order Department at (800) 969-4636.

Customer Support

Do you have questions about this product?

Join the Focal Point community. Focal Point is our online developer center and more than amessage board. It is an interactive network of more than 3,000 developers from almost everyprofession and industry, collaborating on solutions and sharing every tips and techniques.Access Focal Point at http://forums.informationbuilders.com/eve/forums.

You can also access support services electronically, 24 hours a day, with InfoResponseOnline. InfoResponse Online is accessible through our website, http://www.informationbuilders.com. It connects you to the tracking system and known-problemdatabase at the Information Builders support center. Registered users can open, update, andview the status of cases in the tracking system and read descriptions of reported softwareissues. New users can register immediately for this service. The technical support section of www.informationbuilders.com also provides usage techniques, diagnostic tips, and answers tofrequently asked questions.

Call Information Builders Customer Support Services (CSS) at (800) 736-6130 or (212)736-6130. Customer Support Consultants are available Monday through Friday between 8:00A.M. and 8:00 P.M. EST to address all your questions. Information Builders consultants canalso give you general guidance regarding product capabilities. Be prepared to provide your six-digit site code (xxxx.xx) when you call.

To learn about the full range of available support services, ask your Information Buildersrepresentative about InfoResponse Online, or call (800) 969-INFO.

Related Publications


http://www.iwaysoftware.com

http://techsupport.iwaysoftware.com/



Help Us to Serve You Better

To help our consultants answer your questions effectively, be prepared to providespecifications and sample files and to answer questions about errors and problems.

The following table lists the environment information that our consultants require.

Platform

Operating System

OS Version

JVM Vendor

JVM Version

The following table lists additional questions to help us serve you better.

Request/Question Error/Problem Details or Information

Did the problem arise througha service or event?

Provide usage scenarios orsummarize the application thatproduces the problem.

When did the problem start?

Can you reproduce thisproblem consistently?

Describe the problem.

Describe the steps toreproduce the problem.

Specify the error messages.

Preface


Request/Question Error/Problem Details or Information

Any change in the applicationenvironment: softwareconfiguration, EIS/databaseconfiguration, application, andso forth?

Under what circumstance doesthe problem not occur?

The following is a list of error and problem files that might be applicable.

Input documents (XML instance, XML schema, non-XML documents)

Transformation files

Error screen shots

Error output files

Trace files

Custom functions and agents in use

Diagnostic Zip

Transaction log

User Feedback

In an effort to produce effective documentation, the Technical Content Management staffwelcomes your opinions regarding this document. Please use the Reader Comments form atthe end of this document to communicate your feedback to us or to suggest changes that willsupport improvements to our documentation. You can also contact us through our website, http://documentation.informationbuilders.com/connections.asp.

Thank you, in advance, for your comments.

iWay Software Training and Professional Services

Interested in training? Our Education Department offers a wide variety of training courses foriWay Software and other Information Builders products.

User Feedback


http://www.iwaysoftware.com

For information on course descriptions, locations, and dates, or to register for classes, visitour website, http://education.informationbuilders.com, or call (800) 969-INFO to speak to anEducation Representative.

Interested in technical assistance for your implementation? Our Professional Servicesdepartment provides expert design, systems architecture, implementation, and projectmanagement services for all your business integration projects. For information, visit ourwebsite, http://www.informationbuilders.com/consulting.

Preface


http://education.informationbuilders.com

http://www.informationbuilders.com/consulting

iWay Software Training and Professional Services


Chapter1Introduction

Data Quality Monitor (DQM) is a component of Omni-Gen that allows you to monitor thedata quality of records in a system and its impact on business. This information can beused for further analysis and provides a basis for business decisions.

In order to demonstrate clear business and financial impact of poor data quality, thefollowing features have been implemented:

Ability to easily create business rules for measuring impact.

Interface for monetizing data quality.

Trending capabilities to measure data quality over time.

Continuous monitoring and reporting of data quality.

Customized views and insights of data quality.

In this chapter:

Understanding the Layout and Page Structure


This section describes the layout and page structure found in DQM.

General

The DQM page contains the following general page structure, as shown in the correspondingimage.

1. Top menu item. Indicates which page in the Omni-Gen application you are viewing.

2. Domain drop-down list. Provides the list of domains which you have access to and canwork with.

3. Global Filters. Identifies filters that have been applied for Data Quality and BusinessImpact tabs.

4. Data Quality (DQ) and Business Impact (BI) tabs.

5. Subtabs. Identify dimensions on the Data Quality tab and Measures on the BusinessImpact tab.

6. Local Filters. Filters that are applied only to data of a selected dimension (on the DataQuality tab) or Measure (on the Business Impact tab).


7. Show By. Control for changing the grid view by domain.

8. Grid. Shows data from the selected domain.

9. Breakout by. Control for dividing data by an attribute included in the selected dimension'srules.

Both BI and DQ tabs have the same structure, except for the sub-tabs that they contain.

Data Quality Tab

Tabs on the DQ tab are called dimensions. Every dimension contains the following, whichcorrespond to the image below:

1. Chart

2. Menu button



3. Trend

The Menu button only consists of the Show function, that allows toggling between percentagesand actual values.

1. Introduction


Business Impact Tab

Sub-tabs on the BI tab are called measures. Every measure contains the following items, whichcorrespond to the image below:

1. Value

2. Trend



Chapter2Functionality Overview

This chapter provides an overview of the various functions that are used in Data QualityMonitor.

In this chapter:

Accessing Data Quality Monitor

Working With Domains

Working With Dimensions

Working With Measures

Using Charts

Viewing Trends

Using Filters

Using Grids

'Show By' Functionality

Using Breakouts

General

Accessing Data Quality Monitor

You must first configure access to DQM. This can be done through the WSO2Server.

For more information, see WSO2 Identity Server on page 41.



All data displayed in DQM depends upon the domain selected. For example, if thePatientMasters domain is selected, then tabs, dimensions, measures, and data pertaining to itis displayed, as shown in the following image.

Note: You must add the domains for dimensions, tabs, and measures in order to see data inDQM.



Working With Dimensions

Dimensions are sub-tabs for the DQ tab. When dimensions are used, you can see whether yourdata is qualitative enough looking at it from different angles. For example, records in thesystem might be valid, but not conformable to some specific rules or standards, as shown inthe following image.

Dimensions are being calculated by rules added in the dqconfig.xml file. For example, there isa rule that if a record has the 'First name' defined, then it is considered to be valid.

For more information on adding or editing dimensions, see Creating and Modifying Dimensionsand Measures in Omni Designer on page 67.

2. Functionality Overview



Measures are sub-tabs for the BI tab, and allow you to see how the quality of the recordinfluence business. For example, if you have 77% 'bad' conformity records and 0% 'bad'validity records, then your production capacity is 18 shipped items and revenue is 60 euros, asshown in the following image.

Measures are calculated by coefficients and rules added in the dqconfig.xml file.

For more information on how to add or edit measures or coefficients, see Creating andModifying Dimensions and Measures in Omni Designer on page 67.

Using Charts

Charts provide a visual representation of data quality records that are currently in the system.They are available in the DQ tab only, within the dimension and local tabs (after breakout), asshown in the following image.



The rules for dimensions are defined in Omni Designer. Those rules also help create thedqconfig.xml file, and are used to calculate whether a record is 'good' (displayed in green) or'bad' (displayed in red). For example, a rule can state that the social security number fieldshould contain 10 characters. If all records contain a social security number with 10 digits,then the following dimension percentages would be displayed:

Dimension charts have a menu button available for them. At the moment, the only functionalitythat is implemented there is the Show option, as shown in the following image.



The Show option is a drop-down list, where a list of available options will display when youhover the arrow over it, as shown in the following image.

The Show option defines which values are displayed in the chart, either actual values orpercentage. Once it is changed, it applies the same values to the local charts after breakout.For more information on Breakouts, see Using Breakouts on page 34.

Viewing Trends

A trend is one of the most useful indicators in DQM. They provide a visual representation ofdata compared in time. It allows you to determine whether data has become better or worse(DQ tab) and how it influences business (BI tab).

Viewing Trends


In the DQ tab, trends are displayed in the following ways:

If data has improved. A green arrow pointing up is displayed.

If data has deteriorated. A red arrow pointing down is displayed.

If data remained the same. A grey arrow pointing right is displayed.

If there is no data to compare with. A grey no trend icon is displayed.

In the BI tab, trends are displayed slightly different:

If data has improved. A green arrow pointing down is displayed.

If data has deteriorated. A red arrow pointing up is displayed.

If data remained the same. A grey arrow pointing right is displayed.



If there is no data to compare with. A grey no trend icon is displayed.

The difference between trends in the DQ and BI tabs is that the DQ tab trends show whetherdata quality has improved or diminished, while the BI tab trends show whether business lossincreased or decreased. That is why it is good if the arrow is pointing up in the DQ tab, but badif it is pointing up on BI tab (for example, quality improved in the DQ tab and business lossincreased on the BI tab).

Trends are calculated based on the defined number of days which are set in the Administrationand can be changed if needed. For more information on configuring trends, see AdministrationMenu on page 61.

A trend is a comparison of data between the current date and a date that was defined anumber of days ago. For example, if 30 days is set in the Administration, then the trend will bethe difference between data for the current date and data for date that occurred 30 days ago.

Viewing Trends


When you hover the cursor on a trend in the BI tab, the loss or win value will be displayed inunits. For example, if the loss is increased by 67 units, then a hint will appear, as shown inthe following image.

In the DQ tab, hints are not necessary because they just show whether data is better or worsewithout a quantitative description.

Trends are also available for tabs after a breakout is performed. The following image showstrends for local tabs (after breakout) in the DQ tab.



Trends can also display the field selected in the breakout. The following image shows trendsfor a local tab (after breakout) in the BI tab.

Using Filters

This section describes the global and local filters that are used in DQM.

In general, you can use filters if you wish to narrow down data displayed on the page. To add afilter, click the add (+) icon in the Filters section, as shown in the following image.

The fields for filtering are displayed, as shown in the following image.

Using Filters


Each filter consists of the following fields:

Condition. Contains the following drop-down list of conditions:

Must. The list of filtering results fully coincides with the filtering criteria.

Must Not. The list of filtering results should only include records that do not include theselected filtering criteria.

Should. Allows you to search for different values within the same field. For example, iffirst names John and Adam need to be found, then two filters with the Should conditionmust be applied.

Field. Select an attribute that you wish to filter from the list of available attributes. They areconfigured through the Administration menu. For more information, see Configuring Fieldsfor Filters on page 62.

Operator. A list of operators that can be used for filtering. They depend on the type of fieldthat you used as a filtering criteria:

For string values, the Equal ( = ) operator is available.

For numeric value, the Equal ( = ), Greater than ( > ), and Less than ( < ) operators areavailable.

Fore date value, the Equal ( = ), Greater than ( > ), and Less than ( < ) operators areavailable.

For Boolean and SourceCode values, the Equal ( = ) operator is available.

The Equal ( = ) operator searches for values that fully coincide with the criteria entered.

The Greater than ( > ) or Less than ( < ) operators search for values that are greater/lessthan the criteria entered.

Value. Field for entering the actual value of the field. It is enabled after the Field attribute isselected.



To simplify filtering, the autocomplete functionality has been implemented. To use thefunctionality, select the field and enter a value. While you are typing, a list of values fall underthe entered criteria. All values that have that character in them are displayed. For example, ifyou selected City in the Field drop-down list, and then started typing n in the Value field, then alist of cities that contains n will be displayed, as shown in the following image.

Note: Autocomplete functionality is available only for String values.

The list of values that is displayed as autocomplete depends upon filters already applied. Forexample, if filtering by first name Deborah was applied, and you wanted to apply another filterby city that contained the letter n, then only those cities that have citizens with the first nameDeborah will be displayed in the autocomplete list, as shown in the following image.

Using Filters


Note: Filtering by values with asterisks or partial values is not supported.

Once a filter is applied, the whole Filters section can be collapsed (1), or the filter can beedited (2), or deleted (3), as shown in the following image.

The following image shows a collapsed Filters section.



Global Filters

Global filters are filters that are located just under the Domain drop-down list. They are calledGlobal because they are applied both to DQ and BI tabs, and to their sub-tabs, as shown in thefollowing image.

Similar to Dimensions, Global filters work with all of the data in the dataset. After globalfiltering, the dimension percentage is recalculated for the valid records.

Note: If the criterion of a global filter is not met in any data records, the following message willbe displayed, and the dimension percentage will not change:

No data for current domain

Using Filters


Local Filters

Local filters are filters that are located under each sub-tab of the DQ and BI tabs. They can beadded on different levels after breakouts. They can also influence data for the selecteddimension or measure sub-tab.

Similar to grid and breakout functions, the local filters work with the data on the page. Addinga local filter will not have an impact on the calculation of dimensions.

Using Grids

The most important component of DQM is the grid. It contains all of the data that is in thesystem and by which dimensions and/or measures are being calculated.



The following image shows the structure of the grid, and is followed by a list and descriptionthat corresponds to a specific in the grid.

1. Expand/Collapse control. Allows you to hide or show the grid.

2. Paging component header. Allows you to define how many records per page to bedisplayed in the grid.

3. Filtering button. Allows you to filter date by column in the grid.

4. Headers. Names of the displayed columns.

5. Rows. Contains data.

6. Paging component footer. Allows you to navigate between pages.

Columns of the grid can be configured through the Administration menu. For more information,see Configuring Fields for the Grid on page 66.

The grid provides you with the following functionalities:

Sort by data column. When you click a column header, data will be sorted in ascendingorder. When you click it a second time, data will be sorted in descending order. Clicking athird time discards sorting.

Using Grids


When data is sorted by column, the sorting icon appears, as shown in the following image.

Note: If the data of the column consists of more than one word, then data will be sorted bythe first letters of any of the words available. For example, in the image above, Eric Adamsis listed before Alan Hudson because "Adams" comes alphabetically before "Alan".

Filter data by column. In order to sort data in the grid by a selected column, click thefiltering button from the necessary column header.

The field for entering the filtering criteria is displayed. Data is filtered dynamically as youenter data, as shown in the following image.



Note: Same as for sorting, if data of the column consists of more than one word, then datais filtered by the first letters of any of the words available. For example, from the imageabove, both 'David Peterson' and 'Frank Davis' contain the letter 'd', so they both satisfythe filtering criteria.

When filtering is applied, the filter icon appears, as shown in the following image.

Filtering by multiple columns are supported. The filtering icon will appear on each columnusing a filter.


Data displayed in the grid can be changed completely by using the Show By functionality. It wasimplemented in order to view detailed information of records of a specified domain. By default,records of selected domains are displayed, but they can also be changed to the records ofsome specific sub-domain (subject) if needed.



For example, if you are working with the Patient Master domain but want to see information ofthe Person Address Master sub-domain (subject), you will need to select the appropriate itemfrom the Show By drop-down list, as shown in the following image.

All items that are displayed in the drop-down list are sub-domains of the selected domain. Thelist can be modified through the Administration menu.

For more information, see Configuring Fields for 'Show By' Functionality on page 65.

Once a sub-domain is selected, the grid is redrawn and the selected sub-domain will displaythe new data, as shown in the following image.

All records of the selected sub-domain (subject) that exists for the currently selected domainare displayed in the grid.



The columns that appear can be configured the same way as the domain tables. For moreinformation, see Configuring Fields for the Grid on page 66.

Using Breakouts

You can use the Breakout functionality to see more detailed information about the dimensionof a record or measure characteristic.

Note: Breakouts can be used against any field/attribute, not just those included in the rules ofthe selected Dimension.

When an attribute is selected for breakout on a specific Dimension, percentages will becalculated for the records that are in a True state for the related rules of the Dimension.

Percentages are calculated for each breakout group in the following ways:

Without a filter.a ÷ (b × 100)

where:

a

Is the number of records in the group in a true state for the specified Dimension.

b

Is the number of all records in the group for the specified Dimension.

With a filter. c ÷ (d × 100)

where:

c

Is the number of filtered records in the group in a true state for the specifiedDimension.

d

Is the number of all filtered records in the group for the specified Dimension.

Breakouts divide records by a selected criteria and displays it as separate (local) tabs withcharts (DQ tab) and trends displayed for each of them, as shown in the following image.

This allows you to analyze the quality or impact of separate records, and helps you makedecisions.

Using Breakouts


The Breakout by check box is displayed under the grid because it divides data from the grid,but it does not affect the grid itself, as shown in the following image.

In order to apply a Breakout, you must select the necessary breakout criteria from the drop-down list and select the Breakout by check box, as shown in the following image.



Fields that are displayed in the drop-down list are those that are configured in theAdministration menu. For more information about how to configure fields, see ConfiguringFields for Breakouts on page 62.

If the selected domain has sub-domains added in the Administration menu, then the last itemin the drop-down list will be Subject. For more information about how to configure sub-domainfields, see Configuring Fields for Breakouts on page 62.

Each tab represents a separate sub-domain when a breakout by subject is selected, as shownin the following image.

Each sub-domain (subject) tab contains data that is available for that domain (for example,Person Address Masters table is the sub-domain of both Patient Masters and Provider Mastersdomains, but different information will be displayed in the grid for each of them).

The following image shows fields from the Person Address Masters table displayed by default.All fields in the grid are configurable. For more information on configuring grids, see ConfiguringFields for the Grid on page 66.

Using Breakouts


There are 8 tabs displayed on one page. If there are more than 8 tabs available, then paging isdisplayed. You can navigate among the pages by using the Next and Previous buttons, asshown in the following image.

Important: Tabs work using a lazy-loading mechanism. If you add a filter, change the Show by,add a breakout, or other criteria on a specific tab, and then you navigate to the next page oftabs, all changes on the previous tab will be lost. When you navigate back to the original tab,the default options will be selected, discarding all changed made on that specific tab.

After a breakout is applied, all the functionality will be dependent and configured for thebreakout. For example, if you applied a breakout by Subject (for example, Person AddressMasters), then the filters (Show by, Breakout by, and Grid data) will be available for theselected subject, as shown in the following image.

Breakout fields, Show by fields, Grid columns, and Filter fields should be configured forsubjects separately. For more information, see Configuring Fields for Filters on page 62.



General

This section describes the general functionality of Data Quality Monitor (DQM).

Saving State

The state of the DQM page is saved until the session times out or a user logs out. Allbreakouts, filters, tabs, and show by criteria selected on both DQ and BI tabs are saved. Thismeans you will not lose criteria when you return to the DQM page from any other page in theapplication (for example, 360 Viewer). This is common for all components of the application.

Loader

Whenever a request is being sent, the loader will be displayed on the page, shading out thecontent, as shown in the following image.

General


Breadcrumbs

Whenever a filter or breakout is added, a breadcrumb trail is added as well. Breadcrumb trailsprovide a better visual representation of the level the user is at the moment, as shown in thefollowing image.

Hierarchy

DQM page changes affect all criteria selected below the change. So if you have a breakoutadded and a show by displayed for one of the tabs and then you add global filter (or local filterabove breakout), both breakout and show by will be discarded.

This logic is valid for all criteria including filters, breakouts, and show by. Everything that wasadded below a new criterion will be discarded.



General


Chapter3Configuring Data Quality Monitor

This chapter describes how to configure Data Quality Monitor (DQM) using the WSO2Identity Server, the Administration menu, and the configuration files.

In this chapter:

WSO2 Identity Server

Administration Menu

Creating and Modifying Dimensions and Measures in Omni Designer


This section describes how to configure Data Quality Monitor (DQM) through the WSO2 IdentityServer.

Procedure: How to Display the Data Quality Monitor Menu Item

To display Data Quality Monitor as a menu item in the user interface:

1. Add the appropriate syntax to the component-access-menuitem-policy file, as shown in thefollowing image.

The section that appears in the image above defines which user roles will see the DQMtab in the application.

2. Enable the policy (if needed) and then publish it to PDP.


The Data Quality Menu item appears after updating the policy and publishing, then loggingon again in the application, as shown in the following image.

The following syntax is an example of the component-access-menuitem-policy.

<Policy xmlns="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17" PolicyId="component-access-menuitem-policy" RuleCombiningAlgId="urn:oasis:names:tc:xacml:1.0:rule-combining-algorithm:first-applicable" Version="1.0"> <Description>Policy that specifies what page components(functionalities)are available for passed attributes (roles, etc.). Order is important first applicable result will be returned.</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">authorize-component</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:action:action-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:action" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Rule Effect="Permit" RuleId="menuitem-360viewer-component-access-rule"> <Description>Handles the access to 360viewer menu item</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">menuitem_360viewer</AttributeValue>



<AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">System_Administrator</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">User</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Condition> </Rule> <Rule Effect="Permit" RuleId="menuitem-remediation-component-access-rule"> <Description>Handles the access to Remediation menu item</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">menuitem_remediation</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target>

3. Configuring Data Quality Monitor


<Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Condition> </Rule> <Rule Effect="Permit" RuleId="menuitem-datadictionary-component-access-rule"> <Description>Handles the access to Data Dictionary menu item</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">menuitem_datadictionary</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">User</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Condition> </Rule>



<Rule Effect="Permit" RuleId="menuitem-administration-component-access-rule"> <Description>Handles the access to Administration menu item</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">menuitem_administration</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">System_Administrator</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Condition> </Rule> <Rule Effect="Permit" RuleId="menuitem-dqm-component-access-rule"> <Description>Handles the access to Data Quality Monitor menu item</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">menuitem_dqm</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target>



<Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">User</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Condition> </Rule> <Rule Effect="Deny" RuleId="menuitem-denyother-component-access-rule"> <Description>Denies menu items for other roles</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-regexp-match"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">menuitem_*</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> </Rule> </Policy>

Procedure: How to Configure the Domains Which DQM Will Be Available In

DQM works only with those domains that you have access to (which are defined by the roles ofthe user). To check the available domains or add new ones:

1. Click Configure and then select Users and Roles.



2. Find the user and select the assigned roles, as shown in the following image.



Roles that have the domain prefix will be displayed in the domain drop-down list in DQM,as shown in the following image.



Procedure: How to Configure Access to DQ and BI Tabs

The DQ and BI tabs are independent of each other. Access can be defined separately in thecomponent-access-dqm-tabs-policy.xml file, as shown in the following image.

The policy allows you to define which roles can work with a specific tab and which domainsthose tabs are available.

1. After accessing the policy, enable it if needed.

2. Publish the policy to PDP.



The configured tabs appear after you log on back to the application, as shown in thefollowing image.

The following syntax shows an example of the component-access-dqm-tabs-policy.

<Policy xmlns="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17" PolicyId="component-access-dqm-tabs-policy" RuleCombiningAlgId="urn:oasis:names:tc:xacml:1.0:rule-combining-algorithm:first-applicable" Version="1.0"> <Description>Policy that specifies what page components(functionalities)are available for passed attributes (roles, etc.). Order is important first applicable result will be returned.</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">authorize-component</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:action:action-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:action" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Rule Effect="Permit" RuleId="dq-tab-component-access-rule"> <Description>Handles the access for Data Quality tab</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">dataquality</AttributeValue>



<AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">System_Administrator</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">User</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">PatientMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">FacilityMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">ProviderMaster</AttributeValue> </Apply> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:environment:environment-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:environment" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Apply> </Condition> </Rule> <Rule Effect="Permit" RuleId="bi-tab-component-access-rule"> <Description>Handles the access for Business Impact tab</Description> <Target> <AnyOf> <AllOf>



<Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">businessimpact</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">PatientMaster</AttributeValue> </Apply> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:environment:environment-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:environment" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Apply> </Condition> </Rule></Policy>



Procedure: How to Configure Dimensions

Access to dimensions can be configured in the component-access-dimensions-policy file. Eachdimension has its own section, as shown in the following image.

The policy allows you to define which roles can work with specific dimensions and whichdomains those dimensions are available in.

1. After accessing the dimensions, enable the policy (if needed).

2. Publish it to the PDP.



The configured dimensions appear in the application after logging on again, as shown inthe following image.

The following is an example of the component-access-dimensions-policy.

<Policy xmlns="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17" PolicyId="component-access-dimensions-policy" RuleCombiningAlgId="urn:oasis:names:tc:xacml:1.0:rule-combining-algorithm:first-applicable" Version="1.0"> <Description>Policy that specifies if dimensions are available for provided roles. Order is important first applicable result will be returned.</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">authorize-component</AttributeValue>



<AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:action:action-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:action" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Rule Effect="Permit" RuleId="dimensions-validity-component-access-rule"> <Description>Handles the access for validity dimension</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Validity</AttributeValue><AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">System_Administrator</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">User</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag">



<AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">ProviderMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">FacilityMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">PatientMaster</AttributeValue> </Apply> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:environment:environment-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:environment" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Apply> </Condition> </Rule> <Rule Effect="Permit" RuleId="dimensions-conformity-component-access-rule"> <Description>Handles the access for conformity dimension</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Conformity</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target><Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> </Apply> <AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply>



<Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">ProviderMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">PatientMaster</AttributeValue> </Apply> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:environment:environment-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:environment" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Apply> </Condition> </Rule> </Policy>

Procedure: How to Configure Measures

Access to measures can be configured in the component-access-measures-policy file. Eachmeasure has its own section, as shown in the following image.



The policy allows you to define which roles can work with specific measures and whichdomains those dimensions are available in.

1. After accessing the measures, enable the policy (if needed).

2. Publish it to the PDP.

The configured measures appear in the application after logging on again, as shown in thefollowing image.

The following is an example of the component-access-measures-policy.



<Policy xmlns="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17" PolicyId="component-access-measures-policy" RuleCombiningAlgId="urn:oasis:names:tc:xacml:1.0:rule-combining-algorithm:first-applicable" Version="1.0"> <Description>Policy that specifies if measures are available for provided roles. Order is important first applicable result will be returned.</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">authorize-component</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:action:action-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:action" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Rule Effect="Permit" RuleId="dimensions-conformity-component-access-rule"> <Description>Handles the access for Production Capacity measure</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">ProductionCapacity</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> </Apply>



<AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">PatientMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">FacilityMaster</AttributeValue> </Apply> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:environment:environment-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:environment" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Apply> </Condition> </Rule> <Rule Effect="Permit" RuleId="dimensions-validity-component-access-rule"> <Description>Handles the access for Revenue measure</Description> <Target> <AnyOf> <AllOf> <Match MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Revenue</AttributeValue> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="false"></AttributeDesignator> </Match> </AllOf> </AnyOf> </Target> <Condition> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">System_Administrator</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Supervisor</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">Data_Steward</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">User</AttributeValue> </Apply>



<AttributeDesignator AttributeId="http://wso2.org/claims/role" Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of"> <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-bag"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">PatientMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">ProviderMaster</AttributeValue> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">FacilityMaster</AttributeValue> </Apply> <AttributeDesignator AttributeId="urn:oasis:names:tc:xacml:1.0:environment:environment-id" Category="urn:oasis:names:tc:xacml:3.0:attribute-category:environment" DataType="http://www.w3.org/2001/XMLSchema#string" MustBePresent="true"></AttributeDesignator> </Apply> </Apply> </Condition> </Rule> </Policy>

Administration Menu

This section describes how to configure iWay Data Quality Monitor (DQM) through theAdministration menu.



Configuring Fields for Filters

In order to define fields that need to be displayed in the list of Filtering criteria, you must editthe appropriate domain or sub-domain table. For example, if you are working with the PatientMasters domain, you will need to edit the Patient Masters table, in the DQM Filters view. Fieldsin the Included column are shown in the following image.

Configuring Fields for Breakouts

This section describes how to configure the Domain and Sub-domain fields for Breakouts.

Administration Menu


Configuring the Domain Fields

In order to define the fields that are displayed in the list of Breakouts, you must edit theappropriate domain table. For example, if you are working with the Patient Masters domain,you will need to edit the Patient Masters table, in the DQM Breakouts view. Fields in theIncluded column are shown in the following image.



Configuring the Sub-domain Fields

In order to define the fields that are displayed as tabs after the breakout by subject, you mustedit the appropriate domain table. For example, if you are working with the Patient Mastersdomain, you will need to edit the Patient Masters table, in the DQM Breakouts view. Fields inthe Included column for the Links section are displayed in the following image.

Administration Menu


Configuring Fields for 'Show By' Functionality

In order to define fields that are displayed in the list of Show By criteria, you must edit theappropriate domain or sub-domain table. For example, if you are working with the PatientMasters domain, you will need to edit the Patient Masters table, in the DQM Breakouts view.Fields in the Included column for the Links section are shown in the following image.



Configuring Fields for the Grid

In order to define fields that are displayed in the grid, you must edit the appropriate domain orsub-domain table. For example, if you are working with the Patient Masters domain, you willneed to edit the Patient Masters table, in the DQM Grid view. Fields in the Included column areshown in the following image.

Administration Menu


Configuring Fields for Trends

The number of days that are used for calculating trends is defined in the DQMTrendDayssetting (located in the list of Settings in the Settings tab of the Administration menu). You canchange the value as needed, as shown in the following image.


This section describes how dimensions and measures are created and maintained in OmniDesigner. For more information, see the Omni Designer User Guide.

Using the Dqconfig.xml File

The dqconfig.xml file is created when the bundle is deployed to Omni-Gen. It reflects thestructure of dimensions, measures, and rules defined in Omni Designer.

The original location of the file can be found in:

…/omnigen/OmniServer/bundle/artifacts/server/index/dqconfig.xml



Important: Do not edit this file. It is used for familiarization purposes only.

The following syntax shows a sample dqconfig.xml file.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><dqconfig> <dimensions> <dimension> <properties> <name>Validity</name> <default>false</default> </properties> <model name="Customer"> <subject name="Customer"> <subject name="Address"> <subject name="level3"> <subject name="level4"> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject>



<subject name="Phone"> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic> <and> <and rule="DOB_Not_Empty"/> <and rule="Name_Not_Empty"/> </and> </logic> <business> <impact measure="ProductionCapacity">1.0</impact> <impact measure="Revenue">11.0</impact> </business> <rules> <rule id="DOB_Not_Empty">false;</rule> <rule id="Name_Not_Empty">false;</rule> </rules> </source> <instance> <logic> <and rule="first_name"/> </logic> <business> <impact measure="ProductionCapacity">2.0</impact> </business> <rules> <rule id="first_name">($.get('firstName') == '11')? true : false;</rule> <rule id="ssn">($.get('ssn') != '11')? true : false;</rule> <rule id="email">($.get('email') == 'NULL')? true : ($.get('email') == '')? true : false;</rule> </rules> </instance> </subject> </model> <model name="Person"> <subject name="Person"> <source> <logic/> <business/> <rules/> </source>



<instance> <logic> <and rule="qqq"/> </logic> <business> <impact measure="Revenue">1.0</impact> </business> <rules> <rule id="qqq">($.get('string') == 'NULL')? false : false;</rule> </rules> </instance> </subject> </model> </dimension> <dimension> <properties> <name>Conformity</name> <default>false</default> </properties> <model name="Customer"> <subject name="Customer"> <subject name="Address"> <subject name="level3"> <subject name="level4"> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source>



<instance> <logic/> <business/> <rules/> </instance> </subject> <subject name="Phone"> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source> <instance> <logic> <and rule="ssn"/> </logic> <business> <impact measure="Revenue">222.0</impact> </business> <rules> <rule id="first_name">($.get('firstName') == '11')? true : false;</rule> <rule id="ssn">($.get('ssn') != '11')? true : false;</rule> <rule id="email">($.get('email') == 'NULL')? true : ($.get('email') == '')? true : false;</rule> </rules> </instance> </subject> </model> <model name="Person"> <subject name="Person"> <source> <logic> <and rule="rule"/> </logic> <business> <impact measure="Revenue">2.0</impact> <impact measure="ProductionCapacity">3.0</impact> </business>



<rules> <rule id="rule">($.get('string') == 'NULL')? false : false;</rule> </rules> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> </model> </dimension> <dimension> <properties> <name>Completeness</name> <default>false</default> </properties> <model name="Customer"> <subject name="Customer"> <subject name="Address"> <subject name="level3"> <subject name="level4"> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source>



<instance> <logic/> <business/> <rules/> </instance> </subject> <subject name="Phone"> <source> <logic/> <business/> <rules/> </source> <instance> <logic/> <business/> <rules/> </instance> </subject> <source> <logic/> <business/> <rules/> </source> <instance> <logic> <and rule="email"/> </logic> <business> <impact measure="Revenue">2.0</impact> <impact measure="ProductionCapacity">2222.0</impact> </business> <rules> <rule id="first_name">($.get('firstName') == '11')? true : false;</rule> <rule id="ssn">($.get('ssn') != '11')? true : false;</rule> <rule id="email">($.get('email') == 'NULL')? true : ($.get('email') == '')? true : false;</rule> </rules> </instance> </subject> </model> <model name="Person"> <subject name="Person"> <source> <logic/> <business/> <rules/> </source>



<instance> <logic/> <business/> <rules/> </instance> </subject> </model> </dimension> </dimensions> <measures> <measure id="Revenue" units="UAH"/> <measure id="ProductionCapacity" units="something"/> </measures></dqconfig>

Procedure: How to Add and Edit Dimensions and Measures in Omni Designer

For each dimension, there is a rule that defines which records should be defined as good,which is defined for each domain and sub-domain available in the system.

Important: There might be situations when you do not see some or all of the dimensions. Thisis usually due to the fact that those dimensions simply have not been added to the WSO2component-access-dimensions-policy. You should check the policy, add any new dimensions asrequired, publish it, and log back in to the application.



Procedure: How to Add and Edit Measures

Measures and their units are defined in the measures section, as shown in the followingimage.

Measures are calculated based on defined coefficients for each domain and dimension.

Define the coefficients of the measures for each domain and dimension, as shown in thefollowing image.

The formula for calculating the measure value is:

If the measure is only used by one dimension: a × b

where:

a

Is the number of bad dimension records

b

Is the measure coefficient

If the measure is used by many dimensions:

(a × c) + (b × c) = d

where:

aIs the number of bad dimension 1 records.

bIs the number of bad dimension 2 records.



cIs the measure coefficient.

dIs the measure value.

The formula is the same for all dimensions.

Note: Measures are defined for each domain separately.

Important: There might be situations when you do not see some or all of the measures.This is usually due to the fact that those measures simply have not been added to theWSO2 component-access-measures-policy. You should check the policy, add any newmeasures as required, publish it, and log back in to the application.



FeedbackCustomer success is our top priority. Connect with us today!

Information Builders Technical Content Management team is comprised of many talentedindividuals who work together to design and deliver quality technical documentation products.Your feedback supports our ongoing efforts!

You can also preview new innovations to get an early look at new content products andservices. Your participation helps us create great experiences for every customer.

To send us feedback or make a connection, contact Sarah Buccellato, Technical Editor,Technical Content Management at [email protected].

To request permission to repurpose copyrighted material, please contact Frances Gambino,Vice President, Technical Content Management at [email protected].

Creating Reports With WebFOCUS Language

Version 7 Release 6

Information Builders

Two Penn Plaza

New York, NY 10121-2898

Printed on recycled paper in the U.S.A.

Data Quality Monitor User's GuideVersion 3.2 and Higher

Documents

Data Quality Monitor User's Guide - Information Builders1 Introduction Provides an overview and page structure information for Data Quality Monitor (DQM). 2 Functionality Overview