![]() |
Compliance Accelerator groups the search criteria options into multiple sections, which are described below. Click the arrow icons at the right to expand or collapse the sections.
The Search section identifies the search and specifies when it runs.
The Sampling section lets you sample the search results and add a random selection of items to the review set.
The Date range section lets you search for items according to when they were sent or received.
The Authors and Recipients section targets the departments for the search and the direction of the items to search. Any departments that you have organized into partitions can only search items to and from departments in the same partition.
The Search terms section specifies the words or phrases for which Compliance Accelerator should search in the subject lines of items and their bodies. By default, when you search for words in both the subject of an item and its content, Compliance Accelerator finds those items that meet one or both criteria. However, it is possible to set up Compliance Accelerator so that only those items that meet both criteria are found.
The words or phrases that you specify here are highlighted in the Review pane when you review the items that this search has found.
The Attachments section lets you search for items with a certain number or type of attachments.
The Miscellaneous section lets you search for items of a certain size and type or that have the specified retention category.
The Policies section lets you search for items according to the policies with which the Enterprise Vault Automatic Classification Engine has tagged them.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.