The new In-site installation has several advantages over the legacy iframe installation:
- Page height: The iframe integration requires the iframe to have a specific height, which can lead to an empty zone under the short pages or a scrollbar for the long pages.
- CSS: The in-site integration will inherit the CSS of your page which allows it to blend much more efficiently into your application.
Pre-requisites
You need to have the latest version of the hosted pages to be able to use the In-site integration.
See this guide to check whether you have the right version or not.
You need to understand what is a Customer Workflow.
Step 1 – Customer Portal installation
You first need to replace your iframe installation with the new in-site installation by following the procedure described in the Integration / Installation / InSite section.
To find the iframe installation in your code base, look for a fetch to the Customer object using the API Live, where the rel=hosted-home link is used as a source for an iframe.
Step 2 – Customer workflows migration
Your installation may use a few workflows that open in an iframe.
You can find those by checking where the API Live is used to fetch Links from the Customer, Subscription, Invoice or Offer objects. The href parameter of those links is used to open an iframe.
If that’s the case, you have to change the process a little:
- Keep track of the link rel= you are currently using; this is the workflow you want.
- This article will explain how to open the specific workflow using the in-site installation.