Thanks Thad!

 

Actually I'm not using a specific error handler filter not sure what
that would be.

My next filter checks if the number of rows updated by the Push is 1
(via the LASTCOUNT value) if it is not 1 I do a Message action of type
Error to alert the user.

The filter log shows this error caused the current filter guide to stop
processing steps and all my push changes are not applied to the
database.

However the next filter guide called gets called but only the Set fields
and Run Process action actually does anything the other Push fields
action is not applied.

 

Below is excerpt from the filter log where this happens.


Thanks

Debra

 

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> > Checking
PRN_CMS:LaneAuditReport_Check_Row_Update`! (505)

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >    --> Failed
qualification -- perform else actions

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         0: Set Fields

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >
zTmp_TokenStr (536871643) = 06/30/11  3:01:54 PM - Error Processing
Device Update Transaction ID=000000000002070 Report ID=000000000000294

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         1: Process

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >
/tmp/report_error.sh "06/30/11  3:01:54 PM - Error Processing Device
Update Transaction ID=000000000002070 Report ID=000000000000294" 

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         2: Message

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >               Error
Processing Device Transaction #: 000000000002070

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> > **** Error while
performing filter action

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> > **** Error while
performing filter action

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         2: Call Guide
(this is the 2nd guide which I would expect not to be called at all)

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> > Checking
PRN_CMS:LaneAuditReport_Verify_Updates`! (510)

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >    --> Failed
qualification -- perform else actions

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         0: Set Fields

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >
audit_error_message (536871633) = Processing records failed - Records
prepared= 8 and Records Processed=6

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >
audit_report_status (536871632) = ErrorX

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >
zTmp_TokenStr (536871643) = 06/30/11  3:01:54 PM - Error Processing
Audit Report, Prepared Records != Processed Records.  Report
ID=000000000000294

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         1: Process

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >
/opt/ars/server/db/report_error.sh "06/30/11  3:01:54 PM - Error
Processing Audit Report, Prepared Records != Processed Records.  Report
ID=000000000000294" 

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         2: Push Fields

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> >         2: Push Fields
(ARERR 73001)

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> > **** Error while
performing filter action

<FLTR> <TID: 0000000007> <RPC ID: 0000203425> > **** Error while
performing filter action

 

Debra Anderson
T  415.808.9118   |   F  415.808.3535   
600 Harrison St *   San Francisco, CA   *   94107

PRN | media where & when it matters

This e-mail (including any attachments) is meant for only the intended
recipient of the transmission, and may include confidential information.
If you are not the intended recipient or you received this e-mail in
error, any review, use, dissemination, distribution, or copying of this
e-mail is strictly prohibited.  If you have received this message in
error, please notify the sender immediately by telephone at (415)
808-3500 or by return e-mail and delete this e-mail, along with any
attachments and copies, from your system.  Thank you.



 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Thad Esser
Sent: Friday, July 01, 2011 10:05 AM
To: [email protected]
Subject: Re: Un-expected Filter/Filter Guide Processing when errors
occur....

 

** 

Debra,

 

You say:  "If any of the push actions fail a subsequent filter does the
following"

 

Are you using an Error Handler filter to process the "fail" condition?
If so, once your error handler filter handles the error, the system
considers the error handled and processing continues as if there were no
error.  Phasing is also affected.  Check the Workflow Objects guide for
details (I only 7.1 docs handy, so I don't have a page # for your
version).

 

Hope that helps,

Thad


 

On Thu, Jun 30, 2011 at 3:49 PM, Anderson Debra (PRN)
<[email protected]> wrote:

** 

Hi Everyone!

Hoping folks on the list with more experience might be able to explain
unexpected filter processing behavior I am seeing.

We are using 7.0 version

 

Here is an overview of how my workflow is setup

 

1 - Filter 1A fires on Modify on Form_A - Note this filter name is using
thte `! syntax for override filter phasing.

     Actions are in this:

            Set fields

            Call Guide 2A using server-side table loop

            Call Guide 2B

 

Filter 2A - seems to work as expected (based on review of filter log).
It calls several filters that loop thru table entries again using `!
syntax.  Each entry in the table results in a Push field action to two
forms B & C.  If any of the push actions fail a subsequent filter does
the following 

        1 - Run Process command to run unix script to add entry to log
server file

       2 -   Message action of type Error is reported to end-user

As expected after this error occurs none of the push field changes are
applied to the database - this is what I want to happen J

 

However after the error occurs the top level filter still calls Guide 2B
(I see this in the filter log after the error is logged) however the
actions in the Guide are not fully executed  but the one a Run Process
action on a unix shell command does execute but after this runs the next
actions which are Set/Push fields are not executed.

 

Any ideas why my 2nd Call Guide action would execute after the first
Guide called produces an error - my expectation was that if the first
Guide produced an error the filter that called the guide would stop
processing all together and the 2nd Guide would not be executed at all.

 

Any thoughts?

 

Thanks

Debra

 

Debra Anderson
T  415.808.9118   |   F  415.808.3535   
600 Harrison St *   San Francisco, CA   *   94107

PRN | media where & when it matters

This e-mail (including any attachments) is meant for only the intended
recipient of the transmission, and may include confidential information.
If you are not the intended recipient or you received this e-mail in
error, any review, use, dissemination, distribution, or copying of this
e-mail is strictly prohibited.  If you have received this message in
error, please notify the sender immediately by telephone at (415)
808-3500 <tel:%28415%29%20808-3500>  or by return e-mail and delete this
e-mail, along with any attachments and copies, from your system.  Thank
you.

 

_attend WWRUG11 www.wwrug.com <http://www.wwrug.com/>  ARSlist: "Where
the Answers Are"_


_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to