Skip to main content

Administration and Configuration Glossary

This glossary page is meant to explain advanced terms used by the Platform Team on the administration and configuration of Witboost. If you are a Witboost user, we recommend checking out the User glossary or the Getting Started page instead.

Extensions​

Extensions are the category of customizations the Platform Team can perform on Witboost in order to personalize the User experience based on your organization needs and practices, as well as integrate Witboost with external systems and the Data plane.

Tech Adapters are an example of an extension of the Provisioner module.

Notification Webhook​

The Notification Webhook is an extension that you can configure in order to setup a webhook that Witboost uses to send notifications to an external service and broadcast them using your organization desired channels on top of showing them on the user notification panel on Witboost.

Custom Views​

Custom views are extensions that allow platform users to customize some pages of the Builder module, and the Market Plane. It allows defining YAML files using a custom language that maps the fields of the object to be shown to the Witboost visual representation. For example, it's possible to customize the product card shown on the Product list to include additional information that the default view hides.

Custom Pages​

A Custom Page is a page developed by the Platform Team and embedded alongside the other pages on the Market Plane and the Builder module. It leverages the Microfronted architecture so that platform developers can code their custom pages and add them to the Witboost UI.

Practice Shaper​

The Practice Shaper is the main and most impactful Witboost setting that models the platform entities (domains, systems, components, templates) as nodes and their relationships of a fully-configurable property graph of a set of Data Landscapes.

This enables data-oriented organizations to shape Witboost based on their unique use cases, structure, and needs. It is defined using a series of building blocks: Domain Types, System Prototypes, System Types and Component Types. Each concrete Data Landscape will contain their own set of instances of Domain Types, System Types or Component Types, or share it among themselves.

In order to understand how to use this setting to register Data Landscapes, check out this section of the documentation.

Domain Type​

A Domain type represents a class of domains. Typical instances of Domain Types are Business Domain, Departments, Processing Layer, Data Domains, etc. which might belong to a specific Data Landscape or to more than one. Thus, instances of Domain Types are not tied to a specific landscape but rather act as a cross-functional type that several landscapes can use.

System Type​

A System type represents a class of system that belongs to a specific Data Landscape. A instance of a system type is part of a particular instance of domain type and can be composed of a set of different instances of component types. Typical instances of System types are Data Products, Source Systems, ML Projects, etc.

System Prototype​

A System Prototype is designed to enable the creation of a new system by defining its core concepts, while still being in the early design and validation phase. System prototypes are heavily linked to system types as they are designed to evolve into a specific system type when they are validated and exit the prototype phase.

Component Type​

A Component type is analogous of a System Type for system, but for a component. They represent a class of component that are designed to be a part of a specific System type. Component types are also designed to be shoppable and/or consumable, which define the behaviour of the publication and access control flow on the Market Plane.

Events​

A fixed set of actions inside Witboost trigger the creations of events that are stored internally and allow to store and follow the platform activity, as well as ensuring accountability and traceability.

Notification​

Some event triggers (namely those that may be important to the user base) create notifications, which are messages sent to a set of platform users particular to the notification being created. These notifications are sent on the Witboost platform, but it also supports the configuration of Notification Webhooks to send notifications to external services.