Component Description
The WOToOneRelationship component displays a set of possible
destination objects of an enterprise object's to-one relationship,
allows the user to select one of the destination objects, and sets
the enterprise object's relationship accordingly. It displays
the possible destination objects of the relationship in a browser,
a popup list, or as a set of radio buttons. This component must
be embedded within a WOForm.
Synopsis
WOToOneRelationship { [uiStyle="radio"|"popup"|"browser";]
sourceObject=anObject;
sourceEntityName=aString;
relationshipKey=aString; [destinationDisplayKey=aString;]
[isMandatory=aBoolean;]
[maxColumns=aNumber;] [size=aNumber;]
[dataSource=aDataSource;]
};
Bindings
- uiStyle
- The type of user interface (radio buttons, popup list,
or browser.) Defaults to "radio" when the WOToOneRelationship
component displays fewer than five objects. Defaults to "popup"
when the component displays between five and twenty objects. Defaults
to "browser" when the component displays more than twenty
objects.
- sourceObject
- The enterprise object whose relationship is edited.
A display group's
queryMatch dictionary is
also a valid source object. This allows you to query for objects
having a particular to-one relationship.
- sourceEntityName
- The name of the entity that is modified.
- relationshipKey
- The name of the relationship that is modified.
- destinationDisplayKey
- A displayable attribute of the relationship's destination
objects. Defaults to "
userPresentableDescription".
- isMandatory
- A flag to indicate that a selection is necessary. Defaults
to
NO.
- maxColumns
- The maximum number of columns in the radio button array.
Used only when the user interface style is "
radio".
- size
- The maximum number of rows in the browser. Used only
when the user interface style is "
browser".
- dataSource
- A data source for the relationship's destination objects.
By default, the WOToOneRelationship component creates an EODatabaseDataSource
containing all possible destination objects. However, if you want
to limit the number of destination objects the user can choose,
you can create your own EODatabaseDataSource that has a subset of the
possible destination objects and bind it to this attribute.