Mobile Business Object Development

Once you are familiar with the documented platform features, review these new or changed features for mobile business object (MBO) development.

Operation Cache Policy Enhancements

Additional and enhanced cache policies provide more control over the way enterprise information system (EIS)-affecting operation results are applied to the Unwired Server cache, especially for composite graph MBOs (MBOs in a composite relationship).

Documented in:
  • EntityRead Mobile Business Object Project (2.1 ESD#3) - an Unwired WorkSpace example project that illustrates operation cache policy enhancements, Entity Read operations, and output mapping features using a REST Web service. Download the EntityRead example project from the SAP® Community Network: http://scn.sap.com/docs/DOC-8803.
  • Sybase Unwired WorkSpace - Mobile Business Object Development: Setting an Operation Cache Policy
  • Mobile Data Models: Using Mobile Business Objects: Operation Cache Policies

Entity Read Operation

A new MBO operation type enables you to identify a specific entity in the cache. Use the operation with the "Immediately update the cache" operation cache policy, and "Apply output of ENTITY READ operation" option. This operation then refreshes the Unwired Server cache for a single instance of an MBO, or composite graph (MBOs in a composite relationship) for Create and Update operations based on the definition of the Entity Read operation.

Documented in Sybase Unwired WorkSpace - Mobile Business Object Development, Entity Read Operations

Output Mapping

Provides a graphical editor and view of remote operations to MBOs, and attribute mappings, including mappings for MBO graphs (MBOs in a relationship).

Documented in Sybase Unwired WorkSpace - Mobile Business Object Development, search for:
  • Mapping Multiple Results to Multiple Mobile Business Objects
  • Mobile Business Object Operation Properties

Enhanced MBO Modeling Validation Rules

Additional validation rules including primary key requirements and maintaining primary key/foreign key affinity in composite object graphs warn or prevent you from defining an invalid MBO model. This may require MBO developers to update their MBO data models and regenerate object API code. Warning and error messages during MBO development help you avoid runtime errors, such as system exceptions in the client log, and various errors in the Unwired Server log.

Documented in:
  • Troubleshooting:
    • Relationship Guidelines and Restrictions
    • Operation Validation Rules and Error Messages
  • Sybase Unwired WorkSpace - Mobile Business Object Development: Relationship Guidelines and Restrictions
Related reference
New Platform Features