Audit schedule properties file

The audit schedule properties file defines which properties are required or optional for audit schedules of a particular audit type. Each audit type that requires schedules has at least one audit schedule properties file.

The schedule type specifies whether t he schedule type is single or series. A single audit occurs once. A series audit occurs one or more times. An audit type can have both single and series schedule types. In the base configuration, Checking Audit is defined for both schedule types.

In Studio, create a new audit schedule properties file in configuration > config > resources > productmodel > auditschedules. Only Product Designer uses this file. PolicyCenter does not.

You can base this file on existing properties files in this directory. For example, FinalAudit.single.properties is the audit schedule properties file for a Final Audit audit type. Name the audit schedule properties file:

AuditType.scheduleType.properties

Where:

AuditType – The name of the audit type.
scheduleType – The schedule type can be single or series. A single audit occurs once. A series audit occurs one or more times.

For example, Final Audits are always single audits because they only occur once per policy term. Therefore, there is only a FinalAudit.single.properties file.

Premium Reports are generally series audits, because there is a series of them during a policy term. Therefore, there is only a PremiumReports.series.properties file. Some types of audits such as Checking Audits, may happen both as single audits and as series audits. These audits require audit schedule properties files for single and series.

In the audit schedule properties file, specify one of the following values for each property. The value has the following effect when defining an audit schedule in Product Designer:

REQUIRED – When defining an audit schedule of this type, the user must specify a value for this field.
EDITABLE – The user can specify a value for this field. The field is not required.
HIDDEN – This field is hidden.

In the properties file, specify values for the following properties for schedules for your new audit type. If you do not specify a value, the value defaults to EDITABLE.

Properties	Product Designer label	Description
`auditMethod`	Audit Method	A drop-down list to select how to conduct the audit.The drop-down lists values are defined in `AuditMethod` typelist.
Schedule Details fields that only apply to series audit schedules
`frequency`	Scheduled	A drop-down list to select how often audits occur. Values are defined in the `AuditFrequency` typelist.
`intervalComputationType`	Schedule Basis	A drop-down list to select the schedule basis. Values are defined in the `AuditIntervalComputeType` typelist. In the base configuration, the values are: Calendar Month Policy Month
`calendarMonthRoundDate`	Round to Next Month on Day	A text box to enter which day rounds up to the next month.
`minimumAuditPeriodLength`	Minimum Audit Period (Days)	A text box to enter the minimum audit period.
`excludeLastAuditPeriod`	Exclude Last Audit Period	A check box to select whether to exclude the last audit period when creating a schedule of audits.
Schedule Details fields that only apply to single audit schedules
`endDateDelayAmount`	Single Checking Ends After Policy Period Start (days)	A text box to enter the number of days after the policy period start the single audit ends.
`endDateDelayUnit`	Type of Days	A drop-down list to specify the type of days to use when calculating the end date for the audit. Values are defined in the `DateCalcUnit` typelist. In the base configuration, values are: Calendar Days Business Days
Audit Report Initiation fields that apply to both single and series audit schedules
`initDelayDirection`	Audit Initiated	A drop-down list to specify whether the audit is initiated before or after the audit period end date. Values are defined in `AuditReportDateDirection` typelist. This typelist is final.
`initDelayAmount`	Days Before Days After	Depending upon the Audit Initiated selection, a text box to enter the number of days, before or after, to adjust the audit initiation date from the audit period end date.
`initDelayUnit`	Type of Days	A drop-down list to specify the type of days. Values are defined in the `DateCalcUnit` typelist.
`initBusinessDayAdjustment`	If Initiated on a Non-Business Day	A drop-down list to specify how to adjust the calculated audit initiation date if it occurs on a non-business day. Values are defined in the `AuditBusinessDayAdjust` typelist.
Audit Deadline fields that apply to both single and series audit schedules
`dueDelayDirection`	Audit Due	A drop-down list to specify whether the audit is due before or after the audit period end date. Values are defined in `AuditReportDateDirection` typelist. This typelist is final.
`dueDelayAmount`	Days Before Days After	Depending upon the Audit Due selection, a text box to enter the number of days, before or after, to adjust the audit due date.
`dueDelayUnit`	Type of Days	A drop-down list to specify the type of days. Values are defined in the `DateCalcUnit` typelist.
`dueBusinessDayAdjustment`	If Due on a Non-Business Day	A drop-down list to specify how to adjust the audit due date if it occurs on a non-business day. Values are defined in the `AuditBusinessDayAdjust` typelist.
Escalation fields that apply to both single and series audit schedules
`numDaysAfterFirstEscalation`	Escalate Number of Days after First Prompt	A text box to enter the number of days to wait before the first escalation.
`firstEscalationPrompt`	First Escalation Prompt	A drop-down list to specify what prompts the first escalation. Values are defined in the `EscalationPromptType` typelist.
`numDaysAfterSecondEscalation`	Escalate Number of Days after Second Prompt	A text box to enter the number of days to wait before the second escalation.
`secondEscalationPrompt`	Second Escalation Prompt	A drop-down list to specify what prompts the second escalation. Values are defined in the `EscalationPromptType` typelist.
Miscellaneous fields
`paymentPlanCode`	Payment Plan Code	A text box to enter the payment plan code. For an example, see PremiumReport.series.properties and ReportPolicyMonthExclLast.xml.
`reportingDefaultDepositPct`	Reporting Default Deposit %	A text box to enter a default deposit percentage. For an example, see PremiumReport.series.properties and ReportPolicyMonthExclLast.xml.

In the base configuration, PolicyCenter does not use the escalation fields. You can write code to escalate audits when they are not completed.

Product Designer loads your new audit schedule properties files when you log out, switch change lists, or restart Product Designer.