Overview Informatica Master Data Management Cloud (MDM SaaS) is a cloud-based Master Data Management (MDM) solution.
MDM SaaS - Customer 360 is an enterprise cloud-based
customer data management solution which uses MDM SaaS - Customer 360 Records for creating a single source of truth for data as well as onboarding, consolidation, enrichment, governing, and distributing such data.
Set up Applications For any New Org activation – It’s a 3 Step process.
A Customer Success Manager (CSM) will reach out
to customer to get the administrator user details. (Email, First Name, Last Name, Phone no, Address). After the CSM creates org account, administrator user will receive an email to confirm your account. The account confirmation link is valid for 48 hours After you activate the account, customer can log in to Informatica Intelligent Cloud Services and set up the business applications
Key Points User should perform the Set-up Applications before doing any code migration of any asset in org.
User should have "Admin" role and a group assigned.
Org should be upgraded to latest release from Business 360 before performing Set up Applications.
All Business 360 processes in the Application Integration chicklet, should be in Published State.
Create other projects for all additional required assets such as mappings, mapping tasks, task flows or even other MDM SaaS assets and avoid using OOTB (Business 360, Customer 360, MultiDomain MDM, Reference 360, Supplier 360, Product 360) projects for these assets
There should not be any permissions set on the OOTB folders in Explorer Tab in B360. (Business 360, Customer 360, MultiDomain MDM, Reference 360, Supplier 360, Product 360)
Data Modelling Pivoted data modelling strategy from relational database modelling to more advanced Document database style modelling to overcome data modelling challenges Providing "Out of the Box” Data Models for easier modelling experience Introducing “Smart Fields” to provide low effort enjoyable modelling experience Enhanced Basic Fields & Field Groups to provide better flexibility Bringing in Reference Data Assets for easy Lookups
From Traditional “Relational Database style” To Advanced “Document Database style”
OOTB Predefined data model that customers can customize to manage their data needs. Data In GA, Providing 2 OOTB Business Entities – Person and Organization Model
The idea behind smart field is how can we make the Smart fields Available in GA modelling experience super easy for a user by freeing them from worry of choosing data types and need to Smart configure validation rules for fields Fields Postal eMail Phone Address
Key Points For Customer 360 a data dictionary can be used as a guide to map source system attributes with MDM attributes. Please refer KB Article
Once we have the Data Model finalized and we create respective Assets in the ORG, for any new Business use cases, we recommend to create a new Assets as part of Data Model.
Recommend NOT to delete/remove any existing Assets (Business Entity, FieldGroup, Attributes) from Data Model. That may lead to meta data corruption
Follow the proper naming conventions while creating the assets, to differentiate between OOTB assets and custom assets.
Ex: For Custom Attribute: X_<FieldGroupName> or X_<Attribute>
