A hierarchy model consists of a collection of hierarchy relationships between business entities. For example, an Organization hierarchy model shows the relationships from the Organization business entity to the Person business entity.
A hierarchy model consists of a top-level business entity, additional business entities, and hierarchy relationships that define parent-child relationships between business entities. Each business entity in a hierarchy model must be connected to the top-level business entity directly or through other business entities. You can create as many hierarchy relationships as you need to represent the hierarchy model.
You can also define attributes of relationships to allow users to provide additional information about relationships.
For example, your organization needs to track customers by households. You might create the following hierarchy model, hierarchy relationships, and attributes:
1Create an Organization hierarchy model.
2Add the Organization business entity as the top-level business entity.
3Create a relationship from the Organization business entity to the Person business entity.
4Define a Status attribute for the relationship between the Organization and Person business entities. Use this attribute to define whether the organization is actively engaging with the employee.
Then in Business 360 applications, users can create an Organization hierarchy based on the hierarchy model. Users can create a hierarchy relationship from the Informatica record to the John Smith record.
You can also create recursive relationships. For example, you can create a recursive relationship from the Person business entity to the Person business entity. Later, in Business 360 applications, you can create a relationship from a Person record to a Person record. For example, you might create a relationship from the John Smith record to the Jane Smith record. The relationship shows that John Smith is the spouse of Jane Smith.
The following image shows a sample hierarchy model in the Hierarchy Designer:
You can enable a hierarchy model for search. When you enable a hierarchy model for search, users can filter records from the search results of the business applications based on the hierarchy and its nodes and inherit the dynamic field definitions to the child records within a hierarchy. When users update a hierarchy or the dynamic field definitions, the search results page doesn't display the latest changes. To ensure the latest hierarchy updates appear in search results, run a process hierarchies job to index records and inherit dynamic field definitions belonging to the hierarchies. Real-time indexing occurs when users update less than 100 records in the last node of a hierarchy. In this case, users don't need to depend on the job to index the records.
