Form Generator

Guidewire Product Model generation

Generate the form. And everything it depends on.

Turn project-specific workbook data into connected PolicyCenter forms and supporting Product Model changes, ready for your review.

See the connected change How the source is mapped

Connected generated output

Forms are only the visible layer.

A form change rarely ends at the form. Its rules, fields, and supporting files need to agree. Form Generator creates the connected artifacts from the operations you map.

An exploded view of a generated form and its connected Product Model dependencies.
PolicyCenter Form Pattern CG 20 04 · 06/26
Metadata Form Type Clause / Inference Fill-ins + Schedules Availability Gosu Options + Packages XML Typelists + Typekeys Display Keys Entities + Lookup Data
01 · The form

The form, defined.

Generate the pattern, edition, applicability, and metadata from your mapped source data.

02 · Its behavior

The behavior, connected.

Connect clauses, inference, fill-ins, schedules, and the Gosu logic required by the mapped operations.

03 · Its supporting model

The supporting files, together.

Generate the XML, display keys, typelists, entity fields, and lookup data those operations need. Review the complete change, not disconnected edits.

Flexible source mapping

Your workbook. Your project's rules.

Projects use different sheets, headers, and conventions. A developer adapts a project-specific Gosu Script to map those rows into supported generation operations. The reusable generator handles the connected output.

A project-specific workbook row enters an executable Gosu Script that absorbs source-specific vocabulary, emits stable typed FormGen operations, and assembles connected PolicyCenter artifacts.
Script

Executable Gosu adapter

FormRow→typed operation

Review and verification

Generated together. Reviewed by you.

For the classic Product Model, generation is part of a developer-controlled workflow. Validate the inputs, inspect the complete diff, and compile before accepting the change.

  1. 01Check the inputsValidate the mapped operations before writing files.
  2. 02Save the connected changeWrite the classic model in one coordinated save, with rollback support if writing fails.
  3. 03Review and compileInspect all changed files and run the project's compile checks.
  4. 04Check the rerunRepeat generation with unchanged inputs and confirm that no additional files change.

Classic and APD

Local changes. Or a reviewed APD candidate.

Classic Product Model

Generate in your working copy.

Write the connected Product Model files locally, then review and compile the changes before check-in.

APD-managed Product · In development

Prepare for manual import.

For supported operations, prepare an offline APD candidate and optional local overlay preview. Import, cloud synchronization, and product-code generation remain manual. Unsupported operations are blocked.

Form Generator

From source rows to one reviewable Guidewire change.

Bring your project's conventions. Generate the connected model. Keep the final review in your hands.

Discuss your project See all projects