Input Mapping Default Value Precedence

Understand default value usage and runtime precedence during remote operation execution as they relate to input mappings.

View operation input default value properties by selecting the operation in the Mobile Application Diagram, then selecting Input > Default Values from the Properties view:

Argument – name of the operation argument.
When an old value argument is unmapped, it is added to the list of arguments in the Default Values tab, and the Arguments in the Input Mapping tab. Personalization keys and client parameters may be mapped into unmapped old value arguments in the Input Mapping figure, but not attributes.
Datatype – the argument's datatype.
Nullable – selected if Null is a valid value. If a create, update, or delete (CUD) argument is mapped to an attribute and to a personalization key, you cannot set < NULL> value for this argument. If you want to pass < NULL> value for an operation argument which is fill-from-attribute, model additional operations without personalization keys or default values bound to the argument.
Old value argument (update and delete operations mapped to JDBC data sources only) – maps a parameter to a second (old) argument for MBOs. The old value argument is assigned the previous value of the attribute to which the corresponding operation argument is bound. See Old Value Argument.
Default Value – the argument's default value.
For MBO operations with a non-nullable argument, the argument's value must come from either a fill-from-attribute, personalization key, client parameter, or default value. If a non-nullable argument maps to a fill-from-attribute or client parameter, the default value is ignored, even though SAP Mobile 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.