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
ItemMetrics - List by filter
POST https://<Reporting endpoint Base URL>/odata/ItemMetrics
The following filters can be used with the ItemMetrics 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 |
|---|---|---|
Departments | Optional | Specifies the department to which the captured item belongs and returns item counts for items within that department. : JSON array of integers 'id'(identifier fields) that is department IDs. : As an input, the ItemMetrics API can pass maximum of 1000 Departments IDs. |
CaptureType | Optional | Specifies the mode/technique used to capture the item in Compliance Accelerator and returns item counts for items with the specified capture type. : JSON array of integers 'id'(identifier fields) that is CaptureType IDs. : As an input, the ItemMetrics API can pass maximum 10 CaptureType IDs. |
CaptureDateStart | Mandatory | Specifies the date on which items are captured or ingested in Compliance Accelerator is recorded as the CaptureDate for that item. Returns item counts whose CaptureDate is greater than or equal to the specified CaptureDateStart. : yyyy-mm-dd : JSON array of integers 'id'(identifier fields) that is CaptureDateStart. |
CaptureDateEnd | Mandatory | Specifies the date on which items are captured or ingested in Compliance Accelerator is recorded as the CaptureDate for that item. Returns item counts whose CaptureDate is less than or equal to the specified CaptureDateEnd. : yyyy-mm-dd : JSON array of integers 'id'(identifier fields) that is CaptureDateEnd. |
MessageDirections | Optional | 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. : JSON array of integers 'id'(identifier fields) that is MessageDirections IDs : As an input, the ItemMetrics API can pass maximum 5 MessageDirections IDs. |
MessageType | Optional | Specifies the type of captured items and returns item counts for items that have the specified message type. : JSON array of integers 'id'(identifier fields) that is MessageType IDs. : As an input, the ItemMetrics API can pass maximum 100 MessageType IDs on a single page. |
To get the item counts for Departments IDs 7622, between CaptureDates 2023-11-24 and 2023-12-24 and having CaptureType as 1 or 3.
POST https://<Reporting endpoint Base URL>/odata/ItemMetrics
{
{"CaptureDateStart": "2023-11-24",
"CaptureDateEnd": "2023-12-24",
"Departments": [7622],
"CaptureType": [1,3]
}
Status code: 200 OK
To get item counts for Department IDs 9 and 5, between CaptureDates 2023-06-01 and 2023-08-02 and having MessageType IDs as 7 or 8.
POST https://<Reporting endpoint Base URL>/odata/ItemMetrics
{
"CaptureDateStart": "2023-06-01",
"CaptureDateEnd": "2023-08-02",
"Departments": [9,5],
"MessageType": [7,8]
}
To get item counts for Departments IDs 9 and 5 , between CaptureDates 2023-06-01 and 2023-08-02 and having MessageDirections as 1 or 2.
POST https://<Reporting endpoint Base URL>/odata/ItemMetrics
{
"CaptureDateStart": "2023-06-01",
"CaptureDateEnd": "2023-08-02",
"Departments": [9,5],
"MessageDirections": [1,2]
}
To get item counts for Departments IDs 9 and 5 , between CaptureDates 2023-06-01 and 2023-08-02 and having MessageType IDs as 7 or 8.
POST https://<Reporting endpoint Base URL>/odata/ItemMetrics
{
"CaptureDateStart": "2023-06-01",
"CaptureDateEnd": "2023-06-02",
"Departments": [9,5],
"MessageType": [7,8]
}
See Supported OData query options.
See Supported reporting endpoint API filters and their values.
See Responses.