AttachmentViewer Properties

Properties for a control for downloading and viewing attachments to a viewer on the device.

General

Property	Description
Label	Label – text identifying the control on the user interface. Label position – position of the label in relation to the control it describes.
Input data binding	Key – unique identifier within the current scope, used when setting or retrieving a value. Click New key to create a new key for the control, then save the screen. Important: Saving the screen is required because the key is not automatically updated when you enter or change its value. Note: If the value is not unique, the Problems view reports a missing key error. Default value – default value for the control.
Read-only	Specifies that the control is read-only. Default: unselected. Note: The read-only property is not supported on the Windows Mobile platform for the Checkbox, Slider, and Choice controls.
Content	Enables you to bind the AttachmentViewer to data by using an object query and mapping the parameters of the object query to keys. You indicate which binary attribute of the object query corresponds to the contents of the attachment. Use object query – Specifies that you will bind the AttachmentViewer to data by using an object query and mapping the parameters of the object query to keys. Mobile business object – the MBO that contains the object query you want to use. Object query – the object query to invoke. Attribute – the binary value that corresponds to the attachment contents. Note: The MBO binary value must be big enough to support the size of the attachment when developing the MBO. To do this, you must change the MBO's binary attribute from BINARY to BINARY(%) where % is larger than the largest binary content you want to store. See Datatype Support in Sybase Unwired WorkSpace - Mobile Business Object Development for information about setting the binary attribute size. MIME type key – A mime type identifies an object type recognized by the attachment viewer (see http://en.wikipedia.org/wiki/Mime-type#Type_application). Specify either a mime-type or a file name, such as report.pdf. For example, for an attachment named doc1.pdf, you can enter either the file name or its mime-type, application/pdf. Note: The device must have a viewer installed that can view the attachment. File name – a key that is bound to data that defines the name of the file to be viewed. File size – a key that is bound to data that defines the size of the file to be viewed. Note: Attachments requested on demand are limited to 5MB after Base64 encoding.

Parameter Mappings

Online requests and custom actions can bind parameters in Mobile Business Object (MBO) operations and object queries to keys or context data that are used in the submitted messages. The Parameter Mappings properties are generated as metadata in WorkflowClient.xml, which defines all the application's action mappings.

The Parameter Mappings table shows the available parameters in MBO operations and object queries, and their current mappings. The Edit button opens the Parameter Mapping dialog, where you can modify the properties of a selected mapping.

For information about parameter mapping, see WorkflowClient.xml File in Developer Guide: Hybrid Apps.

Property	Generated WorkflowClient.xml File Metadata
Parameter name	The name of the parameter in the operation or query that contains the data.
Parameter type	The type of parameter in MBO terms.
Mapping type	The source of the data, one of these types: Key BackEndPassword BackEndUser DeviceId DeviceName DeviceType UserName MessageId ModuleName ModuleVersion QueueId ContextVariable
Key	The key whose corresponding value is used as the value for this parameter. Used only when the Mapping type is Key.
Return data to client	Includes the key data in the return message to the client. If not selected, key data from the mapping is omitted.

Personalization Key Mappings

This page lists any personalization keys. To define the value of a personalization key, select its row in the list and click Edit.

Personalization keys allow the mobile user to personalize specific input field values by associating a key with a value. If your mobile business object has load parameters mapped to transient personalization keys, you can specify the key values that are loaded when an operation or object query is invoked from the Hybrid App package. This can be useful, for example, in loading specific data from large data sources into a consolidated database.

You can also fill the personalization key values with values extracted from the notification, depending on from where you are invoking the object query.

For more information, see Managing Personalization Keys in Sybase Unwired WorkSpace - Mobile Business Object Development.

Property	Description
Personalization key	The name of the personalization key.
Key	An operation argument, load argument, or synchronization parameter that provides the value of the personalization key.
Project	The project in which this personalization key is created. The personalization key appears in the Personalization Key folder of the selected Mobile Application project.