Update 19B

Revision History

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

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.

Administration

API Access Using User Name and Password

Starting with update 19B, Allow legacy access via API using user login and password option is not shown on the General tab, User Types screen, for the instances where such access is not used. This feature doesn't affect the clients who still use the deprecated access.  

NOTE: The Legacy API Authentication option in the User Type screen was deprecated with the 18D (November 2018) Update. Customers are advised to use the Client_ID/Secret Authentication and OAuth2 supported by the REST and SOAP APIs. These options can be configured using the Configuration - Applications option. The Legacy API Authentication option will be removed with the 19C (August 2019) Update. To ensure your integrations continue to operate after the 19C Update we strongly encourage you to migrate to the Client_ID/Secret Authentication and/or OAuth2 between now any July 2019. 

Android and iOS Applications

Biometric ID on Installed Apps

From update 19B, users will have the option to use fingerprints to login to their Oracle Field Service Cloud instances when using the Installed Android or iOS mobile app. This allows any installed app user to skip the login process with their username/password. Users need to select the ‘Enable Fingerprint ID’ or ‘Enable Touch ID’ option from the login screen to map the password with fingerprint for the first time. For future logins, users can use the finger on the Touch Sensor without having the need to enter the username and password.

APIs

Collaboration REST API for Third-Party Applications

The Collaboration REST API allows external applications to integrate with the Collaboration service and initiate a conversation with the Collaboration users. Starting with update 19B, customers can integrate other messaging applications, such as a chatbot, with Oracle Field Service Cloud using the Collaboration REST API as a channel.

The following operations are supported:

• Initiate a chat with a user or a group of users (as a conference chat)
• Send a message to an existing chat
• Leave a chat
• Get the participant details of a chat
• Invite a user

Metadata API: Support of Forms

Starting with update 19B, a new Metadata API will support the following RESTful operations related to Forms:

• Retrieve a list of configured forms
• Retrieve form attributes and content
• Create or update a form
• Delete a form

Property Update Mode in Bulk Update Operations

Starting with 19B, an optional parameter 'inventoryPropertiesUpdateMode' is added to the Bulk Update Resource Inventories and Bulk Update Activities operations. The value of this parameter indicates whether the existing inventory properties must be replaced or retained and updated with the new properties that are sent in the request.

Support Custom Fields in API for Resource Locations

The Core Resource API is updated in 19B to support custom properties in Resource Locations. You can now specify the custom properties that are used in your travel key configuration.

Capacity Management

Capacity Configuration in Core Application

Starting with update 19B, you can configure a Capacity Area using the Core Application instead of the Legacy Core Manage application. You can configure Capacity Area buckets on the Quota Configuration screen in the following ways:

• The + icon (next to the Search field) allows you to add new capacity areas.
• The Stop using as a Capacity Area button allows you to disable capacity areas from the Resource Tree.

Collaboration

Usability and User Interface Improvements

As part of update 19B, the following usability and UI improvements are made in the Collaboration module:

• Group Message enhancement: If there is only one user present in the User Group, Location, or Activity Broadcast Group message, then the group message is initiated as a one-to-one conversation.
• Drag and Drop functionality: Users can now drag and drop resources and activities from the Core Application Dispatch Console.
• Expiry for Collaboration messages: The expiry period for system chats and automatic broadcasting/activity chats will be set to 1 day (24 hours). You can change the default value of 1 day (24 hours) based on your preferences only for group message and location broadcasting. However, you cannot change the default value of 1 day (24 hours) for activity broadcasting and automatic activity broadcasting.
• UI improvement for Collaboration messages: A new user interface view to share user info and share or transfer inventory or activity is added to Collaboration.
• New line messages in Collaboration: Users can add new line messages in Collaboration using Shift and Enter. In mobile devices, users can use the Enter key. Also, the messages will be left aligned in the chat window.

Core Application

Automatic Creation of Mass and Repeating Activities

Starting with update 19B, mass and repeating activities can be automatically created up to 30 days in advance, making them available through API for external applications that are integrated with Oracle Field Service Cloud.

Improved Map Zoom and Centering

Starting with update 19B, the improvements made to the zoom and centering of dispatch maps include:

• The zoom level of the map remains the same, even if users change the routes. In other words, when an activity is added or removed from a resource, the map does not 'jump' to the new route.
• When there is no data binding for the map, the map is centered based on the company boundaries as defined in the Business Rules screen, the area where the company operates from activity location statistics, or the whole world.
• Dragging of Google map is improved, so a layer with activities and routes 'sticks' to its map tiles.

Improvements to Oracle Field Service Cloud Core Application

Starting with update 19B, the following changes are implemented in the Oracle Field Service Cloud Core Application:

• Responsive Headers: Responsive headers are implemented in the Dispatch Console, Routing, Quota, and Forecasting screens. For devices with a larger screen, the user can view most options upfront without having to navigate a lot within the application. If the user has a device with a small screen, most options are available within the Options menu.
• Improvements to Resource Tree: Users have the option to expand the Resource Tree or collapse it to utilize the device screen efficiently. This change can be viewed in the Dispatch Console, Manage, Maps, Routing, Quota, Forecasting, Resources, and Calendars screens.
• My Route in Main Menu: ‘My Route’ can now be configured in the main menu from the Screen Configuration screen. This option can be used to navigate to the user’s Route screen.
• Activity and Resource Hints: The Activity and Resource hints in Dispatch Console appear similar to how they appear in the Legacy Manage screen.
• Resource Name and Date in Activity Details: The resource name and date of the activity are displayed in the header within the Activity Details screen.

Manage Non-Scheduled Activities on Dispatch Map

Starting with update 19B, non-scheduled activities are displayed on the Core Application Dispatch Console map, allowing you to easily locate activities and assign them to the desired resources.

Multi-Day Activity Improvements

Starting with update 19B, you can suspend multi-day activity segments.

Required Inventory Improvements

Starting with update 19B, you can add, edit, and delete required inventory for activities in Oracle Field Service Cloud Core Application. You can also add required inventory from your Parts Catalog.

Support for Group Actions for Resources in Core Application

Starting with 19B, you can select multiple resources when you perform actions such as activate, deactivate, unlock, or delete resources, and assign users to collaboration groups. Further, you can restrict access to these actions for specific user types.

Unification of Terms

Starting with update 19B, the terms Action, Action link, and Button are referred to as Button throughout the application and in the end-user documentation.

Integration

ChatBots Integration

With update 19B, you can integrate Oracle Digital Assistant (ODA) with Oracle Field Service Cloud and then host a ChatBot service at your site. ODA is an environment for creating ChatBots and then deploying them on a channel of your choice. Using ChatBots helps you engage technicians in their day to day activities and allow them to work smarter and more productively. 

Mobility

Display Departure Time on Landing Page

Starting with update 19B, the Landing page is improved to display the information related to the start of a working day. New data is provided in the Activate route section of the Landing page and is available for the current day until the route is activated, showing when the resource must leave their start location to arrive to their first activity. 

Plugin Framework

Set Parameters for a Plug-In Button

Starting with 19B, you can pass parameters to the buttons associated with plug-ins. For example, you can open a specific screen whenever you click a button within a plug-in. You can also change the appearance, icon, of each button of a plug-in on the Landing page.

Reporting

Multi-Language Support for Reports

With update 19B, the multi-language capabilities for reports have been improved by considering the translatability aspect. The labels on the reports are easy to translate now.

Number of Active Users Report

With 19B, the Number of Active Users report shows the total number of users currently Active in the application. Also the test chart displayed on the number of active users report has been removed.

Routing

Work Skill Ratio for Immediate Routing of Multi-Day Activities

In 19B, the assignment of multi-day activities using Immediate Routing has been improved to consider Work Skill Ratio, where a Resource with a higher Work Skill ratio is assigned to work over another resource with a lower ratio.