Hierarchy Developer's Guide for Oracle Self-Service E-Billing > Extending Advanced Hierarchy Manager Use Cases > Making Your OMF Objects Work with Hierarchy Manager >

Making Your New OMF Object Searchable Through Hierarchy

Through XML configuration, you can specify which attributes can be used as part of search criteria for a given business object. Based on those attributes, you can construct flexible search criteria to conduct different searches. If the related information is spread out among several java classes, the searchable attributes can be specified through object references. For a predefined business object, you can add or remove searchable attributes through XML configuration as well.

The following topics list the steps required to support search capability for your OMF object.

Defining Search Criteria

First, define where the search starts when you search for an attribute. Typically, this is a top-level class. For example: search service number on service agreement object. To enable service agreement object support search criteria:

<bean id="serviceAgreementSearchCriteria"
class="com.edocs.common.omf.search.SearchCriteriaSupport"
singleton="false">
<property name="searchMetaData">
<ref local="serviceAgreementSearchMeta"/>
</property>
</bean>

When a class is a subordinate class, the search for the specified bean class is always done through its parent class. For example, if you would like to search for a user's address, which is stored in the UserProfile class (not the User class), the search criteria support is specified on User class, not on UserProfile class.