Informatica Master Data

Management (MDM)

1
 Topic 13: Informatica Data Director (IDD)

2
Objectives

Following are the objectives of this topic:

•
Introduction to IDD
•
Describe IDD Architecture
•
Configure Subject Area and Child/Grandchild Subject Area
•
Configure IDD Lookups
•
Configure IDD Data Cleansing
•
Configure IDD Search and Matching
•
Configure IDD Hierarchy Management

3
Informatica Data Director (IDD)

Informatica Data Director (IDD)

•
It is a data governance application for Informatica MDM Hub that enables business
users to effectively create, manage, consume, and monitor master data

4
IDD Components

IDD Application
•
Main configuration and deployment unit for IDD
•
This is what business users see when they launch and log into IDD

IDD Configuration Manager

•
Web-based utility used to add, modify and manage IDD applications

IDD Configuration Files

•
IDD configuration file (XML), resource bundles, localization message bundles, online
help, and other auxiliary files
•
These can be loaded of modified in the IDD configuration manager or exported and
edited manually

5
Subject Area

Subject Area(Entity Type)

• A subject area is a collection of data that should be treated as a unit from a business
perspective
• Has a single root record in a single base object
• Has some number of child records

Subject Area Group(BO)

• A set of one or more subject areas that have the same base object at their root
• For example, an ORS using a party model (a single base object representing different
entity types) will have a subject area group (Party) with multiple subject areas (Person,
Organization)
• Subject Area Group and Subject Area provide the high level menus for navigating data
in IDD application

6
Subject Area

Subject Area
•
A Subject Area can have the following configurations
•
Layout of form fields for primary object
•
Data cleansing/standardization/validation functions
•
Package for displaying search results
•
Data searching and matching ability
•
Children and Grandchildren records

Layout Configuration
•
Layout configuration allows you to choose which fields from the base object to include
in the user interface and how to show each record

Search Results Display Package

•
This package determines default table layout for search results
•
Primary table of package must be the same as primary table of subject area
•
If package contains joins to child tables, then it is possible for the package to return
multiple rows

7
Subject Area

Subject Area Relationships

•
IDD understands relationships within subject areas through the match paths that are
configured in MDM
•
A subject area can have the following types of relationships:
•
Child subject areas
•
Grandchild subject areas
•
Sibling references
•
Child Subject Area – Type of Relationships:
•
One:Many - Logical 1:1 and 1:Many
•
Many:Many – Part-Of and Reference
•
Grandchild Subject Area – Type of Relationships:
•
1:Many Grandchild
•
Many:Many Grandchild

8
IDD Data Cleansing

Cleansing, Standardization, and Validation

•
IDD allows you to use cleanse functions already defined in MDM to cleanse,
standardize and validate the input data
•
It is an optional feature for Subject Areas and Subject Area Child
•
It can include address standardization and validation
•
It can include data augmentation from other sources like D&B
•
Each subject area or child subject area can have one cleanse function associated with
it

9
IDD Data Cleansing

Validation Status
•
The cleanse function can reports if it is configured with the validationStatus output
•
If validation errors are found, then the Save or Apply action does not proceed
•
Format of the output is <columnName>.<messageKey> separated by ‘;’
•
Example: FIRST_NAME.canNotBeNull;IS_VALID_IND.invalidIndicator
•
columnName is the name of the input column that has a validation error
•
messageKey is a key to a message
•
messageKey value should be added in IDD application file MessageBundle.properties
•
Format: validation_<messageKey>=Message Text
•
Example: validation_canNotBeNull=This field cannot be empty

1
IDD Searching and Matching

Search
•
Search allows an end user to specify conditions for selecting data for review
•
A search can be based on data in the:
•
Primary Object Record
•
Any of its Child Records
•
Any records related via a Match path Component
•
Two types of searches are provided in IDD:
•
Basic Search
•
Extended Search

1
IDD Searching and Matching

Basic Search
•
It is a SQL-based search that finds results using string pattern comparisons
•
Case-Sensitive
•
Can use any attributes from the Subject Area
•
Wildcards (% or *) can be used in the Search
•
In the IDD application the end-user can create their own Search template
•
When defining an IDD application you should create a default public search for each
subject area

1
IDD Searching and Matching

Extended Search
•
Uses Match Engine to Search
•
Searches are “fuzzy” i.e. will find records that are similar to input criteria,, but that are
not textually identical
•
Match column must already be defined in MDM

1
Topic 14: IDD Workflow and Tasks
Click to edit Master subtitle style

1
Objectives

Following are the objectives of this topic:

•
Overview of Workflow and Tasks
•
Describe Tasks and Task Types
•
Describe Action and Action Types
•
Task Notification and Assignment

1
Workflow and Tasks

Workflow
•
Workflow represents the management of steps in a business process
•
It specifies what tasks need to be done, in what order, and who has permission to
perform each task
•
Base Objects must have State Management enabled in the Schema
•
IDD provides workflow support for:
•
Task creation and editing
•
Task assignment to users
•
Task approval or rejection

Task
•
A task represents a pre-defined step in a user’s business process which is executed by
a particular role
•
IDD comes with a set of pre-defined task types
•
These can be modified and additional task types can also be added

1
Workflow and Tasks

Pre-defined Tasks
•
The IDD default configuration includes seven pre-defined tasks
•
The task definitions may be modified by the user and new tasks can be added as
necessary
Action Type Description
UpdateWithApproval Update a record and the next step requires the user to go through an
approval process before completing the task.
UpdateWithOptionalApproval Update a record and the next step does not require the user to go
through an approval process before completing the task. The
approval step is optional.
ReviewNoApprove Review a change and either escalate or reject it. This task does not
provide an Approve option and requires at least one other person to
review the changes as well.
FinalReview Review a change and approve, reject, or escalate.

Merge Merge records together.

Unmerge Unmerge an XREF record from a Base Object record

UpdateRejectedRecord Update a record that was rejected in an approval process

1
Workflow and Tasks

Action
•
An action has a specific effect on the base object being addressed by the task
•
Multiple actions are possible for a task, but only one may be executed at a time

Action Types and Actions

•
IDD comes with a set of pre-defined action types
•
These Action Types are available across the various Task Types

Assign Task
•
This action is not explicitly available to the user, but is invoked when a task is created
and a user assigned to task via the batch process and assignment daemon

1
Workflow and Tasks

Action Types

Action Type Description

Submit for Approval Submit a change for approval

Augment Reassign the task to another user for assistance

Complete Update Commit changes made to a subject area record

Approve Approve and commit changes made to a subject area record

Reject Reject changes and reassign to the user who made the
changes
Escalate Reassign the task to another reviewer for assistance

Reassign Reassign the task to another user/role

[ Merge ] [ Invoked via the “Merge” button ]

Unmerge Perform the unmerge operation defined by the task

[ Save Task ] [ Invoked via the “Save Pending Changes” button ]

Cancel Task Cancel the task by deleting it

1
Workflow and Tasks

Task Notification and Assignment

•
Task Notification Engine
•
Runs in the MDM Hub and sends email notifications to users on a configured internal
•
Task Assignment Engine
•
Runs in the MDM Hub and periodically assigns any unassigned tasks to the
configured users
•
cmxserver.properties file
•
Specify the Number of Hours between task notifications
•
Specify the Number of Minutes between automated task assignments
•
Specify the Maximum number of tasks automatically assigned to each user

2
Topic 15: Security Access Manager
(SAM)
Click to edit Master subtitle style

2
Objectives

Following are the objectives of this topic:

•
Overview of Security Access Manager (SAM)
•
Describe Resources
•
Describe Privileges
•
Describe Roles
•
Describe Users
•
Define Object and Task level Security
•
Define Data level Security

2
Security Access Manager (SAM)

Security Access Manager (SAM)

•
Informatica MDM’s comprehensive security framework
•
Enforces user authentication and access authorization
•
SAM applies primarily to users of third-party applications and Informatica Data Director
(IDD) wanting to access Informatica MDM resources

Security

Object Security
• Determine access to subject are data and the ability
to perform operation on that data in IDD MDM Security Access
Task Security (Workflow) Manager (SAM)
• Determine access to tasks and actions based on
roles that are defined in the workflow
Data-Level Security
• Determines which rows in a base object a role can IDD Security
access

2
Security Access Manager (SAM)

Security Access Manager (SAM)

•
A resource is configured to be secure
•
Each secure resource is configured with specific
privileges
•
A role can have access to one or more secure resources
•
A user is assigned one or more roles

2
Security Access Manager (SAM)

Resources
•
Resource is an ‘item’ that you wish to secure. 
•
Following resources can be protected (expose or hide to external applications):
•
Base objects, Dependent objects
•
Mappings, Packages, Remote packages, Cleanse functions
•
Match rule sets, Batch groups
•
Metadata, Content metadata, Metadata Manager
•
HM profiles, Audit table, Users table
•
A protected Hub resource can be configured as either private or secure:
•
Private - Hides this Hub resource from the Roles tool
•
Secure - Exposes the resource to the Roles tool

2
Security Access Manager (SAM)

Privileges
•
Privilege scopes the actions that can be performed on a secured resource
•
Secured resources can have the following privileges:

Privilege Description
Read View but not change data
Create Create data records in the Hub Store
Update Update data records in the Hub Store
Merge Merge and unmerge data
Execute Execute cleanse functions and batch groups

2
Security Access Manager (SAM)

Roles
•
Set of privileges to access secure resources
•
To access a secure resource, the user must be assigned a role that grants them
sufficient privileges

Group 2 Role 3 Role 4

Group 1 Role 1

User 2 Role 2

2
Security Access Manager (SAM)

Security Access Manager

Roles

Secure
Resources Assigned
Privileges

2
Security Access Manager (SAM)

Object-Level Security

Role privileges are configurable for subject areas and child/grandchild subject areas

Column Access

Read privileges can selectively be disabled for columns so that users cannot see them in
IDD

Similarly, enable READ and disable UPDATE for columns

2
Security Access Manager (SAM)

Task-Level Security
•
All secured tasks require READ privileges on the subject area to which the task
belongs
•
All secured tasks require EXECUTE privileges on Task Type SA
•
Exception to this are Merge and Unmerge tasks
•
Merge task needs privileges on SA/Merge task type
•
Unmerge task needs privileges on SA/Unmerge task type

3
Security Access Manager (SAM)

Data-Level Security
•
Restricting users from seeing certain records based on the contents of those records
•
Within the search configuration of each subject area, security filters can be defined
•
Security filter specifies a condition that IDD applies to any searches conducted by
users assigned to a specific role
•
For example, a security filter can specify COUNRY_CODE = ‘US’, which can apply to
users with the US Data Steward Role
•
Each filter can apply to multiple roles
•
Multiple filters for the same role and subject area are treated as OR condition

3
Topic 16: IDD Dashboard, Merge & Unmerge and
Hierarchy Management
Click to edit Master subtitle style

3
Objectives

Following are the objectives of this topic:

•
IDD Dashboards
•
Merge process and Unmerge process
•
Hierarchy Management

3
IDD Dashboards

3
Merge and Unmerge Process

3
Hierarchy Management