Share via

3.2.4.3 GetPostScanJobElements

  • Article

The GetPostScanJobElements operation is used to query the scan repository for information pertaining to a single PostScan job.

 <wsdl:operation name="GetPostScanJobElements">
    <wsdl:input message="dsc:GetPostScanJobElementsRequestMsg" 
       wsa:Action="http://schemas.microsoft.com/windows/2008/12/wdp/
       distributedscan/configuration/GetPostScanJobElements"/>
    <wsdl:output message="dsc:GetPostScanJobElementsResponseMsg" 
       wsa:Action="http://schemas.microsoft.com/windows/2008/12/wdp/
       distributedscan/configuration/GetPostScanJobElementsResponse"/>
 </wsdl:operation>
 

Upon receiving a dsc:GetPostScanJobElementsRequestMsg message, the server MUST respond with an dsc:GetPostScanJobElementsResponseMsg message or a SOAP fault, as follows:

  • If the server cannot validate the arguments of the dsc:GetPostScanJobElementsRequestMsg, the server MUST return a dsc:InvalidArgs SOAP fault.<15>

  • If the server encounters an unexpected error from which it can recover while processing the dsc:GetPostScanJobElementsRequestMsg, the server MUST return a dsc:ServerErrorTemporaryError SOAP fault.

  • If the server encounters an unexpected error from which it cannot recover while processing the dsc:GetPostScanJobElementsRequestMsg, the server MUST return a dsc:ServerErrorInternalError SOAP fault depending on the severity of the unexpected error.

  • If the server does not have a PostScan job whose unique identifier matches the value specified in the dsc:JobToken element of the dsc:GetPostScanJobElementsRequest element, the server MUST return an dsc:ClientErrorJobTokenNotFound fault.

  • If the server does have a PostScan job that matches the dsc:JobToken element of the dsc:GetPostScanJobElementsRequest element, the server MUST respond with an dsc:GetPostScanJobElementsResponseMsg message.

  • The dsc:GetPostScanJobElementsResponseMsg element MUST have one dsc:JobElements child, which MUST contain as many dsc:ElementData children as there were dsc:Name children in the request message, and the dsc:ElementData children MUST be in the same order as the dsc:Name children in the request message.

  • Each dsc:ElementData child corresponding to an dsc:Name child of the request's dsc:RequestedElements element MUST have the following characteristics:

    • The attributes of the dsc:ElementData child MUST be set as follows:

      • The Name attribute MUST be set to the same value as the value of the corresponding dsc:Name element of the request.

      • If the requested element is known by the server, the Valid attribute MUST be set to "true"; otherwise, if the requested element is not known by the server, the Valid attribute MUST be set to "false".<16>

      • Vendor-defined attributes MAY be added.

    • The contents of the element MUST be set as follows:

      • If the element is a status element, an dsc:JobStatus child element MUST be added.

      • If the element is a description element, an dsc:JobDescription element MUST be added.

      • If the element is a documents element, an dsc:Documents element MUST be added.

      • Vendor-defined child elements MAY be added.