|
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.
In these cases the Fill from Attribute field is disabled
since there are no attributes associated with Other
operations.
- 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. Be advised that using Test execute or Preview for
large data or object types (BigString/BigBinary), can result in
out of memory errors in Unwired WorkSpace.
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.
|
| Operation Parameters |
View or configure the operation parameters that map to data
source arguments. Select Refresh to update the
parameters. For example, if the data source argument changes. Data
Source- Argument – name of the operation argument. Names cannot
contain C# or Java reserved words.
- Datatype – the argument's datatype.
- Old value argument (update and delete operations only) –
maps a parameter to a second (old) argument. See Old
Value Argument.
Value- Fill from attribute
– fills the argument's value with that of the selected
attribute.
If a create, update, or delete (CUD)
operation parameter argument is a fill from attribute
parameter and is bound to a personalization key, you
cannot set < NULL > value for this argument. If
you want to pass < NULL > value for a CUD
operation parameter argument which is
fill-from-attribute, model additional operations without
personalization keys or default values bound to the
argument.
- Personalization key
– select a personalization key to map to the argument, which
provides the value.
- Client Parameter – select a client parameter to map to the
argument, which provides the value.
- Default value – the default value of the argument.
For MBO operations with a non-nullable argument, the
argument must come from either a fill-from-attribute,
personalization key, client parameter, or default value. If a
non-nullable argument includes a fill-from-attribute or client
parameter, the default value is ignored, even though Unwired
WorkSpace allows you to input a default value. Also, if the
personalization key or fill-from-attribute is used to fill the value
of the argument, the client parameter might not be used.
|
|
Client Parameters
|
Client parameters are available in
the device application and allows the user to enter values that are
passed to the enterprise information system (EIS) operation argument
during operation replay. Client parameters can be mapped to operation
parameter arguments to determine how the client passes information to
the EIS:- Name – name of the client parameter. Names
cannot contain C# or Java reserved words.
- Datatype– the argument's datatype. BigString/BigBinary
datatypes are not supported, and an error displays if the MBO
developer selects a structure type that contains BigString or
BigBinary fields.
To
provide client parameters for BigString/BigBinary datatypes,
or a structure with BigString/BigBinary fields, use
compatible types: String for BigString, Binary for
BigBinary. For a structure, copy the original structure in
WorkSpace Navigator, and change the large object type fields
to String/Binary, then use the new structure as the datatype
of the client parameter.
- Nullable – accepts null as a valid value.
|
|
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 Policy
|
Determine how the results of an MBO operation are applied to the Unwired Server cache. See Cache Policy. |