Known Issues for Sybase Unwired WorkSpace – Mobile Workflow Package Development

A workflow user may have trouble when reusing dynamic choice controls, as this example illustrates:

Two MBOs, State and Customer, are used within the workflow, which contains a Choice control with dynamic contents accessed from the MBO's findAll object query. The selected value is passed to the Customer's findByState. The problem is the State's findAll object query online request makes the choice with the correct display name values, but after calling CustsByState (findByState) and closing the Customer screen, most display names in the Choice drop-down are unavailable.

See Creating Dynamic Contents for the Choice Control.

Workaround: None.

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

Workaround: None.

The default language in which the Workflow is created is always shown regardless of the region and locale in which the Android device is configured.

Workaround: None.

If previously entering a non-existant value for the object query, subsequent invocations can return incorrect data to the device.

Workaround: Do not use object queries for attachementViewer controls, or, verify the value passed to the object query exists in the EIS.

Workaround: Use a later version of the simulator, such as 6.0.0.534.

If you are on a root listview that shows a list of top-level MBOs, and you invoke a Submit Workflow menuitem that performs a parent update, those top-level MBOs are not updated.

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.

For example, new Date().getTimezoneOffset() returns 0 for timezones with + offsets. This causes dateTime values being sent from the Workflow to be offset to UTC incorrectly.

Workaround: None.

While you can add items to the list and save the list, when you submit the operation, it is empty.

Workaround: Array/list fields in structure parameters are not supported. You can have a top-level parameter which is an array/list, and you can have a top-level parameter which is a structure which has non-array/list fields and sub-structures.

Workaround: Upgrade Windows Mobile 6 to OS 5.2.1235 or later.

Workaround: None.

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: 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: Since there is no touch gesture, you must switch on the Select option in context menu, then you can move around the cursor with trackball.

The problem occurs only when returning to the original screen after viewing the attachment. In addition, text fields cannot be edited, as the browser appears to be in a read-only state.

Workaround: None.

no workflow message is sent because no device is found 
to send the mail

{"id":"dcntest_test_001","success":false,"statusMessage":
"no workflow message is sent because no device is found to send the mail"
,"result":[{"id":"dcntest_test_data_1","success":true,"statusMessage":""}]} 

"to":" < this SUP user > "

Mobile Workflow push notification is not processed, even though the backend database is updated with the data.

This may happen if another e-mail client is configured and accessing the workflow Notification Mailbox at the same time as the workflow.

Workaround: Do not configure other e-mail clients that may intercept the mobile workflow message before it is sent to the Notification Mailbox.

Mobile Workflow applications run slowly on the iPhone 3G.

Workaround: Sybase recommends that you use iPhone 3GS or iPhone 4 to run Mobile Workflow applications.

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

You cannot send NULL values from the client to the server. If you attempt to retrieve NULL values from the server, the attempt fails.

Workaround: Do not use NULL values.