Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Pharma Handheld Guide > Siebel Handheld Application Administration > Storing Asynchronous DataAn asynchronous query enables users to search information from the Siebel Server through SFM if the information is not available from the Siebel Handheld application local database. Users can integrate query results from an asynchronous query in the Siebel Handheld application database. Users can perform an asynchronous query for the business objects (for example, Solution, Product, Asset and Orders) defined for the application. For example, if a mobile field technician at a customer site wants to check the status of an order and the order is not available on the local database, the technician can send an asynchronous query to the Siebel Server through SFM by specifying the account name and order date for the order. Shortly afterwards, the Asynchronous Query icon flashes, which means that the query results are returned from the Siebel Server.
NOTE: When the record is stored on your Siebel Handheld application, you can review, search, or update the record from the Handheld application screens and views. Receiving Incoming Messages from the ServerFrom the incoming message notification window, users can drill down on the hyperlink under the dispatched activity section to navigate directly to the activity detail view. Messages or activities are dispatched through SFM. You can handle incoming alert messages differently, depending on your business model. You can tap the message alert icon to open the incoming message alert window. The alert window displays all the incoming messages sent from the Siebel Server by SFM. The top row shows the most recent message. You can close the alert window or can tap the hyperlinked activity # or message to review the detail information of the activity or message. Removing Reassigned ActivitiesYou can remove reassigned activities differently, depending on your business mode. Users can delete an activity from a Siebel Handheld application database through SFM if the activity has been assigned to another user. If an activity has been dispatched to user A on a Handheld application and then the activity is assigned to another mobile user, the activity on user A's Handheld application must be deleted. For example, Technician A is assigned activity 12-98Y98 via SFM and the activity 12-98Y98 is stored in the Handheld application database. A call center agent, however, then decides to re-assign the activity (12-98Y98) to another technician, Technician B. The call center agent goes to the Dispatch Board, drags and drop the activity, and assigns the activity to Technician B. Because the activity has been reassigned to Technician B, the Siebel Server sends an SFM message to Technician A's Handheld application. This message arrives on Technician A's handheld device, and removes the activity from their Handheld application database. Technician A can see an alert message in the application's incoming message alert window, which indicates that the activity has been assigned to another technician and removed from their Handheld application database. |
![]() |
![]() ![]() |
Siebel Pharma Handheld Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |