Migrate Mobile Business Objects

No steps are required to migrate 2.1 ESD #3 mobile business objects (MBOs) to version 2.2 SP02; however, you may need to perform some migration steps to take advantage of new features.

If you are migrating from a version earlier than 2.1 ESD #3, see Release Bulletin 2.1 ESD #3 on Product Documentation, the Mobile Business Object section: http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc00835.0213/doc/html/jwo1333684770287.html.

Migrate Mobile Business Objects to 2.2 SP02

  • In versions earler than Unwired Platform version 2.2 SP02, Sybase Unwired WorkSpace allowed mapping of operations with multiple MBO arguments ('Filled from Attribute', client parameter, and personalization key) at the same time, even though it might not work properly on the device application during runtime.

    With version 2.2 SP02, when adding a mapping of an operation argument, Sybase Unwired WorkSpace now allows only one of the three sources (MBO attribute, client parameter, personalization key) to map into the operation argument at one time; that is, the argument value sources are mutually exclusive.

    However, when migrating the Mobile Application project from earlier versions, Sybase Unwired WorkSpace preserves the original MBO operation argument value assignment choices the developer made, to retain backward compatibility with the project in the earlier version. Sybase Unwired WorkSpace does not remove any mappings when migrating a project.

    In a migrated project, if an operation argument is mapped to a client parameter as well as an attribute or personalization key, this warning appears: 
    Client parameter parameterName might not be used,  as the mapped argument has 'Fill from Attribute' or 'Personalization Key' specified.
    The developer should adjust the MBO model so that an operation argument maps to only one source.
    Note: The developer can provide a default value for the operation argument, regardless of how the argument is mapped.