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
Using $Component to Reference Components from JavaScript
Using JavaScript Libraries with Visualforce
JavaScript Remoting for Apex Controllers
What Is JavaScript Remoting?
When to Use JavaScript Remoting
Adding JavaScript Remoting to a Visualforce Page
Declaring a Remote Method in Apex
Scope and Visibility of @RemoteAction Methods
Remote Methods and Inheritance
Declaring a Remote Method with Interface Parameters
Handling the Remote Response
Debugging JavaScript Remoting
JavaScript Remoting Limits and Considerations
JavaScript Remoting Example
Common Visualforce JavaScript Remoting API Validation Errors
Visualforce Remote Objects
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Standard Visualforce Component Reference
Appendices
PDF

Scope and Visibility of @RemoteAction Methods

Apex @RemoteAction methods must be static and either global or public.
Don’t use globally exposed remote actions to perform sensitive operations or to expose nonpublic data. Global remote actions can only call other global methods. You can’t use public remote actions in global components, or in a global scope. Scope escalation results in a compiler error, or for references that are resolved at runtime, a runtime failure. This table describes the restrictions.
@RemoteAction Scope Visualforce Page Non-Global Component Global Component iframe Access Across Packages
Global Remote Method Allowed Allowed Allowed Allowed Allowed
Public Remote Method Allowed Allowed Error Error Packages must share the namespace. Method must have the @namespaceAccessible annotation.

If a @RemoteAction method is in a managed package and used by Visualforce Remoting, it must have global visibility if user profile or permission set access is used.

Note

When remote actions are accessed via markup they are included indirectly via components, the <apex:include>, or the <apex:composition> tags. The scope of the remote method is carried forward into the top-level container (the top-level item in the inclusion hierarchy), which must abide by scope escalation rules.
Top-Level Container
@RemoteAction Accessed From Visualforce Page Non-Global Component Global Component iframe
Global Component Allowed Allowed Allowed Allowed
Non-Global Component Allowed Allowed Allowed only if non-global component doesn't include public remote methods. Allowed only if non-global component doesn't include public remote methods.
<apex:include> <apex:composition> Allowed within the same namespace; error if namespaces are different and the included page or its child hierarchy contains public remote methods. n/a n/a Error