Design Mobile Web Flows

A Mobile Web flow is a user interaction diagram (or map) showing a collection of the following elements:

Mobile Web screens: WAP screens where the user can interact through links, buttons, and forms. How?
Entry points: starts the Mobile Web flow with the end-user. How?
Mobile Web screen references: link to Mobile Web screens created in a different flow. How?
Connectors: links the elements in the Mobile Web flow. How?

There are other elements that you can use in your Mobile Web flows. See the complete list of elements in a Mobile Web flow.

Each Mobile Web Screen can be connected to more than one Mobile Web Screen, Go To Screen, or External Site. Mobile Web Blocks can be connected to one or several screens; they usually are. Although they appear as initial elements, they do not initiate a screen flow. Conceptually, they do not belong to the execution flow but you can have connectors from them, since they can include links.

To open and edit a Mobile Web flow, you must double-click it in the eSpace tree. Mobile Web Flows must be edited in their owner (An element owner indicates the Producer: eSpace or extension, where the element is defined, that is, where it can be changed. It can also be a web reference, if the element is a Structure) eSpace, if they are Mobile Web Flow references, they cannot even be opened.

Remarks

Mobile Web Flows are available only in .NET environments, specified by the Application Server eSpace property. If this property has the value J2EE or (both) a warning message is presented, notifying you that this type of flow is not implemented in a J2EE environment and will not be available at application runtime.