I'll try this as well! Thanks!
Lisa -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Tuesday, October 08, 2013 2:35 PM To: arslist@ARSLIST.ORG Subject: Re: Display No Match Error ** Another suggestion is to do the lookup with Filters using a Service action from an Active Link Or did I just muddy the waters even more ;) Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mueller, Doug Sent: Tuesday, October 08, 2013 1:25 PM To: arslist@ARSLIST.ORG Subject: Re: Display No Match Error ** Lisa and others, There have been a number of responses to this message - from support to alternate options. The suggestion you have was considered, but it has serious limitations. What if you wanted the system message AND your message? What if you wanted a warning instead of an error? What if you wanted no error but to put a default value in the field? What if you wanted to send a notification but still error? What if you wanted to send a notification, set a default, and NOT error? What if you wanted to ...... Just saying you want to have a message is very limiting and just handles one permutation of what people want to do. And, there are issues like What about localization? Suddenly there is a new place errors can come from and localization needs to be addressed. There is already a mechanism to handle all these different options - workflow. And, in FILTERS, there is a clean mechanism to have the logic triggered - the error handler functionality. This functionality allows you to specify a filter to be called if the current filter encounters an error. Then, you can do ANYTHING you want in that filter - including calling guides and multiple actions. In addition, it has a number of important characteristics: If you match the "run if" condition of the error handler, the error that was encountered is suppressed. The error condition disappears and the error itself disappears. You then execute the actions on the if branch and then continue with the filter following the original filter as if no error occurred. So, you do not get double errors under this condition as the system error is suppressed (if you are seeing the system error in addition still, that is a bug). if you do not, the error encountered is retained, but the else branch (if any) still runs and the actions there can do whatever you want. When they complete, the workflow terminates with the error. Your actions in either branch can be anything - including issuing another error. In addition, there are keywords that let you test the error number if you want to take action only on specific error numbers (like in this case, a no match error you want to handle but something else like a syntax or DB error you don't). Now, this sounds perfect. EXCEPT, error handlers are available for filters at this time but not for active links. Now, if your proposal is to add error handlers to active links..... That is a terrific idea and it provides all the flexibility you are looking for. But, to just handle one special condition by adding a special way to handle one path is not that exciting. It is limiting to your flexibility at minimal savings of definition. And, to do it, you would need a multi-match error error message and then push fields would need the special handling for each and then.... It just spirals and has no end, and you have handled one limited set of conditions. The error handler handles everything in one clean, generic way with as much flexibility for processing as you could ever need. For those of you looking for handling within filters, check out the documentation around this feature, I think you will find it can do what you need. For those needing it on the client side, this feature is not present within active links at this time. I personally wish it was, but it is not. Doug Mueller From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Kemes, Lisa A DLA CTR INFORMATION OPERATIONS Sent: Tuesday, October 08, 2013 7:59 AM To: arslist@ARSLIST.ORG <mailto:arslist@ARSLIST.ORG> Subject: Display No Match Error ** I checked the BMC Communities (under BMC Remedy AR System) to see if anything matched my idea and I couldn't find anything. I'd like to make another drop down for set and field actions to compliment the "Display No Match Error." I'd like to have the ability to create my own error. I know I can do this on my own, but I'd have to create a temp field, populate it, check it, if empty, create my own error. Why can't I do this straight from the Set or Push fields action of an Active Link? It's already doing the work for me, but instead I have to create 3 or more active links (or actions) to create my own error in my own words (instead of the cryptic out of the box error - "No item matches active link conditions; this operation has been defined so that no match generates an error. (ARERR 9278)". So I would like an additional option to be "Display Custom Error." Or something like that. It would automatically be the type: Error, and I can just put some text under the "If No requests Match:" area if "Display Custom Error" is selected. Is this asking too much? Should I add it to the Ideas? Lisa Kemes Remedy Consultant Dev Technology Group DLA Office: (717) 770-6437 Cell Phone: (717) 602-9460 lisa.ke...@devtechnology.com _ARSlist: "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"
