Anywhere Mobility Studio Documentation

Determining the next step in the process

The next step

An editable control only appears as editable when the associated parameter has no value (no session parameter exists). When the user enters a value, there is no need to re-enter it. The Framework looks for the next textbox control without a value and displays it as editable on the client.

When a user selects a button of the empty type '', the Framework determines the next activity as follows: when the current control's Activity End property is False, another editable control exists in the same activity. When that control's parameter has no value (no associated parameter buffer exists), the activity displays on the mobile device with the control as editable. When the control's parameter has a value (an associated parameter buffer exists), the Framework searches for the next editable control without an associated session parameter until no more editable controls remain in the activity.

When no more editable controls exist in the activity (so the control's Activity End is set to Yes by the process release) the Framework looks in the flow to determine the next activity or process to display. It displays the first flow line where Code From is the current activity and the flow condition applies.

Stack

The stack stores every activity in the process along with the record used and the table view applied to that record.

The stack recreates the mobile page when the process is interrupted (for example, when the connection to the server is lost or the device loses power) or to determine the previous activity when navigating back through the process.

When a user selects a button of type Back, the process goes back one activity by default. When a flow defines behaviour for the activity with the back button, the process can go back several activities. This lets the user return to the menu in one selection instead of navigating back activity by activity.

When navigating back, all stack lines between the current activity and the target activity delete. The session parameter records associated with those stack records also delete, so all parameter values entered in the activities between the current and target activity are lost. Typically, process these values using a document or post document processor before taking the process back.