The path to a URL (for external plug-ins). 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. If you clear this check box, the URL is just opened in a new tab/window/iframe. If this option isn’t selected, the HTML5 plugin is just a URL of an external resource that is opened in a new window or in an iframe.ĭetermines whether you want the plug-in to communicate with Oracle Field Service using the Plug-in API. This restriction applies only for plug-ins that use the Plugin API. An HTML5 application plug-in can be used in one of these Mobility contexts - Activity List, Edit., View Activity, Inventory Grid or Add/Details Inventory. HTML5 application: This means, the plug-in uses an external application to extend the functionality. Native application: This means, the plug-in opens another application on the same device. The list of available base actions is filtered according to the Entity that is selected. 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. It appears only in the contexts in which the base action appears and is shown or hidden according to the same visibility conditions. The base action affects only the visibility of buttons and not the functioning of the plug-in. When a base action is selected, the resulting plug-in functions per the same rules as the base action. The base action from which the plug-in is to be derived, if needed. Leave the field blank for the action to be available in all contexts of all the entities. For example, if you select Inventory, the action will appear only in the contexts related to inventory. Plug-in name translations to other languages, if used.Ī mandatory field defining a unique action or plug-in label.Įntity (activity, inventory, required inventory, resource, service request, user) to which the action or plug-in is to be related. The action or plug-in appears under this name in the actual context. Each item, when clicked, leads to the corresponding configuration page.Ī mandatory field defining the plug-in name in the English language. Items are added only to the groups listed earlier. Subsystems (the settings related to Oracle Field Service modules): Users, Security, Integrations (the settings related to user management and system access): Resources, Activities, Inventories (the settings related to the resources the company employs, the activities it performs and the inventory used in the course of their performance):ĭisplays (the settings related to the general appearance of the application, page layouts, languages and translations): General (the settings related to the general principles of the company operation): The configuration elements are grouped logically on the