Forms messaging

The role of your messaging code for forms integration is to examine the list of newly added forms in the PolicyPeriod.NewlyAddedForms property and generate messages for the newly added forms.

Your messaging destination that represents your forms printing system must listen for the issuance events such as IssueSubmission, IssuePolicyChange, IssueReinstatement, and others for other jobs.

Your Event Fired rules must capture these events and generate one message for each form, or one message that contains the data for all the newly added forms.

Within each form there is a property that contains the cached XML data created by the inference class. You can get the cached XML data using code like that shown below.

cachedXML = myForm.FormTextData.TextData

You might make your message payload simply the XML payload generated from that XMLNode such as the following code.

var msg = MessageContext.createMessage(cachedXML)

If you support form multiplicity, remember that you might need to access the Form.FormAssociations property to access the form associations to access the linked entity to generate the payload.

Messaging plugins

Design your messaging transport plugin to send this message to the external forms printing system. Depending on the external system, you could send the XML directly to the system (or to integration code that manages the system).

Alternatively, if your message contained XML, you could traverse the XML data and format the data as appropriate for your printing system. If you use this approach, use XML APIs to convert the XML String data to XMLnode objects.

Creating documents

If your forms printing system can integrate with a document management system (DMS), the printing system can generate a visual representation of the form and add it to the DMS. After it does this, the integration code can call back into PolicyCenter to let it know there is a new document associated with the policy.