Enterprise Vault™ Compliance Accelerator Administrator's Guide
- Overview and latest updates
- Understanding Veritas Surveillance
- Configuring Compliance Accelerator Desktop Client
- Customizing the reviewing action statuses
- Importing configuration data from an XML file
- Specifying the Windows domains with which to synchronize employee details
- Mapping employee properties to Active Directory or Domino directory attributes
- Grouping departments into partitions
- Setting up department attributes
- Setting up custom message types
- Setting Compliance Accelerator system configuration options
- Ad Hoc Searches configuration options
- Diagnostics configuration options
- Document Conversion configuration options
- Export/production configuration options
- General configuration options
- Home Page configuration options
- Hotword Analysis configuration options
- Item Prefetch Cache configuration options
- Item Prefetch Cache (Advanced) configuration options
- Policy Integration configuration options
- Profile Synchronization configuration options
- Random Capture configuration options
- Reviewing configuration options
- Search configuration options
- Security configuration options
- System configuration options
- Vault Directory Synchronization configuration options
- Creating and viewing reports
- About the Compliance Accelerator reports
- Accessing data through the Microsoft SQL Server Reporting Services (SSRS)
- Enhanced reporting
- Accessing reports through the OData web service
- Configuring a Power BI template for reporting
- Appendix A. Troubleshooting
- Veritas Surveillance user interface user interface is not displayed properly in non-English environment
- Issues with the random sampling of items
- Display issues when you open a Compliance Accelerator website in Internet Explorer 10 or later
- Vault stores not displayed in the Veritas Surveillance web client
- TNEF-encoded attachments to Internet Mail (.eml) messages may not be readable after you export the messages from a review set
- Synchronization errors after you rename the SQL Server computer
- Performance counter errors when the Accelerator Manager service starts
- SQL Service Broker warning when restoring a customer database to a different server
- Error messages when the Intelligent Review (IR) API authentication and authorization fails
- Known issues after enabling FIPS
EvidenceOfReviewByDept - List by filter
POST https://<Reporting endpoint base URL>/odata/EvidenceOfReviewByDept
POST https://<Reporting endpoint base URL>/odata/EvidenceOfReviewByDept
The following filters can be used with the EvidenceOfReviewByDept API when invoked using the POST method. The system uses the operator between the filters to return the result based on the specified filters.
Name | Type | Description |
|---|---|---|
StartDate | Mandatory | StartDate is the date on which items are captured or ingested in Compliance Accelerator is recorded as the CaptureDate for that item. This filter specifies the start date for returning count of items whose CaptureDate is greater than or equal to this start date. : YYYY-MM-DD : JSON array of integers 'id'(identifier fields) that is StartDate. |
EndDate | Mandatory | This filter specifies the end date for returning count of items whose CaptureDate is greater than or equal to this date. : YYYY-MM-DD : JSON array of integers 'id'(identifier fields) that is EndDate. |
MessageType | Mandatory | Specifies the type of captured items and returns item counts for items that have the specified message type. : Integer 'id' (identifier fields) that is MessageType ID. |
Departments | Mandatory | Specifies the departments to which the captured item belongs and returns item counts for items within that department. : JSON string containing integer IDs (identifier field) that is department IDs. : As an input, this API can pass maximum of 1000 Departments IDs. |
MessageDirection | Mandatory | Specifies whether the item was sent/received from within the organization or from an external source and returns item counts for items that have the specified message direction. : Integer id (identifier field) that is MessageDirection ID |
To get the item counts for Department IDs 5 and 6, between StartDate 2023-01-01 and EndDate 2024-01-01 and having MessageType as 7, and MessageDirection as 1.
Status code: 200 OK
See Supported OData query options.
See Supported reporting endpoint API filters and their values.
See Responses.