May 2021

Enhancement

To help direct the daily tasks and governance goals of our Knowledge Tier users, we improved the Director Dashboard. We renamed the dashboard to Knowledge Tier Overview because it provides a comprehensive view of your assets and how value can be added to your assets by filling gaps in the assets' information or creating relevant asset relationships. The improved dashboard is updated multiple times daily, so the data displayed is more relevant to daily tasks for which your governance team may want guidance. Users with the Director persona will land on this dashboard when they open the Knowledge Tier. Navigate to https://dm.syniti.com/dashboard/knowledge-tier-overview to access this dashboard. Refer to Knowledge Tier Overview Dashboard for more information.

Bug Fixes

• [KYB-2242]-Fixed an issue that supported case sensitivity when creating user accounts. NAMEAbc@Company.com and NameABC@company.com, for example, were treated as different emails and therefore two different user accounts could be created.

• [KYB-2404]-Fixed an issue where a rule's asset ID displayed as “undefined” in the search results, but was defined on the asset detail page. The rule's asset ID now displays in the search results and on the asset detail page as expected.

Bug Fix

[KYB-2391]-Fixed an issue that occurred if you ran a PUT API call against any asset type that had categories assigned to it (returned from the GET API call as has-a). When the category relationship type was set to has-a, it caused a failure for the PUT API call. It is now correctly processed as a category relationship.

Enhancements

• The process to relate assets (i.e., add a relationship to the asset detail page) has been streamlined and improved:

  • Assets are now related with a single, bi-directional relationship, shown as either Outbound or Inbound, instead of being related to a specific version of the asset.

    • Outbound relationships are defined from the current asset to another asset and display immediately.

    • Inbound relationships are those defined by another asset relating to the current asset. A relationship for a governed asset (terms, rules and policies) only displays as inbound once the asset is published. A relationship for systems and data sets displays as inbound as soon as the relationship is added.

• The process to add relationships to any asset now functions like term-to-term relationships.

• A type-ahead feature is now available to easily filter to the top five related matches when relating assets.

• Goal and Initiative relationships are now tabs on the asset detail pages instead of options in the side panel. This allows for a consistent look and functionality that aligns with the other asset relationships.

• All new tenants are delivered with the following relationships:

  • links to-If Asset A links to Asset B, then Asset B is linked to Asset A.

  • is related to-If Asset A is related to Asset B, then Asset B is related to Asset A.

  • is synonym of-If Asset A is a synonym of Asset B, then Asset B is a synonym of Asset A.

  • has a(n)-If Asset A has a(n) Asset B, then Asset B is a part of Asset A.

  • is a(n)-If Asset A is a(n) Asset B, then Asset B is a(n) Asset A.

  • is like-If Asset A is like Asset B, then Asset B is like Asset A.

    Refer to Relationships for more information.

• We are excited to feature inline help in the Knowledge Tier. When you see a purple ? icon, hover over it for a description of the functionality.

Bug Fixes

• [KYB-2211]-Fixed an error that prevented static guidance from displaying in the Guidance panel when you attempted to add a system. Instead, an "error evaluating guidance condition" message displayed. With the fix, guidance displays when adding a system as expected.

• [KYB-2094]-Fixed an issue that occurred when you edited a term and either saved or canceled the action. Relationships that had been saved on the Fields tab displayed blank until the page was refreshed. With the fix, save and cancel work as expected on the Term Asset Detail page.

• [KYB-2336]-Previously, if a version of an asset was contested or canceled during review, the list of reviewers was maintained on the review panel. However, deleted user accounts were not included in the reviewer list and therefore could not be deselected as a reviewer. Ultimately, this meant that an asset version could never be endorsed if the number of deleted users was 50% or greater of the assigned list of reviewers. This issue has been fixed and deleted users are removed as expected.