How to override default content category settings

A rule can assign a content category and override some of the default content category settings. For example, if you have a content category that defines all the custom properties to index, a retention category and a destination archive, different rules can assign the content category but override values for the archive or retention category, as required.

For example, if a content category called Litigation is defined in Custom Properties.xml as follows:

<CONTENTCATEGORY NAME="Litigation" RETENTIONCATEGORY="Litigation"
  ARCHIVEID="15165263832890493848568161647.server1.local">
	<INDEXEDPROPERTIES RETRIEVE="Y">
	<PROPERTY TAG="AUTHOR01"/>
	<PROPERTY TAG="CASESTATUS"/>
	</INDEXEDPROPERTIES>
</CONTENTCATEGORY>

It can be referenced in a ruleset file as follows:

<RULE NAME="Example rule1" ACTION="ARCHIVE_ITEM"
  CONTENTCATEGORY="Litigation">
	<message attribute filters>
</RULE>
<RULE NAME="Example rule2" ACTION="ARCHIVE_ITEM"
  CONTENTCATEGORY="Litigation"
  ARCHIVEID="1516526383289049384890493848.server2.local">
	<message attribute filters>
</RULE>

Additional properties defined in the content category will be indexed with both rules. The second rule uses the same content category, but items that match this rule will be stored in a different archive.

Note:

Before you alter an existing configuration, make sure that you understand what default behavior has been configured for each type of archiving. Check the DEFAULT content category attribute in Custom Properties.xml and the IGNORENODEFAULT registry setting.