Hello,
you can also send a mail notification just before signaling the error
(I find this very useful to know when users are doing something
they're not supossed to do).
To avoid the notification being deferred to a later phase (which will
never come), you have to change the name of the filter so it ends with
"`!" ( back quote + exclamation mark )
See "Overriding filter processing phasing" in the Basic Guide.
Cheers,
Carlos
On 9/15/06, Misi Mladoniczky <[EMAIL PROTECTED]> wrote:
Hi!
It all depends on what you mean by "capture".
1. If you are programming an API-program, you can will get the error
message, and can code according to the message list returned.
2. You can capture errors in logfiles. Any failed API-calls will have the
text FAIL attached to the ending API-row in the logfile. Put filters/sql
in the same logfile, and you will be able to see what happened.
3. You can send ERROR-messages to ARUser, to prompt the user to fix a
problem and re-save
4. Errors occuring in Filters can usually be circumvented by doing some
tests by creating additional filters. Instead of an ERROR-message, you can
do separate actions that can handle the situation.
Best Regards - Misi, RRR AB, http://www.rrr.se
> Hi,
>
>
>
> All of the my workflows are written in filters..the problem is all
> filters are rolling back when there is any error occurred in any one of
> the filter..
>
> Could you please help me on how to capture errors occurred in filter..
>
>
>
> Any tips would be appreciated.
>
>
>
> Thanks and Regards,
>
> Gopala Krishna.Peela
>
>
>
>
>
>
>
>
>
_______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
