Plugins

        In computing, a plug-in (or plugin, add-in, addin, add-on, or addon) is a software component that adds a specific feature to an existing computer program. When a program supports plug-ins, it enables customization.
        An example of a plugin is the free Macromedia Flash Player, a plugin that allows the web browser to display animations using the Flash format. As the Web has become more commercial, Flash has become a popular format for displaying ads in web pages. As a result, many web users have been prompted to download the Flash plug in and have it installed on their systems.

Type of Plugins

  • Custom language support
  • Framework Integration
  • Tool integration
  • User integration Add-ons
  • Thems
  • commonly used for extensions, are backends, datasources and processors.
    •


    Plugin and its working process

  • HTML5 Web Messaging : W3C defined technology that allows HTML 5 applications opened in the same browser communicate directly, without involving any server. This is the technology on top of which the Oracle Field Service Cloud plug-in API is built. Official description can be found on the W3C site https://www.w3.org/TR/webmessaging/. The browser that is used to work with Oracle Field Service Cloud must be compatible with this technology.
  • Activity modules : Activity modules are essential types of plugins in Moodle as they provide activities in courses. For example: Forum, Quiz and Assignment.
  • Antivirus plugins : Antivirus scanner plugins provide functionality for virus scanning user uploaded files using third-party virus scanning tools in Moodle. For example: ClamAV.
    •


  • Oracle Field Service Cloud Plug-in : An external application that is used to extend Oracle Field Service Cloud capabilities with custom features. The external application can be an HTML 5 application, an offline HTML 5 application, or a mobile application. The application must correspond to certain requirements to be used as a Oracle Field Service Cloud plug-in.
  • Mobile Plug-in Extension Framework : General guidelines and communication protocol that an external offline supported HTML 5 application must follow to be used with Oracle Field Service Cloud as an offline capable plug-in.
  • Oracle Field Service Cloud Action A button or a link placed on an Oracle Field Service Cloud screen that invokes a plug-in or a standard Oracle Field Service Cloud action, using settings configured in the Action Link.
  • Oracle Field Service Cloud Plug-in API : Protocol of communication between a plug-in and Oracle Field Service Cloud, which is used in the Mobile Plug-in Extension Framework.
  • Oracle Field Service Cloud Action link : Oracle Field Service Cloud configuration entity that includes all the information necessary for Oracle Field Service Cloud to invoke a plug-in or a standard form.


    • Configure the application to use a plug-in

  • Procedure : Configure the activity, inventory, and resource properties that you want to update through the plug-in in the Activity Properties, Resource Properties, and Resource Properties plug-in context layouts in Mobility Cloud Service. The following figure shows the Edit/View activity Visual Form Editor.
  • Tap the plug-in button in Oracle Field Service Mobility Cloud Service : The plug-in window opens showing the activity, inventory, and resource properties configured in the plug-in API contexts. You can change the values of these fields from the plug-in window to update the corresponding properties in Oracle Field Service Cloud. The following figure shows a sample plug-in window and includes the activity, inventory, and resource properties:


    • Using the plug-in

            When you create an HTML5 application plug-in, you can use it in the Activity list, Edit/View activity, Inventory grid, Add/Details inventory Mobility Cloud Service contexts. This topic describes how to use a plug-in in Oracle Field Service Cloud. Additionally, you can define the properties of the Oracle Field Service Cloud entities to be sent in the plug-in message. These properties are added to the special context layouts related to plug-ins. A separate context exists for activity, inventory and resource properties. The properties defined in the corresponding contexts will be sent in the plug-in API messages. The property visibilities are also checked and observed.



    Contact us or Request Quote for any type theme Services needs contact us.