Bookshelf Home | Contents | Index | PDF |
Siebel Sales Handheld Guide > Synchronization Conflict Handling and Recovery with Handheld > Preventing Synchronization Transaction Conflicts with Siebel Handheld > Insert Failure Processing in Siebel HandheldWhen the server executes an insert transaction and the insert fails, there are two ways the insert failure can be handled:
NOTE: If FailOnError processing takes place, synchronization is interrupted. The synchronization process continues to fail until the problem is resolved. End users must contact their system administrators to recover from the failure. The recovery effort may involve modifying transactions queued for processing, modifying data on the server, or reentering transactions through the Siebel Handheld application. Handling Insert FailuresYou can enable Extended Pick processing globally or at the business component level when configuring the Siebel Handheld application. The following setting applies globally throughout the application. When FailOnError is specified, every failed insert interrupts synchronization. You can specify the value for this setting through the Settings view in the Administration-Mobile screen. Table 24 shows the settings for this parameter. Optionally, you can enable Extended Pick processing at the business component level. The user property is defined on specific business components. The setting in the business component takes precedence over the setting defined in the Settings view. Table 25 shows the syntax for setting the Insert Fail Mode on a business component and the parameter values. These settings are made in Siebel Tools. Table 26 shows the combined effect of the setting in the Settings view and the setting on a business component.
In Table 26, read down the Tools Configuration column and across to the application settings value to see the combined result. For example, a NoFail BC setting combined with a FailOnError application setting results in the combined effect NoFail. |
Siebel Sales Handheld Guide |