Data objects
Model business information, trace which applications use it and check what a change would affect.
A data object represents information people recognise across systems. A webshop, a warehouse and a finance team can all refer to the same Sales order, even when each stores it differently. Use one object while it has the same business meaning. Give an Invoice its own record when it has a different purpose, users or retention policy.
Choose the right record
| What you need to describe | Where it belongs in Atlas |
|---|---|
| The order number, items and delivery details the business treats as a sales order | A data object. Give it a business display name and keep a technical name or location where it helps someone find the source. |
| The database engine storing the order | An IT component. One engine can store several kinds of information. |
| The webshop making the order available to the warehouse | An integration. Link the data object it carries. |
In the pilot, open Data objects and search the tree before creating another record. Choose New to open Register Data Asset. Enter Name, choose the Type of the asset you are registering, such as a table or topic, and select Register Asset. Use Domain to group records by subject. On the fact sheet, Edit lets an editor set Parent data object. The child then shows Part of. Use a parent for a whole–part relationship, such as Sales order and Order line.
Follow use and movement
- On the object's Applications card, read the role and operations together. C, R, U and D mean create, read, update and delete. A warehouse may read an order that the webshop created. The role alone does not establish which operations it performs.
- Open Integrations to see which exchanges carry this object. Each flow has its own operations. Open the integration to check the source, target and interfaces. Editors can use Edit data objects on an application or an integration to record the operations for that particular relationship.
- Open Lineage. Upstream and Downstream show recorded links to other data objects. Choose View lineage for a diagram of the applications and exchanges for this object. Copy to my album gives you a working copy to arrange or annotate. See Albums and views.
The Capabilities card shows which business abilities use the information. With edit access, use its pencil to link or unlink a capability. Undo restores the previous selection.
Review classification and retention
Owner application identifies the system recorded as owning the object. Steward identifies the person to ask about its meaning and handling. Confirm the authoritative source with that person before resolving conflicting values in two systems.
Classification records sensitivity. Contains personal data records whether the object contains personal information. Enter a confirmed retention period in days. Compliance and gaps highlights items such as a missing steward, a missing retention period for personal data or a failing quality check. Open the supporting source before using a value in a review. The earlier detail view is available from Classic fact sheet.