An integral part of data governance lies in being able to track and audit your data. The Catalog provides you with a simple and scalable solution to control changes in line with your business needs.
You can tailor who makes edits and audit changes for compliance-critical updates. Approvers can be individual users, teams, or even interested parties, giving you full control over how data governance evolves with your business.

Making changes

When you make a change in the Catalog, it will only appear locally in your basket before being published for everyone else to see on the Submit changes for review page. Changes to an object that have not been published are marked with an appropriate icon depending on the type of change:

  • Create icon Create
  • Edit icon Edit
  • Delete icon Delete

Auditing changes

Every edit in the Catalog is recorded and can be viewed in each object's History tab. In addition to showing the date and details of each change, it also gives visibility of proposed changes awaiting review.

Baskets

Your current basket displays all outgoing changes grouped together. You should carefully review and publish with a comment explaining what has changed. Changes can be reverted from this page to remove them before submission. Only when all required approvals for a basket have been completed the changes are applied and visible to all users.
'Submit changes for review' icon
The Manage baskets page shows all of your baskets, including those that have been submitted or applied. You can view the current state of each basket including approvers responses. You can retract and freely add or remove changes from a basket before resubmitting it. You can also access and amend rejected baskets. Please note that retracting a basket removes any existing responses.

Accessing approval tasks

As an approver, you are responsible for reviewing all incoming changes and ultimately decide whether to apply them. You may have your own set of approval tasks to manage, which you can access via the View tasks awaiting approval icon in the header.

Viewing changes

You are able to view baskets awaiting approval and those you have previously approved from this page.

'Review tasks for approval' icon

Selecting a specific basket allows you to review changes to individual objects on a field-by-field basis, including the difference between the proposed object and the existing one. You will also be able to view the entire history of the object and see how it has changed over time.
By default, you will be viewing changes relevant to you - those that you are assigned to approve. If you'd like additional context, you can toggle to All approvals to view all changes.
'Approvals toggle'

While reviewing specific baskets you can also see information about required approvals, including an administrator-configured summary of each approval requirement alongside a list of other approvers and their response to the basket.

Responding to a basket

After reviewing a basket you can either approve or reject the changes. You can also provide a comment explaining your decision and giving feedback.

  • Approving: The contents of a basket are only applied once all necessary approvals have occurred.
  • Rejecting: If any approver rejects a basket it is immediately rejected, allowing the author to make changes based on feedback and resubmit.

Managing approval requirements

An administrator can set up which people or groups are responsible for approving changes for each Object Type.

To manage approval requirements, go to the "gear" icon on the homepage to access the data model configuration page. Within this area of the product, you can select an Object Type and then navigate to the Approval Requirements tab. Alternatively, you can jump straight to that page by using the link in the Approval requirements column for the Object Type.

Approval requirements can be assigned to Users, User Groups, or Interest Types.

  • User - An individual person responsible for reviewing all changes belonging to objects of this type.
  • User group - A group of one or more people. It's best to use a user group instead of specifying individual users: in cases where a person is away or leaves the business then another person can be assigned to the group. Only one of them needs to provide approval.
  • Interest Type - For example, an owner or a follower. Use this to assign different approvers to an individual object within each type. An object can have many interested parties assigned to or just one. Using an Interest Type as an approver is useful where a subject matter expert might be crucial to review some objects, but not all.

Conditional approvals

There are multiple tools available when creating or editing an approval requirement to enable specific, purposeful approval. It is recommended that the Summary on an approval requirement is used to explain what a specific requirement's purpose is to help guide approvers.

  • Actions: Any combination of the Create, Edit, and Delete actions can be selected. At least one action must be selected for the requirement to be valid.
  • Approval condition: An optional condition can be set to control when an approval is required. For example, when a certain field will equal a specific value. When Edit is the only selected action conditions can use the 'Is changed' operator, which is triggered when the field is changed to any value.