Siebel Service Handheld Guide > Data Filtering for Siebel Handheld Applications > Recommendations for Managing Business Object Filters for Siebel Handheld Applications >
Examples of Default Business Object Declarations
You can set default business object declarations in the Administration - Mobile screen > Application Administration > Settings view, as described in the following examples.
"State Model" default business object setting:
State Model - Engine|0||State Model|[BusComp Name]="Expense"|State Model - Transition||State Model - State||State Model - Position|
The first three segments of the declaration are followed by a series of repeating BusCompName search specification pairs:
- Business object name
- Visibility Type
- (Siebel internal)
- Root business component name
- Search specification QBE for root BusComp records
- Child business component name
- Search specification QBE for child BusComp records (this must normally be empty, causing all children to be extracted)
- Grandchild business component name
- Search specification QBE for grandchild BusComp records (this must normally be empty, causing all grandchildren to be extracted), and so on.
The total number of fields must be at least 5 and must be an odd number.
This example default business object declaration results in an extraction of the Action and Action Employee business components where they occur with visibility 0 using the business object filter indicated. The business object filters are generally used only for extracting business components that do not correspond to any views or applets. Business object declarations identify specific business components within the business object to be extracted. The business object filters normally give a query based on the primary business component in the business object and force extraction of any business components mentioned in the query when there is no corresponding applet within the application that can cause the desired extraction to occur.
In the following example, the declaration is used to extract all the Price List Line Items under the Order Entry (Sales) business object.
DefaultBusObjs13= Order Entry (Sales)|0||Price List Item|
Note that this declaration lacks an associated QBE clause. When this is the case, all of the records available to the user for the given visibility are extracted.
Exercise caution when modifying a default business object setting for pick applets, and do so only with the support of a skilled Siebel configurator.
Use default business object declarations to force the extraction of data for a given business component in the context of a given business object and Visibility type. For more information about visibility designations, see Designating Visibility. The default business object extractions are performed in the first phase of data extraction.
You will most often use these declarations to extract additional data that is not extracted as part of the user interface extraction. This can be useful for business components that are referenced programmatically by other business components, but are not exposed in the user interface. The default business object declarations are used to enforce the extraction of a subset of data to the Handheld application that might not have been otherwise extracted or, most commonly, to filter the data downloaded for dynamic picklists or pick applets.
All pick data is not downloaded to the device due to the memory constraints on the device. Only pick data for fields that are editable is downloaded. Therefore, if you are doing a query on a pick field, you might not be able to display the picklist. When viewing a record in an applet, if a pick field is read-only, its pick button will be disabled. If users select a read-only field with a pick control, they receive the following error: No data available in picklist because field is read-only.