I figured out why the filter is firing twice. We have a bug in our system that causes emails to be sent in duplicates or sometimes in triplicates. I knew it was happening in our live system but didn't realize it was happening in our test system till now.
An event triggers an email, which spawns two AR System Email Messages entries instead of one. Each one of them pushes a value to the other form, which is why the workflow happens twice. Unfortunately, this has nothing to do with why the pushed values aren't showing up. Dwayne Martin ---- Original message ---- >Date: Wed, 12 Sep 2007 13:23:12 -0400 >From: "Joe D'Souza" <[EMAIL PROTECTED]> >Subject: Re: Push field sometimes happens and sometimes doesn't >To: arslist@ARSLIST.ORG > > ** > > The questions about timeouts and entries on the > other table that I asked was to check if it might be > an indexing issue, where there might have been some > sort of search on that table before the push fields > causing a table scan.. With 30 entries that should > not be an issue.. > > The filter may fire twice if it is on submit and a > part of a Filter Guide that is called on Submit.. So > it could fire on the execution order of the filter > on Submit, and then again when the Filter guide is > called in which this filter is a part of. > > Check that.. > > Joe > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] Behalf Of Dwayne > Martin > Sent: Wednesday, September 12, 2007 10:25 AM > To: arslist@ARSLIST.ORG > Subject: Re: Push field sometimes happens and > sometimes doesn't > > First of all, Thanks, Mike, for the info on Linux > servers. We just switched from Unix to Linux. Hope > we haven't made a big mistake. > > Joe, > > > When it doesn't get updated, does the filter log > > show that the filter had fired to perform the > push?? > > Yes, the filter log shows it pushing to the other > form whether the other form gets updated or not. > > > Do you ever get ARERR 93 timeout errors during > these > > operations? > > No, no timeout errors, or errors of any kind. > > > What is the record count of the form into which > you > > are performing these push actions? > > 30 entries > > > What is the Push Field If criteria? > > 'PIQ ID' = $Other Call no$ > > "PIQ ID" is the renamed Entry ID field #1. Workflow > does show "Other Call no" getting set correctly. > And the Push Fields is set to display "No Match" > error if it can't find the record, and we are not > getting any error message. > > Earlier I reported that the SQL updates are > happening twice. The filter log shows that the > filter itself sometimes fires twice and sometimes > once. The filter is firing on Submit, so why would > it fire twice? Contrary to what I reported > yesterday, firing once or twice doesn't seem to have > any affect on whether or not the record gets > updated. > > Thanks, > Dwayne > ---- Original message ---- > >Date: Tue, 11 Sep 2007 17:33:05 -0400 > >From: "Joe D'Souza" <[EMAIL PROTECTED]> > >Subject: Re: Push field sometimes happens and > sometimes doesn't > >To: arslist@ARSLIST.ORG > > > > ** > > When it doesn't get updated, does the filter log > > show that the filter had fired to perform the > push?? > > > > Do you ever get ARERR 93 timeout errors during > these > > operations? > > > > What is the record count of the form into which > you > > are performing these push actions? > > > > What is the Push Field If criteria? > > > > Joe > > > > -----Original Message----- > > From: Action Request System discussion > list(ARSList) > > [mailto:[EMAIL PROTECTED] Behalf Of Mike > > Ellertson > > Sent: Tuesday, September 11, 2007 5:06 PM > > To: arslist@ARSLIST.ORG > > Subject: Re: Push field sometimes happens and > > sometimes doesn't > > > > > > Hi Dwayne, > > > > It seems to me that if the SQL routine you > specified > > was executing twice, it should impact > performance > > but not the actual data. > > > > But I can see you are running a Linux server. I > > have worked with several companies experiencing > > weird Linux problems. About a year ago BMC put > a > > special support swat team into place to address > > Linux issues. I would recommend you putting a > call > > into BMC Remedy support and having the issue > > escalated to them. > > > > Mike Ellertson > > Bushido Technologies, Inc. > > Phone: (949) 705-6991 > > Email: [EMAIL PROTECTED] > > -----Original Message----- > > From: Action Request System discussion > list(ARSList) > > [mailto:[EMAIL PROTECTED] On Behalf Of Dwayne > > Martin > > Sent: Tuesday, September 11, 2007 1:38 PM > > To: arslist@ARSLIST.ORG > > Subject: Push field sometimes happens and > sometimes > > doesn't > > > > > > Hello Everyone, > > > > We have a push fields action to a diary form. > The > > same filter is pushing from the same form in all > > cases. Most of the time it works, but sometimes > the > > field does not get updated. The filter log is > > identical in both cases, and it clearly shows > the > > push taking place. > > > > Both when it work and when it doesn't sql log > shows > > these actions: > > > > SELECT C536870931 [the field getting updated] > FROM > > T580 WHERE C1 = 'PIQ00083' > > UPDATE T580 SET C536870931 = EMPTY_CLOB() WHERE > C1 = > > 'PIQ00083' > > SELECT C536870931 FROM T580 WHERE C1 = > 'PIQ00083' > > FOR UPDATE > > Set LOB into the above row ... > > > > But in the cases where the update fails, the sql > log > > shows this routine happening twice. > > > > What would make the routine happen twice? Could > > second routine be overwriting the first? And > what > > can I do to stop it? > > > > (ARS 7.0.1 p2, Linux server, Oracle 10.2 db) > > > > Dwayne Martin > > Computing Support > > James Madison University > > __20060125_______________________This posting > was > > submitted with HTML in it___ > > Dwayne Martin > Computing Support > James Madison University > > __20060125_______________________This posting was > submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
