Visualforce Pages

Development 🟡 Intermediate
📖 4 min read

Definition

Visualforce Pages is a Setup page that lists all Visualforce pages in the org along with their API version, label, and associated controller. Administrators and developers use this page to create, edit, and manage Visualforce pages, which are custom UI pages built using the Visualforce markup language.

Real-World Example

The developer at Heritage Insurance navigates to Visualforce Pages in Setup to review the 25 Visualforce pages in the org. She finds the "GenerateQuotePDF" page that renders insurance quotes as downloadable PDFs. She updates the page to include a new coverage disclaimer section and bumps the API version to the latest release.

Why Visualforce Pages Matters

Visualforce Pages is a Setup page that serves as the central management console for all Visualforce pages in a Salesforce org. It displays a sortable list showing each page's name, label, API version, associated controller, and the date it was last modified. From this page, administrators and developers can create new pages, edit existing markup, preview pages, and manage page-level security by controlling which profiles can access each page. The page also shows whether each Visualforce page is available for use in Lightning Experience, mobile, or Salesforce Sites.

For organizations maintaining legacy Visualforce implementations, this Setup page is essential for governance and migration planning. With some orgs accumulating 50, 100, or more Visualforce pages over years of development, having a centralized inventory with version information enables teams to identify pages running on outdated API versions that may have deprecated functionality. During Lightning migration initiatives, the list becomes a project tracker where teams can categorize pages by business criticality, migration complexity, and user impact. Regular reviews of this page help identify orphaned pages that no longer serve a business purpose, reducing security surface area and simplifying the codebase.

How Organizations Use Visualforce Pages

  • Heritage Insurance — Heritage's developer navigated to Visualforce Pages in Setup to review their 25 Visualforce pages. She found the GenerateQuotePDF page, updated it to include a new coverage disclaimer section required by regulators, and bumped the API version from v48 to the latest release to take advantage of improved PDF rendering capabilities.
  • Quantum Solutions — Quantum's new admin used the Visualforce Pages list to audit the org during onboarding. She sorted by API version and discovered 8 pages still running on version 30, which was over 10 years old. She flagged these for the development team to update, and two turned out to be orphaned pages that could be safely deleted.
  • Trident Corp — Trident's security team performed a quarterly access review using Visualforce Pages. They clicked into each page's security settings to verify that only appropriate profiles had access. They discovered that the HR Compensation page was accessible to the Sales User profile due to a permissions error and immediately restricted access.

🧠 Test Your Knowledge

See something that could be improved?

Suggest an Edit