Submission process Gosu class

Gosu classes contain the code which primarily controls the submission process. In Studio, open SubmissionProcess.gs class in the gw.job package. This is the primary class for submissions. The job classes are part of the default application.

This class contains the main actions involved in a submission. This class ultimately extends the JobProcess class. The JobProcess class contains methods that enable you to get the job, the policy period, and a quote if it exists. It cancels any open activities on the submission, auto assigns the user role, and checks to see if the job can be expired, withdrawn, or approved by an underwriter. It also checks to see if the job can be started as new.

This class starts a new submission and assigns a requestor and producer. The beginEditing method moves a new submission to Draft status. Segmentation classes determines the available underwriting companies for a policy.

Next, the submission process determines whether quoting can be initiated. The process determines if the branch can be quoted in its current state by calling the canRequestQuote method. It also determines whether the submission needs to be reviewed by an underwriter. If the submission began as a quick quote, it also converts it to a full application. That in turn allows a job to be bound bindOnly and issue.

After PolicyCenter starts the bind process for the submission (branch), the submission may be rejected, marked for review by an underwriter, or returned to Draft for additional editing. Otherwise, binding begins, which puts the submission in the Binding status, updates the policy number, and sends an event for additional processing.

To complete binding, PolicyCenter calls the finishBinding method. This method completes the binding of a policy period without issuing it. The policy period is marked as bound and the job is finished. However, if issuance is being held, then PolicyCenter promotes the branch to the main policy period. Branches with no hold status must go through the finishIssuing method. This method promotes the policy period by marking it Bound and the completes job.

After issuing a submission, the user can bill the submission. The billing system plugin interface IBillingSystemPlugin defines the contract between PolicyCenter and the billing system. For example, the billing plugin implementation sends messages to the billing system about new billing instructions associated with a new submission.

Note: The submission job no workflows because it has no background processes. PolicyCenter uses workflows only for background processes.

Modifying the Submission Process

If you need to change or add methods to the submission process, you can edit the job class directly or create a subclass (such as YourCompanySubmissionProcess.gs).

For more information about job classes and job subclasses, see Gosu classes for jobs.

If you create a subclass, you must modify the job process customization plugin. For more information, see Job process creation plugin.