|
General
|
- Operation name – the name of the operation.
- Operation type – the operation to be performed. Operation types include Create, Update, Delete, and Other. Use Other only when there are no attributes associated with the MBO ( disallowing the Fill from Attribute field to determine the operation's parameters).
- Comment – describes the operation.
|
|
Data Source
|
Information about the data source from which the operation is derived. Select Change Connection Profile to bind the operation to a different connection profile of the same data source type, or Bind Data Source to bind the operation to a data source, or to rebind to a data source. |
|
Definition
|
View, modify, and test operations:- View – display the operation (SQL statement, or Web service method, for example) in a read-only window.
- Edit – modify the operation definition. You can change the type of operation as long as it is supported by the data source, and validate your changes. Enter credentials, if required, to access the data source.
- Test execute – tests the operation against the data source to which it is bound. The Test execute dialog allows you to load any existing test configurations and preview the results.
Note: Selecting Test execute can modify data stored on the data source to which the operation is bound. However, SQL statements are automatically rolled back and do not modify data.
|
|
Parameters
|
View or edit the operation parameters
that map to data source arguments. Operation parameters determine how
the client passes information to the enterprise information system (EIS). Select Refresh to update the parameters. Click Remap to automatically generate new mappings for unmapped parameter arguments based on metadata changes of the data source to which the mobile business object (MBO) is bound.
Select:-
Parameters
- Name – name of the mobile business object parameter. Names cannot contain C# or Java reserved words.
- Datatype– the parameter's datatype
- 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.
- Updatable – allows the parameter to be updated on the device.
- Required – indicates a required parameter.
- Personalization key – select a personalization key to map to the parameter, which provides the value.
- Fill from attribute – fills the parameter's value with that of the selected attribute.
If a create, update, or delete (CUD) operation parameter is a fill from attribute parameter and is bound to a personalization key, you cannot set < NULL > value for this parameter.
If you want to pass < NULL > value for a CUD operation parameter which is fill-from-attribute, model additional operations without personalization keys or default values bound to the parameters.
- Old value argument (update operations only)– maps a parameter to a second (old) argument. See Old Value Argument.
-
Data Source
- Argument – data source argument name to which the parameter is mapped.
- Datatype – Datatype of the data source argument to which the parameter is mapped.
- Nullable – accepts null as a valid value.
- Default value – the default value for the argument, or select <NULL> from the drop-down list.
- Show Figure – display a graphical representation of the operation's parameter mappings. Modify the mapping by clicking and moving the arrow that identifies the mapping.
|
|
Roles
|
Lists all logical roles granted to the operation along with all available roles. Use Add and Add All to move available roles to granted, and Remove and Remove All to remove roles from an operation. Select Create to define a new role. |
|
Cache Update Policy
|
Determine how the results of an MBO operation are applied to the Unwired Server cache. See Cache Update Policy. |