Skip to main content

Custom Models

We standardized our terminology as follows, there are 2 types of models on the repository:

  • Imported Models are the models associated with an import bridge to be populated through the model harvesting process. Many times these models are referred to as technical models, however they are also sometimes considered business models when imported from business applications or business intelligence (BI) tools.
  • Custom Models are instantiations of a custom model type in the metamodel and may be populated via the UI, bulk CSV import , or the REST API . They are commonly referred to as business models, however they are also sometimes considered technical models withing the domains of reference data, business rules, etc.

Custom models can be defined for the custom metamodels needed in many data governance related domains such as data management, reference data, data quality, data trust, data security, data sharing and shopping, data issue management, business rules, business process modeling and improvements, vertical market specific business applications and regulation compliance. Administrators can use a new MANAGE > Metamodel capability to define their custom models with the full power of object modeling, all the way the graphical editing of UML class diagrams for each custom models.

By default, custom model will have no workflow requirement, thus there will be no formal review and approval process. However, all Metadata Viewing , Editing and Management capability object role assignment s may be used to manage access and update. You may see the functions without workflow defined below.

TDC also provides a very flexible and complete set of possible workflow and publication processes that you may employ. When your organization would like to have a more formal development process that involves multiple users with various review/approval/publishing roles you can enable the glossary workflow. The workflow is a prepackaged sequence of activities around term proposal, editing, review, acceptance, publishing and depreciation. It is a flexible process that can be customized to require only publishing activity, approval with or without review, approval and review by one or multiple users, etc.

All the functions of a custom model are affected by the imposition of a workflow, especially in terms of changes to the object classes which are under workflow requirements. As an example, the we have an example of a glossary (a type of pre-defined custom model) under workflow and how these functions are affected along with how to enable the workflow in the first place.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!