Mapping Policy Coverage Fields in PDF and Web Forms

Learn how to map policy coverage values such as limits, deductibles, selections, and Boolean coverages into PDF and Web Form templates.

Gravatar
Jorge Vera
  • 2 days ago
  • Published
What this article covers: How to map policy coverage values to PDF and Web Form fields so limits, deductibles, selections, and other coverage values are filled automatically for a policy.

What Are Policy Coverage Mappings?

Policy coverage mappings connect a form field to a coverage value saved on a specific policy. For example, a PDF or Web Form can display a policy's General Liability limit, Commercial Property building limit, or Personal Auto deductible without requiring the user to type the value again.

Coverage mappings use the same Field Mappings Selection panel used for other policy fields. In the panel, choose Policy, then choose the coverage area and field you need.

Where Coverage Fields Appear

Coverage fields are grouped under the policy mapping area and organized by Line of Business. The available fields come from the coverage catalog configured in Taino, so the list can grow as new coverage definitions are added.

The mapping panel is the current source of truth for the available fields. If a field is not shown, verify that the policy has the expected Line of Business and coverage definition configured.

Examples of Coverage Mapping Codes

Coverage mappings use stable codes that identify the Line of Business and coverage field. Examples include:

Coverage fieldExample mapping code
Each Occurrence Limit15:GL_EACH_OCCURRENCE_LIMIT
General Aggregate Limit15:GL_GENERAL_AGGREGATE_LIMIT
Building Limit50:CP_BUILDING_LIMIT
Bodily Injury Limit6:PA_BODILY_INJURY_LIMIT

The exact code is selected by the platform. Do not manually invent or edit a coverage code in a template.

PDF and Web Form Behavior

  • Text fields: receive the formatted coverage value, such as a limit or deductible.
  • Selection fields: match the saved option value while displaying the localized option label.
  • Checkbox fields: are checked or unchecked from the saved Boolean coverage value.
  • Localized forms: display labels and selection text using the current language when localized values are available.

PDF and Web Form templates use the same coverage mapping concept. Web Forms can also use the mapped value when submitting data back to update a record, subject to the form's configuration and permissions.

Troubleshooting

  • The field is not listed: confirm the policy's Line of Business and coverage configuration.
  • A dropdown remains blank: confirm that the saved option is available for that coverage definition. Stored values are matched independently from their display labels.
  • A checkbox is not checked: confirm that the policy value is Boolean and that the target form field is a checkbox control.
  • The value is empty: confirm that the policy has a value saved for that coverage field.
Important: Product coverage defaults are copied to a policy when the product is selected. A mapping reads the coverage value saved on the policy at generation time; changing a product later does not rewrite historical policy values.
Was this article helpful?

0 out of 0 found this helpful