Understanding Sun Master Index Configuration Options (Repository)

Enterprise Data Manager Configuration

The Enterprise Data Manager (EDM) is the web-based user interface for the master index application that allows you to monitor and modify data in the index. This interface is highly configurable, and can be customized by modifying the Enterprise Data Manager file in the maser index project.

The following topics describe the EDM, the Enterprise Data Manager file structure, and how the EDM can be configured:

About the EDM

The EDM is a web-based interface that allows you to manage and monitor the data in your master index database. Using the EDM, you can search for records; add, update, deactivate, and reactivate records; review and resolve potentially duplicate records; compare records; and merge and unmerge records. You can also view a transaction history for each record and an audit log of access to the database. This interface is highly configurable, allowing you to customize certain processing properties as well as the appearance of certain windows.

The EDM facilitates the use of screen readers and other assistive technology by providing information through HTML tags. It also provides tooltips when the cursor is placed over links and images on the EDM pages.

EDM Configuration Components

You can configure several properties of the EDM to display the information you want in the way you want, to define the way searches can be processed, and to define the criteria that can be used for each search. Certain implementation options are also configured in the Enterprise Data Manager file, such as application server information, debug options, and security information.

The configurable properties of the user interface fall into these five categories:

Object and Field Properties

In the Enterprise Data Manager file, you can specify which objects appear on the EDM windows and the order in which they appear. You can also specify the fields displayed in each object and configure properties for each field. You can specify a field’s name, length, order of appearance on the EDM, required data type, whether text can be entered into a field or if it must be selected from a predefined value, whether a field or combination of fields must be unique to the parent object, and whether the value of the field is hidden under certain circumstances. You can also specify whether the format of a field is dependent on the value of a related field (for example, the format of a credit card number field could be dependent on the type of credit card specified).

Relationships

In the Enterprise Data Manager file, relationships define the hierarchy of the object types listed for the EDM. By specifying relationships, you define parent and child nodes. The parent and child nodes you specify in the relationships element must also be defined in the node elements of the file. You can specify one parent object; the remaining objects must be child objects to the parent you define. This section is dependent on the relationships section in the Object Definition file, and should only be changed if corresponding changes are made to the Object Definition file.

Page Configurations

You can configure several display properties for the pages that appear on the EDM. For most configurable pages, you can specify the number of fields on each row, and for all search pages you can specify the number of results to display on each page. You can also specify the type of object to display on a page and the name of the tabbed heading.

Certain properties of the following pages can be configured:

Search
Search Results
History Search
History Search Results
Matching Review Search
Matching Review Search Results
View/Edit

Audit Log

In the display configuration, you can specify whether an audit log is maintained of all instances in which object information was accessed from the EDM. If the log is maintained, then information about each instance of access can be viewed on the EDM. This is especially useful in healthcare implementations, where privacy of information is mandated.

Local ID Labels

A local ID is a unique identification code assigned to a record by the system in which the record originated. By default, this code is named “Local ID” on the EDM pages. This name can be modified to a name more recognizable by EDM users.

Search Page Configuration

Of the configurable pages, the page that requires the most configuration is the Search page. In addition to defining the number of fields per row and the number of records to display in the search results list, you can also specify the search criteria that appear and the types of searches allowed from the EDM.

You can define and name several search pages, each with their own configuration. For each page, you specify groups of fields that are displayed in boxed areas. Each boxed area can represent a different type of search, such as a demographic search, address search, EUID search, and so on.

For each search page you define, you must also specify the search types available, such as alphanumeric or phonetic. You can configure searches by specifying a name for the search, the maximum number of records to return, whether the results are weighted, and whether wildcard characters can be used. When you define the search types for the EDM, you must specify a query for each type you define. The queries you specify must already be defined in the Candidate Select file.

Implementation Configuration

The Enterprise Data Manager file defines certain information about the application server for the master index implementation, such as the names of certain validation and management components, debug parameters, and security information. The security for the master index application is based in the application server.

The Enterprise Data Manager File Structure

EDM properties are defined in the Enterprise Data Manager file in XML format. Some of the information entered into the default configuration file is based on the fields you defined in the wizard, and some is standard across all implementations. For most implementations, this file will require customization.

The following topics provide information about working with the Enterprise Data Manager file:

Modifying the Enterprise Data Manager File

You can modify the Enterprise Data Manager file at any time, but you must regenerate the application and redeploy the project after making any changes to the file. Changes made to this file do not affect match processing; it only affects the EDM. Most components of this file cannot be modified using the Configuration Editor; you need to modify the file directly. The possible modifications to this file are restricted by the schema definition, so be sure to validate the file after making any changes.

Enterprise Data Manager File Description

Table 14 lists each element in the Enterprise Data Manager file and provides a description of each element along with any requirements or constraints for each element.

Table 14 Enterprise Data Manager File Structure


Element/Attribute	Description
node-`object_name`	The configuration information for an object on the EDM. Each object that appears on the EDM must be defined in a node element. The node is named for the object it defines; for example: `node-Person` or `node-Address`. Most of the information you need to specify in the node elements is generated by the wizard, but you can modify the information as needed. Note – All fields defined in the Enterprise Data Manager file must also be defined in the Object Definition file; however, not all fields defined in the Object Definition file need to be defined for the EDM. Any fields or objects not listed in the Enterprise Data Manager file will not appear on the EDM.
node/display-order	The order in which the child object types appear in the tree view pane on the EDM pages.
node/merge-must-delete	An indicator of whether EDM users must specify which instances of the child object type to retain during a system record merge. Specify `false` to give EDM users the option of selecting the child objects to retain or accepting the default objects (the default objects are those in the destination system). Specify `true` to force the user to select the child objects to retain.
field-<field_name>	The configuration information for a field on the EDM. Each field that appears on the EDM must be defined in a field element. The element is named for the field it defines; for example: `field-FirstName`.
display-name	The name of the field as it will appear on the EDM.
display-order	The order in which the field appears on the EDM. For example, specify `1` to indicate this is the first field on the EDM pages, `2` to indicate it is the second field, and so on.
max-length	The maximum number of characters displayed on the EDM for the field.
gui-type	The type of display for the field. Specify one of the following options. TextBox - A standard data entry field MenuList - A field that must be populated by selecting from a drop-down list TextArea - A long field that requires a scrollbar, such as a comments field
value-type	The master index data type for the data populated in the field. The following data types are supported: string - Contains a string of characters. date - Contains a date value. float - Contains a floating point integer. int - Contains an integer. char - Contains a single character. boolean - Contains either true or false.
input-mask	A mask used by the EDM to add punctuation to a field. You can add an input mask to display telephone numbers as “(123)456-7890” even though the database might store them as “1234567890” and the user enters the numbers with no punctuation. The following character types are allowed: D - indicates a numeric character. L - indicates an alphabetic character. A - indicates an alphanumeric character. For example, the input mask for the above telephone format is “(DDD)DDD-DDDD”. Note – If the length of the input mask is greater than the value specified for the `max-length` element, the length of the input mask is used.
value-mask	A mask used by the master index application to strip any extra characters that were added by the input mask to ensure that data is stored in the database in the correct format. This mask must be the same length as the input mask. To specify a value mask, type the same value as is entered for the input mask, but type an “x” in place of each punctuation mark. For example, using the above phone number example, you need to specify a value mask of xDDDxDDDxDDDD. A value mask is not required for date fields.
value-list	The name of the menu list used to populate the drop-down list for the field. This is required if the `gui-type` specified is MenuList, and it must match a code of an element in the sbyn_common_header database table.
key-type	An indicator of whether the field (or a combination of key fields) must be unique in an enterprise record. Unique key fields identify unique child objects in an enterprise object. Specify `true` to indicate the field is a key field; specify `false` if it is not.
is-sensitive	An indicator of whether the value of the field is hidden on the EDM for records with a VIP status of “VIP”. Only users with the eView.Admin or eView.VIP user roles can view the hidden information. Specify `true` to hide the field value; specify `false` (or remove the `is-sensitive` element) to display the field value. Note – This element is only used if the `object-sensitive-plug-in-class` in the `impl-details` section is populated.
relationships	Configuration information for the hierarchy of the parent and child objects displayed on the EDM.
name	The name of the parent object.
children	The name of a child object. There should be one `children` element for each child node.
impl-details	The configuration information for certain classes that are required for the EDM to connect to the server. This section also defines debug and security options.
master-controller-jndi-name	The JNDI name for the Master Controller. The default name is ejb/`app-name`MasterController, where `app-name` is the name of the master index application.
validation-service-jndi-name	The JNDI name for the processing code validator. The default name is ejb/`app-name`CodeLookup.
usercode-jndi-name	The JNDI name for the user code validator (used for non-unique IDs). The default name is ejb/`app-name`UserCodeLookup.
report-generator-jndi-name	The JNDI name for the EDM report generator. The default name is ejb/`app-name`ReportGenerator.
debug-flag	An indicator of whether debug information is logged. Specify `true` to log debug information.
debug-dest	The destination to which debug information is written. Specify `console` to log debug information to a monitor; specify `file` to print to a file.
enable-security	An indicator of whether authorization security is enabled for the EDM (this refers to the security permissions defined in the application server). Specify `true` to enable security.
object-sensitive-plug-in-class	The name of the class that contains logic for masking the data in certain fields from certain users. For example, certain sensitive information should only be viewed by administrators. If you specify field masking, you must define a custom plug-in to handle the process and specify it here. Note – Sun Master Patient Index provides a predefined field-masking class.
gui-definition	The configuration information for the pages that appear on the EDM, including the types of searches available on the EDM.
initial-screen	The first page to appear when you log in to the EDM. Enter one of the following values. Matching Review EO Search Create System Record History Reports
system-display-name-overrides	Configuration information for the names of the local ID fields and headings that appear on the EDM. If you want to change the field label from “Local ID” to a name that is more relevant to your implementation, define that name here.
local-id-header	The name to use for the heading label of the local ID search section of the EDM Lookup page.
local-id	The name to use for all fields and columns containing local IDs. In fields where the local ID label is abbreviated to “LID1” or “LID2”, the name becomes `local-id`1 or `local-id`2 (where `local-id` is the value specified for this element).
page-definition	The configuration information for individual pages on the EDM.
eo-search	The configuration information for the Search pages.
root-object	The name of the type of object returned by the search (this must be the parent object).
tab-name	A name for the search pages. This name appears on tab label associated with the search pages on the EDM.
tab-entrance	The URL to the entry page of the search pages. This element should not be modified.
simple-search-page	Each `simple-search-page` element contains the configuration information for one of the searches that appears on the Search page.
screen-title	The name of the search as it appears in the Search Type drop-down list on the EDM, from which users can select a type of search to perform.
field-per-row	The number of fields to display in each row on the search page. For best readability, this value should be set at 1 or 2.
show-euid	An indicator of whether to display the EUID. Specify `true` to display the EUID; otherwise specify `false`. Only display this field if you want it to take precedence over all other search criteria. When the EUID is displayed, it appears in its own labelled box.
show-lid	An indicator of whether to display the local ID and system fields. Specify `true` to display the fields; otherwise specify `false`. Only display these fields if you want them to take precedence over all other search criteria (except the EUID field). When the local ID is displayed, the local ID and system fields appear in their own labelled box.
instruction	A short statement to help the user process a search. The text you enter here appears above the search fields on the Search page.
field-group	A list of fields that appear on the Search page. Each field group is contained in a labelled box on the Search page.
description	A description of the fields defined for the `field-group` element. This value appears as a box label for the area of the page that contains the specified fields.
field-ref	The simple field names of the fields in the field group using their corresponding objects as the root. For example, the path to the FirstName field in the Person object is “Person.FirstName”. You can define multiple `field-ref` elements for each field group.
field-ref/required	An indicator of whether the field is required in order to perform a search. Specify any of the following values. true - The corresponding field is required to perform the search. These fields are marked with an asterisk (). false* - The corresponding field is not required to perform the search. If the `required` attribute is not defined, the default is false. oneof - This is assigned to more than one field and at least one of the fields with this designation is required to perform the search. If a group of fields is designated as “oneof”, those fields are marked with a dagger (†) on the search page.
field-ref/choice	An indicator of whether this field allows you to search by a range of values rather than an exact value. Specify one of the following values. exact - The search is performed on the exact value entered (wildcard may be allowed). If the `choice` attribute is not specified, this is the default value. range - The search is performed on a range of values based on the entered search criteria. Fields with this designation appear twice on the search page, once with “From” appended to the field label and once with “To” appended to the field label. Be sure any searches that use range searching in the EDM are configured to use range searching in the Candidate Select file. To define a field for both exact and range searching, define the field twice; once with this attribute set to exact and once with it set to range.
search-option	The configuration information for a search. Each `search-option` element defines one type of search for the page.
display-name	A short phrase describing the type of search to perform, such as “Alphanumeric Search” or “Phonetic Search”. This appears next to the option button on the search page when multiple search options are defined for one page.
query-builder	The type of query to use when this type of search is selected. The value entered here must match a `query-builder` name in the Candidate Select file.
weighted	An indicator of whether the results of the search are assigned matching probability weights. Specify `true` to assign matching weights or `false` to return unweighted results.
candidate-threshold	The maximum number of records to return for a search. This value must be a positive number, and is only used for blocking queries. Setting the candidate threshold to zero is equivalent to not setting a threshold.
parameter	A list of optional parameters for the search.
name	The name of the parameter. Currently, only `UseWildCard` is available.
value	The value of the parameter. For the `UseWildCard` parameter, this is an indicator of whether the parameter is enabled or disabled. Specify `true` to allow wildcard characters or `false` to perform exact-match searches.
search-result-list-page	The configuration information for the Search Results page.
item-per-page	The number of resulting records to display on one page.
max-result-size	The maximum number of records to return for a search.
field-ref	The simple field names of the fields to appear in the search results list using their corresponding objects as the root. For example, the path to the FirstName field in the Person object is “Person.FirstName”. You can define multiple `field-ref` elements. The EUID appears in the list by default, so it does not need to be specified here.
eo-view-page	The configuration information for the View/Edit page.
field-per-row	The number of fields to display in each row of the EDM. For best readability, this value should be kept at 1.
create-eo	The configuration of the Create System Record pages.
root-object	The name of the type of object created (this must be the parent object).
tab-name	A name for the Create System Record pages. This name appears on tab label associated with the Create System Record pages on the EDM.
tab-entrance	The URL to the entry page of the Create System Record pages. This element should not be modified.
history	The configuration information for the History page.
root-object	The name of the type of object displayed on the History pages (this must be the parent object).
tab-name	A name for the History pages. This name appears on tab label associated with the History pages on the EDM.
tab-entrance	The URL to the entry page of the History pages. This element should not be modified.
xa-search-page	The configuration information for the History Search page.
field-per-row	The number of fields to display in each row of the History Search page. For best readability, this value should be set at 1 or 2.
search-result-list-page	The configuration information for the History Search Results page.
item-per-page	The number of transaction records to display on each page of the search results.
max-result-size	The maximum number of records to return for a History search.
field-ref	The simple field names of the fields to appear in the search results list using their corresponding objects as the root. These fields are in addition to the permanent fields, which include TransactionID, EUID1, EUID2, System, LID1, LID2, Function, SystemUser, and TimeStamp.
merge-history-key-field	The configuration information for the merge history tree.
field-ref	The configuration information for the fields that appear on the merge tree in addition to those that permanently appear in the merge tree transaction table. Permanent fields in the transaction table include TransactionID, EUID1, EUID2, System, LID1, LID2, Function, SystemUser, and TimeStamp. Any fields defined here also appear on the History Search Result page, but if a field is listed in both this element and the `search-result-list-page` element, only one instance of the field appears in the results list
matching-review	The configuration information for the Matching Review page.
root-object	The name of the type of object displayed on the Matching Review pages (this must be the parent object).
tab-name	A name for the Matching Review pages. This name appears on tab label associated with the Matching Review pages on the EDM.
tab-entrance	The URL to the entry page of the Matching Review pages. This element should not be modified.
pd-search-page	The configuration information for the Potential Duplicate Search page.
field-per-row	The number of fields to appear in each row on the Potential Duplicate Search page. For best readability, this value should be set at 1 or 2.
search-result-list-page	The configuration information for the Matching Review Search Results page.
item-per-page	The number of resulting records to display on each page of the search results.
max-result-size	The maximum number of records to return for the Matching Review search.
reports	The configuration information for the Reports page.
root-object	The name of the type of object displayed on the Reports pages (this must be the parent object).
tab-name	A name for the Reports pages. This name appears on tab label associated with the Reports pages on the EDM.
tab-entrance	The URL to the entry page of the Reports pages. This element should not be modified.
search-page-field-per-row	The number of fields to display in each row of the Reports Search page.
report	Configuration information for each report run by the EDM with the exception of search reports (which do not need to be configured). Each report is defined by a `report` element. These reports are identical to the reports that can be run from the command line report client.
report/name	The type of report being generated. Specify any of the following production reports. Assumed Match Potential Duplicate Deactivated Merged Unmerged Update Or specify any of the following activity reports. Weekly Activity Monthly Activity Yearly Activity
report/title	The descriptive name of the report. This can be any string and will appear as the title in the specified report.
enable	An indicator of whether the report can be run from the EDM. Specify true to allow the report to be run; specify `false` to disable the report.
max-result-size	The number of records to display on the report. If no value is entered or if the value is zero (0), the size defaults to 1000 records. To retrieve all records for a report, enter a very large value for this element.
fields	The configuration information for the fields that appear on each report.
field-ref	A list of fields to display on the report in addition to those that are displayed automatically. Use the simple field name for the `field-ref` value (simple field names are described in Master Index Field Notations). This element should be empty for the activity reports; if a list of fields is supplied for any activity reports, it is ignored.
audit-log	The configuration information for the Audit Log pages.
allow-insert	An indicator of whether entries are written to the audit log each time data is accessed on the EDM. Specify `true` to enable the audit log. Specify `false` to disable the audit log. If the audit log is maintained, the Audit Log page is available on the EDM for searching and viewing audit log entries and the information is stored in the sbyn_audit table.

Enterprise Data Manager File Example

Below is a short sample of the Enterprise Data Manager file based on a master index application processing person information.

<node-Person>
   <field-LastName>
      <display-name>Last Name</display-name>
      <display-order>1</display-order>
      <max-length>40</max-length>
      <gui-type>TextBox</gui-type>
      <value-type>string</value-type>
      <key-type>true</key-type>
   </field-LastName>
   <field-FirstName>
      <display-name>First Name</display-name>
      <display-order>2</display-order>
      <max-length>40</max-length>
      <gui-type>TextBox</gui-type>
      <value-type>string</value-type>
      <key-type>true</key-type>
   </field-FirstName>
   <field-DOB>
      <display-name>DOB</display-name>
      <display-order>3</display-order>
      <max-length>32</max-length>
      <gui-type>TextBox</gui-type>
      <value-type>date</value-type>
      <key-type>true</key-type>
   </field-DOB>
   <field-Gender>
      <display-name>Gender</display-name>
      <display-order>4</display-order>
      <max-length>8</max-length>
      <gui-type>MenuList</gui-type>
      <value-list>GENDER</value-list>
      <value-type>string</value-type>
      <key-type>true</key-type>
   </field-Gender>
   <field-SSN>
      <display-name>SSN</display-name>
      <display-order>5</display-order>
      <max-length>16</max-length>
      <gui-type>TextBox</gui-type>
      <value-type>string</value-type>
      <input-mask>DDD-DD-DDDD</input-mask>
      <value-mask>DDDxDDxDDDD</value-mask>
      <is-sensitive>true</is-sensitive>
   </field-SSN>
</node-Person>
<node-Alias display-order="1">
   <field-LastName>
      <display-name>LastName</display-name>
      <display-order>1</display-order>
      <max-length>40</max-length>
      <gui-type>TextBox</gui-type>
      <value-type>string</value-type>
      <key-type>true</key-type>
   </field-LastName>
   <field-FirstName>
      <display-name>FirstName</display-name>
      <display-order>2</display-order>
      <max-length>40</max-length>
      <gui-type>TextBox</gui-type>
      <value-type>string</value-type>
      <key-type>true</key-type>
   </field-FirstName>
</node-Alias>
<relationships>
   <name>Person</name>
   <children>Alias</children>
</relationships>
<impl-details>
   <master-controller-jndi-name>ejb/PersonMasterController
   </master-controller-jndi-name>
   <validation-service-jndi-name>ejb/PersonCodeLookup
   </validation-service-jndi-name>
   <usercode-jndi-name>ejb/PersonUserCodeLookup</usercode-jndi-name>
   <reportgenerator-jndi-name>ejb/PersonReportGenerator
   </reportgenerator-jndi-name>
   <debug-flag>true</debug-flag>
   <debug-dest>console</debug-dest>
   <enable-security>true</enable-security>
   <object-sensitive-plug-in-class>
    com.stc.eindex.security.VIPObjectSensitivePlugIn
   </object-sensitive-plug-in-class>
</impl-details>
<gui-definition>
   <system-display-name-overrides>
      <local-id-header>System Identifier</local-id-header>
      <local-id>System ID</local-id>
   </system-display-name-overrides>
   <page-definition>
      <eo-search>
         <root-object>Person</root-object>
         <tab-name>Person Search</tab-name>
         <tab-entrance>/EnterEOSearchSimpleAction.do</tab-entrance>
         <simple-search-page>
            <screen-title>Advanced Lookup (Phonetic)</screen-title>
            <field-per-row>2</field-per-row>
            <show-euid>false</show-euid>
            <show-lid>false</show-lid>
            <instruction/>
            <field-group>
               <description>Demographics</description>
               <field-ref>Person.LastName</field-ref>
               <field-ref>Person.FirstName</field-ref>
               <field-ref choice="range">Person.DOB</field-ref>
               <field-ref>Person.Gender</field-ref>
               <field-ref>Person.SSN</field-ref>
            </field-group>
            <search-option>
               <display-name>Phonetic Search</display-name>
               <query-builder>BLOCKER-SEARCH2</query-builder>
               <weighted>true</weighted>
               <parameter>
                  <name>UseWildcard</name>
                  <value>false</value>
               </parameter>
            </search-option>
         </simple-search-page>
         <simple-search-page>
            <screen-title>Advanced Lookup (Alpha)</screen-title>
            <field-per-row>2</field-per-row>
            <show-euid>false</show-euid>
            <show-lid>false</show-lid>
            <instruction>Enter as much information as possible to
             narrow the search</instruction>
            <field-group>
               <description>Demographics</description>
               <field-ref>Person.LastName</field-ref>
               <field-ref>Person.FirstName</field-ref>
               <field-ref>Person.Gender</field-ref>
               <field-ref choice="range">Person.DOB</field-ref>
               <field-ref>Person.SSN</field-ref>
            </field-group>
            <search-option>
               <display-name>Alpha Search</display-name>
               <query-builder>ALPHA-SEARCH</query-builder>
               <weighted>false</weighted>
               <parameter>
                  <name>UseWildcard</name>
                  <value>true</value>
               </parameter>
            </search-option>
         </simple-search-page>
         <simple-search-page>
            <screen-title>Simple Person Lookup</screen-title>
            <field-per-row>2</field-per-row>
            <show-euid>true</show-euid>
            <show-lid>true</show-lid>
            <instruction/>
            <field-group>
               <description>SSN</description>
               <field-ref>Person.SSN</field-ref>
            </field-group>
            <search-option>
               <display-name>Alpha Search</display-name>
               <query-builder>ALPHA-SEARCH</query-builder>
               <weighted>false</weighted>
               <parameter>
                  <name>UseWildcard</name>
                  <value>true</value>
               </parameter>
            </search-option>
         </simple-search-page>
         <search-result-list-page>
            <item-per-page>10</item-per-page>
            <max-result-size>100</max-result-size>
            <field-ref>Person.LastName</field-ref>
            <field-ref>Person.FirstName</field-ref>
            <field-ref>Person.DOB</field-ref>
         </search-result-list-page>
         <eo-view-page>
            <field-per-row>1</field-per-row>
         </eo-view-page>
      </eo-search>
      <create-eo>
         <root-object>Person</root-object>
         <tab-name>Create System Record</tab-name>
         <tab-entrance>/EnterEOCreateAction.do</tab-entrance>
      </create-eo>
      <history>
         <root-object>Person</root-object>
         <tab-name>History</tab-name>
         <tab-entrance>/EnterXASearchAction.do</tab-entrance>
         <xa-search-page>
            <field-per-row>2</field-per-row>
         </xa-search-page>
         <search-result-list-page>
            <item-per-page>10</item-per-page>
            <max-result-size>100</max-result-size>
            <field-ref>Person.FirstName</field-ref>
            <field-ref>Person.LastName</field-ref>
         </search-result-list-page>
         <merge-history-key-field>
            <field-ref>Person.FirstName</field-ref>
            <field-ref>Person.LastName</field-ref>
         </merge-history-key-field>
      </history>
      <matching-review>
         <root-object>Person</root-object>
         <tab-name>Matching Review</tab-name>
         <tab-entrance>/EnterPDSearchAction.do</tab-entrance>
         <pd-search-page>
            <field-per-row>2</field-per-row>
         </pd-search-page>
         <search-result-list-page>
            <item-per-page>10</item-per-page>
            <max-result-size>100</max-result-size>
         </search-result-list-page>
      </matching-review>
      <reports>
         <root-object>Person</root-object>
         <tab-name>Reports</tab-name>
         <tab-entrance>/EnterReportSearchAction.do</tab-entrance>
         <search-page-field-per-row>2</search-page-field-per-row>
         <report name="Potential Duplicate"
          title="Potential Duplicate Report">
            <enable>true</enable>
            <max-result-size>2000</max-result-size>
            <fields>
               <field-ref>Person.FirstName</field-ref>
               <field-ref>Person.LastName</field-ref>
               <field-ref>Person.SSN</field-ref>
               <field-ref>Person.DOB</field-ref>
            </fields>
         </report>
      </reports>
      <audit-log>
         <allow-insert>false</allow-insert>
      </audit-log>
   </page-definition>
</gui-definition>