1. Using Core Application
  2. Pin an Activity to a Specific Time in a Route

Pin an Activity to a Specific Time in a Route

You might want to pin an activity to a specific time in a route, especially when you work with a third-party provider. Oracle Fusion Field Service uses the Communicated Window Start and Communicated Window End fields to pin an activity. The Communicated Window is preserved throughout the application.

Prerequisites:

  • Your administrator must add the Communicated Window Start and Communicated Window End fields to the Add/Edit Activity page.
  • Your administrator can configure an activity identifier using the Communicated Window End Is not empty condition to distinguish pinned activities from other activities.

How it works:

You must select the date and time in the Communicated Window Start and Communicated Window End fields on the Activity Details page for the activity that you want to pin. Then:

  • The Time view shows the activity with the visual identifier.
  • If you try to move the activity manually, you see a warning. If you move it despite the warning, you can see that the activity is in jeopardy.
  • Bulk routing optimizes and moves the activity back so that the Communicated Window is preserved.

Exceptions:

  • Urgent and Immediate routing ignore the Communicated Window Start and Communicated Window End values.
  • Bulk update API might move the activity outside its Communicated Window date and time. This is to ensure that the activity is synchronized correctly with third-party applications.
Note: The Communicated Window functionality is designed for customer-facing activities to record the time that was communicated to the customer. For single-day internal activities, the Communicated Window fields work as expected and you can pin them to specific times. However, the Communicated Window fields aren't intended to be used for repeating internal activities such as trainings, lunches, or warehouse tasks. These activities are treated as phantom activities in future routes until at least one customer-facing or internal activity is assigned to the resource's queue for that date. As a result, their pinned time will not be held.