| Siebel CRM Siebel Mobile Guide: Disconnected Siebel Innovation Pack 2015, Rev. D E52427-01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM Siebel Mobile Guide: Disconnected Siebel Innovation Pack 2015, Rev. D E52427-01 |
|
Previous |
Next |
View PDF |
The following topics describe how to create and manage filters:
For server synchronization deployments, administrators can create business object and business component filters. Both application-level and user-level filters can be used in this deployment. The application-level filters are managed in the Administration - Siebel Mobile, Application Administration view. The user-level filters are managed in the Administration - Mobile, User Administration view. Changes to any filters will be effective on your next synchronization session, without having to restart the Siebel Application Object Manager's synchronization component for the mobile application. Filters are available to all users. Therefore, define the filters with the needs of all users in mind. For more information about creating filters, see
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.
Example 5-1 Default Business Object Declaration
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.
Example 5-2 Default Business Object Declaration
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. |
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. The default business object extractions are performed in the first phase of data extraction. For more information about visibility designations, see "Determining the Correct Visibility".
You use these declarations most often to extract additional data that is not extracted as part of the user-interface extraction. This feature 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 force the extraction of a subset of data to the mobile 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 mobile application because of 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, then you might not be able to display the picklist. If a pick field is read-only when viewing a record in an applet, then its pick button is disabled.
You must use the correct visibility designation in the default business object declarations. The visibility code entered must be the visibility that governs the data displayed for the business component within the context of the business object specified in the declaration. For example, the visibility code 3 corresponds to All Visibility, which is the visibility that applies to the Account business component when it is used in a pick applet.
To determine the correct visibility
Log in to Siebel Tools.
Examine the view and business component properties, and do the following:
When creating a default business object declaration to restrict the volume of data extracted for a pick applet, begin by examining the Popup Visibility field in Business Component Properties.
Cross-reference the visibility type with the visibility code in Table 5-7, and enter the appropriate visibility code in the declaration.
If the Popup Visibility type for the business component is null, then the default value is All.
Table 5-7 summarizes the Popup Visibility types and the corresponding visibility codes.
Table 5-7 Popup Visibility Types and Codes
| Popup Visibility Type | Visibility Code |
|---|---|
|
Sales Representative |
0 |
|
Manager |
1 |
|
Personal |
2 |
|
All |
3 |
|
None |
4 |
|
Organization |
5 |
|
Contact |
6 |
|
Note: Do not use the Group, Catalog, or Sub Organization Popup Visibility types. These visibility types are not supported in the Siebel Mobile disconnected application. |
If the Popup Visibility type is not sufficiently restrictive (for example, All Visibility), then this setting can lead to a large number of records being extracted when the picklist is processed during synchronization. Making the pop-up visibility more restrictive reduces the number of records extracted for picklists. The OverridePopupVisibility user property for an applet overrides the Popup Visibility type on a business component. Use this property when the visibility that you want differs from the business component's Popup Visibility type, and you do not want to change the Popup Visibility type. If several picklists use the same business component, then you can also use the OverridePopupVisibility user property to vary the visibility of the picklists in the different applets.
Restrictions That Apply When Several Applications Share the Same Repository
Consider the following restrictions if multiple applications are sharing the same repository:
Changing the Popup Visibility type has a global effect on all instances where the business component is used. If multiple applications share the same repository and use the same business components, then changing the Popup Visibility type for a common business component might have an undesirable effect on another application.
If multiple applications share the same applet, then the picklist in each applet shares the same visibility as defined by the OverridePopupVisibility property. This is because the OverridePopupVisibility property is set on the containing applet.
To override the pop-up visibility
In Siebel Tools, navigate to Applet, then Applet User Properties, and define the OverridePopupVisibility user property on the applet containing the control that opens the pick applet.
If OverridePopupVisibility is used, then the picklist and pick applet search specifications are ignored during the synchronization when the records for the picklist are extracted.
It is recommended that you use the condition filter PopUpSearch as described in "Configuring Business Component Filters for Pop-up Applets" to restrict data download rather than the OverridePopupVisibility user property.
When a record is extracted by using different visibilities, the record is tagged with each visibility. For example, if an individual contact record is extracted under Org visibility, and if the same contact record is extracted later under Salesrep visibility, then the visibility field on the record contains a bitmask indicating that the two visibilities apply to this record. The synchronization of mobile applications extracts data in the following order:
DefaultBusObjs
Views
PickList
Each record downloaded to the Siebel Mobile client is sampled with a visibility number. The visibility number is used to determine which views the record must display. The visibilities supported and the corresponding visibility codes are shown in Table 5-7.
|
Note: Group, Catalog, or Sub Organization visibility are not supported. For each BC Table in the local storage, there is a column called _PdaVisibilityTypes which holds the visibility information. The value in this field is calculated using the following formula: The sum of the power of 2 to the n, where n is the visibility code indicating the visibility of the record. For example, if a record is configured with the Sales Representative and All visibility types, then the value in the _PdaVisibilityTypes field would be (2^0 + 2^3) = (1+8) = 9. |
