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
Overriding 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
Salesforce Platform Development Process
Tell Me More: Where Visualforce Pages Can Appear in the Salesforce App
Guidelines and Best Practices
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Best Practices
Standard Component Reference
Appendices
Glossary
PDF

Newer Version Available

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

Tell Me More: Where Visualforce Pages Can Appear in the Salesforce App

When you create a Visualforce page, you can make it available from a number of places in the user interface.
  • Navigation menu—available when you tap Salesforce App Nav from the mobile app
    Find warehouses navigation menu
  • Action bar and action menu—available from the bottom of any page that supports actions
    Create Quick Order action in the action menu
  • Record related information page (as a mobile card)—available when you navigate to a record
    Mobile card in Salesforce app

You can also reference, and link to, another Visualforce page in your Visualforce markup using the supported navigation calls listed at Navigation with the sforce.one Object. Be sure to select Available for Lightning Experience, Lightning Communities, and the mobile app for all pages in a multi-page process.

If a referenced page doesn’t have Available for Lightning Experience, Lightning Communities, and the mobile app selected, it doesn’t prevent the referencing, or parent, page from appearing. However, when a user tries to access the nonmobile enabled page, they receive an “Unsupported Page” error message.