Packaging the Fuse and JavaScript
You have completed your content, mappings and did any modifications, and you have checked via the preview if the result is satisfactory. Upon completion of the entire Fuse, you can click a button that will compile the entire html code and converts it into a Fuse-reference.
Fuse reference
The Fuse reference consists of a div-tag with a data attribute <div data-wf-fuseid></div>
Additionally, the user also can copy a generic JavaScript snippet into the footer of the webpage.
Add Fuse-reference to website
A simplified reference to the Fuse and a JavaScript snippet that can be copied onto your specific webpage.
The Fuse reference will be a div-tag with a data attribute <div data-wf-fuseid></div>. The entire div gets replaced by the rendered content.
The end user can copy and paste the account.js (bridge.webfuse.io/v1/account.js). This needs to happen as an async JavaScript snippet cfr. Google analytics code.
Additionally, the end user needs to copy-paste also the div-reference with the data-attribute.
The JavaScript snippet needs to be able to call the bridge of WebFuse. The JavaScript snippet will be specific for that account and is stored on the database of the server.
This JavaScript needs to do a “QuerySelectorAll” to find all the divs with the data-wf-fuseid attribute. For each Fuse he finds, he takes the fuseid and calls the URL behind that ID. That URL is a JavaScript file that calls the load balancer and checks the database of WebFuse (Azure) if the domain is whitelisted and the corresponding DLL that renders the content as html.
Rendering data
Upon loading the webpage, the JavaScript calls WebFuse, requesting the information for the specific Fuse on the webpage. WebFuse calls Dynamics 365 and picks up the latest data for the requested fields.
WebFuse then renders the data to the webpage in combination with the added content in the Fuse.