Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS Master Index Configuration Guide Java CAPS Documentation |
Oracle Java CAPS Master Index Configuration Guide
Master Index Configuration Overview
About the Master Index Configuration Files
Modifying the Master Index XML Files Directly
Using the Master Index Master Index Configuration Editor
Match Configuration File (matchConfigFile.cfg)
Maintaining Version Control in the Master Index Configuration Files
Copying, Cutting, and Pasting Files
Configuring the Master Index Object Structure
Adding an Object to the Master Index Object Structure
To Add an Undefined Object (Configuration Editor)
To Add a Predefined Object (Configuration Editor)
To Add an Undefined Object (XML editor)
Modifying an Object's Name In the Master Index Object Definition
To Modify an Object's Name (Configuration Editor)
To Modify an Object's Name (XML Editor)
Deleting an Object From the Master Index Object Structure
To Delete an Object (Configuration Editor)
To Delete an Object (XML Editor)
Adding a Field to the Master Index Object Structure
To Add a Field (Configuration Editor)
Deleting a Field from the Master Index Object Structure
To Delete a Field (Configuration Editor)
To Delete a Field (XML Editor)
Modifying Master Field Properties
To Modify Field Properties (Configuration Editor)
To Modify Field Properties (XML Editor)
Defining Relationships Between Master Index Objects
To Define Object Relationships (XML Editor)
Master Index Field Properties and Name Restrictions
Master Index Field Name Restrictions
Master Index Configuration Editor Field Properties
Master Index Field Property Elements
Creating a Master Index Basic Query
To Create a Basic Query (Configuration Editor)
To Create a Basic Query (XML Editor)
Master Index Query Builder Dialog Box Fields and XML Elements
Creating Master Index Blocking Queries
To Create a Blocking Query (Configuration Editor)
To Create a Blocking Query (XML Editor)
Master Index Query Block Fields and XML Elements
Modifying Master Index Queries
Modifying a Master Index Query
To Modify a Basic Query (Configuration Editor)
To Modify a Query (XML Editor)
Adding a Query Block to a Master Index Query
To Add a Query Block (Configuration Editor)
To Add a Query Block (XML Editor)
Modifying a Query Block for a Master Index Query
To Modify a Query Block (Configuration Editor)
To Modify a Query Block (XML Editor)
Deleting a Query Block From a Master Index Query
To Delete a Query Block (Configuration Editor)
To Delete a Query Block (XML Editor)
To Delete a Query (Configuration Editor)
Configuring Master Index Processing Options
Specifying Master Index Custom Logic Classes
To Specify Custom Logic for External System Messages
To Specify Custom Logic for the Master Index Data Manager
Specifying the Master Index Update Mode
To Specify Potential Duplicates be Reevaluated at Each Update
To Specify Potential Duplicates not be Reevaluated at Each Update
Configuring Master Index Merged Record Updates
To Allow Merged Record Updates
To Prevent Merged Record Updates
Specifying the Master Index Blocking Query for Matching
To Specify the Blocking Query for Matching
Setting Master Index Blocking Query Options
Defining Master Index Transactional Support
To Configure the Master Index for Local Transactions
To Configure the Master Index to Distributed Transactions Across Applications
To Configure the Master Index for Distributed Transactions Within the Master Index Application Only
Configuring Matching Parameters
Specifying the Master Index Decision Maker Class
To Specify the Decision Maker Class
Defining How to Handle Multiple Assumed Matches (OneExactMatch)
To Create Potential Duplicates When Multiple Records Match
To Match the Highest Weighted Records When Multiple Records Match
Specifying Whether Same System Matches are Allowed (SameSystemMatch)
To Allow Same System Records to be Automatically Merged
To Prevent Same System Records From Being Automatically Merged
Specifying the Master Index Duplicate Threshold
To Specify the Duplicate Threshold (Configuration Editor)
To Specify the Duplicate Threshold (XML Editor)
Specifying the Master Index Match Threshold
To Specify the Match Threshold (Configuration Editor)
To Specify the Match Threshold (XML Editor)
Adding and Deleting Master Index Decision Maker Parameters
To Add a New Decision Maker Parameter
To Delete a Decision Maker Parameter
Configuring Master Index EUIDs
Specifying the Master Index EUID Generator Class
To Specify the EUID Generator Class
Specifying the Master Index EUID Length
Specifying a Master Index Checksum Length
Specifying the Master Index Chunk Size
Adding and Deleting Master Index EUID Generator Parameters
To Add EUID Generator Parameters
To Delete EUID Generator Parameters
Defining Master Index Normalization Rules
Defining a Master Index Field to be Normalized
To Define a Field to be Normalized (Configuration Editor)
To Define a Field to be Normalized (XML Editor)
Master Index Normalization and Standardization Structure Properties
Master Index Variants Properties
Modifying a Master Index Normalization Definition
To Modify a Normalization Definition (Configuration Editor)
To Modify a Normalization Structure (XML Editor)
Deleting a Master Index Normalization Definition
To Delete a Normalization Definition
To Delete a Normalization Structure
Defining Master Index Standardization Rules
Defining Master Index Fields to be Standardized
To Define Fields to be Standardized (Configuration Editor)
To Define Fields to be Standardized (XML Editor)
Master Index Standardization Source and Target Field Elements
Modifying a Master Index Standardization Definition
To Modify a Standardization Definition (Configuration Editor)
To Modify a Standardization Definition (XML Editor)
Deleting a Master Index Standardization Definition
To Delete a Standardization Definition (Configuration Editor)
To Delete a Standardization Definition (Configuration Editor)
Defining Phonetic Encoding for the Master Index
Defining Master Index Fields for Phonetic Encoding
To Define a Field for Phonetic Encoding (Configuration Editor)
To Define a Field for Phonetic Encoding (XML Editor)
Master Index Phonetic Encoding Fields and Elements
Modifying a Master Index Phonetic Encoding Definition
To Modify a Phonetic Encoding Definition (Configuration Editor)
To Modify a Phonetic Encoding Definition (XML Editor)
Deleting a Master Index Phonetic Encoding Definition
To Delete a Phonetic Encoding Definition (Configuration Editor)
To Delete a Phonetic Encoding Definition (XML Editor)
Defining a Master Index Phonetic Encoder
To Define a Phonetic Encoder (Configuration Editor)
To Define a Phonetic Encoder (XML Editor)
Master Index Encoder Elements and Types
Modifying a Master Index Phonetic Encoder
To Modify a Phonetic Encoder (Configuration Editor)
To Modify a Phonetic Encoder (XML Editor)
Deleting a Master Index Phonetic Encoder
To Delete a Phonetic Encoder (Configuration Editor)
To Delete a Phonetic Encoder (XML Editor)
Defining the Master Index Match String
Creating the Master Index Match String
To Create the Match String (Configuration Editor)
To Create the Match String (XML Editor)
Modifying the Master Index Match String
To Modify the Match String (Configuration Editor)
To Modify the Match String (XML Editor)
Defining how Master Index Query Blocks are Processed
To Specify the Pass Controller Class
Defining the Master Index Survivor Calculator
Specifying the Master Index Survivor Helper
To Specify the Survivor Helper
Specifying a Master Index Default Survivor Strategy
To Specify a Default Survivor Strategy
Configuring the Default Survivor Strategy
Master Index Default Survivor Strategy Parameter Elements
Defining the Master Index Single Best Record Structure
Defining a Master Index Survivor Strategy for a Field or Object
To Define a Survivor Strategy for a Field
Defining Master Index Custom Weighted Strategies
Defining Custom Weighted Strategies
Configuring Weighted Strategies
Modifying Weighted Calculator Parameters
Deleting Weighted Calculator Parameters
Master Index Weighted Calculator Parameter Elements
Filtering Default Values From Master Index Processes
To Filter Default Values From the SBR, Blocking Query, or Match Process
Configuring Master Index Update Policies
Defining Master Index Update Policies
Setting the Master Index Update Policy Flag
Defining Custom Field Validations for the Master Index
To Implement a Validation Rule
Specifying a Match Engine for the Master Index
Configuring the Comparison Functions for a Master Index Application
To Configure the Comparison Functions (Configuration Editor)
To Configure the Comparison Functions (Text Editor)
Match Comparator Configuration Properties for Oracle Java CAPS Master Index
Importing Custom Comparison Functions
To Import a Comparison Function
Deleting a Custom Comparison Function
To Delete a Custom Comparison Function
Configuring the Standardization Engine
Specifying a Standardization Engine for the Master Index
To Specify the Standardization Engine
Modifying Master Index Standardization Files
To Modify Standardization Data Configuration Files
Importing Standardization Data Types and Variants
To Import a Data Type or Variant
Deleting a Standardization Variant or Data Type
To Delete a Variant or Data Type
Configuring the Master Index MIDM Appearance
Deleting Objects From the MIDM
MIDM Field Configuration Elements
To Remove a Field From the MIDM
Modifying MIDM Field Display Options
To Modify a Field's Display Options
Specifying a Drop-Down List for an MIDM Field
Specifying an MIDM Field's Length and Format
To Modify a Field's Length and Format
Modifying an MIDM Field's Data Type
Defining Key Fields for an Object
Masking Field Values on the MIDM
To Mask Field Values on the MIDM
Defining MIDM Object Relationships
Configuring the Master Index MIDM Pages
Specifying the Initial View for the MIDM
Configuring the MIDM Duplicate Records Page
Configuring Duplicate Records Display Options
Configuring Duplicate Records Search Pages
Configuring the Duplicate Records Results List
Duplicate Records Page Configuration Elements
Duplicate Records Search Page Elements
Duplicate Records Search Results List Elements
Configuring the MIDM Record Details Page
To Configure Record Details Display Options
Creating Search Pages on the Record Details Page
Step 1: Define the Search Page
Step 2: Define the Search Fields
Step 3: Specify Search Options
Record Details Search Page Definition Elements
Record Details Search Field Definition Elements
Record Details Search Option Elements
Modifying a Search Page on the Record Details Page
Modifying a Search Page Definition
Modifying Record Details Search Page Options
Configuring the MIDM Assumed Matches Page
To Configure the Assumed Matches Page
Configuring the MIDM Transactions Page
To Configure the Transactions Page
Configuring the MIDM Reports Page
Configuring the Reports Page Definition
Configuring Production Reports
Production Reports Definition Elements
Activity Reports Definition Elements
Activity Reports Page Definition Elements
Activity Reports Search Elements
Activity Reports Results Elements
Configuring the MIDM Source Record Page
Configuring the Source Record Page Definition
Configuring the Tabbed Pages on the Source Record Page
Configuring Master Index MIDM Implementation Information
Specifying the Master Controller JNDI Class
To Specify the Master Controller JNDI Class
Specifying the Master Index Report Generator JNDI Class
To Specify the Report Generator JNDI Class
Specifying Master Index Validation Services
To Specify the Validation Service
Setting Master Index Debug Options
You can configure certain pages that appear on the MIDM by modifying the midm.xml. Each page on the MIDM is configured separately, though many contain the same XML elements and attributes. For the Record Details page, you can configure and create search pages and search results lists. If you add a new query to query.xml and you want to access that query from the MIDM, you need to create a new search page for the query on the Record Details page. The Dashboard page cannot be configured.
Perform any of the following actions to configure the pages of the MIDM.
By default, the Record Details page appears when a user logs in to the Master Index Data Manager. You can specify any of the other tabbed pages as the initial view. Each page on the MIDM is identified by a screen ID in midm.xml, which is an integer defined in the screen-id element for each page. Use this ID to specify which page to display first when a user logs in.
The file opens in the NetBeans XML editor.
The Duplicate Records page allows you to search for potential duplicate records, view a results list, and then view a comparison of the records you select. It also provides features to resolve or merge the potential duplicates in question. You can configure several aspects of the Duplicate Records page, including display options, search pages, and the results list.
The following topics provide instructions for each type of configuration:
You can configure certain display options for the Duplicate Records page, such as the name of the tabbed heading and the order in which the tab appears on the MIDM. Below is a sample of the display option elements for the Duplicate Records page.
<duplicate-records> <root-object>Person</root-object> <tab-name>Duplicate Records</tab-name> <screen-id>3</screen-id> <display-order>1</display-order> ... </duplicate-records>
You should never need to modify the root-object or screen-id element for the Duplicate Records page.
The file opens in the NetBeans XML editor.
Note - You might need to renumber the remaining tabs to keep the numbering sequential.
For the Duplicate Records search pages, you can configure the names of the searches that can be performed, the fields to use as search criteria (within a limited set of system fields), and instructions for performing a search. Below is a sample of the search page configuration for the Duplicate Records page.
<duplicate-records> ... <simple-search-page> <screen-title>Advanced Search</screen-title> <search-result-id>0</search-result-id> <search-screen-order>0</search-screen-order> <show-euid>true</show-euid> <show-lid>true</show-lid> <show-status>true</show-status> <show-create-date>true</show-create-date> <show-create-time>true</show-create-time> <instruction></instruction> <field-group/> </simple-search-page> ... </duplicate-records>
The file opens in the NetBeans XML editor.
For the Duplicate Records results list, you can configure the number of results to display at one time, the total number of results a search can return, and the fields that appear in the results list. Below is a sample results list configuration for the Duplicate Records page.
<duplicate-records> ... <search-result-pages> <search-result-list-page> <search-result-id>0</search-result-id> <item-per-page>10</item-per-page> <max-result-size>100</max-result-size> <field-group> <description></description> <field-ref>Person.FirstName</field-ref> <field-ref>Person.LastName</field-ref> <field-ref>Person.SSN</field-ref> <field-ref>Person.DOB</field-ref> <field-ref>Person.Gender</field-ref> </field-group> </search-result-list-page> </search-result-pages> </duplicate-records>
The file opens in the NetBeans XML editor.
The following two tables describe the configuration elements in midm.xml for the Duplicate Records search and results pages. The same elements are also used for the Source Record View/Edit page.
The following table lists and describes the configurable elements for the Duplicate Records and Source Record search pages.
Table 1 Duplicate Records Search Page Configuration
|
The following table lists and describes the configurable elements for the Duplicate Records search results list.
Table 2 Duplicate Records Search Results Configuration
|
You can configure certain display options for the Record Details page, such as the name of the tabbed heading and the order in which the tab appears on the MIDM. You can also create, modify, and delete search pages and search results lists. Search configuration is described in Creating Search Pages on the Record Details Page and Modifying a Search Page on the Record Details Page.
Below is a sample of the display option elements for the Record Details page.
<record-details> <root-object>Person</root-object> <tab-name>Record Details</tab-name> <screen-id>1</screen-id> <display-order>2</display-order> ... </duplicate-records>
You should never need to modify the root-object or screen-id element.
The file opens in the NetBeans XML editor.
Note - You might need to renumber the remaining tabs to keep the numbering sequential.
Several search pages are created by the Master Index Wizard based on the information you specify. You can create and customize new search pages for the Record Details page. Each search you define must use a query that is defined in query.xml.
Follow these steps to create a new search page:
The first step in creating a search page is to define certain properties for the appearance of the page, such as its name, whether to display the EUID or local ID field, and general instructions for the search.
Note - If either the EUID field or the local ID and system fields appear on a search page, any values entered into these fields take precedence over information entered into other search fields. For example, if an invalid EUID is entered but valid first and last names are entered, no results are returned due to the invalid EUID. The EUID field takes precedence over the local ID and system fields.
The file opens in the NetBeans XML editor.
Make sure the new element falls within the record-details element, but outside any existing simple-search-page elements. For example:
<record-details> <simple-search-page> ... </simple-search-page> <simple-search-page> </simple-search-page> </record-details>
For example:
<record-details> <simple-search-page> ... </simple-search-page> <simple-search-page> <screen-title>Address Search</screen-title> <search-result-id>1</search-result-id> <show-euid>true</show-euid> <show-lid>false</show-lid> <instruction>Enter address information below.</instruction> </simple-search-page> </record-details>
Once you define the search page, you need to specify the fields that appear on the page. Fields are specified in field groups, and each field group represents an area on the search page. All fields specified for a field group appear in the area defined by that group. The label for the area is defined by the description of the field group.
For example:
<simple-search-page> <screen-title>Simple Person Search</screen-title> <search-result-id>2</search-result-id> <search-screen-order>1</search-screen-order> <show-euid>false</show-euid> <show-lid>false</show-lid> <field-group> </field-group> </simple-search-page>
For example:
<simple-search-page> .. <field-group> <description>Address</description> <field-ref>Address.AddressType</field-ref> <field-ref>Address.AddressLine1</field-ref> <field-ref>Address.AddressLine2</field-ref> <field-ref required=“true”>Address.City</field-ref> <field-ref>Address.State</field-ref> </field-group> </simple-search-page>
After you define the criteria fields for the MIDM search, you can specify certain options for the search, such as the types of available searches, whether each search is weighted, and whether the search allows wildcard characters.
Note - Wildcards should not be allowed for blocking queries or phonetic searches.
For example:
<simple-search-page> <screen-title>Simple Person Search</screen-title> <search-result-id>2</search-result-id> <search-screen-order>1</search-screen-order> <show-euid>false</show-euid> <show-lid>false</show-lid> <field-group> ... </field-group> <search-option> </search-option> </simple-search-page>
For example:
<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>
Note - If you define multiple search option elements, an option button (labelled by the value of the display-name element) appears on the search page for each search option.
The following table lists and describes the elements you can configure in midm.xml to define the search pages on the Record Details page.
|
The following table lists and describes the elements you can configure in midm.xml to define the fields for each search on the Record Details page.
|
The following table lists and describes the elements you can configure in midm.xml to define the attributes for each search on the MIDM, such as which query to use, whether the search results are weighted, and so on.
|
Once a search page is defined for the Record Details page, it can be modified as needed. Be sure to review the search pages automatically generated by the wizard to see if any further configuration is required. You can perform any of the following actions to customize existing search page elements.
Once a search page is defined for the Record Details page, you can modify the search page definition. The search page definition includes properties like the name of the page, the order of the search, the results list to use for the search, and so on.
The file opens in the NetBeans XML editor.
For example:
<simple-search-page> <screen-title>Customer Search</screen-title> <search-result-id>2</search-result-id> <search-screen-order>2</search-screen-order> <show-euid>true</show-euid> <show-lid>false</show-lid> <instruction>Enter the EUID below.</instruction> </simple-search-page>
Once field groups and fields are specified for a Record Details search page, you can modify the properties of the group and of the fields contained in a group. For more information about the elements that contain the search field configuration, see Record Details Search Field Definition Elements.
The file opens in the NetBeans XML editor.
Once search options are defined for a Record Details search page, you can modify those options if needed. For more information about the elements that define search options, see Record Details Search Option Elements.
The file opens in the NetBeans XML editor.
The Assumed Matches page allows you to search for assumed match records, view a results list, and then view the details for the record you select. You can also undo an assumed match if you think it was made in error. You can configure the name of the tabbed heading for the page, the display order, the number of records to return and display for a search, and the fields to display in the result list. The fields on the search page and in the results list are automatically generated and cannot be modified.
Below is a sample Assumed Matches page definition.
<assumed-matches> <root-object>Person</root-object> <tab-name>Assumed Matches</tab-name> <screen-id>4</screen-id> <display-order>3</display-order> <search-pages/> <search-result-pages> <search-result-list-page> <search-result-id>0</search-result-id> <item-per-page>10</item-per-page> <max-result-size>100</max-result-size> <field-group> <description></description> <field-ref>Person.FirstName</field-ref> <field-ref>Person.LastName</field-ref> <field-ref>Person.SSN</field-ref> <field-ref>Person.DOB</field-ref> <field-ref>Person.Gender</field-ref> <field-ref>Person.Address.AddressLine1</field-ref> <field-ref>Person.Address.AddressLine2</field-ref> </field-group> </search-result-list-page> </search-result-pages> </assumed-matches>
The file opens in the NetBeans XML editor.
Note - If you change the order of one tab, make sure to change the order of the remaining tabs so no tabs have an identical display order value.
For example:
<field-group> <field-ref>Person.FirstName</field-ref> <field-ref>Person.LastName</field-ref> <field-ref>Person.SSN</field-ref> <field-ref>Person.DOB</field-ref> </field-group>
The Transactions page allows you to search for transaction records, view a results list, and then view the changes for the record you select. You can configure the name of the tabbed heading for the page, the display order, and the number of records to return and to display in the results list. The fields on the search page and results list are automatically generated and cannot be modified with the exception of the EUID, system, and local ID.
Below is the default Transactions page definition.
<transactions> <root-object>Person</root-object> <tab-name>Transactions</tab-name> <screen-id>2</screen-id> <display-order>4</display-order> <search-pages> <simple-search-page> <show-euid>true</show-euid> <show-lid>true</show-lid> </simple-search-page> </search-pages> <search-result-pages> <search-result-list-page <search-result-id>0</search-result-id> <item-per-page>10</item-per-page> <max-result-size>100</max-result-size> <field-group/> </search-result-list-page> </search-result-pages> </transactions>
The file opens in the NetBeans XML editor.
Note - If you change the order of one tab, make sure to change the order of the remaining tabs so no tabs have an identical display order value.
Configuring the Reports page consists of configuring the page itself and configuring the individual reports. Production reports are each configured in the same way in their own sub-screen definition element. Activity reports are configured together in one sub-screen definition. The sub-screen definitions means there are a series of tabbed pages within the Reports page for each different type of report.
Perform any of the following tasks to configure the reports:
For the Reports page, you can configure the name of the tabbed heading for the page and the order in which the tab appears on the MIDM. The report configuration section defines the appearance of the Reports page, and is located within a set of reports tags near the end of the file. Following is a sample of the Reports page configuration elements.
<reports> <root-object>Person</root-object> <tab-name>Reports</tab-name> <screen-id>6</screen-id> <display-order>5</display-order> <search-pages/> <search-result-pages/>
The file opens in the NetBeans XML editor.
Note - You might need to renumber the remaining tabs to keep the numbering sequential.
Note - You might need to renumber the remaining tabs to keep the numbering sequential.
A sub-screen on the Reports page is defined for each of the production reports. Use these sections to configure each production report to display information as you want to view it. You can also specify which reports can be run from the MIDM. Following is an example of a report configuration stanza.
<subscreen> <enable>true</enable> <root-object>Person</root-object> <tab-name>Potential Duplicate Report</tab-name> <report-name>Potential Duplicate</report-name> <screen-id>0</screen-id> <display-order>5</display-order> <search-pages/> <search-result-pages> <search-result-list-page> <search-result-id>0</search-result-id> <item-per-page>10</item-per-page> <max-result-size>2000</max-result-size> <field-group> <description></description> <field-ref>Person.FirstName</field-ref> <field-ref>Person.LastName</field-ref> <field-ref>Person.SSN</field-ref> <field-ref>Person.DOB</field-ref> <field-ref>Person.Address.AddressLine1</field-ref> <field-ref>Person.Address.AddressLine2</field-ref> <field-ref>Person.Address.City</field-ref> </field-group> </search-result-list-page> </search-result-pages> </subscreen>
Perform the following steps for each production report.
The file opens in the NetBeans XML editor.
A sub-screen on the Reports page is defined for all of the activity reports. Use this sections to configure each activity report to display information as you want to view it. You can also specify which reports can be run from the MIDM. Following is an excerpt from the Activity report configuration stanza.
<subscreen> <enable>true</enable> <root-object>Person</root-object> <tab-name>Activity Report</tab-name> <report-name>Transaction Summary</report-name> <screen-id>5</screen-id> <display-order>4</display-order> <search-pages> <simple-search-page> <screen-title>Weekly Activity</screen-title> <report-name>Weekly Transaction Summary Report</report-name> <search-result-id>0</search-result-id> <search-screen-order>1</search-screen-order> <field-group/> </simple-search-page> ... </search-pages> <search-result-pages> <search-result-list-page> <search-result-id>0</search-result-id> <item-per-page>10</item-per-page> <max-result-size>2000</max-result-size> <field-group/> </search-result-list-page> </search-result-pages> </subscreen>
Perform the following steps for each production and activity report.
The file opens in the NetBeans XML editor.
The following table lists and describes the elements you can configure in midm.xml to define the production reports.
|
The following tables list and describe the elements you can configure for the activity reports in midm.xml.
The following table lists and describes the elements you can configure in midm.xml to define the Activity Reports page.
|
The following table lists and describes the elements you can configure in midm.xml to define each activity report search.
|
The following table lists and describes the elements you can configure in midm.xml to define each activity report search result.
|
The Source Record page is where anMIDM user adds new records to the master index database and performs actions against a source record rather than an enterprise record. This page includes sub-screen configurations, which means there are a series of tabbed pages within the Source Record page. These pages each provide different functions, such as view and edit, compare and merge, and create a new record.
You can configure certain display options for the main Source Record page, including the order in which the tab appears on the MIDM and the name of the page.
The file opens in the NetBeans XML editor.
Note - You might need to renumber the remaining tabs to keep the numbering sequential.
You can configure any of the pages on the Source Record page by changing the tab name and display order and by enabling or disabling each page. Do not modify the search page or search results list for the sub-screens. Below is a sample configuration for the View/Edit page on the Source Record page.
<subscreen> <enable>true</enable> <root-object>Person</root-object> <tab-name>View/Edit</tab-name> <screen-id>0</screen-id> <display-order>0</display-order> ...
You should never need to modify the root-object or screen-id elements.
The file opens in the NetBeans XML editor.
Note - You might need to renumber the remaining tabs to keep the numbering sequential.
When enabled, the audit log stores a history of each instance in which information from the object tables in the master index database is accessed. The MIDM allows you to search for and view the audit log entries. You can enable or disable the audit log, change the display order, and customize the size of the results list. Below is the default Audit Log page definition.
<audit-log> <allow-insert>false</allow-insert> <root-object>Person</root-object> <tab-name>Audit Log</tab-name> <screen-id>7</screen-id> <display-order>7</display-order> <search-pages> <simple-search-page> <show-euid>true</show-euid> <show-lid>true</show-lid> </simple-search-page> </search-pages> <search-result-pages> <search-result-list-page> <search-result-id>0</search-result-id> <item-per-page>10</item-per-page> <max-result-size>100</max-result-size> <field-group/> </search-result-list-page> </search-result-pages> </audit-log>
The file opens in the NetBeans XML editor.
Note - If you change the order of one tab, make sure to change the order of the remaining tabs so no tabs have an identical display order value.