EDM Configuration Components
You can configure several properties of the EDM to display the information you want in the way you want, to define the way searches can be processed, and to define the criteria that can be used for each search. Certain implementation options are also configured in the Enterprise Data Manager file, such as application server information, debug options, and security information.
The configurable properties of the user interface fall into these five categories:
Object and Field Properties
In the Enterprise Data Manager file, you can specify which objects appear on the EDM windows and the order in which they appear. You can also specify the fields displayed in each object and configure properties for each field. You can specify a field’s name, length, order of appearance on the EDM, required data type, whether text can be entered into a field or if it must be selected from a predefined value, whether a field or combination of fields must be unique to the parent object, and whether the value of the field is hidden under certain circumstances. You can also specify whether the format of a field is dependent on the value of a related field (for example, the format of a credit card number field could be dependent on the type of credit card specified).
Relationships
In the Enterprise Data Manager file, relationships define the hierarchy of the object types listed for the EDM. By specifying relationships, you define parent and child nodes. The parent and child nodes you specify in the relationships element must also be defined in the node elements of the file. You can specify one parent object; the remaining objects must be child objects to the parent you define. This section is dependent on the relationships section in the Object Definition file, and should only be changed if corresponding changes are made to the Object Definition file.
Page Configurations
You can configure several display properties for the pages that appear on the EDM. For most configurable pages, you can specify the number of fields on each row, and for all search pages you can specify the number of results to display on each page. You can also specify the type of object to display on a page and the name of the tabbed heading.
Certain properties of the following pages can be configured:
Audit Log
In the display configuration, you can specify whether an audit log is maintained of all instances in which object information was accessed from the EDM. If the log is maintained, then information about each instance of access can be viewed on the EDM. This is especially useful in healthcare implementations, where privacy of information is mandated.
Local ID Labels
A local ID is a unique identification code assigned to a record by the system in which the record originated. By default, this code is named “Local ID” on the EDM pages. This name can be modified to a name more recognizable by EDM users.
Search Page Configuration
Of the configurable pages, the page that requires the most configuration is the Search page. In addition to defining the number of fields per row and the number of records to display in the search results list, you can also specify the search criteria that appear and the types of searches allowed from the EDM.
You can define and name several search pages, each with their own configuration. For each page, you specify groups of fields that are displayed in boxed areas. Each boxed area can represent a different type of search, such as a demographic search, address search, EUID search, and so on.
For each search page you define, you must also specify the search types available, such as alphanumeric or phonetic. You can configure searches by specifying a name for the search, the maximum number of records to return, whether the results are weighted, and whether wildcard characters can be used. When you define the search types for the EDM, you must specify a query for each type you define. The queries you specify must already be defined in the Candidate Select file.
Implementation Configuration
The Enterprise Data Manager file defines certain information about the application server for the master index implementation, such as the names of certain validation and management components, debug parameters, and security information. The security for the master index application is based in the application server.
- © 2010, Oracle Corporation and/or its affiliates