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
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
Standard Visualforce Component Reference
Appendices
Global Variables, Functions, and Expression Operators
Global Variables
$Action
$Api
$Asset
$Cache.Org
$Cache.Session
$Component
$ComponentLabel
$CurrentPage
$FieldSet
$Label
$Label.Site
$MessageChannel
$Network
$ObjectType
$Organization
$Page
$Permission
$Profile
$Resource
$SControl
$Setup
$Site
$System.OriginDateTime
$User
$User.UITheme and and $User.UIThemeDisplayed
$UserRole
Functions
Expression Operators
Security Tips for Apex and Visualforce Development
Apex Classes Used in Visualforce Controllers
Execution Governors and Limits
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

$User.UITheme and and $User.UIThemeDisplayed

These global merge fields identify the Salesforce look and feel a user sees on a given Web page.

The difference between the two variables is that $User.UITheme returns the look and feel the user is supposed to see, while $User.UIThemeDisplayed returns the look and feel the user actually sees. For example, a user can have the preference and permissions to see the Lightning Experience look and feel, but if they’re using a browser that doesn’t support that look and feel, for example, older versions of Internet Explorer, $User.UIThemeDisplayed returns a different value.

Usage

Use these variables to identify the CSS used to render Salesforce web pages to a user. Both variables return one of the following values.

Valid values include:
  • Theme1—Obsolete Salesforce theme
  • Theme2—Salesforce Classic 2005 user interface theme
  • Theme3—Salesforce Classic 2010 user interface theme
  • Theme4d—Modern “Lightning Experience” Salesforce theme
  • Theme4t—Salesforce mobile app theme
  • Theme4u—Lightning Console theme
  • PortalDefault—Salesforce Customer Portal theme that applies to Customer Portals only and not to Experience Builder sites
  • Webstore—AppExchange theme

Example

The following example shows how you can render different layouts based on a user’s theme:
1<apex:page>
2    <apex:pageBlock title="My Content" rendered="{!$User.UITheme == 'Theme2'}">
3        // this is the old theme...
4    </apex:pageBlock>
5
6    <apex:pageBlock title="My Content" rendered="{!$User.UITheme == 'Theme3'}">
7       // this is the classic theme ...
8    </apex:pageBlock>
9</apex:page>