July 2021

Enhancements

• The Knowledge Tier now supports adding relationships between Data Sets.

• Previously, the type-ahead feature filtered the top five related matches when relating assets, even if there were more than five matches. Now, it returns the top 50 related matches.

• "Deep Guidance" has been simplified and renamed to "Guidance" throughout the Knowledge Tier UI.

• To ease confusion around inbound and outbound relationships, and to clarify the fact that destination relationships won't appear for the asset until the asset is published, the following enhancements were made:

  • We removed the headings "Outbound" and "Inbound" from the asset detail pages. Relationships are now ordered alphabetically with each related asset listed underneath. You may edit relationships defined from the originating asset (i.e., the current asset) to another asset. However, to edit relationships defined on a destination asset (as in, another asset) to the current asset, you must navigate to the originating asset.

  • We added the status of the asset along with a tooltip display on the asset detail page for relationships on governed assets (terms, rules and policies) that have not been published.

  • We added several new tooltips to the asset detail page to increase usability.

Bug Fixes

• [KYB-2559]-Fixed an issue where the Status of an asset when related to another asset was In Process, regardless of the asset's actual Status.

• [KYB-2677]-Fixed an issue that prevented you from being able to add a custom relationship to an asset if the relationship had the same name as a previously deleted relationship.

Enhancement

To improve the user experience for those who work using multiple tenants, we now display the Tenant name on the User Profile list box. To copy the Tenant ID to your clipboard, click the Tenant name.

Bug Fix

[KYB-2013]-Previously, when users tried to create a Data Set with more than 65 characters in the name, the Data Set couldn't be saved and no error message would display. With this fix, when users try to save a Data Set with more than 65 characters in the name, an error message displays to let users know there was an error that occurred when trying to save the Data Set.

Enhancement

The type-ahead feature to add an asset relationship on the Asset Detail page requires at least 3 letters of the asset to be entered. The feature now includes a watermark to prompt you to enter at least 3 letters in order to filter the asset.

Bug Fixes

• [KYB-2624]-Fixed an issue on the Asset Relationships page in Admin where when you selected the first relationship, the URL did not update to include the asset ID for that relationship.

• [KYB-2718]-Fixed an issue that prevented Author user roles from adding or editing asset relationships.

New Feature

Administrators can now deactivate and activate user accounts. When a new user account is created, it is active by default. A few notes about deactivated accounts:

• There are visual indicators throughout the Knowledge Platform to distinguish between active and deactivated accounts, such as:

  • The user's name is appended with "(Inactive)" in all areas where user names are displayed, such as Sponsors lists, Assigned To lists, in bulk update and in search facets and results. Use the hover tooltip to view the full name in an event the appending text causes the name to extend beyond view.

  • The user's name displays in gray (versus blue for active accounts) on the Accounts page and across the Knowledge Platform.

  • The avatar is white for deactivated accounts as opposed to a blue avatar for active accounts

• All fields on the Accounts page are read-only; Administrators cannot update a user's account if it is deactivated.

• Deactivated users cannot be assigned to assets or included in the review process

Note

For non-SSO tenants, user accounts can no longer be deleted. For SSO tenants, this is a new feature. Administrators no longer have to go through the company's portal administrator to deactivate (delete was the previous functionality) a user account.

Refer to Deactivate or Activate a User Account for more information.

Bug Fix

Previously, when users tried to create a Data Set with more than 65 characters in the name, the Data Set couldn't be saved and no error message would display. With this fix, when users try to save a Data Set with more than 65 characters in the name, an error message displays to let users know that an error occurred when trying to save the Data Set.