Favorite
configurations |
(Optional) Select a
configuration. |
Package Generation and
Deployment |
Update generated
code |
Generate the mobile
workflow package and its files. When this option is
unselected, the mobile workflow package files are not
regenerated, so that modifications made to files that are
normally regenerated are not overwritten. This also means,
however, that changes made in the Mobile Workflow Forms
Editor are not reflected in the generated files. Note: The manifest.xml and workflow_package.zip files are generated
even if this is not selected.
|
Generate into the
project |
Place the generated mobile
workflow package and its files in the current project.
|
Generate to an external
folder |
Place the generated ZIP
file containing the mobile workflow package and its
generated files into a location outside of the current
project. Click Browse to select the
alternate location. |
jQuery Mobile
theme |
Choose a theme for devices
that use the jQuery Mobile as the UI framework. The default
is theme B. See the jQuery Mobile documentation at http://jquerymobile.com/ for information about
the jQuery Mobile themes. |
Unwired Server
profile |
Select the Unwired Server
profile with which to associate the mobile workflow and
extract the user name and password credentials if you are
using static authentication. |
Deploy to an Unwired
Server |
Deploy the mobile workflow
package to an Unwired Server. |
Deploy mode |
The deploy mode is
automatically set; you cannot change it.
|
Assign workflow to
user(s) |
The mobile workflow must
be assigned to a device user before the mobile workflow is
visible on the user's device. You can assign the same mobile
workflow to multiple users. Separate multiple users with a
comma. Device users must be registered in Sybase Control
Center. Click Get
Users to select device users from the
list. You must have registered device users in Sybase
Control Center to populate this.
|
Validate controls as soon
as the user tries to change focus away from them |
If this option is
unselected, validation occurs only when the screen is saved.
If selected, validation occurs as soon as the control loses
focus. If validation fails, a help element appears and shows
the error message. |
Optimize JavaScript in the
generated workflow package |
The public JavaScript
files (API.js, Callbacks.js, Camera.js, and so on) contain
the client API functions that you can access for use with
your Mobile Workflow package customization. By default, the
wizard generates a single JavaScript file (such as SUP0.js,
SUP1.js, or SUP2.js), that concatenates these files.
Unselect this option if you prefer to use the JavaScript
files separately. |