Learn about known issues and apply workarounds for Unwired WorkSpace and Mobile Workflow application development.
Issue Number | Description |
---|---|
CR 707123 | Uploading large image not successful on some Android devices. This
message appears after selecting an image while in a workflow, but image
previews and uploads continue to
work:
File type is not supported! Workaround:
Because this issue only occurs with the File Manager application, use a
different gallery application by resetting the default:
|
CR 700357 | Comma added for int types when number is more than 1000. On iOS 5.0, with the Safari mobile browser, in fields with the int type, when you enter a number larger than 1000, a comma is inserted. This is expected behavior with the Safari mobile browser. Workaround: Set the logical-type to text instead of numeric. |
CR 700077 | BlackBerry 5 read-only slider can be modified. The anchor can be moved on a slider that is designed to be read-only. This is a known BlackBerry problem. Workaround: None. |
CR 699341 | BlackBerry 7 form labels do not use specified theme. On BlackBerry 7 devices, in a form that uses labels on the left, if the first field is editable, the second label does not initially use the theme set in the form. Workaround: Type in the field to change the label to the appropriate theme. |
CR
698779 | DatePicker control does not reopen in BlackBerry 7+. In a BlackBerry 7 or later device, if you invoke the DatePicker control in a workflow by clicking in a date field, click Cancel in the DatePicker, and then click again in the same field, the DatePicker control does not reopen. Workaround: After clicking Cancel in the DatePicker, click in another field that is not of type DATETIME or TIME. You can then click in the original date field to open the DatePicker. |
CR 694665 | AsyncRequestErrorLogs
key not generated in a migrated project.
If you migrated a Mobile Workflow project that previously contained a submit workflow action, setting its error screen property does not generate the AsyncRequestErrorLogs list key. Workaround: Create a new Submit Workflow action, or click the Generate Error Screen button. |
CR 694652 | In
Mobile Workflow applications generated with a 2.0 version of the Mobile
Workflow Package generation wizard, running on an iPad OS 5 and running
in a 2.1 ESD #2 or later container, edit boxes that should be editable
may not be editable. Workaround: Regenerate and redeploy the Mobile Workflow application using a 2.1 ESD #2 or later version of the Mobile Workflow Package generation wizard. |
CR 690460 | On
BlackBerry devices, in most cases, the module name is the same as the
module display name, but if there is a case when the module name ! =
module display name,the device cannot receive asynchronous error
messages.
Workaround: None. |
CR 690438 | A
workflow does not initiate an operation.
This could happen if the workflow is not constructed correctly. On a Listview details screen, you cannot invoke a submit workflow to invoke an MBO operation that uses child keys of the list key that is bound to that listview. To prevent developers from performing an illegal operation, the keys are removed from the list. However, you can see those keys before making the workflow type operation a Listview details screen because it is not illegal in that circumstance; it is only illegal once you make it a Listview details screen. If you use those keys when it is not a Listview details screen and then make it a Listview details screen, the workflow operation will fail with no indication of the problem. Workaround: Client-initiated workflow: verify that no online request operations (such as findall) precede the submit workflow type operation. If so, remove the operations. Server-initiated workflow: verify that no links (between the start point and the first screen saved) precede the submit workflow operation. If so, remove the links. |
CR 684635 |
Choice
controls with a large number of rows do not behave as expected on some
platforms. Workaround: For best performance, keep the number of rows in choice controls under 200. |
CR 682741 | "Validate controls as soon as the user tries to
change focus away from them"
option in Mobile Workflow Package generation wizard is not supported on
Windows Mobile. Workaround: None. |
CR 681918 | When you click the Workflow icon on iOS devices, you see
the message Sybase Mobile Workflow please go to the settings
application and enter your configuration.... This happens if you attempt to open a version 2.0 workflow on the iOS device and connect to version 2.1 of Unwired Server. Workaround: In Sybase Control Center, use the HWC template to create an application connection and leave the application identifier empty. |
CR 678440 | On BlackBerry devices, you receive an error when running
an HTTPS GET method from the Mobile Workflow Workaround: Refer to the BlackBerry Knowledge Base article at http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB20833&sliceId=1&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=1652002964&stateId=0%200%201652004660. |
CR 677684 | Locale properties file is not updated if screens,
controls, menu items and so on are removed. During Mobile Workflow package generation, you see a warning that validation keys are missing from the <locale>.properties file if screens, controls, menu items and so on have changed in number, for example, if you deleted a menu item. Resource strings associated with screens, controls, and menu items do not correctly update the sequence. Workaround: Either do not remove screens, controls, menu items and so on after localizing, or manually correct the localization .properties file after making the changes. |
CR 675904 | Object
queries in the Online cache group are case-sensitive. If the enterprise information system (EIS) to which an
object query is associated with has case-sensitive parameters, the
client must pass matching parameters or no data is returned. For
example, if the Customer MBO is in an Online cache group, has a load
parameter "state" that is propagated to the attribute "state," and a
findByParameter object query defined as:
SELECT x.* FROM Customer x WHERE x.state = :stateNo data is returned to the client if they enter state=Ca, since the database parameter is case-sensitive (requiring "CA"). This is not an issue for object queries in other types of cache groups. Workaround: None. |
CR 674149 | Exception received with large amounts of data.
When the amount of data is too large to download to the
workflow client device, you may get an exception similar
to:
"iAnywhere.MobileOffice.AMP.ResponseRetryException" on device, and following error in WorkflowClient.log: 20110616T110249.554|4|My:1 -- ExecuteRequest- > Out 20110616T110249.694|1|iAnywhere.MobileOffice.AMP.ResponseRetryException: Exception of type 'iAnywhere.MobileOffice.AMP.ResponseRetryException' was thrown. 20110616T110249.694|1| at Sybase.UnwiredPlatform.WorkflowClient.Utils.CheckMessageSize (String serializedMessage, ContextData oContextData, Boolean fromResponder) 20110616T110249.694|1| at Sybase.UnwiredPlatform.WorkflowClient.Responder.ProcessMessageFromDevice (ContextData oContextData, String sData, Boolean isSynchronous) 20110616T110249.694|1| at Sybase.UnwiredPlatform.WorkflowClient.Responder.ProcessSyncRequest (ContextData oContextData, String sData) 20110616T110249.694|4|My:1 -- ProcessSyncRequest- > Out Workaround: Increase the allowed maximum workflow message size (SupMaximumMessageLength). From Sybase Control Center, expand Workflows and select the workflow of interest. Select the Context Variables tab. Modify the property. |
CR 673572 | Workflows do not work with Android simulators version
2.3.3. See http://code.google.com/p/android/issues/detail?id=12987 for a description of this issue. Workaround: Use an earlier version of the Android simulator. |
CR 671242 | Submit operation is empty if the workflow uses a Web
Service that takes a structure as its input. While you can add items to the listview and save the list, when you submit the operation, it is empty. Array/list fields in structure parameters are not supported. You can have a top-level parameter that is an array/list, and you can have a top-level parameter that is a structure that has non-array/list fields and substructures. Workaround: None. |
CR 669251 | On
a BlackBerry 9630 running OS 5.0, data with the DATETIME type does not
display in certain circumstances. Workaround: None. |
CR 667325 | On
BlackBerry 5.0, if there is a dynamic choice on the screen, labels for
drop-down and comments fields overlap, which hides the drop-down
control.
This happens only on some BlackBerry 5.0 devices, and only intermittently. Workaround: If you know where to click for the drop-down, you can access the drop-down control, and it accepts your choice. |
CR 667187 | The BlackBerry Bold 9700 device simulator sometimes does
not allow the user to have full control of the screen for an
application, and may perform the wrong operations, and return the wrong
results. Real devices work correctly. Workaround: None. |
CR 666672 | On BlackBerry 6.0 simulators (non-touch models), it is
difficult to enter the password. Workaround: There are two workarounds for this issue:
|