Cloud Readiness / Oracle Field Service
What's New
Expand All


  1. Update 20D
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Administration
        1. Authenticate SAML and OpenID Login Policy Users Using Instance URL
    2. Android and iOS Applications
        1. Print from Installed Applications
        2. Request Location Permissions at Regular Intervals
    3. APIs
        1. Link a Segmentable Activity with a Segmentable Activity using REST APIs
    4. Capacity Management
        1. Configure Quota Page as Read-Only
    5. Collaboration
        1. Collaboration Redesign and Improvements
    6. Core Application
        1. Assignment Assistant Improvements
        2. Dispatch Console Improvements
        3. Open External Plug-Ins from the Main Menu
        4. Redesigned Messages Tab
        5. Use the Resource Tree on Manage, Calendar, and Map Pages
    7. Routing
        1. Automate Required Inventory Pickup Creation Using Bulk Routing
  4. IMPORTANT Actions and Considerations

Update 20D

Revision History

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
07 DEC 2020 Administration

Authenticate SAML and OpenID Login Policy Users Using Instance URL

Updated document. Revised feature information.
13 NOV 2020 Routing Automate Required Inventory Pickup Creation Using Bulk Routing

Updated document. Revised feature information.

06 NOV 2020 Routing

Automate Required Inventory Pickup Creation Using Bulk Routing

Updated document. Revised feature information.

23 OCT 2020     Created initial document.

Overview

This guide outlines the information you need to know about new and improved functionality in Oracle Field Service Update 20D. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you. For a listing of browsers supported by Oracle Field Service, log in to our support site and access Answer ID 8415.

Oracle Field Service Best Practices Guide: Please be sure to download our Oracle Field Service Best Practices Guide found on the Oracle Service Cloud Support Portal Answer ID 8215 (requires a login). This book contains many helpful hints and suggestions to help you improve and get the full benefit from your Oracle Field Service subscription.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at https://documentation.custhelp.com/ci/documents/detail/5/4/12.

Feature Summary

Column Definitions:

Features Delivered Enabled

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Features Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Action is Needed BEFORE Use by End Users
(Features Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Administration

Authenticate SAML and OpenID Login Policy Users Using Instance URL

Android and iOS Applications

Print from Installed Applications

Request Location Permissions at Regular Intervals

APIs

Link a Segmentable Activity with a Segmentable Activity using REST APIs

Capacity Management

Configure Quota Page as Read-Only

Collaboration

Collaboration Redesign and Improvements

Core Application

Assignment Assistant Improvements

Dispatch Console Improvements

Open External Plug-Ins from the Main Menu

Redesigned Messages Tab

Use the Resource Tree on Manage, Calendar, and Map Pages

Routing

Automate Required Inventory Pickup Creation Using Bulk Routing

>>Click for IMPORTANT Actions and Considerations

Administration

Authenticate SAML and OpenID Login Policy Users Using Instance URL

Earlier, you could log in to the instance using SAML and OpenID Connect authentication through just login.etadirect.com. Starting with Update 20D, it is recommended that you update the URL used to log in to the instances connecting over external identity providers, through SAML and OpenID Connect types of authentication. The URL must be the instance URL instead of login.etadirect.com. You must change the URL before Update 21D.

Add a Login Policy

  1. Click Configuration, Login Policies.
  2. Click Add new. The Add Policy dialog box appears.
  3. Complete these fields:

Field

Description

Label

A unique identifier label. For SAML login policy, enter only alphabets, numbers, and underscores ( _ ).

Policy name

A name assigned to this policy. Enter the name in English and in all the languages that are active in the application.

Authenticate using

The type of authentication method used for this login policy.

These fields are displayed for the SAML authentication method:

Specify SAML IdP

The way in which you want to select the SAML identity provider. The options are:

  • Upload metadata XML
  • Specify metadata URL
  • Oracle IDCS
  • Manual populate

IdP Metadata XML

This field is displayed if you select Upload metadata XML in the Specify SAML IdP field. Click Upload to upload the XML file that contains the metadata details for the identity provider. If the uploaded file is incomplete, or does not contain the details in the proper format, the message, Cannot download metadata from the specified XML: XML parser error is displayed. Contact your Identity Service Provider to get this metadata XML. Ensure that the XML includes or conforms to this information:

  • Metadata XML must be in accordance with SAML 2.0 specifications.
  • The file contains "SAML Issuer" (parameter "entityID" of the node "EntityDescriptor").
  • The file provides identity provider certificate (nodes "md:EntityDescriptor/md:IDPSSODescriptor/KeyDescriptor/KeyInfo/X509Data/X509Certificate/").

IdP Metadata URL

This field is displayed if you select Specify metadata URL in the Specify SAML IdP field. Type the URL from which you want to take the SAML metadata details for the identity provider. If the URL is unresolved, the message, "Cannot download metadata from the specified URL: no route to host" is displayed.

IDCS Metadata XML

This field is displayed if you select Oracle IDCS in the Specify SAML IdP field. Click Upload to upload the XML file that contains the metadata details for Oracle IDCS. Contact your implementation consultant for more details on Oracle IDCS.

OFS Metadata XML

The link to download the Oracle Field Service metadata XML. You must pair your identity provider with Oracle Field Service. Use the downloaded XML file to register Oracle Field Service with your identity provider.

Max sessions

The maximum number of simultaneous sessions allowed to the user.

SAML issuer

Used to identify asserts from Identity provider (IdP). It can be any string provided by IdP, not only URL. It is used for IdP and Service provider (SP) initiated connections.

SAML identity provider certificate

IdP public key used to sign requests.

SAML identity provider login URL

IdP URL to redirect to for login. It is needed only for SP initiated logins.

SAML identity provider logout URL

IdP URL to redirect to for logout. It is needed only for SP initiated logins.

SAML attribute containing username

The SAML assertion attribute name where IdP must store the user name (login name for Oracle Field Service). Example:

[saml:Attribute Name="uid" NameFormat="urn:oasis:names:tc:SAML:2.0:attrnameformat:basic"][saml:AttributeValue xsi:type="xs:string"]dispatcher[/saml:AttributeValue][/saml:Attribute]

If it is empty then Oracle Field Service gets the user name from the Name Identifier element of Subject statement. Example: 

[saml:Subject][saml:NameIDSPNameQualifier="https://sp.com/sp/module.php/ saml/sp/metadata.php/ default-sp"Format="urn:oasis:names:tc:SAML:2.0:nameidformat:persistent"]dispatcher[/saml:NameID][/saml:Subject]

Generate metadata using instance URL

The URL to log in is constructed using the instance URL. This is the recommended way and is the default option for all new SAML Login Policies. The URL displayed in the screenshot that is given after this procedure is just an example. The URL for your organization is based on your instance name and is displayed under this field in the application.

Generate metadata using login.etadirect.com

The URL to log in is login.etadirect.com. This is the non-recommended way and the option selected for existing SAML Login Policies.

These fields are displayed for the Open ID Connect authentication method:

Max sessions

The maximum number of simultaneous sessions allowed to the user.

Configuration login URL

The Identity Provider URL to start authentication.

Logout URL

URL to which the user is redirected after logout. It may be the URL for logout from the Identity Provider.

Attribute containing username

The name of the OpenId attribute where the Identity Provider must store the user's name (login name for Oracle Field Service). Example: email.

Client ID

The value of the field containing data from registered OpenID provider (for example, Client ID).

Client secret

The value of the field containing data from registered OpenID provider (for example, Client Secret).

OFS link back URL

Use instance URL for redirect to OFS

The URL is constructed using the instance URL. This is the recommended way and is the default option for all new OpenID Connect Login Policies. The URL displayed in the screenshot that is given after this procedure is just an example. The URL for your organization is based on your instance name and is displayed under this field in the application.

Use login.etadirect.com for redirect to OFS

The URL is login.etadirect.com. This is the non-recommended way and the option selected for existing OpenID Connect Login Policies.

  1. In your OpenID application, configure a link back URL. Use the URL displayed on this dialog box for the option that you have selected. Your Identity Provider uses this link to redirect users to Oracle Field Service upon successful login.
  2. Click Add. The application generates the metadata based on the options you have selected. Use this metadata to link your identity provider with the instance. Note down the instance URL that you must use when setting up an external identity provider.

This screenshot shows the OFS metadata section for a Login Policy with the SAML authentication method:

OFS Metadata Section for a Login Policy with SAML Authentication Method

OFS Metadata Section for a Login Policy with SAML Authentication Method

This screenshot shows the OFS link back URL section for a Login Policy with OpenID Connect authentication method:

OFS Link Back URL Section for a Login Policy with OpenID Connect Authentication Method

OFS Link Back URL Section for a Login Policy with OpenID Connect Authentication Method

The benefits of this feature are:

  • Decreased time of authentication: Logging through the instance URL guarantees that the authentication requests always hit a data-center where the instance is available and working. With this kind of access there is no need for proxy requests through login.etadirect.com and the redirection caused by it.
  • Continuous VPN connection to the instance: If you use a VPN connection, you can choose this feature to point your identity providers to the required data centers.
  • Compliance with government and corporate policy regulations: Authentication requests are always preserved only in your geographical region.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Android and iOS Applications

Print from Installed Applications

Starting Update 20D, you can now print files from within the installed application. All screens within the application that supports printing like Reports within Dashboards and the Print Route functionality are supported in the installed apps.

Print Functionality

The user can now click Print to access the device's native print functionality and print the file.

This screenshot shows the native print option of a device.

To print any screen, tap Print. A preview of the printed information appears. Tap Print to open the native Print functionality and complete printing.

Print with Custom Plugins

The users can use the openLink procedure of Plugin API to print files from within custom plugins. This procedure will open the link in the default system browser from where users can use the browser's print functionality to print the document.

The installed application allows you to print files using the standard Print dialog box.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Request Location Permissions at Regular Intervals

The installed application need location permissions to access the location of the field resource to provide accurate location based alerts and duration estimations. If the field resource did not provide the location permissions previously, a prompt message to provide the required permissions appears when the user tries to activate the route.

If the 'Disable route activation when geolocation is not enabled on device' check box is disabled or, if the location services (GPS) is already turned ON but the field resource did not provide the location permissions, the application prompts the user to provide appropriate permissions. A prompt message displays the steps to provide location permissions. Click Open Settings to display the app settings screen where users can provide location permissions.

This screenshot shows the message with the Open Settings button.

If the 'Disable route activation when geolocation is not enabled on device' is checked, the app identifies that the location services (GPS) are not turned ON and location permissions are not provided, the prompt message displays what needs to be done - notifies that the user has to  provide location permissions and turn on location services. In such cases, users cannot Activate the route unless the location permissions are provided and the location services are turned ON.

This screenshot shows the message when a user tries to activitate a route and the location service is not enabled.

If the 'Disable route activation when geolocation is not enabled on device' is unchecked, the user is not prevented from activating the route.

This screenshot shows the message when 'Disable route activation when geolocation is not enabled on device' is not selected.

The installed application needs location permissions to access the location of the field resource to provide accurate location based alerts and duration estimations.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

APIs

Link a Segmentable Activity with a Segmentable Activity using REST APIs

Starting with Update 20D, you can use the REST APIs to link a segmentable activity with another segmentable activity using the same link types that you use to link a regular activity with a segmentable activity.

This includes updates to the following Core API functions:

  • Create an activity link: POST /rest/ofscCore/v1/activities/{activityId}/linkedActivities
  • Replace an activity link: PUT /rest/ofscCore/v1/activities/{activityId}/linkedActivities/{linkedActivityId}/linkTypes/{linkType}

To route a linked segmentable activity:

  • Run the multiday routing plan where the segmentable activities fit the filters.
  • Set a Bulk routing plan running for a scheduled time to cover all the linked segmentable activities that you want to route.

NOTE: Only Bulk routing supports routing linked segmentable activities. Immediate routing ignores all segmentable activities that have links.

Supported Link Types and Constraints

Here are the link types and constraints that are supported for the links between segmentable activities:

  • Simultaneous (Segmentable and Segmentable activities): No constraints available
  • Segmentable activity Finish to Segmentable activity Start:
    • Same Day: Earliest (as of calendar means) segment of a latter activity must start the same day as the latest (as of calendar means) segment of the former activity finishes
    • Same Provider: All segments of the latter activity must be done by the same resource(s) that participated in any segment of the former activity.
    • Different Providers: All segments of the latter activity must be done by different resource(s) than those that participated in any segment of the former activity.
  • Segmentable activity Start to Segmentable activity Start:
    • Different Providers: All segments of the latter activity must be done by different resource(s) than those that participated in any segment of the former activity.
    • If you try to add an unsupported activity link type and/or a constraint, a warning is displayed and no link is added.
  • For Segmentable Activity Start linked to Regular Activity Start (or the reverse):
    • Different Providers: All segments of the latter activity must be done by different resource(s) than those that participated in any segment of the former activity.

REST APIs can now be used to link a segmentable activity with another segmentable activity.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Capacity Management

Configure Quota Page as Read-Only

Earlier, you could configure the visibility to the Quota page menu items such as Booking status, Quota, and Available capacity only in Legacy Manage. Starting with Update 20D, you can configure read-only or read-write access to each user type for the Booking status, Quota, and Available capacity pages in Core Application.

NOTE: The visibility level of the Main menu item does not control the access level for the Booking status, Quota, and Available capacity pages anymore. You must configure the visibility levels for each of these pages separately.

All the existing configurations will be migrated to maintain the previously-granted access level, so that the access level of each User Type to Quota page is the same after you upgrade to Update 20D.

Configure the Visibility for Booking Status, Quota, and Available Capacity Pages

  1. Click Configuration, User Types.
  2. Click the user type for which you want to add or modify the visibility for the Quota pages.
  3. Click Screen configuration.
  4. Expand Application screens and click Quota. Booking status, Quota, and Available capacity are displayed in the Buttons section. This screenshot shows the Booking status, Quota, and Available capacity buttons on the Quota context layout structure:

Booking Status, Quota, and Available Capacity Buttons on the Quota Context Layout Structure

  1. Click an item of your choice. Click Modify in the visibility table.
  2. Click the access mode of your choice and then click Save.

You can now configure read-only or read-write access to each user type for the Booking status, Quota, and Available capacity pages in Core Application.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Backward Compatibility

The visibility level of the Main menu item does not control the access level of the page after this Update. Instead, users must configure the visibility levels for the screen layout.

All existing configurations will be migrated to maintain the previously-granted access level, so that the access level of each User Type to Quota screen will be the same after the upgrade.

Key Resources

Collaboration

Collaboration Redesign and Improvements

Earlier, Collaboration opened as a new window. Starting with Update 20D, these improvements are available:

  • You can attach the Collaboration window to your working page and view it in full-screen mode. All the message notifications are available on this page, so you don’t have to leave the page.
  • If you are working with multiple monitors, you can open the Collaboration window in one monitor and the remaining Oracle Field Service pages in another monitor. You can also view the count of unread chats in the monitor were you have closed the Collaboration window.
  • You can resize the Collaboration window by selecting the drag option highlighted in the image. Drag it to the left side of the monitor to increase the width. You can also use the Expand to full screen button to see the Collaboration window in full-screen mode. You can resize the window to a maximum of 60% of the screen size. However, the Collaboration window is always displayed in full-screen mode in small devices, regardless of whether the screen is Portrait or auto-rotate mode.
  • The Collaboration window appears as a dual-pane with the left pane showing the list of the active chats, helpdesk chats (for a helpdesk operator), and history chats. The right pane shows the details of the selected chat.
  • You can use "X " to close the Collaboration window.
  • The chats and helpdesk tabs show the number of unread chats as badges on the corresponding tabs.
  • You can start a new conversation by clicking the start chat icon. You can initiate a one-to-one conversation by selecting a contact from the contact list, a Group message by selecting a group of users, or a new conversation with nearby users by selecting the Who’s Nearby option.
  • When there are no active chats in the Collaboration or Helpdesk chats, you can see the Start new conversation option by default. The remaining chat options are available as menu items.
  • You can add a user to an active chat by clicking the  icon.
  • You can start a video call directly from the Collaboration window by clicking the Start Video Call icon from the active Collaboration window.

NOTE: You must have a subscription to Oracle Field Service Enterprise edition to use the video call feature.

  • If you are a helpdesk operator, you can select the helpdesk chats from the Helpdesk tab within the Collaboration window. There is no separate Collaboration icon for the helpdesk chat.
  • Helpdesk operators can use the transfer chat icon to transfer a chat. Helpdesk operators can monitor the chats that are in progress, using the Chats in process option within the Helpdesk tab.
  • The size of chat bubbles change dynamically, based on your device size and the size of the message.

This screenshot shows the Collaboration window on a working page:

Collaboration window on a working page

Collaboration Window on a Working Page

Legends:

1: The Expand to Full Screen button with which you can view the Collaboration window in full-screen mode.

2: The Invite user icon with which you can invite a user to a conference.

3: The Drag option with which you can resize the Collaboration window.

4: The New conversation icon with which you can start a new conversation.

This screenshot shows the Collaboration window in full-screen mode:

Collaboration window in full-screen mode

Collaboration Window in Full-Screen Mode

This screenshot shows the New conversation option:

New conversation option on the Collaboration window

New Conversation Option on the Collaboration Window

This screenshot shows the new Group Message option:

New Group Message option on the Collaboration window

New Group Message Option on the Collaboration Window

This screenshot shows the Helpdesk chat pane and the transfer chat icon highlighted:

Helpdesk chat pane and the transfer chat icon highlighted

This screenshot shows the Options menu:

Options menu

Options Menu

This screenshot shows the Collaboration window in portrait mode on a small screen device:

Collaboration window in portrait mode on a small screen device

Collaboration Window in Portrait Mode on a Small Screen Device

This screenshot shows the Collaboration window in landscape mode on a small screen device:

Collaboration window in landscape mode on a small screen device

Collaboration Window in Landscape Mode on a Small Screen Device

Configure the following settings to use the video call feature:

  1. At the time of implementation, opt for the Field Collaboration with Video Call service in Oracle Field Service.
  2. Click Configuration, User Types, General and select Allow video call in the Collaboration section. This enables the video call option for the selected user types.
  3. Ensure that the browser you use supports WebRTC.
  4. Ensure that your browser has the permission to access your camera and microphone. The Start Video Call icon is visible only when the receiver is online.

Here are a few business benefits:

  • Collaboration Chats and Helpdesk are combined in unified single view allowing users to see and manage engagements with fewer clicks ensuring conversations are not missed.
  • The Collaboration screen is attached to the working screen allowing improved navigation between Collaboration and other screens in Core Application with fewer clicks.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Core Application

Assignment Assistant Improvements

Earlier, the Main screen of Assignment Assistant provided the overall impact of moving an activity to a route. Starting with Update 20D, the Assignment Assistant includes these improvements:

Hint for Route Impact 

You can now see the duration of the activity being moved and the extra travel time required for the activity on the hint in the Route impact column. Click the column to see the hint.

This screenshot shows the main page of the Assignment Assistant with the History, time scale, and route impact highlighted:

Assignment Assistant with History, time scale, and Route impact highlighted

Assignment Assistant with History, Time Scale, and Route Impact Highlighted

History Page

If you have moved at least one activity in the current session, you can see the History page. Use the History page as a quick access page to assign activities to the same resource several times. The page contains a list of technicians and buckets, and is sorted by the time of move, with the last moved activity on the top. For each resource you can see the route impact, activity date, and the number of activities moved. You may see some resources listed multiple times. For example, let’s say you have moved activities to a resource twice, for different dates. Then, the resource is listed twice.

Assign an activity from the History page:

  1. From the list of resources, determine the resource and the date for which you want to assign.
  2. Click Assign. The number of activities moved to the resource for the selected date changes. If there are warnings to move the activity to a resource, the date is displayed in red.
  3. To review the route details of the resource, click the details icon.

This screenshot shows the History page:

Assignment Assistant History page

Time Scale

You can see the start time of the activity in the time scale. This gives you a better idea of not only the position of the activity in the route, but the activity start time as well.

Non-Movable Section

You see the Non-movable section on the Route details page, when you cannot assign an activity to the current resource. For example, let’s say you try to drag-and-drop an activity to a resource that is set as 'Forbidden' for the activity. The activity is then displayed in the Non-movable section and you cannot drag it to other sections as well.

This screenshot shows the Non-movable section on the Route details page:

Non-movable section on the Route details page

The Assignment Assistant is now available with improved functionality.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Dispatch Console Improvements

Earlier, there were two context layouts for printing a resource’s route. Further, the print layout generated by the application was not user-friendly. Starting with Update 20D, these improvements are made in the Dispatch Console:

One Context Layout for Printing Routes

There were two context layouts under the Application screens section on the Screen configuration page  'Activity fields for print' and 'Print Route'. The 'Activity fields for print' layout is removed and the 'Print Route' context layout is used to configure fields for the Print Route functionality. Further, there were a set of nine fields that were always included on the Print Route screen - Start, Type, Work Order, Service Window, Account Number, Name, Address, ZIP/Postal Code and Phone. These fields are no longer included by default. You must configure the fields to be displayed on the Print Route page, using the 'Print Route' context layout.

NOTE: The application can print a maximum of 1000 activities at a time using the Print Route function. If there are more than 1000 activities, only the first 1000 activities are displayed with a note.

All the configured fields for the selected resource or bucket are displayed and printed in this layout. In addition to the configured fields, the list of inventory in the Resource pool is displayed at the bottom.

This screenshot shows the activity details printed using the Print Route option:

Activity details printed using the Print Route option

This screenshot shows the inventory details printed at the end of the report:

Inventory details printed at the end of the report

Migration

If you have configured the Print Route layout for a user type, the nine fields that were displayed by default will now be displayed in the context layout. You will not see any change in the set of fields that are displayed. If you had configured any additional fields those will also be present in the context layout.

Configure the Fields for Print Route

  1. Click Configuration, User Types.
  2. Click the user type for which you want to configure Print Route.
  3. Click Screen configuration.
  4. Expand Application screens and click Print Route under Main menu, Activity list.
  5. Click ‘Click to Add’ and then select the required fields. You can select all the activity related fields, including custom fields.
  6. Click OK.
  7. For all the fields, click Add new visibility and then click Save.

Multiple Action Sections and Buttons in the Header

If you had configured any Actions and Groups of Actions separately under the 'List view columns' context layout, they now appear as separate actions or groups in the Dispatch Console header, if there is enough space.

This screenshot shows the actions and group of actions configured for the List view:

Actions and group of actions configured for the List view

This screenshot shows the multiple actions and group of actions configured on the Dispatch Console:

Multiple actions and group of actions configured on the Dispatch Console

As earlier, in smaller screens the Actions appear in the options menu in the top right corner based on the available space.

This screenshot shows the multiple actions and group of actions on a small screen:

Multiple actions and group of actions on a small screen

Add Child Resource Based on Core Application

When you clicked 'Add Child Resource' action from the Actions menu or the resource hint in the Dispatch Console, the screen displayed was based on the context layout from Legacy Manage. 'Add Child Resource' now displays based on the context layout of Core Application.

This screenshot shows the Add Child Resource option from the Actions menu and the resource hint:

Add Child Resource option from the Actions menu and the resource hint

This screenshot shows the Add Child Resource page based on the context layout of Core Application:

Add Child Resource page based on the context layout of Core Application

The Dispatch Console is now available with improved functionality.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Open External Plug-Ins from the Main Menu

Earlier, you could add only the plug-ins that use the Plugin API to the Main menu in Core Application. Starting with Update 20D, you can add external plug-ins to the Main menu.

NOTE: You cannot add the plug-ins that have the option "Only for Legacy Manage main menu" selected. And, you cannot add native application plug-ins either.

Follow this procedure to add an external plug-in to the Main menu:

  1. Configure a plug-in to add to the Main menu.
  2. Add the plug-in to the Main menu context layout structure.

Configure a Plug-In to Add to the Main Menu

  1. Click Configuration > Forms & Plugins.
  2. Click Add Plugin.
  3. Complete these fields on the Add Plugin page:
Field Name Description

General Information section

Name (English)

A mandatory field defining the plug-in name in the English language. The action or plug-in appears under this name in the actual context.

Name (other languages)

Plug-in name translations to other languages, if used.

Label

A mandatory field defining a unique action or plug-in label.

Entity

Entity (activity, inventory, required inventory, resource, service request, user) to which the action or plug-in is to be related. For example, if you select Inventory, the action will appear only in the contexts related to inventory. Leave the field blank for the action to be available in all contexts of all the entities.

Visibility rules similar to

The base action from which the plug-in is to be derived, if needed. When a base action is selected, the resulting plug-in functions per the same rules as the base action. The base action affects only the visibility of buttons and not the functioning of the plug-in. It appears only in the contexts in which the base action appears and is shown or hidden according to the same visibility conditions. For example, if start_activity is selected as the base action for a plug-in, the plug-in is only be shown in the context of a pending activity when there is no started activity in the same route, similar to the Start action. The list of available base actions is filtered according to the Entity that is selected.

Type

The type of plug-in you want to use. Select HTML5 application.

This means, the plug-in uses an external application to extend the functionality. The HTML5 plugin is a URL of an external resource that is opened in a new window or in an iframe.

Fields for the HTML 5 Application Option

Use Plug-in API

Determines whether you want the plug-in to communicate with Oracle Field Service using the Plug-in API. Clear this check box.

When you do not use the Plug-In API, the URL is opened in a new tab, window, or iframe. To interact with Oracle Field Service you must pass some data (such as activity id, resource name) to the plug-in using the placeholders in the "POST Data" and "URL" fields.

URL

The path to a URL (for external plug-ins). This URL executes the HTML5 application and it executes the plug-in in the entire browser window. The URL must start with the protocol (https). The URL must point to an external resource, which is opened either in a new window or inside Oracle Field Service in an iframe (if the “Tab or iframe layout” option is selected).

POST Data

The data that you want to be sent to the external plug-in. You can use only User entity fields as placeholders.

Disable plug-in in offline

Determines whether you want to disable the plug-in when Oracle Field Service is offline. Clear this check box for the plug-in to work in offline mode with Oracle Field Service Mobility Cloud Service.

Only for Legacy Manage Main menu

Determines whether the plug-in can be set as a Main menu item through the Main menu context layout. Clear this check box.

Open in iframe

Determines whether the plug-in uses the iframe layout. If you clear the field, the plug-in’s URL is opened in a new browser tab or window.

Show scrollbars

Determines whether the window in which the plug-in runs has scroll bars. This setting is applicable to the Legacy Manage application.

Width in pixels/ Height in pixels

The width and height of the plug-in window in pixels. This setting is applicable to the Legacy Manage application.

  1. Click Save.

This screenshot shows the Add plugin page where you configure a plug-in to display on the Main menu:

Configure a plug-in on the Add plugin page

Configure a Plug-In on the Add Plugin Page

List of Available Placeholders for URL/POST Data for Main Menu Plug-Ins

Placeholder User Property
allow_desktop_notifications Popup Notification
allow_vibration Vibration
design_theme Design Theme
main_resource_id Main Resource
mobile_activity_count Mobile Activity Count
mobile_inventory_count Mobile Inventory Count
mobile_provider_count Mobile Resource Count
sudate_fid Date Format
sulong_date_fid Long Date Format
sustatus Status
sutime_fid Time Format
su_zid Time Zone
uid User ID
ulanguage Language
ulogin Login
uname User
uname User Name
user_type_id User Type

Some of these properties are available only if you add them to an application screen, either directly or through a button for any Form for which you have configured these fields as available.

Add the Plug-In to the Main Menu Context Layout Structure

  1. Click Configuration > User Types.
  2. Select the type of user for which you want to add the plug-in.
  3. Click Screen configuration.
  4. Expand Application screens and click Main menu.
  5. Select an existing button and click Add button.
  6. On the Add button dialog box, click Plugins.
  7. Select the plug-in that you want to add and click OK. This screenshot shows the Add button dialog box:

Add button dialog box to select a plug-in to add to the Main menu

Add Button Dialog Box to Select a Plug-In to Add to the Main Menu

  1. Click Add new visibility, and then click Save.
  2. Follow these steps, if you want to pass any parameters to the plug-in:
    1. Click Add new in the Parameters section.
    2. Enter a name for the parameter in the Name field. For example, enter defaultScreen to define a page as the default page in the plug-in. The maximum length of the name that you can enter is 248 characters.
    3. Enter a value for the parameter. For example, enter part_order to display the Part order page as the default page in the plug-in. The maximum length of the value that you can enter is 4000 characters.
    4. Click Save.
    5. Repeat the procedure for all the parameters that you want to configure. The total combined length of all parameter names and values must not exceed 5000 characters. These parameters are not encrypted when sent to the plug-in.
  3. Click Close or X. The plug-in is added to the Main menu. If you add an external plug-in as the first item in the Main menu, the menu item shows in the correct order. However, the plug-in does not open when the user logs in. Instead, a standard page or a plug-in that you have created using the Plugin API Framework that is next in the order is opened.
  4. Click the Main menu and confirm that the plug-in is available.

The benefit of this feature is that you can add external plug-ins to the Main menu in Core Application.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Redesigned Messages Tab

Earlier, the width of the columns on the Messages page was the same, regardless of the content. You had to zoom in to read the content. Starting with Update 20D, the column width adjusts automatically based on the content and the screen size.

This screenshot shows the redesigned Messages page:

Redesigned Messages page

Redesigned Messages Page

The option to resend messages that was available for everyone who had access to the Messages page is removed. You can resend a message using the 'Resend' option on the Messages Report. For all users who resend data, you must provide access to the Messages Report. You can search and select the required message from within the Messages Report and resend the message using the 'Resend' option.

This screenshot shows an individual message opened from the Messages page:

Individual message opened from the Messages page

Individual Message Opened from the Messages Page

The best practice is to configure the Messages Report within the Dashboard for all user types that would resend messages.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Use the Resource Tree on Manage, Calendar, and Map Pages

Earlier, you couldn’t see the hierarchy of resources and search for resources on the Calendars and Manage pages in Core Application. In addition, the steps you performed to manage groups in the Dispatch Console was different from those on the Calendars and Manage pages. Starting with Update 20D, you can perform these functions with the resource tree:

  • Access the hierarchical resource tree on the Manage, Calendars, and Map pages.
  • Go to any level of a resource’s hierarchy using the breadcrumbs in the resource hint.
  • Manage groups in the Dispatch Console and on Manage, Calendars, and Map pages the same way.
  • Use the date editor to select the date to view the Manage and Calendars pages.
  • View the Resource info page for the users with the Manager/Dispatcher/Admin role.
  • See the style of avatars and badges in Redwood theme.
  • See the style of tiles and icons on the Resource info page in Redwood theme.

Access the Hierarchical Resource Tree on the Manage, Calendars, and Map Pages

You can navigate from a parent to child resource and a child to parent resource, and select the required resource to see the activities or schedules.

  • To go to a child resource of an Organization Unit, a Bucket, or a Group, click the arrow in front of the resource.
  • To go to a parent resource, click the arrow before a resource (one level up). Or, click the 'organization' icon to jump to the root level in the resource tree.
  • To open resources on the Time, Calendar, or Map view, click a resource. The resource’s child resources are displayed on the right. The selected resource is highlighted with bold font in the resource tree.
  • To open a resource hint, click the avatar.
  • To find a required resource in the resource tree, enter the name in the Search field.
  • To hide the resource tree, click X next to the Search field. To show the resource tree, click Manage and then click the pin icon.
  • To go to a different level of hierarchy of the resource tree, open the resource hint and use the breadcrumbs.

This screenshot shows the resource tree for the Florida bucket expanded:

Resource tree for the Florida bucket expanded

This screenshot shows the Manage page where the resource tree hidden:

Resource tree hidden

Resource Tree Hidden on the Manage Page

This screenshot shows the unpinned resource tree:

Unpinned resource tree

Unpinned Resource Tree

This screenshot shows the Search option for the resource tree:

Search option for the resource tree

Search Option for the Resource Tree

This screenshot shows the resource hint with breadcrumbs and the outline of the star icon, which indicates that the resource has not been added to a favorite group:

Resource hint with breadcrumbs

Resource Hint with Breadcrumbs

Use the Date Editor to Select the Date to View the Manage and Calendars Pages

You can use the date editor and select a date to view the Manage and Calendars page.

Manage Groups on Manage, Calendars, and Map Pages

Whether you are in the Dispatch Console, or the Manage, Calendars, or Map page, the way you work with favorite groups is the same. You can create a Favorite group. You can edit the group, add and remove resources to it, and modify the Favorite group.

Create a Favorite Group

  1. Determine the resource that you want to be in the new group.
  2. Open the resource hint.
  3. Click the star icon.
  4. Select New group and enter the name of the group. When you add a resource to a group, the star icon on the resource hint is filled.

NOTE: You can add Org Units, Buckets, or individual resources to the group. When adding an Org Unit or a Bucket, note that the OrgUnit/Buckets is a dynamic entity. This means that the child resources within this group may change over time, and these changes show in your group content. Therefore, if you want to have specific resources in your managed group, assign those resources individually. Selecting a group resource automatically selects all the resources it contains.

Add a Resource to an Existing Favorite Group

  1. Determine the resource that you want to be in a group.
  2. Open the resource hint.
  3. Click the star icon.
  4. Select the desired group and click or tap Save. The resource is added to the selected group and the star icon is filled. This screenshot shows the Favorite Groups dialog box:

Favorite Groups dialog box

Remove a Resource from a Favorite Group

  1. Determine the resource that you want to remove from a group.
  2. Open the resource hint.
  3. Click the star icon.
  4. In the Favorite Groups dialog box, clear the checkbox for the group from which you want to remove the resource.
  5. Click or tap Submit. If you remove the resource from all the favorite groups, you can see only the outline of the star icon.

Edit a Favorite Group

Follow these steps to rename a group, change resources in the group, or add a filter:

  1. To rename a group:
    1. Click the star icon next to the group name.
    2. Click Edit group.
    3. Change the name in the Group name field.
    4. Click or tap Submit. This screenshot shows the Edit group and Remove group options:

Remove or edit a favorite group

Remove or Edit a Favorite Group

  1. To remove a favorite group:
    1. Click the star icon next to the group name.
    2. Click Remove group.
    3. Click or tap Submit on the confirmation dialog box.
  2. Select a filter that applies to the group.
    1. Ensure that your administrator has created a filter for the resource entity and selected the List/Time/Map/Daily checkbox. This filter is used when displaying the members of the group on the Manage screen.
    2. Select the desired checkboxes to add or remove resources to the group.
    3. Click or tap Submit to save your changes.

View the Resource Info Page for the Users with the Manager/Dispatcher/Admin Role

The users with Manager/Dispatchers/Admin role can now view the Resource info page. You can see the details on the Information tile and all the resources you manage on the Resources tile. Work zones, Work skills, Locations, Inventory, and Resource history are not available for this role.

This screenshot shows the Resource info page for the users with the Manager/Dispatcher/Admin role:

Resource info page for the users with the Manager/Dispatcher/Admin role

Avatars and Badges

The resources avatars are now displayed with a square shape for all the themes. Redwood theme shows avatars and on-call badges with Redwood colors and structure.

This screenshot shows avatars and badges in Redwood theme:

Avatars and badges in Redwood theme

Resource Info in Redwood Theme

The Resource Info page is now displayed in Redwood theme.

This screenshot shows the Resource Info page in Redwood theme:

Resource Info page in Redwood theme

The benefits of this feature are:

  • Searching for resources in Core Application
  • Managing resource calendars in Core Application

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Routing

Automate Required Inventory Pickup Creation Using Bulk Routing

Starting update 20D, when an activity has required inventory and the resource assigned to this activity does not have that required inventory in their resource pool, Routing can automatically create a Warehouse Visit activity. The Warehouse Visit activity is scheduled prior to the customer activity so that the resource can pick up the necessary inventory before traveling to the job site.

Each Warehouse Visit activity includes a list of all the required inventory that needs to be picked up, including that for other jobs on the resource’s route if necessary. The required inventory that needs to be picked up is listed in the Customer pool on the Warehouse Visit activity’s Inventory screen.  When the Warehouse Visit activity is created, the required inventory to be picked up is reserved/booked within the warehouse resource pool so that OFS won’t commit that inventory to other activities.

Additionally, Routing optimization runs can automatically update Warehouse Visit activities throughout the day, as activities are added, removed, and reassigned. This might include adding or removing Warehouse Visits as well as updating the required inventory list for each Warehouse Visit activity.

You can use the required inventory pickup option with routing plans that are run manually, sequentially, recurrently, or once a day. After the plan is run, you’ll see Warehouse Visit activities created in resource routes. Here’s the logic OFS uses to route these activities:

  • To optimize routing, OFS will create the activities to book inventory from the nearest warehouse containing the required inventory. ‘Booked’ inventory refers to required inventory that is already committed to be picked up. 
  • If possible, inventory pickup for multiple activities will be combined in one Warehouse Visit. 
  • If it’s necessary to visit more than one warehouse to gather all of the required inventory for an activity, Routing will schedule multiple visits. 
  • For multi-day routing plans, activity pickups will be created separately for each day.

This feature includes the following enhancements to OFS:

  • A new setting to support required inventory pickup in the Assignment Parameters section of a routing plan.
  • A new activity type group and a pre-defined activity type for Warehouse Visits.
  • The automatic creation of a Warehouse Visit activity when a resource does not possess one or more pieces of inventory required for the activities on the route.

The benefits of this feature include increased autorouting performance and improved route quality and efficiency.

Watch a Demo

The benefits of this feature are:

  • Increased autorouted percentage value.
  • Improved routing quality as the same technician completes more activities.

Steps to Enable

Follow these steps to utilize inventory pickup functionality:

  • Review Warehouse Visit activity type and modify if necessary or create a new activity type
  • Add a warehouse resource type
  • Create and configure a warehouse resource
  • Fill warehouse resource with inventory
  • Update the inventory identifier screen configuration
  • Add resource filter for use in routing plans
  • Configure routing plan
  • Plan for recurrent optimization (recommended)

REVIEW WAREHOUSE VISIT ACTIVITY TYPE

The 20D version of OFS automatically includes a Warehouse Visits activity type group, and the default Warehouse Visit activity type is included for your convenience. If the default activity type meets your organization’s needs, you don’t have to do anything else regarding this step.

If it doesn’t meet your needs, you can edit it by defining the default duration, selecting time slots, and disabling any of the selected features (except for “Support of Inventory” and “Support of not-ordered activities,” which are enabled by default). Notice that pending Warehouse Visit activities use purple color-coding to help identify them on the Manage view and Dispatch Console.

If you want to create a new warehouse activity, you must select Warehouse Visits for the activity group. The Warehouse Visits activity group automatically limits the available features for any activity type created within that group. For example, “Support of inventory” is selected by default. Other constraints include the inability to select the activity to be mass or repeating activities, to move or reschedule activities of this type, and to support work skills or work zones. Additional limitations exist, and the Features list is specifically configured to enable only the allowable features for activity types in this activity group.

ADD A WAREHOUSE RESOURCE TYPE

Add a warehouse resource type that uses the Bucket resource role. Be sure that it’s active. The “Routing can assign activities” and “Used for quota management” features can be enabled at your discretion.

CREATE AND CONFIGURE A WAREHOUSE RESOURCE

Decide whether the warehouse routing resource should be a child of the bucket that contains the activities to be routed. Another option is to locate it outside the routing bucket’s hierarchy. If you choose this option, the following conditions must be met before Routing can create an automatic pickup activity for required inventory:

  • The warehouse resource must have at least one of the same work zones as the routing bucket.
  • The Filters section of the routing plan must have “Use resources outside the routing bucket” enabled.
  • The activity’s work zone must match the warehouse’s work zone.

Now, you’ll create a warehouse resource. For Resource Type, select the one you just created. And for Org Unit/Bucket, select either the routing bucket or the entity where you want to warehouse to reside in the resource tree.

You must add a Start location for the warehouse resource, which is simply its address, and that you set that Start location for each day of the week the warehouse is open. You must also ensure that the warehouse resource’s calendar is set for the days of the week and hours of the day when field resources can pick up required inventory. Routing can create Warehouse Visit activities only if the warehouse resource has both location and calendar information specified.

FILL WAREHOUSE RESOURCE WITH INVENTORY

You can create inventory for the warehouse resource via API (see the Integration section under Additional Information), or you can do so manually by selecting Resource Inventory on the Resource Info screen for the warehouse resource, selecting Add to Resource, and adding inventory items.

UPDATE THE INVENTORY IDENTIFIER SCREEN CONFIGURATION

This step updates the “Identify equipment by” identifier screen configuration to display the Booked Quantity value for each inventory item. The regular Quantity value does not change when the Warehouse Visit activity is created, although OFS does note that the required inventory is booked. And OFS knows that the remaining available inventory is the total quantity minus the booked quantity. Adding this step simply lets you see what’s been booked.

To do this, under the Collaboration and Identifiers section of the user type screen configuration, open the “Identify equipment by” screen context and add the Booked Quantity property. If no required inventory has been booked, this value will not appear in the equipment list.

ADD RESOURCE FILTER FOR USE IN ROUTING PLANS

Routing needs to be able to identify warehouse resources, so the next step is to create a resource filter that uses the condition “Resource Type (ptype) In Warehouse.” (Creating a custom property to distinguish a warehouse resource type from other resource types is also an option.)

CONFIGURE ROUTING PLAN

You can configure the automatic creation of Warehouse Visits to pick up required inventory for any type of routing plan.

The first thing you need to do is modify the Assignment Parameters section by selecting Enable Routing by Inventory. Then select Enable Inventory Pickup and select the Warehouse Visit activity type from the “Inventory pickup activity type” drop-down menu.

Next, you’ll make some changes to the Filters section of the routing plan. Select one of the activity filters, select Resources, and then select the Warehouse resource and set its priority to “Treat as warehouse.” (This step needs to be done for only one filter within the routing plan, regardless of the total number of filters being used.)

PLAN FOR RECURRENT OPTIMIZATION

Throughout the day, if activities get added, canceled, or deleted, it may affect the booked and available quantities of inventory at the warehouse.

Here’s what happens in those circumstances:

  • If the activity requiring inventory is deleted or canceled before inventory pickup, the inventory in the Warehouse Visit activity is not changed, but a warning appears to let the technician know that inventory needs have been changed. It is possible that the Warehouse Visit is for picking up inventory for multiple jobs, the Warehouse Visit activity is not deleted automatically.
  • In these additional situations, no changes are made to the Warehouse Visit activity:
    • If the activity requiring inventory is suspended or changed to non-ordered
    • If the activity is moved (manually or via API) to another day and/or resource

That’s why it’s recommended that you follow the best practice of running recurrent optimization plans on the bucket. This practice can add, modify, or remove Warehouse Visit activities and update the warehouse inventory list. This is true even if multiple Warehouse Visit activities were scheduled for a single customer activity.

You may want to set up a recurring daily Warehouse Visit activity to maintain a placeholder for that activity in every route to account for a resource’s time. Then, when a day-before or intraday optimization plan is run, if no missing required inventory is identified, Routing will automatically remove the Warehouse Visit activity from the route.

ADDITIONAL INFORMATION

Moving Automatically Created Warehouse Visit Activities

Although you can manually edit Warehouse Visit activities that were created automatically, we recommend against it to avoid jeopardizing other activities in the route. If manual editing makes changes that do jeopardize other activities or the Warehouse Visit activity, a warning message appears.

Working with Both Regular and Automatically Created Warehouse Visits

Although Routing will automatically create Warehouse Visit activities when needed for activities with required inventory, it’s possible that you also have “regular” warehouse visit activities that were created either manually or via API for example to replenish trunk stock. Both of these types of warehouse activities can appear in the same route. And you may want to continue to manage the regular activities manually. However, it may be possible that the inventory needed by regular visits is available at the same warehouse as the automatically created visit, it makes sense to pick up all inventory at the same time.

One way to accomplish that is through two different activity types for warehouse visits: one created in the Internal activity group for manually managed warehouse activities, and the other created in the Warehouse Visits activity type group. When you do that, Routing will create, update, and delete required inventory pickups automatically, and it will bundle regular visits with the automatically created visits if they both have the same address – the warehouse resource’s Start location.

Another way to accomplish that is to create regular Warehouse Visit activities as placeholders in every route. You can even use the same activity type in the Warehouse Visits group for both manually and automatically created Warehouse Visit activities. Then, any required inventory that needs to be picked up is automatically added to the pre-created activity, and if no required inventory is needed, the activity is removed. If you want to ensure that Warehouse Visit activities remain on future days’ routes, you can set your optimization plan to remove only today’s warehouse activities if no required inventory needs to be picked up.

Working with Multiple Warehouse Visit Types

By default only one predefined Warehouse Visit activity type is available to automatically create a visit activity to pick up required inventory. You can, however, create additional types for use in different routing plans. For example, you might want to differentiate Warehouse Visits for in-house workers and contractors. You can set up one activity type with a default activity duration for the contractor Warehouse Visit, while setting up another that uses learned statistics to estimate pickup duration for in-house resources.

Working with Visits Created by Order Parts Plug-in V.2

You might want to created an order pickup plug-in using the sample code plugin-order-parts-collection_v2.zip at https://www.oracle.com/downloads/samplecode/ofsc-samplecode-downloads.html. When you use the option to create follow-up activity and you want to use plug-in and the feature under the same routing bucket, you must make sure that:

  • The inventory items ordered via Order parts plug-in are not the same inventory items assigned to the warehouse.
  • Moving activities between providers and reordering is prohibited for activities being created by Order Parts plug-in.

Integration

To fill the inventory list of the warehouse, use REST API the same way as filling the field resource inventory: Use the standard API requests, and refer to:

  • https://docs.oracle.com/en/cloud/saas/field-service/20c/cxfsc/op-rest-ofsccore-v1-resources-resourceid-inventories-post.html for individual requests 
  • https://docs.oracle.com/en/cloud/saas/field-service/20c/cxfsc/op-rest-ofsccore-v1-resources-custom-actions-bulkupdateinventories-post.html for bulk requests

The Events API can be used to track the initial activity booking by filtering the events for the creation of Warehouse Visit activity types. You can also track changes made to inventory booking through routing optimization by filtering the events of inventory creation/deletion for the activity type. These are the events produced when Routing automatically creates required inventory pickup activities:

  • activityCreated – Routing creates warehouse visit activity.
  • activityMoved –  Initiated when rollback occurs and a Warehouse Visit is deleted. An Undo Rollback action is available because Routing does not actually delete the Warehouse Visit activity but instead moves it to a hidden queue of the same resource for the same day. Then, if no Undo Rollback occurs, Routing deletes those hidden visits in the next routing run.
  • customerInventoryCreated, customerInventoryUpdated, customerInventoryDeleted – Routing performs adjustment of inventory reservation. The created inventory items belong to the customer pool and has references to both the Warehouse Visit activity and warehouse bucket. A reference to the warehouse bucket can be used to distinguish the reserved inventory from the regular customer inventory. Also, although the reserved inventory can be serialized, it doesn’t have serial number values.

Capacity/Quota

Routes that have multiple Warehouse Visits can affect capacity and quota because these activities require time to pick up inventory from warehouse. To compensate for this, you can reserve quota by setting the threshold lower than 100% of capacity for activities in capacity categories that might be affected by inventory pickup.

Limitations

Routing by inventory functionality does not support segmentable activities. It does not create required inventory pickups for such activities.

Warning Messages / Troubleshooting

If the warehouse resource cannot be used, you will see one of the following messages. This table provides the steps to correct the problem:

Warning How to Fix

Field resource cannot be used as a warehouse

Modify the routing filter used for "Treat as warehouse" to exclude field resources. Warehouses should use the bucket resource role.

A resource sharing inventory in teamwork cannot be used as a warehouse

Use the bucket resource role for warehouses; this role does not include sharing inventory in teamwork.

A resource without Start Location cannot be used as a warehouse

Ensure that Start Locations are assigned for warehouse resources for all the days covered by routing plan.

A resource without working calendar cannot be used as a warehouse

Ensure that Working Schedules are assigned for warehouse resources for all the days covered by routing plan.

A resource without inventory cannot be used as a warehouse

Ensure that inventory was assigned to the warehouse resource.

Watch a Setup Demo

Key Resources

IMPORTANT Actions and Considerations

DEPRECATIONS AND REMOVALS

  1. Legacy Manage will be removed with the 21A (February 2021) Update. In preparation for migrating to the Core Application, we strongly encourage you to begin configuring the Application Screens for each User Type in your configuration. This will ensure that you are prepared for the removal of the Legacy Core Manage screens with the 21A (February 2021) Update.

  2. The https://login.etadirect.com URL scheme, used to access Oracle Field Service is deprecated in 20D (November 2020) with a planned removal in the 21D (November 2021) Update. Review and change your current integrations and if needed change the URLs to use https://<instance_name>.etadirect.com. All OFS users should start accessing their instances using instance URL.  This change will improve authentication time and adhere to government/corporate policy regulations related to data residency by ensuring the request is directed to the proper data center from the initial submission. The instance name is available on the Configuration > About screen of the OFS application and in the Login policy screen. Alternatively, you can use the instance name you added in Service console. We recommend making the change in TEST first and then applying that change to your Production instance.

  3. The Classic and Vanilla Themes are deprecated with the 20D (November 2020) Update. Starting with the 21A (February 2021) Update, customers those themes will be converted to the Redwood style where your existing  logo and colors will be migrated.

  4. Starting with the 20D (November 2020) Update, the Get Events “subscriptionId = optional” parameter is being deprecated.  The parameter will be mandatory starting with the 21C (August 2021) Update. If a request is send without the mandatory parameter, the response will be: 401 Bad Request,

    "Mandatory parameter 'subscriptionId' is missing. You need to use a subscription to get the events.”

    Please make any necessary changes to your Events API between now and July 2021 to be prepared for this change.

  5. The https://api.etadirect.com URL scheme, used to access Oracle Field Service APIs is deprecated and being removed as part of the upcoming OCI data center migration. Prior to the OCI migration, you will be required to change the URL. Review and change your current integrations and if needed change the URLs to use https://<instance_name>.etadirect.com. The instance name is available on the Configuration > About screen of the OFS application. Alternatively, you can use the alternate instance name displayed in service console. We recommend making the change in TEST first and then applying that change to your Production instance.

  6. Starting in 20D, the process that calculates statistics will not be run in non-production instances (i.e. TEST). This means any started and completed activities will not be used to create statistics in a non-production instance. Customers are advised to use the Cloud Portal to re-create their Production instance to TEST to copy over statistics.