What's new in dataspot. 4.0
· 5 min read
Basic functions
| Functionality | Description |
|---|---|
| Workflow | The new parameterizable workflow can be assigned and defined individually for each model. It is possible to define which roles can perform which changes conforming specifically to your own governance processes. |
| Authorization | The role-based authorization concept is closely related to the workflow definition. Read and write permissions are assigned based on the role of the user, rather than depending only on their access level. |
Access level Author | Due to the role-based authorization concept, the access level Author is obsolete and has been removed. All previous authors are automatically migrated to Editor. The role-base authorizations are defined in the workflow. |
| Collaboration | Collaboration is supported by means of issues and discussions. Metadata discussions as well as change requests or bugs can be attached directly to the respective assets. Business and technical discussions are accessible to the data excellence community and decision-making is facilitated. |
| Approval | In a workflow, approvals can be required in the event of status transitions. If defined, an approval is automatically triggered for an asset and ensures that the responsible persons agree to the status transition. The criteria for an approval or a rejection can be defined in the workflow. |
| Notifications | Responsible persons are informed about changes to assets by means of notifications. Pending notifications are displayed in the user interface and can be configured individually for each workflow. |
| Responsibility | Roles and agents (persons, groups, or posts) can be responsible for assets independently of each other. Acting in the selected role, the agent is responsible for the asset as well as all any subordinate assets. If the selected agent is not a person (i.e. a group or a post), then the responsibility is automatically delegated to the underlying persons. |
| Measurement | Comments can be recorded for individual measurements, documenting additional information regarding the measurement (e.g. plausibility checks). These comments are also output in exports and reports. |
| Derivation | Business or technical derivations can be defined for data domains and data types. |
| REST/API | The OpenAPI Specification of the REST/API can be accessed at the path /specification/openapi.yaml or /specification/openapi.json |
| Manual | The complete manual is available in English. |
Import/Export & Reports
| Functionality | Description |
|---|---|
| Project Report | The new project report makes it possible to get all information from assets assigned to a project in a single document. |
| Mandatory fields in Excel | In Excel exports, all mandatory fields are marked with a background color. Both mandatory standard fields as well as mandatory customer-specific fields are marked. |
| Data Quality Report | The data quality report has been extended to display the last two measurements per measured system. In addition, a trend is shown based on these measurements. Measurement comments are also printed. |
Usability
| Functionality | Description |
|---|---|
| Asset access | Assets can be accessed directly by their unique identifier using the path {db}/assets/{id}. |
| Single sign-on | Single sign-on is now possible in multi-tenant mode. |
| Expand and collapse | All data, which can usually be opened and closed item by item, can now be expanded or collapsed by clicking on the buttons "Expand all" or "Collapse all". |
| Ticket search | The ticket search makes it possible to quickly get an overview of all open and closed tickets. |
| Markdown Editor | The markdown editor provides a quick link (icon ?) to a markdown quick reference page. |
| Diagram | The diagram of a business data model has been extended to include relationships to business objects marked as favorite. |
| Lineage diagram | Translations are displayed in the lineage diagram if they are part of the lineage. |
| External Links | Links to external sources are always opened in a new tab, allowing additional content to be displayed without closing the current page. |
| Sort sub-assets | Sub-assets (subprojects, subdatasets, and subsystems) can be sorted by name and status. |
| Dashboard | Issues and approvals as well as notifications are displayed directly in the dashboard. |
| Editor | The asset editor can be closed with the keyboard shortcut CMD/CTRL + Enter. |
Configuration
| Functionality | Description |
|---|---|
| Mandatory custom properties | Custom properties can be marked as mandatory. In the user interface, the corresponding input fields are displayed as mandatory fields. New assets with mandatory properties can only be added after all mandatory fields are filled. For existing assets, the mandatory fields must be specified before the asset can be saved during the next modification. Mandatory properties can also be combined with default values. |
| Group custom properties | Custom properties can be arranged in a group. In the user interface, the corresponding input fields are arranged according to these groups. |
| Status | Existing status can be edited and new status can be added, allowing the workflow to conform specifically to your own governance processes. |
| Icons | The Font Awesome library (see icon) has been updated to a new release (6.1). During migration, the names of the old icons are automatically mapped to new icons. |
