Good question. Honestly, I dont have an exact answer to that..I am also not 
sure if there is any equivalent function in Remedy for that(looking for 
something like "equalsIgnoreCase" in java).

List, is FTS(Full-Text Search) an answer to this question?

Thanks
Chintan.

--- On Tue, 5/10/11, Prasanth Prabhakaran <prasanth.prabhaka...@wipro.com> 
wrote:

From: Prasanth Prabhakaran <prasanth.prabhaka...@wipro.com>
Subject: Re: Web services qualification
To: arslist@ARSLIST.ORG
Date: Tuesday, May 10, 2011, 11:10 PM

**



 
 






Hi Chintan / Vamsi, 

   

   Good morning & Thank you very much for helping me
J  

   

my scenario is what Chintan explained, am using only a
particular field for searching so I need to use the specific qualification in
my WSDL.I have one more question. How can I enable a keyword search with out
case sensitive through WSDL 

   

example :- if I search with test or Test or TEST
it should list all the records which contains the word test in it. Hope I’m
clear with my question. 

   

Looking forward to hearing from you. 

   

Thanks & Regards 

Prasanth.P 



From: Action Request
System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of 
Chintan
Shah

Sent: Wednesday, May 11, 2011 6:34 AM

To: arslist@ARSLIST.ORG

Subject: Re: Web services qualification 



   

**  


 
  
  Vamsi, the problem with that is client has to know
  Label/DBNames(dont remember exactly which one is needed in WSDL). The idea of
  web-service is to hide that information from them, hence places where only
  particular fixed parameters need to be passed, they can be passed as XPATH
  elements.

  

  That way the client does not have to build the entire qualification and just
  need to pass parameters.

  

  eg. using Qualification XPATH Element, client has to build query that might
  look like this

  'Test' LIKE '%Test%'.

  

  using Parameters, client only has to pass value '%Test%'. 

  

  Also, its easier for client to manipulate WSDL if input parameters are
  properly specified. 

  

  Again, this goes only for operations where we know what we want to query. If
  client comes back and says I want to query on every field that is on your
  ticket, then "Qualification" attribute makes complete sense, since
  you will be generalizing your WS operation at that point.

  

  Thanks

  Chintan.

  

  --- On Tue, 5/10/11, patchsk <vamsi...@gmail.com> wrote: 
  

  From: patchsk <vamsi...@gmail.com>

  Subject: Re: Web services qualification

  To: arslist@ARSLIST.ORG

  Date: Tuesday, May 10, 2011, 10:49 AM 
  
  For a getlist operation, by default one of the input
  mapping

  attributes is: Qualification

  You send the qualification as input to remedy using this attribute.

  This qualification is same as what you use in remedy user tool

  advanced qualification bar.

  You do not need to change XPATH element.

  

  

  On May 10, 7:30 am, Prasanth Prabhakaran

  <prasanth.prabhaka...@wipro.com>
  wrote:

  > Dear experts

  >

  > Seeking your help again .

  >

  > I want to  query a list of data using a WSDL for this am using
  GetList

  > operation, how can I give the below qualification in the XPATH.

  >

  > 'Test' LIKE "%test%"

  >

  > Can I use the below qualification for the same in web service / what is

  > the syntax for LIKE query in web services any idea ?

  >

  > 'Test' LIKE XPATH(/ROOT/Test)

  >

  > Thanks & Regards

  >

  > Prasanth.P

  >

  > Please do not print this email unless it is absolutely necessary.

  >

  > The information contained in this electronic message and any attachments
  to this message are intended for the exclusive use of the addressee(s) and
  may contain proprietary, confidential or privileged information. If you are
  not the intended recipient, you should not disseminate, distribute or copy
  this e-mail. Please notify the sender immediately and destroy all copies of
  this message and any attachments.

  >

  > WARNING: Computer viruses can be transmitted via email. The recipient
  should check this email and any attachments for the presence of viruses. The
  company accepts no liability for any damage caused by any virus transmitted
  by this email.

  >

  > www.wipro.com

  >

  > ___________________________________________________________________________
  ____

  > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org

  > attend wwrug11www.wwrug.comARSList: "Where the Answers Are"

  

  
_______________________________________________________________________________

  UNSUBSCRIBE or access ARSlist Archives at www.arslist.org

  attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" 
  
  
 


_attend WWRUG11 www.wwrug.com ARSlist: "Where the
Answers Are"_ 



 Please do not print this email unless it is absolutely necessary.  


 The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com

 

_attend WWRUG11 www.wwrug.com  ARSlist: "Where the Answers Are"_


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to