Tadeu,
You have found your problem. How to fix it depends on more details
than you have disclosed so let me point out what I am fairly sure is
the problem.
A) The condition your using in your push action might need to change
during the loop to get the results your after.
And/OR
B) The records your creating need to be "more different" to avoid an
index on the target form
And/Or
C) The record your left with in the current transaction needs to be
"more different" to avoid an index on the working form.
(Assuming your "if no match' = "Create a new record")
Condition 2 and 4 confirms that the Push If qualification your using
does not match a record _initially_. But condition 3 indicates that it
does match records that are created by the filter loop.
So...
For Possibility A)
You may need to do an "initial" push (with the qualification) that you
have, and use a different qualification for the 2nd through Nth loops
through the vector of data.
However you have not posted the qualifications/data details so it is
impossible for me to give you advice on how you can make those
alterations.
For Possibility B)
A record that the push action is making may be conflicting with a
unique index on the target form. (Again it all depends on the exact
data involved.) It might be that the first record is ok, but the
second one is to much like the first. (Or something like that.)
For Possibility C)
It is possible that the workflow on the record that is spawing the
target records is left in a state that violates an index on that
record too. So after all of the looping is done, then the whole
transaction is rolled back due to an inability to commit the spawing
record to the DB.
It is very hard to tell if B and/or C are the issue, but I seem them
as definite possibilities. I really think A is your main problem.
HTH
--
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 Wed, Feb 27, 2008 at 1:18 PM, Tadeu Augusto Dutra Pinto
<[EMAIL PROTECTED]> wrote:
<snip>
> What I've noticed is that workflow behavior changes if I modify the opiton
> If Any Requests Match in my Filter that executes the Push Fields Action...
>
> Here are the occurrences:
<snip>
> 2 - If I use Modify First Matching Request, the record is saved in my First
> form, but workflow is not completed...
>
> P.S.: I'm wishing to insert 3 records that are in a character field
> separated by "blank space", and only the last record is created on my Second
> Form... Although, my Filter Guide Loop shows on log file that the Loop has
> been executed successfully (setting my auxiliar field with all the values of
> my vector*). Then, I've concluded that my Filter that creates a record on my
> Second Form is, on truth, "modifying" the record that was created in first
> run loop....
>
> * vector - character field separated by "blank space";
>
> 3 - If I use Modify All Matching Requests, I receive the following message:
>
> ARERR [382] The value(s) for this entry violate a unique index that has been
> defined for this form : User entry:000000000000003
>
> 4 - And finally, If I use Take No Action, the workflow (Push Fields) is not
> executed...
>
> ---
> Tadeu Augusto Dutra Pinto
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
