FAQs¶
Common questions for DTV are as follows:
Q: How can I export and import pages/templates across OUs?¶
A: Since the configuration ID of a page is unique between different OUs, you cannot import the same file multiple times within an environment. It is recommended to use the following methods to reuse pages or templates between OUs:
Duplicate this page/template within A OU.
Export copied pages/templates.
Import exported pages/templates into B OU.
Go back to A OU and delete the copied page/template.
Q: How do I develop data visualization pages using DTV?¶
A: Open your project in DTV Dashboard, select the DT dashboard page and proceed to start creating and editing widgets in a drag-and-drop manner. DTV empowers users to achieve data visualization through a no/low-code experience.
Q: How do I embed visualization pages developed in DTV in my applications?¶
A: There are three ways to achieve this:
By using Iframe and page URL to embed the pages.
You can perform in-place editing using DTV’s SDK.
You may also utilize the URL shortcut function in Application Portal’s toolbar menu to embed DTV pages into your application.
Q: What data authentication methods does DTV provide?¶
A: DTV Workspace can isolate user data with different data authentication methods. There are many authentication methods, such as Application Portal, EnOS Management Console, Cookie (all newly created authentication methods use Cookie), no authentication and so on.
Q: What data capabilities does DTV provide?¶
A: DTV data sources are divided into three types, external data sources, built-in data sources, and open data sources.
External data sources: Provide external data access capabilities such as Swagger, Restful, MySql, Data Federation, and so on.
Built-in data source: Built-in TSDB and Common Data Service data services that are ready to use.
To access asset data in DTV, you need to authorize the asset model to the DTV service account in the EnOS Management Console, and add theauth_unit:truetag on the model.Open data sources: Data sources used by all OU in this environment are available.
Q: What are the key features of DTV?¶
A: DTV is divided into two parts: statistical analysis KPI dashboard engine (Dashboard) and real-time monitoring visual engine (DTM, DT Monitoring).
Dashboard allows users to develop indicator data visualization pages for operational scenarios.
Dashboard allows users to develop status data visualization pages for monitoring scenarios.
Dashboard and DTM are developed under DTViz, an application in the same Application Portal, and the developed visualization pages can be embedded in third-party applications.
Functional level: In addition to basic data representation and widget selection, Dashboard also provides widget linkage, global filtering and other functions.
Dashboard provides the widget template function which allows users to save a configured widget as a widget template for repeated use.
Dashboard provides the page template function which allows users to combine configured widgets and save it as a page template for repeated use.
Q: How are data rights defined in DTV?¶
A: The data rights definition mechanism of DTV is: filtering data rights with assets as resources. The mechanism is: calling the data service interface through the user identity (token) in the Application Portal, thereby realizing asset authentication.
Q: How does DTV discover data?¶
A: Data sources are largely divided into two categories: Built-In and External.
Data Source |
Category |
Built-In/External |
Data Type |
Can it be shared across OUs? |
Authentication Method |
|---|---|---|---|---|---|
TSDB |
LatestData |
Built-In |
Model |
No |
Data authentication with OU granularity based on EnOS IAM token |
Current Day Electric Power |
Built-In |
Model |
No |
||
Electric Power |
Built-In |
Model |
No |
||
DI Data |
Built-In |
Model |
No |
||
AI Raw |
Built-In |
Model |
No |
||
AI Aggregation |
Built-In |
Model |
No |
||
Generic |
Built-In |
No |
|||
Raw Data |
Built-In |
No |
|||
Common Data Service |
Realtime |
Built-In |
Model |
No |
|
Timeseries |
Built-In |
Model |
No |
||
Alarm |
Built-In |
Model |
No |
||
Topology |
Built-In |
Model |
No |
||
Data |
MySQL |
External |
Dataset |
Yes |
Database account authentication |
Data Federation |
External |
Dataset |
Yes |
||
OLAP Fact |
Built-In |
Dataset |
Yes |
||
OLAP Metrics |
Built-In |
Dataset |
Yes |
||
Static Data |
External |
Static Data Source |
Yes |
||
API |
Swagger |
External |
Assets |
No |
Third-party IAM service authentication: the authentication method and path are specified in the workspace |
Restful |
External |
Assets |
No |
Note
Models that users can see in DTV = the number of assets authorized to the DTV Service Account (SA) in the EnOS Management Console.
Asset data that users can see in DTV = the number of asset instances configured for the access account in the Application Portal.
The asset data that the user wants to access in DTV needs to be tagged with
auth_unit : true.
Q: How do I set the Resolution Response for the three response modes: big panel, web, and mobile?¶
A: You can set the ranges of the three response modes through the Resolution Response Setting, and when the screen resolution falls within the resolution range of a mode, the layout of that mode will be displayed in response.
Note
The web mode resolution should be smaller than the big panel mode resolution, and you can only input positive integers.
Q: After updating the page configuration, the published page did not reflect the changes, why?¶
A: After updating a page, it needs to be republished for it to reflect the latest changes.