The ability to create custom installation pages has proven to be very popular within our developer community. Today, we are announcing changes to this feature to improve security and to increase the ease of testing.
To improve the security of how apps work within Freshdesk, the custom installation page will be sandboxed within an IFrame when it is rendered in the Freshdesk Product UI.
How does this impact you? If your custom installation page relied on certain libraries or stylesheets to be available by default from the parent page, those will no longer be available. You will also need to include our fresh_client library to enable the page to communicate with the product.
What action must you take?
- Include the complete HTML with all the libraries and stylesheets your install page will need. To maintain design consistency with the product, include our product-specific stylesheets as shown below.
<link rel=”stylesheet” type=”text/css” href=”https://static.freshdev.io/fdk/2.0/assets/freshdesk.css">
- You must include our fresh_client.js to enable communication between your custom installation page and the parent page, through the sandbox.
- If you are currently using mkp.request in your install page script, please use client.request as shown below
As part of v4.2.1 of the FDK, we included the ability for develoers to local test the custom installation page. When you type in FDK run into your console, you will see the URL that you can use to test the installation page.
You can now test out the app installation experience. Once you have filled in the fields, you can press the “Install” button to test the app using the entered values.
Please reach out to us at email@example.com if you have any questions about these updates. And follow us on @FWMarketplace