Beyond the new features described at the start of this document, Unwired WorkSpace has undergone further enhancements.
- Complete Visual Studio project support – Now, when generating C# Object API code for Mobile Application projects from Eclipse, a Visual Studio .NET project (.csproj) file.
Documented in:
- Sybase Unwired Workspace - Device Application Development – Search for:
- Rebuilding the Generated Solution in Visual Studio
- Mobile workflow development enhancements – Several improvements have been made to the development of mobile workflow packages:
- Requires activation key and Credentials cache key are
two new properties that have been added to allow the user to specify a key to use for activation or credentials. If the developer does not supply a key, then different keys are used for every workflow by default, which replicates workflow behavior used by 1.5.2 versions of workflow packages. However, this default behaviour can be changed so that one or more workflow packages share the same activation/credential keys. If the developer activates one workflow, then all other workflows sharing the same activation key do not need to be activated separately. Similarly, if there is more than one workflow with the same credentials key, they can all share the same credentials without having to separately define the authentication for each workflow.
- You can now bind the parameters of an operation or object query to context data in addition to a key. Some examples of context data include: BackEndPassword, BackEndUser, DeviceId, DeviceName, DeviceType, UserName, MessageId, ModuleName, ModuleVersion, QueueId.
- You can now extract to a key instead of extracting to a parameter. Values you extract to a key can, in turn, be mapped to parameters. This allows developers to extract values from the notification without needing to use them right away as parameter values. Instead developers can either bind them to controls and display them to the user, or use them later on in the workflow to submit a create, read, update, or delete operation, or other uses.
- The error screen that appeared during the server transformation for synchronous submit errors no longer appears. In this release, only the asynchronous submits generate exceptions from the Unwired Server, which checks to see whether the exception is recoverable or unrecoverable, or whether a credential check failed.
If the exception is recoverable, the workflow is returned to the queue, but with a default of a 15 minute timeout. If the exception is unrecoverable, the workflow is returned to the queue with a default of a three day timeout. This timeout temporarily blocks that workflow's queue and allows the administrator an opportunity to address the underlying cause of the exception. The administrator must address the exception. If the credential fails, an error appears in the credentials screen via a workflow message.
Documented in:
- Developer Reference for Mobile Workflow Packages or Sybase Unwired WorkSpace - Device Application Development – search for:
- Develop a Mobile Workflow
- Modified name for SAP attribute mapping option – The No-Output-Table has been renamed to Header Fields. The functionality of this option remains the same.
Documented in:
- Sybase Unwired WorkSpace - Mobile Business Object Development – search for:
- Creating Multiple MBOs from a Single EIS Operation
- Improved language support for SAP JCo driver connections – Developers can now either choose or type the correct language property for SAP data source connections. If manually entering this value, a valid language length is two characters. Only two characters are used by SAP JCo driver.
Documented in:
- Sybase Unwired WorkSpace - Mobile Business Object Development – search for:
- Creating an SAP Connection Profile
- Partition-level invalidation for cache-affecting operations changes – The behavior of the Invalidate the cache cache policy has changed to enhance cache performance. Now, this policy restricts invalidation to only those cache partitions that are affected by the create
or update operation, and the previous behavior for this policy is removed. The Invalidate the cache policy cannot be used for MBOs that have data populated by data change notifications (DCNs).
Documented in:
- Sybase Unwired WorkSpace - Mobile Business Object Development – search for: