Core Feature Overview

Brief overview of the core features in Open Cloud MDM (for a detailed description of a feature, click on the feature name in the navigation bar on the left):

Composite Transactions in Open Cloud MDM:

• Definition: Composite transactions are a way to aggregate multiple single transactions into a cohesive operation. They are used for complex business processes where multiple discrete actions need to be performed in sequence or together.
• Methods: Composite transactions can be created using customized business proxies or defined in XML scripts.
• Benefits: They streamline complex processes, ensure data integrity, and synchronize updates across multiple data entities.

Data Validation in Open Cloud MDM:

• Overview: Data validation ensures that transactions comply with predefined requirements and business rules, maintaining data quality and consistency.
• Levels: Controller level validation filters out issues early, while business component level validation handles more complex validations during transaction execution.
• Types: Internal validation maintains database integrity, while external validation checks data against business rules and standards.

Data Standardization Framework:

• Definition: This framework standardizes master data to ensure high quality, customizable standards, and conditional invocation.
• Customization: It allows configuration of custom standardization rules for different business objects.
• Representation: Data is standardized into a defined format, making it easier to work with and integrate into other systems.

Error Handling and Exception Logging:

• Error Handling: Open Cloud MDM provides localized error messages, flexible error severity levels, and customizable error definitions.
• Logging: It logs application and system errors, helping maintain system integrity and providing insights for improvement.

External Business Rules in Open Cloud MDM:

• Definition: External business rules integrate business logic into transaction workflows, enabling complex operations and decision-making.
• How It Works: Data requirements are identified, and actions are taken based on the outcomes of external rules.
• Significance: It enhances flexibility, customizable logic, and improves decision-making in response to external conditions.

Inquiry Levels in Open Cloud MDM:

• Defining Inquiry Levels: Users can customize the level of detail for objects returned during searches or inquiries.
• Parameter-Driven: Parameters dictate the granularity of the information retrieved, allowing for tailored search results.
• Versatility: It enables retrieval of new combinations of objects, useful for complex queries.

Locale and Language Customization:

• Language and Locale Selection: Allows configuration of the system in a specific language and locale.
• Globalization Support: Provides business and system error messages in the chosen language or locale.
• Multilingual Data: Supports maintaining product data in various languages.
• Unicode Compatibility: Uses Unicode for seamless data flow across languages.

Multi-time Zone Deployment:

• Deployment Across Time Zones: Ensures data consistency across servers and databases in different time zones.
• Daylight Savings Time Handling: Standardizes timestamps to UTC for simplified management.
• Data Consistency: Guarantees uniform timestamp recording for global operations.

Notifications:

• Definition: Notifications are messages conveying data about specific events within the sending application. They are essential for informing other systems or components about relevant changes or occurrences.
• Notifications Manager: This component plays a pivotal role in transmitting notification messages from Open Cloud MDM to various destinations. It utilizes the ActiveMQ messaging system for message publication.
• ActiveMQ Integration: ActiveMQ is used as the underlying infrastructure for the Notifications Service, enabling targeted message distribution to user groups or external systems.
• Real-time Communication: The Notifications Manager enhances real-time communication capabilities in Open Cloud MDM, ensuring prompt information sharing with external systems and users.

Point in Time History (PIT):

• Audit Database: PIT history relies on an audit or history database, a duplicate of the operational database with additional audit attributes. Audit tables store data changes during transactions, providing a comprehensive record.
• Benefits and Functionality: Users can access historical data to understand how business objects appeared at specific points in time. It aids in tracking data evolution, offers a valuable audit trail, and ensures data accountability and transparency.

Source Values and Data Decay:

• Source Values: This feature standardizes the storage and retrieval of information from external sources, even when attributes don't align perfectly with the Open Cloud MDM structure. It tracks metadata, such as collection date and changes.
• Versatile Handling: The Source Values System can add, update, and retrieve various types of information, including privacy preferences, campaign data, and more. It integrates into multiple function areas within Open Cloud MDM.
• Extensive Coverage: It is integrated into core entities within the Party Module and ensures effective management and tracking of data from various sources.

Event Manager:

• Capabilities: Event Manager detects and manages events and activities within the system. It can detect time-based events, events after transactions, and record event information.
• Action Execution: Event Manager can execute actions as part of business rules based on event occurrence, including triggering additional transactions and sending notifications.
• Flexibility: Highly flexible and can be integrated with any business system, tracking events for various business objects, such as campaigns.

Interactions:

• Overview: Interactions in Open Cloud MDM allow tracking and documentation of various customer and organization interactions, including phone calls, emails, fax, notes, and task-related interactions.
• Use Cases: It helps maintain a comprehensive history of engagements, facilitating better customer relationship management and informed decision-making.

Rules of Visibility and Data Persistency:

• Entitlement Assignment: These modules manage user entitlements regarding data access and manipulation based on data values.
• Rules of Visibility (RoV): Defines what elements users can see based on constraints, evaluated post-transaction.
• Data Persistency Entitlements: Defines what users can add or update based on constraints, evaluated pre-transaction.
• Row and Column Level Security: Ensures data visibility and persistence, considering data instances and types.

Specs:

• Definition: Specs define metadata to support dynamic attributes within Open Cloud MDM. They allow customization without hardcoding dynamic attributes into the data model.
• Usage: Specs are used in areas like Party demographics and the product domain to support highly dynamic and adaptable custom data models.
• Management: Specs are defined and managed through the Open Cloud MDM Workbench, offering flexibility and efficient management of custom data models.

Task Management Services:

• Entity Lifecycle Management: Manages stages in the lifecycle of entities, such as products or customer support tickets, orchestrating tasks for each stage.
• Orchestration and Business Process: Orchestrates and executes tasks for various business processes, ensuring smooth workflow and task completion.
• Task Lifecycle Management: From task creation to resolution, Task Management Services efficiently handle tasks, providing context and accountability.
• Runtime Execution Environment: Handles tasks within a runtime environment, crucial for processes like loan approvals or order processing.
• Generic Task Design: Adapts to various processes, such as project task assignment, by creating and assigning tasks to team members.
• Task Assignment: Assigns tasks to team members in project management or other scenarios, ensuring responsibilities are clear and tasks are managed effectively.

Transaction Audit Information Log (TAIL):

• Database-Driven Configuration: TAIL relies on database-driven configuration to log different types of business transactions, both external and internal.
• Internal Transaction Logging: It logs both external and internal transactions associated with business transactions, providing a comprehensive transaction history.
• Synchronous and Asynchronous Logging: TAIL supports both synchronous and asynchronous logging, ensuring flexibility in the logging process.
• Main Features: TAIL's main features include configuring which transactions to log, logging transaction details, and retrieving logged audit transactions for a comprehensive view of transaction history.

User Accounts, Profiles, Roles, and Groups:

• Definition: User management in Open Cloud MDM encompasses user accounts, profiles, roles, and groups, enabling precise access control and data security.
• Methods: User accounts link system users to real-world contacts, while profiles define attributes, roles, and permissions. Grouping users simplifies management, and access rights are assigned via profiles and groups.
• Benefits: This approach accommodates complex structures, supports succession planning, and adapts to changing roles, enhancing efficiency and security in Open Cloud MDM.