Hi,
So you want to log the error event in a form, and then continue to throw the
actual error?
After your error handler has caught the error, you can do a new Message Action
with the ERROR, ERRMSG and ERRAPPENDMSG keywords to get it to the end user.
The problem is getting the Push to commit to the database so that it does not
roll back with the rest of the transaction.
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Ask the Remedy Licensing Experts (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.
> Dear All,
>
> If I build an error handler which performs the set/push field to capture
> the data, but don't throw an error, the error is considered as 'handled
> successfully' and Remedy continues further operations.
>
> Is there a way to stop further operations when we record error using error
> handler? I am facing a problem when I have written error handler to store
> custom error message and wanted to respond to third party but there are
> other operations performing so I am not able to achieve my result.
>
> Or is there any way we can store Faultstring message before responding to
> third party and sending custom message to third party consuming remedy wsdl?
> Thanks!!
>
> Regards,
> Sandy
>
> _______________________________________________________________________________
> 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"
