Mobile workflow projects work properly without special handling, unless you want to upgrade to the new workflow client containers.
After upgrading to SDK version 2.1:
- Mobile workflows developed in version 2.0 and 2.0.1 must be regenerated and repackaged using the Mobile Workflow Forms Editor to use the new 2.1 functionality. The new functionality is included as additions and modifications to the JavaScript files.
- Any customizations made in version 2.0 and 2.0.1 to the Custom.js and Stylesheet.css files in the mobile workflow package are maintained and functional after regenerating and repackaging.
- Any customizations made in version 2.0 and 2.0.1 of the API.js, Utils.js, or WorkflowMessage.js files in the mobile workflow package are backed up (to a .backup extension) the first time the mobile workflow package is generated in 2.1., then they are replaced with the new 2.1 version. If you made changes to those files in 2.0 or 2.0.1, you must manually reapply those changes.
- Mobile workflow packages generated in version 2.0 and 2.0.1 do not work with version 2.1 of Unwired Server unless you manually modify the manifest.xml file to reference the shared WorkflowClient.dll file located in <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\MessagingServer\Bin.
Supported Upgrade Scenarios
When Unwired Server is upgraded from version 2.0 or 2.0.1 to version 2.1, no modifications to the deployed version 2.0 mobile workflow packages on the server or clients are necessary for the version 2.0 or 2.0.1 functionality to operate correctly.
When SDK clients are upgraded from version 2.0 or 2.0.1 to version 2.1, version 2.0 and 2.0.1 are coexistent installation with 2.1 on BlackBerry and Windows Mobile platforms. Workflow messages and existing version 2.0 mobile workflows remain on the clients. Native applications continue to use version 2.0 or 2.0.1 binaries and settings.
Android
If the 2.1 Android mobile workflow container is installed on an Android device in which the 2.0.1 Android mobile workflow container is already installed:
- The 2.1 container upgrades and replaces the 2.0.1 container.
- Existing mobile workflows and messages stay intact and are automatically mapped to the 2.1 mobile workflow container.
- No new registration or re-registration is required on Unwired Server, nor do you need to reassign mobile workflows to the 2.1 mobile workflow container.
BlackBerry
If the 2.1 BlackBerry mobile workflow container is installed on a BlackBerry device on which the 2.0 BlackBerry mobile workflow container is already installed:
- The two mobile workflow containers coexist on that BlackBerry device or simulator.
- The existing mobile workflow applications and messages remain tied to the version 2.0 or 2.0.1 container and are NOT removed.
- A new application connection on Unwired Server is required for the 2.1 container, mobile workflows must be assigned to the 2.1 container, and the connection settings must be entered in the 2.1 Settings application.
- When the 2.1 container is installed, an additional Workflow menu item will NOT be added to the Messages application. The existing Workflow menu item in the Messages application maps to the 2.0 Container. If the 2.1 BlackBerry client is the only version of the workflow container running on the device, the Workflows menu item is mapped to the 2.1 BlackBerry client.
- The new 2.1 Workflow Container application icon must be used to launch the 2.1 Container. Workflow messages in the inbox will open whichever container version they are associated with.
iOS
If the 2.1 mobile workflow container is installed on an iOS device on which the 2.0 or 2.0.1 iOS mobile workflow container is already installed:
- The version 2.1 mobile workflow container upgrades and replaces the 2.0 or 2.0.1 container.
- Existing mobile workflow applications and messages stay intact and are automatically mapped to the 2.1 container.
- No new registration or re-registration of application connections is required on Unwired Server, nor do mobile workflows need to be reassigned to the 2.1 container.
Windows Mobile
If the version 2.1 mobile workflow container is installed on a Windows Mobile device on which the 2.0 or 2.0.1 mobile workflow container is already installed:
- The two mobile workflow containers coexist on that Windows Mobile device or emulator.
- The existing mobile workflow applications and messages remain tied to the version 2.0 or 2.0.1 mobile workflow container and are NOT be removed.
- A new application connection on Unwired Server is required for the 2.1 container, mobile workflows must be assigned to the 2.1 container, and the connection settings must be entered in the 2.1 Settings application.
- When the 2.1 container is installed, and a version 2.0 or 2.0.1 installation is present, an additional Workflow menu item is NOT added to the menu in the mail application. The existing Workflow menu item in the Messages application maps to the 2.0 or 2.0.1 container.
- You must use the new 2.1 Workflow container icon displayed in Programs to launch the 2.1 container.
- Workflow messages in the inbox will open whichever container version they are associated with. If 2.0 or 2.0.1 and 2.1 are assigned the same workflow and have messages sent to the user, two emails are sent – one for each registration.
If previous versions are not installed at the time 2.1 is installed, the mail menu item Workflows is created and can be used to access the 2.1 Workflows application. No special handling is present if a mobile workflow container 2.1 is installed on the device or emulator first, and a 2.0 2.0.1 mobile workflow container installed subsequently. One possible result is that there may be two mail menu items named Workflows.
The Windows Mobile Programs folder will have icons for accessing both 2.0, 2.0.1, and 2.1 settings. Versions 2.0 and 2.0.1 icons and names will remain. For 2.1, two new icons will be present—Workflow Settings for the 2.1 settings application and Sybase Mobile Workflow for the 2.1 workflow application.