Developing Secure Code
Testing Components
getError()
getName()
getParam()
getParams()
getReturnValue()
getState()
isBackground()
setAbortable()
setBackground()
setCallback()
setParam()
setParams()
setStorable()
Previous PDF Versions
Action contains methods to work with JavaScript actions that you can use to communicate with Apex classes.
Returns an array of error objects for server-side actions only. Each error object has a message field. In any mode except PROD mode, each object also has a stack field, which is a list describing the execution stack when the error occurred.
Returns the name of an action.
Returns an action parameter value for a parameter name.
Returns the collection of parameters for an action.
Gets the return value of an Apex action. An Apex action can return any object containing serializable JSON data.
Returns the current state of an action. Check the state of the action in the callback after an Apex action completes.
Returns true if the action is enqueued in the background, false if it’s enqueued in the foreground.
Sets an action as abortable. If the component is not valid, abortable actions are not sent to the server. A component is automatically destroyed and marked invalid by the framework when it is unrendered. Actions not marked abortable are always sent to the server regardless of the validity of the component.
Sets the action to run as a background action. This cannot be unset. Background actions are usually long running and lower priority actions. A background action is useful when you want your app to remain responsive to a user while it executes a low priority, long-running action. A rough guideline is to use a background action if it takes more than five seconds for the response to return from the server.
Sets the callback function that is executed after an Apex action returns.
Sets a single parameter for an action. Use parameters to pass data to an Apex action.
Sets parameters for an action. Use parameters to pass data to an Apex action.
Marks an Apex action as storable to have its response stored in the framework’s client-side cache . Enhance your component’s performance by marking actions as storable (cacheable) to quickly show cached data from client-side storage without waiting for a server trip. If the cached data is stale, the framework retrieves the latest data from the server. Caching is especially beneficial for users on high latency, slow, or unreliable connections such as 3G networks.