Bookshelf Home | Contents | Index | PDF     

Hierarchy Developer's Guide for Oracle Self-Service E-Billing > Basic Hierarchy Manager Use Cases >

Configuring Hierarchy Types

Hierarchy Manager supports configurable hierarchy types. You can change the properties of preconfigured hierarchy types and add additional hierarchy types when necessary. Each hierarchy type can have name, code, description and allowable link targets for that type. Code in a hierarchy type uniquely identifies the type object. You can use the IHierarchyTypeManager interface to find all hierarchy types and the valid link targets for each type.

The following aspects of hierarchy type are configurable:

  • Number of hierarchy types supported
  • Name of each hierarchy type
  • Valid link target types each hierarchy type allows
  • Valid children types for each link target allowed in a hierarchy type
  • Some special behavior for hierarchy importer and exporter

By default, Hierarchy Manager supports business and billing hierarchy types. The configuration for these default types is shown in the following file:

  • UNIX. EDX_HOME/xma/config/modules/hierarchy/Hierarchy.cfg.xma.xml
  • Windows. EDX_HOME\xma\config\modules\hierarchy\Hierarchy.cfg.xma.xml

The configuration file, Hierarchy.cfg.xma.xml, contains the bean entries that define the two hierarchy types to support: BusinessHierarchyType and BillingHierarchyType. You can add more types as new beans in the types property, shown in Figure 16.

Figure 16. Configuration of Additional Hierarchy Types

Figure 17 shows the business hierarchy type preconfigured in the hierarchy.cfg.xma.xml file.

Figure 17. Business Hierarchy Type Configuration

Table 1 describes the hierarchy configuration properties as shown in Figure 17.

Table 1. Business Hierarchy Configuration Properties
Call Out
Property
Description

1

name

Specifies the resource bundle key for displaying the name of this hierarchy type.

2

code

A unique string value to identify business hierarchy type. It is recommended that you do not change this value.

3

validLinkTarget

You can link a list of valid link target objects into this type of hierarchy.

4

linkTargetRelationship

Specifies the rule by which a link target can be linked in as a child node. The list includes all link targets that can restrict their list of link targets when they link into hierarchies.

5

parent, with ServiceAgreementConfig bean

Indicates that for Service Agreement objects in a business hierarchy, no valid link target can be linked in as its child. Service Agreement must be the leaf node of a business hierarchy.

6

parent, with CompanyConfig bean

Indicates that in a business hierarchy, company objects can have folders as a child node.

7

hierarchyExchange
Configuration

Specifies certain behaviors that you can override for hierarchy import and export.

Figure 18 shows the default billing hierarchy type preconfigured in the hierarchy.cfg.xma.xml file.

Figure 18. Billing Hierarchy Type Configuration

    
Hierarchy Developer's Guide for Oracle Self-Service E-Billing Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.