Mobile business objects and operations must meet certain requirements to support a cache update policy.
Before you can define a cache update policy for a mobile business object (MBO) operation, the MBO must meet these requirements:
Cache update policy requirements
| Policy |
Requirements |
| Apply results to the cache |
- The MBO must be bound to a data source that has one or more Primary key attributes set.
- All columns in the record set returned by the operation contains all key attributes.
|
| Invalidate the cache |
A partition key identifies the cache partitions affected by the operation. Partition key definition guidelines require that:
- An input parameter must be mapped to a synchronization key or to an attribute of another MBO to be considered a partition key.
- Input parameters that are only mapped to personalization keys are excluded as partition keys, since personalization keys are available only within a client context and not suitable for this cache update policy. If you want to use personalization keys as partition keys, you must map the personalization keys to a synchronization parameter.
- A synchronization key must be mapped to an MBO attribute.
|