I_ModifyWIPDATA Return Status Is Always Success Even For Invalid Request
(Doc ID 2203616.1)
Last updated on MARCH 31, 2019
Applies to:Oracle Documaker - Version 11.5 and later
Information in this document applies to any platform.
A series of requests are submitted to IDS via EWPS when finalizing a transaction. During each request the attachment variable “RESULTS” is inspected for errors. A i_ModifyWipData request that has a PDF file attached in the payload is returned.
The below response is appearing:
2016-10-05 05:30:06,354 Contents of DSI message is:
Request Type: i_ModifyWIPDATA
DPR0014 Row 1 AREA=DXMLoadXMLRecs
MESSAGE=XML Parse Error: The 7 chars before error=<%PDF-1.>, the 20 chars starting at error=<3
221 0 obj
Row 2 AREA=DXMLoadXMLRecs
MESSAGE=not well-formed (invalid token) at line 1 column 8
Row 3 AREA=DPRLoadXMLAttachment
ERRORS Row 1 CODE=DPR0014
Row 2 CODE=DPR0014
Row 3 CODE=DPR0014
Obviously, the request type expects a XML file to update WIP based on the rules that are listed under the request type. User is researching why a PDF payload is attached to the message sent to IDS via EWPS currently. Debugging information is turned on at the EWPS and IDS level to help resolve this.
The impact to the business is with the failure to detect an error occurred using the RESULTS attachment variable. The workflow completes with an invalid transaction being placed in Mobius. The issue is not reported until the print team flags the output as being incorrect.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document