The statistical value is produced as a result of the expansion algorithm. This adjustment may occur when one of the following situations occurs:Īpplication is unable to find a Statistical “Learned' record that matches a Travel Key The steps will be the same for organization units and buckets – simply select them from the Resource Tree instead of individual resources.Īfter routing is performed, the application may adjust Travel Time further for activities that are pending and ordered on a route.

For the purpose of this guide, the steps for building calendars at the resource level will be covered. However, if options are set at the resource level, they take precedence over their inherited settings. When associating calendar options with higher-level entities (organization units, buckets), their child resources assume the same options.

This ties back in with the explanation of the calendar hierarchy. While the process is the same for each – depending on the selection made from the Resource Tree – the implications differ. Non-working Time - Non-working time is used to identify known absences such as bereavement, illness, holidays and vacations.Įarlier portions of this guide covered the creation of work schedules, shifts and non-working time therefore this section will concentrate on assigning those calendar options to entities on the Resource Tree (organization units, buckets, resources). Working Time – The time frame in which a resource is scheduled to work that does not comply with one of a company’s standard shift definitions. In addition to work schedules, shifts can also be assigned directly to organization units, buckets or resources. They can be created once and used by a variety of work schedules, simplifying the assignment of schedules. Shifts - Shifts are used to define the different working times as defined by a given organization. Work schedules represent the highest level of calendar options. Work Schedules - Work schedules contain multiple shifts and non-working times and are the mechanisms for grouping these items so that they can be applied to a single resource or an entire organization unit or a bucket. To better understand calendars and their potential components, we must define the different options. Typically, the time zone of a physical location is used for notifications, but you may use your preferred time zone, such as your headquarters time zone or any other in which you prefer to get notifications. The activity time zone is used for notifications and can be used in APIs (for example, for sending messages).

A field resource sees all the data in their own time zone, but when the activity (customer) is in a different time zone, both times are shown as appropriate. Configuring these time zones is even more important if they are different. If your organization operates in multiple time zones, it is important that you configure both, the field resource and activity time zones correctly.

When a user opens the non-scheduled or non-ordered activities on the right of the screen, the activity identifier shows information according to the rules described in the Activity related information section later in the topic. Information on the activity hint and activity label is displayed according to the rules described in the Activity related information section later in the topic. Information on the resource hint is displayed in the time zone of the resource this hint belongs to. The only exceptions are the resource hint, activity hint, and activity label.

Faadu meaning