Adding a Load Parameter to a Mobile Business Object

Load parameters control the amount of data refreshed between the enterprise information system (EIS) and the Unwired Server cache database (CDB). You can also map them to synchronization parameters, unless the MBO for which you are defining the load parameter is in a cache group that uses an Online policy.

1. In the Mobile Application Diagram, right-click the MBO, and select Show Properties View. Alternatively, click in the MBO title header to open the associated MBO properties view.
2. In the Properties view, select the Attributes tab, then select the Load Parameters tab.
   Any parameters defined as part of the MBO definition automatically appear as load parameters. For example, if your MBO is bound to the sample database's customer table, and the SQL definition is:

   SELECT customer.id,   
            customer.fname,   
            customer.lname,   
            customer.address,   
            customer.city,   
            customer.state,   
            customer.zip,   
            customer.phone,   
            customer.company_name  
       FROM customer  
      WHERE customer.state = :state_name

   then state_name is a load parameter and state is the Propagate to attribute. You can modify this load parameter or add additional load parameters from the Load Parameters tab.
3. Click Add.
   A new parameter is created with the default name of "parameter1." The next parameter you create is called "parameter2," and so on.
4. For each parameter, specify:

   Property	Description
   Parameters
   Name	Name of the mobile business object parameter. Names cannot contain C# or Java reserved words.
   Datatype	Select the parameter datatype. Datatypes include string, date, int, datetime, decimal, and so on, and map to the data source's datatype.
   Nullable	Select this option if Null is a valid value for the parameter, the corresponding data source Argument to which it maps, and the Propagate to attribute.
   Personalization key	(Optional) You can select a personalization key to map to the parameter, which provides an argument value. For example, you can create and specify the "state" personalization key, and return values that match a specific value, such as "California." If Synchronization parameter is selected, this option is unavailable.
   Synchronization parameter	(Optional and unavailable for MBOs in cache groups that use an Online policy) Map the load parameter to an existing synchronization parameter (defined from the Synchronization tab) to filter the results that are downloaded to mobile devices based on the value. The Default value and Personalization key options are ignored if you select synchronization parameter.
   Propagate to attribute	(Optional) Select an attribute to use its value for that of the parameter.
   Data Source
   Argument	Data source argument name to which the parameter is mapped. If you select Unmap as the data source argument, an extra unnamed row is added to the load parameter list. This is not an error. The data source requires an argument mapping for these parameters. Selecting Refresh, or remapping the parameter removes the extra row.
   Datatype	Datatype of the data source argument to which the parameter is mapped. You can change the argument's datatype only if it maps to a parameter bound to a JDBC data source.
   Nullable	Select this option only for EIS arguments that support NULL as a valid value.
   Default value	(Optional) Enter a default value for the parameter. If Synchronization parameter is selected, this option is unavailable.
   Show/Hide figure	Once you define a parameter, select Show figure to view a graphical representation of the parameter-to-data source argument mapping. You can modify the mapping by dragging the connector line from the parameter to a different argument, which automatically updates the datatype to that of the argument.