Using Paths and Expressions in Smart Client
Smart Client Run-Time Focus Objects
Smart Client Named Collections
Named Collection data path handler enables resolving an item by name within a named collection, such as
$Form:Controlset:Controls:MyDateControl
Named Collection Data Paths
A named element in a collection can be extracted from a java object by using two path items:
- The first identifies the collection,
- The second identifies the item’s name
An example data path is as follows:
$Dataset:DataModel:myDataModel
The $Dataset context type contains a collection that can be accessed by:
getDataModelByName("myDataModel")
The followings Smart Client runtime elements are implemented as Named Collections:
Example:
The following path resolves to a Grid column control in the current Form using Named Collection:
$Form:ControlSet:Control:caseOverviewGrid:GridColumn:caseTitleCol:ColumnControl
where:
- Form is the starting context and it specifies a UifForm context type
- ControlSet is a member in UifForm
- Control is the accessor collection name for ControlSet
- caseOverviewGrid is the name of the Grid control
- GridColumn is the accessor collection name for the caseOverviewGrid object
- caseTitleCol is the name of GridColumn inside the caseOverviewGrid grid control
- ColumnControl is a property in GridColumn which specifies the contained UifControl for the GridColumn control.
Example:
The following path resolves to a logical form called com.nextgen.GlobalUtils:
$Workspace:Form:com.nextgen.GlobalUtils
where
- Workspace is the starting context and it specifies a Workspace context type
- Form is the accessor collection name for Workspace
- com.nextgen.GlobalUtils is the name of the Form.
Data Path Contexts
Data Model, Data Provider
Form, Control, Action
Create Data Request Map
Choice List Action Request Map
Input, Workspace, Locale, WorkspaceForm
ContainingFormDataModel, OpenerFormDataModel, TopLevelFormDataModel, Form
ServiceInput, ServiceOutput, Bindable, Control, DataModel, Input, Relative