I'm not familiar with that error message. I would start by comparing the data on the newAssignPage and the corresponding pxFlow page. Do they disagree? Are you unable to open the newAssignPage? Does the assignment exist in the database? My guess is that you can't open the assignment, object, but that one exists in the database (because otherwise you'd be getting a flow removed, or flow not at task type error or one saying the assignment doesn't exist). From there, I'd look at the assignment in the DB. Does it appear corrupt? If you create an activity that does an obj-open-by-handle passing in the assignment key, does it load into the clipboard or give you an error? What error do you get?
Thanks a lot for the response. I'm able to see the newAssignPage on the tracer. Attached the screenshot.
Since this application is on Cloud, We don't have access to the database to further debug.
To be more precise with this issue, We are able to proceed with this request further in normal scenario. We have a scenario where we can create a vendor before proceeding with the assignment. So, When we try to create a new vendor(which seems to be working good) within the request, we are unable to proceed further with the above assignment corrupted.
We are creating vendor with this utility - 'createWorkProcess' before proceeding with the assignment.
Posted: 4 years ago
Posted: 3 Nov 2017 8:11 EDT
Mike Townsend (MikeTownsend_GCS)
Director, Technical Support, Customer Service
The good news is both objects exist in the trace. The next step is to open up the newAssignPage and compare it to the contents of the pxFlow page. Do they match up? Also, that doesn't appear to be a trace of the error. What is the page that it fails on? Is it the newAssignPage for the new assignment?