URL Isolation Method 
When you set the Isolation Method property of an iView to URL, the iView is written into an iFrame, which is inserted into a container on the page.
Each iFrame works independently. One iFrame can run a script, for example, or any other event, without interfering with the content in the other iFrames, although iViews can interact through client-side events.
iViews are not encoded in the HTML of the page:
PageBuilder generates an iFrame and sets the source attribute to point to the iView URL.
iView content is generated after an additional server request.
PageBuilder writes content into the iFrame on the client side.
Interactions and reload actions on the iView do not affect the rest of the page.
Flicker-free pages.
Enhanced performance.
PageBuilder has full control over the appearance of the iView content.
The page determines the iFrame size.
The administrator has three page settings to control iView height:
Fixed / Full Page / Automatic
The page can add vertical and horizontal scrollbars to the iFrame.
Only client-side events are supported.
An iView that is set to the URL isolation method is isolated from the page request and does not automatically receive the parameters from the page request.
The Parameters to Pass from Page Request property lets you define a set of URL-based parameters that should be forwarded from a portal page request to the iFrame displaying the current iView.
Use this property to define page request parameters as follows:
Property Value |
Description |
|---|---|
Asterisk (*) |
Passes all parameters |
Empty field |
Does not pass any parameters |
Asterisk, comma, and parameters separated by a comma (*,param1,param2) |
Passes all parameters, except for those listed |
Parameters separated by a comma (param1,param2) |
Passes the listed parameters |
Caution
Content-loading events on embedded iViews cause the loss of iViews that are in iFrames. It is not recommended to put embedded and isolated iViews on the same page.