Learn & Share

Hi everyone,  Are you just starting out with Data Governance or would like to brush off some of your skills? Check out our learning journey below and follow along to improve your Data Governance skills one article at a time⚡ First things first: Let’s start with the basics 📚 Continue with the essentials 🔑 Advance your skills 🔗 Need some brainstorming? Check out our digest issue 🧠 

Hi, I’m Oliver. a Solutions Consultant here at Ataccama.Workflows and governance are integral to any form of modern data management, be it MDM or RDM. But with so much to do in a typical workday, how do you respect the time of your end users and ensure they are informed when their input is required?Out of the box, Ataccama MDM and RDM include useful functionality to send emails to defined roles (i.e. groups of users) whenever records are moved through C(R)UD workflows. But what if we need to:Create consolidated, routine summaries for cases where data changes often and frequently? Allow users (e.g. project managers) who are not directly involved in the workflow to see progress? Notify users in different ways (e.g. Microsoft Teams, Slack, or Amazon SNS)? Create dashboards of daily workflow progress to report against?Once again, we can turn to Ataccama Plans & Scheduled Workflows! Notification WorkflowsIn this example, consider a pretend client using RDM, with a custom workflow whenev

Hi everyone,  Learning new skills or starting something from scratch can be daunting sometimes. We may feel a bit lost in all the information coming at us or scroll endlessly in the search results. That’s why in this post, I want to create a how to get started with ONE Desktop journey, compiling all the articles we have published in the last months. According to your experience, you can jump a few articles or click on the one you find the most challenging at the moment. Please also do share your feedback and questions in the comments section 👇🏻 Beginner Friendly - Learn the essentials: How to work with plans? aka  your canvas on ONE Desktop:  Main elements of ONE Desktop 🔥🌍💧💨 Tips & Tricks:  If you got the basics let’s move on..  Integrations 🖇️ Best Practices from the community 💪🏻      

Hi all!In today’s post, we will go a step further and briefly touch on the main features of the RDM. RDM and its features are without a doubt much more layered so I’ll be sharing links to further reading on each of the features mentioned 🖇️Before starting, I suggest you take a look at the first two posts of our RDM Best Practice series to get familiar with the solution if you aren’t already 🔎  1. Model and Metadata ConfigurationThe RDM metadata is the core configuration of the RDM project. The central reference data model swiftly configures critical processes, from integration interfaces to synchronization processes and relationships.Through the metadata model it defines all entities, structures, workflows, synchronization jobs, and more. For detailed instructions, refer to RDM Configuration. 2. Data Management RDM seamlessly supports the complete lifecycle of reference data. It serves as the central authority for changes, ensuring consistency across diverse systems. Create, modify,

Hi everyone! We are back with the second part of the introduction to RDM series. If you missed our first post you can find it here 👇🏻In this post, we'll delve into the fundamentals of RDM—creating new reference data, editing existing records, publishing changes, and exploring advanced features like viewing modes and hierarchies. Let's get started 🏃🏻‍♀️ How to Create New Reference DataLet’s go through a quick example to demonstrate. Navigate to 102: Branch Table: Open the DATA section in the left menu. Choose Tables and open the 102: Branch table, showcasing a list of banking branches.  Create New Record:Hit the Create button, unveiling an empty form. Fill in required fields, leaving Code blank. Validate your entries, correcting any issues. Hit Enrich to auto-populate certain fields based on predefined logic. Before saving, ensure your Address lacks the number 9. Save the record, acknowledging the warning prompt. Explore the option to create a new record from an existing one for ef

Hi everyone, and happy Monday! In this post, we will cover Ataccama’s Reference Data Management solution with a short introduction, follow us for part 2 and check out our MDM Series below 👇🏻 First things first. What is RDM?Reference data is data that defines the values that are used to classify and characterize other data. This is sometimes known - not always correctly - as Master Data, Golden Record, Golden Copy, or Single Source of Truth.RDM is an essential component of Master Data Management (MDM) that has evolved to become a mature data management discipline in its own right.  Who's It For?At the heart of the RDM web application are three key player roles:Reference Data Stewards Analysts ManagersDesigned with precision, the RDM web application caters to these roles, ensuring a user-friendly and efficient experience. What Can You Do?The RDM web application empowers you with a rich set of features: View, Edit, and Manage: Seamlessly view, edit, and manage reference data, putting yo

 Happy Tuesday community 🙋‍♀️ This week we have a series of best practices on all things components on ONE Desktop. Component steps, often referred to as simply "components," are instrumental tools that come with unique capabilities. Here, we'll explore what makes components special and how to make the most of them in your data projects. What Sets Components ApartComponents are akin to plans but with distinctive attributes: Reusable: Components can be employed repeatedly, functioning like steps within other plan files. Parameterization: Components can have properties within their constituent steps mapped as parameters, allowing external plans to interact with them (learn more in the section on "Mapping Properties as Parameters"). Console Launch: Components can be executed directly from the console, with parameters for added flexibility. Example: The Component in ActionComponent files are identifiable by their ".comp" extension and can play pivotal roles within your data workflows.

Hi everyone, Welcome back to our best practice series on MDM. In this post, we're diving deep into the features that make MDM - so buckle up 🚘 MDM’s primary feature is its model-driven architecture. It's a domain-agnostic MDM that empowers developers to craft domain-specific MDM models. Let's break down its high-level features by type. Model-Driven ArchitectureMDM's domain-agnostic approach is complemented by vertical models (metadata templates) designed to be domain-specific. These models are not cast in stone; they are customizable and extendable to meet the unique needs of your project. To delve deeper into this model-driven marvel, check out the Model. Internal Workflow and Processing PerfectionMDM boasts a remarkable set of features:Out-of-the-box change detection on load: MDM is a keen observer. It can detect changes in source instance records by tracking their unique source IDs. If a record has changed, it triggers the MDM process for that specific record. The granularity of de

Hi everyone, In this post, we will continue our introduction to Master Data Management (MDM), if you have missed our first post you can find it here 👇🏻This article will focus on the architectural details of MDM, breaking down the components, dependencies, and practical management tips ✨ The Pillars of MDMAt the heart of MDM, we find four essential components:Keycloak: Our third-party identity management tool. MDM Server (formerly known as MDC): The robust Ataccama MDM processing engine. MDM Webapp (formerly known as MDA): The user-friendly Ataccama MDM web application. Relational Database: The sturdy backend database, supporting PostgreSQL, MS SQL, or Oracle.Each of these components is configured as a Linux service, allowing independent restarts and individual log access for issue identification. The Backbone of DatabasesMDM is compatible with PostgreSQL, MS SQL, and Oracle relational databases. However, it's important to note that Ataccama officially supports only PostgreSQL Standal

Hi everyone, happy Monday 👋🏻 After publishing more than 20 articles on ONE Desktop best practices, I’m happy to share that we are ready to take the next step into Ataccama's Master Data Management (MDM), a robust, scalable, and highly available platform designed to simplify and enhance your master data management tasks. Let’s start with the basics ⚡  What is MDM and how is it different? Unlike the traditional "data flow driven" Data Quality Center (DQC), Ataccama MDM stands out as a fully metadata-driven data processing system. It incorporates an array of powerful tools, including the Advanced Metadata Editor (AME), a cutting-edge data processing engine (NME), and the DQC Plan Executor (complete with its steps and components).By doing so, MDM naturally extends the capabilities of the DQC, offering comprehensive data quality management functionality. In essence, MDM combines Master Data Management with a strong emphasis on Data Quality as a fundamental part of the process, providing a

Hi everyone, happy Wednesday! In this post, we will walk you through Model projects! Model projects play a crucial role in configuring various Ataccama products like DQ Issue Tracker, ONE RDM, and ONE MDM. These model projects are structured based on model templates, which define a specific set of nodes, folders, and files during project creation or import. It's important to note that you cannot modify or remove nodes created by a template.The configuration within model projects is developed using the Advanced Metadata Editor (AME). In this context, metadata refers to the configurations made within the model project nodes, which are used to generate plans, components, web service configurations, XML files, and other necessary components for a particular solution.Developing solutions based on metadata is carried out in the Model Explorer view, and detailed instructions for each product can be found in the respective Developer Guides.Every Ataccama build includes a default model project

📌  Links to the legacy documentation portal are no longer available. Read about the changes and how to access our documentation here.Hi community!In this post, we will discover how to create server connections in ONE Desktop for various tasks and workflow steps. Read on to find out more 👀 How to register a new server?To set up a new server connection, follow these steps:Right-click Servers in the File Explorer and select New Server.   Choose the desired Environment. Learn more about Environments.   Provide a unique server Name and select the appropriate Implementation. Configure the server connection according to your implementation, and click Finish.Once registered, the new server connection will appear in the File Explorer tree.Please note that, during development, right-clicking the server connection and selecting Connect is not considered a valid connectivity test, and it's not necessary for enabling step communication. Implementation TypesGenericUse this implementation to conn