Bug Fixes
Revealed Agent Would Capture IMs When Not Active
Due to a bug in the network interception mechanism, the Revealed Agent would continue to capture IM activities even when the user stopped the Agent (by pressing the "Stop" button) and there was active tasks.
The bug seems to affect Agent versions 5.0 and 4.1 but other versions might be affected too.
The bug is fixed now so that the Revealed Agent will not monitor any IM conversations if it's stopped.
Online Meetings on RingCentral Not Captured
Due to some recent changes introduced by RingCentral, the Agent had been unable to capture online meeting activities on RingCentral. As a result, no incoming or outgoing meetings on RingCentral would be displayed on the Monitoring > Online Meetings report.
The bug seems to affect Agent version 6.1 but other versions might be affected too.
The bug is fixed now.
Online Meetings on WebEx Desktop Not Captured
Due to some recent changes introduced by WebEx, the Agent had been unable to capture online meeting activities on the WebEx Desktop client. As a result, no incoming or outgoing meetings on WebEx Desktop would be displayed on the Monitoring > Online Meetings report.
The bug is fixed now.
Online Meetings on WebEx Web Not Captured
Due to some recent changes introduced by WebEx, the Agent had been unable to capture online meeting activities on WebEx Web. As a result, no incoming or outgoing meetings on WebEx Web would be displayed on the Monitoring > Online Meetings report.
The bug is fixed now.
Teramind Instance Would Crash When Handling Large Groups on WhatsApp Web
Due to a bug in the Agent's IM parser module, sometimes it would cause the server to crash if a user engaged in conversations with a large group (e.g., about 50 or more participants) on WhatsApp Web. As a result, the Agent wouldn't be able to connect to the server and the group conversation wouldn't show up on the Monitoring > Instant Messaging report.
The bug is fixed now.
Some Websites Monitoring Settings Wouldn't Work for Some URLs
Due to a bug, websites monitoring settings (Monitoring Settings > Monitoring Profile > Websites) that accept a URL (for example, MONITOR ONLY THESE WEBSITES, DON'T MONITOR WEB TRAFFIC FOR THESE WEBSITES, SUSPEND MONITORING WHEN THESE WEBSITES ARE VISITED, etc.) wouldn't work for some websites/URLs that contained special characters (for example, #).
The bug is fixed now so that website addresses/URLs with special characters will be detected properly and the monitoring settings will work as expected.
Files Content Rule Would Ignore the File Operation Condition
Due to a bug, Files Content Rules would ignore the File operation condition causing the rules to get triggered for any file operation. For example, the rule below would incorrectly block all file operations such as Copy, Access, Write, Upload, Rename, Delete, etc. instead of just blocking the Copy operation:
The bug is fixed now.
Duplicate Entries on Emails Reports When Mails Sent From Outlook Web
Due to a bug, any email sent from the Outlook Web would generate duplicate entries on the BI Reports > Emails, Monitoring > Emailing, etc.:
However, the attachment column would only be shown for the first entry.
The bug is fixed now.
Disabling Password Field Monitoring Wouldn't Work Sometimes
Due to a bug, the MONITOR KEYSTROKES FOR PASSWORD FIELDS option (Monitoring Settings > Monitoring Profile > Websites) might get ignored when certain applications (e.g., MS Access, inora.exe, Data Maintenance.exe, etc.) were opened. As a result, even if you turned off the MONITOR KEYSTROKES FOR PASSWORD FIELDS option, password fields on websites might get captured. Additionally, other, unusual behavior might occur in those apps (e.g., cells getting duplicated).
The bug is fixed now.