Configuring submissions

This topic describes how to configure submission jobs (submission policy transactions).

Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration documentation refers to policy transactions as jobs.

Use Studio to view and edit the Gosu classes and other files related to the renewal process.

Key files include:

  • Gosu classes such as: SubmissionProcess.gs. This class defines and begins the new submission process.
  • Gosu enhancement files such as: SubmissionEnhancement.gsx. This enhancement allows you to augment classes and other types with additional methods and properties. An example is the addToGroup method which groups it into the appropriate Submission group or creates a new one if a valid group does not exist.
  • Page configuration files (PCF files) such as SubmissionWizard.pcf or SubmissionWizard_PaymentScreen.pcf.
  • Typelists such as JobGroup, or QuoteType.
Note: Since the submission process for any insurer can be configured based on business requirements, all discussions apply to the default application only.

See also