Skip to main content

Visualforce actionPoller Component

About Us
Published by admin
24 March 2016
79

A timer that sends an AJAX request to the server according to the time interval that you specify. Each request can result in a full or partial page update. This component is an alternative to using setInterval (js).

In attribute action some controller method should be put. For this you must use standard syntax, for example, action="{!someAction}". If an action is not specified, the page simply refreshes.

Attributes enabled and rendered have the same function. With the help of them you can turn your actionPoller on or off.

Id is an identifier that allows the component to be referenced by other components in the page.

Attribute interval sets the time interval between AJAX update requests, in seconds. This value must be 5 seconds or greater, and if not specified, it defaults to 60 seconds. Note that the interval is only the amount of time between update requests. Once an update request is sent to the server, it enters a queue and can take additional time to process and display on the client.

Into attribute oncomplete you can put the JavaScript, which will be invoked when the result of an AJAX update request completes on the client.

Into attribute onsubmit you can put the JavaScript, which will be invoked before an AJAX update request has been sent to the server.

In attribute reRender you can put Id of one or more components that will be redrawn, when the result of an AJAX update request returns to the client. This value can be a single ID, a comma-separated list of IDs, or a merge field expression for a list or collection of IDs.

In attribute status you can put Id of an associated component that displays the status of an AJAX update request.

You can use attribute timeout, if you need your request to last no more time than it is required. Value of this attribute should be entered in milliseconds.

It is a good practice to make action methods used by <apex:actionPoller> lightweight, to avoid performing DML and to avoid using this component with enhanced lists. <apex:actionPoller> refreshes the connection regularly, keeping login sessions alive. A page with <apex:actionPoller> on it won't time out due to inactivity.

Visualforce actionPoller Component


image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026