Extended Location Privacy Configuration

Starting 25C release, Oracle Fusion Field Service introduces new features that make it easier to manage and control how resource locations data and positions history are displayed. This means your organization can now set up access based on roles, keep sensitive location information secure, and ensure that the mobile workers visibility aligns with operational needs and privacy considerations..

Replacement of the Maps Option

To give administrators more precise control over what different users can see on maps, the single Maps option on User Types page has been replaced with two more targeted permissions. 

  • Display Current Position of Resources on Maps: This new permission controls whether users can see the real-time locations of resources in
    • Dispatch Console Map -> Show Nearby Resources 
    • Dispatch Console Map -> Show Resource Location on the Map (renamed to Show Resource Position on Map)
    • Team Map -> Layer switcher -> Resources
    • Route Map -> Layer switcher -> Resources 

Display Current Position of Resources on Maps

This screenshot shows the Show Resource Position on Map and Show Nearby Resources settings on the Dispatch Console map. These settings are shown when the Display Current Position of Resources on Map setting is selected on the User Types page.

  • Display Resource Trace on Dispatch Console: The Display Resource Trace on Dispatch Console permission controls who can view the historical movement of resources on the following areas of the Dispatch Console: 
    • Dispatch Console Map -> Show Resource Trace 
    • Dispatch Console Time -> View  Show Resource Trace

Display Resource Trace on Dispatch Console

Display Resource Trace on Dispatch Console

With these enhanced permissions, your organization gains more precise control over the visibility of location data, allowing you to customize access based on operational needs. For example, dispatchers can now see nearby resources to make quick decisions, without needing to share this real-time data with everyone. Meanwhile, supervisors can review route histories to check performance or for auditing purposes. This update helps with both making real-time decision making and respecting role-based privacy.

NOTE: If the general Maps permission was enabled for a User Type before the 25C upgrade, both the Display Current Position of Resources on Maps and Display Resource Trace on Dispatch Console permissions are automatically enabled after the upgrade.

Resource Location privacy flag
To enhance control over location privacy, a new Location is private option is now available on the Resource Locations page. This setting, which is also available through the API using the parameter PrivateLocationFlag, allows you to mark a resource's location as private.  
The following API operations support the PrivateLocationFlag parameter:

  • Create a resource location
  • Update a resource location
  • Get a resource location
  • Get resource locations

When the Location is private check box is selected for a resource:

  • The mobile workers starting and ending locations are not displayed on both the Dispatch Console and the Route Map.

NOTE: If mobile worker has logged in to the application as themselves, they can see their own location on the Route Map.

This feature is especially helpful for protecting the location privacy of home-based workers, contractors, or when there are specific regional rules about location visibility.

Resource Location privacy

Resource Location privacy

Business Benefits

  • Ensure that Oracle Fusion Field Service provides robust features to enable compliance with data privacy regulations, by offering configurable controls for resource location, compliance visibility, among others.
  • Provide users with the ability to manage access permissions at a granular level, ensuring that only authorized users can view resource location and compliance data as necessary for their roles and responsibilities.
  • Build trust and confidence among Oracle Fusion Field Service users by demonstrating a commitment to data privacy and compliance through the implementation of visibility controls.
  • Ensure that the solution is scalable and adaptable to accommodate evolving regulatory requirements and organizational needs (such as requests from unions), allowing for continued compliance and operational effectiveness over time.

Steps to Enable

To enable the new map visibility permissions:

1. Automatic migration: Upon upgrade to 25C, if the legacy Maps option was previously enabled for a User Type, both new permissions are automatically enabled:

  • Display Current Position of Resources on Maps
  • Display Resource Trace on Dispatch Console 

2. Manual configuration (if needed): Navigate to Configuration -> User Types, select the relevant user type, and enable:

  • Display Current Position of Resources on Maps
  • Display Resource Trace on Dispatch Console

To enable the Location is private setting:

  1. Navigate and open the Resources Info page of the relevant resource record and then click Locations -> Resource Locations and check Location is private.
  2. This setting (PrivateLocationFlag) can also be updated programmatically using the Resource Locations API operations ( Create a resource location and Update a resource location ) for automated updates. 

Tips And Considerations

N/A