Duplicate Process Execution

vinsnash

We are using a BO rule:

"IF NSCPers.NewID WAS CHANGED TO 'Yes' THEN
NHQNewIDPending"

With the main form displayed and the box is checked 'Yes' NHQNewIDPending is executed immediately and a transaction is created.

When the instance of the BO is saved the process is executed a second time and we end up with two transactions.

What causes this and how can it be prevented?

Vins Nash

pbrad

Hi,
Evidently the rule conditions are still being met when the object is saved, an easy solution is to enter a new rule in your process 'NHQINewIDPending' to change the NSCPers.NewID back to 'No' or to another value so that the rule conditions are no longer met.
cheers,
Pete

vinsnash

That really confuses me. If I've set the rule to "dynamic calculation" I would expect that when the yes/no attribute check box is changed on the form the attribute is changed in the database. The system sees the attribute "WAS CHANGED TO 'YES'" and then executes the process. Why would it check and see the attribute "WAS CHANGED TO 'YES'" and execute a second and even third time? What's the point of that? I removed the "dynamic" setting thinking possibly that only applies to the display but it made no difference the rule is applied when the user checks the box and again when the "Save" button is clicked and acts as if the attribute was still "No" and was changed to "Yes" at the save function.

I solved the problem by using a second attribute that is changed by the process and setting the yes/no back to "No" immediately in the attribute rule. That's a bit of overkill having to use two attributes in the same BO for the same purpose.

I've been told the "LOG" is straight forward and easy to follow. You couldn't prove that by me. I don't see how you track what his happening and when at all.

Vins Nash