Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Management2017.11

Integrate > Service Manager integration methods and tools > Web Services > SOAP API > Consuming a Service Manager Web Service > The response

The response

<SOAP-ENV:Envelope 
 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
      <RetrieveIncidentKeysListResponse message="Success" 
       query="" returnCode="0" schemaRevisionDate="2007-04-14"  
       schemaRevisionLevel="1" status="SUCCESS" 
       xsi:schemaLocation="http://servicecenter.peregrine.com/PWS 
       http://<sm server>.americas.hpqcorp.net:13701/sc62server/ws/
       Incident.xsd" 
       xmlns="http://servicecenter.peregrine.com/PWS" 
       xmlns:cmn="http://servicecenter.peregrine.com/PWS/Common" 
       xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <keys>
            <IncidentID type="String">IM10055</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10063</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10070</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10077</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10090</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10115</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10116</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10117</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10118</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10119</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10120</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10121</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10122</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10123</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10124</IncidentID>
         </keys>
         <keys>
            <IncidentID type="String">IM10125</IncidentID>
         </keys>
      </RetrieveIncidentKeysListResponse>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Note The field names in such directly entered query strings reflect either the actual field names (such as update.time) or the Caption (such as UpdateTime). Clients who want to submit an expert/advanced query should use either the query attribute on the <keys> element or the query attribute on the <instance> element. Both are provided because some requests do not define any <instance> element. During SOAP API request processing, the server will look first at the <keys> element and, if there is no query attribute there, will look at the <instance> element. Query attributes defined on any other element are never consulted during inbound SOAP request processing.

Send Help Center feedback