Informatica® Business 360 Console

July 2023

Configure Data Quality

Informatica Business 360 Console Configure Data Quality
July 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-07-31

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

Chapter 1: Configuring data quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2: Types of rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Basic rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Advanced rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Guidelines for advanced rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
DaaS rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Integrity checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3: Adding basic rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4: Changing the execution order of basic rule associations. . . . . . . . . . 12

Chapter 5: Adding advanced rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 6: Deleting rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 7: Adding DaaS rule associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

DaaS rule association for batch processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Adding DaaS rule association to address field groups. . . . . . . . . . . . . . . . . . . . . . . . . . . 16
DaaS rule association for real-time processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Guidelines for real-time address verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Adding a DaaS rule association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
DaaS rule associations for email and phone verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 8: Adding integrity checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table of Contents 3
Preface
Follow the instructions in Configure Data Quality to associate data quality rules with the business entity fields
to validate the field values.

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/

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

Preface 5
Chapter 1

Configuring data quality

You can associate data quality rules with the business entity fields to cleanse, standardize, or validate the
field values. For example, you can remove unwanted punctuation marks or spaces, standardize the date
format, or verify phone numbers. Data quality rules help improve the quality and consistency of data.

You can associate data quality rules based on simple conditions, Cloud Data Quality, and DaaS with business
entity fields. You can also add integrity checks to business entity fields only. When you add or import records,
the rule associations validate and transform the records, and store them in the data store.

When validation fails, you can downgrade the trust score of the field, and that helps determine the confidence
level of the source data.

Note: When you configure data quality rules for picklists, MDM SaaS runs the data quality rules on the code
values of the selected reference data. The rule validation considers only the code and not the name of the
code value.

For example, if you configure a basic rule association with a lowercase function for the Country picklist, MDM
SaaS runs the rule association on the code IN. It doesn't run the rule association on the name India.

6
Chapter 2

Types of rule associations

You can create different types of rule associations for business entity fields.

Use the following rule association types:

• Basic rule associations

• Advanced rule associations
• DaaS rule associations
• Integrity checks

Basic rule associations

A basic rule association is an association between a business entity field and a simple condition-based rule.
When you create basic rule associations, you configure conditions, which are predefined functions, such as
Regular Match and Concatenate.

For example, Smith Store wants to master data from a newly acquired business. Smith Store wants to
combine the first name and last name of each customer to generate the full name to print on the receipt.
Smith Store can associate a basic rule with the Full Name field and concatenate the first name and last name
values.

Note: You can't add basic rule associations for boolean fields.

When you configure basic rule associations, you configure conditions that transform or validate field values.
To set the conditions, you can use the predefined validation functions or the predefined transformation
functions. A validation function validates whether data matches the specified condition. A transformation
function transforms source data.

The following table describes the validation functions that you can use:

Function Description

Maximum Length Validates whether the length of a string is less than or equal to the specified length.

Minimum Length Validates whether the length of a string is greater than or equal to the specified length.

Starts With Validates whether a string starts with the specified string.

Ends With Validates whether a string ends with the specified string.

7
 Function Description

No Spaces Validates whether a string does not contain spaces.

Contains Validates whether a value contains the specified string in the exact order.

Does Not Contain Validates whether a value does not contain the specified string in the exact order.

Allowed Validates whether a value contains the specified allowed characters.

Characters

Not Allowed Validates whether a value contains the specified characters that are not allowed.
Characters

Regular Match Validates whether a string matches with the specified regular expression pattern.

External Validates the field data based on an external validation rule that is associated to a Cloud
Validation Application Integration process. The Cloud Application Integration process uses external APIs to
validate the data.
For more information about creating a process, see Cloud Application Integration Design.

Date Range Validates whether a date is in between two specified dates.

Greater Than Date Validates whether a date is greater than the specified date.

Lesser Than Date Validates whether a date is less than the specified date.

No Future Date Validates whether a date is not a future date.

Maximum Decimal Validates whether the number of decimal places is less than or equal to the specified value.
Scale

Minimum Value Validates whether a numerical value is greater than or equal to the specified value.

Maximum Value Validates whether a numerical value is less than or equal to the specified value.

Maximum Validates whether the total number of digits in a decimal number is less than or equal to the
Precision specified value.

Note: When you define a basic rule association with a maximum or minimum value, the rule considers only
the first 16 digits of numeric values. For example, if you specify 20 as the maximum value and the input is
20.09123456904589098743, the rule considers 20.09123456904589 and ignores the remaining digits.

The following table describes the transformation functions that you can use:

Function Description

Concatenate Concatenates two or more strings.

Concatenate With Concatenates two or more strings with spaces in between.

Spaces

Uppercase Converts lowercase string characters to uppercase.

Lowercase Converts uppercase string characters to lowercase.

8 Chapter 2: Types of rule associations

 Function Description

Title Case Capitalizes the first character in each word of a string and converts all other characters to
lowercase.

Left Trim Removes spaces from the beginning of a string.

Right Trim Removes spaces at the end of a string.

Replace Replaces a character set in a string with another character set.

Advanced rule associations

An advanced rule association is an association between business entity fields and a Cloud Data Quality rule
specification. You can use the predefined rule specifications, or create custom rule specifications in Cloud
Data Quality and use them.

The supported predefined rule specification is DUNS SSN Validation that validates the DUNS and Social
Security numbers.

You can create advanced rule associations to validate input fields that are empty. Based on the rule
specification, the advanced rule association validates the input fields in the business application. If the input
fields are empty, the rule returns a value for the empty fields.

For more information about creating or editing rule specifications in Cloud Data Quality, see Rule
specification assets in Cloud Data Quality.

Guidelines for advanced rule associations

When you define advanced rule associations, you need to define rule outputs.

Consider the following guidelines to define advanced rule associations:

• To ensure the success of the business entity field comparison operation in Business 360 Console, use
integer or string values in the rule statement output in Cloud Data Quality.
• When you configure an advanced rule association for a transformation function, set rule statement output
values for all the conditions in Cloud Data Quality to generate values in the output field.
• When you modify a rule specification in Cloud Data Quality, select the rule specification again or reset the
fields of the advanced rule association in Business 360 Console. Otherwise, the changes to the rule
specification aren't effective when the rule is executed.
• Advanced rule associations for date fields with a rule specification that contains the current_timestamp
function in Cloud Data Quality return the output in the UTC timezone. To display the date field in other
timezones, configure the rule specification with a different timestamp function.
• When you configure advanced rule association in Business 360 Console, ensure that you don't select a
rule specification configured with advanced mode from Cloud Data Quality.

Advanced rule associations 9

DaaS rule associations
A DaaS rule association is an association between a field group and Informatica Data as a Service (DaaS).

You can use the DaaS rule association only on the fields that store postal addresses, email addresses and
phone numbers. To use the required DaaS services, add valid license keys in the Global Settings page.

Integrity checks
You can configure integrity checks to validate business entity records. Integrity checks are a unique type of
data quality check that can only be configured for the business entity record attributes.

You can configure integrity checks based on the following criteria:

• Business entity attribute. Checks the business entity records based on other business entity attributes
and values. For example, you can configure an integrity check to verify that the date of incorporation for a
company is before or after a specific date.
• Relationship attribute. Checks the business entity records based on relationship attributes. For example,
you can configure an integrity check to verify that a relationship exists between an employee and an
organization from a specific date.
• Relationship. Checks the business entity record to verify that a specific relationship exists. For example,
you can configure an integrity check to verify that a relationship exists between an employee and a
manager.

If a business entity record fails an integrity check, a warning appears in the related records table. To help
users understand the warning, you must also configure an error message for each integrity check.

10 Chapter 2: Types of rule associations

Chapter 3

Adding basic rule associations

When you use a validation predefined function, ensure that you configure the validation message.

1. On the business entity page, select a field to associate rules.

2. In the Properties section, click Data Quality > Basic.
3. Click Add Basic Rule Association.
A form appears.
4. In the General section, enter a unique name for the rule association.
5. Optionally, enter a description.
6. On the Condition tab, perform the following tasks:
a. Select a function.
b. For the input field, select an option from the list.
c. If you select Select a Field, select a business entity field from the list.
d. If you select Enter a Value, type a value for validation.
7. If you select a validation function, on the Validation tab, perform the following tasks:
a. Select one of the following severity levels for the validation failure:
• Information. For minor data quality issues. The users can save the data.
• Warning. For less severe data quality issues. The users can save the data.
• Error. For severe data quality issues. The users cannot save the data.
Note: Severity of the validation failure is applicable only when you ingress data or create records in
real time.
b. Enter an error message to display.
c. Enter the percentage of trust score to downgrade when the validation fails.
Note: Severity of the validation failure and trust score downgrade are applicable only when you
ingress data.
8. To verify the created rule, perform the following tasks:
a. Click Test.
The Test dialog box appears.
b. Enter values in the Input column, and click Run.
The validation result appears in the Output column.
c. Click Close.
9. Click Save.

11
Chapter 4

Changing the execution order of

basic rule associations
When you have multiple basic rule associations for a business entity field, set their order of execution to
obtain clean and correct data. For example, if you want to concatenate the first name and last name of a
person, you might need to validate the length of the strings first. In this case, you first run the rule
association to validate the length of the names, and then run the rule association to concatenate the names.
If a business entity field contains basic and advanced rule associations, the basic rule associations run first.

1. On the Basic tab, click Change Order.

The Change Order dialog box appears.
2. Use the up and down arrows to change the order of the rule associations.
3. Click OK.
The list of rule associations with the updated order of execution appears.

12
Chapter 5

Adding advanced rule

associations
Use Cloud Data Quality rule specifications to add advanced rule associations for business entity fields.

1. On the business entity page, select a field to associate rules.

2. In the Properties section, click Data Quality > Advanced.
3. Click Add Advanced Rule Association.
A form appears.
4. To validate inputs fields that are empty, enable Run rule association even if all input fields are empty.
5. To select a rule specification, perform the following tasks:
a. Click the asset picker.
The Select an Asset page appears.
b. Select a rule specification, and click Select.
6. Enter a unique name for the rule association.
7. Optionally, enter a description.
8. On the Input and Output Fields tab, perform the following tasks:
a. In the Input Fields section, select a business entity field or enter an input value for each rule
specification field.
b. In the Output Fields section, select a business entity field for each rule specification field.
9. On the Validation tab, perform the following tasks:
a. In the Rule Status section, select a rule specification field that contains the validation status.
b. Enter a validation status that indicates successful validation.
Note: Ensure that the validation status matches the rule specification output value for successful
validation.
c. In the Error Status section, select one of the following options to define the severity of the validation
failure:
• Information. For minor data quality issues. The users can save the data.
• Warning. For less severe data quality issues. The users can save the data.
• Error. For severe data quality issues. The users cannot save the data.
Note: Severity of the validation failure is applicable only when you ingress data or create records in
real time.

13
 d. To configure the error message, select one of the following options:
• From Rule Specification Field. Select a rule specification field that contains error message.
• Custom Message. Enter a custom error message.
e. Select a field to use to downgrade the trust score.
Note: Trust score downgrade is applicable only when you ingress data.
f. Enter the percentage of trust score to downgrade when the validation fails.
g. Click Save.

14 Chapter 5: Adding advanced rule associations

Chapter 6

Deleting rule associations

You can delete basic or advanced rule associations that you no longer need. You can delete rule associations
for fields in the Properties section or on the Data Quality tab.

Note: You can't delete predefined basic and advanced rule associations.

1. On the business entity page, select a field that has rule associations.
2. To delete a basic rule association, click Data Quality > Basic in the Properties section.
3. Hover over the basic rule association to delete, and click Delete.
4. To delete a advanced rule association, click Data Quality > Advanced in the Properties section.
5. Hover over the advanced rule association to delete, and click Delete.

15
Chapter 7

Adding DaaS rule associations

Use DaaS rule associations to validate and enrich postal addresses in batches and real time. You can also
use DaaS rule associations to validate email addresses and phone numbers in real time.

To validate and enrich addresses in batches, a DaaS rule association uses an address verifier asset from
Cloud Data Quality. To validate and enrich addresses in real time, a DaaS rule association uses Informatica
Address Verification. To validate email addresses in real-time, a DaaS rule association uses Informatica
Email Verification. To validate phone numbers in real time, a DaaS rule association uses Informatica Global
Phone Validation.

For more information about adding license details, see Configure Global Settings.

DaaS rule association for batch processing

To validate and enrich the address values in the records that you import in bulk, use the predefined address
verifier asset from Cloud Data Quality. The predefined address verifier asset contains a predefined mapping
of the input and output fields.

Note: You can't add a DaaS rule association to validate and enrich an email, phone, and custom field groups
in batches.

Adding DaaS rule association to address field groups

You can verify and enrich the postal addresses in the records with the Cloud Data Quality address verifier. To
validate the address data that you import in bulk, add DaaS rule associations to the field groups that store
postal addresses.

1. On the business entity page, select a field group that stores postal addresses.
2. In the Properties section, click Data Quality > DaaS Batch.
3. To enable DaaS validation, select Enable DaaS Validation.
Note: When you enable DaaS validation, you can't add basic and advanced rule associations to the fields
in the field group.
4. Click Configure Address Verification.
5. In the Verifier field, view the preselected Address Verifier asset.
Note: By default, the predefined address verifier asset is selected. For more information about the
address verifier asset, see the Informatica Cloud Data Quality Online Help.

16
6. On the Input and Output Fields tab, view the input and output fields that are mapped to the business
entity fields.
For more information about the input and output field mappings, see “Predefined mapping of input and
output fields” on page 17.
7. On the Validation tab, perform the following tasks:
a. In the Error Status section, select the severity of the validation failure.
b. Enter a custom error message.
c. In the Trust Score section, select the fields to use to downgrade the trust score.
d. Enter the percentage of trust score to downgrade when the validation fails.
8. Click Save.

Predefined mapping of input and output fields

Ensure that you don't modify the input and output field mappings in Cloud Data Quality.

The following table lists the input fields of the address verifier asset and their mapped business entity fields:

Address Verifier Field Data Type Business Entity Field

Address Lines 1 String Address.Address Line 1

Address Lines 2 String Address.Address Line 2

Address Lines 3 String Address.Address Line 3

Postal Code 1 String Address.Postal Code

Locality 1 String Address.City

Administrative Division 1 String Address.County

Country 1 String Address.Country

The following table lists the output fields of the address verifier asset and their mapped business entity
fields:

Address Verifier Field Data Type Business Entity Field

Postal Code 1 String Address.Postal Code

Locality 1 String Address.City

Administrative Division Name String Address.County

2

Address Lines 1 String Address.Address Line 1

Address Lines 2 String Address.Address Line 2

Address Lines 3 String Address.Address Line 3

DaaS rule association for batch processing 17

 Address Verifier Field Data Type Business Entity Field

Verification Status Code String Address.Verification Status Code

Result Quality String Not mapped to any field.

Geo Coordinates String Address.Coordinate System

Geo Coordinates Latitude String Address.Latitude

Geo Coordinates Longitude String Address.Longitude

DaaS rule association for real-time processing

To validate and enrich addresses in real time, Business 360 Console uses Informatica Address Verification
as the default DaaS provider. The address verification DaaS provider contains predefined input and output
fields to use in DaaS rule associations. You can also enrich the email addresses and phone numbers in real-
time.

The predefined field group comes configured with a default DaaS rule association and a mapping of the
address verification DaaS provider fields and business entity fields. You can also create a DaaS rule for
custom field groups and map the input and output fields as required.

Guidelines for real-time address verification

Consider the following guidelines before you create a DaaS rule association for real-time address verification:

• You can’t create a DaaS rule association or edit the predefined DaaS rule association for the predefined
postal address field group.
• You can add one DaaS rule association at each level within nested custom field groups.
• Before you create a DaaS rule association, ensure that you save any changes to fields of the business
entity.
• Ensure that you map a business entity field to the Country field of the Address Verification DaaS provider.
Note: If you don't map any of the business entity fields to the Country field, the rule can't validate or enrich
the values of the address fields in real time.
• Unlike email and phone validation, if users add an incorrect address in the business application, real-time
address verification doesn't display the validation error during record creation. The validation error
appears after the user submits the record.

Adding a DaaS rule association

You can add a DaaS rule association to field groups in your business entity.

1. On the business entity page, select a postal address field group or any custom field group that stores
postal addresses.
2. For a predefined postal address field group, perform the following steps:
a. In the Properties section, click Data Quality > DaaS Real-time.

18 Chapter 7: Adding DaaS rule associations

 b. View a predefined rule that contains a default input and output field mapping.
For more information about the predefined input and output field mapping, see “Predefined mapping
of input and output fields” on page 19.
3. For a custom field groups, perform the following steps:
a. In the Properties section, click Data Quality > DaaS.
b. Click Add Rule.
A form appears.
c. On the Select Data Provider tab, enter a unique name for the rule association.
The predefined rule type is DaaS.
d. To enable the rule, select Enable Rule.
e. Select a data provider to enrich the address values.
The supported data provider is Address Verification DaaS.
f. In the Input and Output Fields of the Data Provider section, view the input and output fields of the
data provider.
g. Click Next.
h. On the Map Input and Output Fields tab, enter a unique name for the field mapping.
i. In the Input Field Mapping section, to map fields, drag the business entity fields to the data provider
fields.
j. In the Output Field Mapping section, to map fields, drag the data provider fields to the business
entity fields.
k. Click Save.
After you save the DaaS rule association, Business 360 Console automatically saves the business entity if
you don't have any other changes in the business entity.

Predefined mapping of input and output fields

You can view a predefined input and output field mapping of the Address Verification DaaS data provider and
business entity fields.

The following table lists the input fields of Address Verification DaaS data provider and their mapped
business entity fields:

Address Verification DaaS Data Provider Field Field Type Mapped Business Entity Field

Address Elements > Country Text Country

Postal Code > Postal Code 1 Text Postal Code

Locality > Locality 1 Text City

Administrative Division > Administrative Division 1 > Text County

Extended

Preformatted data > Postal Delivery Address Lines > Address Text Address Line 1
Lines 1

DaaS rule association for real-time processing 19

 Address Verification DaaS Data Provider Field Field Type Mapped Business Entity Field

Preformatted data > Postal Delivery Address Lines > Address Text Address Line 2
Lines 2

Preformatted data > Postal Delivery Address Lines > Address Text Address Line 3
Lines 3

Additional Fields > Text Field 1 Text State

Additional Fields > Text Field 2 Text Address Type

Additional Fields > Text Field 3 Text Usage Type

Additional Fields > Text Field 4 Text Address Status

Additional Fields > Text Field 5 Text Postal Code Extension

Additional Fields > Boolean Field 1 Boolean Default Indicator

Additional Fields > DateTime Field 1 DateTime Start Date

Additional Fields > DateTime Field 2 DateTime End Date

The following table lists the output fields of the business entity and their mapped Address Verification DaaS
data provider fields:

Business Entity Field Field Type Mapped Address Verification DaaS Data Provider Field

Default Indicator Boolean Enrichments > Additional Fields > Boolean Field 1

Address Type Text Enrichments > Additional Fields > Text Field 2

Usage Type Text Enrichments > Additional Fields > Text Field 3

Address Status Text Enrichments > Additional Fields > Text Field 4

Address Line 1 Text Preformatted data > Postal Delivery Address Lines > Address
Lines 1

Address Line 2 Text Preformatted data > Postal Delivery Address Lines > Address
Lines 2

Address Line 3 Text Preformatted data > Postal Delivery Address Lines > Address
Lines 3

Country Text Address Elements > Country > Code

State Text Enrichments > Additional Fields > Text Field 1

City Text Address Elements > Locality > Locality 1

County Text Address Elements > Administrative Division > Administrative

Division 2 > Extended

20 Chapter 7: Adding DaaS rule associations

 Business Entity Field Field Type Mapped Address Verification DaaS Data Provider Field

Postal Code Text Address Elements > Postal Code > Postal Code 1

Postal Code Extension Text Enrichments > Additional Fields > Text Field 5

Coordinate System Text Enrichments > Geo Codes > Arrival Point > Coordinates

Start Date DateTime Enrichments > Additional Fields > DateTime Field 1

End Date DateTime Enrichments > Additional Fields > DateTime Field 2

Latitude Text Enrichments > Geo Codes > Arrival Point > Latitude

Longitude Text Enrichments > Geo Codes > Arrival Point > Longitude

Enriched Indicator Text Enrichments > Status Codes > Enriched Indicator

Verification Status Code Text Enrichments > Status Codes > Verification Status Code

Verification Message Text Enrichments > Status Codes > Verification Status Message

DaaS rule associations for email and phone

verification
You can validate email addresses and phone numbers for the records that you create in real time. You can
verify whether an email address or phone number exists and is formatted correctly.

1. On the business entity page, select a field group that stores email addresses or phone numbers.
2. In the Properties section, click DaaS.
3. To enable DaaS validation, select Enable DaaS Validation.
4. Select the severity of the validation failure.
5. Enter an error message to display when the validation fails.
6. Enter the percentage of trust score to downgrade when the validation fails.
7. Click Save.

DaaS rule associations for email and phone verification 21

Chapter 8

Adding integrity checks

You can configure multiple integrity checks to validate business entity record fields.

1. On the business entity page, select a business entity record field to configure an integrity check.
2. In the Properties section, click Data Quality.
3. Click Add Integrity Check.
The Add Integrity Check dialog box appears.
4. From the Based On list, select the option based on which you want to configure the integrity check.

Option Description

Business Entity Attribute Uses a business entity attribute value to check the field values.

Relationship Attribute Uses a relationship attribute value for the integrity check.

Relationship Uses a relationship for the integrity check.

5. If you select Business Entity Attribute, enter the following values:

Field Description

Applied Field The selected business entity record field for which you are configuring the integrity check. The
value is automatically populated.

Attribute Name of the attribute based on which you want to check the integrity of the selected business
entity record field. All attributes that belong to the related business entity of the business entity
record field appear.

Operator An operator to validate the attribute value. The available operators depend on the attribute type.

Value A value of the selected attribute.

6. If you select Relationship Attribute, enter the following values:

Field Description

In Relationship The second business entity that has a relationship with the business entity to which the
Between business entity record field belongs.

Relationship Type of relationship that exist between the two business entities.

22
 Field Description

Attribute Name of the relationship attribute based on which you want to check the integrity of the
business entity record field. All attributes associated with the selected relationship appear.

Operator An operator to validate the attribute value. The available operators depend on the attribute
type.

Value A value of the selected attribute.

7. If you select Relationship, enter the following values:

Field Description

Between The second business entity that has a relationship with the business entity to which the business
entity record field belongs.

Relationship Type of relationship that exist between the two business entities.

Condition A condition that uses the specified relationship to verify the integrity of the business entity record
field values.

8. Enter an error message to display in the business application when the integrity check fails.
9. Click Save.

23
Index

I system status 5

Informatica Global Customer Support

contact information 5
Informatica Intelligent Cloud Services
T
web site 4 trust site
description 5

M U
maintenance outages 5
upgrade notifications 5

S W
status
Informatica Intelligent Cloud Services 5 web site 4

24