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
- <workflow_name>.zip
These files are regenerated only if you select the Generate option in the Mobile Workflow Package Generation wizard:
- <workflow_name>.html
- <workflow_name>_CustomLookAndFeel.html
- <workflow_name>_jQueryMobileLookAndFeel.html
- WorkflowClient.xml
- <workflow_name>.xml
- Resources.js
- Workflow.js
These files are generated only if you select the
Generate option and the files do not exist:
- API.js
- Custom.js
- Utils.js
- WorkflowMessage.js
- All *.css files
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