The Plugin Framework

Oracle Fusion Field Service is a highly developed application that can be customized for the unique purposes and specialized business needs of organizations. That extensibility is achieved in part through the use of plugins, which can perform actions not found in the standard solution. Plug-ins appear as selectable links on the application. They open a new window, tab, or frame in a browser where an external HTML5 application is processed.

Plug-ins can be internal or external. Internal plugins can be created only by Oracle developers. External plugins, however, can be developed by anyone; they use externally stored data and communicate with the application by HTTP requests. The external plugins use HTML5 features such as offline work and persistence storage. However, be aware that if an external plugin has its own domain, offline mode is not supported for iOS Native Application. The plugin framework also allows these applications to exchange data with Oracle Fusion Field Service, in two ways:

• Traditional one-way communication when the plugin receives data from Oracle Fusion Field Service through the HTTP GET and POST parameters.

• Two-way communication using Oracle Fusion Field Service Plug-in API

The plugin framework offers these features:

• Integration with Oracle Fusion Field Service through an API and, therefore, the ability to perform complex tasks which could previously be performed only by internal plugins

• Ability to work offline with Mobility Cloud Service

• Plugin development by your organization or third-party developers without requiring Oracle developers

The plugins can manipulate these entities:

• Resource

• Activity

• Inventory

• Activity list

• Inventory list

Consequently, the plugins can be added to these contexts:

• Activity list

• Activity Details

• Inventory grid

• Add/Details inventory

• Route Map/Team Map (for Custom Map Layer assets)