Fuuz is migrating to a brand new Chrome browser extension by the same name. The reason for this migration is to comply with Google’s new security requirements for extensions. This new browser extension (found here) has most of the same functionality as before, with 2 key differences:
The Visualization action type has been removed
The ability to inherently render screens in floating windows has been replaced with an iframe to the Fuuz website directly
This action type, along with the data flow action type’s corresponding response type, has been removed. This feature was actively being used, and is now redundant with the ability to set up Screens with Chart screen elements in them instead.
The change to screen rendering has 2 main side effects to be aware of:
The authentication is not shared between the browser extension and the iframe, so users will be prompted to log into Fuuz in the floating window again with a username and password
All parameters that are sent to screens from the browser extension now come in as strings regardless of original data type
Note: To reiterate, these limitations are strictly for the Screen action type. All other action types available in the browser extension (Webhook, Data Flow, etc.) are unaffected and will function exactly the same as before.
Let’s break down what each of these mean:
The iframe works basically like a regular browser tab; it is literally navigating directly to our Fuuz website. This means that you will have to log into Fuuz the same way you would if you opened the website in a new browser tab, with a username and password. Once logged in, the session will remain active via the same rules as before, until 90 minutes of activity. The session will also persist between actual browser tabs logged into Fuuz.
If you were previously using the Fuuz Browser Extension with just an API key and no password, then you’ll have to contact your administrator to get a password set up for your account as well if you plan on using the Screen functionality.
When designing a screen to be rendered in the browser extension, previously all parameters that came from the browser extension would retain their data type, so checkboxes would be either true or false, numbers would be numbers, etc. Now with this new version of the Fuuz Browser Extension, screens that receive parameters from the browser extension via $metadata.urlParameters will now receive them all as strings. This means that checkboxes and other boolean values will be available as ‘true' and ‘false', and number parameters will be available as string versions as well such as '123'.