Learn about known issues and apply workarounds for Unwired WorkSpace and Mobile Workflow application development.
| CR # | Description |
|---|---|
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. |