Metric Management
The metric platform manages metrics through business themes and authorizes their usage. In metric management, business administrators create relevant themes based on business needs, add business-related metrics to the themes, manage the activation and deactivation of metrics, and authorize the themes and their associated metrics for use by other users within the platform.
This article primarily introduces how business administrators can create business themes, manage metrics, and authorize business themes for use by other users under metric management.
Create a Business Topic
Indicator management is composed of business topics, each containing indicators and subtopics. Below is an introduction to creating business topics and adding indicators.
Click the blue "+" under Indicator Management, enter the topic name in the popup window, and click Confirm. This creates a new business topic under Indicator Management.
To add indicators under a business topic, click "Add Indicator" within the topic and select the indicators you want to add. You can use filters to screen different types of indicators.
If the business topic contains subtopics, you can click the "+" to the right of the topic to add subtopics to it.
Tips
- Indicator management requires users to have three user roles: system management, data management, and indicator management, to qualify as a super business administrator. Super business administrators can create business topics in the root directory of indicator management. Super administrators can authorize business topics in the root directory to regular administrators (regular administrators have data management and indicator management roles) for management.
- The same indicator can be added to multiple business topics. If an indicator is related to multiple business topics, it can be added to the relevant business topics.
Business Theme Management Metrics
Metrics can be added to business themes and their sub-themes for management. Metrics within a theme can undergo operations such as publishing, unpublishing, removal, and other related actions.
- Publish: After executing the publish operation, the metric enters a published state, allowing users to view and analyze the metric. Metrics are in the published state by default upon addition.
- Unpublish: After executing the unpublish operation, the metric enters an unpublished state, and users cannot view or use the metric.
- Remove: Metrics can be removed from the business theme when they are no longer needed.
- Refresh: Update metric information.
- Edit: Edit the metric. This requires permissions for the dataset containing the metric and the data management role.
- Enter Dataset: Access the dataset where the metric was created to view and manage the metric. This requires permissions for the dataset containing the metric and the data management role.
Operations Related to Business Topics
Business topics support operations such as renaming, authorization, deletion, vectorization of business topics, and Chatbot configuration.
- Create a Subdomain: Add subtopics under a business topic.
- Rename: Modify the name while editing a business topic.
- Delete: Delete a business topic when it is no longer in use. Deletion requires the business topic to be empty, with no subtopics or metrics.
- Permission Management: Business topics can be authorized to other users through permission management. Below is a detailed introduction to the operations users can perform after authorization.
- Vectorization of Business Metrics Topics: Process business metrics topics through vectorization to enhance data understanding. This feature is visible only after configuring the AI License. See AI Vector Library.
- Chatbot Configuration: Provide a data Q&A bot in instant messaging tools, supporting ChatBot configuration for WeCom/Feishu/DingTalk. This feature is visible only after configuring the AI License. For details, see ChatBot.
Business Topic Permission Management
When managing permissions for business topics, users are provided with the following two types of permissions. If the User Role includes the metric management role, they can simultaneously have Permission 1 and Permission 2; otherwise, they only have Permission 2.
Permission 1: Business topics can authorize other users as managers, editors, viewers, or tenant users. Authorized users can jointly manage and view the business topics.
- Manager: Manages the business topic, including editing, deleting, permission management, adding subtopics, and adding metrics.
- Editor: Edits the business topic, including editing, deleting, adding subtopics, and adding metrics.
- Viewer: Views the business topic and the metric information under its subtopics.
- Tenant User: Authorized tenants can view the business topic and the metric information under its subtopics in the tenant system's metric management module.
Permission 2: After a business topic is authorized to other users, the authorized users can see the relevant business topics and the metrics under their subtopics in Metric Analysis -> Metric Marketplace. They can perform business analysis on these metrics in the Metric Analysis Dashboard.
Tip
The same business metric can be included in multiple topic domains. It will be treated as two independent metrics in different topic domains. Having permission for one topic domain does not automatically grant the user viewing permission for the same business metric in another topic domain.
The administrator of a business metric must have management permissions for the dataset where the metric library resides in order to add the business metric to a topic domain in the metric management module. This check is only performed when the metric is added to the topic domain. Therefore, even if the administrator later loses management permissions for the dataset, it will not affect the usage of business metrics already added to the topic domain.
Viewing Permissions for Business Metric Data in Business Topics
After a business topic is authorized to a user, the user will automatically be granted viewing permissions for the underlying data package. The row-level permissions for the underlying data are restricted by the row-level permission configurations in the data package.