I_ModifyWIPDATA Return Status Is Always Success Even For Invalid Request (Doc ID 2203616.1)

Last updated on NOVEMBER 21, 2016

Applies to:

Oracle Documaker - Version 11.5 and later
Information in this document applies to any platform.

Symptoms

Issue:
  
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:

Send:
2016-10-05 05:30:06,354 Contents of DSI message is:
Request Type: i_ModifyWIPDATA
Message variables:
IDSGUID=ED1CC3F7-C39A-95B2-9D59-7013156B2192
IDSHOSTNAME=sau1h041.xxx.com
RESULTS=SUCCESS
SERVERTIMESPENT=1.177

Rowsets:
DPR0014 Row 1 AREA=DXMLoadXMLRecs
  CODE=48
  CODE2=0
  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
  CODE=48
  CODE2=0
  MESSAGE=not well-formed (invalid token) at line 1 column 8
Row 3 AREA=DPRLoadXMLAttachment
  CODE=1
  CODE2=1
  MESSAGE=Cannot DXMLoadXMLSizedBuffer()
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 Xerox print team flags the output as being incorrect.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms