Enterprise Vault™ Discovery Accelerator Reviewer's Guide
- Introducing Discovery Accelerator
- Introducing Veritas Surveillance
- Searching for items
- Manually reviewing items
- About reviewing with Discovery Accelerator
- About the Review pane
- Filtering the items in the Review pane
- Searching within the review set
- Finding all items in the same conversation
- Assigning review marks and tags to items
- Adding comments to items
- Viewing the history of items
- Displaying printable versions of items
- Downloading the original versions of items
- Copying the item list to the Clipboard
- Deleting items from Enterprise Vault archives
- Changing how the Review pane looks
- Setting your Review pane preferences
- Working with research folders
- About research folders
- Creating research folders
- Editing the properties of research folders
- Copying items to research folders
- Reviewing the items in research folders
- Exporting items from research folders
- Giving other users access to your research folders
- Removing items from research folders
- Converting research folders into cases
- Deleting folders
- Exporting and producing items
- Creating and viewing reports
- About the Discovery Accelerator reports
- Enhanced reporting
- Creating Discovery Accelerator reports
- Available Discovery Accelerator reports
- Viewing existing reports
- Deleting reports
- Accessing reports through the OData web service
- Configuring a Power BI template for reporting
- Appendix A. Enterprise Vault properties for use in Discovery Accelerator searches
- About the Enterprise Vault search properties
- System properties
- Custom Enterprise Vault properties
- Custom Enterprise Vault properties for File System Archiving items
- Custom Enterprise Vault properties for SharePoint items
- Custom Enterprise Vault properties for Compliance Accelerator-processed items
- Custom properties for use by policy management software
- Custom properties for Enterprise Vault SMTP Archiving
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.