Table of Contents

Search

  1. Preface
  2. Introduction
  3. Establishing a Root Node
  4. Defining the Business Entity Model
  5. Configuring Business Entity Properties
  6. Configuring Reference Entity Properties
  7. Transforming Business Entities and Views
  8. Managing Many-to-Many Relationships
  9. Configuring Search
  10. Configuring Workflow Tasks and Triggers
  11. Configuring Security and Data Filters for Business Entities
  12. Integrating Data as a Service
  13. Configuring External Calls
  14. Designing the Data Director User Interface
  15. Localizing Data Director
  16. Provisioning Tool Frequently Asked Questions

Configure the Searchable Fields

Configure the Searchable Fields

You can use the Provisioning tool to configure a field as a searchable field and set the field properties. A search request searches only the fields that you configure as searchable fields.
Multiple searchable fields might affect the performance of the search requests, so configure only the significant fields as searchable fields. For example, configure fields that contain full names, organization names, or email addresses as searchable fields rather than fields that contain country codes, gender codes, or address types.
  1. Open a supported browser, and use the following URL to log into the Provisioning tool:
    https://<MDM Hub Server host name>:<MDM Server port number>/provisioning/
  2. From the
    Database
    list, select the database for which you want to configure the fields.
  3. Click
    Business Entity
    Modeling
    .
    The
    Modeling
    page appears.
  4. Select
    Business Entities
    from the list, and select the business entity for which you want to configure the searchable fields.
  5. In the tree view, under the business entity, select
    Fields
    , and click
    Create
    .
  6. Configure the following properties based on your requirement:
    Name
    Name that appears in the business entity configuration file for the field.
    Label
    Name that appears in the Provisioning tool tree view for the field.
    Read Only
    Optional. Indicates whether you can edit the field in the Entity View. To configure the field as a non-editable field, select the property.
    Required
    Optional. Indicates whether the field is a required field. To configure the field as a required field, select
    Required
    . By default, the field is not a required field.
    URI
    Optional. Namespace where custom data types are defined. Default is commonj.sdo.
    Type
    Optional. Data type of the field. By default, the data type of the field is the same as the data type of the base object column that you associate with the field.
    Column
    Name of the base object column that you want to associate with the field.
  7. Select
    Searchable
    .
    Additional field properties appear.
  8. Based on your requirement, select one or more of the following properties:
    • Suggester
    • Sortable
    • Fuzzy
    • Filterable
    • Facet
  9. Optionally, specify the language for the field values.
    You can specify one of the following languages:
    • chinese
    • japanese
    • korean
    • english
    Default is english.
  10. Optionally, if you select
    Facet
    , in the
    Facet Range
    field, specify the range for the numeric or date fields that you configure as facets in the following format:
    <Start Value>,<End Value>,<Frequency>
    For example,
    1000,2000,50
    The facet ranges are not visible in the
    Data Director
    application. When you use the REST web service to perform the search, the response can return the facet ranges.
  11. Click
    Apply
    .
  12. Publish the changes to the MDM Hub.
    1. Click
      Publish
      .
      A change confirmation dialog box appears that prompts you to confirm the changes.
    2. Review the changes, and click
      Confirm
      .
      A validation process runs on the application. A confirmation dialog box appears that prompts you to publish the changes.
    3. Click one of the following buttons:
      • Publish
        . Saves the changes to the MDM Hub.
      • No
        . The changes remain in the temporary workspace.

0 COMMENTS

We’d like to hear from you!