UpdateTestsResponse

A response to an UpdateOrDeleteTestsRequest. Contains a collection of 0 to many MonitorOrderResponses (actually monitor update order responses). If no errors occurred during processing, there should be as many monitor update order responses as there were monitor update order requests. If a failure occurred during processing, at the most one monitor update order response will contain a failure, since processing halts after the first failure. Successfully processed monitor order requests will be committed. However, no change resulting from a failure to complete a monitor update will be committed.

Derived by

Type ProvisioningResponseType

Content model

Contains elements as defined in the following table.

Component Type Occurs Nillable? Description
SEQUENCE   1..1    
ResponseStatus ResponseStatusType 1..1 No This element appears in most of the responses issued when the Test Management API operations are invoked.
ErrorMessage [type OperationResponseType] string 0..1 No The error message is provided if the ResponseStatus was FAILURE.
MonitorOrderResponses anyType (restriction) 1..1 No MonitorOrderResponses are collections of MonitorOrderResponse elements. They occur in the responses of both ProvisionTests and UpdateTests operation invocations. See the MonitorOrderResponse help page for more information.

Example

<UpdateTestsResponse
   xmlns="http://www.gomeznetworks.com/schemas/provisioning">
   <ResponseStatus>SUCCESS</ResponseStatus>
   <MonitorOrderResponses>
      <MonitorOrderResponse name="js_2012-08-16T13:11:50.460_FF 2" folder="ws_provision"
            monitorId="306528" monitorStatus="Active" orderStatus="SUCCESS">
         <Message>Successfully provisioned monitor: AccountName = DEV - Eric Smith,
            MonitorName = eg_2012-08-16T13:11:50.460_FF 2, MonitorId =306528</Message>
      </MonitorOrderResponse>
   </MonitorOrderResponses>
</UpdateTestsResponse>