John,
By any chance.... this is workflow actually firing on an Outer Join form?
Is the workflow actually "breaking" the Join conditions between Form A
and Form B as part of it's processing?
The reason I ask is that I reciently found what I would call an odd
behaviour in ARS with Outer Join forms. Apparently at the end of a
SetEntry (Modify) event the ARS server fetches the Joins 'Entry ID'
value back from the DB. ( I presume this is sanity check to verify
that the pending "GetEntry" call from the client will work.) If the
ARS server sees that the 'Entry ID' of the Join is no longer valid it
then issues a "roleback" to the transaction that broke the 'EntryID'
in question.
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
On 2/19/07, John Kovalcik <[EMAIL PROTECTED]> wrote:
**
All,
I have an escalation that updates a record on "Table A". When that
record is updated a filter then pushes data to a "Table B". If the matching
record on Table B has a warning fired from a filter, then the change rolls
itself back out of Table A and Table B.
Is there anyway around this ???
Thanks,
John M. Kovalcik
Kennametal Inc.
__20060125_______________________This posting was
submitted with HTML in it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
