Just a thought.. Filters ARE THE WAY TO GO IF what you need to check can be performed at filter level, i.e., its either a check on Submit or Modify or Delete or Merge or Service.
This will ensure that the validation you design will run every time the AR System API is executed irrespective to the type of client that the request has come through. AL's will run only when the Mid-Tier client or the User tool is used. It will not fire when any other client is used such as maybe Web Service or any other API. So the fact that you have got it working with a Filter is great and the right thing to have considered in the first place. Use AL's only for client side actions like if you want something to happen at the press of a button or when you perform any other keyboard action or mouse action. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Timothy Buchanan Sent: Thursday, October 24, 2013 2:56 PM To: [email protected] Subject: Re: Using workflow to compare two fields Thank you! I used this same logic in a filter like you suggested and it works perfectly. Thank you. :) Tim Buchanan Systems Analyst SHS|Information Services -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Misi Mladoniczky Sent: Thursday, October 24, 2013 11:47 AM To: [email protected] Subject: Re: Using workflow to compare two fields Hi, Your thinking is not off. The run-if should contain something like you tried. The problem is probably WHEN to do the check. ACTL:s has some kind of user action as their trigger. I would probably choose to do this in a FLTR instead, as they are run on the server, and controls values before they get stored in the database. ACTL:s are more geared to assist the user, and FLTR:s are the ones to control things. The filter also need a trigger, and that would be Submit and Modify, which corresponds to creating a new (Submit) ticket, and updating an existing ticket (Modify). Make sure to get yourself to some training as soon as possible! Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12/13): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Hello, > > Forgive me if this is a ridiculously simple problem. I inherited > support of our AR System environment from a former trained Admin, but > I myself have been entirely self-taught so there is a bit I do not > know. I am trying to create an active Lync that will throw an error if > there is a mismatch between 2 fields that should contain the same value. > > I have created several active links before this for various things, > but have never had to try and write logic to compare the values > between fields to ensure they are the same, this would be easy if the > values were always supposed to be one, thing, but in this case they > are the Assigned group and the "Owner group" of an incident. > > I tried using the following Logic just as an experiment: 'Assigned > Group' != 'Owner Group' > > This did not throw any errors in Dev Studio, but also does not seem to > be working when I test it. > > I would appreciate any help. Thanks! > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
