[et_pb_section fb_built=”1″ _builder_version=”3.22″][et_pb_row _builder_version=”3.25″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″ _builder_version=”3.25″ custom_padding=”|||” custom_padding__hover=”|||”][et_pb_post_title meta=”off” featured_image=”off” _builder_version=”3.0.105″ title_font=”Source Sans Pro||||||||” title_text_align=”left” title_text_color=”rgba(0,0,0,0.8)” title_font_size=”47″ text_orientation=”center” custom_margin=”|||10%” title_font_size_tablet=”40″ title_font_size_phone=”35″ title_font_size_last_edited=”on|desktop”][\/et_pb_post_title][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”3.25″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″ _builder_version=”3.25″ custom_padding=”|||” custom_padding__hover=”|||”][et_pb_text _builder_version=”3.27.4″ text_font=”Titillium Web|300|||||||” text_text_color=”rgba(0,0,0,0.8)” text_font_size=”20″ text_line_height=”1.6em” max_width=”800px” custom_margin=”|||10%” text_font_size_tablet=”” text_font_size_phone=”” text_font_size_last_edited=”on|desktop”]<\/p>\n
\u00a0100% Free Informatica MDM Course, Enroll Now<\/strong><\/span><\/a><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.7″ text_font=”Titillium Web|300|||||||” text_text_color=”rgba(0,0,0,0.8)” text_font_size=”20″ text_line_height=”1.6em” max_width=”800px” custom_margin=”|||10%” hover_enabled=”0″ text_font_size_tablet=”” text_font_size_phone=”” text_font_size_last_edited=”on|desktop” module_class=”pa-blog-new-tab” sticky_enabled=”0″]<\/p>\n Objectives<\/p>\n Following are the objectives of this topic:<\/p>\n i)<\/strong>\u00a0Introduction to IDD.<\/p>\n ii)<\/strong>\u00a0Describe IDD Architecture<\/a>.<\/p>\n iii)<\/strong>\u00a0Configure Subject Area and Child\/Grandchild Subject Area.<\/p>\n iv)<\/strong>\u00a0Configure IDD Lookups.<\/p>\n v)\u00a0<\/strong>Configure IDD Data Cleansing.<\/p>\n vi)<\/strong>\u00a0Configure IDD Search and Matching.<\/p>\n vii)<\/strong>\u00a0Configure IDD Hierarchy Management.<\/p>\n Informatica Data Director (IDD)<\/strong><\/p>\n It is a data governance application for Informatica MDM Hub that enables business users to effectively create, manage, consume, and monitor master data<\/a>.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/asha24.net\/blog\/\/wp-content\/uploads\/2018\/03\/w1.png” align=”center” align_tablet=”center” align_phone=”” align_last_edited=”on|desktop” _builder_version=”3.23″ max_width=”80%”][\/et_pb_image][et_pb_text _builder_version=”3.27.4″ text_font=”Titillium Web|300|||||||” text_text_color=”rgba(0,0,0,0.8)” text_font_size=”20″ text_line_height=”1.6em” max_width=”800px” custom_margin=”|||10%” text_font_size_tablet=”” text_font_size_phone=”” text_font_size_last_edited=”on|desktop”]<\/p>\n \nIDD Components<\/strong><\/p>\n IDD Application<\/strong><\/p>\n Main configuration and deployment unit for IDD<\/a>.<\/p>\n This is what business users see when they launch and log into IDD.<\/p>\n IDD Configuration Manager<\/strong><\/p>\n Web-based utility used to add, modify and manage IDD applications.<\/p>\n IDD Configuration Files<\/strong><\/p>\n IDD configuration file (XML), resource bundles, localization message bundles, online help, and other auxiliary files.<\/p>\n These can be loaded of modified in the IDD configuration manager or exported and edited manually.<\/p>\n Subject Area:<\/strong><\/p>\n Subject Area (Entity Type)<\/strong><\/p>\n i)<\/strong>\u00a0A subject area is a collection of data that should be treated as a unit from a business perspective.<\/p>\n ii)<\/strong>\u00a0Has a single root record in a single base object.<\/p>\n iii)<\/strong>\u00a0Has some number of child records.<\/p>\n Subject Area Group (BO)<\/strong><\/p>\n i)<\/strong>\u00a0A set of one or more subject areas that have the same base object at their root.<\/p>\n ii)<\/strong>\u00a0For 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).<\/p>\n iii)<\/strong>\u00a0Subject Area Group and Subject Area provide the high-level menus for navigating data in IDD application.<\/p>\n Subject Area<\/strong><\/p>\n A Subject Area can have the following configurations.<\/p>\n i)<\/strong>\u00a0Layout of form fields for primary object.<\/p>\n ii)\u00a0<\/strong>Data cleansing\/standardization\/validation functions.<\/p>\n iii)<\/strong>\u00a0Package for displaying search results.<\/p>\n iv)<\/strong>\u00a0Data searching and matching ability.<\/p>\n v)<\/strong>\u00a0Children and Grandchildren records.<\/p>\n Layout Configuration<\/strong><\/p>\n Layout configuration allows you to choose which fields from the base object to include in the user interface and how to show each record.<\/p>\n Search Results Display Package<\/strong><\/p>\n i)\u00a0<\/strong>This package determines default table layout for search results.<\/p>\n ii)<\/strong>\u00a0Primary table of package must be the same as primary table of subject area.<\/p>\n iii)<\/strong>\u00a0If package contains joins to child tables, then it is possible for the package to return multiple rows.<\/p>\n Subject Area Relationships<\/strong><\/p>\n a)<\/strong>\u00a0IDD understands relationships within subject areas through the match paths<\/a> that are configured in MDM.<\/p>\n A subject area can have the following types of relationships:<\/p>\n i)<\/strong>\u00a0Child subject areas.<\/p>\n ii)<\/strong>\u00a0Grandchild subject areas.<\/p>\n iii)<\/strong>\u00a0Sibling references.<\/p>\n b)<\/strong>\u00a0Child Subject Area \u2013 Type of Relationships:<\/p>\n i)\u00a0<\/strong>One: Many – Logical one: one and one: Many<\/p>\n ii)\u00a0<\/strong>Many: Many \u2013 Part-Of and Reference<\/p>\n c)<\/strong>\u00a0Grandchild Subject Area \u2013 Type of Relationships:<\/p>\n i)<\/strong>\u00a0One: Many Grandchild.<\/p>\n ii)\u00a0<\/strong>Many: Many Grandchild.<\/p>\n IDD Data Cleansing:<\/strong><\/p>\n Cleansing, Standardization, and Validation<\/strong><\/p>\n i)\u00a0<\/strong>IDD allows you to use cleanse functions already defined in MDM to cleanse, standardize and validate the input data.<\/p>\n ii)<\/strong>\u00a0It is an optional feature for Subject Areas and Subject Area Child.<\/p>\n iii)<\/strong>\u00a0It can include address standardization and validation.<\/p>\n iv)<\/strong>\u00a0It can include data augmentation from other sources like D&B.<\/p>\n v)<\/strong>\u00a0Each subject area or child subject area can have one cleanse function associated with it.<\/p>\n Validation Status<\/strong><\/p>\n a)\u00a0<\/strong>The cleanse function can reports if it is configured with the validationStatus output.<\/p>\n b)<\/strong>\u00a0If validation errors are found, then the Save or Apply action does not proceed.<\/p>\n i)<\/strong>\u00a0 Format of the output is . separated by \u2018;\u2019<\/p>\n ii)<\/strong>\u00a0Example: FIRST_NAME.canNotBeNull;IS_VALID_IND.invalidIndicator.<\/p>\n iii)<\/strong>\u00a0columnName is the name of the input column that has a validation error.<\/p>\n iv)<\/strong>\u00a0messageKey is a key to a message<\/p>\n c)<\/strong>\u00a0messageKey value should be added in IDD application file MessageBundle.properties<\/p>\n i)<\/strong>\u00a0Format: validation_=Message Text<\/p>\n ii)\u00a0<\/strong>Example: validation_canNotBeNull=This field cannot be empty<\/p>\n IDD Searching and Matching:<\/strong><\/p>\n Search<\/strong><\/p>\n i)\u00a0<\/strong>Search allows an end user to specify conditions for selecting data for review.<\/p>\n ii)<\/strong>\u00a0A search can be based on data in the:<\/p>\n a)<\/strong>\u00a0Primary Object Record.<\/p>\n b)<\/strong>\u00a0Any of its Child Records.<\/p>\n c)\u00a0<\/strong>Any records related via a Match path Component.<\/p>\n iii)<\/strong>\u00a0Two types of searches are provided in IDD:<\/p>\n a)\u00a0<\/strong>\u00a0Basic Search.<\/p>\n b)<\/strong>\u00a0Extended Search.<\/p>\n Basic Search<\/strong><\/p>\n i)\u00a0<\/strong>It is a SQL-based search that finds results using string pattern comparisons.<\/p>\n ii)\u00a0<\/strong>Case-Sensitive.<\/p>\n iii)\u00a0<\/strong>Can use any attributes from the Subject Area.<\/p>\n iv)<\/strong>\u00a0Wildcards (% or *) can be used in the Search.<\/p>\n v)<\/strong>\u00a0In the IDD application, the end-user can create their own Search template.<\/p>\n vi)<\/strong>\u00a0When defining an IDD application you should create a default public search for each subject area.<\/p>\n Extended Search<\/strong><\/p>\n Uses Match Engine to Search.<\/p>\n Searches are \u201cfuzzy\u201d i.e. will find records that are similar to input criteria, but that are not textually identical.<\/p>\n Match column must already be defined in MDM.<\/p>\n \u00a0IDD Workflow and Tasks:<\/strong><\/p>\n Objectives:<\/strong><\/p>\n Following are the objectives of this topic:<\/p>\n Overview of Workflow and Tasks.<\/p>\n Describe Tasks and Task Types.<\/p>\n Describe Action and Action Types.<\/p>\n Task Notification and Assignment.<\/p>\n Workflow and Tasks:<\/strong><\/p>\n Workflow<\/strong><\/p>\n a)\u00a0<\/strong>Workflow<\/a> represents the management of steps in a business process.<\/p>\n b)<\/strong>\u00a0It specifies what tasks need to be done, in what order, and who has permission to perform each task.<\/p>\n c)<\/strong>\u00a0Base Objects must have State Management enabled in the Schema.<\/p>\n d)<\/strong>\u00a0IDD provides workflow support for:<\/p>\n i)<\/strong>\u00a0Task creation and editing.<\/p>\n ii)<\/strong>\u00a0Task assignment to users.<\/p>\n iii)<\/strong>\u00a0Task approval or rejection.<\/p>\n Task<\/strong><\/p>\n A task represents a pre-defined step in a user\u2019s business process which is executed by a particular role.<\/p>\n IDD comes with a set of pre-defined task types.<\/p>\n These can be modified and additional task types can also be added.<\/p>\n Pre-defined Tasks<\/strong><\/p>\n The IDD default configuration includes seven pre-defined tasks.<\/p>\n The task definitions may be modified by the user and new tasks can be added as necessary.<\/p>\n