Migrating Mobile Workflow Projects

Mobile workflow projects work properly without special handling, unless you want to upgrade to the new workflow client containers.

When upgrading to SDK version 2.1 ESD #2:

To use the new 2.1 ESD #2 functionality, use the Mobile Workflow Forms Editor to regenerate and repackage mobile workflows developed in earlier versions.
Any customizations made in previous versions 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 previous versions 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 ESD #2, then they are replaced with the new 2.1 ESD #2 version. If you made changes to those files in previous versions, you must manually reapply those changes.
Mobile workflow packages generated in previous versions do not work with version 2.1 ESD #2 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.
For workflows generated in previous versions, the custom.js and stylesheet.css files are backed up before being overwritten. Each backup file is created in the same directory with .backup appended to the original name.
If projects created before 2.1 ESD #2 have controls without labels, after migrating to 2.1 ESD #2, error markers appear. You must manually add any missing labels after migrating to 2.1 ESD #2.

Supported Upgrade Scenarios

When Unwired Server is upgraded to version 2.1 ESD #2, no modifications to the earlier deployed versions of Hybrid Web Containers on the server or clients are necessary for the same functionality to operate correctly.

When SDK clients are upgraded from version 2.0 or 2.0.1 to version 2.1.x, version 2.0 and 2.0.1 coexist with 2.1.x 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.

You can install Mobile Workflow applications of different versions, for example, 2.1 and 2.1 ESD #1 on the same device, but if they have the same AppID and same device ID, they cannot connect to the same Unwired Server. Mobile Workflow applications with different AppIDs installed on the same device can connect to the same Unwired Server.

Android

If the 2.1 ESD #2 Android Hybrid Web Container is installed on an Android device in which the previous version of Android Hybrid Web Container is already installed:

The later version of the container upgrades and replaces the previous version of the container.
Existing mobile workflow applications and messages stay intact and are automatically mapped to the 2.1 ESD #2 Hybrid Web Container.
No new registration or re-registration is required on Unwired Server, nor do you need to reassign mobile workflows to the 2.1 ESD #2 Hybrid Web Container.

BlackBerry

If the 2.1 BlackBerry mobile workflow container is installed on a BlackBerry device on which an earlier version of BlackBerry Hybrid Web Container is already installed:

The Hybrid Web Containers coexist on that BlackBerry device or simulator.
The existing mobile workflow applications and messages remain tied to the earlier version of the container and are not removed.
A new application connection on Unwired Server is required for the 2.1 ESD #2 container, mobile workflows must be assigned to the 2.1 ESD #2 container, and the connection settings must be entered in the 2.1 ESD #2 application.

iOS

If the 2.1 ESD #2 Hybrid Web Container is installed on an iOS device on which the 2.0, 2.0.1, or 2.1 iOS Hybrid Web Container is already installed:

The version 2.1 ESD #2 Hybrid Web Container replaces the 2.0, 2.0.1, 2.1, or 2.1 ESD #1 container.
Existing mobile workflow applications and messages stay intact and are automatically mapped to the 2.1 ESD #2 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 ESD #2 container.

Windows Mobile

If the version 2.1 ESD #2 Hybrid Web Container is installed on a Windows Mobile device on which the 2.0, 2.0.1, 2.1, or 2.1 ESD #1 Hybrid Web Container is already installed:

The two Hybrid Web Containers coexist on that Windows Mobile device or emulator.
The existing mobile workflow applications and messages remain tied to the version 2.0, 2.0.1, 2.1, or 2.1 ESD #1 Hybrid Web Container and are not removed.
A new application connection on Unwired Server is required for the 2.1 ESD #2 container, mobile workflows must be assigned to the 2.1 ESD #2 container, and the connection settings must be entered in the 2.1 ESD #2 mobile workflow application.
When the 2.1 ESD #2 container is installed, and a version 2.0, 2.0.1, 2.1, or 2.1 ESD #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, 2.0.1, or 2.1 container.
Workflow messages in the inbox open whichever container version they are associated with. If 2.0 or 2.0.1, or 2.1.x are assigned to the same workflow and have messages sent to the user, two e-mail messages are sent — one for each registration.

The Windows Mobile Programs folder has icons for accessing 2.0, 2.0.1, and 2.1 settings. Versions 2.0 and 2.0.1 icons and names remain. For 2.1.x, two new icons are present—Workflow Settings for the 2.1.x settings application and Sybase Mobile Workflow for the 2.1.x workflow application.