1. Using Core Application
  2. Suspend a Segmentable Activity

Suspend a Segmentable Activity

When you must stop working on a segment for the time being and don't want to cancel it, you can suspend it. When you suspend a segment, you provide the time that is required to complete the remaining part of the segment. In this scenario, the application creates a new, duplicate segment (activity) that you can start at any time throughout the day.

Note: You can suspend only started or pending segmentable activity segments.
  1. Click the hamburger icon and then click Dispatch Console.
  2. Select a bucket or resource in the Resource Tree and go to the List view.
  3. Click Adjust Time in the activity hint for the started segment that you wish to suspend.
  4. On the Adjust time page, select the time that is still required to complete the segment. Click Submit.
  5. Click Suspend in the activity hint.
    The Suspend Activity dialog box opens.
  6. Add the reason for suspending the segment and click Submit.
    Here is the result of suspending a segmentable activity segment:
    If... Then...
    You suspend a started segment Two segments, Suspended and Pending not-ordered are created. The original segment becomes not-ordered. The duration of the not-ordered segment is reduced by the duration of the Suspended part. For example, the duration of the segment is 60 minutes and you have worked for 10 minutes before suspending the activity. Then, the Pending segment is created for 50 minutes. The final duration of the not-ordered segment is not less than the minimum duration of the segment defined for the activity type. However, the duration of the not-ordered segment can exceed the "Maximum total duration of segments created for a particular day" constraint.
    You suspend a pending ordered segment The current segment becomes non-ordered. The remaining details are same as the previous row.
    You don't work on the pending segment for the rest of the day, and the segment is moved to the bucket The duration of the outdated segments is added to the length of the not-scheduled segment. Let’s say the not-scheduled segment doesn't exist and there is an outdated segment for which the duration has not been distributed. The application adds this not-scheduled segment through a background process.