Help & Support
Elevate Your Agents with AgentExchange Solutions
Easily enhance Agentforce with pre-built AI solutions from AgentExchange. Browse, install, and deploy agents, actions, and apps directly into your environment. Tell Me More
Have Questions?
Private ListingThis listing is private and can't be found by searching or browsing AppExchange.
iNetIndustry: Inline VisualForce Expander
- Business Need
- Admin & Developer Tools
Automatically resize inline VisualForce components on standard page layouts. Create custom functionality without scroll bars and empty white space.
Rating
Reputation
MVP
Recognized by Salesforce for their leadership, expertise, and generosity
Top Reviewer
Contribute reviews that encourage conversation and help others make informed decisions
Ranger
Lifelong learners who have earned the Ranger rank or higher on Trailhead
Showing 10 of 32 Reviews
Doesn't work
Installed the package then followed the instructions and it doesn't dynamically update the height of the VF Page within the Standard page layout.
The height of the section was not changing dynamically as we expanded
I installed inline visualforce expander in my sandbox and configured it as per guidelines provided. But seems it is not performing dynamically once we expanded or contracted the Account Hierarchy. The Height of the Account Hierarchy was not changing. Can any one suggest me any required changes to make it possible dynamically.
Works Perfectly...as expected!! Excellent App! Thanks a ton!
Found this app on one of the forums while searching for code to dynamically resize inline visualforce pages. This app does exactly that...with just simple configuration steps. The users absolutely love the functionality. Thanks for putting this up.
Does not work when using namespace
This app does no work when we are using namespace. Is there any work around for that! Otherwise it is a great app
Great Application. Doesn't work in Service Console though.
This is a great application and solves many problems associated with height of the section containing inline visualforce page. However, this does not work in service console because of its dependency on the sidebar component, I guess.
Worked in Sandboxes, not in Production
I installed this app in two sandboxes and it worked like a charm. I just installed it in Production and... nothing. I went over the installation guide twice and even uninstalled and reinstalled. I don't know what the difference is.
Did not work. Got it using jquery. Uninstalled.
Installed, followed instructions but didn't work at all. I had jquery already in a sidebar element to hide some stuff and I found that I can use it for autoheight the visualforce pages. Well, with jquery almost any style property can be changed, so, I got it with one line of code: j$("#visualforcepageId").height(‘auto’); So, uninstalled the app.
Makes my inline page dissapere.
For whatever reason this works TOO well because it shrinks the size of my inline VF page to zero. I know its there because for a brief second while the page is loading the Account Hierarchy VF page shows but quickly minimized to nothing as soon as the page finishes loading.
Great App, but...
Be sure to read the review below to get it working in IE from Marcel Oesterhaus. UPDATE, it appears this app will become no longer functional with the Summer '15 release. If you go to the InlineVFExpander Home Page custom component you'll now get this warning: This component contains code that is no longer supported. For security reasons, in Summer '15 we will start removing non-supported code from HTML Area home page components. As a result, this component may stop working properly. If you want to use JavaScript or other advanced HTML elements in your home page component, we recommend that you create a Visualforce Area component instead.
**UPDATE SUMMER '15** Works perfectly, even on Internet Explorer after editing one .js file
UPDATE SUMMER '15: Due to changes concerning unsupported code from HTML Area home page components we have to do some changes to make the scripts of the static resource still being loaded, which doesn't work using a Visualforce Area by the way. 1) Go to 'Setup' >> 'Customize' >> 'Home' >> 'Custom Links'. 2) Create a new Link with behavior 'Execute JavaScript' or edit an existing link with this behavior. 3) Add the following code: {!REQUIRESCRIPT("/resource/1301087741000/InlineVFExpander/easyXDM.packed.js")} {!REQUIRESCRIPT("/resource/1301087741000/InlineVFExpander/inlineVFExpander.parent.js")} 4) Go to 'Home' >> 'Home Page Components' and create a 'Links' Component or choose an existing one. 5) Add the created Link. I have read that even that workaround could be shut down in Winter '16: http://salesforce.stackexchange.com/questions/68587 ---------------------- To fix my issue with IE I had to search for two (!!) outquoted parts within the .js file: 1) Go to 'Setup' >> 'Develop' >> 'Static Resources'. 2) Click on 'InlineVFExpander'. 3) Click on 'View File', then save the file to your local drive. 4) Unzip the file 'InlineVFExpander.zip' (if the '.zip' is missing, rename the file and add .zip to the end). 5) Open the file 'easyXDM.packed.js' (for example with Notepad++). 6) Search for '/*'. 7) I had to remove the following code: 7.1) /*@cc_on@if(@_jscript)frame=document.createElement("");@else*/ 7.2) /* @end @*/ 7.3) I found both in line 24. Any outquoted parts have to be removed from line 24, because those outquotes seem to offend IE. 8) Save the changed 'easyXDM.packed.js' and replace the old one in the zip file. 9) Go to the Static Resource again and click on 'Edit', then 'Choose File', choose the changed zip file and click '
Marcel Oesterhaus
09/14/2015
Hi Nitin, I haven't tested it yet, but regarding the Winter '16 Release Notes it seems to be the end of including Script from other resources. "REQUIRESCRIPT No Longer Executes JavaScript On Page Load We’ve changed the way custom JavaScript buttons and links work when they use REQUIRESCRIPT. The REQUIRESCRIPT resources aren’t included in the page until the user clicks the custom JavaScript button or link." http://docs.releasenotes.salesforce.com/en-us/winter16/release-notes/rn_forcecom_general_requirescript.htm I think we have to say goodbye to Inline VisualForce Expander. I guess Salesforce won't care anyway, since they are forcing the development and usage of the new Lightning Experience. Furthermore I've heard, that they are forcing appexchange providers into new contracts to qualify and disqualify. I am afraid this is going to disqualify many free apps. But this is only my wild speculation. We will see.
Nitin Paliwal
09/14/2015
Hi, is this application working after the recent winter 16 release?For me it's failing in all sandbox which have been updated. Is there any another workaround for this app?
Marcel Oesterhaus
06/11/2015
Sounds great. Probably the script is being blocked or even not being loaded in the Partners Community, for whatever reason. It's a tragedy. Such a nice feature. It's almost worth an idea, but I'm too lazy to post and describe it with my broken English. ;)
Jack Sanford
06/11/2015
Yes I installed it yesterday, our full sandbox has Summer 15, it worked in our main environment, but couldn't get it to work in the Partners Community. Tried adjusting the links to the JavaScript custom links, made sure the VF page was added to the Partners area, but couldn't get it to work.
Srikanth Pothuraj
06/10/2015
Hi Jack, Have you tried installing today? Is your Org in Summer'15?
Jack Sanford
06/10/2015
That works great except not in our Partners Community
Srikanth Pothuraj
06/01/2015
When you try and edit the "InlineVFExpander" Home Page Custom Component in production, The below message would appear. "This component contains code that is no longer supported. For security reasons, in Summer '15 we will start removing non-supported code from HTML Area home page components. As a result, this component may stop working properly. If you want to use JavaScript or other advanced HTML elements in your home page component, we recommend that you create a Visualforce Area component instead."
Srikanth Pothuraj
06/01/2015
Weird when you mentioned this comments if for a Summer 15.. Thanks! Hope you find a fix soon.
Marcel Oesterhaus
06/01/2015
Unfortunately our Sandbox is a non-preview instance, so I have to wait until Summer '15 Update - I am afraid, that it will fail then. My last idea is, to include Script via a button. Let's see, if it works. But to be honest, I don't like that solution.
Srikanth Pothuraj
05/29/2015
I have tried the same steps you have mentioned. It still fails. Dont know why. Do we even have a fix ? In next 2 weeks it will also fail in Production. Please help
Marcel Oesterhaus
05/12/2015
In addition: You can even hide the link including the script (take a look here: http://salesforce.stackexchange.com/questions/38918/end-of-javascript-sidebar-workarounds), but at our org it wasn't necessary to hide the link, because we were already using a custom Home Page Component for Links to provide Links which opens in a new tab automatically. Example for such a custom Link: Label: 'Google Mail' Behavior 'Execute JavaScript' Content Source: 'OnClick JavaScript' Code: {!REQUIRESCRIPT("/resource/1301087741000/InlineVFExpander/easyXDM.packed.js")} {!REQUIRESCRIPT("/resource/1301087741000/InlineVFExpander/inlineVFExpander.parent.js")} var gmail = window.open("https://mail.google.com") Killed two birds with one stone: Opens Google Mail in a new tab and loads the script for InlineVFExpander. :) I add all custom Links this way to make them open in a new tab, but the required script I do only load within one of those custom links, or course!
Hi Ajit, Is this application working after the recent Summer'15 release? For me it's failing in the Sandbox.