Properties for starting points.
The Properties view for all starting points includes the Keys page. Server-initiated starting points have the additional properties pages described in this topic.
| Property | Description |
|---|---|
| Mobile business object | (Optional) A mobile business object with which the Server-initiated starting point is associated. |
| Object query | (Optional) When you define an
object query in the mobile business object associated with the
Hybrid App screen flow, the object query
returns the specified instances of the mobile business object. For
example, if a Hybrid App user submits a travel
request to Hawaii, the object query returns an instance of that
mobile business object so the approver can review the travel request
details then modify the status and comment fields. You can use object queries that return multiple instances, as well as object queries that return only one instance. |
| Generate old value keys | Send two copies of data—one with the key names you select at
design time, and one with the same names prefixed with "_old"
(default). The application might update the keys you select at design time, but the old values are not updated unless this option is selected. The "_old" value keys can be critical when an update or parent update operation is executed later. |
| Jumpstart | Launch the Notification Processing wizard, where you can compose a sample notification message that specifies parameter value extraction rules and matching rules. |
| Extraction rules | Shows the notification extraction rules for the Server-initiated starting point. Select a rule and click Edit to change the transformation rule. |
| Error screen | The screen to which the user navigates if an asynchronous operation invocation fails. |
| Subject | If an error occurs, a notification is sent to the device with the appropriate error log keys and the specified subject. The value you specify here appears in the Subject field of the notification. |
| From | Text that appears in the From field of error notifications. |
The Keys page lets you view and configure properties for keys that are associated with a starting point. You can sort on any property in the table by clicking its column heading.
| Property | Description |
|---|---|
| Key name | The name of the associated key. |
| Type | The data type of the associated key, for example, string. |
| Data binding | The data source (if any) to which the key is bound. |
The view provides buttons to perform these operations on keys:
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.
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. |
This page contains a table of condition names with the matching Start screen. If there are no conditions or if all of the conditions are evaluated as false, the default navigation is executed.
| Property | Description |
|---|---|
| Default screen | Select the default start screen. This is the start screen that is used if all of the conditions are false or absent. |
| Condition name | Click Add to add a condition. If this condition is true, the screen that matches the condition is used as the start screen. |
| Conditional success screen name | Select the screen that is associated with the condition. |
| Property | Description |
|---|---|
| Field type | The field in the notification from which the parameter value is extracted, for example, Subject, indicating a value in the subject line of the notification message. |
| Tag before parameter | Text indicating what to extract from the beginning of the field's contents, for example, "Approval Request\(". |
| Tag after parameter | Text indicating what to extract from the end of the field's contents, for example, "\)was sent". |
| Format | Format uses the C# ParseExact syntax, and applies only to DateTime. It supports locale-specific parameter extraction. For example, you can indicate that a given date parameter is in the form yyyy-MM-dd in the e-mail, and another date parameter is in the form yyyy-dd-MM. |
| Key | The key to extract from the notification value. |