List of Contributions

As part of our international expansion where English may not be the language understood by the audience of Data360, we need localization of the Data360 Govern UI, artefacts, field label & values. The user would select his language amongst the accepted ones, e.g. English (default), German, French ...

When browsing the parent asset, we want to add a child under that parent with a ‘+’ button. This optimizes operations, gains in efficiency and procures a better UX. Example: We created a business asset Term (child) as part of a business asset Concept (parent) with the Parent-Child configuration. The ...

When a Data360 artefact (asset, rule, relationship etc.) has been deleted, there is no way to recover it. There is no possibility to see all assets that has been deleted. This may lead to tremendous impact on Data Management practices and on systems that consume Data360 artefacts. We need a Recycle ...

We need an automatic assignment of the Creator responsibility to the creating user, at the creation time of a Data360 artefact. In other words, we need the possibility to assign automatically the Id of the user, who is creating new Data360 artefact, to the “Creator” Responsibility.

We need the ability to roll back to previous changes. Errors in manipulation (e.g. a deleted relationship, a changed or deleted field value, etc.) happen to everyone, even unintentionally. We want to recover from accidental changes.

We ask for multiple selection of Class:Type elements when creating or modifying an Ownership Rule. This avoids creating various instances of the Ownership Rule for different Class:Type, since it groups an identical Ownership Rule for multiple Business Assets together. The user earns in efficiency and ...