Oracle Field Service
Using Core Application
Chapter 2
Dispatcher Activities
This helps you find all segments of the same segmentable activity quickly, especially when they are assigned to
different resources.
This table provides the individual segment and segmentable activity property value sharing and inheritance rules.
System/Custom Property Behavior When Individual
Segment is Generated
Behavior When Property
is Changed Within
Individual Segment
Behavior When Property
is Changed Within
Segmentable Activity
Level
System Status (for example,
Pending, Started)
Segments are created in
Pending status
Segments hold their own
Status, no sharing or
inheritance
Transition of segmentable
activity to a terminal
state causes: completion/
deletion of pending
segments
System Position in route Segments are created
with the ability to be
ordered or non-ordered,
according to the activity
type feature defined for the
Segmentable activity.
Segments hold their own
Status, no sharing or
inheritance.
Position in route for
segmentable activity is
either ordered or non-
ordered.
If the value is changed,
pending segments are
updated: from being not
"Non-ordered" to "Ordered"
and vice-versa.
System Duration Segments are created
with the Duration value,
within the constraints and
optimized route in presence
of other activities.
Segments hold their own
Duration values. Within
a segment, to access the
overall activity duration
explicitly, Time to complete
is used.
Non-scheduled portion of
the segmentable activity
is a buffer for difference
between total activity
duration and the sum of
created segment durations.
System Time to complete Segments have access
to segmentable activity's
"Time to complete", but
don't hold own values.
Value doesn't include
finished segments.
Segmentable activity's
"Time to complete" field is
updated.
Segments have access to
the updated value of the
segmentable activity's
"Time to complete".
87
To Next Page
Loading...
Need help?
General
