Salesforce DEV-501 Dumps

An HTML input element of type hidden, that is, an input element that is invisible to the user. Use
this component to pass variables from page to page.

A single column in a table. An <apex:column> component must always be a child of an
<apex:dataTable> or <apex:pageBlockTable> component.
Note that if you specify an sObject field as the value attribute for an <apex:column>, the
associated label for that field is used as the column header by default. To override this behavior,
use the headerValue attribute on the column, or the column's header facet.

A timer that sends an AJAX update request to the server according to a time interval that you
specify. The update request can then result in a full or partial page update. You should avoid using
this component with enhanced lists.

A link that executes an action defined by a controller, and then either refreshes the current page,
or navigates to a different page based on the PageReference variable that is returned by the
action. An <apex:commandLink> component must always be a child of an <apex:form>
component.
To add request parameters to an <apex:commandLink>, use nested <apex:param> components.

An area of a Visualforce page that demarcates which components should be processed by the
Force.com server when an AJAX request is generated. Only the components in the body of the
<apex:actionRegion> are processed by the server, thereby increasing the performance of the
page.

The email publisher lets support agents who use Case Feed compose and send email messages
to customers. You can customize this publisher to support email templates and attachments. This
component can only be used in organizations that have Case Feed and Email-to-Case enabled.
Ext JS versions less than 3 should not be included on pages that use this component.

A set of content that is grouped together, rendered with an HTML <span> tag, <div> tag, or
neither. Use an <apex:outputPanel> to group components together for AJAX refreshes.

A placeholder for content that is rendered in a specific part of the parent component, such as the
header or footer of an <apex:dataTable>.
An <apex:facet> component can only exist in the body of a parent component if the parent
supports facets. The name of the facet component must match one of the pre-defined facet names
on the parent component. This name determines where the content of the facet component is
rendered. Consequently, the order in which a facet component is defined within the body of a
parent component does not affect the appearence of the parent component.
See <apex:dataTable> for an example of facets.
Note: Although you can't represent an <apex:facet> directly in Apex, you can specify it on a
dynamic component that has the facet. For example:

An area of a page that includes content from a second template page. Template pages are
Visualforce pages that include one or more <apex:insert> components. The <apex:composition>
component names the associated template, and provides body for the template's <apex:insert>
components with matching <apex:define> components. Any content outside of an
<apex:composition> component is not rendered.

Defines an axis for a chart. Use this to set the units, scale, labeling, and other visual options for the axis. You can define up to four axes for a single chart, one for each edge.
Note: This component must be enclosed within an <apex:chart> component. This component is
only applicable to bar and line charts.