Visualforce Developer Guide

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
Integrating 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
Investigate Performance Issues
Follow Visualforce Design Guidelines
Control Data Size
Cache Frequently Accessed Data
Lazy Load Page Components
Handle Multiple Concurrent Requests
Write Efficient Apex and SOQL
Write Efficient Getter Methods
Optimize Lists and Tables
Optimize the View State
Optimize HTML
Optimize CSS
Optimize JavaScript
Optimize Images
Prevent Fields from Dropping Off the Page
Use the immediate Attribute Carefully
Visualforce Performance Case Study
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 Component Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Use the immediate Attribute Carefully

Visualforce components with the immediate attribute set to true execute an action without processing any validation rules for the associated fields on the page. This attribute should only be used if the component executes an action that navigates away from the page after completion.

Functional problems occur when the component behavior includes more than basic navigation functionality. Because immediate="true" doesn’t update the page's data model, the page's data model won't reflect any changes made during the action. This discrepancy can cause undefined behavior and possible data corruption.

Use of the immediate attribute is recommended only for cancellation actions. The following example shows an appropriate use of this attribute. When the user clicks Cancel, the <apex:CommandLink> component immediately performs cancelApplication without requiring the user to fix validation errors.

1<apex:CommandLink action="{!cancelApplication}" value="Cancel" styleClass="btn" id="btnCancel" immediate="true">