3.2.4.5 GetJobHistory
The GetJobHistory operation is used to query the scan repository for information about completed PostScan jobs.
-
<wsdl:operation name="GetJobHistory"> <wsdl:input message="dsc:GetJobHistoryRequestMsg" wsa:Action="http://schemas.microsoft.com/windows/2008/12/wdp/ distributedscan/configuration/GetJobHistory"/> <wsdl:output message="dsc:GetJobHistoryResponseMsg" wsa:Action="http://schemas.microsoft.com/windows/2008/12/wdp/ distributedscan/configuration/GetJobHistoryResponse"/> </wsdl:operation>
Upon receiving a dsc:GetJobHistoryRequestMsg, the server MUST respond with an dsc:GetJobHistoryResponseMsg or a SOAP fault, as follows:
If the server encounters an unexpected error from which it can recover while processing the dsc:GetJobHistoryRequestMsg, 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:GetJobHistoryRequestMsg, the server MUST return a dsc:ServerErrorInternalError SOAP fault depending on the severity of the unexpected error.
If the server can successfully process the dsc:GetJobHistoryRequestMsg, the server MUST return a dsc:GetJobHistoryResponseMsg with the following requirements:
The GetJobHistoryResponseMsg MUST have one dsc:JobHistory child that MUST contain as many dsc:JobSummary children as there are completed PostScan jobs saved by the scan repository that received the GetJobHistoryRequestMsg. The number of PostScan jobs saved is server dependent.
Each child corresponding to a completed PostScan job MUST have the following characteristics:
The contents of the element MUST be set as follows:
All the data elements of the dsc:JobSummary element MUST contain the corresponding data from the PostScan job.
Vendor-defined child elements MAY be added.