Forms inference classes

You configure basic forms settings in Product Designer by creating and editing a FormPattern in the Forms tab in a policy line window. As part of that editor, you provide the fully-qualified class name of a Gosu class that extends the abstract class FormData. Your class must generate data that describes the variable data of the form. This data must not include boilerplate text. Such classes are known as forms inference classes.

You can subclass FormData directly for each form, or create your own subclasses of FormData that provide common behaviors or data. For example, PolicyCenter includes a class called PAFormData that defines some common behaviors for the built-in personal auto forms. Individual forms extend PAFormData instead of FormData.

After a job finishes, PolicyCenter triggers forms inference and then raises a messaging event. You can catch the messaging event in your Event Fired Rules to generate messages to the external forms printing system. For example, the submission job process contains code like that shown below.

FormInferenceEngine.Instance.inferPreBindForms(_branch)
_branch.addEvent("IssueSubmission")