Step 1: Find a plugin slot that will support your functionality
To create a plugin you need to find an existent plugin slot that:
- Is available in the UI location where you want to load your plugin.
- Allows for the behavior/functionality you want your plugin to support.
Note: At this point, you can add plugins to the BriteQuote risk edit pages and the Policy Overview screen only.
Step 2: Add the script tag to your plugin HTML file
Add this following script to the header of your HTML file:
Step 3: Initialize the plugin
Use the BriteCorePlugin helper so your plugin can communicate with BriteCore:
The slotInput object will vary upon the plugin slot you want to connect to.
Example: the button-row slot with a single button:
You can use the plugin’s visible and enabled functions to dynamically hide/disable it based on risk type or certain fields.
Step 4: Register the plugin in the BriteIntegrations service
Send an API call to BriteIntegrations using the /plugins/ endpoint to POST the following payload:
Available actions are POST, GET, PATCH, and DELETE. Use GET without an appended plugin_id to retrieve a list of plugins.
- type: plugin
- name: Name of the plugin (this isn’t what necessarily shows up on the UI)
- Plugin_file_path: The plugin_file_path is the path appended to the base_url
- Slot_name: britequote:risk-edit:bottom-row:button-row
- base_url: Can be used to specify a fully qualified domain name (FQDN). If the base_url is empty, it will default to: integrations.britecore.com.
- configuration: Configuration is an object of arbitrary data that gets passed into the plugin on initialization that you can use to store any configuration you don’t want to hardcode into the plugin itself. An example use case is attaching an API key.
Note: Anything stored in configuration can be seen by an (authenticated) end-user.
You’re now ready to deploy and test your plugin.
A note on hosting
Each plugin is an HTML document rendered in a hidden iframe. BriteCore’s UI queries for the plugins available and renders any plugin on the specified pages.
Since BriteCore’s UI is running in a browser, the hosting for the plugin must occur without credentials to a publicly available location.
Plugins often query other restricted resources. If the plugin is served from a domain that also has access to the credentials, it’s possible to use those.
Example of a hosting decision
The Example Insurance Company allows logged in agents to quote. Upon logging in, Example Insurance stores an access token in the local storage of the browser. A plugin served from https://www.exampleinsurance.com can access the local storage for that domain and use the access token to make further requests.