Policy change integration

For the policy change job, the PolicyChangeAPI includes two methods to start policy change jobs:

• The startAutomaticPolicyChange method starts a policy change job for a policy (specified by policy number) and an effective date. It returns the job number of the new job (its JobNumber property). In the default configuration, this method does not make any changes to the policy data. You can add your own methods to make changes to the data.
• The startManualPolicyChange method has the same arguments and return values, but does not attempt to bind and quote automatically. The policy change starts and waits in draft mode for the user to quote and finish it manually.

The policy change job has the following plugins.

IPolicyPlugin

The canStartPolicyChange method returns an error message if a change cannot be started for a policy and an effective date. Changes that are started internally or externally call this plugin.

For more information, see Policy plugin.

IPolicyPeriodPlugin

The postCreateNewBranchForChangeEditEffectiveDate method is called to handle a change to the effective date of a job such as a policy change. In the default configuration, policy change is the only job that calls this method.

In PolicyCenter, events are changes (such as a new policy change) that might be of interest to an external system. In the bind method of the PolicyChangeProcess.gs class, you can generate the IssuePolicyChange event. In the default configuration, this code is commented out. The code notifies an external system to issue a policy change.

See also

• Messaging and events