Salesforce Advanced Developer 501 - Visualforce Component Reference

Front 1

apex:actionFunction

Back 1

A component that provides support for invoking controller action methods directly from JavaScript code using an AJAX request. An <apex:actionFunction> component must be a child of an <apex:form> component.

Hint 1

action, focus, id, immediate, name, onbeforedomupdate, oncomplete, rendered, reRender, status, timeout

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_actionFunction.htm

Front 2

apex:actionPoller

Back 2

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.

Hint 2

action, enabled, id, interval, oncomplete, onsubmit, rendered, reRender, status, timeout

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_actionPoller.htm

Front 3

apex:actionRegion

Back 3

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.

Hint 3

id, immediate, rendered, renderRegionOnly

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_actionRegion.htm

Front 4

apex:actionStatus

Back 4

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

Hint 4

dir, for, id, lang, layout, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onstart, onstop, rendered, startStyle, startStyleClass, startText, stopStyle, stopStyleClass, stopText, style, styleClass, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_actionStatus.htm

Front 5

apex:actionSupport

Back 5

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>.

Hint 5

action, disabled, disableDefault, event, focus, id, immediate, onbeforedomupdate, oncomplete, onsubmit, rendered, reRender, status, timeout
http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_actionSupport.htm

Front 6

apex:attribute

Back 6

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.

Hint 6

access, assignTo, default, description, encode, id, name, required, type

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_attribute.htm

Front 7

apex:axis

Back 7

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.

Hint 7

dashSize, fields,grid, gridFill, id, maximum, minimum, position, rendered, title, type

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_axis.htm

Front 8

apex:barSeries

Back 8

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.

Hint 8

axis, highlight, id, orientation, rendered, showInLegend, tips, title, xField, yField

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_barSeries.htm

Front 9

apex:chart

Back 9

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

Hint 9

animate, border, data, height, id, legend, name, rendered, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_chart.htm

Front 10

apex:chartLabel

Back 10

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.

Hint 10

color, display, field, font, id, minMargin, orientation, rendered, rotate

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_chartLabel.htm

Front 11

apex:chartTips

Back 11

Defines tooltips which appear on mouseover of data series elements. This component offers more configuration options than the default tooltips displayed by setting the tips attribute of a data series component to true.
Note: This component must be enclosed by a data series component (<apex:barSeries>, <apex:lineSeries>, or <apex:pieSeries>).

Hint 11

height, id, labelField, rendered, trackmouse, valueField, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_chartTips.htm

Front 12

apex:column

Back 12

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.

Hint 12

breakBefore, colspan, dir, footerClass, footerValue, headerClass, headerValue, id, lang, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, rowspan, style, styleClass, title, value, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_column.htm

Front 13

apex:commandButton

Back 13

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>

Hint 13

accesskey, action, alt, dir, disabled, id, image, immediate, lang, onblur, onclick, oncomplete, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, reRender, status, style, styleClass, tabindex, timeout, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_commandButton.htm

Front 14

apex:commandLink

Back 14

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.

Hint 14

accesskey, action, charset, coords, dir, hreflang, id, immediate, lang, onblur, onclick, oncomplete, ondblckick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rel, rendered, reRender, rev, shape, status, style, styleClass, tabindex, target, timeout, title, type, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_commandLink.htm

Front 15

apex:component

Back 15

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

Hint 15

access, allowDML, controller, extensions, id, language, layout, rendered, selfClosing

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_component.htm

Front 16

apex:componentBody

Back 16

This tag allows a custom component author to define a location where a user can insert content into the custom component. This is especially useful for generating custom iteration components. This component is valid only within an <apex:component> tag, and only a single definition per custom component is allowed.

Hint 16

id, rendered

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_componentBody.htm

Front 17

apex:composition

Back 17

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.

Hint 17

rendered, template

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_composition.htm

Front 18

apex:dataList

Back 18

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.

Hint 18

dir, first, id, lang, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, rows, style, styleClass, title, type, value, var


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.

Front 19

apex:dataTable

Back 19

An HTML table that is defined by iterating over a set of data, displaying information about one item of data per row. The body of the <apex:dataTable> contains one or more column components that specify what information should be displayed for each item of data. The data set can include up to 1,000 items.

Hint 19

align, bgcolor, border, captionClass, captionStyle, cellpadding, cellspacing, columnClasses, columns, columnsWidth, dir, first, footerClass, frame, headerClass, id, lang, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onRowClick, onrowDblClick, onRowMouseDown, onRowMouseMove, onRowMouseOut, onRowMouseOver, onRowMouseUp, rendered, rowClasses, rows, rules, style, styleClass, summary, title, value, var, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_dataTable.htm

Front 20

apex:define

Back 20

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

Hint 20

name

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_define.htm

Front 21

apex:detail

Back 21

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.

Hint 21

id, inlineEdit, oncomplete, relatedList, relatedListLover, rendered, rerender, showChatter, subject, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_detail.htm

Front 22

apex:dynamicComponent

Back 22

This tag acts as a placeholder for your dynamic Apex components. It has one required parameter—componentValue—which accepts the name of an Apex method that returns a dynamic component.
The following Visualforce components do not have dynamic Apex representations:
<apex:actionRegion>
<apex:attribute>
<apex:component>
<apex:componentBody>
<apex:composition>
<apex:define>
<apex:dynamicComponent>
<apex:flash>
<apex:inputFile>
<apex:include>
<apex:insert>
<apex:pageMessage>
<apex:pageMessages>
<apex:variable>
<apex:vote>
Any non-<apex:> tag, like <chatter:>, <flow:>, <ideas:>, <knowledge:>, <messaging:>, or <site:>

Hint 22

componentValue, id, rendered

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_dynamicComponent.htm

Front 23

apex:emailPublisher

Back 23

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.

Hint 23

autoCollapseBody, bccVisibility, ccvisibility, emailBody, emailBodyFormat, emailBodyHeight, enableQuickText, entityId, expandableHeader, fromAddresses, fromVisibility, id, onSubmitFailure, onSubmitSuccess, rendered, reRender, sendButtonName, showAdditionalFields, showAttachments, showSendButton, showTemplates, subject, subjectVisibility, submitFunctionName, title, toAddresses, toVisibility, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_emailPublisher.htm

Front 24

apex:enhancedList

Back 24

The list view picklist for an object, including its associated list of records for the currently selected view. In standard Salesforce applications this component is displayed on the main tab for a particular object. This component has additional attributes that can be specified, such as the height and rows per page, as compared to <apex:listView>.
Note: When an <apex:enhancedList> is rerendered through another component's rerender attribute, the <apex:enhancedList> must be inside of an <apex:outputPanel> component that has its layout attribute set to "block". The <apex:enhancedList> component is not allowed on pages that have the attribute showHeader set to false. You can only have five <apex:enhancedList> components on a single page. Ext JS versions less than 3 should not be included on pages that use this component.

Hint 24

customizable, height, id, listId, oncomplete, rendered, reRender, rowsPerPage, type, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_enhancedList.htm

Front 25

apex:facet

Back 25

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:

Hint 25

name

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_facet.htm

Front 26

apex:flash

Back 26

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

Hint 26

flashvars, height, id, loop, play, rendered, src, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_flash.htm

Front 27

apex:form

Back 27

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>.

Hint 27

accept, acceptcharset, dir, enctype, forceSSL, id, lang, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onreset, onsubmit, prependId, rendered, style, styleClass, target, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_form.htm

Front 28

apex:iframe

Back 28

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.

Hint 28

frameborder, height, id, rendered, scrolling, src, title, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_iframe.htm

Front 29

apex:image

Back 29

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

Hint 29

alt, dir, height, id, ismap, lang, longdesc, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, style, styleClass, title, url, usemap, value, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_image.htm

Front 30

apex:include

Back 30

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.

Hint 30

id, pageName, rendered

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_include.htm

Front 31

apex:includeScript

Back 31

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.

Hint 31

id, project, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_includeScript.htm

Front 32

apex:inlineEditSupport

Back 32

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>

Hint 32

changedStyleClass, disabled, event, hideOnEdit, id, rendered, resetFunction, showOnEdit

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inlineEditSupport.htm

Front 33

apex:inputCheckbox

Back 33

An HTML input element of type checkbox. Use this component to get user input for a controller method that does not correspond to a field on a Salesforce object.

Hint 33

accesskey, dir, disabled, id, immediate, label, lang, onblur, onchange, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onselect, rendered, required, selected, style, styleClass, tabindex, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inputField.htm

Front 34

apex:inputField

Back 34

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.

Hint 34

id, label, onblur, onchange, onclick, ondblclcick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onselect, rendered, required, style, styleClass, taborderhint, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inputField.htm

Front 35

apex:inputFile

Back 35

A component that creates an input field to upload a file.
Note: The maximum file size that can be uploaded via Visualforce is 10 MB.

Hint 35

accept, accessKey, alt, contentType, dir, disabled, fileName, fileSize, id, lang, onblur, onchange, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, rendered, required, size, style, styleClass, tabindex, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inputFile.htm

Front 36

apex:inputHidden

Back 36

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.

Hint 36

id, immediate, rendered, required, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inputHidden.htm

Front 37

apex:inputSecret

Back 37

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.

Hint 37

accesskey, alt, dir, disabled, id, immediate, label, lang, maxlength, onblur, onchange, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseover, onmouseout, onmouseup, onselect, readonly, redisplay, rendered, required, size, style, styleClass, tabindex, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inputSecret.htm

Front 38

apex:inputText

Back 38

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.

Hint 38

accesskey, alt, dir, disabled, id, label, lang, manxlength, onblur, onchange, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, required, size, style, styleClass, tabindex, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inputText.htm

Front 39

apex:inputTextarea

Back 39

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.

Hint 39

accesskey, cols, dir, disabled, id, label, lang, onblur, onchange, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onselect, readonly, rendered, required, rickText, rows, style, styleClass, tabindex, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_inputTextarea.htm

Front 40

apex:insert

Back 40

A template component that declares a named area that must be defined by an <apex:define> component in another Visualforce page. Use this component with the <apex:composition> and <apex:define> components to share data between multiple pages.

Hint 40

name


A template component that declares a named area that must be defined by an <apex:define> component in another Visualforce page. Use this component with the <apex:composition> and <apex:define> components to share data between multiple pages.

Front 41

apex:legend

Back 41

Defines a chart legend. This component offers additional configuration options beyond the defaults used by the legend attribute of the <apex:chart> component.
Note: This component must be enclosed within an <apex:chart> component.

Hint 41

font, id, padding, position, rendered, spacing

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_legend.htm

Front 42

apex:lineSeries

Back 42

A data series to be rendered as connected points 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 point, 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.

Hint 42

axis, fill, highlight, id, markerFill, markerSize, markerType, rendered, showInlegend, tips, title, xField, yField

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_lineSeries.htm

Front 43

apex:listViews

Back 43

The list view picklist for an object, including its associated list of records for the currently selected view. In standard Salesforce applications this component is displayed on the main tab for a particular object.
See also: <apex:enhancedList>.

Hint 43

id, rendered, type

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_listViews.htm

Front 44

apex:logCallPublisher

Back 44

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.

Hint 44

autoCollapseBody, entityId, id, logCallBody, logCallBodyHeight, onSubmitFailure, onSubmitSuccess, rendered, reRender, showAdditionalFields, showSubmitButton, submitButtonName, submitFunctionName, title, width

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_logCallPublisher.htm

Front 45

apex:message

Back 45

A message for a specific component, such as a warning or error. 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.

Hint 45

dir, for, id, lang, rendered, style, styleClass, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_message.htm

Front 46

apex:messages

Back 46

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.

Hint 46

dir, globalOnly, id, lang, layout, rendered, style, styleClass, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_messages.htm

Front 47

apex:outputField

Back 47

A read-only display of a label and value for a field on a Salesforce object. An <apex:outputField> component respects the attributes of the associated field, including how it should be displayed to the user. For example, if the specified <apex:outputField> component is a currency field, the appropriate currency symbol is displayed. Likewise, if the <apex:outputField> component is a lookup field or URL, the value of the field is displayed as a link.
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:outputField> in the body of an <apex:pageBlockSectionItem>.
The Rich Text Area data type can only be used with this component on pages running Salesforce.com API versions greater than 18.0.

Hint 47

dir, id, label, lang, rendered, style, styleClass, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_outputField.htm

Front 48

apex:outputLabel

Back 48

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.

Hint 48

accesskey, dir, escape, for, id, lang, onblur, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, style, styleClass, tabindex, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_outputLabel.htm

Front 49

apex:outputLink

Back 49

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.

Hint 49

accesskey, charset, coords, dir, disabled, hreflang, id, lang, onblur, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rel, rendered, rev, shape, style, styleClass, tabindex, target, title, type, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_outputLink.htm

Front 50

apex:outputPanel

Back 50

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.

Hint 50

dir, id, lang, layout, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, style, styleClass, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_outputPanel.htm

Front 51

apex:outputText

Back 51

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.

Hint 51

dir, escape, id, label, lang, rendered, style, styleClass, title, value

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_outputText.htm

Front 52

apex:page

Back 52

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

Hint 52

action, apiVersion, cache, contentType, controller, docType, expires, extensions, id, label, language, name, pageStyle, readOnly, recordSetName, recordSetVar, renderAs, rendered, setup, showChat, showHeader, sidebar, standardController, standardStylesheets, tabStyle, title, wizard

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_page.htm

Front 53

apex:pageBlock

Back 53

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

Hint 53

dir, helpTitle, helpUrl, id, lang, mode, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseiup, rendered, tabStyle, title


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

Front 54

apex:pageBlockButtons

Back 54

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.

Hint 54

dir, id, lang, location, onclick, ondblclick, onkeydown, onkeypress, onkeyup onmousedonw, onmousemove, onmouseout, onmouseover, onmouseup, rendered, style, styleClass, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_pageBlockButtons.htm

Front 55

apex:pageblockSection

Back 55

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.

Hint 55

collapsible, columns, dir, id, lang, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, showHeader, title

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_pageBlockSection.htm

Front 56

apex:pageBlockSectionItem

Back 56

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.

Hint 56

dataStyle, dataStyleClass, dataTitle, dir, helpText, id, labelStyle, labelStyleClass, labelTitle, lang, onDataclick, onDatadblclick, onDatakeydown, onDatakeypress, onDatakeyup, onDatamousedown, onDatamousemove, onDatamouseout, onDatamouseover, onDatamouseup, onLabelclick, onLabeldblclick, onLabelkeydown, onLabelkeypress, onLabelkeyup, onLabelmousedown, onLabelmousemove, onLabelmouseout, onLabelmouseover, onLabelmouseup, rendered

http://www.salesforce.com/us/developer/docs/pages/Content/pages_compref_pageBlockSectionItem.htm