When you generate mobile workflow package files, some files are generated every time and others are generated only under certain conditions.
These files are generated every time you generate the mobile workflow package:
- manifest.xml –
describes
how the contents of the Mobile Workflow package .zip file are
organized.
- workflow_name.zip
– contains all of the Mobile Workflow files, including the Web application
files, look and feel files, the JavaScript files, and so
on.
These files are regenerated only if you select the Generate option in the Mobile Workflow Package Generation wizard:
-
workflow_name.html – an HTML file that
describes simple workflow screens and forms. Default name:
workflow.html.
- workflow_name_CustomLookAndFeel.html –
a workflow html file that adds Sybase JavaScript functions and CSS styles.
- workflow_name_jQueryMobileLookAndFeel.html
– a workflow html file that adds jQuery
Mobile
functions and CSS styles.
- WorkflowClient.xml – contains metadata that specifies how
to map the data in the workflow message to and from calls to Mobile Business
Object (MBO) operations and object queries.
- workflow_name.xml – look and feel file that uses the basic
workflow_name.html file.
- Resources.js – allows you to access localized string
resources.
- Workflow.js – contains functions for common menu, screen,
and database operations.
These files are generated only if you select the Generate
option and the files do not exist:
- API.js and Utils.js – provide Mobile
Workflow functions used to communicate with the Hybrid Web container.
- Custom.js – enables you to add JavaScript code to customize
the Mobile Workflow application. Your file is preserved each time you regenerate
the package.
- WorkflowMessage.js – provides functions to access Workflow
Message resources.
- All *.css files – defines formatting rules to render the
screens in HTML.
When you generate the mobile workflow package into the current project, the ZIP
file containing the mobile workflow application and its files is placed in the
Generated Workflow folder in the project, for example,
C:\Documents and
Settings\username\workspace\Project_Name\Generated
Workflow. The files are shown in the WorkSpace Navigator. This shows
the generated file structure for a project named PurchaseOrder.
The
Generated Workflow\project_name
folder contains:
- html – this folder includes:
- workflow.html – contains all the screens in the Mobile Workflow application, each in its own <div> section. This is used on BlackBerry, Android, and iOS platforms with the Optimize for performance look and feel. On Windows Mobile, it is used for all looks-and-feels.
- workflow_customlookandfeel.html – contains all the screens in the Mobile Workflow application. This is used with the Optimize for appearance look and feel on BlackBerry 5.0
- workflow_jquerymobilelookandfeel.html – contains all the screens in the Mobile Workflow application. This is used with the Optimize for appearance look and feel on iOS, BlackBerry 6.0, and Android.
- js\Custom.js – edit this file
to customize the Mobile Workflow application. Since you can modify
this file, it is generated only once, or when not already present in
the generated files. This ensures that it is not overwritten if you
subsequently regenerate the Mobile Workflow package. Examples of
ways you can customize the Mobile Workflow application include:
- Manipulating HTML elements.
- Writing code that is called before or after
generated behavior is invoked for menu items.
- Implementing custom validation logic.
- <project_name>.zip – contains the
mobile workflow application and its files, including the images, user
interface, and controls