Known Issues and Limitations
- Known Issues and Limitations
- Automation
- Output Display
- Data Type Incompatibility
- Script Execution via GraphQL Query
- Business Intelligence
- Handling of Empty Values in Tables
- Monitoring Agent
- Activity Collection Limitations
- Program Activity Tracking Characteristics
- Program Crashes
- Monitoring Agent Update
- Monitoring Agent Removal
This page describes known limitations in the Operavix system by module:
Automation
Output Display
If table columns have identical names before the dot (e.g., col.id, col.employee), these columns will appear as nested in script output (col: id, employee).
Data Type Incompatibility
The Int64 and UInt64 data types are incompatible. During script execution, errors may occur when transferring data between columns of these types.
Script Execution via GraphQL Query
Only scripts with the Manual start trigger can be executed via GraphQL. Scripts with the Scheduler trigger cannot be executed this way — they can only be enabled or disabled, but not run once via a query.
Business Intelligence
Handling of Empty Values in Tables
Created and imported tables are stored on user ClickHouse servers. For each value, a field with the corresponding data type is created. For each field with the Nullable property, two fields are created in the database.
ClickHouse uses the following for storing Nullable fields:
- A separate file with NULL masks. The mask determines whether a cell contains
NULLor a value - A file with values
If the mask indicates that a cell contains NULL, the values file stores the default value for the data type. For example, if the field is of type Nullable(Int8), the cell will store the default value for Int8. This behavior increases storage size.
Using the Nullable property reduces performance. Consider this when designing databases.
Monitoring Agent
Activity Collection Limitations
The monitoring agent uses UI Automation technology. Where this technology is not supported, activity collection may be limited.
If an element does not emit a focus event, it is not recorded in the activity log.
Program Activity Tracking Characteristics
The monitoring agent may record robotic activity outside working hours. Such robots may include file-transfer bots and others. In the “monitoring_activity” monitoring table, the input_type field will contain 0. In some cases, input_type will be 1 if the agent could not recognize the activity as robotic (e.g., if the robot generated insufficient activity for analysis).
Windows OS
The monitoring agent installed on Windows OS has the following program activity tracking characteristics:
- For applications where the FilePath of an open file cannot be obtained, the wrong path is tracked after saving a document. In such cases, only the file name is recorded in the path
- Keystrokes F1–F12 are not captured when they perform hardware functions (e.g., adjusting screen brightness, volume, etc.)
- Microsoft Excel: cell editing and right-click context menu actions are not captured
- Desktop applications with a top menu bar and a toolbar with icons (e.g., Notepad++, WinRAR, 7-Zip) do not capture clicks on toolbar buttons
Linux OS
- In Linux environments, the Operavix Monitoring Agent uses the AT-SPI (Assistive Technology Service Provider Interface) technology to inspect user interfaces. This technology has several system-level and architectural limitations:
- Data collection completeness cannot be guaranteed: some events are captured incompletely or lost at the system level due to event handling specifics and the lack of UI element caching. Unlike Microsoft UI Automation, AT-SPI does not cache interface element properties. Elements that disappear immediately after interaction (e.g., dropdown menus, pop-up dialogs, refresh buttons) are permanently removed from the accessibility tree before the agent can retrieve the necessary information.
- Collection quality directly depends on the correctness of accessibility API implementation in the applications used and the quality of their interaction with accessibility technologies. Applications with incomplete or incorrect accessibility API support may provide limited or distorted user activity information.
- Control over disappearing elements (e.g., dropdown menus or dialog boxes) is difficult or impossible, as they may be removed before the agent captures the event.
- Different Linux distributions, desktop environment versions, and components may implement AT-SPI with variations, further affecting monitoring functionality.
- Using the monitoring agent in Linux environments implies the customer’s acceptance of the above technical limitations. Operavix is not liable for incomplete or missing data due to reasons beyond the company’s control or technical capabilities.
The monitoring agent installed on Linux OS has the following program activity tracking characteristics:
- In Chromium-based browsers, Copy and Paste events via the context menu are not captured.
Program Crashes
Microsoft Office
UI Automation collection is disabled in the main document window because program crashes may occur when the monitoring agent is installed. Clicks in the main window (e.g., right-click context menu) are not captured, so Copy and Paste events from the context menu are not recorded.
Microsoft Outlook 2013 and 2016
Program crashes may occur in the following cases:
- When attaching more than one file to an email or filling in the Attachment field
- When switching to the Tasks tab and back
Monitoring Agent Update
Updating the agent may cause errors if the previous version was installed using a GPO file and uninstalled using an EXE file.
Monitoring Agent Removal
After removing the monitoring agent, the OperavixAgent folder is not deleted from the AppData folder.
Was the article helpful?