Known Issues for Sybase Unwired WorkSpace – Mobile Workflow Package Development

Workaround: None.

Workaround: Do not format the content of the rmi.xml when debugging the Mobile Workflow using Chrome.

• iOS: not supported.
• Android 2.2: not supported. http://code.google.com/p/android/issues/detail?id=9376
• BlackBerry: supported.
• Windows Mobile: supported. (Only picture the emulator lets you take is a grey/black screen.)

Workaround: None.

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

Workaround: None.

On Windows Mobile, when selecting a picture into the workflow, if the encoded size is less than 512KB, the picture is correctly encoded, and the Create operation executes successfully. If the encoded size is greater than 1MB, you receive error code "-5." If the picture size is between 512K and 1MB, after selecting, you may receive an alert message saying "Error: The parameter is incorrect", or "Not Enough Storage."

Workaround:Take lower resolution pictures so they are not so large. Windows Mobile has a 1 MB limit.

The locale .properties files become dangling, so code generation misses those resources.

Workaround: If you rename a mobile workflow application, you must also manually rename the associated locale .properties files.

This happens when trying to open a version 2.0 Workflow on the iOS device and connecting on version 2.1 of Unwired Server.

Workaround: In SCC use the HWC template to create an application connection and leave the application identifier empty.

When the disabled datetime/date/time HTML field is clicked, the native datetime/date/time picker pops up.

Workaround: None.

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.

Array of structure type personalization keys are not supported.

Workaround: None.

During Mobile Workflow package generation, a warning is seen that validation keys are missing from the <locale>.properties file if screens, controls, menu items and so on have changed in number, for example, you deleted a menu item. Resource strings associated with screens, controls, and menu items do not update sequence correctly.

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.

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

After clicking on a link of the logical type Phone Number or Email Address and returning to the Mobile Workflow application, there is an IE browser window that must be closed before you can return to the running Mobile Workflow application.

<a href="javascript:showUrlInBrowser('mailto:<user_name>@<email_address>.com')">email me</a>

For information about how to use the showURLInBrowser function, see the Developer Guide: Mobile Workflow Packages in the topic Mobile Workflow Application Native Device Functions.

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.

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 list 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 sub-structures.

Workaround: None.

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

Workaround: None.

Workaround: None.

This happens only on some BlackBerry 5.0 devices, and then it happens 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: Use the edit box instead of the slider.

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.

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.