Other Segmentable Activity Specifications

This section includes the specifications for segmentable activities in areas such as property inheritance, activity search, travel time calculation, work zone and work skill support, inventory and required inventory support, capacity management and routing, and so on.

Property inheritance from a segmentable activity to its segments

In a pending segmentable activity, segments inherit all fields and custom properties, except for the Duration and Position in route fields. These two fields are determined for each segment. If you add a file property to a segmentable activity, the content of such property isn't cloned to each segment. Instead, a reference to the file property is created for segments. If you upload a new file to a started segment, the new File ID is used only for the segment for which it was created. All other segments refer to the file uploaded to the entire activity, if any.

Activity search

The search is performed both in the activities and in their segments. Therefore, the search results may include these:
  • All existing segments of a scheduled segmentable activity. The activity itself isn't returned.

  • Non-scheduled segmentable activities.

There's no visual difference between segmentable activities and single-day activities in the list of search results.

Support of Work Zones, Work Skills, and preferred resources

If you've selected the Support of work zones, Support of work skills, and Support of preferred resources options for the segmentable activity type, they will be determined for all activities of such type. The work zone, work skills, and preferred resources are determined for the entire segmentable activity and retrieved for each segment on demand. The same work zone, the set of work skills, and the same preferred resources are applied to all segments.

Travel time calculation

If you've selected the ‘Calculate travel’ option for a segmentable activity, then the travel time is calculated for all the segments. The calculation logic and usage for statistical purposes is the same as that for single-day activities.

Support of inventory and required inventory

Any inventory added to a segmentable activity is added for the entire activity. Each segment shows the same set of inventory. Any inventory action (install, deinstall, add, and so on) can only be performed on a specific segment. However, these operations will update the inventory list for the entire segmentable activity and, consequently, the inventory list shown for all other segments. Similarly, any required inventory is also assigned to the segmentable activity rather than its segments. The same required inventory is shown for all segments. All required inventory actions are performed for the segmentable activity and update the required inventory list for all segments. Note: Required inventory added to a segmentable activity sets no assignment restrictions. No alerts are shown when the resource’s inventory doesn't match the required inventory.
Note: Installed inventory isn't associated with any specific segment. Instead, it's accumulated at the master activity level. Therefore, the "installed_inventory" block will be empty for each segment. Once the entire segmentable activity is completed, the "installed_inventory" block will contain all installed inventory, as it does for ordinary activities.

Capacity management and routing

segmentable activities aren't included in capacity and quota calculation. No capacity categories are calculated for segmentable activities and neither are they included in the Used values. However, segments of segmentable activities are added to the Other activities value, therefore, the capacity is still consumed. Also, they're included in the start-time statistics. Segmentable activities can be assigned manually or through Immediate Routing plans. These rules apply for Quota Management:
  • Segmentable activities are handled as "internal" activities.

  • Segmentable activities can't be booked with the "get_capacity" function. This function doesn't calculate capacity categories for such activities.

  • Segmentable activities aren't included in the Used quota values on the Quota view. Instead, they're added to Other activities.

Activity links

If you've selected the Support of links option for the segmentable activity type, you can link it with other activities. When you create a link to a segmentable activity, the link is always made to the entire activity and never to a particular segment. Therefore, not all types of activity links can be used for segmentable activities. Links defining the sequence of activities make no sense with segmentable activities which can be split between different days and resources, when their separate segments are moved, rescheduled, canceled, and placed in the non-scheduled pool. Segmentable activities can be linked to other activities based on assignment constraints defining whether activities must be assigned to the same resource, or to different resources. You must create the link template for segmentable activities using the Related link type. If you've selected a different link type, the error message, ‘Unable to create link of this type for segmentable activity.’ is displayed. If a segmentable activity is linked to another activity, an alert informing of the existing link appears as follows:
  • Manage—in the Links tab of the Activity details page

  • Manage—in the Move confirmation dialog

  • Installed App—on the Linked activities page

The link data displayed for a particular segment relates to the entire segmentable activity. Adding or deleting a link for a segment actually adds or deletes a link for the entire activity.

Activity history

You can retrieve history from both, a non-scheduled segmentable activity and a segment of a scheduled segmentable activity. The history for a non-scheduled activity contains records for the activity itself. The history for a segment contains records for the current segment and for the entire activity. Some actions relate both, the segmentable activity and one of its segments. In this case, the history contains two records, the one for the entire activity marked with (segmentable activity) in the Action column.

Processing of segmentable activities by Daily Extract

Important: This information only applies to Oracle Field Service environments. You can verify whether you've Oracle Field Service or Oracle Fusion Field Service, by signing in and checking on the About page.

Daily Extract stores segmentable activities and their segments together with activities of other types and extracts them into the Activity Fields file. You can identify segmentable activities by their type—‘multiday_activity’ for the entire activity and ‘multiday_activity_segment’ for individual segments. If a segmentable activity is still in progress, each daily extraction contains the completed segments of the activity in the current day routes. As soon as the entire activity is completed, the extracted file contains the data of both, the individual segments and the entire segmentable activity.