Determine the causes of problems the system administrator encounters and apply the recommended solutions.
Existing Users are Disabled after Mobile Workflow Configuration Changes
Issue: Once a user has Mobile Workflow working properly on the device, and is communicating successfully with the server, changes in the supporting configuration may leave that user's device unable to function with Mobile Workflow. Additionally, the system may be unable to show a useful error message to either the user or the administrator.
Synchronous requests
- When the administrator unassigns a workflow package from a user, the user is still allowed to complete an incomplete request and submit the request to SAP.
- If the administrator removes the user from the server, the user receives the message Invalid user name and activation code when selecting a synchronous action button to continue the request.
- After uninstalling the workflow package, the user receives the message ProcessSyncRequest: No plugin configuration found for device/module/version when he or she clicks on a synchronous action button to continue the request.
Submit requests
- When the administrator unassigns a workflow package from a user, the user can submit a request and the request is created.
- If the administrator removes the user from the server, the user can submit the request without receiving a error. However, the request does not reach the server and no error message is returned to the device.
- After uninstalling the workflow package, the user can submit a request without an error. However, the request will not reach the server, and no error message is returned to the device.
Workaround: Before you uninstall Mobile Workflow, or unassign a device from a Mobile Workflow workflow, or delete a user from Unwired Server, first inform the device user. Then remove the client application from the device and lastly perform the procedure. This sequence prevents the user from encountering the problems above.
User is Authenticated Repeatedly with Mobile Workflow in an Unwired Platform Cluster
Issue: With Mobile Workflow installed in a Sybase Unwired Platform cluster, after being authenticated successfully on the initial activation screen, user is asked to enter credentials again at various points.
Workaround: This problem can be caused by the following:
- The Unwired Platform cluster installation assumed that an existing Unwired Platform database could be used without migrating the data. Unwired Platform cannot be directly reinstalled to use an existing data tier. You must migrate the runtime data from the earlier installation into the reinstalled Unwired Platform cluster. See Installation Guide for Sybase Unwired Platform 1.5.2 > Upgrading and Migrating > Performing Migration Tasks > Migrating Production Unwired Server Runtime Data.
User Leaving Activation Success Screen Open Blocks Reassignment of Workflow to Same User.
Issue: If a user activates a workflow and leaves the Activation Successful screen open while the administrator unassigns and reassigns that workflow to the same user, that user will not be able to activate the reassigned workflow from the device.
Workaround: Unassign and reassign the workflow to the same user again, making sure the user closes the Activation Success screen this time.