Be careful that you consider whether you are talking about Active Links or 
Filters.

This question is about Active Links.

IF it was about filters, then the question about transactions and whether the 
push is committed if the
main operation failed would all be true.

HOWEVER, this is about active links.  Every action performed by an active link 
is performed and committed
immediately.  There is no delay.  There is no transaction.  Each action for 
each active link is a discrete
operation and is performed to completion at the completion of the action.


My real question here is what is the bigger task you are doing.  It seems to me 
that you have BUSINESS
LOGIC encoded in active links.  This is the error in your situation.  BUSINESS 
LOGIC for your application
should always be done in filters.  Filters are run under a single transaction 
and it is an all or none commit
(subject to your overrides of course).  Active links are for screen fiddling or 
for defaulting or for displaying
related data or the like.  They should not be doing the business logic of your 
application.  Hence, there is
no reason for transactions or rollbacks or anything from active links.

It seems to me like you need to move your logic from active links to filters.  
Then, the push field will not
commit unless the operation itself commits.

Something to think about,

Doug Mueller

________________________________
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of LJ LongWing
Sent: Thursday, April 07, 2011 10:01 AM
To: [email protected]
Subject: Re: Push by an AL when error on FL

**
Yes, the entire stack of updates is part of a single transaction, if there is 
an error at any point, everything rolls back.

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Adam Neidzwiecki
Sent: Thursday, April 07, 2011 9:11 AM
To: [email protected]
Subject: Push by an AL when error on FL

**
Hello,

Anybody can help?

I  am on a form A and have an AL to push to a form B.

This is happening when modifying A - no problem (no errors)

Now, if there is an error returned by a FL - attached to form A - further down 
the execution order. Will this error  stop  a push action done by an AL to a 
form B?

Thanks,

Adam
_attend WWRUG11 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