Defining Synchronization Properties for Individual Mobile Business Objects

Each mobile business object (MBO) that can be synchronized includes a Synchronization tab from which you configure synchronization behavior.

1. From the Mobile Application Diagram, right-click the MBO for which you are configuring synchronization, and select Show Properties View.
   Note: MBOs not bound to a data source or that use an Online cache policy do not support synchronization.

   In the context of 2.1. req#0404 the statement that "MBOs not bound to a data source do not support synchronization." is incorrect. This should already be supported in 2.0 and definitely need to be corrected in the context of 2.1 ESD#1. If this is not the case this is a feature requirements mismatch. For DCN we must be able to support modeling and deploying MBO without load operation/data source binding and these MBO must have sync parameter support, they are filled by the EIS and sync'd by the user/device. Please co-ordinate with Hung, I already spoke with him. MAKE THIS CHANGE IN THE ESD

2. In the Properties view, select the Synchronization tab.
   Note: If you do not see the Synchronization tab, switch to the Advanced Developer profile.
3. Complete the synchronization definition:
   Use the Add, Delete, and Delete All buttons to create or remove parameters. You can also supply additional parameter information for each parameter, including:

   • Parameter name – by default each new parameter name is parameterN (N is the number of the parameter), which you can change.
   • Datatype – the datatype of the parameter. Datatypes in the Personalization key and Mapped-to columns must be compatible with the datatype selected here.
   • Nullable – accepts null as a valid value. Unselect this option if the argument to which this parameter is mapped does not support null as a valid value.
   • Default value – enter a valid value.
   • Personalization key – maps the synchronization parameter to a personalization-key value. If you specify a Personalization Key, the client is not required to provide a value, but must define a personalization value for the key before successfully using the MBO.
   • Mapped to – maps the synchronization parameter to an existing attribute. During synchronization, the application's synchronized local cache contains only entities that match the synchronization parameter value with that of the mapped attribute.
   • Query limiting – deprecated. Instead use dynamic device-side queries to limit synchronization to the last value entered by the device application user.
4. Select Customized download data to generate the SQL statement that defines the synchronization filter. Unselecting this option clears the statement.
   By default, the internally generated SQL statement, based on the synchronization parameters, includes only the '=' operator. To properly generate the SQL for any MBO that is bound to a JDBC data source that includes a where clause operator other than '=' ( > , < , < > , != , > =, < =, ! > , ! <, and so on), update the generated SQL statement after selecting Customized download data. For example, change the '=' operator to '>'.