Forms inference and integration

For an insured customer, the physical representation of an insurance policy is a collection of forms. Different forms define different aspects of a policy, such as coverages, exclusions, government regulations, and similar items. PolicyCenter supports forms in the user interface. This topic describes how to integrate an external forms printing service with PolicyCenter.

Although forms has a user interface for previewing what forms to create, the forms feature exists primarily to send data to an external forms printing system during issuance. Forms can also print for other jobs such as a policy change job that triggers reprinting a changed form, or printing additional forms that are now necessary.

You must perform the following tasks to integrate an external forms printing service with PolicyCenter forms.

Create forms inference classes to generate XML – You must define Gosu classes that extend the FormData abstract class. The FormData class generates XML that describes data on the form that changes with each issuance of the form. The generated XML does not include introductory or boilerplate text that does not change.
Write Event Fired rules that generate messages to a forms printing service – Event Fired rules intercept forms issuance events and generate messages to the external forms printing service. The message payload might be simply the XML generated by the forms inference classes.
Write forms messaging code to talk to the external system – Your custom messaging plugins (and new messaging destinations) that you register must send the XML payload to the forms printing system.