Users with the role permission Manage Catalog model will see a gear icon on the Catalog homepage, which allows them to access the data model configuration page.
Within this area of the product admins can specify new Object Types, fields to capture against these objects, associations between different Object types, and the Intertypes of interests for each Object Type.
Object Types
To specify additional metadata to capture within the platform press the Create new Object Type button and follow the steps to specify the required information:
Name: This is used for in app menus and for defining the URL path when navigating around objects of this type (for example an Object Type of Policy would have a URL with the format …/policy/…).
Plural: This is used for the homepage to represent this type of object.
Approvers: If you wish for changes made by users to objects within this Object Type to trigger an approval, please specify the user or group of users whom you want to approve these changes.
Further customization options enable you to display certain Object Types on the homepage if needed, allowing users to navigate to them directly.
Field Types
By default, users only set a name value for new objects. However, additional fields can be configured to capture additional data about the object.
When configuring the fields for the object, various options are available to allow you to specify the data type captured by each field, the layout, and presentation of the field within the form including:
Data type: Specifies the type of information being captured. This then drives further configuration options of component type, minimum or maximum length, or value.
Sort order: Allows you to define a logical sequence of how the fields are arranged within forms and tables.
Field size: Allows you to specify the width of the field from 1-12, where 12 covers the full width of the page.
Tooltip: A hover-over tooltip that helps guide the user on what is required for this piece of information. This supports Markdown formatting so you can embed images, link to other materials (for example internal documentation) or simply use rich formatting to drive the ideal experience for your users. To learn more about Markdown formatting, expand the accordion below.
Component type: Defines what form of the component to use in the field:
For string field, “textbox” only allows plaintext input, whereas “textarea” permits the use of Markdown.
Number, date and boolean only have a single option available.
Is required: Allows you to define how important the population of each field is:
Required: New records can’t be saved without this being populated.
Preferred – red: If a record is missing this, a red flag will be triggered for conformance monitoring.
Preferred – amber: If a record is missing this, an amber flag will be triggered for conformance monitoring.
Optional: This field is available to populate but triggers no warnings if left empty.
Is advanced column: Determines if the table will display this field by default when the user clicks the Show advanced columns button.
Is displayed in primary tables: If true, the field will be shown in the Object Type list table.
Is displayed in secondary tables: If true, the field will be shown in the secondary tables.
Markdown is a simple markup language for adding rich formatting and embeds to plain text. Below are some of the most commonly used markdown elements.
Using special characters
When using special characters such as a hashtag, backtick, or an asterisk, to escape markdown formatting within your text use a backslash before the character, for example \#.
Headings
# Heading 1
## Heading 2
### Heading 3
Headings go as small as H6.
Bold and Italic Text
**Create bold text with double asterisks** and *italic text with single asterisks.*
Lists
Markdown supports ordered lists using numbers:
First item
Second item
Third item
Markdown also supports unordered (bulleted) lists using dashes:
- First item
- Second Item
- Third item
Code
`Format a line of code with backticks.`
Horizontal Rule
Add a horizontal rule line with three dashes (---).
Images are supported if the image file is Base64 encoded.
For example: 
Tables
Format tables with horizontal bars and dashes.
| Table | Column | Header |
| ------ | ------ | ------ |
| First | row | here |
| Second | row | here |
The resulting table:
[.no-100perc-width]
Table
Column
Header
First
row
here
Second
row
here
Association Types
Moving beyond specifying the fields users need to populate, there’s also the option to specify the associations from this object to other Object Types too. This could take the form of:
References: These allow you to define dropdown options within the form itself (i.e. reference lists) such as for ensuring risk levels assigned to a data asset are from a defined list, or business units that a process belongs to are consistently represented. Associations of this type act similarly to a new field and have the same options from a configuration perspective, so that the surfacing of these picklists can be configured to drive a sensible page layout.
Is child of: This mapping allows you to group metadata appropriately (for example processes have a parent of ‘business function’ or ‘business unit’ and ‘data terms’ are grouped by ‘domain/entity’). This Association Type drive the navigation between objects as users traverse the hierarchy of the Catalog.
When this is selected you have the option to choose if you want this context to be displayed in the tables themselves (primary/secondary) and whether it should appear by default or as an advanced column.
Is assigned with: Many-to-many relationship mappings so that processes can be mapped to the data fueling it, or the critical data elements that are crucial to its successful execution. Associations of this type result in a table being displayed alongside the object so as multiple entries can be shown.
Interest Types
Interest Types can also be specified (if required) to allow roles to be explicitly assigned to users within the tool. This can be mapped at a user or a group level and can be aligned to appropriate terminology. For example, against a policy you might want to ensure an ‘executive sponsor’ is assigned, against a data asset you might want to map a ‘steward’, an ‘owner’ and a ‘custodian’, or against a business process you might want to map who is ‘responsible’, ‘accountable’ and ‘consulted’.
As with reference associations and the population of fields, conformance monitoring logic can be configured at the interest assignment level allowing you to choose how crucial the mapping of each Interest Type is within the ‘Is required’ setting:
Required: New records can’t be saved without this Interest Type being assigned.
Preferred – red: If unassigned, this triggers a red flag for conformance monitoring.
Preferred – amber: If unassigned, this triggers an amber flag for conformance monitoring.
Optional: The assignment of this interest is available if needed but triggers no warnings if left unassigned.
Within this area, Catalog admins can also optionally allow users to subscribe to updates for each object of this type. For example, a user can subscribe to updates relating to a specific policy so that they get notified against any updates relating to this item.
Approvers
These are the individual Users, User groups and/or Interest Types responsible for reviewing user suggested changes for an object or Object Type.
Review Cycles
Review cycles ensure designated Object owners periodically review and confirm the accuracy of data.
Performing bulk updates of Catalog data
Certain admin users might also be given the role permission Bulk load Catalog data. This permission allows the creation of an API key, which can be used in a Workflow to extract Catalog objects and create/update/delete Catalog objects at scale.
