Informatica® Business 360 Console

December 2023

Define the Data Model

Informatica Business 360 Console Define the Data Model
December 2023
© Copyright Informatica LLC 2020, 2023

This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be
reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC.

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial
computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,
the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the
extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License.

Informatica, Informatica Cloud, Informatica Intelligent Cloud Services, PowerCenter, PowerExchange, and the Informatica logo are trademarks or registered trademarks
of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://
www.informatica.com/trademarks.html. Other company and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product.

The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at
[email protected].

Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE
INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.

Publication Date: 2023-12-11

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Intelligent Cloud Services web site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Intelligent Cloud Services Communities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Intelligent Cloud Services Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Intelligent Cloud Services Trust Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 1: Defining the data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Prerequisites for defining your data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2: Defining business entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Custom business entity configuration process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Defining custom business entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Configuring predefined business entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Business entity properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Review the predefined business entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Create a custom business entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Business entity field types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Dynamic fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Add fields to a business entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Add a picklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Add a dependent picklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Add business entity record fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Add dynamic fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configure the field properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configure general properties for a field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configure data quality properties for a field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configure search properties for a field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configure survivorship properties for a field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Calculated fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Enable last updated dates for source records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Forcefully ingress source records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Unprocessed source records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Example: Ingress data with source last updated date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Source record with an old last updated date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Source record with a newer last updated date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Edit a business entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table of Contents 3
 Chapter 3: Defining reference data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Rules and Guidelines for using reference data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Create reference data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4: Defining dynamic pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Create a dynamic pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 5: Defining hierarchy models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Step 1. Create a hierarchy model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Step 2. Configure the top-level node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Step 3. Add a node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Step 4. Define relationship attributes (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 6: Defining relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Relationship types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Create a relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Define relationship attributes (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4 Table of Contents
Preface
Follow the instructions in Define the Data Model to build data models and configure data quality, matching,
and survivorship rules. Learn how to define business entities, and the hierarchical and network of
relationships between business entities in the model.

Informatica Resources
Informatica provides you with a range of product resources through the Informatica Network and other online
portals. Use the resources to get the most from your Informatica products and solutions and to learn from
other Informatica users and subject matter experts.

Informatica Documentation
Use the Informatica Documentation Portal to explore an extensive library of documentation for current and
recent product releases. To explore the Documentation Portal, visit https://docs.informatica.com.

If you have questions, comments, or ideas about the product documentation, contact the Informatica
Documentation team at [email protected].

Informatica Intelligent Cloud Services web site

You can access the Informatica Intelligent Cloud Services web site at http://www.informatica.com/cloud.
This site contains information about Informatica Cloud integration services.

Informatica Intelligent Cloud Services Communities

Use the Informatica Intelligent Cloud Services Community to discuss and resolve technical issues. You can
also find technical tips, documentation updates, and answers to frequently asked questions.

To access the Informatica Intelligent Cloud Services Community, see

Master Data Management SaaS Community.

Developers can learn more and share tips at the Cloud Developer community:

https://network.informatica.com/community/informatica-network/products/cloud-integration/cloud-
developers

Informatica Intelligent Cloud Services Marketplace

Visit the Informatica Marketplace to try and buy Data Integration Connectors, templates, and mapplets:

https://marketplace.informatica.com/

5
 Informatica Knowledge Base
Use the Informatica Knowledge Base to find product resources such as how-to articles, best practices, video
tutorials, and answers to frequently asked questions.

To search the Knowledge Base, visit https://search.informatica.com. If you have questions, comments, or
ideas about the Knowledge Base, contact the Informatica Knowledge Base team at
[email protected].

Informatica Intelligent Cloud Services Trust Center

The Informatica Intelligent Cloud Services Trust Center provides information about Informatica security
policies and real-time system availability.

You can access the trust center at https://www.informatica.com/trust-center.html.

Subscribe to the Informatica Intelligent Cloud Services Trust Center to receive upgrade, maintenance, and
incident notifications. The Informatica Intelligent Cloud Services Status page displays the production status
of all the Informatica cloud products. All maintenance updates are posted to this page, and during an outage,
it will have the most current information. To ensure you are notified of updates and outages, you can
subscribe to receive updates for a single component or all Informatica Intelligent Cloud Services
components. Subscribing to all components is the best way to be certain you never miss an update.

To subscribe, on the Informatica Intelligent Cloud Services Status page, click SUBSCRIBE TO UPDATES. You
can choose to receive notifications sent as emails, SMS text messages, webhooks, RSS feeds, or any
combination of the four.

Informatica Global Customer Support

You can contact a Global Support Center through the Informatica Network or by telephone.

To find online support resources on the Informatica Network, click Contact Support in the Informatica
Intelligent Cloud Services Help menu to go to the Cloud Support page. The Cloud Support page includes
system status information and community discussions. Log in to Informatica Network and click Need Help to
find additional resources and to contact Informatica Global Customer Support through email.

The telephone numbers for Informatica Global Customer Support are available from the Informatica web site
at https://www.informatica.com/services-and-training/support-services/contact-us.html.

6 Preface
Chapter 1

Defining the data model

You can use the predefined data model and customize it to suit your business needs or define a custom data
model.

To define your data model, perform the following tasks:

• Customize predefined business entities, or define custom business entities and configure data quality,
match model, and survivorship.
• Define reference data, which is a set of values, to use in picklists that you include in business entities.
• Define relationships between business entities.

Prerequisites for defining your data model

To define a data model, you need to analyze, strategize, and define your business and data requirements by
collaborating with various stakeholders.

Before you define a data model, perform the following steps:

• Understand the business objectives and requirements for your data management project.
• Provide insights into what various stakeholders want and need from the data management project.
• Identify the source systems that contribute to the master data.
• Analyze the attributes and quality of the data that you want to consolidate into master data.
• Identify the business entities and the relationships between business entities that are critical to your data
model.
• Identify reference data, such as lists of countries, currencies, products, gender, and salutations, that your
organization uses.

7
Chapter 2

Defining business entities

A business entity is an entity of importance to your organization and consists of fields that support your data
needs. To define a business entity, decide on the fields based on the data that your source systems will
contribute to the master data.

For example, a company that manufactures cars might define business entities for some or all of the
following entities: customers, employees, suppliers, factories, materials, and products. A charitable
organization might define donors, households, and projects. A health care provider might define doctors, care
sites, and insured services.

When you use the predefined data model, edit the business entity properties and fields to match the needs of
your organization. For example, you can change the name of the business entity, change field names or
remove fields that are not relevant to your organization. You can also create custom configurations around
data quality, search, and survivorship.

To define a business entity, you often use an iterative process. You can come back later to add more fields
and to modify or add configurations, such as data quality, search, and survivorship.

Before you define a business entity, determine the type of business entity that you want to use.

You can define and use the following types of business entities:

• Predefined business entities

• Custom business entities

8
Custom business entity configuration process
To be able to define and use a custom business entity, ensure that you follow the steps in the configuration
process.

The following image walks you through the steps in the custom business entity configuration process:

The following table lists the steps in the custom business entity configuration process and their reference
content:

Configuration Step Reference Content

Step 1. Define custom business entities “Defining custom business entities” on page 10

Step 2. Add fields to the business entities “Add fields to a business entity” on page 16

Step 3. Configure the business entity fields for records to be “Configure search properties for a field” on page 23
searchable

Step 4. Configure data quality rules Configuring data quality

Step 5. Configure survivorship rules and rank source systems Configuring survivorship for business entity

Step 6. Create a match model Creating a match model from scratch

Step 7. Define relationships between business entities “Create a relationship” on page 41

Step 8. Define business entity hierarchies Chapter 5, “Defining hierarchy models” on page 36

Step 9. Create custom pages to view and edit records Creating a custom page

Step 10. Create layouts for search results Configure a search result layout component

Custom business entity configuration process 9

 Configuration Step Reference Content

Step 11. Add business entities to your business application Add business entities to an application

Step 12. Add custom pages and search result layouts to your Configure search for an application
business application

Defining custom business entities

To define a custom business entity, perform the following tasks:

1. “Create a custom business entity” on page 11

2. “Add fields to a business entity” on page 16
3. “Configure the field properties” on page 21

Configuring predefined business entities

To configure a predefined business entity, perform the following tasks:

1. “Review the predefined business entities” on page 11

2. “Add fields to a business entity” on page 16
3. “Configure the field properties” on page 21

Business entity properties

You can configure business entity properties that suit your business requirements.

The following table describes the business entity properties:

Property Description

Display Name Required. Name of the business entity that you want to appear in the Business 360 application.

Internal ID Required. A unique business entity identifier, which is generated based on the display name that you
enter. You cannot change the internal ID after you create the business entity.

Description Optional. A description of the business entity.

Location Required. Project or folder within which you want to save the business entity.

Icon Optional. Icon to represent the business entity for easy identification.

10 Chapter 2: Defining business entities

Review the predefined business entities
Review the predefined business entities to determine whether these consists of fields that support your
business requirements.

1. Open a business entity from the Explore page.

All the fields that the business entity includes appear on the canvas.
2. Review the business entity properties such as the display name to align it with your business
requirements.
a. Click the Actions icon, and then click Properties.
b. In the Business Entity dialog box, edit the property values, and click OK.
3. Review the predefined fields to determine whether they meet your business requirements.
• If a predefined field does not meet business requirements, determine the edits to the field to match
your requirements.
• If the predefined business entity does not include some fields that your business needs, note the
missing fields so you can add the fields later.
4. Review the field properties such as data quality, survivorship, and search for each field to determine any
changes that you might require.

Create a custom business entity

You can define a custom business entity and configure at least the required properties, such as display name
and location.

1. Click New.
The New Asset dialog box appears.
2. Click Model > Business Entity.
3. Click Create.
The Business Entity dialog box appears.
4. Specify the business entity properties.
5. Click OK.
The business entity is created and a blank canvas appears.
6. Next step: Add fields to the business entity.

Business entity field types

Your application includes predefined business entity fields. If the predefined fields don't meet the needs of
your organization, edit the predefined field and add fields that you need. These fields can appear in the
business user interface as fields of records, such as the fields of master records and source records. Each

Review the predefined business entities 11

 field contains a single data item. For example, you can add a field to contain the full name and another field
to contain the date of birth.

You can add the following types fields to business entities:

• Text
• Integer
• Double
• Decimal
• Boolean
• Date and Time
• Date
• Picklist
• Dependent Picklist
• Field Group
• Business Entity Record
• Postal Address
• Phone Number
• Email Address
• Dynamic Field Definitions
• Dynamic Field Values

Dynamic fields
When you want a set of fields to vary across records of a business entity, configure dynamic fields. Dynamic
fields aren't fixed and can be added or removed as needed for specific records.

When you use dynamic fields, a business user can add suitable dynamic fields for different records. Records
related through a hierarchy or a graph relationship receive the dynamic fields, and the business users can add
values to the dynamic fields.

For example, consider the Grocery and Electronics records that belong to a business entity, such as Category.
Fields, such as Allergens and Ingredients, might be suitable for the Grocery record. Fields, such as Display
and Camera, might be suitable for the Electronics record.

Consider the Borges Penne and Teddy 5G Mobile records that belong to another business entity, such as
Item. Assign the Borges Penne record to the Grocery record and the Teddy 5G Mobile record to the
Electronics record in a hierarchy.

The Borges Penne record gets the Allergens and Ingredients fields from the Grocery record, and you can add
values for them in the Borges Penne record. Similarly, the Teddy 5G Mobile record gets the Display and
Camera fields from the Electronics record, and you can add values for them in the Teddy 5G Mobile record.

To configure dynamic fields, you require a dynamic pool asset, dynamic field definitions attributes in a
provider business entity, and dynamic field values attributes in a consumer business entity. Dynamic fields
are contained in an asset called the dynamic pool. Dynamic fields are basic fields and field groups and a
collection of these is a dynamic pool. You can create multiple dynamic pools to address different use cases.
For example, create a dynamic pool for Products and another dynamic pool for Suppliers.

12 Chapter 2: Defining business entities

The following image shows an example of a dynamic pool, dynamic field definitions, and dynamic field
values:

Note: Effective in the October 2023 release, the dynamic fields are available for preview, and you can add
dynamic fields to business entities.

Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in
production environments or any environment that you plan to push to production. Informatica intends to
include the preview functionality in an upcoming release for production use, but might choose not to in
accordance with changing market or technical circumstances. For more information, contact Informatica
Global Customer Support.

Dynamic fields attributes

When you configure dynamic fields, you need to define dynamic field definitions and dynamic field values
attributes.

Dynamic field definitions

Dynamic field definitions are associated with a dynamic pool and acts as a container for the fields and field
groups in the pool that users can select in business applications. Add a dynamic field definitions attribute to
a provider business entity. Business users can select the fields and field groups that are relevant to a record
that they create. You can also configure inheritance settings to determine how the records in a hierarchy can
inherit these definitions. For more information on inheritance of dynamic field definitions, see “Inheritance of
dynamic field definitions” on page 15.

Business entity field types 13

 The following image shows the dynamic field definitions that a user selected for the Pasta & Noodles record:

Dynamic field values

Dynamic field values are associated with a dynamic field definitions attribute that you added to a provider
business entity. The dynamic field values attribute displays all the fields that are selected through the
dynamic field definitions attribute. Add a dynamic field values attribute to a consumer business entity.
Business users can enter values for the fields and field groups in records after they add these records to a
hierarchy or relate through a graph relationship.

The following image shows the dynamic fields of the Borges Penne 200g record after a user assigns it to the
Pasta & Noodles record:

The following image shows how a dynamic pool, a dynamic field definitions attribute, and a dynamic field
values attributes are related:

For more information about configuring dynamic fields, see “Add dynamic fields” on page 19.

14 Chapter 2: Defining business entities

Inheritance of dynamic field definitions
Records in a hierarchy can inherit dynamic field definitions from their parent records.

When you configure a dynamic field definitions attribute, you can specify how the attribute can inherit
dynamic fields definitions from the same or another dynamic fields definitions attribute. The inheritance
depends on a hierarchical relationship between the business entities that contain the dynamic field
definitions attributes and the direction of the relationship. The hierarchy that contains the hierarchical
relationship must be set to be searchable. When you assign a record to another record in a hierarchy, the
child record inherits the dynamic field definitions from the parent record based on the relationship between
them.

For example, add a record named Food & Beverages and set the dynamic field definitions to include Allergens
and Ingredients. When you add a child record named Pasta & Noodles record to the Food & Beverages record,
the Pasta & Noodles record inherits the dynamic field definitions, such as Allergens and Ingredients, from the
Food & Beverages record.

The following image shows the Pasta & Noodles record with the inherited dynamic field definitions:

Note: To update the dynamic field definitions that the related records inherit, run the process hierarchies
jobs. For more information about defining and running the process hierarchies job, see Define and run a
process hierarchies job.

Supported and unsupported features for dynamic fields

Before you use dynamic fields, ensure that you understand the features that the dynamic fields support.

You can use the following features with the dynamic fields:

• You can configure survivorship for the dynamic fields, but you can't configure declarative match rules.
• You can't define basic and advanced data quality rule associations for the dynamic fields.
• You can ingress and egress data from the dynamic fields, but the users can't import data to the dynamic
fields through file import.
• You can configure permissions for the user roles to access the dynamic field definitions and dynamic
field values attributes, but not to the specific fields and field groups in the dynamic pool. You can't
configure data access rules for dynamic fields.
• You can't create business events for the dynamic fields. You can't configure permissions to view dynamic
fields in the approval tasks.
• The users can edit the dynamic field values attribute when they edit a custom page. But users can't edit
the dynamic field values attribute when they create a record.

Business entity field types 15

 • The users can't search for the dynamic field values and filter the search results based on the dynamic
fields. Users can't search and replace the dynamic fields. The exported search results don't contain any
dynamic fields.
• The users can't view the history of the dynamic field updates.
• The users can't view the dynamic field values when they view the source records of a master record.
• The users can't create reports based on the dynamic fields.

Add fields to a business entity

To quickly define a business entity, start by adding smart fields. Smart fields are context-aware fields that
have predefined properties, such as validation and match rules. The smart fields are building blocks for
common fields, such as address, email, and phone. After you define smart fields, add basic fields for other
types of data.

1. Open the business entity from the Explore page.

2. In the fields panel, expand the Smart Fields and Basic Fields sections, and review the fields in each
section.
Note: You cannot disable the fields that are part of the default search layout.
3. Double-click a field to add the field to the canvas, and then specify the general field properties, such as
display name and internal ID.
You can later configure field properties such as data quality, survivorship, and search.
4. If you added a smart field, click the down arrow to open and review the associated fields.
Note: You cannot add or delete fields from a smart field.
a. Click each field that is associated with the smart field and review the field properties.
b. If required, edit the properties of the associated fields.
c. To close the smart field, click the up arrow on the smart field.
5. If you add a picklist or a dependent picklist, select the reference data asset for the picklist field.
For more information, see “Add a picklist” on page 17 and “Add a dependent picklist” on page 18.
6. If you add a dynamic field definitions attribute, select a dynamic pool to associate it with the dynamic
field definitions attribute.
For more information about adding a dynamic field definitions attribute, see “ Add a dynamic field
definitions attribute” on page 20.
7. If you add a dynamic field values attribute, select a dynamic field definitions attribute to associate it with
the dynamic field values attribute.
For more information about adding a dynamic field values attribute, see “Add a dynamic field values
attribute” on page 20.
8. If you added a field group, click the down arrow to open the group and add fields.
a. Double-click fields to add the fields to the canvas, and then specify the field properties.
b. To close the field group, click the up arrow on the field group.
Within a field group, you can nest up to six levels of field groups. You can't add smart fields to the nested
field group at the last level.
9. Define additional fields for the business entity.

16 Chapter 2: Defining business entities

 10. Save the fields that you added to the business entity.
a. Click Save.
The validation process checks the field properties. If there are no errors, the fields are saved.
b. If there are validation errors, correct the errors, and click Save.
11. To close the canvas, click the Close icon.
The saved business entity appears in the Explore page.

Add a picklist
To provide a list of values for users to select from, you can add a picklist to a business entity. A picklist uses
a list of values contained in a reference data asset. A maximum of 1000 picklist values that are sorted in
alphabetical order can appear in business applications.

When you configure a picklist, you can select existing reference data or add new reference data. Reference
data created in Reference 360 appears along with reference data that are published in Business 360 Console.
If you select reference data created in Reference 360, Business 360 Console automatically publishes the
reference data to Business 360 Console.

1. In the fields panel, expand the Basic Fields section, and double-click the Picklist field to add it to the
canvas.
2. Specify a display name and an internal ID.
3. Optionally, specify a description for the picklist field.
4. If you want to select existing reference data, perform the following steps:
a. Click the asset picker.
b. In the Select Reference Data dialog box, select the reference data asset for the picklist field, and
click Select.
The selected reference data asset appears as a link in the Reference Data field. You can click the
link to open the reference data in Reference 360.
5. If you want to add new reference data, perform the following steps:
a. Click New.
b. In the Reference data dialog box, add the reference data properties, such as display name and
location, and click OK.
c. View the summary of the reference data, and click Save.
You can view the reference data that you created in the Default folder on the Explore page.
6. Select one of the following Cache Reference Data options:

Option Description

Display cached values Lists the cached values in the business application.

Always read from Reference 360 Lists the latest values from Reference 360.

Add fields to a business entity 17

 Add a dependent picklist
When the list of values that users select from has a dependency on a value that users select in another list,
use a dependent picklist. For example, a list of states is dependent on the country selected from a countries
list. When you add a dependent picklist, you must first add a parent picklist.

In a dependent picklist field, you use a list of values that a dependent reference data asset contains. Before
you add parent and dependent picklist fields to a business entity, ensure that the parent and the dependent
reference data assets to use in the picklists are configured. Also, ensure that both the dependent and parent
picklists are root fields or belong to the same field group.

1. Add a parent picklist, such as Country.

a. In the fields panel, expand the Basic Fields section, and double-click the Picklist field to add it to the
canvas.
b. Specify a display name, such as Country, and an internal ID.
c. Optionally, specify a description for the picklist field.
d. If you want to select existing reference data, perform the following steps:
1. Click the asset picker.
2. In the Select Reference Data dialog box, select the reference data asset for the picklist field,
and click Select.
The selected reference data asset appears as a link in the Reference Data field. You can click
the link to open the reference data in Reference 360.
e. If you want to add new reference data, perform the following steps:
1. Click New.
2. In the Reference data dialog box, add the reference data properties, such as display name and
location, and click OK.
3. View the summary of the reference data, and click Save.
You can view the reference data that you created in the Default folder on the Explore page.
f. Select one of the following Cache Reference Data options:

Option Description

Display cached values Lists the cached values in the business application.

Always read from Reference 360 Lists the latest values from Reference 360.

2. Add a dependent picklist, such as State.

a. In the fields panel, expand the Smart Fields section, and double-click the Dependent Picklist field to
add it to the canvas.
b. Specify a display name, such as State, and an internal ID.
c. Optionally, specify a description for the picklist field.
d. If you want to select existing reference data, perform the following steps:
1. Click the asset picker.

18 Chapter 2: Defining business entities

 2. In the Select Reference Data dialog box, select the reference data asset for the picklist field,
and click Select.
The selected reference data asset appears as a link in the Reference Data field. You can click
the link to open the reference data in Reference 360.
e. If you want to add new reference data, perform the following steps:
1. Click New.
2. In the Reference data dialog box, add the reference data properties, such as display name and
location, and click OK.
3. View the summary of the reference data, and click Save.
You can view the reference data that you created in the Default folder on the Explore page.
f. Select one of the following Cache Reference Data options:

Option Description

Display cached values Lists the cached values in the business application.

Always read from Reference 360 Lists the latest values from Reference 360.

g. From the Parent Picklist, select a picklist.

Note: The list contains only the parent picklists that are added to the canvas.

3. Optionally, add additional dependent picklists.

Add business entity record fields

Add business entity record fields to relate records. The users search for business entity records and select a
record to relate by using this field. You can add up to 15 business entity record fields to a business entity.

1. In the fields panel, expand the Basic Fields section, and double-click Business Entity Record.
2. Specify a display name and an internal ID for the field.
3. Optionally, specify a description for the field.
4. In the Business Entity field, click the asset picker.
The Business Entity dialog box appears.
5. Find and select a business entity for the field.
6. Click Select.
The canvas appears with the selected asset in the Business Entity Record field.
7. To add more business entity record fields, repeat steps 1 through 6.
8. Save the business entity.

Add dynamic fields

Before you add dynamic fields, create a dynamic pool. You can then add a dynamic field definitions attribute
to one business entity and a dynamic field values attribute to another related business entity.

For more information about creating dynamic pools, see “Create a dynamic pool” on page 34.

Note: Effective in the October 2023 release, the dynamic fields are available for preview, and you can add the
dynamic field definitions and dynamic field values attributes to business entities.

Add fields to a business entity 19

 Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in
production environments or any environment that you plan to push to production. Informatica intends to
include the preview functionality in an upcoming release for production use, but might choose not to in
accordance with changing market or technical circumstances. For more information, contact Informatica
Global Customer Support.

Add a dynamic field definitions attribute

Associate a dynamic field definitions attribute to a dynamic pool, and the attribute acts as a container for the
fields and field groups in the dynamic pool. Users can select the relevant fields in business applications.

1. Open a business entity from the Explore page.

2. In the fields panel, expand the Dynamic Fields section.
3. Double-click Dynamic Field Definitions to add it to the canvas, and then specify the general field
properties, such as display name and internal ID.
4. Select the dynamic pool to which you want to associate the dynamic field definitions attribute.
5. In the Properties section, click Inheritance.
6. Select a business entity that you want to participate in the inheritance of dynamic field definitions.
A list of dynamic field definitions attributes that belong to the same dynamic pool appear.
7. Select a dynamic field definitions attribute from which you want to inherit the dynamic field definitions.
8. Select a hierarchical relationship that indicates the direction of inheritance for the dynamic field
definitions.
You can view the relationships that belong to searchable hierarchies and the selected business entities
participate.
9. Click Save.
10. To close the canvas, click the Close icon.

Add a dynamic field values attribute

Associate a dynamic field values attribute in a consumer business entity to a dynamic field definition
attribute from a provider business entity. The dynamic field values attribute displays all the fields that are
selected through the dynamic field definitions attribute.

1. Open a business entity from the Explore page.

2. In the fields panel, expand the Dynamic Fields section.
3. Double-click Dynamic Field Values to add it to the canvas, and then specify the general field properties,
such as display name and internal ID.
4. Select a business entity that contains the dynamic field definitions attributes.
All the dynamic field definitions that you added to the selected business entity appear.
5. Select the dynamic field definitions attribute from which you want to get the dynamic field definitions for
the child records in a hierarchy.
6. Select a relationship between the provider and consumer business entities.
You can view only the relationships that have the consumer business entity configured as Business
Entity 1. When users assign records based on the selected relationship in a hierarchy or a graph, the
child records get the dynamic field definitions from the parent records. For more information on creating
a relationship, see “Create a relationship” on page 41.
7. Click Save.

20 Chapter 2: Defining business entities

Configure the field properties
After you review or add fields to the business entity, configure the field properties, such as general, data
quality, search, and survivorship properties.

Configure general properties for a field

You can configure the general properties for a business entity field. Based on the type of field, the properties
vary.

1. From the Explore page, find and open a business entity.

2. Select a field from the canvas.
3. Configure the general properties for the field.
The following table lists the properties that you can configure for a field:

General Description
property

Status Specifies whether to use the field in the business entity. To disable a field, select Disabled.
Note: You can disable an optional basic field, smart field, and field group that do not have any
dependencies. You cannot disable the fields that are part of the default search layout.

Display Name Name of the business entity field.

Ensure that you don't configure display names that are identical to the following system field
names:
- Error Message
- Severity
- Business ID
- Created By
- Created On
- Last Updated By
- Last Updated Date
- Record State
- Source Business ID
- Source Primary Key
- Source System
When you export search results related to these business entities from your business
application, the exported search results file includes information in an incorrect format.

Internal ID Unique identifier of the business entity field.

Description Description of the business entity field.

Maximum Length of the string the field can contain. Applies to text fields.
Length

Multiline field Specifies whether the field can contain multiple lines of text separated by paragraph breaks or
line breaks. For example, a multiline text field can contain an address with multiple lines.

Configure the field properties 21

 General Description
property

Calculated field Specifies whether the field contains a value that's calculated based on a calculated field rule.
The calculated field rule is based on the values of attributes of a business entity or
relationship. You can configure integer, double, decimal, date, or date and time attributes to be
calculated fields.
For more information about calculated fields, see calculated fields.
Note: Effective in the November 2023 release, the ability to configure attributes to be
calculated fields is available for preview.
Preview functionality is supported for evaluation purposes but is unwarranted and is not
supported in production environments or any environment that you plan to push to production.
Informatica intends to include the preview functionality in an upcoming release for production
use, but might choose not to in accordance with changing market or technical circumstances.
For more information, contact Informatica Global Customer Support.

Precision The total number of digits, including the decimal places. For example, 123.45 has a precision
of 5. Applies to decimal fields.

Scale The number of digits after the decimal place. For example, 123.45 has a scale of 2. Applies to
decimal fields.

Reference Data Name of reference data asset that contains the list of values for the field.
Applies to the following field types:
- Picklist
- Dependent Picklist

Parent Picklist Name of reference data that you want set as a parent reference data. Applies to dependent
picklists.

Required Specifies whether the field is a required field.

Applies to all the field types except field groups.

22 Chapter 2: Defining business entities

 General Description
property

Uniqueness Applies to field groups. Specify fields in a field group based on which you want field group
Criteria values qualified as unique or duplicates. Duplicate values are merged based on the fields that
establish the uniqueness criteria. Duplicate values are not case-sensitive.
To set uniqueness criteria, you can't use fields from nested field groups.
The field group values survive based on the survivorship rules.
For example, the Address field group has the uniqueness criteria set for postal code. If the
Address field group contains two addresses which both have the same postal code, the two
addresses are merged into one address.
Note: Effective in the July 2023 release, the ability to select optional fields of field groups as
uniqueness criteria and merge duplicate field group values that aren't case sensitive are
available for preview.
Preview functionality is supported for evaluation purposes but is unwarranted and is not
supported in production environments or any environment that you plan to push to production.
Informatica intends to include the preview functionality in an upcoming release for production
use, but might choose not to in accordance with changing market or technical circumstances.
For more information, contact Informatica Global Customer Support.

Source Last Enables the ability to capture the last updated date for source records.
Updated Date You can enable the source last update date for field groups. By default, the source last
updated date field is enabled for root fields.
You can map the source last updated field from a source record to a target record.
For more information about mappings, see the "Target transformation mapping example"
chapter in the B360 Connector help.

4. Click Save.

Configure data quality properties for a field

You can associate data quality rules to the business entity fields to cleanse, standardize, or validate the field
values.

1. From the Explore page, find and open a business entity.

2. Select a field from the canvas, and click Data Quality in the properties section.
You can add basic, advanced, or DaaS rule associations based on the field you select. For more
information about adding rule associations, see Configure Data Quality.

Configure search properties for a field

You can configure the search properties for each business entity field. Depending on the configuration, a field
can be searchable, facetable, and appear as an auto-suggestion during a search operation.

1. From the Explore page, find and open a business entity.

2. Select a field from the canvas, and click Search in the properties section.
3. Configure the following search properties:
• Searchable. Enables the field for search requests.
• Auto Suggest. Enables suggestions based on search strings that users type in a search box.
• Facetable. Enables the field to appear in the Filters panel of the search results page. Users can
narrow down the search results using these fields.

Configure the field properties 23

 If you select a numeric or date field, you can select one of the following options:
- Simple. Filters search results based on individual field values. By default, this option is selected.

- Range. Allows users to specify a range for the selected field.

• Reportable. Enables the field to appear as dimensions and measures when users create reports. You
can enable up to 150 fields in a business entity as reportable. In a field group that has nested field
groups, you can enable fields in the first two levels as reportable.
Note: Effective in the November 2023 release, the ability to set a field as reportable is available for
preview.
Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in
production environments or any environment that you plan to push to production. Informatica intends to
include the preview functionality in an upcoming release for production use, but might choose not to in
accordance with changing market or technical circumstances. For more information, contact Informatica
Global Customer Support.
4. Click Save.

Configure survivorship properties for a field

You can configure survivorship rules and rank source systems that contribute values to a business entity
field. The survivorship configuration determines the best value for a field.

1. From the Explore page, find and open the business entity.
2. Select a field from the canvas and click Survivorship in the properties section.
3. To configure survivorship properties, click Edit.
You can configure the following properties:
• Rule. Type of rule. You can configure decay, maximum, and minimum rules.
• Source Ranking. Rank for the source systems based on their reliability.
4. Click Save.
For more information about configuring survivorship, see Configure Survivorship.

Calculated fields
Calculated fields indicate that the field values are calculated based on the values of attributes of a business
entity or relationship.

For example, Client Site and Location are two related business entities. Opening Date is a field of the Client
Site business entity. If you want the earliest opening date of a client site in a location, create a calculated
attribute in the Location business entity.

The following table describes field types that can be configured as calculated attributes and the field types
that they support:

Field Type Supported Field Types

Integer Integer

Double - Integer
- Double

24 Chapter 2: Defining business entities

 Field Type Supported Field Types

Decimal - Integer
- Double

Date - Date
- Date and Time

Date and Time Date and Time

Note: You can't use a calculated field in a declarative rule, survivorship configuration, a user-triggered event,
and a business application as a display field. You can't assign create, update, and delete privileges to a
custom user role for the calculated fields.

Configure attributes to be calculated fields

You can configure integer, double, decimal, date, or date and time attributes to be calculated fields.

Note: Effective in the November 2023 release, the ability to configure attributes to be calculated fields is
available for preview.

Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in
production environments or any environment that you plan to push to production. Informatica intends to
include the preview functionality in an upcoming release for production use, but might choose not to in
accordance with changing market or technical circumstances. For more information, contact Informatica
Global Customer Support.

1. In the fields panel, expand the Basic Fields section, and double-click the field that you want to configure
as a calculated attribute to add it to the canvas.
2. Specify a display name and an internal ID.
3. Optionally, specify a description for the field.
4. Select Calculated field.
The Calculated Field Rule section opens.
5. Click Add.
6. Select one of the following options:
• A field value from a record related through a business entity record attribute. Indicates that the
attribute value is based on records related through a business entity record field.
• A field value from a record related through a relationship. Indicates that the attribute value is based
on the records related through a relationship type in which the current business entity participates.

Configure the field properties 25

 7. If you select A field value from a record related through a business entity record attribute, perform the
following steps:
a. Select a business entity.
You can view a list of primary business entities that include at least one attribute of supporting field
type and one business entity record field related to the current business entity. For each primary
business entity, you can also view a list of secondary business entities based on the other business
entity record fields that the primary business entity contains. The secondary business entities also
contain at least one attribute of supporting field type.
The following image shows a list of business entities as related business entities:

In the preceding sample, an integer field in the Organization business entity is set to be a calculated
field. Faculty Rooster is a primary business entity because it contains an integer field and the
faculty_org business entity record field that is related to the Organization business entity. Person is
a secondary business entity because it contains a double field, and the Faculty Rooster business
entity contains the head_of_faculty business entity record field that is related to the Person
business entity.
b. Select the field that you want to use to calculate values.
c. Select a function to calculate values.

26 Chapter 2: Defining business entities

 The following table describes the functions:

Function Description

Maximum Calculates the maximum value of the fields.

Minimum Calculates the minimum value of the fields.

Average Calculates the average value of the fields. Applies only to integer, double, and
decimal fields.

Sum Calculates the total sum of the fields. Applies only to integer, double, and
decimal fields.

Count Calculates the number of records that contain valid values.

8. If you select A field value from a record related through a relationship, perform the following steps:
a. Select a relationship type.
You can view a list of all the relationship types in which the current business entity participates.
b. Select one of the following options:

Option Description

Business entity attribute Indicates that you want to use a business entity attribute to calculate values.

Relationship attribute Indicates that you want to use a relationship attribute to calculate values.

c. Select a field that you want to use to calculate values.

You can view all the fields of supporting field types from the other business entity that participates
in the relationship type.
d. Select a function to calculate values.

9. Click Save.

Enable last updated dates for source records

You can enable the last updated dates of source records to ensure that you get the latest data during ingress.

You can map the last updated date from a source record to a target record. For each field, you can capture
the last updated date from a source system.

You can enable the source last updated date to prevent the override of the latest data during ingress. When
you ingress incremental changes to records from source systems, the source records are updated only when
the last updated date is the latest date.

Enable last updated dates for source records 27

 Forcefully ingress source records
You can forcefully ingress incremental records irrespective of the source last updated dates in the source
system.

For example, you can ingress incremental records with older or same last updated dates as compared to the
existing record.

To force ingress source records, select the Force Record Update option when you create an ingress job or
use the _forceUpdate parameter in the Source Record API.

Unprocessed source records

When you enable the source last updated date for a field group, the ingress job doesn't process some records
based on the source last updated dates of the root fields or field groups.

When you ingress incremental changes to a record, the changes to the root fields or the field groups succeed
or fail based on their source last updated date. If the last updated date is a future date or an earlier date
when compared to the last updated date in the Business 360 data store, the ingress job doesn't process the
incremental changes

You can view the number of records that the ingress job didn't process from the Load step of an ingress job.
For more information about ingress jobs, see Monitoring ingress jobs.

Example: Ingress data with source last updated date

For example, you want to ingress records from Savings and Loan source systems.

The following table lists records from the Savings and Loan source systems:

Source First Name Last Name Gender Phone Source Last

System Updated Date

Savings John Smith M 123456789 30/03/2021

Loan Johnson Smith M 987654321 28/03/2021

The records from Savings and Loan source systems are merged to create a master record. The master
record was created on 30/03/2021. When you ingress data from the Savings and Loan source systems the
Savings record has the latest source last updated date. The master record is updated with the data from the
Savings record.

The following table lists the updated data of the master record:

Record First Name Last Name Gender Phone Last Updated Date

Master John Smith M 123456789 30/03/2021

28 Chapter 2: Defining business entities

Source record with an old last updated date
When you ingress a source record with an older last updated date compared to the last updated date of the
master record, the master record changes only if you enable Force Record Update.

The following table lists the new data from the Loan source system to ingress:

Source System First Name Last Name Gender Phone Source Last Updated Date

Loan Johnson Smith M 332244556 29/03/2021

When Force Record Update isn't enabled

For example, if you don't enable Force Record Update and ingress new data from the Loan source system,
based on the last updated date of the Loan record, the master record remains unchanged.

The following table lists the Savings, Loan, and Master records after you ingress new data:

Source System First Name Last Name Gender Phone Source Last Updated Date

Savings John Smith M 123456789 30/03/2021

Loan Johnson Smith M 332244556 29/03/2021

Master John Smith M 123456789 NA

When Force Record Update is enabled

However, if you enable Force Record Update and ingress new data from the Loan source system, based on
the last updated date of the Loan record, the master record changes.

The following table lists the Savings, Loan, and Master records after you ingress new data:

Source System First Name Last Name Gender Phone Source Last Updated Date

Savings John Smith M 123456789 30/03/2021

Loan Johnson Smith M 332244556 29/03/2021

Master Johnson Smith M 332244556 NA

Source record with a newer last updated date

When you ingress a source record with a newer source last updated date, the master record is updated.

For example, you want to ingress a new record from the Loan source system.

The following table lists the data in the new record from the Loan source system:

Source System First Name Last Name Gender Phone Source Last Updated Date

Loan John S M 976597654 01/04/2022

When you ingress the updated record from Loan source system, the changes for the master record are
accepted. The master record is updated because the source last updated date of the new record from the

Example: Ingress data with source last updated date 29

 Loan source system is 01/04/2021, which is newer than the source last updated date of the existing record
from the same source system.

The following table lists the Savings, Loan, and Master records before you ingress records from the Loan
source system:

Source System First Name Last Name Gender Phone Source Last Updated Date

Savings John Smith M 123456789 30/03/2021

Loan Johnson Smith M 332244556 29/03/2021

Master Record John Smith M 123456789 Not applicable

The following table lists the Savings, Loan, and Master records after you ingress the new record from the
Loan source system:

Source System First Name Last Name Gender Phone Source Last Updated Date

Savings John Smith M 123456789 30/03/2021

Loan John S M 976597654 01/04/2022

Master Record John S M 976597654 Not applicable

Edit a business entity

When you edit a business entity, you can add and edit business entity fields, and change data quality and
survivorship configurations. Your user role must have the privileges required to edit the business entity.

Note: You can't delete business entity fields.

1. From the Explore page, find and open the business entity.
2. Click the Actions icon, and then click Properties.
The Business Entity dialog box appears.
3. Edit the property values, and click OK.
4. Optionally, edit fields.
a. To show the fields that you want to edit on the canvas, select one of the following values from the
Show list:
• All Fields. Displays all the fields.
• Enabled Fields. Displays only the enabled fields. Default is Enabled Fields.
• System Fields. Displays only the system fields, which are automatically added to a record by
MDM SaaS. Some examples of system fields include Business ID, Record State, or Created By.
b. Select a field if you want to edit the field properties.
c. To edit field properties, edit the values in the Properties panel.
For example, to disable a field, select Disabled.

30 Chapter 2: Defining business entities

5. Optionally, add fields.
a. Double-click a field to add the field to the canvas.
b. Define the properties.
6. Save the business entity.
A confirmation dialog box appears.
a. To generate indexes for the records immediately, click Save and Index.
b. To generate indexes for the records at a later point in time, click Save without Indexing.
If you choose to index the records later, the records continue to use the outdated indexes.
Note: If the business entities include internal schema updates, you might get a prompt to index the
business entity records . If you are prompted to index the records, ensure that you index the records to
apply the internal schema updates. If you choose to index the records later, the records continue to use
the indexes based on the older schema.
Effective in the October 2023 release, business entities include internal schema updates and you can
index the business entity records when you edit business entities. These functionalities are available for
preview.
Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in
production environments or any environment that you plan to push to production. Informatica intends to
include the preview functionality in an upcoming release for production use, but might choose not to in
accordance with changing market or technical circumstances. For more information, contact Informatica
Global Customer Support.

Edit a business entity 31

Chapter 3

Defining reference data

Reference data is a set of values that you can use in a business entity picklist field. Use reference data, such
as countries, currency codes, and cost centers, to standardize the use of values. You can manually create
reference data, import from a file, or use reference data created in Reference 360.

For example, a Country reference data might contain a list of all the countries in the world. If you need a
Country field in a business entity, add a Country picklist field that has values sourced from the Country
reference data.

You can use reference data that are dependent on other reference data to provide context for values that are
not unique, such as the names of cities. For example, to uniquely identify a city, you need the state and
country of the city. Also, dependent reference data narrows down a large set of values. For example, when
the City reference data is dependent on the Country and State reference data, only the cities within the
selected state of a country are listed.

Reference data includes code values, which are unique values, such as business terms, codes, and lookup
values. When you use the predefined data model, reference data such as gender, countries, and currencies
are available by default.

Note: You can't open a reference data and add code values and crosswalks in Business 360 Console. Use
Reference 360 to open a reference data and add code values and crosswalks for reference data.

Rules and Guidelines for using reference data

Consider the following guidelines when you use reference data in Business 360 Console:

• You can't edit reference data in Business 360 Console. To add or edit code values and crosswalks to
reference data, use Reference 360. You require the Reference 360 Business Steward user role.
• When you select reference data created in Reference 360, Business 360 Console publishes the reference
data. You can view the published reference data on the Explore page.
• You can't publish a reference data configured with workflow approval process from Reference 360 to
Business 360 Console.
To publish the reference data and use it in Business 360 Console, the reference data must be published in
Reference 360.
• You can't publish a hierarchical code list from Reference 360 to Business 360 Console.
When you delete a predefined code list and create a hierarchical code list for the reference data set in
Reference 360, Business 360 Console considers the hierarchical code list as the predefined code list. If
you select a hierarchical code list from Reference 360, Business 360 Console can't publish and use the
reference data. Ensure that you don't delete the predefined code list in Reference 360.

32
Create reference data
Create reference data and configure at least the required properties, such as display name and location. To
create dependent reference data, first create the parent reference data.

1. Click New.
The New Asset dialog box appears.
2. Select Model as the asset type that you want to create.
3. Click Reference Data, and then click Create.
The Reference Data dialog box appears.
4. Specify the reference data properties.

Property Description

Display Name Required. Name of the reference data that you want to appear in the Business 360 applications.
Note: You can view the reference data in Reference 360. You can't change the display name from
Reference 360.

Description Optional. A description of the reference data.

Location Required. Project or folder within which you want to save the reference data.

5. Click OK.
The reference data is created and the Summary page appears.
6. Optionally, define a dependent reference data structure that depends on code values in another
reference data.
a. Select Dependent.
b. In the Parent Reference Data field, click the asset picker.
The Select an Asset dialog box appears.
c. Select a parent reference data asset, and click Select.
7. Click Save.
You can use the reference data when you configure picklists in business entities.
For more information about adding reference data to a picklist field, see “Add a picklist” on page 17.

Create reference data 33

Chapter 4

Defining dynamic pools

Dynamic pool is a collection of fields and field groups that you can use as dynamic fields. You don't share
fields between dynamic pools. You can create multiple dynamic pools based on your use case and add
relevant fields and field groups to each pool.

For example, you can create two dynamic pools for consumer business entities, such as Product Data and
Supplier Data. You can add basic fields to a dynamic pool, but you can't add smart fields. To use the fields in
a pool as dynamic fields, configure a dynamic field definitions attribute to refer to the dynamic pool. For
more information about the dynamic field definitions attribute, see “ Add a dynamic field definitions
attribute” on page 20.

Note: Effective in the October 2023 release, the dynamic fields are available for preview, and you can create
dynamic pools and add fields and field groups to the dynamic pool.

Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in
production environments or any environment that you plan to push to production. Informatica intends to
include the preview functionality in an upcoming release for production use, but might choose not to in
accordance with changing market or technical circumstances. For more information, contact Informatica
Global Customer Support.

Create a dynamic pool

Before you create a dynamic pool, understand your data model so that you can add appropriate fields and
field groups to the dynamic pool.

1. Click New.
The New Asset dialog box appears.
2. Click Model > Dynamic Pool.
3. Click Create.
The Dynamic Pool dialog box appears.
4. Specify the dynamic pool properties.
5. Click OK.
The dynamic pool is created and a blank canvas appears.
6. Add the fields and field groups that you want to use as dynamic fields.
For more information about adding fields, see “Add fields to a business entity” on page 16.

34
 Note: When you add fields to a dynamic pool, if you mark a field as a required field, the corresponding
dynamic field definitions attribute appears as a required field in the business application. A business
user needs to enter values for the field while editing a record.
7. Click Save.

Create a dynamic pool 35

Chapter 5

Defining hierarchy models

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:

1. Create an Organization hierarchy model.

2. Add the Organization business entity as the top-level business entity.
3. Create a relationship from the Organization business entity to the Person business entity.
4. Define 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:

36
 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.

Note: Effective in the October 2023 release, the ability to configure searchable hierarchy models is available
for preview in Product 360 SaaS.

Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in
production environments or any environment that you plan to push to production. Informatica intends to
include the preview functionality in an upcoming release for production use, but might choose not to in
accordance with changing market or technical circumstances. For more information, contact Informatica
Global Customer Support.

Step 1. Create a hierarchy model

Create a hierarchy model and configure at least the required properties, such as display name, search and
location. For example, create an Organization hierarchy model to define relationships in your organization.

1. Click New.
The New Asset dialog box appears.
2. Click Model > Hierarchy > Create.
The Hierarchy dialog box appears.

Step 1. Create a hierarchy model 37

 3. Specify the hierarchy model properties.

Property Description

Display Name Required. Name of the hierarchy that you want to appear in Business 360 applications.

Description Optional. A description of the hierarchy.

Search Optional. You can enable the hierarchy to be searchable.

Location Required. Project or folder within which you want to save the hierarchy.

4. Click OK.
The hierarchy model is created, and the Hierarchy Designer appears.

Step 2. Configure the top-level node

Specify a business entity as the top-level node in the hierarchy model. For example, in the Organization
hierarchy model, you define the Organization business entity as the top-level node.

u In the Properties panel, select a business entity.

The selected business entity appears as the top-level node on the canvas.

Step 3. Add a node

Add a business entity node and relationship to a the top-level node. For example, add the Person business
entity and create a hierarchy relationship from the Organization business entity to the Person business entity.

1. Hover over the node from which you want to create a relationship and click Add Child.
An undefined node appears on the canvas.
2. In the Properties panel, select a business entity for the undefined node.
The Parent Relationships field populates based on the business entity selected.
3. Optionally, add additional nodes to the hierarchy.
4. Optionally, to add a recursive relationship, hover over the node for which you want to create a recursive
relationship, and click Recursive.
A relationship arrow pointing from the selected node to the same node appears.
5. Click Save.

38 Chapter 5: Defining hierarchy models

Step 4. Define relationship attributes (Optional)
Define attributes of a relationship so that users in Business 360 applications can provide additional
information about relationships.

For example, you might want to track whether your organization is actively engaging with customers. You
define a Status attribute for the relationship between the Organization to Person business entities. Then
users in Business 360 applications can specify that the status of the Informatica to John Smith relationship
is active.

1. In the Hierarchy Designer panel, select a relationship.

2. In the Attributes section, click Add.
The New Attribute dialog box appears.
3. Enter a name for the attribute.
4. Select an attribute type.
The following table describes the attribute types:

Attribute Type Description

Primary The attribute field appears wherever related records appear, such as the related records
section of the Record Details tab or the Hierarchy tab of a record.

Secondary The attribute field only appears on the Hierarchy tab of a record.

5. Select the data type allowed in the attribute field.

6. If you select the picklist value type, select the reference data set for the attribute field.
7. To define a default value for the attribute, select Yes.
When you select Yes, the Value field appears. Enter a default value for the attribute.
8. To reorder the attributes, click Up or Down beside the attribute that you want to move.
9. To define additional attributes of the relationship, repeat steps 2 to 5.
10. Click Save.

Step 4. Define relationship attributes (Optional) 39

Chapter 6

Defining relationships
You can define relationships between business entities that have some type of association.

The users of Business 360 applications, such as Customer 360 SaaS, can then define and visualize the
relationships between business entity records.

You can define multiple relationships for a business entity. A business entity can have a relationship with
other business entities or with itself. For example, you can define a relationship between the Organization
and Person business entities to indicate that an organization employs person. You can also define a
relationship from the Person business entity to the Person business entity to indicate a spouse relationship.

Relationship types
Records can be related based on hierarchical relationships, related record relationships, and business entity
record field relationships.

MDM SaaS supports one-to-one, one-to-many, and many-to-many relationships between business entities.
Configure one-to-one relationships using hierarchies or relationships. Configure one-to-many and many-to-
many relationships using business entity record fields. If a user has the necessary permissions, they can
view, add, edit, and manage relationships. Records can be related in the following ways:

• Hierarchical relationships
• Related record relationships
• Business entity field relationships

Hierarchical relationships
Hierarchical relationships connect two business entity records in a hierarchy. For example, the Informatica
record is the parent of the John Smith record.

You can view these relationships in a hierarchy or relationship graph for the record.

Related record relationships

Related record relationships connect related business entity records by using relationships. For example, the
John Smith record is related to the PX100 Keyboard record through the person to object relationship.

You can view these relationships in a relationship graph or related records component for the record.

Business entity record field relationships

Business entity record field relationships use a field to relate to business entity records. The users can
search for records and set them as field values.

Business entity record field relationships are maintained when you ingress or egress data.

40
 For example, you can add the following business entity record fields to the Person business entity:

• Professor
• Course
• Classroom

When the user creates a record, they select appropriate records for these fields to create relationships.

You can view these relationships in tabular format in the related records component for the record.

Create a relationship
Create a relationship and configure at least the required properties.

1. Click New.
The New Asset dialog box appears.
2. Click Model > Relationship.
3. Click Create.
The Relationship dialog box appears.
4. Specify the relationship properties.

Property Description

Relationship Name Required. Name of the relationship that you want to appear in Business 360 applications.

Internal ID Required. A unique relationship identifier, which is generated based on the name that you
enter. You cannot change the internal ID after you create the relationship.

Business Entity 1 Required. The first business entity from or to which you want to define a relationship.

Business Entity 2 Required. The second business entity from or to which you want to define a relationship.

Direction Required. The direction of the relationship between the business entities.
Select one of the following directions:
- Business Entity 1 to Business Entity 2. One-directional relationship from business entity
1 to business entity 2.
- Business Entity 2 to Business Entity 1. One-directional relationship from business entity
2 to business entity 1.
- Bi-directional. Bi-directional relationship between the business entities.

Location Required. Project or folder within which you want to save the relationship.

Description Optional. A description of the relationship.

5. Click OK.
The relationship appears on the Properties page.
6. Click Save.
The relationship appears on the Explore page.

Create a relationship 41
Define relationship attributes (Optional)
Define attributes for custom relationships so that users in Business 360 applications can provide additional
information about relationships.

Note: You can't define attributes for predefined relationships.

For example, you might want to track the period for which customers stay connected with your organization.
You define the Start Date and End Date attributes for the relationship between the Organization and
Customer business entities. Then users in Business 360 applications can specify the start date and the end
date for the relationship between Informatica and John Smith.

1. From the Explore page, find and open the relationship.

2. In the Attributes section, click Add Attribute.
The Add Attribute dialog box appears.
3. Specify the properties of the attribute.

Property Description

Label The attribute field label that you want to appear in business applications.

Internal ID A unique identifier that can't be changed later.

Data Type The data type of the attribute value that can't be changed later.

Attribute Type Determines whether the attribute appears on user interface components that have space
constraints. To ensure that an attribute appears on a user interface component, select Primary.
A secondary attribute doesn't appear on components with space constraints.
Note: You can configure up to two primary attributes for a relationship.

4. To reorder the attributes, click Move up or Move down beside the attribute that you want to move.
5. To define additional attributes for the relationship, repeat steps 2 and 3.
6. Click Save.

42 Chapter 6: Defining relationships

Index

A hierarchy models (continued)

defining 12, 34, 36
add field attributes
dynamic field definitions 20
dynamic field values 20
add fields
I
dynamic fields 19 Informatica Global Customer Support
assets contact information 6
business entities 8 Informatica Intelligent Cloud Services
hierarchies 12, 34, 36 web site 5
reference data 32
relationships 40
M
B maintenance outages 6
master data
business entities modeling prerequisites 7
defining 8 model See business entity
editing 30
reviewing 11
business entity
creating 11
N
customizing 10 nodes
properties 10 hierarchies, defining 38

C O
custom business entity out-of-the-box business entities
configuration process 9 reviewing 11

D P
data model picklists
defining 7, 13, 15 adding 17
data modeling adding dependent 18
prerequisites 7 defining 17
dependent predefined business entities
picklists, adding 18 reviewing 11
drop-down lists See picklists

R
F reference data
field properties about 32
configuring 21 creating 33
fields defining 32
business entities, defining 16 relationship
creating 41
defining 41

H defining attributes 42
relationships
hierarchy models about 40
about 12, 34, 36 defining 40
creating 37 hierarchies, defining 38

43
S U
status upgrade notifications 6
Informatica Intelligent Cloud Services 6
system status 6

W
T web site 5

top-level node
hierarchy models, defining 38
trust site
description 6

44 Index