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
Supported OData query options
The currently supported OData query options that can be used for query composition to customize responses are mentioned below.
: Use the $select query parameter to return a set of properties that are different than the default set for an individual resource or a collection of resources. With $select, you can specify a subset of the default properties.
Example: In the example below, the query returns only two properties, Department name and Department status in the result.
https://<Reporting endpoint base URL>/odata/departments?$select=DepartmentName,Status
Use the $count query parameter to retrieve the total count of matching resources.
In the example below, the query returns a total count of roles in the system irrespective of any other filters.
https://<Reporting endpoint Base URL>/odata/roles?$count=true
Use the $top query parameter to limits the number of records returned.
In the example below, the query returns the top 10 records in the result.
https://<Reporting endpoint Base URL>/odata/departments?$top=10
Use the $skip query parameter to skips a specified number of records before returning results.
In the example below, the query returns the records skipping the first 60 records in the result.
https://<Reporting endpoint Base URL>/odata/departments?$skip=60
Use the $skipToken query parameter to retrieve the next page of results from result sets that span multiple pages.
Some requests return multiple pages of data due to server-side paging to limit the page size of the response. Reporting APIs use the $skipToken query parameter to reference subsequent pages of the result. The $skipToken parameter contains an opaque token that references the next page of results and is returned in the URL provided in the @odata.nextLink property in the response.
For example, if you call the Roles API that have more than 1000 records in the result, then the response will return only 1000 records with @odata.nextLink property as shown below.
"@odata.nextLink": "https://<Reporting endpoint Base URL>/odata/roles?$skipToken=29310"
To fetch the next page of records, the value of the @odata.nextLink can be used as the endpoint URL which has a skipToken value.