Veritas Advanced eDiscovery User Guide
- About Veritas Advanced eDiscovery
- Getting started with Advanced eDiscovery
- Advanced eDiscovery roles
- Case management
- Reviewing and working with emails in eDiscovery
- Email export
- Collaborative reports
- Advanced eDiscovery alerts
- Email Continuity
- Methods for searching cases and accounts
- Boolean operator searches
- Methods for searching tables and reports
- Advanced eDiscovery Frequently Asked Questions
- Best practices, limitations, and known issues
- Advanced eDiscovery updates in previous releases
Best practices and limitations with Advanced eDiscovery
Although the users that are provisioned for archive access can view their messages from Advanced eDiscovery, we recommend that users work with their messages using Personal.cloud. Additional functionality such as search filters and active folders is provided when users work with archived messages in Personal.cloud.
Search times improve after a user performs their first search during each session because Advanced eDiscovery keeps the index in memory during each session.
Inaccurate search results may be returned if the hyphen in a domain name is included because the hyphen is dropped.
Use Advanced Search to cut down search results If you see a message stating that you have exceeded the number of search results that can be returned.
Search terms are limited to 1,000 characters.
Use Query Search to accurately find and to reduce search results.
Searching with empty quotes or whitespace within quotes produces unexpected results.
Searching with an empty field produces an error.
Tags are only searchable on the Tags & Holds page, which is located within the Investigations tab.
The search interface prevents the user from entering the following special characters: / \ # < >
The maximum number of Boolean operands in a search is 249. Note that roof rusted OR paint has two Boolean operands: the OR, and the space between the first two terms. The space is treated as an AND operator.
Unable to search for DBCS/hiascii char in the Quick Search field in Alerts.
Unable to search for DBCS/hiascii char in Policy Names - Alerts.
Unable to search for DBCs/hiascii char in Advanced/Query search - comments
Unable to search for DBCs/hiascii char in Advanced/Query search - Alert Emails
Search fails in Managed Account if last name includes non-ASCII characters
Search fails in Reviewers Account if last name includes non-ASCII characters
Corrupted DBCS/hiascii character results in Case Review Status Tag name and description
Case Status has the hard-code issue risk