Contingency object model

The following illustration shows Contingency and related objects.

Contingency

Each Contingency has a number of properties, including:

Property	Description
`Title`	Brief description enabling a user to quickly understand the type of contingency.
`Description`	Longer description which can include specific details of this instance. Can include, for example, the conditions under which the contingency can be resolved.
`Status`	Type key indicating if this contingency is still active, has been successfully resolved, or failed to be resolved in a timely manner. After contingencies have been processed by the Handle Unresolved Contingency work queue, their status is `ACTION_INITIATED`. Values of `FAILED` or `ACTION_INITIATED` appear on the Contingency screen under Closed Without Satisfactory Resolution.
`Action`	What action to start if the contingency is not resolved prior to the action start date. The action can start a policy transaction.
`ActionStartDate`	When to initiate action if the contingency is not resolved.
`DueDate`	The due date for the contingency. If the contingency is not closed by this date, batch processing changes the status to failed, and closes the contingency.
`CloseDate`	When the contingency was closed.
`CloseUser`	The user who closed the contingency.
`Policy`	The policy associated with the contingency.
`PolicyPeriod`	Generally the policy period that caused the contingency to be associated with the policy. If the contingency was attached directly to the policy, policy period is null.

Contingency Job

If a contingency is not resolved in a timely manner, Unresolved Contingency batch processing initiates action on the contingency. ContingencyJob is the job initiated by the action.