Element: <oj-combobox-many>

Slots

JET elements can have up to two types of child content:

• Any child element with a slot attribute will be moved into that named slot, e.g. <span slot='startIcon'>...</span>. All supported named slots are documented below. Child elements with unsupported named slots will be removed from the DOM.
• Any child element lacking a slot attribute will be moved to the default slot, also known as a regular child. This is documented under the "Default" heading below.

Default

The <oj-combobox-many> element accepts oj-options as children. See the oj-option doc for details about accepted children and slots.

Example

Initialize the Combobox with child content specified:

<oj-combobox-many>
  <oj-option value="option1">Option1</oj-option>
</oj-combobox-many>

contextMenu

The contextMenu slot is set on the oj-menu within this element. This is used to designate the JET Menu that this component should launch as a context menu on right-click, Shift-F10, Press & Hold, or component-specific gesture. If specified, the browser's native context menu will be replaced by the JET Menu specified in this slot.

The application can register a listener for the Menu's ojBeforeOpen event. The listener can cancel the launch via event.preventDefault(), or it can customize the menu contents by editing the menu DOM directly, and then calling refresh() on the Menu.

To help determine whether it's appropriate to cancel the launch or customize the menu, the ojBeforeOpen listener can use component API's to determine which table cell, chart item, etc., is the target of the context menu. See the JSDoc and demos of the individual components for details.

Keep in mind that any such logic must work whether the context menu was launched via right-click, Shift-F10, Press & Hold, or component-specific touch gesture.

Example

Initialize the component with a context menu:

<oj-some-element>
    <-- use the contextMenu slot to designate this as the context menu for this component -->
    <oj-menu slot="contextMenu" style="display:none" aria-label="Some element's context menu">
...
    </oj-menu>
</oj-some-element>

Attributes

async-validators :Array.<oj.AsyncValidator.<V>>

List of asynchronous validators used by the component when performing validation. Use async-validators when you need to perform some validation work on the server. Otherwise, use validators, which are synchronous.

Each item in the Array is an instance that duck types oj.AsyncValidator. Implicit validators created by a component when certain attributes are present (e.g. required attribute) are separate from validators specified through the async-validators attribute and the validators attribute. At runtime when the component runs validation, it combines the implicit validators with the list specified through the validators attribute and also the list specified through the async-validators attribute. Error messages are shown as soon as each async validator returns; we do not wait until all the async validators finish to show errors. If the component's valid state changes for the worse, it is also updated as each validator returns so valid will be invalidShown as soon as the first validator has an Error.

It is recommended that you show the value you are validating in the error message because if the async operation takes a while, the user could be typing in a new value when the error message comes back and might be confused what value the error is for. However, if the user enters a new value (like presses Enter or Tab), a new validation lifecycle will start and validation errors for the previous value will not be shown to the user. If you need to format the value for the error message, you can use oj.IntlConverterUtils.getConverterInstance(converterOption) to get the converter instance, then call converter.format(value).

Hints exposed by async-validators and validators are shown in the notewindow by default, or as determined by the 'validatorHint' property set on the display-options attribute.

Since async validators are run asynchronously, you should wait on the BusyContext before you check valid property or the value property. Alternatively you can add a callback to the onValidChanged or ojValueChanged events.

The steps performed always, running validation and clearing messages is the same as for the validators attribute.

Default Value:

• []

Names

Item	Name
Property	asyncValidators
Property change event	asyncValidatorsChanged
Property change listener attribute (must be of type function)	on-async-validators-changed

Examples

Create an Object that duck-types the oj.AsyncValidator interface. Bind the Object to the JET form component's async-validators attribute. The validator's 'validate' method will be called when the user changes the input.

 self.asyncValidator1 = {
   // required validate method
   'validate': function(value) {
     return new Promise(function(resolve, reject) {
       var successful = someBackendMethod();
       if (successful) {
         resolve(true);
       } else {
         reject(new Error('The amount of purchase is too high. It is ' + value));
       }
     });
   },
   // optional hint attribute. hint shows up when user sets focus to input.
   'hint': new Promise(function (resolve, reject) {
     var formattedMaxPurchase = getSomeBackendFormattedMaxPurchase();
     resolve(maxPurchase + " is the maximum.");
   });
 };
 -- HTML --
 <oj-combobox-many async-validators="[[[asyncValidator1]]]"></oj-combobox-many>

Initialize the component with multiple AsyncValidator duck-typed instances:

-- HTML --
<oj-combobox-many
                  async-validators="[[[asyncValidator1, asyncValidator2]]]"></oj-combobox-many>

Get or set the asyncValidators property after initialization:

// getter
var validators = myComp.asyncValidators;

// setter
var myValidators = [{
'validate' : function(value) {
  return new Promise(function(resolve, reject) {
  // mock server-side delay
  setTimeout(function () {
    if (value === "pass" || value === "another pass") {
      resolve(true);
    } else {
      reject(new Error("value isn't 'pass' or 'another pass'. It is " + value.));
    }
  },10);
  });
}
}];
myComp.asyncValidators = myValidators;

converter :(oj.Converter.<any>|oj.Validation.RegisteredConverter)

A converter instance that duck types oj.Converter. Or an object literal containing the following properties.

When converter property changes due to programmatic intervention, the element performs various tasks based on the current state it is in.

Steps Performed Always

• Any cached converter instance is cleared and new converter created. The converter hint is pushed to messaging. E.g., notewindow displays the new hint(s).

Running Validation

• if element is valid when converter property changes, the display value is refreshed.
• if element is invalid and is showing messages when converter property changes, then all messages generated by the element are cleared and full validation run using its current display value.
  • if there are validation errors, then value property is not updated, and the errors are shown. The display value is not refreshed in this case.
  • if no errors result from the validation, value property is updated; page author can listen to the valueChanged event on the value property to clear custom errors. The display value is refreshed with the formatted value provided by converter.
• if element is invalid and has deferred messages when converter property changes, then the display value is refreshed with the formatted value provided by converter.

Clearing Messages

• When element messages are cleared in the cases described above, messages created by the element are cleared.
• messages-custom property is not cleared. Page authors can choose to clear it explicitly when setting the converter property.

Properties:

Name	Type	Argument	Description
type	string		the conveter type registered with the oj.ConverterFactory. Supported type is 'number'. See oj.ConverterFactory for details. E.g., {converter: {type: 'number'}
options	Object	<optional>	optional Object literal of options that the converter expects. See oj.IntlNumberConverter for options supported by the number converter. E.g., {converter: {type: 'number', options: {style: 'decimal'}}

Default Value:

• null

Names

Item	Name
Property	converter
Property change event	converterChanged
Property change listener attribute (must be of type function)	on-converter-changed

(nullable) described-by :string

It is used to establish a relationship between this component and another element. Typically this is not used by the application developer, but by the oj-label custom element's code. One use case is where the oj-label custom element code writes described-by on its form component for accessibility reasons. To facilitate correct screen reader behavior, the described-by attribute is copied to the aria-describedby attribute on the component's dom element.

Since:

• 4.0.0

Names

Item	Name
Property	describedBy
Property change event	describedByChanged
Property change listener attribute (must be of type function)	on-described-by-changed

Examples

Initialize component with the described-by attribute specified:

<oj-some-element described-by="someId"></oj-some-element>

Get or set the describedBy property after initialization:

// getter
var descById = myComp.describedBy;

// setter
myComp.describedBy = "someId";

disabled :boolean

Whether the component is disabled. The default is false.

When the disabled property changes due to programmatic intervention, the component may clear messages and run validation in some cases.

• when a required component is initialized as disabled value="{{currentValue}}" required disabled, deferred validation is skipped.
• when a disabled component is enabled,
  • if component is invalid and showing messages then all component messages are cleared, and full validation run using the display value.
    • if there are validation errors, they are shown.
    • if no errors result from the validation, the value property is updated. Page authors can listen to the onValueChanged event to clear custom errors.
  • if component is valid and has no errors then deferred validation is run.
    • if there is a deferred validation error, then the valid property is updated.
  • if component is invalid and deferred errors then component messages are cleared and deferred validation re-run.
    • if there is a deferred validation error, then the valid property is updated.
• when enabled component is disabled then no validation is run and the component appears disabled.

Default Value:

• false

Since:

• 0.7

Names

Item	Name
Property	disabled
Property change event	disabledChanged
Property change listener attribute (must be of type function)	on-disabled-changed

Examples

Initialize component with disabled attribute:

<oj-some-element disabled></oj-some-element>

Get or set the disabled property after initialization:

// getter
var disabled = myComp.disabled;

// setter
myComp.disabled = false;

display-options :Object

Display options for auxilliary content that determines where it should be displayed in relation to the component.

The types of messaging content for which display options can be configured include converterHint, helpInstruction, messages, and validatorHint.
The display options for each type is specified either as an array of strings or a string. When an array is specified the first display option takes precedence over the second and so on.

When display-options changes due to programmatic intervention, the component updates its display to reflect the updated choices. For example, if 'help.instruction' property goes from 'notewindow' to 'none' then it no longer shows in the notewindow.

A side note: help.instruction and message detail text can include formatted HTML text, whereas hints and message summary text cannot. If you use formatted text, it should be accessible and make sense to the user if formatting wasn't there. To format the help.instruction, you could do this:

<html>Enter <b>at least</b> 6 characters</html>

Since:

• 0.7

Names

Item	Name
Property	displayOptions
Property change event	displayOptionsChanged
Property change listener attribute (must be of type function)	on-display-options-changed

Examples

Override default values for display-options for one component:

// In this example, the display-options are changed from the defaults.
// The 'converterHint' is none, the 'validatorHint' is none and the 'helpInstruction' is none,
// so only the 'messages' will display in its default state.
//
<oj-some-element display-options='{"converterHint": "none",
                                    "validatorHint": "none",
                                    "helpInstruction": "none"}'></oj-some-element>

Get or set the displayOptions property after initialization:

// Get one subproperty
var hint = myComp.displayOptions.converterHint;

// Set one, leaving the others intact. Use the setProperty API for 
// subproperties so that a property change event is fired.
myComp.setProperty("displayOptions.converterHint", "none");

// get all
var options = myComp.displayOptions;

// set all.  Must list every resource key, as those not listed are lost.
myComp.displayOptions = {converterHint: "none", validatorHint: "none", helpInstruction: "none"};

display-options.converter-hint :(Array.<('placeholder'|'notewindow'|'none')>|'placeholder'|'notewindow'|'none')

Display options for auxilliary converter hint text that determines where it should be displayed in relation to the component. When there is already a placeholder set on the component, the converter hint falls back to display type of 'notewindow'.

Default Value:

• ['placeholder','notewindow']

Since:

• 0.7

Names

Item	Name
Property	displayOptions.converterHint

display-options.help-instruction :(Array.<('notewindow'|'none')>|'notewindow'|'none')

Display options for auxilliary help instruction text that determines where it should be displayed in relation to the component.

Default Value:

• ['notewindow']

Since:

• 0.7

Names

Item	Name
Property	displayOptions.helpInstruction

display-options.messages :(Array.<('inline'|'notewindow'|'none')>|'inline'|'notewindow'|'none')

Display options for auxilliary message text that determines where it should be displayed in relation to the component.

Default Value:

• ['inline']

Since:

• 0.7

Names

Item	Name
Property	displayOptions.messages

display-options.validator-hint :(Array.<('notewindow'|'none')>|'notewindow'|'none')

Display options for auxilliary validator hint text that determines where it should be displayed in relation to the component.

Default Value:

• ['notewindow']

Since:

• 0.7

Names

Item	Name
Property	displayOptions.validatorHint

help :Object

Form component help information.

The properties supported on the help option are:

Properties:

Name	Type	Argument	Description
instruction	string	<optional>	this represents advisory information for the component The default value is null.

Since:

• 0.7

Names

Item	Name
Property	help
Property change event	helpChanged
Property change listener attribute (must be of type function)	on-help-changed

help.instruction :string

Represents advisory information for the component, such as would be appropriate for a tooltip.

When help.instruction is present it is by default displayed in the notewindow, or as determined by the 'helpInstruction' property set on the displayOptions attribute. When the help.instruction property changes the component refreshes to display the updated information.

JET takes the help instruction text and creates a notewindow with the text. The help instruction only shows up as a tooltip on mouse over, not on keyboard and not in a mobile device. So help instruction would only be for text that is not important enough to show all users, or for text that you show the users in another way as well, like in the label. Also you cannot theme the native browser's title window like you can the JET notewindow, so low vision users may have a hard time seeing it. For these reasons, the JET EditableValue components do not use the HTML's title attribute.

To include formatted text in the help.instruction, format the string using html tags. For example the help.instruction might look like:

<oj-some-element help.instruction="<html>Enter <b>at least</b> 6 characters</html>"></oj-some-element>

If you use formatted text, it should be accessible and make sense to the user if formatting wasn't there.

Default Value:

• ""

Since:

• 4.0.0

Names

Item	Name
Property	help.instruction

Examples

Initialize the component with the help.instruction sub-attribute:

<oj-some-element help.instruction="some tooltip"></oj-some-element>
 

Get or set the help.instruction property after initialization:

// Get one subproperty
var instr = myComp.help.instruction;

// Set one subproperty, leaving the others intact. Use the setProperty API for 
// subproperties so that a property change event is fired.
myComponent.setProperty('help.instruction', 'some new value');

// Get all
var values = myComponent.help;

// Set all.  Must list every resource key, as those not listed are lost.
myComponent.help = {
  instruction: 'some new value'
};

help-hints :Object

Represents hints for oj-form-layout element to render help information on the label of the editable component.

This is used only if the editable component is added as a direct child to an oj-form-layout element, and the labelHint property is also specified.

The helpHints object contains a definition property and a source property.

• definition - hint for help definition text.
• source - hint for help source URL.

Since:

• 4.1.0

Names

Item	Name
Property	helpHints
Property change event	helpHintsChanged
Property change listener attribute (must be of type function)	on-help-hints-changed

Examples

Initialize the component with help hints:

<!-- Using dot notation -->
<oj-some-element help-hints.definition='some value' help-hints.source='some-url'></oj-some-element>

<!-- Using JSON notation -->
<oj-some-element help-hints='{"definition":"some value", "source":"some-url"}'></oj-some-element>

Get or set the helpHints property after initialization:

// Get one
var value = myComponent.helpHints.definition;

// Set one, leaving the others intact. Always use the setProperty API for 
// subproperties rather than setting a subproperty directly.
myComponent.setProperty('helpHints.definition', 'some new value');

// Get all
var values = myComponent.helpHints;

// Set all.  Must list every subproperty, as those not listed are lost.
myComponent.helpHints = {
    definition: 'some new value',
    source: 'some-new-url'
};

help-hints.definition :string

Hint for help definition text associated with the label.

It is what shows up when the user hovers over the help icon, or tabs into the help icon, or press and holds the help icon on a mobile device. No formatted text is available for help definition attribute.

See the help-hints attribute for usage examples.

Default Value:

• ""

Since:

• 4.1.0

Names

Item	Name
Property	helpHints.definition

help-hints.source :string

Hint for help source URL associated with the label.

If present, a help icon will render next to the label. For security reasons we only support urls with protocol http: or https:. If the url doesn't comply we ignore it and throw an error. Pass in an encoded URL since we do not encode the URL.

See the help-hints attribute for usage examples.

Default Value:

• ""

Since:

• 4.1.0

Names

Item	Name
Property	helpHints.source

label-hint :string

Represents a hint for oj-form-layout element to render a label on the editable component.

This is used only if the editable component is added as a direct child to an oj-form-layout element.

When labelHint is present it gives a hint to the oj-form-layout element to create an oj-label element for the editable component. When the labelHint property changes oj-form-layout element refreshes to display the updated label information.

Default Value:

• ""

Since:

• 4.1.0

Names

Item	Name
Property	labelHint
Property change event	labelHintChanged
Property change listener attribute (must be of type function)	on-label-hint-changed

Examples

Initialize the component with the label-hint attribute specified:

<oj-some-element label-hint='input label'></oj-some-element>

Get or set the labelHint property after initialization:

// getter
var value = myComponent.labelHint;

// setter
myComponent.labelHint = 'some new value'

messages-custom :Array.<Object>

List of messages an app would add to the component when it has business/custom validation errors that it wants the component to show. This allows the app to perform further validation before sending data to the server. When this option is set the message shows to the user right away. To clear the custom message, set messagesCustom back to an empty array.

Each message in the array is an object that duck types oj.Message. See oj.Message for details.

See the Validation and Messages section for details on when the component clears messagesCustom; for example, when full validation is run.

Default Value:

• []

Supports writeback:

• true

Since:

• 0.7

Names

Item	Name
Property	messagesCustom
Property change event	messagesCustomChanged
Property change listener attribute (must be of type function)	on-messages-custom-changed

Examples

Get or set the messagesCustom property after initialization:

// getter
var customMsgs = myComp.messagesCustom;

// setter
myComp.messagesCustom = [{summary:"hello", detail:"detail", severity:oj.Message.SEVERITY_LEVEL.INFO}];

Set messagesCustom when there are cross-validation errors:

--- HTML ---
<oj-some-element messages-custom='{{messagesCustom}}'></oj-some-element> 

--- ViewModel code ---
self.messagesCustom = ko.observableArray([]);

// the app's function that gets called when the user presses the submit button
if (!myValidateCrossValidationFields())
{
  // the app adds a custom messages to the component and it is displayed right away
  var msgs = [];
  msgs.push({'summary':'Cross field error', 'detail':'Field 1 needs to be less than Field 2'});
  self.messagesCustom(msgs);
}
else
{
  // submit data to the server
}

(nullable) min-length :number

The minimum number of characters a user must type before a options filtering is performed. Zero is useful for local data with just a few items, but a higher value should be used when a single character search could match a few thousand items.

Default Value:

• 0

Names

Item	Name
Property	minLength
Property change event	minLengthChanged
Property change listener attribute (must be of type function)	on-min-length-changed

Examples

Initialize the Combobox with the min-length attribute specified:

<oj-combobox-many min-length="2"></oj-combobox-many>

Get or set the minLength property after initialization:

// getter
var minLengthValue = myCombobox.minLength;

// setter
myCombobox.minLength = 3;

option-renderer :(function(Object)|null)

The renderer function that renders the content of an each option. The function should return one of the following:

• An Object with the following property:
  • insert: HTMLElement - A DOM element representing the content of the option.
• undefined: If the developer chooses to manipulate the option content directly, the function should return undefined.

The option-renderer decides only how the options' content has to be rendered in the drop down. Once an option is selected from the drop down, what value has to be displayed in the in input field is decided by the label field in the data object. See options and options-keys for configuring option label and value.

The context parameter passed to the renderer contains the following keys:

Key	Description
component	A reference to the Combobox element.
parent	The parent of the data item. The parent is null for root node.
index	The index of the option, where 0 is the index of the first option. In the hierarchical case the index is relative to its parent.
depth	The depth of the option. The depth of the first level children under the invisible root is 0.
leaf	Whether the option is a leaf or a group.
data	The data object for the option.
parentElement	The option label element. The renderer can use this to directly append content.

Default Value:

• null

Names

Item	Name
Property	optionRenderer
Property change event	optionRendererChanged
Property change listener attribute (must be of type function)	on-option-renderer-changed

Examples

Initialize the Combobox with a renderer:

<oj-combobox-many option-renderer="[[optionRenderer]]"></oj-combobox-many>

var optionRenderer = function(optionContext) {
           return optionContext['data']['FIRST_NAME'];
         };

options :(Array.<(oj.Option|oj.Optgroup)>|oj.DataProvider.<oj.Option>)

The option items for the Combobox. This attribute can be used instead of providing a list of oj-option or oj-optgroup child elements of the Combobox element. This attribute accepts:

1. an array of oj.Options and/or oj.Optgroups.
   • Use oj.Option for a leaf option.
   • Use oj.Optgroup for a group option.
2. a data provider of oj.Options. This data provider must implement oj.DataProvider.
   • value in oj.Option must be the row key in the data provider.
   • A maximum of 15 rows will be displayed in the dropdown. If more than 15 results are available then users need to filter further.
   • If the data provider supports the filter criteria capability including the contains ($co) operator, JET Combobox will request the data provider to do filtering. Otherwise it will filter internally.

Default Value:

• null

Names

Item	Name
Property	options
Property change event	optionsChanged
Property change listener attribute (must be of type function)	on-options-changed

Examples

Initialize the Combobox with the options specified:

<oj-combobox-many options="[[dataArray]]"></oj-combobox-many>

The options array should contain objects with value and label properties:

var dataArray = [{value: 'option1', label: 'Option 1'}, 
                 {value: 'option2', label: 'Option 2', disabled: true}, 
                 {value: 'option3', label: 'Option 3'}];

Initialize the Combobox with a data provider and data mapping:

<oj-combobox-many options="[[dataProvider]]"></oj-combobox-many>

Data mapping can be used if data doesn't have value and label properties.

// actual field names are "id" and "name"
var dataArray = [
           {id: 'Id 1', name: 'Name 1'},
           {id: 'Id 2', name: 'Name 2'},
           {id: 'Id 3', name: 'Name 3'}];

// In mapfields, map "name" to "label" and "id" to "value"
var mapFields = function(item) {
  var data = item['data'];
  var mappedItem = {};
  mappedItem['data'] = {};
  mappedItem['data']['label'] = data['name'];
  mappedItem['data']['value'] = data['id'];
  mappedItem['metadata'] = {'key': data['id']};
  return mappedItem;
}; 
var dataMapping = {'mapFields': mapFields};

var arrayDataProvider = new oj.ArrayDataProvider(dataArray, {keyAttributes: 'id'});
var dataProvider = new oj.ListDataProviderView(arrayDataProvider, {'dataMapping': dataMapping});

(nullable) options-keys :Object

Specify the key names to use in the options array.

Depending on options-keys means that the signature of the data does not match what is supported by the options attribute. When using Typescript, this would result in a compilation error.

Best practice is to use a oj.ListDataProviderView with data mapping as a replacement.

However, for the app that must fetch data from a REST endpoint where the data fields do not match those that are supported by the options attribute, you may use the options-keys with any dataProvider that implements oj.DataProvider interface.

Names

Item	Name
Property	optionsKeys
Property change event	optionsKeysChanged
Property change listener attribute (must be of type function)	on-options-keys-changed

Examples

Initialize the Combobox with options-keys specified. This allows the key names to be redefined in the options array.

<oj-combobox-xxx options-keys="[[optionsKeys]]"></oj-combobox-xxx>

var optionsKeys = {value : "state_abbr", label : "state_name"};

Redefine keys for data with subgroups.

var optionsKeys = {label : "regions", children : "states", 
                   childKeys : {value : "state_abbr", label : "state_name"}};

(nullable) options-keys.child-keys :Object

The object for the child keys.

Properties:

Name	Type	Argument	Description
label	string	<nullable>	The key name for the label.
value	string	<nullable>	The key name for the value.
children	string	<nullable>	The key name for the children.
childKeys	Object	<nullable>	The object for the child keys.

Default Value:

• null

Names

Item	Name
Property	optionsKeys.childKeys

(nullable) options-keys.children :string

The key name for the children.

Default Value:

• null

Names

Item	Name
Property	optionsKeys.children

(nullable) options-keys.label :string

The key name for the label.

Default Value:

• null

Names

Item	Name
Property	optionsKeys.label

(nullable) options-keys.value :string

The key name for the value.

Default Value:

• null

Names

Item	Name
Property	optionsKeys.value

(nullable) picker-attributes :Object

Attributes specified here will be set on the picker DOM element when it's launched.

The supported attributes are class and style, which are appended to the picker's class and style, if any. Note: 1) picker-attributes is not applied in the native theme. 2) setting this attribute after element creation has no effect.

Default Value:

• null

Names

Item	Name
Property	pickerAttributes
Property change event	pickerAttributesChanged
Property change listener attribute (must be of type function)	on-picker-attributes-changed

Examples

Initialize the combobox specifying a set of attributes to be set on the picker DOM element:

<oj-combobox-many picker-attributes="[[pickerAttributes]]"></oj-combobox-many>

var pickerAttributes = {
  "style": "color:blue;",
  "class": "my-class"
};

placeholder :string|null

The placeholder text to set on the element. The placeholder specifies a short hint that can be displayed before user selects or enters a value.

Default Value:

• null

Names

Item	Name
Property	placeholder
Property change event	placeholderChanged
Property change listener attribute (must be of type function)	on-placeholder-changed

Examples

Initialize the combobox with the placeholder attribute specified:

<oj-combobox-many placeholder="Please select ..."></oj-combobox-many>

Get or set the placeholder property after initialization:

// getter
var placeholderValue = myCombobox.placeholder;

// setter
myCombobox.placeholder = "Select values";

(readonly) raw-value :string

The rawValue is the read-only property for retrieving the current value from the input field in string form. The main consumer of rawValue is a converter.

The rawValue updates on the 'input' javascript event, so the rawValue changes as the value of the input is changed. If the user types in '1,200' into the field, the rawValue will be '1', then '1,', then '1,2', ..., and finally '1,200'. Then when the user blurs or presses Enter the value property gets converted and validated (if there is a converter or validators) and then gets updated if valid.

This is a read-only attribute so page authors cannot set or change it directly.

Supports writeback:

• true

Since:

• 1.2.1

Names

Item	Name
Property	rawValue
Property change event	rawValueChanged
Property change listener attribute (must be of type function)	on-raw-value-changed

Example

Get the rawValue property after initialization:

// getter
var rawValue = myCombobox.rawValue;

required :boolean

Whether the Combobox is required or optional. When required is set to true, an implicit required validator is created using the validator factory - oj.Validation.validatorFactory(oj.ValidatorFactory.VALIDATOR_TYPE_REQUIRED).createValidator(). Translations specified using the translations.required attribute and the label associated with the Combobox, are passed through to the options parameter of the createValidator method.

When required property changes due to programmatic intervention, the Combobox may clear messages and run validation, based on the current state it's in.

Running Validation

• if element is valid when required is set to true, then it runs deferred validation on the value. This is to ensure errors are not flagged unnecessarily.
• if element is invalid and has deferred messages when required is set to false, then element messages are cleared but no deferred validation is run.
• if element is invalid and currently showing invalid messages when required is set, then element messages are cleared and normal validation is run using the current display value.
  • if there are validation errors, then value property is not updated and the error is shown.
  • if no errors result from the validation, the value property is updated; page author can listen to the valueChanged event on the value property to clear custom errors.

Clearing Messages

• Only messages created by the element are cleared.
• messages-custom attribute is not cleared.

This property set to false implies that a value is not required to be provided by the user. This is the default. This property set to true implies that a value is required to be provided by user and the input's label will render a required icon. Additionally a required validator - oj.RequiredValidator - is implicitly used if no explicit required validator is set. An explicit required validator can be set by page authors using the validators attribute.

Default Value:

• false

Since:

• 0.7

See:

• #translations

Names

Item	Name
Property	required
Property change event	requiredChanged
Property change listener attribute (must be of type function)	on-required-changed

Examples

Initialize the Combobox with the required attribute:

<oj-combobox-many required="[[isRequired]]"></oj-combobox-many>

Get or set the required property after initialization:

// getter
var requiredValue = myCombobox.required;

// setter
myCombobox.required = true;

translations :Object|null

A collection of translated resources from the translation bundle, or null if this component has no resources. Resources may be accessed and overridden individually or collectively, as seen in the examples.

If the component does not contain any translatable resource, the default value of this attribute will be null. If not, an object containing all resources relevant to the component.

If this component has translations, their documentation immediately follows this doc entry.

Names

Item	Name
Property	translations
Property change event	translationsChanged
Property change listener attribute (must be of type function)	on-translations-changed

Examples

Initialize the component, overriding some translated resources and leaving the others intact:

<!-- Using dot notation -->
<oj-some-element translations.some-key='some value' translations.some-other-key='some other value'></oj-some-element>

<!-- Using JSON notation -->
<oj-some-element translations='{"someKey":"some value", "someOtherKey":"some other value"}'></oj-some-element>

Get or set the translations property after initialization:

// Get one
var value = myComponent.translations.someKey;

// Set one, leaving the others intact. Always use the setProperty API for 
// subproperties rather than setting a subproperty directly.
myComponent.setProperty('translations.someKey', 'some value');

// Get all
var values = myComponent.translations;

// Set all.  Must list every resource key, as those not listed are lost.
myComponent.translations = {
    someKey: 'some value',
    someOtherKey: 'some other value'
};

translations.filter-further :string

Text at the top of drop down when not all results are fetched and users need to filter further.

Default Value:

• "More results available, please filter further."

Names

Item	Name
Property	translations.filterFurther

translations.no-matches-found :string

No options found text for drop down.

Default Value:

• "No matches found"

Names

Item	Name
Property	translations.noMatchesFound

(nullable) translations.required :Object

Provides properties to customize the summary, detail and hint text used by the implicit required validator associated to any editable component that supports the required option.

See the translations attribute and required option for usage examples.

Since:

• 0.7

Names

Item	Name
Property	translations.required

(nullable) translations.required.hint :string

Hint text used by required validation error.

See the translations attribute for usage examples.

Default Value:

• ""

Since:

• 0.7

See:

• oj.RequiredValidator

Names

Item	Name
Property	translations.required.hint

(nullable) translations.required.message-detail :string

Message text that describes the details of the required validation error.

See the translations attribute for usage examples.

Default Value:

• ""

Since:

• 0.7

See:

• oj.RequiredValidator

Names

Item	Name
Property	translations.required.messageDetail

(nullable) translations.required.message-summary :string

Message text for summarizing a required validation error.

See the translations attribute for usage examples.

Default Value:

• ""

Since:

• 0.7

See:

• oj.RequiredValidator

Names

Item	Name
Property	translations.required.messageSummary

(readonly) valid :string

PREVIEW: This is a preview API. Preview APIs are production quality, but can be changed on a major version without a deprecation path.

The current valid state of the component. It is evaluated on initial render. It is re-evaluated

• after validation is run (full or deferred)
• when messagesCustom is updated, since messagesCustom can be added by the app developer any time.
• when showMessages() is called. Since showMessages() moves the hidden messages into messages shown, if the valid state was "invalidHidden" then it would become "invalidShown".
• when the required property has changed. If a component is empty and has required set, the valid state may be "invalidHidden" (if no invalid messages are being shown as well). If required property is removed, the valid state would change to "valid".

Note: New valid states may be added to the list of valid values in future releases. Any new values will start with "invalid" if it is an invalid state, "pending" if it is pending state, and "valid" if it is a valid state.

Supported Values:

Name	Type	Description
"invalidHidden"	string	The component has invalid messages hidden and no invalid messages showing. An invalid message is one with severity "error" or higher.
"invalidShown"	string	The component has invalid messages showing. An invalid message is one with severity "error" or higher.
"pending"	string	The component is waiting for the validation state to be determined. The "pending" state is set at the start of the convert/validate process.
"valid"	string	The component is valid

Supports writeback:

• true

Since:

• 4.2.0

Names

Item	Name
Property	valid
Property change event	validChanged
Property change listener attribute (must be of type function)	on-valid-changed

Examples

Get valid attribute, after initialization:

// Getter:
var valid = myComp.valid;

Set the on-valid-changed listener so you can do work in the ViewModel based on the valid property:

<oj-some-element id='username' on-valid-changed='[[validChangedListener]]'>
</oj-some-element>
<oj-some-element id='password' on-valid-changed='[[validChangedListener]]'>
</oj-some-element>
<oj-button disabled='[[componentDisabled]]' on-click='[[submit]]'>Submit</oj-button>
-- ViewModel --
self.validChangedListener = function (event) {
  var enableButton;
  var usernameValidState;
  var passwordValidState;
  
  // update the button's disabled state.
  usernameValidState = document.getElementById("username").valid;
  passwordValidState = document.getElementById("password").valid;
  
  // this updates the Submit button's disabled property's observable based
  // on the valid state of two components, username and password.
  // It is up to the application how it wants to handle the �pending� state 
  // but we think that in general buttons don�t need to be 
  // enabled / disabled based on the "pending" state.
  enableButton = 
   (usernameValidState !== "invalidShown") &&
   (passwordValidState !== "invalidShown");
  self.componentDisabled(!enableButton);;
};

validators :(Array.<(oj.Validator.<V>|oj.Validation.RegisteredValidator)>|null)

List of synchronous validators used by component along with asynchronous validators and the implicit component validators when performing validation. Each item is either an instance that duck types oj.Validator, or is an Object literal containing the properties listed below.

Implicit validators are created by the element when certain attributes are present. For example, if the required attribute is set, an implicit oj.RequiredValidator is created. At runtime when the component runs validation, it combines all the implicit validators with all the validators specified through this validators attribute and the async-validators attribute, and runs all of them.

Hints exposed by validators are shown in the notewindow by default, or as determined by the 'validatorHint' property set on the display-options attribute.

When validators property changes due to programmatic intervention, the element may decide to clear messages and run validation, based on the current state it is in.

Steps Performed Always

• The cached list of validator instances are cleared and new validator hints is pushed to messaging. E.g., notewindow displays the new hint(s).

Running Validation

• if element is valid when validators changes, element does nothing other than the steps it always performs.
• if element is invalid and is showing messages - messages-shown property is non-empty, when validators or async-validators
• if there are validation errors, then value property is not updated and the error is shown.
• if no errors result from the validation, the value property is updated; page author can listen to the valueChanged event on the value property to clear custom errors.

if element is invalid and has deferred messages when validators changes, it does nothing other than the steps it performs always.

Clearing Messages

• Only messages created by the element are cleared.
• messages-custom property is not cleared.

Default Value:

• []

Names

Item	Name
Property	validators
Property change event	validatorsChanged
Property change listener attribute (must be of type function)	on-validators-changed

Examples

Initialize the Combobox with validator object literal:

<oj-combobox-many validators="[[validators]]"></oj-combobox-many>

var validators = [{
    type: 'regExp', 
    options : {
      pattern: '[a-zA-Z0-9]{3,}'
    }
  }];

NOTE: oj.Validation.validatorFactory('numberRange') returns the validator factory that is used 
to instantiate a range validator for numbers.

Initialize the Combobox with multiple validator instances:

var validator1 = new MyCustomValidator({'foo': 'A'}); 
var validator2 = new MyCustomValidator({'foo': 'B'});
var validators = [validator1, validator2];
<oj-combobox-many validators="[[validators]]"></oj-combobox-many>

Get or set the validators property after initialization:

// get one
var validator = myCombobox.validators[0];

// get all
var validators = myCombobox.validators;

// set all
myCombobox.validators = myValidators;

value :Array.<any>

The value of the element. The value is an array with any type of items.

Supports writeback:

• true

Names

Item	Name
Property	value
Property change event	valueChanged
Property change listener attribute (must be of type function)	on-value-changed

Examples

Initialize the combobox with the value attribute specified:

<oj-combobox-many value="{{val}}"></oj-combobox-many>

var val = ['option1', 'option2'];

Get or set the value property after initialization:

// getter
var value = myCombobox.value;

// setter
myCombobox.value = ["option1", "option2"];

value-options :Array<{value: any, label?: string}> | null

The valueOptions is similar to the value, but is an array of Objects and each Object contains both a value and display label. The value and valueOptions are kept in sync. If initially both are set, the selected values in the value attribute has precedence.

Note: There may be a performance gain if the options attribute is a data provider and the valueOptions is initially set then its labels are used before the real data is fetched. If valueOptions is not specified or one of the selected value is missing, then the labels will be fetched from the data provider.

Properties:

Name	Type	Argument	Description
value	any		a current value of JET Combobox
label	string	<optional>	display label of value above. If missing, String(value) is used.

Default Value:

• null

Supports writeback:

• true

Names

Item	Name
Property	valueOptions
Property change event	valueOptionsChanged
Property change listener attribute (must be of type function)	on-value-options-changed

Examples

Initialize the Combobox with the value-options attribute specified:

<oj-combobox-many value-options="[[optionsArray]]"></oj-combobox-many>

Array of Objects with value and label properties:

var optionsArray = [{'value': 'val1', 'label': 'Label 1'}, 
                    {'value': 'val2', 'label': 'Label 2'}];

Get or set the valueOptions property after initialization:

// getter
var valueOptions = myCombobox.valueOptions;

// setter
myCombobox.valueOptions = optionsArray;

Events

ojAnimateEnd

Triggered when a default animation has ended.

Properties:

All of the event payloads listed below can be found under event.detail.

Name	Type	Description
action	string	The action that triggers the animation. Supported values are: "inline-open" - when an inline message container opens or increases in size "inline-close" - when an inline message container closes or decreases in size "notewindow-open" - when a note window opens "notewindow-close" - when a note window closes
element	Element	The element being animated.

Since:

• 4.0.0

Examples

Define an event listener for the ojAnimateEnd event to add any processing after the end of "inline-open" animation:

var listener = function( event )
{
  // Check if this is the end of "inline-open" animation for inline message
  if (event.detail.action == "inline-open") {
    // Add any processing here
  }
};

Specify an ojAnimateEnd listener via the DOM attribute:

<oj-combobox-many on-oj-animate-end='[[listener]]'></oj-combobox-many>

Specify an ojAnimateEnd listener via the JavaScript property:

myComboboxMany.onOjAnimateEnd = listener;

Add an ojAnimateEnd listener via the addEventListener API:

myComboboxMany.addEventListener('ojAnimateEnd', listener);

ojAnimateStart

Triggered when a default animation is about to start on an element owned by the component.

The default animation can be cancelled by calling event.preventDefault, followed by a call to event.detail.endCallback. event.detail.endCallback should be called immediately after event.preventDefault if the application merely wants to cancel animation, or it should be called when the custom animation ends if the application is invoking another animation function. Failure to call event.detail.endCallback may prevent the component from working properly.

For more information on customizing animations, see the documentation of oj.AnimationUtils.

The default animations are controlled via the theme (SCSS) :

// default animations for "notewindow" display option
$noteWindowOpenAnimation: (effect: "zoomIn", transformOrigin: "#myPosition") !default;
$noteWindowCloseAnimation: (effect: "none") !default;

// default animations for "inline" display option
$messageComponentInlineOpenAnimation: (effect: "expand", startMaxHeight: "#oldHeight") !default;
$messageComponentInlineCloseAnimation: (effect: "collapse", endMaxHeight: "#newHeight") !default;

Properties:

All of the event payloads listed below can be found under event.detail.

Name	Type	Description
action	string	The action that triggers the animation. Supported values are: "inline-open" - when an inline message container opens or increases in size "inline-close" - when an inline message container closes or decreases in size "notewindow-open" - when a note window opens "notewindow-close" - when a note window closes
element	Element	The element being animated.
endCallback	function():void	If the event listener calls event.preventDefault to cancel the default animation, it must call the endCallback function when it finishes its own animation handling and any custom animation has ended.

Since:

• 4.0.0

Examples

Define an event listener for the ojAnimateStart event to override the default "inline-open" animation:

var listener = function( event )
  {
    // Change the "inline-open" animation for inline message
    if (event.detail.action == "inline-open") {
      // Cancel default animation
      event.preventDefault();
      // Invoke new animation and call endCallback when the animation ends
      oj.AnimationUtils.fadeIn(event.detail.element).then(event.detail.endCallback);
    }
  };

Define an event listener for the ojAnimateStart event to cancel the default "notewindow-close" animation:

var listener = function( event )
  {
    // Change the "notewindow-close" animation for note window
    if (ui.action == "notewindow-close") {
      // Cancel default animation
      event.preventDefault();
      // Call endCallback immediately to indicate no more animation
      event.detail.endCallback();
  };

Specify an ojAnimateStart listener via the DOM attribute:

<oj-combobox-many on-oj-animate-start='[[listener]]'></oj-combobox-many>

Specify an ojAnimateStart listener via the JavaScript property:

myComboboxMany.onOjAnimateStart = listener;

Add an ojAnimateStart listener via the addEventListener API:

myComboboxMany.addEventListener('ojAnimateStart', listener);

Methods

getProperty(property) → {any}

Retrieves a value for a property or a single subproperty for complex properties.

Parameters:

Name	Type	Description
property	string	The property name to get. Supports dot notation for subproperty access.

Since:

• 4.0.0

Returns:

Type

any

Example

Get a single subproperty of a complex property:

var subpropValue = myComponent.getProperty('complexProperty.subProperty1.subProperty2');

refresh()

Refreshes the combobox.

This method does not accept any arguments.

reset() → {void}

Resets the component by clearing all messages and messages attributes - messagesCustom - and updates the component's display value using the attribute value. User entered values will be erased when this method is called.

Since:

• 0.7

Returns:

Type

void

Example

Reset component

myComp.reset(); 

setProperties(properties) → {void}

Performs a batch set of properties.

Parameters:

Name	Type	Description
properties	Object	An object containing the property and value pairs to set.

Since:

• 4.0.0

Returns:

Type

void

Example

Set a batch of properties:

myComponent.setProperties({"prop1": "value1", "prop2.subprop": "value2", "prop3": "value3"});

setProperty(property, value) → {void}

Sets a property or a single subproperty for complex properties and notifies the component of the change, triggering a [property]Changed event.

Parameters:

Name	Type	Description
property	string	The property name to set. Supports dot notation for subproperty access.
value	any	The new value to set the property to.

Since:

• 4.0.0

Returns:

Type

void

Example

Set a single subproperty of a complex property:

myComponent.setProperty('complexProperty.subProperty1.subProperty2', "someValue");

showMessages() → {void}

Takes all deferred messages and shows them. It then updates the valid property; e.g., if the valid state was "invalidHidden" before showMessages(), the valid state will become "invalidShown" after showMessages().

If there were no deferred messages this method simply returns.

Since:

• 0.7

Returns:

Type

void

Example

Display all messages including deferred ones.

myComp.showMessages();

validate() → {Promise}

PREVIEW: This is a preview API. Preview APIs are production quality, but can be changed on a major version without a deprecation path.

1. All messages are cleared, including custom messages added by the app.
2. If no converter is present then processing continues to next step. If a converter is present, the UI value is first converted (i.e., parsed). If there is a parse error then the messages are shown.
3. If there are no validators setup for the component the value option is updated using the display value. Otherwise all validators are run in sequence using the parsed value from the previous step. The implicit required validator is run first if the component is marked required. When a validation error is encountered it is remembered and the next validator in the sequence is run.
4. At the end of validation if there are errors, the messages are shown. If there were no errors, then the value option is updated.

Returns:

Promise resolves to "valid" if there were no converter parse errors and the component passed all validations. The Promise resolves to "invalid" if there were converter parse errors or if there were validation errors.

Type

Promise

Examples

Validate component using its current value.

myComp.validate();

Validate component and use the Promise's resolved state.

myComp.validate().then(
 function(result) {
   if(result === "valid")
   {
     submitForm();
   }
 });