Set SDO
- Monica Jacobsen
In this scenario, there are some prerequisites:
The unsigned document is generated by etinglysing.
The document is signed by required parties
Set SDO The integrator initiates the process by sending a SDO to www.etinglysing.no, with the documents unique ID in etinglysing as input.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dok="http://dokument.ws7.etinglysing.no/">
<soapenv:Header/>
<soapenv:Body>
<dok:setSDO>
<documentId>12345</documentId>
<sdo>Byte64 representation</sdo>
</dok:setSDO>
</soapenv:Body>
</soapenv:Envelope>
Example response
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:getStatusResponse xmlns:ns2="http://dokument.ws7.etinglysing.no/">
<ns2:return>
<status>
<created>2018-08-02T14:00:09.205+02:00</created>
<documentStatusTinglysing/>
<id>45721524</id>
<statusCode>SIGNERT</statusCode>
</status>
<type>PANTEDOKUMENT</type>
<documentVersion>KARTVERKET</documentVersion>
</ns2:return>
</ns2:getStatusResponse>
</soap:Body>
</soap:Envelope>
Alternative flow Set SDO - Error in provided SDO
In this case the web service has detected an error, due to an invalid SDO or that the content is changed from what was generated. In this case the response will indicate the error. The document will not be updated with the received SDO, which will be reflected in the document status.
Set SDO as list
This scenario is equal to the setSDO function, but enables the integrator to send multiple SDOs in a list, and return multiple responses.