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
UserRoles - List by filters
POST https://<Reporting endpoint Base URL>/odata/userroles
Specify the following filters to obtain refined and selective results from this report.
Note:
Either Departments or Users is a mandatory parameter. The Scope is an optional parameter.
Name | Type | Description |
|---|---|---|
Departments | Mandatory (if the Users parameter is not provided) Optional (if the Users parameter is provided) | Specifies IDs of the departments to which users and their roles belongs to. : The Users roles API can pass a maximum of 100 Departments IDs as input. : JSON array of integers 'id'(identifier fields) that is Departments. |
Scopes | Optional | Specifies the scope of the users roles. Possible values are: 160 for application-level roles and 161 for department-level roles. : JSON array of integers 'id'(identifier fields) that is Scopes. |
Users | Mandatory (if the Departments parameter is not provided) Optional (if the Departments parameter is provided) | Specifies IDs of the users. The Users roles API can pass a maximum of 100 User IDs as input. : JSON array of integers 'id'(identifier fields) that is Users. |
To get the item counts only for Users when the Users are mentioned, but the Departments and the Scopes are not mentioned.
POST https://<Reporting endpoint Base URL>/odata/Userroles
{
"Departments": [],
"Scopes" :[]
"Users" :[3821]
}
To get the item counts only for users when Departments are mentioned, but the Scopes and Users are mentioned.
POST https://<Reporting endpoint Base URL>/odata/Userroles
{
"Departments": [23],
"Scopes" :[]
"Users" :[]
}
To get the item counts only for users when Departments and Scopes are mentioned, but Users are not mentioned.
POST https://<Reporting endpoint Base URL>/odata/Userroles
{
"Departments": [23],
"Scopes" :[161]
"Users" :[]
}
To get the item counts only for users when Departments are not mentioned, but the Scopes and Users are mentioned.
POST https://<Reporting endpoint Base URL>/odata/Userroles
{
"Departments": []
"Scopes" :[160]
"Users" :[3821]
}
To get the item counts only for users when the Departments, Scopes, and Users are mentioned.
POST https://<Reporting endpoint Base URL>/odata/Userroles
{
"Departments": [23],
"Scopes" :[160,161]
"Users" :[55,67]
}
(For scenario 1 to 5) Status code: 200 OK
Invalid Inputs. Either the Department or the User parameter must be specified as input.
POST https://<Reporting endpoint Base URL>/odata/Userroles
{
"Departments": [],
"Scopes" :[160]
"Users" :[]
}
Status code: 400 Bad Request Error Code: InvalidOdataQuery
See Supported OData query options.
See Responses.