DEV-501-II

An HTML input element of type text. Use this component to get user input for a controller method
that does not correspond to a field on a Salesforce object.
This component does not use Salesforce styling. Also, since it does not correspond to a field, or
any other data on an object, custom code is required to use the value the user inputs.

A custom Visualforce component. All custom component definitions must be wrapped inside a
single <apex:component> tag.

A Visualforce chart. Defines general characteristics of the chart, including size and data binding.

A single piece of data in an <apex:pageBlockSection> that takes up one column in one row. An
<apex:pageBlockSectionItem> component can include up to two child components. If no content is
specified, the column is rendered as an empty space. If one child component is specified, the
content spans both cells of the column. If two child components are specified, the content of the first is rendered in the left, "label" cell of the column, while the content of the second is rendered in
the right, "data" cell of the column.
Note that if you include an <apex:outputField> or an <apex:inputField> component in an
<apex:pageBlockSectionItem>, these components do not display with their label or custom help
text as they do when they are children of an <apex:pageBlockSectionItem>. Also note that
<apex:pageBlockSectionItem> components cannot be rerendered; rerender the child components
instead.

The standard detail page for a particular object, as defined by the associated page layout for the
object in Setup. This component includes attributes for including or excluding the associated
related lists, related list hover links, and title bar that appear in the standard Salesforce application
interface.

A component that creates an inline frame within a Visualforce page. A frame allows you to keep
some information visible while other information is scrolled or replaced.

Defines how labels are displayed. Depending on what component wraps it, <apex:chartLabel>
gives you options for affecting labels for bar and line series labels, pie chart segments, and axes
labels.
Note: This component must be enclosed by a data series component (<apex:barSeries>,
<apex:lineSeries>, or <apex:pieSeries>) or an <apex:axis> component.

A data series to be rendered as bars in a Visualforce chart. At a minimum you must specify the
fields in the data collection to use as X and Y values for each bar, as well as the X and Y axes to
scale against.
Note: This component must be enclosed within an <apex:chart> component. You can have
multiple <apex:barSeries> and <apex:lineSeries> components in a single chart.

This component provides inline editing support to <apex:outputField> and various container
components. In order to support inline editing, this component must also be within an <apex:form>
tag.
The <apex:inlineEditSupport> component can only be a descendant of the following tags:
<apex:dataList>
<apex:dataTable>
<apex:form>
<apex:outputField>
<apex:pageBlock>
<apex:pageBlockSection>
<apex:pageBlockTable>
<apex:repeat>
See also: the inlineEdit attribute of <apex:detail>

A link to a JavaScript library that can be used in the Visualforce page. When specified, this
component injects a script reference into the head element of the generated HTML page.
For performance reasons, you may simply want to use a JavaScript tag before your closing
<apex:page> tag, rather than this component.

A section of data within an <apex:pageBlock> component, similar to a section in a standard
Salesforce page layout definition.
An <apex:pageBlockSection> component consists of one or more columns, each of which spans
two cells: one for a field's label, and one for its value. Each component found in the body of an
<apex:pageBlockSection> is placed into the next cell in a row until the number of columns is
reached. At that point, the next component wraps to the next row and is placed in the first cell.
To add a field from a Salesforce object to an <apex:pageBlockSection>, use an <apex:inputField>
or <apex:outputField> component. Each of these components automatically displays with the
field's associated label. To add fields for variables or methods that are not based on Salesforce
object fields, or to customize the format of Salesforce object field labels, use an
<apex:pageBlockSectionItem> component. Each <apex:inputField>, <apex:outputField>, or
<apex:pageBlockSectionItem> component spans both cells of a single column.

A set of buttons that are styled like standard Salesforce buttons. This component must be a child
component of an <apex:pageBlock>.
Note that it is not necessary for the buttons themselves to be direct children of the
<apex:pageBlockButtons> component—buttons that are located at any level within an
<apex:pageBlockButtons> component are styled appropriately.

A text area input element. Use this component to get user input for a controller method that does
not correspond to a field on a Salesforce object, for a value that requires a text area.

A section of a Visualforce page that allows users to enter input and then submit it with an
<apex:commandButton> or <apex:commandLink>. The body of the form determines the data that
is displayed and the way it is processed. It's a best practice to verify that pages and custom
components use at most one <apex:form> tag.
As of API version 18.0, this tag can't be a child component of <apex:repeat>.

A single Visualforce page. All pages must be wrapped inside a single page component tag.

An HTML input element of type password. Use this component to get user input for a controller
method that does not correspond to a field on a Salesforce object, for a value that is masked as
the user types.

An area of a page that uses styling similar to the appearance of a Salesforce detail page, but
without any default content.

A button that is rendered as an HTML input element with the type attribute set to submit, reset, or
image, depending on the <apex:commandButton> tag's specified values. The button 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:commandButton> component must always be a child of an <apex:form> component.
See also: <apex:commandLink>

A Flash movie, rendered with the HTML object and embed tags.

An ordered or unordered list of values that is defined by iterating over a set of data. The body of
the <apex:dataList> component specifies how a single item should appear in the list. The data set
can include up to 1,000 items.

All messages that were generated for all components on the current page. If an <apex:message>
or <apex:messages> component is not included in a page, most warning and error messages are
only shown in the debug log.

A template component that provides content for an <apex:insert> component defined in a
Visualforce template page.
See also: <apex:composition>, <apex:insert>

The Log a Call publisher lets support agents who use Case Feed create logs for customer calls.
This component can only be used in organizations that have Case Feed, Chatter, and feed
tracking on cases enabled.

A component that displays the status of an AJAX update request. An AJAX request can either be
in progress or complete.

A label for an input or output field. Use this component to provide a label for a controller method
that does not correspond to a field on a Salesforce object.

A definition of an attribute on a custom component. The attribute tag can only be a child of a
component tag.
Note that you cannot define attributes with names like id or rendered. These attributes are
automatically created for all custom component definitions.

An HTML input element for a value that corresponds to a field on a Salesforce object. The
<apex:inputField> component respects the attributes of the associated field, including whether the
field is required or unique, and the user interface widget to display to get input from the user. For
example, if the specified <apex:inputField> component is a date field, a calendar input widget is
displayed. When used in an <apex:pageBlockSection>, <apex:inputField> tags always display
with their corresponding output label.
Note that if custom help is defined for the field in Setup, the field must be a child of an
<apex:pageBlock> or <apex:pageBlockSectionItem>, and the Salesforce page header must be
displayed for the custom help to appear on your Visualforce page. To override the display of
custom help, use the <apex:inputField> in the body of an <apex:pageBlockSectionItem>.
Consider the following when using JavaScript events with this tag:
For lookup fields, mouse events fire on both the text box and graphic icon
For multi-select picklists, all events fire, but the DOM ID is suffixed with _unselected for the left
box, _selected for the right box, and _right_arrow and _left_arrow for the graphic icons
For rich text areas, no events fire.

A link to a URL. This component is rendered in HTML as an anchor tag with an href attribute. Like
its HTML equivalent, the body of an <apex:outputLink> is the text or image that displays as the
link. To add query string parameters to a link, use nested <apex:param> components.

Displays text on a Visualforce page. You can customize the appearance of <apex:outputText>
using CSS styles, in which case the generated text is wrapped in an HTML <span> tag. You can
also escape the rendered text if it contains sensitive HTML and XML characters. This component
does take localization into account.
Use with nested param tags to format the text values, where {n} corresponds to the n-th nested
param tag. The value attribute supports the same syntax as the MessageFormat class in Java.
See the MessageFormat class JavaDocs for more information.
Warning:Encrypted custom fields that are embedded in the <apex:outputText> component display
in clear text. The <apex:outputText> component doesn't respect the View Encrypted Data
permission for users. To prevent showing sensitive information to unauthorized users, use the
<apex:outputField> tag instead.

A component that adds AJAX support to another component, allowing the component to be
refreshed asynchronously by the server when a particular event occurs, such as a button click or
mouseover.
See also: <apex:actionFunction>.

A graphic image, rendered with the HTML <img> tag.

A component that inserts a second Visualforce page into the current page. The entire page
subtree is injected into the Visualforce DOM at the point of reference and the scope of the
included page is maintained.
If content should be stripped from the included page, use the <apex:composition> component
instead.

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.

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.

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:

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.

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.

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.

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.

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.