Move Reasons Enhancements

When activities are manually moved within Oracle Field Service, depending on the configuration, dispatchers may be required to indicate a move reason. Move reasons help the leadership to understand why moves are being made thus, enabling them to drive optimization changes within the organization.

To better analyze such changes, move reasons can be exported to Oracle Analytics Cloud, Oracle Autonomous Database or other systems using Events API. For example, you may be interested to know what types of activities are being moved most often or how each division is trending with the adoption of automated routing plans. Exporting move reasons to Oracle Analytics Cloud, or other BI tools, allows you to group, filter and/or pivot the data in different ways. Doing so helps you to identify a new routing plan configuration requirement or potentially a process change within the organization.

New Property: Label

A mandatory property Label has been added to the Add/Edit Move Reason dialog. During upgrade to Update 22C, this field is populated with move_reason_id value. This property is available for the Manual Move Fields entity in the Daily Extract Application.

Export to Oracle Analytics Cloud and Oracle Autonomous Database

You can export activity move action details to Oracle Analytics and Oracle Autonomous Database. The new entity Manual Move Fields is available for Applications with types Oracle Analytics and Oracle Autonomous Database.

The possible data transfer value is Once Daily.

Manual Move Fields contain the same dataset as the Daily Extract application.

Events API Support

Activity move action details are available in the Events API.

The event activityMoved contains a new section moveDetails. This section contains the move action fields moveReason, moveCondition, workSkillMismatch, and workZoneMismatch.