View and configure the server-initiated starting point properties.
Select the Server-initiated starting point in the Flow Design page to view and configure its properties.
| Property | Description |
|---|---|
| Mobile business object | The mobile business object with which the server-initiated starting point is associated. |
| Object query | When you define an object query in the mobile business object associated with the Mobile Workflow form, the object query returns the specified instances of the mobile business object. For example, if a travel request to Hawaii is submitted, 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 for that mobile business object. Object queries that return multiple instances are supported, as well as object queries that return only one instance. |
| Generate old value keys | By default, this is selected, which means when data is sent, there are two copies sent—one with the key names you select at design time, and one with the same names prefixed with "_old." The keys you selected at design time may get updated by the application, but the old values will not unless this option is selected. Those "_old" value keys may be critical when executing an update or parent update operation at a later time. If you unselect this option, old value keys are not generated. |
| Jumpstart | Launch the Notification Processing wizard, where you can compose a sample notification message from which to specify 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. |
Keys associated with the controls on the screen are shown.
| Property | Description |
|---|---|
| Key name | The name of the associated key. |
| Type | The type of the associated key, for example, string. |
| Data binding | Shows the data source to which the key is bound.
Click New to create a new key. Select any key and click Edit to edit the information for an existing key. Select a key and click Remove to remove an existing key. |
Use the Parameter Mapping section to bind the parameters (if any) of an operation or object query to keys or, context data, such as DeviceName, BackEndPassword, BackEndUser, and so on.
If you have a mobile business object with load parameters mapped to transient personalization keys, you can specify values for those personalization keys when you invoke an operation or object query from the Mobile Workflow package. This can, for example, be useful for loading only specific data into the consolidated database from large data sources.