|Bookshelf Home | Contents | Index | PDF|
The Handheld application is used to capture and record transactions entered by users. During synchronization, these transactions are processed on the server. A situation can arise in which a transaction fails when it is applied to the Siebel Server (through Direct Server Synchronization). For example, a Handheld application user creates a professional call activity for one of their contacts. However, since they last synchronized with the server, the contact involved in this transaction was deleted from the server database. As a result, when the user tries to synchronize their handheld device, the server does not find the contact, and the call activity for the contact cannot be inserted into the server database. To generalize this example, any transaction that involves data selected through picklists or pick applets fails on the server if that pick data is not present at the time of synchronization.
The following describes how a pick transaction is recorded on a handheld device and processed on the server during synchronization. Assume that the user wants to create a new call activity for the contact. In order to do this, the user inserts a new record in the Professional Call screen and picks the desired contact. When the contact is selected on the handheld device, the Row Id of the contact (Contact Id) is recorded. However, on the handheld device, the application does not record any of the pick map fields associated with the contact; only the Contact Id is recorded. When the user synchronizes their handheld device, that Contact Id is used to locate the contact record in the server database. The Contact Id is then used to retrieve all of the fields used in the pick map for the Contact Id (Last Name, First Name, Middle Initial, Address, City, State, Zip Code, and so on).
In order to minimize pick processing failures, the Handheld application must record the pick row ID and all of the pick map data that is required for a successful transaction. This data must be recorded at the time of the pick, so that it can be passed to the server for processing. This enhanced functionality is called Extended Pick processing. Now, when the user synchronizes, the transaction is processed on the server as follows:
You can enable Extended Pick processing globally or at the business component level when configuring the Siebel Handheld application. When the DefaultHandheldSyncPickMode parameter is enabled, every pick transaction is subject to pick processing.
Table 25 shows the combined effect of the settings in the Application - Mobile > Settings View and on a business component.
In Table 25, read down the Tools Configuration column (which shows what HandheldSyncPickMode is equal to) and across to the Mobile Administration View Setting column (which shows what DefaultHandheldSyncPickMode is equal to) to see the combined result. For example, a NoFail configuration in Tools combined with a FailOnError setting in the Mobile Administration View results in the combined effect NoFail.
|Siebel Service Handheld Guide||Copyright © 2008, Oracle. All rights reserved.|