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

Insert Failure Processing in Siebel Handheld Applications

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. FailOnError behavior guarantees that, if an insert fails, 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. Users must contact their system administrators to recover from the failure. The recovery effort can 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 insert failure processing globally or at the business component level when you configure 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 25 shows the settings for this parameter.

You can also use the HandheldInsertFailMode user property to enable insert failure processing at the business component level. For more information about this user property, see HandheldInsertFailMode User Property.

Table 26 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 26, read down the Tools Configuration column (which shows what HandheldInsertFailMode is equal to) and across to the Application Settings Value (which shows what the DefaultHandheldInsertMode is equal to) to see the combined result. For example, a NoFail BC setting combined with a FailOnError application setting results in the combined effect NoFail.