What do the calendar entry types mean?

[joshuamayes]

When adding a calendar entry to  cmn_schedule_span table (as a related record to  cmn_schedule) I'm unsure as to how the type field changes the behavior of a schedule.

Looking at this article  https://docs.servicenow.com/bundle/helsinki-servicenow-platform/page/administer/time/reference/r_Sch... there's two pieces of the table that define type:

Type     Enter a label that describes the purpose of the schedule. The system also uses the schedule type to determine how to process certain schedules. Excluded: excludes time periods from SLA counts. Maintenance: specifies time periods where change management activities are allowed. A schedule containing maintenance schedule entries cannot also contain blackout schedule entries. Blackout: excludes time periods from change management schedules. A schedule containing blackout schedule entries cannot also contain maintenance schedule entries.

and  

Type   [Optional] Enter a schedule entry description.

However, the drop-down choices I have available are:  

• --None--
• Time Off
• Appointment
• Meeting
• Phone Call
• Excluded
• On Call

I understand how "Excluded" works since it's listed above.. and in my testing that's how i've found it to work.  But I really don't understand what the other options are for.

[Mwatkins · Accepted solution]

Unless something has changed in the last couple releases, the ones listed in the drop down - with the exception of "excluded" of course - are just informational. They don't technically do anything. They exist to allow someone to choose to provide more information about the intended reason for the schedule span.

Regarding the Maintenance and Blackout types, they are defined on the schedule (cmn_schedule.type) not the span (cmn_schedule_span). In the demo data, the spans (cmn_schedule_span) in a Maintenance schedule or Blackout schedule (cmn_schedule) do not have a type specified; cmn_schedule_span.type = [blank]

[joshuamayes]

Thanks for clearing that up for me.

I've sent a feedback on the KB article to point out the errors.