Siebel Service Handheld Guide > Synchronization Conflict Handling and Recovery with Handheld > Preventing Synchronization Transaction Conflicts with Siebel Handheld >

Insert Failure Processing in Siebel Handheld

When the server executes an insert transaction and the insert fails, there are two ways the insert failure can be handled:

• A record is logged that indicates the insert failed, and synchronization continues. This is the default insert behavior. The Conflict Administration screen can be used to recover the data.
• The insert failure is logged, including details of the failure, and synchronization is interrupted. This is the FailOnError behavior. FailOnErrore behavior guarantees that, should an insert fail, data loss does not occur since synchronization is stopped until the circumstances causing the failure are resolved.

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 Failures

You 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.

DefaultHandheldInsertMode.

You can specify the value for this setting through the Settings view in the Administration-Mobile screen.

Table 27 shows the settings for this parameter.

Optionally, you can enable Extended Pick processing at the business component level.

HandheldInsertFailMode=Mode

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 28 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 29 shows the combined effect of the setting in the Settings view and the setting on a business component.

• The business component setting always takes precedence over the settings defined in the Administration-Mobile > Settings view.
• If there is no setting on a particular business component, the Applications Settings value applies.
• If there is no setting in either the Settings view or on the business component, the default behavior is the same as NoFail. Insert failures are logged and synchronization continues.

In Table 29, 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.