Examples of Default Business Object Declarations

You can configure the extraction of business components from business objects, which are not exposed as part of an applet. You set default business object declarations under Settings in the Administration - Siebel Mobile, Application Administration view as described in the following examples.

Default Business Object Declaration Example 1: The following example of a default business object declaration extracts the Action and Action Employee business components where they occur with the visibility set to zero (0) by using the filter indicated:

Action|0||Action||Action Employee|

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. Business object filters normally give a query that is based on the primary business component in the business object. They force the extraction of any business components mentioned in the query when there is no corresponding applet within the application that can cause the extraction to occur.

Default Business Object Declaration Example 2: 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|

This declaration does not have an associated QBE clause. When this is the case, all of the records available to the user for the given visibility are extracted.

Note: Be careful when modifying a default business object setting for pick applets, and do so only with the support of a skilled configurator of Siebel Business Applications.