Policy Change tab for form patterns

The Policy Change tab contains settings for the form in policy change transactions. PolicyCenter displays this tab if you added Policy Change to the Transaction Types tab.

The Policy Change tab has the following fields:

Field

Description

Is this form only used to indicate removal or replacement of another form?

Values are Yes and No. This input is always visible. This field indicates whether the form is a removal endorsement. The RemovalEndorsement field on the FormPattern entity stores the value of this field.

Can this form get added again on a policy change if its data changes (i.e. replaced)?

Values are Yes and No. This field is visible if the value of the first field is No. This field the indicates whether to reissue the form when its inference data changes. The ReissueOnChange field on the FormPattern entity stores the value of this field.

If this form’s data changes, also add the following invalidation/replacement form:

Value is a drop-down list of form patterns to add or remove because the data has changed. PolicyCenter populates the drop-down list with all removal endorsements valid for the same policy line. This field is visible if the value of the second field is Yes.

Reissuing forms during policy changes

Set the answer to Can this form get added again on a policy change if its data changes...? to Yes to reissue forms on a policy.

The form can be initially added to a policy during a submission, issuance, rewrite, renewal, or policy change transaction. If there is a change to the underlying data, the form can be reissued in a policy change transaction.

During a policy change, PolicyCenter must determine whether a version of the reissued form is already present. If it is, it must determine whether the data on the old version of the form is the same as the new version of the form. PolicyCenter compares the data between the old and new versions of the form. PolicyCenter compares:

New version of form

Old version of form

The XML created by the addDataForComparisonOrExport method of the corresponding forms inference class from the new version of the form

To the equivalent XML persisted with the old version of the form.

There are multiple possible outcomes:

If a previous version of the form exists...

  • ... And the form pattern is no longer inferred by the current data, PolicyCenter does the following:
    • Sets the removal date on the previous version so that PolicyCenter ignores it during subsequent forms processing.
    • If the pattern specifies adding another form when the current form is inaccurate because the data has changed, PolicyCenter infers a copy of that other form pattern.

    PolicyCenter also performs these actions if there is no new version of the form at all.

  • ... And PolicyCenter infers the form pattern by the current data and the form contains exactly the same data as the previous version, PolicyCenter does nothing with the form.
  • ... And PolicyCenter infers the form pattern by the current data and it does not contain exactly the same data as the previous version, PolicyCenter does the following:
    • Sets the removal date on the previous version.
    • It adds the new version.
    • It marks the new version as superseding the old version.
    • If the pattern specifies adding another form when the current form is inaccurate because the data has changed, then PolicyCenter infers a copy of that other form pattern.

If no previous version of the form exists...

  • ... And PolicyCenter infers the form pattern by the current data, PolicyCenter adds the new version of the form.
  • ... And PolicyCenter does not infer the form pattern by the current data, PolicyCenter does nothing with the form.

Do not reissue

Set the answer to Can this form get added again on a policy change if its data changes...? to No to specify a one-time form on a policy.

These are forms that PolicyCenter adds to the policy at most a single time during a policy term and that never require updating or removal. A one-time form is generally suitable for use with a form that does not have any policy-specific data (for example, for something like a jurisdiction notice). PolicyCenter adds a one-time form if the InferredByCurrentData() property on FormData returns true and if there is no previous version of the form with the current policy term.

Removal endorsement

Removal endorsements are forms that nullify a previously issued form. Set the answer to Is this form only used to indicate removal or replacement of another form? to Yes to specify a removal endorsement form on a policy.

Removal endorsements have the unique property of always being processed last. Therefore, these endorsements can refer back to any forms that PolicyCenter removed earlier in the inference process. You use removal endorsements to indicate that a particular contract form is no longer valid.

You specify a removal endorsement by specifying to Yes to the question Is this form only used to indicate removal or replacement of another form?. In addition, a removal endorsement is typically configured by choosing one of the following answers to the Form inference conditions field on the Inference tab:

  • An associated form is invalidated
  • An associated form is invalidated or replaced