Note: To access Job Setup, you must have the authority, "Scheduler Setup," (Company Configuration group).
After you have given authority to users who will be running the programs automatically and have set up your system settings, the next thing you want to do is set up each job you will be running.
From the Company Configuration Tool Tree View, select Service Controller / Job Setup to display the Job Setup List View. Click the Add button to show a drop down menu, and choose the type of job you want to run automatically:
Add End of Period Job
Add Renewal Job
Add Non-Diamond Job
Add Error Log Job
Add Queued Policy Export Job
Add SQL Server Job
Add Other Job
Prior to Version 525, information specific to End of Period was stored separately with a job. Now, a job can be linked to one or more configurations as set up in the EOP Interface. This means a job would only link to an End of Day configuration if neither End of Month or End of Year should be handled by a job. When adding a new EOP job, the Add New Job screen displays a set of combo boxes for each Period Type (Day, Month and Year). Fields include:
Description: Free form; enter the name of the job that will be run.
Suppress Email Notification: If a check is placed in this field, no Email Notification will be sent when the process starts / finishes.
End of Day / End of Month / End of Year Configurations:
SQL Job to Run Before: From the combo box, select the job you wish to run prior to the selected configuration. When selected, the job will run before the EOP Running Flag is set to "True."
Configuration: The EOP configuration you want to run.
Details: Select to display the configuration as it exists in the Configure tab in the EOP UI. Processes that are selected in the configuration will run.
SQL Job to Run After: From the combo box, select the job you wish to run after to the selected configuration. When selected, it will run after the EOP Running Flag is set to "False."
Click Save. The job is added to the Data Grid.
Special Notes About End of Period Jobs!
The result of the associated job selected to run before the EOP type does not impact whether or not the EOP type is executed. The EOP type will run regardless of the result of the associated job.
The associated job (s) only execute if the EOP process type is allowed to execute.
When scheduling the EOP Processes automatically, here is how Diamond processes the scheduling. Every day EXCEPT the last day of every month (including the last day of the year) will process normally with one exception as follows:
Override the System Lock on the Last Day of the Month: Used with EOM and EOY configurations. When EOM or EOY run, the EOP Running Flag is set to "True" (lock the system) before beginning these configurations. The Lock System flag for each process is ignored; system remains locked. Once all processes finish, the EOP Running Flag is then set to "False" (unlock). When this field contains a check, each process is locked at the start and unlocked when it finishes (similar to what happens in EOD configurations). This can allow users to issue policies between running EOD / EOM and EOY! It is recommended this setting is not used in your EOM & EOY configurations.
The system will require that End of Day has finished before allowing End of Month to run. (Note: This same rule is in effect when running End of Day manually.)
The System Date will not roll after End of Day is finished even if the configured job is set to roll the System Date.
The System Date will then roll AFTER End of Month has finished depending on whether or not the Roll System Date Flag is set on the configuration job.
The same thing applies to BOTH End of Day and End of Month when it is the last day of the year.
You will need to set up multiple Renewal jobs if your company processes Renewal Offers at a different time than Renewals or if your company Pre Processes Renewals and Renewals.
Process Renewals: When this is selected, Diamond uses the Renewal Lead Days to determine how far in advance your company allows renewals to process. (Note: Both of these fields are found in the Company State LOB or Company State LOB Agency tables - if set up at the Agency level.)
Date Range
Days Before System Date: It is recommended
this value is set to at least 30 days, but it can be set to a larger
value.
Days After System Date: Set this
value to the largest value between Renewal Lead Days (if running Renewals)
and Pre Process Renewal Lead Days (if running Pre Process Renewals)
that has been set up for any Company / State / Line of Business combination.
Suppress Email Notification: If you have Email Notification set up for your scheduled jobs and want to receive an Email Notification, select this field to place a check mark in it. Otherwise, leave blank to suppress the Email Notification.
Here are some examples of how these jobs can be set up.
Process All Renewals for All Types (Renewals and Renewal Offers / All Bill Methods)
Renewal Project Name: Renewals - ALL
Process Renewals: Select.
Renewals Type (Renewal Offers or Renewals): Select "Both."
Bill Method (Direct Bill or Agency Bill): Select "Both."
Days Before System Date: 30 (or larger value).
Days After System Date: 60
Suppress Email Notification: Select to receive Email Notification when job completes.
Process Renewal Offers Only
Renewal Project Name: Renewal Offers
Process Renewals: Select.
Renewals Type (Renewal Offers or Renewals): Select "Renewal Offers."
Bill Method (Direct Bill or Agency Bill): Select "Both."
Days Before System Date: 30 (or larger value).
Days After System Date: 60
Suppress Email Notification: Select to receive Email Notification when job completes.
Process Renewals Only
Renewal Project Name: Renewals Only
Process Renewals: Select.
Renewals Type (Renewal Offers or Renewals): Select "Renewals."
Bill Method (Direct Bill or Agency Bill): Select "Both."
Days Before System Date: 30 (or larger value).
Days After System Date: 60
Suppress Email Notification: Select to receive Email Notification when job completes.
This allows an SQL Server Agent Job to be executed:
Once Add has been selected, the SQL Server Job Setup screen displays.
Description: Enter the name of the job (e.g., EOD Backup).
SQL Server Agent Job: Select the job from the combo box.
Initial Polling Interval: This is the number, in seconds, to wait after initially starting the SQL Server Agent Job before beginning to poll its current status.
Polling Interval: This is the number, in seconds, to wait between each retrieval of the SQL Server Agent Job execution starts.
If automated Email has been set up for End of Period Processing (Company Configuration Tool / System Email), then an Email Notification will be sent when the job starts and completes. A record is also written to the Error Log table that has the same information.
Special Notes: If you would like to begin using the new job type, you must make sure the following has been completed:
The SQL Server Agent Job has been created.
The SQL Service Agent service is running on the SQL Server.
Any Diamond user running the SQL Sever Agent Job has all of the authorities needed.