EnOS Known Issues and Limitations
This article lists the known issues and limitations of EnOS, categorized by products and services.
Application Enablement
These tables list the known issues and limitations of Industry Application Common Building Blocks.
Application Portal
Issue Description |
Workaround |
Discovered On |
The logs on assigning or removing assets do not appear in the audit log list. |
None |
2023/02 |
In the audit log list, the User of the logs triggered by a removed user is “-“. |
None |
2023/02 |
In an exported audit log file, the Resource Type of Export Users events is “null”. |
None |
2023/02 |
Common Data Service
Issue Description |
Workaround |
Discovered On |
If a data source key is unique in the current OU but not in the current environment, the data source cannot be registered in Common Data Service. |
Use another data source key. |
2023/02 |
After an object type is deleted, the dimensions, metrics, measurement points, and attributes associated with it cannot be deleted. |
Contact System Administrator to delete the associated dimensions, metrics, measurement points, and attributes. |
2023/02 |
Work Management
Issue Description |
Workaround |
Discovered On |
When the system theme is Black and white, the Service Requests and Work Orders menus will show the Edit Column button and the corresponding pop-up window in the top right of the list as black, overlapping the black background. |
None |
2023/02 |
Device Connectivity & Management
These tables list the known issues and limitations of Device Connectivity & Management.
Alert Engine
Issue Description |
Workaround |
Discovered On |
Occasionally, alert records may be lost when a large amount of delay alerts occur continuously in a certain time period. |
None |
2023/02 |
Only limited performance are provided by Alert Engine when the alert rules with multiple measurement point are triggered. |
None |
2023/02 |
Data Management and Analytics
These tables list the known issues and limitations of Data Management and Analytics.
Device Data Integration Service
Issue Description |
Workaround |
Discovered On |
Since the upgraded version is not compatible with the old version of Notification Management, the OU admin can not obtain the verification code and users can not import the ZIP file when creating a custom node. |
Contact EnOS support team to change configuration items and users can use the universal verification code to import the ZIP file. |
2023/02 |
HTTP Client & Refresh Token node: If you select POST (also PUT and DELETE in HTTP Client node) in Request and enter Content-type in the key of Headers, the value you entered will be overwritten by the default value application/json; charset=UTF-8 , which has no effect on other keys. |
Import the custom-node.zip to create a custom node to customize the value in Content-type key. |
2023/02 |
Time Series Data Management
Issue Description |
Workaround |
Discovered On |
Modify TSDB storage policy storage duration: If the data size of the table corresponding to this storage bucket is large, it will take a long time to update the storage duration, and the data under this table may not be available for TSDB service during the update period. |
None |
2023/02 |
AI Studio
Issue Description |
Workaround |
Discovered On |
Git is unavailable for Notebook instances using Azure storage. |
Use Ceph storage instead. |
2023/02 |
Data Synchronization
Issue Description |
Workaround |
Discovered On |
The SFTP data source is unable to synchronize its structured data from the database to the EnOS Hive data warehouse. |
Use an FTP data source to implement data synchronization. |
2023/12 |
The FTP data source using FTPS protocol is unable to synchronize its structured data from the database to the EnOS Hive data warehouse. |
Use an FTP data source to implement data synchronization. |
2023/12 |
Documentation
This table lists the known issues and limitations of Documentation.
Issue Description |
Workaround |
Discovered On |
Partial or no search results are returned occasionally. |
None |
2023/02 |