You can use knowledge objects in queries and use them to create other knowledge objects. This article explains the following ways in which you can also work with knowledge objects:
Changing the visibility of knowledge objects
You can set knowledge objects to be hidden or visible.
- Visible objects can be viewed and searched for by all users in object lists, and can be used to define knowledge objects, as well as being used in queries. Objects are visible by default.
- Hidden objects are only visible to admin users, and cannot be used in queries or to define objects. However, hidden objects still appear in object lists. You can use this setting to keep drop-down lists manageable, since hidden objects are not shown in drop-down menus in query and object builders. You can also use the hidden setting to prevent users from using specific objects.
Object visibility and ownership
Any Interana user can toggle any object to be visible or hidden.
The visibility status is not related to object ownership. If you want to use an object in a query or when defining an object but otherwise want it hidden from lists, first make it visible, use it, then turn it back to hidden. Other users won’t be able to accidentally use a hidden object in a query or object definition, but the data in the hidden object might be helpful as part of something else.
For example, if you have a raw event property that has important data but needs to be cleaned up, you can create another event property (a manual context) for the clean version, then hide the original raw event property. Users will then pick the right event property, using the one with a friendly name.
Basically, you want to hide objects that users don't rely on, or things they shouldn’t use. However, there are also more complex reasons, such as needing to create an Event Property A that is defined by an Event Property B which is in turn defined by a Raw Event Property C. In that case, you’ll want to hide Event Properties B and C.
Favoriting knowledge objects
Users from across your organization who are not familiar with your data schema will want to be able to easily identify objects for use in their queries and reference the correct data. Keep in mind that users who aren't involved in naming the knowledge objects may not know which objects are the correct ones to use in a sentence. This is especially true if knowledge objects have similar names.
Favoriting knowledge objects can help guide users in their selection for queries. Admins may want to consider favoriting the following types of knowledge objects:
- Which data objects are officially approved, or sanctioned by a trusted authority at your organization?
- Which objects are used most often?
Providing information about each object, and examples of values when applicable, also help users to the correct objects for their queries.
Types of favorites
There are two categories of favorites:
- Personal favorite: This can be applied by any user, and is only visible to that user. However, an object's popularity rating is based on the number of times it has been marked as a favorite by users. Personal favorites are identified by a gold star.
- Admin favorite: This can only be applied by admin users, but it's visible to all users. Admin favorites are identified by a gray star.
Favorited items appear at the top of lists, in alphabetical order. Personal favorites are shown before admin favorites.