Add On-Call, Non-Working, or Custom Working Time to a Calendar

Use nonworking time to identify times when a resource, an organization unit, or a bucket isn't available for work. You can use the custom working time to specify a custom schedule for a resource. Similarly, you can use the on-call option to specify the time during which a resource is available on call. Be aware that you can change the calendar, only if you've the Read-Write permission for Resource Calendar on the Resource/User Info context layout structure.

Before you start

For Maintenance Resources, nonworking time and custom working time are included in the availability information used by Maintenance Cloud when scheduling maintenance work orders and operations.

Here's what to do

1. If you're using Oracle Field Service click the Navigator Menu and then select Calendars.
   The Calendar view appears for the group or bucket assigned to you.
2. Select the bucket, group, or resource for which you want to change the calendar.
3. Click the date for which you want to add the nonworking time, custom working time, or an on-call schedule.
4. Select On-Call and update these fields:

   Name	Description
   On-Call Schedule	The field specifies whether the resource isn't working, is working in a custom schedule, or is on call. Select Nonworking Time, Custom Working Time, or On-Call. If you select the blank option, the existing on-call schedule is removed and the earlier schedule is restored. You can't remove an on-call shift, which is part of a Schedule.
   Reason	If you've selected Nonworking Time, select the reason for which the resource isn't working. For example, Others. This field isn't displayed if you've selected Custom Working Time or On-Call.
   Start time, End time	If you've selected Custom Working Time, select the custom start and end time of the schedule. This field isn't displayed if you've selected Nonworking Time or On-Call.
   Comment	Enter any comment that you wish to provide, for example, Daughter’s graduation day, or Dentist’s appointment at 4:00 pm. This field isn't displayed if you select On-Call.
   End Date	Select the date on which you want to end the new working time.
   Repeat	Select the frequency (Daily, Weekly, Yearly) at the new working time must be repeated. Enter the number of days or select the day of the week on which you want the new working time to be repeated. If you've selected Yearly, select the end date for the recurrence of the new working time. The end date of the new schedule is displayed below the field. You can't add recurrence for a schedule and for Nonworking Time.
   Keep the Non-working days	Select this checkbox to retain the existing nonworking days in the resource’s calendar. This checkbox is available and enabled by default if the schedule is changed for more than a day. That is, it's available if you change the End date field.

5. Click Submit.
   If the nonworking time can be applied, the resource is marked as a nonworking resource for the selected date range. If the nonworking time can't be applied, a warning message appears. If you click OK, the nonworking time is applied, but a warning message appears on the resource tree for that resource on that day. Nonworking time can't be applied if the mobile worker has anything other than repeating, shift, or mass type of activities assigned on this route. The activities on the resource’s route, other than mass and repeating activities, are rerouted or assigned to the bucket, if these conditions are met:

   • The routing plan has the Enable reoptimization checkbox selected.

   • The resource meets the routing plan filter conditions.

   • If the Use resources outside the bucket option isn't selected for the routing plan, the activities may be assigned to the bucket despite having different work zones.

   • If the Use resources outside the bucket option is selected, then it depends on the resource. If the resource is a child of the routing bucket, their activities may be assigned to the bucket even if the work zone isn't a common work zone. However, if the resource isn't a child of the routing bucket, then only the activities for which the bucket has all the work zones may be assigned to the bucket.