name

The name of the master index application. This name must match the name of the parent object. 

database

The database platform used by the master index application. Currently, the only values allowed are Oracle and SQL Server.

dateformat

The date format to use for the master index application. Three formats are allowed for the date: MM/dd/yyyy, yyyy/MM/dd, and dd/MM/yyyy. 

nodes

The configuration information for an object. There can be multiple nodes elements, each defining one parent or child object in the object structure. Each nodes element also defines the fields contained in each object along with the field attributes. The object structure must include one parent object and can include several child objects or no child objects.

tag

The name of the parent or child object defined by the nodes element.

Due to database naming constraints, the length of the name of the parent object plus the length of any child object name must be 21 characters or less.

fields

The configuration information for a field. There can be multiple fields elements.

field-name

The name of the field. Follow these guidelines when naming fields. 

• The name cannot be longer than 30 characters.

• The name cannot be objectId, where object is the name of an object in the data structure. For example, you cannot create a field named AddressId if there is an Address object in the structure.

• Field names must conform to Oracle or SQL Server naming conventions, must conform to Java naming standards, and cannot contain XML reserved characters.

field-type

The data type for each field. Possible data types are: 

• string - Fields of this type contain a string of characters.

• date - Fields of this type contain a date value.

• float - Fields of this type contain a floating point integer.

• int - Fields of this type contain an integer.

• byte - Fields of this type contain a single character.

• boolean - Fields of this type can contain either true or false.

size

The number of characters allowed in each field. If you modify this value, be sure to modify the corresponding database column accordingly. 

updateable

An indicator of whether the field can be updated using the EDM or from back-end messages. Specify true if the field can be updated, or specify false if it cannot.

required

An indicator of whether the field is required in order to save an enterprise object in the database. Specify true if the field is required, or specify false if it is not.

code-module

The identification code for the menu list that appears for this field in the EDM. This must match a value in the code column of the sbyn_comment_header database table. This element is optional. 

maximum-value

The maximum value allowed in the field. To specify a value for a date field, use the format YYYY-MM-DD. This element is optional. 

minimum-value

The minimum value allowed in the field. To specify a value for a date field, use the format YYYY-MM-DD. This element is optional. 

pattern

The required pattern for the field. For more information about possible values and using Java patterns, see “Patterns” in the class list for java.util.regex in the Javadocs provided with J2SE Platform. This element is optional.

user-code

The processing code for the drop-down list that appears on the MIDM for the fields defined by the constraint–by property, described below. These codes are used for non-unique IDs, such as account numbers, insurance policies, credit cards, and so on.

This must match an entry in the code_list column of the sbyn_user_code database table.

constraint-by

The name of the field that contains the corresponding user–code value (described above) to use to validate the current field. The user–code and constraint-by properties are used in conjunction to define non-unique ID types, such as credit card numbers or account numbers. The first purpose is to define a drop-down list for the field that contains the user code value. The second purpose is to validate the field that contains the constraint value against definitions for the field with the user code value.

For example, if you store non-unique IDs such as credit card numbers or insurance policy numbers, you could create a field named ID Type with a user–code of CREDCARD (CREDCARD also needs to be defined as a code in the sbyn_user_code table). This gives the ID Type field a drop-down list based on the definitions for CREDCARD in the sbyn_user_code table. Definitions would be VISA, MASTERCARD, AMEX, and so on. You could then create a field named ID that would be constrained by the formats defined for the ID Type field. Any credit card numbers you enter would be validated against the format defined for the type of credit card you selected in ID Type.

key-type

An indicator of whether the field is used to identify unique objects. Specify true if the element is a unique object identifier; specify false if it is not. This element is optional.

Each child object should contain at least one field that is a unique object identifier, but it is not required. If two or more fields are unique identifiers, the combined value of these fields must be unique in a given enterprise record.

relationships

The configuration information for the hierarchy of the objects you defined in the nodes elements. Only one object can be the parent object; the remaining objects must be defined as children. The relationship definition allows a record to contain multiple instances of each child object. For example, if you define Address and Telephone child objects, the record can contain multiple addresses and telephone numbers.

name

The name of the parent object, as defined in the nodes elements.

children

The name of a child object, as defined in the nodes elements. You can define multiple children elements.

   <name>Person</name>
   <database>oracle</database>
   <dateformat>MM/dd/yyyy</dateformat>
   <nodes>
      <tag>Person</tag>
      <fields>
         <field-name>LastName</field-name>
         <field-type>string</field-type>
         <size>40</size>
         <updateable>true</updateable>
         <required>true</required>
         <key-type>false</key-type>
      </fields>
      <fields>
         <field-name>FirstName</field-name>
         <field-type>string</field-type>
         <size>40</size>
         <updateable>true</updateable>
         <required>true</required>
         <key-type>false</key-type>
      </fields>
      <fields>
         <field-name>DOB</field-name>
         <field-type>date</field-type>
         <updateable>true</updateable>
         <required>true</required>
         <minimum-value>1900-01-01</minimum-value>
         <key-type>false</key-type>
      </fields>
      <fields>
         <field-name>SSN</field-name>
         <field-type>string</field-type>
         <size>16</size>
         <updateable>true</updateable>
         <required>false</required>
         <pattern>[0-9]{9}</pattern>
         <key-type>false</key-type>
      </fields>
   </nodes>
   <nodes>
      <tag>Address</tag>
      <fields>
         <field-name>AddressType</field-name>
         <field-type>string</field-type>
         <size>8</size>
         <updateable>true</updateable>
         <required>true</required>
         <code-module>ADDRTYPE</code-module>
         <key-type>true</key-type>
      </fields>
      ...
   </nodes>
   <nodes>
      <tag>Phone</tag>
      ...
   </nodes>
   <relationships>
      <name>Person</name>
      <children>Address</children>
      <children>Phone</children>
   </relationships>

QueryBuilderConfig

The configuration class for the query builders. This should not be modified. 

query-builder

A list of query definitions. This element defines each query and the attributes of each query. 

query-builder/name

A unique ID for the element. This element is used to identify the Query Builder and is referenced from the Enterprise Data Manager file when specifying the query to use on a search page. It is also referenced from the Match Field file when specifying the query to use for matching. No spaces are allowed in this attribute. 

query-builder/class

The fully qualified name of the query class. Two default Query Builder classes are provided. 

• com.stc.eindex.querybuilder.BasicQueryBuilder – Builds dynamic queries using all the available input fields. When configured to use normalized and phonetic data, this query performs phonetic searches; when configured not to use normalized and phonetic data, this query is used for exact alphanumeric searches.

• com.stc.eindex.querybuilder.BlockerQueryBuilder – Builds queries using the criteria defined in the block definitions defined for the query. When a blocking query is performed, the application searches only on the blocks for which the query has complete data.

query-builder/parser-class

The fully qualified name of the class that parses the config elements for each query. This should not be modified for the default queries.

query-builder/standardize

An indicator of whether the query criteria is standardized before being passed to the query. Specify true if any fields are standardized for the query; specify false if no fields are standardized for the query.

query-builder/phoneticize

An indicator of whether the query criteria is phonetically encoded before being passed to the query. Specify true if any fields are phonetically encoded for the query specify; false if no fields are phonetically encoded for the query.

config

The configuration information for a query. Each query-builder element contains one config element.

option

One query parameter, specified by key and value attributes, as described below. This is only used by basic queries; blocking queries do not use this element.

option/key

A parameter for the query option. For the default basic query, only the UseWildCard key is available.

option/value

The value of the key specified by the corresponding key attribute. For the default option, UseWildCard, specify true to allow wildcard characters for that query type; otherwise specify false. When wildcard characters are enabled, you can enter a percent sign (%) to indicate multiple unknown characters.

block-definition

A list of Oracle hints or SQL Server OPTION hints and defined query criteria blocks, which are identified by unique ID numbers. 

block-definition/number

An attribute of the block-definition element that specifies the unique ID number of each query block. Each block defined for the blocking query must be identified by a unique ID.

hint

A hint to add to the query to help optimize query execution. Hints are especially useful when a blocking query uses only child object fields; the hint can specify to scan the child object table first. This element is optional. For SQL Server, only OPTION hints are supported.

block-rule

A list of fields to be included in each query block, including indicators of whether a range is to be used and, if so, what type of range search to perform. 

type of search

An indicator of the type of search to perform on the field defined in the following elements. Each type of search element defines one field in a block-rule element; that is, one field in a query block. This element includes a field element, a source or constant element, and, for range searches only, a default element that defines lower and upper bounds.

Specify one of the following types.

• equals - Performs an exact search against either the criteria or the value defined for the constant element.

• not-equals - Searches for values that do not equal either the criteria or the value defined for the constant element.

• greater-than-or-equal - Performs a search for values that are greater than or equal to either the criteria or the value defined for the constant element.

• less-than-or-equal - Performs a search for values that are less than or equal to either the criteria or the value defined for the constant element.

• range - Performs a search against a range of either static or user-defined ranges. If you select this option, you must specify upper and lower bounds in a default element.

If a field is to be used for simple range searching (where the user or incoming message supplies lower and upper limits of the range are supplied) be sure to define that field for range searching in the Enterprise Data Manager file for the searches that use this query. For more complex range searches that use offset values or constants instead of user-supplied limits, do not define the field for range searching in the Enterprise Data Manager file.

field

The fully qualified field name of the field to be included in the query block (for example, Enterprise.Person.Address.AddressLine1). 

source

The qualified field name of the source field in the object from which the criteria is obtained (for example, Person.Address.AddressLine1). An asterisk (*) can be used as a wildcard character. If the criteria should be a constant value instead of being supplied by a user or incoming message, define a constant element instead of a source element.

When a field in a child object is defined for a blocking query, use the asterisk wildcard character in the ePath to the source field to ensure all instances of the child object in an incoming message are used as search criteria. Each instance is joined by an OR operator. For example, this configuration:

<field>Enterprise.SystemSBR.Person.Alias.FirstName

</field>

<source>Person.Alias[*].FirstName</source>

would result in a WHERE clause similar to this:

WHERE Alias.FirstName=”Meg” OR Alias.FirstName=”Maggie”

constant

A constant value that provides the criteria for a search. Define this element instead of a source element if the criteria is a constant rather than being user defined. You can use a constant value with the following types of queries: equals, not-equals, greater-than-or-equals, and less-than-or-equals.

default

A list of upper and lower limits defining a range search. If no limits are defined, the search is a simple range search in which the upper and lower values are supplied by the user or the incoming message (for example, in “Date of Birth From” and “Date of Birth To” fields). 

lower-bound

The lower limit of a constant or offset range search. Use a negative number for the lower limit of an offset search. This number is added to the value supplied for the search to determine the lower limit of the range. The value can be numeric, date, or string. See Range Search Processing (Repository) for more information.

lower-bound/type

The type of range search. Define the type attribute as offset to use an offset value or as constant to define a lower constant.

upper-bound

The upper limit of a constant or offset range search. The value can be numeric, date, or string. See Range Search Processing (Repository) or more information.

upper-bound/type

The type of range search. Define the type attribute as offset to use an offset value or as constant to define an upper constant.

<QueryBuilderConfig module-name="QueryBuilder" parser-class=
   "com.stc.eindex.configurator.impl.querybuilder.QueryBuilderConfiguration">
   <query-builder name="ALPHA-SEARCH"
    class="com.stc.eindex.querybuilder.BasicQueryBuilder"
    parser-class="com.stc.eindex.configurator.impl.querybuilder.
    KeyValueConfiguration" standardize="true" phoneticize="false">
      <config>
         <option key="UseWildcard" value="true"/>
      </config>
   </query-builder>
   <query-builder name="PHONETIC-SEARCH"
    class="com.stc.eindex.querybuilder.BasicQueryBuilder"
    parser-class="com.stc.eindex.configurator.impl.querybuilder.
    KeyValueConfiguration" standardize="true" phoneticize="true">
      <config>
         <option key="UseWildcard" value="false"/>
      </config>
   </query-builder>
   <query-builder name="BLOCKER-SEARCH"
    class="com.stc.eindex.querybuilder.BlockerQueryBuilder" parser-
    class="com.stc.eindex.configurator.impl.blocker.BlockerConfig"
    standardize="true" phoneticize="true">
      <config>
         <block-definition number="ID000000">
            <block-rule>
               <equals>
                  <field>Enterprise.SystemSBR.Person.FnamePhonetic
                  </field>
                  <source>Person.FnamePhoneticCode</source>
               </equals>
               <equals>
                  <field>Enterprise.SystemSBR.Person.LnamePhonetic
                  </field>
                  <source>Person.LnamePhoneticCode</source>
               </equals>
            </block-rule>
         </block-definition>
         <block-definition number="ID000001">
            <block-rule>
               <equals>
                  <field>Enterprise.SystemSBR.Person.SSN</field>
                  <source>Person.SSN</source>
               </equals>
            </block-rule>
         </block-definition>
         <block-definition number="ID000002">
            <hint>ALL_ROWS</hint>
            <block-rule>
               <equals>
                  <field>Enterprise.SystemSBR.Person.FnamePhonetic
                  </field>
                  <source>Person.FnamePhoneticCode</source>
               </equals>
               <range>
                  <field>Enterprise.SystemSBR.Person.DOB</field>
                  <source>Person.DOB</source>
                  <default>
                     <lower-bound type="offset">-5</lower-bound>
                     <upper-bound type="offset">5</upper-bound>
                  </default>
               </range>
               <equals>
                  <field>Enterprise.SystemSBR.Person.Gender</field>
                  <source>Person.Gender</source>
               </equals>
            </block-rule>
         </block-definition>
      </config>
   </query-builder>
</QueryBuilderConfig>

choice attribute set to “exact”

field_name

field_name

where field_name = value

choice attribute set to “range”

field_name From

field_name To

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

choice attribute set to “range”

field_name From

field_name To

field_name From

where field_name >= value_from

choice attribute set to “range”

field_name From

field_name To

field_name To

where field_name <= value_to

field defined once with choice attribute set to “exact” and once with it set to “range”

field_name

field_name From

field_name To

field_name

where field_name = value

field defined once with choice attribute set to “exact” and once with it set to “range”

field_name

field_name From

field_name To

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

field defined once with choice attribute set to “exact” and once with it set to “range”

field_name

field_name From

field_name To

field_name From

where field_name >= value_from

field defined once with choice attribute set to “exact” and once with it set to “range”

field_name

field_name From

field_name To

field_name To

where field_name <= value_to

field defined once with choice attribute set to “exact” and once with it set to “range” *

field_name

field_name From

field_name To

field_name

field_name From

where field_name >= value_from

field defined once with choice attribute set to “exact” and once with it set to “range” *

field_name

field_name From

field_name To

field_name

field_name To

where field_name <= value_to

field defined once with choice attribute set to “exact” and once with it set to “range” *

field_name

field_name From

field_name To

field_name

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

choice attribute set to “exact”

field_name

both upper and lower offsets defined 

field_name

where field_name >= (value + lower) and field_name <= (value + upper)

choice attribute set to “exact”

field_name

only lower offset defined 

field_name

where field_name >= (value + lower)

choice attribute set to “exact”

field_name

only upper offset defined 

field_name

where field_name <= (value + upper)

choice attribute set to “range”

field_name From

field_name To

upper, lower, or both offsets are defined 

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

choice attribute set to “range”

field_name From

field_name To

upper, lower, or both offsets are defined 

field_name From

where field_name >= value_from

choice attribute set to “range”

field_name From

field_name To

upper, lower, or both offsets are defined 

field_name To

where field_name <= value_to

both upper and lower bound offsets are defined 

field_name

field_name From

field_name To

field_name

where field_name >= (value + lower) and field_name <= (value + upper)

only a lower offset is defined 

field_name

field_name From

field_name To

field_name

where field_name >= (value + lower)

only an upper offset is defined 

field_name

field_name From

field_name To

field_name

where field_name <= (value + upper)

upper, lower, or both offsets are defined 

field_name

field_name From

field_name To

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

upper, lower, or both offsets are defined 

field_name

field_name From

field_name To

field_name From

where field_name >= value_from

upper, lower, or both offsets are defined 

field_name

field_name From

field_name To

field_name To

where field_name <= value_to

both upper and lower offsets are defined 

field_name

field_name From

field_name To

field_name

field_name From

where field_name >= value_from and field_name <= (value + upper)

only a lower offset is defined 

field_name

field_name From

field_name To

field_name

field_name From

where field_name >= (value + lower)

only an upper offset is defined 

field_name

field_name From

field_name To

field_name

field_name From

where field_name <= (value + upper)

both upper and lower offsets are defined 

field_name

field_name From

field_name To

field_name

field_name To

where field_name <= value_to and field_name >= (value + lower)

only a lower offset is defined 

field_name

field_name From

field_name To

field_name

field_name To

where field_name >= (value + lower)

only an upper offset is defined 

field_name

field_name From

field_name To

field_name

field_name To

where field_name <= (value + upper)

both upper and lower offsets are defined* 

field_name

field_name From

field_name To

field_name

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

choice attribute set to “exact”

field_name

field_name

where field_name = value

choice attribute set to “range”

field_name From

field_name To

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

choice attribute set to “range”

field_name From

field_name To

field_name From

where field_name >= value_from and field_name <= upper

choice attribute set to “range”

field_name From

field_name To

field_name To

where field_name <= value_to and field_name >= lower

upper, lower, or both constants are defined 

field_name

field_name From

field_name To

field_name

where field_name = value

upper, lower, or both constants are defined 

field_name

field_name From

field_name To

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

either upper or both constants are defined 

field_name

field_name From

field_name To

field_name From

where field_name >= value_from and field_name <= upper

lower constant is defined 

field_name

field_name From

field_name To

field_name From

where field_name >= value_from

either upper or both constants are defined 

field_name

field_name From

field_name To

field_name

field_name From

where field_name >= value_from and field_name <= upper

lower constant is defined * 

field_name

field_name From

field_name To

field_name

field_name From

where field_name >= value_from

either lower or both constants are defined 

field_name

field_name From

field_name To

field_name To

where field_name <= value_to and field_name >= lower

upper constant is defined 

field_name

field_name From

field_name To

field_name To

where field_name <= value_to

either lower or both constants are defined 

field_name

field_name From

field_name To

field_name

field_name To

where field_name <= value_to and field_name >= lower

upper constant is defined * 

field_name

field_name From

field_name To

field_name

field_name To

where field_name <= value_to

upper, lower, or both constants are defined * 

field_name

field_name From

field_name To

field_name

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

upper offset and lower constant are defined 

field_name

field_name From

field_name To

field_name

where field_name >= lower and field_name <= (value + upper)

upper offset and lower constant are defined 

field_name

field_name From

field_name To

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

upper offset and lower constant are defined 

field_name

field_name From

field_name To

field_name From

where field_name >= value_from

upper offset and lower constant are defined 

field_name

field_name From

field_name To

field_name To

where field_name <= value_to and field_name >= lower

upper offset and lower constant are defined 

field_name

field_name From

field_name To

field_name

field_name From

where field_name <= (value + upper) and field_name >= value_from

upper offset and lower constant are defined 

field_name

field_name From

field_name To

field_name

field_name To

where field_name <= value_to and field_name >= lower

upper offset and lower constant are defined * 

field_name

field_name From

field_name To

field_name

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

upper constant and lower offset are defined 

field_name

field_name From

field_name To

field_name

where field_name <= upper and field_name >= (value + lower)

upper constant and lower offset are defined 

field_name

field_name From

field_name To

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

upper constant and lower offset are defined 

field_name

field_name From

field_name To

field_name From

where field_name >= value_from and field_name <= upper

upper constant and lower offset are defined 

field_name

field_name From

field_name To

field_name To

where field_name <= value_to

upper constant and lower offset are defined * 

field_name

field_name From

field_name To

field_name

field_name From

where field_name <= upper and field_name >= value_from

upper constant and lower offset are defined * 

field_name

field_name From

field_name To

field_name

field_name To

where field_name <= value_to and field_name >= (value + lower)

upper constant and lower offset are defined + 

field_name

field_name From

field_name To

field_name

field_name From

field_name To

where field_name >= value_from and field_name <= value_to

MasterControllerConfig

The configuration class for the Manager Service. The attributes define the module name and Java class. The default values should not be changed. 

logic-class

A custom plug-in that defines custom processing logic for the execute match functions that can be called from Collaborations and Business Processes. This element is optional. 

logic-class-gui

A custom plug-in that defines custom processing logic for the execute match function that is called from the Enterprise Data Manager (EDM). This element is optional. 

update-mode

An indicator of whether to recalculate potential duplicates when a record is updated. Specify Pessimistic to recalculate potential duplicates; specify Optimistic to prevent potential duplicate recalculation on updates.

merged-record-update

An indicator of whether records with a status of Merged can be updated. Specify Enabled to allow updates of merged records; specify Disabled to ensure that records with a Merged status are not updated.

execute-match

Specifies the blocking query to use for match processing. 

query-builder

The name of the blocking query to use for match processing. The name must match a query defined in the Candidate Select file. 

option

Optional parameters for the blocking query. Currently parameters are not used by any predefined blocking queries. 

option/key

A parameter for the blocking query. 

option/value

The value of the key specified by the corresponding key attribute.

DecisionMakerConfig

The configuration class for the Decision Maker. The attributes define the module name and Java class. The default values should not be changed. 

decision-maker-class

The Java class that contains the methods used by the Decision Maker class. The default value, com.stc.eindex.decision.impl.DefaultDecisionMaker, should not need to be changed, but you can implement a custom Decision Maker class. The default class accepts the parameters described below.

parameters

A list of parameters for the Decision Maker class. 

parameter

A definition of a Decision Maker parameter. The parameters element can contain multiple parameter elements, each defining one parameter.

description

A brief description of the parameter. This element is optional. 

parameter-name

The name of the parameter. The default Decision Maker class takes the following parameters (see Decision Makerfor more information about these parameters).

• OneExactMatch - A Boolean indicator of whether an assumed match is made when there are more than one record above the match threshold.

• SameSystemMatch - A Boolean indicator of whether an assumed match can be made between two records that originate from the same external system.

• DuplicateThreshold - The lowest match weight at which two records are considered to be potential duplicates.

• MatchThreshold - The lowest match weight at which two records are assumed to be a match of one another.

parameter-type

The type of parameter. Valid values are java.lang.Long, java.lang.Short, java.lang.Byte, java.lang.String, java.lang.Integer, java.lang.Boolean, java.lang.Double, or java.lang.Float.

parameter-value

The value of the parameter. For OneExactMatch and SameSystemMatch, this must be a Boolean value. For MatchThreshold and DuplicateThreshold, this must be a Float value.

EuidGeneratorConfig

The configuration class for the EUID Generator. The attributes define the module name and Java class. The default values should not be changed. 

euid-generator-class

The Java class used by the master index application to generate new EUIDs. The default class is com.stc.eindex.idgen.impl.DefaultEuidGenerator, which assigns sequential EUIDs based on the three parameters described below.

parameters

A list of parameters for the EUID Generator class. 

parameter

A parameter definition. The parameters element can contain multiple parameter elements, each defining one parameter.

description

A brief description of the parameter. This element is optional. 

parameter-name

The name of the parameter. The default EUID Generator class takes the following parameters (see EUID Generator for more information about these parameters).

• IdLength - The length of the EUIDs generated by the master index application.

• CheckSum - The length of the checksum value used to validate EUIDs.

• ChunkSize - The number of EUIDs allocated to the server at one time.

parameter-type

The type of parameter. Valid values are java.lang.Long, java.lang.Short, java.lang.Byte, java.lang.String, java.lang.Integer, java.lang.Boolean, java.lang.Double, or java.lang.Float.

parameter-value

The value of the parameter. For the default parameters, the values are all integers. 

<MasterControllerConfig module-name="MasterController" 
parser-class="com.stc.eindex.configurator.impl.master.MasterControllerConfiguration">
   <logic-class>CustomMatchLogic</logic-class>
   <logic-class-gui>CustomMatchLogicEDM</logic-class-gui>
   <update-mode>Pessimistic</update-mode>
   <merged-record-update>Disabled</merged-record-update>
   <execute-match>
      <query-builder name="BLOCKER-SEARCH"></query-builder>
   </execute-match>
</MasterControllerConfig>
<DecisionMakerConfig module-name="DecisionMaker" 
parser-class="com.stc.eindex.configurator.impl.decision.DecisionMakerConfiguration">
   <decision-maker-class>
      com.stc.eindex.decision.impl.DefaultDecisionMaker
   </decision-maker-class>
   <parameters>
      <parameter>
         <parameter-name>OneExactMatch</parameter-name>
         <parameter-type>java.lang.Boolean</parameter-type>
         <parameter-value>false</parameter-value>
      </parameter>
      <parameter>
         <parameter-name>SameSystemMatch</parameter-name>
         <parameter-type>java.lang.Boolean</parameter-type>
         <parameter-value>true</parameter-value>
      </parameter>
      <parameter>
         <parameter-name>DuplicateThreshold</parameter-name>
         <parameter-type>java.lang.Float</parameter-type>
         <parameter-value>7.25</parameter-value>
      </parameter>
      <parameter>
         <parameter-name>MatchThreshold</parameter-name>
         <parameter-type>java.lang.Float</parameter-type>
         <parameter-value>29.0</parameter-value>
      </parameter>            
   </parameters>
</DecisionMakerConfig>
<EuidGeneratorConfig module-name="EuidGenerator" parser-class=
"com.stc.eindex.configurator.impl.idgen.EuidGeneratorConfiguration">
   <euid-generator-class>
      com.stc.eindex.idgen.impl.DefaultEuidGenerator
   </euid-generator-class>
   <parameters>
      <parameter>
         <parameter-name>IdLength</parameter-name>
         <parameter-type>java.lang.Integer</parameter-type>
         <parameter-value>10</parameter-value>
      </parameter>
      <parameter>
         <parameter-name>ChecksumLength</parameter-name>
         <parameter-type>java.lang.Integer</parameter-type>
         <parameter-value>0</parameter-value>
      </parameter>
      <parameter>
         <parameter-name>ChunkSize</parameter-name>
         <parameter-type>java.lang.Integer</parameter-type>
         <parameter-value>1000</parameter-value>
      </parameter>
   </parameters>
</EuidGeneratorConfig>

StandardizationConfig

The configuration information for fields to be standardized. It consists of several structures that define standardization rules for a set of fields. The StandardizationConfig attributes define the module name and Java class, and their default values should not be changed.

standardize-system-object

A standardization structure that defines configuration rules, including normalization, parsing, and phonetic encoding. Each standardization structure contains three primary elements: structures-to-normalize, free-form-texts-to-standardize, and phoneticize-fields. These elements are all required, however any of them can be empty

system-object-name

The name of the object containing the fields defined for standardization. Specifying the parent object allows you to specify any field in any object for standardization. You can also create multiple standardization structures and specify a different object for each structure. 

structures-to-normalize

The configuration information for fields that require normalization (but not parsing or reformatting) before being processed by the standardization engine. 

group

The national domain, source fields, and target fields for one normalization unit. You can define multiple group elements.

group/standardization-type

The type of standardization to perform on the source fields. This is specific to the type of data being processed and the standardization engine being used. For more information about Sun Match Engine types, see Understanding the Sun Match Engine.

group/domain-selector

The Java class used by the Sun Match Engine to determine the nationality of the data being processed. If no selector is specified, the default is US. 

Possible values for the Sun Match Engine include the following:

• com.stc.eindex.matching.impl.SingleDomainSelectorAU

• com.stc.eindex.matching.impl.SingleDomainSelectorFR

• com.stc.eindex.matching.impl.SingleDomainSelectorUK

• com.stc.eindex.matching.impl.SingleDomainSelectorUS

• com.stc.eindex.matching.impl.MultipleDomainSelector

local-field-name

The ePath to an identifying field in the object structure that indicates which of the defined local-codes definitions to use. If no field is specified, the standardization engine defaults to the United States domain. This field must be contained in the object that contains the fields defined for normalization in this structure.

locale-maps

A list of local codes that define how the standardization engine determines which national domain to use. 

local-codes

A list of value and locale pairs that indicate the national domain to use based on the value of the identifying field in an incoming message (specified by the local-field-name).

value

A value that, when contained in the identifying field, indicates that the standardization engine will use the corresponding locale element to determine which national domain to use to standardize the data. To specify a default domain, enter “Default” in this element.

locale

A domain code indicating which national domain to use to standardize data when the identifying field value in a transaction matches the corresponding value element.

The supported locale codes for the Sun Match Engine include the following:

• AU - for Australian data

• FR - for French data

• UK - for United Kingdom data

• US - for United States data

unnormalized-source-fields

A list of source fields to be normalized. 

source-mapping

The configuration information for one field in the list of source fields to be normalized. 

unnormalized-source-field-name

The ePath of the source field to normalize in the system object (for example, Person.FirstName). 

standardized-object-field-id

An identification code that identifies the field to normalize to the standardization engine. This ID is specific to the standardization engine in use and must correspond to a field ID defined by that engine. For more information, see Understanding the Sun Match Engine.

normalization-targets

A list of destination fields to hold the normalized data. 

target-mapping

The configuration information for one field in the list of destination fields. 

standardized-object-field-id

An identification code that identifies the normalized field to the standardization engine. This is specific to the standardization engine in use and must correspond to a field ID defined by that engine. For more information, see Understanding the Sun Match Engine.

standardized-target-field-name

The ePath of the target field in which the normalized value is saved in the system object (for example, Person.Alias[*].StdLastName). 

freeform-texts-to-standardize

The configuration information for fields that require parsing or reformatting and, optionally, normalization, before being processed by the standardization engine. 

group

The configuration information for the national domain and the source and target fields for one standardization unit. You can define multiple group elements.

group/standardization-type

The type of standardization to perform on the source fields. This is specific to the standardization engine being used and the type of data being processed. For more information, see Understanding the Sun Match Engine.

group/domain-selector

The Java class used by the Sun Match Engine to determine the nationality of the data being processed. Possible values are listed below. If no selector is specified, the default is US. 

• com.stc.eindex.matching.impl.SingleDomainSelectorAU

• com.stc.eindex.matching.impl.SingleDomainSelectorFR

• com.stc.eindex.matching.impl.SingleDomainSelectorUK

• com.stc.eindex.matching.impl.SingleDomainSelectorUS

• com.stc.eindex.matching.impl.MultipleDomainSelector

local-field-name

The ePath to an identifying field in the object structure that indicates which of the defined local-codes definitions to use. If this element is not defined, the standardization engine defaults to the United States domain. This field must be contained in the object that contains the fields defined for standardization in this structure.

locale-maps

A list of local codes that define how the standardization engine determines which national domain to use. 

local-codes

A list of value and locale pairs that indicate the national domain to use based on the value of the identifying field in an incoming message (specified by the local-field-name).

value

A value that, when contained in the identifying field, indicates that the standardization engine will use the corresponding locale element to determine which national domain to use to standardize the data. To specify a default domain, enter “Default” in this element.

locale

A domain code indicating which national domain to use to standardize data when the identifying field value in a transaction matches the corresponding value element. Supported locale codes for the Sun Match Engine are listed below.

• AU - for Australian data

• FR - for French data

• UK - for United Kingdom data

• US - for United States data

unstandardized-source-fields

A list of fields to be standardized. 

unstandardized-source-field-name

A field to be standardized. If you define more than one source field in the same standardization unit, the fields are concatenated during standardization with a pipe (|) between lines (for the Sun Match Engine). 

standardization-targets

A list of fields in which the standardized data from the source fields is stored. 

target-mapping

The configuration information for one destination field in which standardized data from the source field will be stored. One source field will likely have several destination fields. 

standardized-object-field-id

An abbreviation that identifies the destination field to the standardization engine. This must correspond to a field ID defined by the standardization engine being used. For more information, see Understanding the Sun Match Engine.

standardized-target-field-name

The ePath of the destination field in the object where the standardized value will be saved (for example, Person.Address[*].StreetName). 

phoneticize-fields

A list of fields to be phonetically encoded. 

phoneticize-field

The configuration information for each field to be phonetically encoded, including the encoder to use. 

unphoneticized-source-field-name

The ePath of the source field in the system object from which the value to phonetically encode will be retrieved (for example, Person.Address[*].StreetName). 

This can refer to the original field or to a standardized or normalized field.

phoneticized-target-field-name

The ePath of the field in which the phonetically encoded value will be saved in the system object. 

phoneticized-object-field-id

A field ID to identify the field to the phonetic encoder. This is not currently used with the Sun Match Engine. 

encoding-type

The phonetic encoder to use for this field. This must correspond to the encoding-type configured for the desired encoder in the PhoneticEncodersConfig element.

MatchingConfig

The configuration information for the match string (that is, the fields that are included in the data string sent to the match engine and against which weighting is performed). The attributes of the MatchingConfig element define the module name and Java class, and their default values should not be changed.

match-system-object

The configuration and field definitions for the match string. 

object-name

The name of the object containing the fields in the match string. If you specify the parent object, you can specify fields from the parent and any child object in the match string. 

match-columns

A list of fields in the match string. This element contains multiple match-column elements.

match-column

The configuration information for one field in the match string. You will use multiple match-column elements.

column-name

The fully qualified field name that defines the location of each field on which to match (for example, Enterprise.SystemSBR.Person.Address.City). 

match-type

The type of matching performed on the specified field. This is an ID that is specific to the match engine and identifies the field to the match engine. This value must correspond to a match type defined for the match engine. 

match-order

An integer specifying the order in which the field appears in the match string. This element is optional. If no order is specified, matching is performed in the order in which the fields are listed. 

MEFAConfig

The configuration information for the components of the matching service. The MEFAConfig attributes (module-name and parser-class) define the module name and Java class, and their default values should not be changed. You should only change the names of the component classes in this section if you created a corresponding custom component.

block-picker

The configuration information for the Java class that chooses which block of criteria defined for the blocking query to use for each match pass. 

class-name

The name of the block picker Java class.  

pass-controller

The configuration information for the Java class that determines whether the blocking query should continue performing match passes after each match pass is complete. 

class-name

The name of the pass controller Java class.  

standardizer-api

The configuration information for the standardization engine to use. 

class-name

The name of the standardizer API Java class. 

standardizer-config

The configuration information for the Java class that provides configuration information to the standardization engine. 

class-name

The name of the standardizer configuration Java class. 

matcher-api

The configuration information for the match engine to use. 

class-name

The name of the match engine API Java class. 

matcher-config

The configuration information for the Java class that provides configuration information to the match engine. 

class-name

The name of the match engine configuration Java class. 

PhoneticEncodersConfig

The configuration information for the phonetic encoders used by the master index application. The attributes (module-name and parser-class) define the module name and Java class. The default values should not be changed.

encoder

A list of phonetic encoders used by the standardization engine. 

encoding-type

The name of the phonetic encoder, such as NYSIIS, Soundex, or Metaphone. 

encoder-implementation-class

The fully qualified name of the Java class that determines the behavior of the phonetic encoder. The following default classes are defined for the Sun Match Engine. 

• com.stc.eindex.phonetic.impl.Nysiis

• com.stc.eindex.phonetic.impl.Soundex

• com.stc.eindex.phonetic.impl.Metaphone

• com.stc.eindex.phonetic.impl.DoubleMetaphone

• com.stc.eindex.phonetic.impl.RefinedSoundex

• com.stc.eindex.phonetic.impl.SoundexFR

<StandardizationConfig module-name="Standardization" parser-class=
"com.stc.eindex.configurator.impl.standardization.StandardizationConfiguration">
   <standardize-system-object>
      <system-object-name>Person</system-object-name>
      <structures-to-normalize>
         <group standardization-type="PersonName" domain-selector=
          ”com.stc.eindex.matching.impl.SingleDomainSelectorUS">
            <unnormalized-source-fields>
               <source-mapping>
                  <unnormalized-source-field-name>
                   Person.Alias[*].FirstName
                  </unnormalized-source-field-name>
                  <standardized-object-field-id>FirstName
                  </standardized-object-field-id>
               </source-mapping>
               <source-mapping>
                  <unnormalized-source-field-name>
                   Person.Alias[*].LastName
                  </unnormalized-source-field-name>
                  <standardized-object-field-id>LastName
                  </standardized-object-field-id>
               </source-mapping>
            </unnormalized-source-fields>
            <normalization-targets>
               <target-mapping>
                  <standardized-object-field-id>FirstName
                  </standardized-object-field-id>
                  <standardized-target-field-name>
                     Person.Alias[*].StdFirstName
                  </standardized-target-field-name>
               </target-mapping>
               <target-mapping>
                  <standardized-object-field-id>LastName
                  </standardized-object-field-id>
                  <standardized-target-field-name>
                     Person.Alias[*].StdLastName
                  </standardized-target-field-name>
               </target-mapping>
            </normalization-targets>
         </group>
         <group standardization-type="PersonName" domain-selector=
           "com.stc.eindex.matching.impl.SingleDomainSelectorUS”>
            <unnormalized-source-fields>
               <source-mapping>
                  <unnormalized-source-field-name>Person.FirstName
                  </unnormalized-source-field-name>
                  <standardized-object-field-id>FirstName
                  </standardized-object-field-id>
               </source-mapping>
               <source-mapping>
                  <unnormalized-source-field-name>Person.LastName
                  </unnormalized-source-field-name>
                  <standardized-object-field-id>LastName
                  </standardized-object-field-id>
               </source-mapping>
            </unnormalized-source-fields>
            <normalization-targets>
               <target-mapping>
                  <standardized-object-field-id>FirstName
                  </standardized-object-field-id>
                  <standardized-target-field-name>Person.StdFirstName
                  </standardized-target-field-name>
               </target-mapping>
               <target-mapping>
                  <standardized-object-field-id>LastName
                  </standardized-object-field-id>
                  <standardized-target-field-name>Person.StdLastName
                  </standardized-target-field-name>
               </target-mapping>
            </normalization-targets>
         </group>
      </structures-to-normalize>
      <free-form-texts-to-standardize>
         <group standardization-type="Address" domain-selector=
          "com.stc.eindex.matching.impl.MultiDomainSelector">
            <locale-field-name>Person.Country</locale-field-name>
            <locale-maps>
               <locale-codes>
                  <value>Default</value>
                  <locale>US</locale>
               </locale-codes>
            </locale-maps>
            <unstandardized-source-fields>
               <unstandardized-source-field-name>
                Person.Address[*].AddressLine1
               </unstandardized-source-field-name>
               <unstandardized-source-field-name>
                Person.Address[*].AddressLine2
               </unstandardized-source-field-name>
            </unstandardized-source-fields>
            <standardization-targets>
               <target-mapping>
                  <standardized-object-field-id>HouseNumber
                  </standardized-object-field-id>
                  <standardized-target-field-name>
                   Person.Address[*].HouseNumber
                  </standardized-target-field-name>
               </target-mapping>
               <target-mapping>
                  <standardized-object-field-id>MatchStreetName
                  </standardized-object-field-id>
                  <standardized-target-field-name>
                   Person.Address[*].StreetName
                  </standardized-target-field-name>
               </target-mapping>
               <target-mapping>
                  <standardized-object-field-id>
                   StreetNamePrefDirection
                  </standardized-object-field-id>
                  <standardized-target-field-name>
                   Person.Address[*].StreetDir
                  </standardized-target-field-name>
               </target-mapping>
               <target-mapping>
                  <standardized-object-field-id>StreetNameSufType
                  </standardized-object-field-id>
                  <standardized-target-field-name>
                   Person.Address[*].StreetType
                  </standardized-target-field-name>
               </target-mapping>
            </standardization-targets>
         </group>
      </free-form-texts-to-standardize>
      <phoneticize-fields>
         <phoneticize-field>
            <unphoneticized-source-field-name>Person.FirstName_Std
            </unphoneticized-source-field-name>
            <phoneticized-target-field-name>Person.FirstName_Phon
            </phoneticized-target-field-name>
            <encoding-type>Soundex</encoding-type>
         </phoneticize-field>
         <phoneticize-field>
            <unphoneticized-source-field-name>Person.LastName_Std
            </unphoneticized-source-field-name>
            <phoneticized-target-field-name>Person.LastName_Phon
            </phoneticized-target-field-name>
            <encoding-type>NYSIIS</encoding-type>
         </phoneticize-field>
         <phoneticize-field>
            <unphoneticized-source-field-name>
             Person.Address[*].StreetName
            </unphoneticized-source-field-name>
            <phoneticized-target-field-name>
             Person.Address[*].StreetNamePhoneticCode
            </phoneticized-target-field-name>
            <encoding-type>NYSIIS</encoding-type>
         </phoneticize-field>
      </phoneticize-fields>
   </standardize-system-object>
</StandardizationConfig>
<MatchingConfig module-name="Matching" parser-class=
 "com.stc.eindex.configurator.impl.matching.MatchingConfiguration">
   <match-system-object>
      <object-name>Person</object-name>
      <match-columns>
         <match-column>
           <column-name>Enterprise.SystemSBR.Person.StdFirstName
           </column-name>
           <match-type>FirstName</match-type>
         </match-column>
         <match-column>
           <column-name>Enterprise.SystemSBR.Person.StdLastName
           </column-name>
           <match-type>LastName</match-type>
         </match-column>
         <match-column>
           <column-name>Enterprise.SystemSBR.Person.DOB</column-name>
           <match-type>DOB</match-type>
         </match-column>
      </match-columns>
   </match-system-object>
</MatchingConfig>
<MEFAConfig module-name="MEFA" parser-class=
 "com.stc.eindex.configurator.impl.MEFAConfiguration">
   <block-picker>
      <class-name>com.stc.eindex.matching.impl.PickAllBlocksAtOnce
      </class-name>
   </block-picker>
   <pass-controller>
      <class-name>com.stc.eindex.matching.impl.PassAllBlocks
      </class-name>
   </pass-controller>
      <class-name>
       com.stc.eindex.matching.adapter.SbmeStandardizerAdapter
      </class-name>
   </standardizer-api>
   <standardizer-config>
      <class-name>
       com.stc.eindex.matching.adapter.SbmeStandardizerAdapterConfig
      </class-name>
   </standardizer-config>
   <matcher-api>
      <class-name>com.stc.eindex.matching.adapter.SbmeMatcherAdapter
      </class-name>
   </matcher-api>
   <matcher-config>
      <class-name>
       com.stc.eindex.matching.adapter.SbmeMatcherAdapterConfig
      </class-name>
   </matcher-config>
</MEFAConfig>
<PhoneticEncodersConfig module-name="PhoneticEncoders" parser-class=
 "com.stc.eindex.configurator.impl.PhoneticEncodersConfig">
   <encoder>
      <encoding-type>NYSIIS</encoding-type>
      <encoder-implementation-class>
       com.stc.eindex.phonetic.impl.Nysiis
      </encoder-implementation-class>
   </encoder>
   <encoder>
      <encoding-type>Soundex</encoding-type>
      <encoder-implementation-class>
       com.stc.eindex.phonetic.impl.Soundex
      </encoder-implementation-class>
   </encoder>
</PhoneticEncodersConfig>

SurvivorHelperConfig

The configuration of the overall survivor strategy. The SurvivorHelperConfig attributes (module-name and parser-class) define the module name and Java class, and their default values should not be changed.

helper-class

The Java class that determines how to retrieve values from system records and to set them in the SBR. The default class uses the ePath notation to retrieve and set the values. 

default-survivor-strategy

The configuration information for the survivor strategy to use as the default. You can define multiple survivor strategies and use different strategy combinations for the candidate fields. Any field that is not assigned a specific survivor strategy in the candidate-definitions list uses the default survivor strategy specified here.

strategy-class

The Java class name of the default strategy. 

parameters

A list of optional parameters for the default survivor strategy. 

parameter

A parameter for the default survivor strategy. The default parameter points to another section in the Best Record file that configures the default class. There can be multiple parameter elements.

description

An optional element that briefly describes the parameter. 

parameter-name

The name of the parameter. 

• For the DefaultSurvivorStrategy, this value is preferredSystem.

• For the WeightedSurvivorStrategy, this value is ConfigurationModuleName.

• For the UnionSurvivorStrategy. this is not used.

parameter-type

The Java data type for the parameter value. For both the DefaultSurvivorStrategy and the WeightedSurvivorStrategy, this value is java.lang.String.

parameter-value

The value of the named parameter. 

• For the DefaultSurvivorStrategy, this is the processing code of the source system from which the SBR field value is retrieved.

• For the WeightedSurvivorStrategy, this is the name of the module-name element that defines the weighted calculator to use as the default strategy (by default, WeightedSurvivorCalculator).

candidate-definitions

The configuration information for the fields to be included in the SBR. For any field that does not use the default survivor strategy, an alternate strategy is defined. All field that are included in the SBR must be listed here. 

candidate-field/name

The qualified field name for a field in the SBR (for more information about field notations, see Master Index Field Notations).

description

A short description of the candidate field (this element is optional). 

system-fields

A field (other than the candidate field) that is evaluated to determine the value for the SBR. One example of this would be to evaluate the last update date of the system records to determine which value is most recent. This element is not currently used by any of the standard survivor strategies provided with the master index application, but might be useful when defining custom strategies. 

field-name

The name of the field to use to determine the value for the SBR. 

survivor-strategy

An alternate survivor strategy to use for the given field in place of the default strategy defined in the default-survivor-strategy element. If a strategy is not specifically defined for a field, the default strategy is used for that field.

strategy-class

The name of the Java class to use for the alternate survivor strategy. 

WeightedCalculator

The configuration of the weighted calculator. By default, this is the strategy specified as the default strategy in the default-survivor-strategy element. The WeightedCalculator attributes (module-name and parser-class) define the module name and Java class, and their default values should not be changed unless you create a custom class.

default-parameters

The configuration information for the default weighted calculator logic for all fields except those whose logic is defined in the candidate-field element below.

parameter

A parameter for the default logic of the weighted calculator. 

quality

The type of weighted calculation to perform. You can specify any of the following: 

• SourceSystem

• SystemAgreement

• MostRecentModified

For more information about these qualities, see Weighted Calculator.

preference

The preferred value for the specified quality. This element is only used for the SourceSystem quality and must be a source system code.

utility

A value that indicates the reliability of the specified quality for determining the best field value for the SBR. You define the scale for the utility values. 

candidate-field

A field for which you want to use custom logic for the weighted calculator. The logic you specify here overrides the logic defined in the default-parameters section, but only for the fields specified. Each candidate field is identified by a name attribute and defines the survivor strategies for one field.

candidate-field/name

The name of the candidate field for which you want to define override logic. 

parameter

A parameter configuring the weighted calculator for the candidate field. You can define multiple parameters for each candidate field. 

quality

The type of weighted calculation to perform. You can specify any of the following: 

• SourceSystem

• SystemAgreement

• MostRecentModified

  For more information about these qualities, see Weighted Calculator.

preference

The preferred value for the specified quality. This element is only used for the SourceSystem quality and the preference must be a source system code.

utility

A value that indicates the reliability of the specified quality for determining the best field value for the SBR. You define the scale for the utility values. 

UpdateManagerConfig

The configuration information for the Update Manager. This section defines a list of Java classes to manage custom processing for different types of transactions. You can create the custom classes in the Custom Plug-ins function of the master index project and then specify those classes here. The UpdateManagerConfig attributes (module-name and parser-class) define the module name and Java class, and their default values should not be changed.

EnterpriseMergePolicy

A class that defines additional processing to perform when two enterprise objects are merged. 

EnterpriseUnmergePolicy

A class that defines additional processing to perform when two enterprise objects are unmerged. 

EnterpriseUpdatePolicy

A class that defines additional processing to perform when a record is updated. 

EnterpriseCreatePolicy

A class that defines additional processing to perform when a new record is created. 

SystemMergePolicy

A class that defines additional processing to perform when two system objects are merged. 

SystemUnmergePolicy

A class that defines additional processing to perform when system objects are unmerged. 

UndoAssumeMatchPolicy

A class that defines additional processing to perform when an assumed match transaction is reversed. 

SkipUpdateIfNoChange

An indicator of whether the update policies are carried out if no changes are made to the existing record. Specify “true” to prevent the update policies from being performed when no changes are made to an existing record. 

<SurvivorHelperConfig module-name="SurvivorHelper" 
 parser-class="com.stc.eindex.configurator.impl.SurvivorHelperConfig">
   <helper-class>com.stc.eindex.survivor.impl.DefaultSurvivorHelper
   </helper-class>
   <default-survivor-strategy>
      <strategy-class>
       com.stc.eindex.survivor.impl.WeightedSurvivorStrategy
      </strategy-class>
      <parameters>
         <parameter>
            <parameter-name>ConfigurationModuleName</parameter-name>
            <parameter-type>java.lang.String</parameter-type>
            <parameter-value>WeightedSurvivorCalculator
            </parameter-value>
         </parameter>
      </parameters>
   </default-survivor-strategy>
   <candidate-definitions>
      <candidate-field name="Person.LastName">
         <system-fields>
            <field-name>Person.SSN</field-name>
         </system-fields>
      </candidate-field>
      <candidate-field name="Person.FirstName"/>
      <candidate-field name="Person.MiddleName"/>
      <candidate-field name="Person.DOB"/>
      <candidate-field name="Person.Gender"/>
      <candidate-field name="Person.SSN"/>
      <candidate-field name="Person.FnamePhoneticCode"/>
      <candidate-field name="Person.LnamePhoneticCode"/>
      <candidate-field name="Person.StdFirstName"/>
      <candidate-field name="Person.StdLastName"/>
      <candidate-field name="Person.Alias[*].*">
         <survivor-strategy>
            <strategy-class>
             com.stc.eindex.survivor.impl.UnionSurvivorStrategy
            </strategy-class>
         </survivor-strategy>
      </candidate-field>
   </candidate-definitions>
</SurvivorHelperConfig>
<WeightedCalculator module-name="WeightedSurvivorCalculator"
 parser-class="com.stc.eindex.configurator.impl.WeightedCalculatorConfig">
   <candidate-field name="Person.SSN">
      <parameter>
         <quality>SourceSystem</quality>
         <preference>SBYN</preference>
         <utility>100.0</utility>
      </parameter>
      <parameter>
         <quality>MostRecentModified</quality>
         <utility>75.0</utility>
      </parameter>
   </candidate-field>
   <default-parameters>
      <parameter>
         <quality>MostRecentModified</quality>
         <utility>80.0</utility>
      </parameter>
      <parameter>
         <quality>SourceSystem</quality>
         <preference>SBYN</preference>
         <utility>100.0</utility>
      </parameter>
   </default-parameters>
</WeightedCalculator>
<UpdateManagerConfig module-name="UpdateManager" 
 parser-class="com.stc.eindex.configurator.impl.UpdateManagerConfig">
   <EnterpriseMergePolicy>com.stc.eindex.user.CustomMergePolicy
   </EnterpriseMergePolicy>
   <EnterpriseUnmergePolicy>com.stc.eindex.user.CustomUnmergePolicy
   </EnterpriseUnmergePolicy>
   <EnterpriseUpdatePolicy>com.stc.eindex.user.CustomUpdatePolicy
   </EnterpriseUpdatePolicy>
   <EnterpriseCreatePolicy>com.stc.eindex.user.CustomCreatePolicy
   </EnterpriseCreatePolicy>
   <SystemMergePolicy>com.stc.eindex.user.CustomSystemMergePolicy
   </SystemMergePolicy>
   <SystemUnmergePolicy>com.stc.eindex.user.CustomSystemUnmergePolicy
   </SystemUnmergePolicy>
   <UndoAssumeMatchPolicy>com.stc.eindex.user.CustomUndoMatchPolicy
   </UndoAssumeMatchPolicy>
   <SkipUpdateIfNoChange>true</SkipUpdateIfNoChange>
</UpdateManagerConfig>

<default-parameters>
   <parameter>
      <quality>SourceSystem</quality>
      <preference>SAP</preference>
      <utility>80.0</utility>
   </parameter>
   <parameter>
      <quality>MostRecentModified</quality>
      <utility>70.0</utility>
   </parameter>
   <parameter>
      <quality>SourceSystem</quality>
      <preference>CDW</preference>
      <utility>30.0</utility>
   </parameter>
</default-parameters>

rules

The configuration information for the validation rules. 

rule

The configuration information for a specific validation rule in a rules list.

rule/name

A rule attribute that specifies a name for the validation rule.

rule/object-name

A rule attribute that specifies the name of the class that defines the object to which the validation rule is applied, such as SystemObject or ParentNameObject (where ParentName is the name of the parent object in the Object Definition).

rule/class

A rule attribute that specifies the complete path of the Java class containing the validation rule.

<ValidationConfig module-name="Validation" 
parser-class= "com.stc.eindex.configurator.impl.validation.ValidationConfiguration"
   <rules>
      <rule name="validate-auxiliary-id" object-name="PersonObject"
       class="com.stc.eindex.user.AuxiliaryId"/>
      <rule name="validate-birth-date" object-name="PersonObject"
       class="com.stc.eindex.user.BirthDate"/>
   </rules>
</ValidationConfig>

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.

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.

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-nameMasterController, 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-nameCodeLookup.

usercode-jndi-name

The JNDI name for the user code validator (used for non-unique IDs). The default name is ejb/app-nameUserCodeLookup.

report-generator-jndi-name

The JNDI name for the EDM report generator. The default name is ejb/app-nameReportGenerator.

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. 

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-id1 or local-id2 (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.

<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>

node{.node{”[”qualifier’]’}+}+.field

Enterprise
   SystemObject - A 111
      Person
         FirstName
         LastName
         -Address
            AddressType = Home
            Street = 800 Royal Oaks Dr.
            City = Monrovia
            State = CA
            PostalCode = 91016
         -Address
            AddressType = Office
            Street = 181 2nd Ave..
            City = Monrovia
            State = CA
            PostalCode = 91016
         -Address
            AddressType = Billing
            Street = 100 Grand Avenue
            City = El Segundo
            State = CA
            PostalCode = 90245

Person
   FirstName
   LastName
   DateOfBirth
   Gender
   -Address
      AddressType
      StreetAddress
      Street
      City
      State
      PostalCode
   -Phone
      PhoneType
      PhoneNumber

Person
   FirstName
   LastName
   DateOfBirth
   Gender
   -Address
      AddressType
      StreetAddress
      Street
      City
      State
      PostalCode
   -Phone
      PhoneType
      PhoneNumber