Handheld S&F Message Delivery Timeout
(Doc ID 534318.1)
Last updated on MARCH 01, 2018
Applies to:Siebel Handheld - Version 7.7.1 PDA  to 220.127.116.11.9 [IP2013] [Release V7 to V8]
Microsoft Windows (32-bit)
Product Release: V7 (Enterprise)
Version: 18.104.22.168  ITA
Database: Oracle 22.214.171.124
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-3139615631.
***Checked for relevance on 27-Feb-2013***
We are in Production Environment with Siebel Service Handheld 126.96.36.199 PDA  ITA, schema version 188.8.131.52 and we are using Store-and-Forward functionality.
We notice the following behaviour: when an activity is sent to the device and this is not connected (we mean GPRS not connected or Siebel Handheld application closed), Message Delivery Timeout parameter is ignored.
We know that this parameter is used in "SMQ Outbound Activity to one recipient" Workflow Process and we setted to 18.000 seconds, in order to assure user can receive activity also after a no connection period.
But this parameter seems to be ignored because, in any case if device is disconnected, after 10 minutes activity status changes is "Dispatch Failed" and message in Store-and-forward message history changes in "Overdue - Not Received".
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document