New Features Summary
For a list of existing features, refer to the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Field Service documentation at:
The following enhancements are included in this integration:
Attachment Support In Planned Service History
The Planned Service History plugin is enhanced with attachment support similar to the Service History plugin. Using this feature, the mobile workers can add attachments.
In the Planned Service History > Service History Entry page, the Attach button is added to support attachments in Planned Service History.
Users can add up to 15 activity levels (planned) and asset level service histories (combined) under any activity.
Support Attachments From WAM
The Attachment section allows users to add attachments from the Oracle Utilities Work and Asset Management application in the Work Activity page. The attachments are then passed to Oracle Field Service after sending outbound message for an activity from Oracle Utilities Work and Asset Management to Oracle Field Service.
On the Oracle Field Service mobile screen, attachments can only be downloaded for viewing. Users will not have any privileges to modify or delete these attachments from Oracle Utilities Work and Asset Management.
Support Activity Dependencies
Work activities in Oracle Utilities Work and Asset Cloud Service may have dependencies on other activities within the same work order or on activities in different work orders. These dependencies can have timing options, such as “after finish” and “after start”. They will be reflected in the Oracle Field Service system by linking the dependent activities together.
The previous releases (before 23A) of this integration did not support Activity Dependencies.
The Activity Dependency information is added to the Work Activity API to be consumed by a mobile solution or Oracle Field Service. Oracle Field Service already includes this functionality, but was not used to send information. It has been enhanced in this integration to utilize this information.
OFS Domain Name Changes
To support dynamic Oracle Field Service domain names, in 23A release, the ofsc_siteAddress property is deprecated from the Oracle Field Service properties. The ofsc_hostname property is added instead.
An example API path to be configured under ofsc_hostname can be:
https://<site address>.<domainName>