Veritas Alta™ Surveillance User Guide
- Introducing Veritas Alta Surveillance
- Getting started
- Working with dashboard widgets
- Managing employee groups
- Managing departments
- About departments
- Understanding the Departments page
- Searching departments
- Creating departments
- Moving existing departments under other departments
- Adding monitored employees and employee groups to departments
- Editing monitoring policies
- Editing department details and monitoring policy
- Managing exception employees
- Designating employees as exception employee
- Assigning further exception reviewers to an exception employee
- Removing exception status
- Removing exception reviewers
- Managing department users
- Managing department-level searches
- Managing department-specific hotword sets
- Managing department-specific labels
- Managing department-specific trash rules
- Managing department-specific allowlist rules
- Managing department-specific review comments
- Viewing employees associated with departments
- Managing users, roles, and permissions
- Managing application-level searches
- Managing application-specific hotword sets
- Managing application-specific labels
- Managing application-specific trash rules
- Managing application-specific allowlist rules
- Managing application-specific review comments
- Managing data requests
- Managing search schedules
- Managing export operations
- Managing reviews
- About reviewing with Alta Surveillance
- Limitations on reviewing certain types of Skype for Business content
- Understanding the Review page
- Changing the Preview pane position
- Rearranging columns in the item list pane
- Filtering the items in the Review pane
- Viewing dynamic review item counts on the calendar
- Reviewing searched items
- Adding or removing text for machine learning
- Assigning review status to items
- Viewing hotwords highlighting
- Viewing hotwords in collaboration message
- Viewing tags highlighting
- Viewing predicted labels of review items
- Viewing the full content in a new window
- Adding comments to items
- Escalating the review items
- Applying labels to items
- Viewing history of items
- Printing and downloading the items and attachments
- Viewing Intelligent Review Details
- Working with reports
- About Alta Surveillance reports
- Predefined reports
- Enhanced reporting
- Configuring a reporting endpoint
- Authentication
- Departments API
- Users API
- UserRoles API
- Roles API
- ItemMetrics API
- ReviewerMapping API
- MonitoredEmployees API
- Evidence Of Review By Dept Async API
- Report Status API
- Evidence of Review by Department API
- Supported OData query options
- Supported reporting endpoint API filters and their values
- Responses
- Managing Power BI templates for reporting APIs
- Guidelines for using Alta Surveillance templates with Microsoft Power BI Desktop
- Configuring Microsoft Power BI Templates for Reporting APIs
- TEMPLATE - Item Metrics
- TEMPLATE - Reviewer Mapping
- TEMPLATE- Evidence Of Review By Department - Submit report request
- TEMPLATE- Evidence Of Review By Department - View report data
- Saving, editing, and refreshing the Power BI reports
- Managing Audit Settings
- Working with Audit viewer
Enhanced reporting
Alta Surveillance has introduced reporting endpoint APIs to improve reporting and analytics capabilities. Currently there are two types of reporting endpoint APIs.
: This API executes requests in a blocking manner, where each request is processed sequentially. Upon execution the request, the server waits to complete the first task before proceeding with another tasks. The client remains idle during this time.
: This API executes a request and continue to perform other tasks without waiting for the immediate response from servers. The server processes the requests independently. Client receives a response from asynchronous API with details to track the request. When the data is ready, the client calls the API to retrieve data. Alta Surveillance reporting asynchronous API returns report status and report data location in response. The client uses this location URL to track the status of report generation and get the data when the report is ready.
Synchronous APIs do not possess suffix after the API name. However, asynchronous APIs are indicated with the "Async" as a suffix. For example, EvidenceOfReviewByDept is synchronous API name and EvidenceOfReviewByDeptAsync is the asynchronous API name.
Refer to the details below for the available synchronous and asynchronous APIs.
Departments API
: Supported (https://<Reporting endpoint Base URL>/odata/departments)
: Not supported
Users API
: Supported (https://<Reporting endpoint Base URL>/odata/users)
: Not supported
UserRoles API
: Supported (https://<Reporting endpoint Base URL>/odata/userroles)
: Not supported
Roles API
: Supported (https://<Reporting endpoint Base URL>/odata/roles)
: Not supported
ItemMetrics API
: Supported (https://<Reporting endpoint Base URL>/odata/itemmetrics)
: Not supported
ReviewerMapping API
: Supported (https://<Reporting endpoint Base URL>/odata/reviewermapping)
: Not supported
MonitoredEmployees API
: Supported (https://<Reporting endpoint Base URL>/odata/monitoredemployees)
: Not supported
EvidenceOfReviewByDept API
: Supported (https://<Reporting endpoint Base URL>/odata/EvidenceOfReviewByDept)
: Supported (https://<Reporting endpoint Base URL>/odata/EvidenceOfReviewByDeptAsync)
ReviewStatus API
: Supported (https://<Reporting endpoint Base URL>/odata/reviewstatus)
: Not supported
To utilize these reporting endpoints, the administrator must configure them in Alta Surveillance. Upon successful configuration, Alta Surveillance generates a base URL and API keys to ensure secure access to the reporting endpoints.
To securely access data, the primary or secondary API keys serve as passwords, unique to each reporting endpoint configuration. The specified IP addresses during the configuration of these enhanced reporting endpoints are authorized and permitted for API calls.
See ReviewerMapping API.
See Evidence Of Review By Dept Async API.
See Report Status API.