1. Using Core Application
  2. Constraints on Creating a Segmentable Activity

Constraints on Creating a Segmentable Activity

When you create a segmentable activity, the application generates its segments automatically. While generating the segments, the application takes into account various constraints ensuring efficient task distribution and compliance with the customer agreements.

These constraints apply to a scheduled segmentable activity:

  • When you assign a scheduled segmentable activity to a route, its segments are always generated starting from the date of the route. The first segment is always inserted on the day for which the activity is scheduled, regardless of whether a corresponding free time interval is available in the route.

  • The minimum duration of a single segment is always observed. If the route for a particular day has no time interval for a minimal single segment, no segment is created for that day, except the first segment, which is always created on the selected date.

  • If there is no interval available for assigning the remaining duration for 31 days after the last assigned segment is created, the remaining duration is moved to the non-scheduled pool of the same resource making the activity partially scheduled.

  • The service window constraint applies only to the first segment of a segmentable activity in the route.

  • When creating a segmentable activity, the application should observe the service window constraint not only for the segmentable activity but also for other activities in the route. However, the less time that remains from ETA to the service window end, the higher is the probability of service window overdue. To reduce the overdue probability, the application reserves 20% of the service window scheduling the activity only to the first 80% of the service window interval.

  • In addition to the service window reservation, the Service Window Warning parameter defined on the Display page also controls the service window compliance.

  • If the SLA start corresponds to the day on which the segmentable activity is started, this value is used as the minimum ETA for the first created segment of such activity.

  • No segmentable activity segments are created on non-working days. If a non-working calendar is assigned to a resource after the segmentable activity is created, the segment assigned to that day is not moved automatically. An alert is displayed, indicating that a manual action is required. Such behavior is intended to prevent unnecessary segment changes, or removals when the calendar is changed only temporarily.

  • On-call calendar is ignored in segmentable activity segment creation.

  • When a segmentable activity is non-scheduled, no segments are created. Segments are created as soon as the activity is scheduled to a particular day.

  • Segmentability is defined at the activity type level and cannot be changed after the activity is created. For activities that may potentially span multiple days, it is a best practice to use a segmentable activity type from the beginning, with appropriate minimum and maximum segment durations configured. If an activity was created as non-segmentable and later needs to be segmented, the recommended approach is to close or cancel the original activity and create a new one using a segmentable type.