System properties for On-Call Scheduling

  • Release version: Australia
  • Updated March 12, 2026
  • 4 minutes to read

    • The property settings configure On-Call Scheduling operations.

    Setting properties from the UI

    You can set most property values from the On-Call Properties page at On-Call Scheduling > Administration > On-Call Properties.

    Property Description
    com.snc.on_call_rotation.calendar_macro The name of the macro that provides a calendar functionality for On-Call shift. The default uses DHTMLX scheduler. Fullcalendar is set by ocf_calendar.xml.
    com.snc.on_call_rotation.support_legacy_spans Used to search for override or time-off records that may have been generated as cmn_schedule_span records and not the standard roster_schedule_span table.
    com.snc.on_call_rotation.pto.approval.required Configuration to determine if PTO requests need approval.
    com.snc.on_call_rotation.factor_daily_rotation_interval_all_day If true, mandates daily rotation to occur at midnight. If false, then use the time that is specified for the roster start time for the next day.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.log.level Enable logs for debugging.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.log_escalations Enable logging of escalations. See View details in an escalation log.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.calendar_macro The name of the macro that provides a calendar for On-Call shift. The default uses DHTMLX scheduler. Fullcalendar is set by ocf_calendar.xml.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.support_legacy_spans Used to search for override or time-off records that may have been generated as records in the cmn_schedule_span table and not in the standard roster_schedule_span table.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.pto.approval.required Configuration to determine whether PTO requests require approval.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.contrast Sets text color to either white or black depending on which has the highest contrast with the background color on the calendar. The following algorithms determine text color:
    • ContrastYIQ
    • ContrastPercent
    • ContrastLuminance
    Note:
    ContrastYIQ is used if the property is not enabled.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.access.debug If true, enable general On-Call logs for debugging.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.reminders.showtz Include a user's time zone in On-Call Shift Reminder notification emails.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.show_legacy_calendar Show the legacy On-Call calendar.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.calendar_read_roles Comma-separated list of roles that can read the calendar.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.cover.color Sets the color of the span for On-Call coverage for another roster member.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.timeoff.color Sets the color of the span when the type is time-off.

    Location: System Property [sys_properties] table
    com.snc.on_call_rotation.landing_page.group_limit The number of On-Call schedules loaded per batch on the client side. Default: 20.
    com.snc.on_call_rotation.landing_page.max_groups The maximum number of On-Call schedules that can be loaded on the client side. Default: 300.
    Note:
    The default value is chosen as the limit of acceptable client performance.
    com.snc.on_call_rotation.landing_page.pinned_notification Displays a message when any schedule is pinned successfully.
    com.snc.on_call_rotation.landing_page.notification_timeout Specifies the time (in milliseconds) until the message for successful pinned scheduled is displayed.
    com.snc.on_call_rotation.landing_page.show_wizard_btn Displays the New button to open the On-Call schedule wizard.
    com.snc.iam.conference_call_follow_on_call_escalation If selected, On-Call the escalation path is followed when a user group is added to a conference call.

    This property is added when the Incident Communications Management (com.snc.iam) plugin is activated.
    com.snc.iam.conference_call_escalation_workflow If selected, custom escalation hierarchy is applicable in On-Call Scheduling workflows.

    This property is added when the Incident Communications Management (com.snc.iam) plugin is activated.
    com.snc.on_call_rotation.landing_page.show_pending_actions If true, displays the pending actions on the On-Call Schedules landing page.
    com.snc.on_call_rotation.allow_rota_overlap If true, overlapping shifts are allowed for a user group.
    com.snc.on_call_rotation.escalation_rule_rota_overlap Escalation rule that applies for shift overlap. Options:
    • Escalate to outgoing Shift
    • Escalate to incoming Shift
    • Escalate to all Shifts
    com.snc.on_call_rotation.pto.configuration Specifies how a roster member can create vacation time (PTO). Options:
    • With approval
    • Without approval
    • Not allowed
    com.snc.notify.default.conference_call_follow_on_call_escalation If true, the On-Call escalation path is followed when a user group is added to a conference call. However, the time between reminders is set to 60 secs. Users can create properties for required task types such as incident. Example: For Incident, the property key would be com.snc.notify.incident.conference_call_follow_on_call_escalation.
    Note:
    The property is enabled only when the Notify plugin (com.snc.notify) is active.
    com.snc.notify.default.on_call_escalation_level Fetches the number of users from the group escalation plan. A value of -1 fetches all users from the plan. A value of 1 fetches only the first level of users, and so on.
    Note:
    • This is the default property that is used until the specific property for the task type is configured. To use different workflows for different task types (such as incident or problem), create a new property by replacing the word default in the key with the task type.
    • This property is used only when the com.snc.notify.default.conference_call_follow_on_call_escalation sys property is false.
    • The property is enabled only when the Notify plugin (com.snc.notify) is active.
    com.snc.notify.default.conference_call_escalation_workflow The sys_id of the default workflow that must be attached when escalating a conference call.
    Note:
    • This is the default property that is used until the specific property for the task type is configured. To use different workflows for different task types (such as incident or problem), create a new property by replacing the word default in the key with the task type. Example: For Incident, the property key would be com.snc.notify.incident.conference_call_escalation_workflow.
    • The property is enabled only when the Notify plugin (com.snc.notify) is active.
    com.snc.on_call_rotation.use_slack_for_dm If false, disables direct messaging via Slack on all On-Call Scheduling pages.
    com.snc.on_call_rotation.use_msteams_for_dm If false, disables direct messaging via Microsoft Teams on all On-Call Scheduling pages.
    com.snc.on_call.announcement_message If false, removes the banner of SOW announcement from on_call_calendar page.
    com.snc.on_call_rotation.new_trigger_engine If true, a new on-call trigger engine is activated which enables on-call subflows get triggered via flow runner queue. As the on-call subflows are marked as high priority they get processed faster via flow runner queue compared to the traditional event queue especially when multiple events are triggered at the same time and are in the process queue.