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
Live Controller (Pilot)
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
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
Visualforce Remote Objects
Communicating Across the DOM with Lightning Message Service (Beta)
Best Practices
Standard Component Reference
Appendices
Glossary
PDF

Newer Version Available

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

Scope and Visibility of @RemoteAction Methods

Apex @RemoteAction methods must be static and either global or public.
Globally-exposed remote actions shouldn’t perform sensitive operations or expose non-public data. global remote actions may only call other global methods. public remote actions may not be used in global components, or otherwise used in a global scope. Scope escalation will result in a compiler error or, for references that are resolved at runtime, a runtime failure. The following table describes these restrictions in more detail:
@RemoteAction Scope Visualforce Page Non-Global Component Global Component iframe
Global Remote Method Allowed Allowed Allowed Allowed
Public Remote Method Allowed Allowed Error Error
When remote actions are accessed via markup that is included indirectly, via components or the <apex:include> or <apex:composition> tags, the scope of the remote method is carried forward into the top level container, that is, 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