Known Issues for Sybase Unwired WorkSpace – Mobile Workflow Package Development

The pop-up menu stays open after a selection is made, instead of closing as expected. Making additional selections of the same menu item are ignored. This behavior is observed only with many menu selections in a single screen (~12+).

Workaround: Click Cancel to close the pop-up window.

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.

Workaround: Regenerate and redeploy the Mobile Workflow application using a 2.1.2 version of the Mobile Workflow Package generation wizard.

Even though the Mobile Workflow application is unassigned on the client side, the subscription information still shows the package is assigned to the user in Sybase Control Center.

Workaround: None.

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.

Workaround: For best performance, keep the number of rows in choice controls under 200.

Workaround: None.

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.

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.

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.

SELECT x.* FROM Customer x WHERE x.state = :state 

Workaround: None.

"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.

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.

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.

Workaround: None.

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.

Workaround: None.

Workaround: There are two workarounds for this issue:

1. When the password control has focus, press the scroll button and scroll to the left, then it accepts input.
2. When the password control has focus, press the Menu button, choose Select, and then move the cursor to the password control.

Workaround: Copy and paste only one Listview or Htmlview at a time.