|
Always show policy display in review grid
|
When you preview an item that has no associated policies in the
Review pane, specifies whether to show the Policy field above the
item. By default, Compliance Accelerator hides this field when
there are no associated policies.
|
|
Category policies message header
|
Specifies the prefix to use for X-header lines that contain a
semicolon-delimited list of category policies. The default prefix
is x-EV-evtag-category.
Applying category policies to items does not affect their
capture in any way; it provides a means to categorize the items.
For example, you might use category policies to flag the items that
are in Spanish or marked as Personal.
|
|
Deduce overall policy action from policy types
|
Determines how Compliance Accelerator proceeds when it
encounters an item for which the policy management software has not
specified an overall action in either an index property or item
X-header. The overall action can be one of the following:
-
Inclusion (demands or suggests capture). The Journaling
Connector always samples the item, but you can choose to include or
exclude the item when you conduct a search.
-
Exclusion (precludes capture or advocates non-capture). The
Journaling Connector never samples the item, and you can choose to
exclude it from searches.
-
No action. The item is subject to normal Compliance Accelerator
random sampling by the Journaling Connector.
By default, when it encounters an item for which no overall
policy action has been specified, Compliance Accelerator does the
following:
-
Includes the item if it has any associated inclusion
policies.
-
Excludes the item if it has one or more associated exclusion
policies but no inclusion policies.
-
Takes no action if the item has no associated inclusion or
exclusion policies (but it may have some associated category
policies).
If you disable this behavior, Compliance Accelerator assumes
that it should take no action on items for which no overall policy
action has been set.
|
|
Exclusion policies message header
|
Specifies the prefix to use for X-header lines that contain a
semicolon-delimited list of exclusion policies. The default prefix
is x-EV-evtag-exclusion.
An exclusion policy either precludes capture or advocates the
non-capture of items. For example, spam items or newsletters may
fall into this category.
|
|
Include policies take precedence over exclude policies
|
Specifies whether to give higher priority to inclusion policies
than to exclusion policies. By default, the Journaling Connector
always samples an item that has at least one associated inclusion
policy. This is the case even if the item also has one or more
exclusion policies.
|
|
Inclusion policies message header
|
Specifies the prefix to use for X-header lines that contain a
semicolon-delimited list of inclusion policies. The default prefix
is x-EV-evtag-inclusion.
An inclusion policy addresses the most serious issues, such as
swearing, racism, and insider trading. You would normally want to
ensure that items to which such policies were applied are always
captured for review.
|
|
Policy action message header
|
Specifies the prefix to use for X-header lines that contain the
prescribed overall policy action for an item (one of INCLUDE,
EXCLUDE, or NOACTION). The default prefix is x-EV-Vault-PolicyAction.
|
|
Sort Policies within type
|
When you preview an item in the Review pane, specifies the order
in which to list the associated policies in the banner above the
item. Enter one of the following values:
-
0. The policies are not sorted.
-
1 (default). Compliance Accelerator first groups the policies by
policy type (inclusion, exclusion, and category) and then sorts
them alphabetically within each type.
-
2. The policies are sorted alphabetically, regardless of policy
type.
Changing the sort order does not affect the items that are
already in the Accelerator database; only newly-added items are
affected.
|
|
XML policy message header
|
Specifies the prefix to use for X-header lines that define a
policy action through a string of XML code . Each XML definition
must be on a single X-header line, like the following:
<POLICIES
ACTION="INCLUDE"><INCLUSION><POLICY>Profanity</POLICY></INCLUSION></POLICIES>
The default prefix is x-EV-evtag-xmlpolicies.
|
