VERIFIED SOLUTION i

How to avoid issue where searchDeliveryItems web service request is not working in EngageOne Interactive / On-Demand version 3.1.2 although it is working on earlier versions

Product Feature: Web Service (API)
 
When searchDeliveryItems web service request is submitted in older versions of EngageOne like 3.0 and 3.1.1.1, the response is returned as expected e.g.

 <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <ns4:SearchDeliveryItemsResponse 
xmlns:ns2="http://pb.com/EngageOne/ws/model" 
xmlns:ns3="http://pb.com/EngageOne/ws/common" 
xmlns:ns4="http://pb.com/EngageOne/ws/delivery" 
xmlns:ns5="http://pb.com/EngageOne/ws/editor">
         <deliveryItems>
            <deliveryItem>
               <ns2:id>501</ns2:id>
               <ns2:deliveryChannel>
                  <ns2:id>1</ns2:id>
                  <ns2:name>CH1</ns2:name>
                  <ns2:type>PRINT</ns2:type>
               </ns2:deliveryChannel>
               <ns2:status>COMPOSED</ns2:status>
            </deliveryItem>
         </deliveryItems>
      </ns4:SearchDeliveryItemsResponse>
   </env:Body>
</env:Envelope>


However, in version 3.1.2 (in particular the builds dated 6th September 2016 and older), Fault exception is consistently thrown for the exact same web service request:

<env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns="">env:Server</faultcode>
<faultstring xmlns="">com.pb.engageone.ws.delivery.DeliveryFault</faultstring>
<detail xmlns="">
<ns2:ServiceFault xmlns:ns2="http://pb.com/EngageOne/ws/common" xmlns:ns3="http://pb.com/EngageOne/ws/delivery" xmlns:ns4="http://pb.com/EngageOne/ws/delivery/statusupdate" xmlns:ns5="http://pb.com/EngageOne/ws/model">
<ns2:code>-1</ns2:code>
<ns2:message>Failed to search delivery items.</ns2:message>
</ns2:ServiceFault>
</detail>
</env:Fault>


Above symptom is the result of a defect in version 3.1.2 of older builds (3.1.2.17-build-94 and older).

The defect is fixed as of 3.1.2.17-build-96 released 13th September 2016. Please upgrade to at least this version to see the above defect resolved.
UPDATED:  August 10, 2017