This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 12 JUL 2021 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Work Zone Management Integration Enhancements
Starting with update 21C, a new parameter workZoneStatus is added to the ‘Get resource work zones’ (GET /rest/ofscCore/v1/resources/{resourceId}/workZones) REST API method’s response. The workZoneStatus parameter indicates whether the status of a work zone is active or inactive. Having this information in the response avoids additional API calls to the work zone dictionary to check whether the work zone is active, and makes integrations easier.
View and Update Travel Key Level Parameters
Starting with Update 21C, the application calculates the airline speed and parking time for each travel key separately, if there is enough reported data to estimate them. As part of this functionality, you can use these REST API methods to perform various actions:
- Use the ‘‘Get airline distance based travel’ GET /rest/ofscStatistics/v1/airlineDistanceBasedTravel) REST API method to retrieve the estimated and overridden airline distance based travel time at a travel key level.
- Use the ‘Get airline distance based travel’ (PATCH rest/ofscStatistics/v1/airlineDistanceBasedTravel/) REST API method to override the airline distance based travel time at a travel key level.
Activity and Location Notifications in Collaboration
Starting with update 21C, to improve the user experience, all the notifications are consolidated in one area under the chat icon in the header. So, the Collaboration window now contains chat messages, Help desk chats, history chats, and notifications.
Auto-Refresh Dashboard Charts in Core Application
Starting with Update 21C, dashboard charts are refreshed automatically based on the refresh rate configured at the resource level. You can configure the refresh rate in the minutes field on the Edit Resource page. The dashboard gets automatically refreshed based on the duration set for the resource.
Starting with Update 21C, you can select a division-wide schedule for resources and change it back to a default schedule, if required. You can also add comments when you add a regular schedule to a resource.
Date/Time Picker UX Improvements for Service Window, SLA and Activity Start/End Time
Starting with Update 21C, several improvements have been added for date and time fields. You can select the values for Service Window start and Service Window end using a Time editor for the activities that do not require the support of time slot. Or, you can clear the Service Window values with a single click.
You can select the date and time from a Date and Time editor for these fields:
- SLA start and SLA end
- Start date and End date for repeating activities
Starting with Update 21C, the Print Route option has a more compact view. The Print Route option available in the Dispatch Console and Activity List pages enables users to print the route of field resources.
Use Plug-Ins or Custom Forms with a Map Layer Asset
Starting with Update 21C, map layers include the new ‘Shape Hint’ button. You can use this button to open a plug-in or a custom form from the map layer to perform actions such as, creating an activity.
Upload a Shape File from a Local File System
Starting with Update 21C, you can create a Work Zone layer or custom map layer by uploading a shape file from your local device. This eliminates the need to host the shape file somewhere else, but you can still host it at your preferred location.
Set Read-only Mode for Outbound Integration Channels
Starting with Update 21C, you can set Outbound Integration channels to read-only using the Configuration screen context.
Applying Machine Learning to Define Airline-Distance Parameters
Starting with Update 21C, the application calculates the airline speed and parking time for each travel key separately, if there is enough reported data. For travel keys where there isn't enough reported travel data, the default airline speed and parking time are used. You can also get and override this data using APIs.
Routing pages have new user interfaces based on Redwood styles.
What's New in Routing:
- For Immediate routing plans (both for Urgent activities and for activities which fit the filter), you may control which days of the week they should run, similar to Once a Day and Recurrent ones. Now specific business rules for immediate activities can be defined based on your organization's working and non-working days.
- Look and feel of the routing plan Add and Edit page is changed in accordance with the latest Oracle Redwood guidelines, so the page now looks similar to other Oracle CX applications.
- Particular dialog box translations were changed for better clarity and to correspond to Oracle Redwood guidelines.
- Routing plans within the routing profile are now listed alphabetically, which makes it easier to find the needed routing plan.