Objects that get purged or pruned

The following illustration shows some of the objects that get purged or pruned.

Purging and pruning remove the policy period and all effective dated objects in the policy period branch.

Objects where the branch is equal to the policy period are also removed. These objects, which include notes, documents, and activities, directly relate to the policy period and would otherwise point to a removed object. Purging and pruning does not remove objects not directly related to the policy period.

Purging and pruning also remove forms.

Form text data is not removed because form text data can be shared between policy periods. As a result, form text data can be orphaned as a result of quote purging. The Form Text Data Delete batch process removes orphaned form text data. For more information, see Scheduling work queue writers and batch processes.

In addition to removing policy periods, purging also removes the job. If purging removes all jobs associated with a policy, it also removes the Policy object. For example, purging removes a Policy if it only exists because of an unbound submission. Pruning only removes policy periods; pruning does not remove the job.

If you added custom objects that attach to policy period, these objects will be removed if they meet the criteria mentioned above. Through configuration, you can remove objects that do not meet this criteria. The way that forms are removed may provide some help in your implementation.

Underwriting issues

The following illustration shows objects related to underwriting issues that get purged or pruned.

Purging and pruning also remove objects related to underwriting issues on the policy period. Human-touched underwriting issues are not purged or pruned. A human-touched UWIssue has the HumanTouched property set to true.