Page Comparison

Overview

Using the same field names, transfers data between pages

Header fields on a called page, are automatically filled out, when their name matches

A page  Header fields are populated when field names match a field in the response of the calling page

See example

(Example 1 and 2

This method works for all combination of pages, as long as field names match
The

)

• Name your fields the same, and values are transferred
• Name your fields differently and values are NOT transferred

Note: The XML response of a calling page, are available as "ContextValues" in the request on the called page

Tip: Use the"standard" .

This is useful to determine where the user "came from", when handling a XML request.

Utilize the standard names

All standard functions uses the same field and header field names:

1. OrderBackendId or  / BackendID: = Source  Source Document No.

2. LineNumber: = Source Document Line No.

3. Item = Item No.Etc:  Item No.
4. And more..

Use these names to get your custom fields populated.

,

• Mobile always initiates the communication with a Request
• BC always Responds

Example 1: Planned function Line to Unplanned function Header

Scenario

1. The user is viewing "Pick Order Lines"
2. User selects the submenu-action "Locate Item"
3. "Locate Item" also has a field called "Item" in it's Header
   
4. Item No. is now transferred. Because it exits in both the Order result AND the receiving page header.
5. Location is NOT transferred as field "Location" do not exists in the "GetPickOrderLines"-response. Field "Location" can be populated in the response from a customization using the OnGetShipOrderLines_OnAfterSetFromWarehouseShipmentLine event.

Example 2: Transfer Lookup function result to Unplanned function

Scenario

1. The user is viewing a result of the "Bin Content" Lookup function
2. User selects the action "Unplanned Move"
3. "Unplanned Move" also has a field called "Item" in it's Header.
4. Item No. is now automatically transferred, because it exits in both the lookup result AND the receiving page header.

1. asd

Example 3: Transfer Lookup function result values to an Unplanned function

Scenario

1. The user is viewing Lookup result
2. User selects Action in the menu
3. The current (single) Lookup Result can be included in the Unplanned function "PostAdhocRegistration" -request

Add the following change in Mobile Configuration Files

Add includeInputDataRowInSubmitRequest="true" to the <lookupConfiguration.. tag of the Lookup page. 

Header (and subsequently to PostAdhocRegistration) 

Scenario

1. The user is viewing a result of a Lookup i.e."Bin Content" 
2. User selects a (single) lookup result and is navigated to an Unplanned function
3. The current (single) lookup result values can be transferred to the Header of the Unplanned function
4. Values are subsequently included in the Unplanned function "PostAdhocRegistration" -request

Add the following change in Mobile Configuration Files

1. <onResultSelected enabled="true" navigateTo="MyUnplannedFunction"/> to the <lookupConfiguration.. tag of the Lookup page. 
   and
2. <open id="MyUnplannedFunction" title="Edit" icon="mainmenulocateitem" enabled="false"/> to the <actions></actions> tags

Example 4: Transfer Lookup function result values directly to an Unplanned function Action (PostAdhocRegistration)

Scenario

1. The user is viewing Lookup result
2. User selects Action in the menu
3. The current (single) Lookup Result can be included in the Unplanned function "PostAdhocRegistration" -request

Add the following change in Mobile Configuration Files

Add includeInputDataRowInSubmitRequest="true" to the <lookupConfiguration.. tag of the Lookup page.