<af:inputSearch>

Example header template:

In table mode, the template should have td tags for each column needed in the UI. The template should have th scope="row" tag if there is a need for a row header. The list mode templates don't have any such restriction.

a character used to gain quick access to the form element specified by the for, if set (or this component itself, if it is a "non-simple" form element). If the same access key appears in multiple locations in the same page of output, the rendering user agent will cycle among the elements accessed by the similar keys.

This attribute is sometimes referred to as the "mnemonic".

Note that the accessKey is triggered by browser-specific and platform-specific modifier keys. It even has browser-specific meaning. For example, Internet Explorer will set focus when you press Alt+<accessKey>. Firefox sets focus on some operating systems when you press Alt+Shift+<accessKey>. Firefox on other operating systems sets focus when you press Control+<accessKey>. Refer to your browser's documentation for how it treats access keys.

Indicates the search criteria.

Valid Values to be used in the tag:

• startsWith - Performs a per-word starts-with matching. i.e. if there are multiple words in an attribute, starts-with match is attempted on each of these words individually.
• contains - Standard contains matching. Contains matching scores the startsWith matches higher. i.e. startsWith matches are displayed before contains matches in the suggestions panel.
• attributeStartsWith - Performs a simple starts-with matching for each attribute value
• auto - Current implementation defaults auto to contains search

• data: The raw row data
• index: The index of the row in the collection fetched from the REST call
• key: The key value for the row

{
          'EmpNo': 1234,
          'Ename': 'Somename'
        }

the object passed to this method will be of format

{
          'data': {
            'EmpNo': 1234,
            'Ename': 'Somename'
          },
          'index': 24,
          'key': 1234
        }

Sample JS method:

function dependencyFiltering(rowObj, rowIndex)
        {
          return rowObj.data['dependentAttribute'] == parentComponentValue;
        }

Note: This method is not invoked when attempting server filtering. This filtering of collection is expected to be done on the server during server filtering

• They must start with a letter (as defined by the Character.isLetter() method) or underscore ( _ ).
• Subsequent characters must be letters (as defined by the Character.isLetter() method), digits as defined by the Character.isDigit() method, dashes ( - ), or underscores ( _ ). To minimize the size of responses generated by JavaServer Faces, it is recommended that component identifiers be as short as possible. If a component has been given an identifier, it must be unique in the namespace of the closest ancestor to that component that is a NamingContainer (if any).

For example, setting this attribute to "L&amp;abel" will set the label to "Label" and the access key to 'a'.

Parameters:

• {0} the label that identifies the component

Note: If the suggestions list is too long and will be paged, then filterParameters attribute will have to be configured on default searchSection with criteria type AdfRichInputSearch.CRITERIA_VALUE_EQUALS to obtain the full suggestion objects for the initial selected values.

For components with images, the shortDesc is often used to render an HTML alt attribute for the image. Please see the accessibility guidelines section for correct alt text usage of the shortDesc attribute.

shortDesc is also commonly used to render an HTML title attribute, which is used by user agents to display tooltip help text. In this case the behavior for the tooltip is controlled by the user agent, e.g. Firefox 2 truncates long tooltips. For form components, the shortDesc is displayed in a note window. For components that support the helpTopicId attribute and are not using the shortDesc as image alt text, it is recommended that helpTopicId is used instead of shortDesc as it is more flexible and provides more accessible descriptive text than the use of the title attribute.

e.g. If the component is being used for displaying (and filtering) employee details, Employee Number is a good candidate to be chosen as value attribute.