Visualforce Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Override Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrate Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Best Practices for Improving Visualforce Performance
Best Practices for Accessing Component IDs
Best Practices for Static Resources
Best Practices for Controllers and Controller Extensions
Best Practices for Using Component Facets
Best Practices for Page Block Components
Best Practices for Rendering PDF Files
Best Practices for <apex:panelbar>
Documentation Typographical Conventions
Standard Visualforce Component Reference
Appendices
PDF

Best Practices for Static Resources

Displaying the Content of a Static Resource with the action Attribute on <apex:page>
You can use the action attribute on a <apex:page> component to redirect from a Visualforce page to a static resource. This functionality allows you to add rich, custom help to your Visualforce pages. For example, to redirect a user to a PDF:
  1. Upload the PDF as a static resource named customhelp.
  2. Create the following page:
    <apex:page sidebar="false" showHeader="false" standardStylesheets="false" 
      action="{!URLFOR($Resource.customhelp)}">
</apex:page>
Notice that the static resource reference is wrapped in a URLFOR function. Without that, the page does not redirect properly.
This redirect is not limited to PDF files. You can also redirect a page to the content of any static resource. For example, you can create a static resource that includes an entire help system composed of many HTML files mixed with JavaScript, images, and other multimedia files. As long as there is a single entry point, the redirect works. For example:
  1. Create a zip file that includes your help content.
  2. Upload the zip file as a static resource named customhelpsystem.
  3. Create the following page:
    <apex:page sidebar="false" showHeader="false" standardStylesheets="false" 
      action="{!URLFOR($Resource.customhelpsystem, 'index.htm')}">
</apex:page>
When a user visits the page, the index.htm file in the static resource displays.