Depending on what you want to do, you can ‘bypass’ this through native 
workflow.. For the same search condition that returns a no match error, perform 
a search to set the request ID or a unique identifier to a temporary field. 
This field would then tell you if records exist or not.. matching records exist 
this field will not be null. If no records exist it will be null..

You can use this information to go forward from there..

Joe

From: Shiju John 
Sent: Wednesday, September 14, 2011 8:26 AM
Newsgroups: public.remedy.arsystem.general
To: [email protected] 
Subject: Re: Can we disable the ARSWARN 1200 (No Records Matched) error?

** 
Actually in my scenario, I have a read only form which has two fields and a 
button. Based on the values entered in the fields I am doing some 
calculations(SQL Query as well as table looping) and populating the read-only 
fields below. I am able to perform this, but at the end I am getting a warning 
message - ARSWARN 1200, which is of no meaning, since the current form is a 
read-only form.
Hence I was thinking of just disabling that warning message. 

But right now my doubt is that, any how that warning message is thrown through 
remedy work flows only. Then why are they not tracked in the logs?
If I can get the work flow name i can just remove my read-only form's name from 
the 'Associated Forms'. :)

Thanks,
Shiju....


On Wed, Sep 14, 2011 at 3:21 PM, Matt Laurenceau <[email protected]> 
wrote:

  This is native in AR System.
  I believe you can change the wording with "AR System Message Catalog" form.
  If you fully remove this msg (in case it's possible), what feedback will you 
send to the user?

  Thanks,

  Matt Laurenceau
  Senior Community Ambassador, BMC Communities
  [email protected]
  Follow me @Matt_L
  Skype: matt.laurenceau


  On 14 sept. 2011, at 13:22, Shiju John <[email protected]> wrote:

  > **

  > Hi,
  > Is there any option to disable the ARSWARN 1200 Message - which is 
displayed when No Records are matched on a search.
  >
  > Please help me in tracking the workflow names which are responsible for 
these default messages, as these are not tracked in either client side or 
server side logs.
  >
  > Thanks and Regards,
  > Shiju John

  > _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"




-- 

Thanks and Regards,
Shiju John

_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