Setting the Cache Update Policy

The cache update policy defines how the consolidated database is updated after calling a mobile business object operation at a finer granularity than the primary read operation.

1. In the Mobile Application Diagram, double-click the operation.
2. In the Operation Properties dialog, select the Cache Policy tab.
3. Select the cache update policy:

   Cache Update Policy	Description
   Invalidate	Invalidates and refreshes the CDB after the client calls the mobile business object (MBO) operation. This is the default cache update policy.
   No invalidate	The CDB remains unchanged after the client calls the MBO operation.
   Apply operation result	Updates the CDB based on the result set that is returned from the MBO operation.
   Apply operation parameters	Updates the CDB based on the operation’s parameters.
   Chained operation	Chain an alternate read operation to the MBO operation. The CDB is updated with the results returned by the alternate read operation. If you select this option, a Chained Operation drop-down list appears, which allows you to either choose an existing operation, or create a new one by selecting New. Define the chained operation the same as other operations; set the operation type to "Read." Note: Find by must be selected for at least one attribute. The alternate read operation is no different from an operation that uses the apply operation result cache update policy. Specifying a different read type operation enables chaining it to the MBO operations to get the desired results.

• Apply Operation Result Cache Policy
  Use the apply operation result cache policy to update the consolidated database, based on the results returned by the operation..
• Apply Operation Parameters Cache Policy
  Use the apply operation parameters cache policy to apply the operation's parameters to the consolidated database.
• Chained Operation Cache Policy
  The chained operation cache update policy allows you to chain a read operation to create, update, or delete operations, and update the consolidated database (CDB) at a finer granularity.
• Invalidate Cache Policy
  Use the invalidate cache policy only when other policies cannot be implemented or performance is not an important consideration.
• No Invalidate Cache Policy
  Use the no invalidate cache policy when changes to the enterprise information system (EIS) do not need to be immediately passed to the consolidated database (CDB).