Re: error handler and stop transaction

[Misi Mladoniczky]

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"

Re: error handler and stop transaction

[Brent Goodman]

Throw everything into a guide. When your error handler triggers, do your data 
push and then jump to the label at the end of the guide and exit, bypassing all 
the rest of the workflow in the guide. I use this setup all the time.

I have seen BMC code that also uses the go to execution order 1000, which will 
bypass workflow as well. I haven't used this method though.

Guides are very useful in directing the workflow route.




Sent from my iPhone

> On Jan 5, 2016, at 1:45 AM, Misi Mladoniczky  wrote:
> 
> 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"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: error handler and stop transaction

[Jason Miller]

I'll have to remember this trick. What I usually do is have a status field
where one of the values is "Error". When the Error Handler filter fires it
sets the status to Error. All of the other worlflow has 'Status' != "Error"
in the Run If so it won't fire once the error has been handled.

The nice thing with capturing the error status is you quickly can find the
records that encountered an error. In most cases my process is set up to
try again when I change the status from Error.

Jason

On Tue, Jan 5, 2016, 9:09 AM Brent Goodman  wrote:

> Throw everything into a guide. When your error handler triggers, do your
> data push and then jump to the label at the end of the guide and exit,
> bypassing all the rest of the workflow in the guide. I use this setup all
> the time.
>
> I have seen BMC code that also uses the go to execution order 1000, which
> will bypass workflow as well. I haven't used this method though.
>
> Guides are very useful in directing the workflow route.
>
>
>
>
> Sent from my iPhone
>
> > On Jan 5, 2016, at 1:45 AM, Misi Mladoniczky  wrote:
> >
> > 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"
>
>
> ___
> 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"

error handler and stop transaction

[Sandeep Pandey]

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"