Configuring policy change

This topic describes how to configure policy change jobs (policy change 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.

Gosu classes primarily control policy changes. In Studio, navigate to configuration > gsrc to view or edit the gw.job.PolicyChangeProcess.gs Gosu class that contains most of the policy change code.

In a policy change job, the JobProcess.gs class, the QuoteProcess.gs class, and the PolicyChangeProcess.gs class contain code for the main job actions. The default application spreads the policy change code among multiple classes for better organization and use of code. For example, changing the quote logic can be done in one location (QuoteProcess.gs). You can modify the quote logic in one location and many types of jobs can access it.

Note: In the default configuration, the policy change job has no workflows because it has no background processes. PolicyCenter uses workflows only for background processes.