Informatica World 2019

Accelerate Business
Outcomes by Leveraging
New Features in MDM 10.3
Claudio Nold `

Manager Global Customer Support

David Anantharajan
Principal Technical Support Engineer
 Safe Harbor
The information being provided today is for informational purposes only. The development,
release and timing of any Informatica product or functionality described today remain at the
sole discretion of Informatica and should not be relied upon in making a purchasing decision.
Statements made today are based on currently available information, which is subject to
change. Such statements should not be relied upon as a representation, warranty
or commitment to deliver specific products or functionality in the future.
2 © Informatica. Proprietary and Confidential.
Agenda

1 New Features in 2 Demonstration 3 Q&A

MDM 10.3

3 © Informatica. Proprietary and Confidential.

Highlights at a Glance: MDM 10.3

• Layout Enhancements
• Search Framework
• Security Enhancements
• Core Enhancements / Localization Support
• BPM Enhancements

4 © Informatica. Proprietary and Confidential.

10.3 Enhancements

Layout Enhancements
• Modern user experience provides consistent look and feel
• Configurable IDD/e360 application to reduce time to value
• Updated support screens improving usability

5 © Informatica. Proprietary and Confidential.

New Visual Design

Complete overhaul of
user interface
• Aligns with wider INFA efforts
for uniformity in product UX
• Narrows the gap between MDM
platform offering and Customer
360 solution

6 © Informatica. Proprietary and Confidential.

Matching Records View

Two screens to view matching records:

• Matching Records View (advanced):
- Previously known as Matching candidate
view (e360)
- Can operate at root level and child level
- New functionality in 10.3
- Improved UX

• Matching Records View (basic):

- Previously known as Legacy Merge view (IDD)
- Can operate only at root level
- Improved UX
7 © Informatica. Proprietary and Confidential.
Cross-Reference Records View

• Cross-Reference Records View:

- Just one screen (no basic vs. advanced)
- Previously known as Cross-Reference
View (e360)
- Can operate at root level and child level
- Improved UX

8 © Informatica. Proprietary and Confidential.

History View

9 © Informatica. Proprietary and Confidential.

New Layout Designer Workflow

• Updated configuration options for existing steps

• One new additional step

10.2 1 Properties 2 Purpose 3 Template 4 Design

10.3 1 Properties 2 User Roles 3 Purpose 4 Template 5 Design

*Updated *New *Updated *Updated

10 © Informatica. Proprietary and Confidential.

10.3 Enhancements

Updated search functionality

• ElasticSearch integration to provide full HA (High Availability) and
improved performance
• New query functionality using exact (database search) and fuzzy
(SearchMatch) capabilities
• Configuration option to use either SOLR, ElasticSearch or query to
meet customer- specific requirements

11 © Informatica. Proprietary and Confidential.

Background
• MDM 10.3 now has three options for providing search capabilities to users.
- SmartSearch is the term used to denote the search capability introduced in 10.0 and provides the
global search bar at the top of IDD. SmartSearch initially used SOLR as the backend to perform
searches and for MDM 10.3, we have the option of using SOLR or ElasticSearch.
- Solr is still available for upgrading customers who prefer not to make any changes to their current
architecture. This is not a recommended solution and we encourage all customers not to use
ElasticSearch option.
- ElasticSearch is our preferred SmartSearch engine from 10.3 onwards. It provides all the capabilities
of Solr but also provides full HA and scalability options as well provides further flexibility to expand
search capabilities in the future.

• Queries is a new functionality introduced in 10.3 built on the same use case as the subject
area query functionality. It allows users to build a query based on BE (Business Entity)
attributes, as well as save, share and run those queries. Queries can either be exact text-
based search or use Name3 matching algorithms.

12 © Informatica. Proprietary and Confidential.

Capabilities

• Smart Search and Queries are driven by Business Entity views.

Configure and specify the view you wish to use for search results
• Ability to export search results (visible columns or all columns
available on the root node)

13 © Informatica. Proprietary and Confidential.

Smart Search - ElasticSearch

14 © Informatica. Proprietary and Confidential.

Search Configuration

• Within Provisioning tool, you can

specify whether to use Smart Search
or Queries functionality
• If both are selected, then user is able
to specify which search capability is
used within the application for things
like adding potential candidates or
searching for related records

15 © Informatica. Proprietary and Confidential.

Queries Capability

• Queries provide you the capability to

create, save, share and execute queries
using exact or fuzzy searching capabilities
• Exact queries are based on BE and any
attribute can be used for searching
• Fuzzy queries use Name3 matching
algorithms and require user to specify
which algorithm they want to search with

16 © Informatica. Proprietary and Confidential.

Export search results

17 © Informatica. Proprietary and Confidential.

10.3 Enhancements

Improved security
• Data filters to support row level security
• SAM Integration to support data security and improved usability
• Configuring default values

18 © Informatica. Proprietary and Confidential.

Data Security Filters

• Data security filters restricts users from seeing certain records based on the contents in
the records and their user role. Each filter can apply to multiple roles.
- E.g. Data Steward should only be able to see records with addresses in their country. In the case
of US Data Stewards, a security filter can be configured so that all records with the field
“COUNTRY_CODE = US” will be available to US Data Stewards, and all other user roles are
disallowed from seeing the record contents.

• Previously, security filters were only available to subject areas.

In 10.3, the security filter functionality is extended to business entities.

19 © Informatica. Proprietary and Confidential.

How Security Filters Work

There are two types of filters: Allow and Deny

Allow: enables a user role to see the specified data
Deny: prevents a user role from seeing the specified data

20 © Informatica. Proprietary and Confidential.

How Security Filters Work (Continued)

Filters can be applied at the field and node level

Node filter: Can be added to child BE nodes and is used
to define a rule when the child has no records
Field filter: Can be added to data fields in the BE

Deny has precedence over Allow

21 © Informatica. Proprietary and Confidential.

Security Filter Behavior

The general rule is, “allow everything, except what is denied”

If no filter is configured, then all users can see the data
If a Deny filter has no values, then all users can see the data (whatever is Allowed to their role)
If there is only a Deny filter, and a user role isn’t part of that Deny filter, then the user can see the data
If an Allow filter is created for a field, but has no user roles or Other Roles configured, then all users
are not allowed to see the data

22 © Informatica. Proprietary and Confidential.

Default Values

• This feature allows you to set one or more default values for a field based on the user
role, allowing you to control what a user can enter into a record
• Default values can be set for fields either at the root level or for all instances of a child
• Default values can be used for data fields of any type including reference lookups

23 © Informatica. Proprietary and Confidential.

Configuring Default Values

Login to the Provisioning Tool

Navigate to Business Entity > Modeling
Choose a Business Entity type
and a field
Click the “+” bottom to add default
value rules
Value
User role
Other roles

24 © Informatica. Proprietary and Confidential.

SAM Integration

• Security Access Manager (SAM) provides role-based security privileges on design objects
and columns defined in an ORS. Depending on what user role is assigned to a user account,
that user can only see the data and utilize functionalities that they’ve been granted access to.
• In Entity 360, SAM has been integrated so that REST services and the E360 UI are aware of
these role-based security privileges.

25 © Informatica. Proprietary and Confidential.

SAM for Business Entities

• SAM can be used to control access to data and functionalities to entire business entities
or parts of business entities based on user role-based privileges
• The role privileges for a business entity include:
- CREATE, READ, UPDATE, DELETE, MERGE TASK, MERGE, UNMERGE TASK, UNMERGE,
SEARCH

26 © Informatica. Proprietary and Confidential.

10.3 Enhancements

Core improvements
• Updated PAM
- Support for Java 8
- Jboss 7.1 and Websphere 9 support in MDM 10.3 Hotfix 1

• Full localization support for IDD

27 © Informatica. Proprietary and Confidential.

Background

Localization ensures that all elements in the Entity 360 (E360) interface can be viewed
in the user’s local language. Users can select from a list of 10 different languages
Three types of texts that can be localized:
1. Static Data (titles, menu items, tool tips, etc.)
2. Metadata (base object names, fields, etc.)
3. Data (lookup table data)

28 © Informatica. Proprietary and Confidential.

Changing Language Preferences in 10.3

To change the language in 10.3, users can click on

their username, select Change Language, and
choose their preferred language

29 © Informatica. Proprietary and Confidential.

Localization in E360

The following elements are localized in the E360 UI:

• Metadata
- BE names, menu names, field names, task types and task actions, etc. can be localized

• Error messages
- Error messages can be localized

• Components (widgets)
- All components support localization

30 © Informatica. Proprietary and Confidential.

10.3 Enhancements

BPM enhancements
• Support for attachments for workflows
• Support for configurations for attachments and comments for tasks
• New options to improve usability of inbox and Task Management

31 © Informatica. Proprietary and Confidential.

Configuring Inbox and Task Manager

• Ability to customize the task manager by configuring the specific fields

that should be displayed and in which order
• Providing new filters (from “My Task” and “All tasks”)
• Ability to create different task inbox instances for customized start pages
with the specific filters required and also which columns will be displayed

32 © Informatica. Proprietary and Confidential.

Task Comments and Attachments

• Informatica BPM (ActiveVOS) allows for users to attach documents to workflows.

This can be used for business processes like Supplier Onboarding
• MDM uses the BPM API to load attachments to workflow. Only users allowed to
view tasks will be able to retrieve the documents
• Property file settings determine which file types are allowed. By default PDF and
JPG is allowed
- cmx.file.allowed_file_extensions=pdf,jpg,txt,zip,exe,bat
- Same parameter for attaching files to a BE

33 © Informatica. Proprietary and Confidential.

 Demonstration

34 © Informatica. Proprietary and Confidential.

Q&A
“Ask An Expert” is a unique new channel for
customers to engage with Informatica technical
experts live.

Features
• Easy online scheduling available with over 350 slots
across Timzones on the Esupport portal
• Dedicated time with an SME, blocked 5 days in
advance
• Scheduled time with pre-defined agenda to help aid
productive discussion
• Topics of engagement include Product Roadmap,
New Features, Best practices, and others.
• Products include BDM, IICS, PC, DQ, MDM
and EDC

36 © Informatica. Proprietary and Confidential.

Thank You

Claudio Nold `

Manager Global Customer Support

David Anantharajan
Principal Technical Support Engineer