Why rule executes twice

gust

Hi!
I have a rule that executes twice and cannot understand why. I expected it to execute once. Could you give me any tip on it please?

My rule is - If Appointment WAS ADDED TO Information.Appointments Then CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment

From the log it is seen that it executes twice, but I dont see the reason. And log is

Creating business object Appointment
 -Starting execution of rules when updating references of the business object Information 34
  -Starting execution of rules when updating business object Information 34
    -Started evaluation of rules
      -Evaluating rule 'CreateStage' If Appointment WAS ADDED TO Information.Appointments Then   CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment 
    -Executing action CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment from rules of object Information


Starting execution of rules when updating references of the business object Information 34
 -Started evaluation of rules
      -Evaluating rule 'CreateStage' If Appointment WAS ADDED TO Information.Appointments Then   CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment 
 -Executing action CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment from rules of object Information

gust

PS. The rule is attached to Appointment BO.

gust

As a result it creates two Stage BO's instead of one.

gust

gust wrote
PS. The rule is attached to Appointment BO.

Sorry, but cannot understand how to edit previous message, I mistyped
The rule is attached to Information BO.

aware_support

One possibility is that the first CREATE actually modifies references of the Appointment and Information object again and causes the rule to fire again

gust

Thanks for help, will modify the rule.

gust

Tried to modify it this way

If Appointment WAS ADDED TO Information.Appointments AND NOT(EXISTS Appointment WHERE (Appointment.Stage=AddedAppointment.Stage AND Appointment IN Information.Appointments)) Then 
CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment

and added one more

If EXISTS Appointment WHERE (Appointment.Stage=AddedAppointment.Stage AND Appointment IN Information.Appointments) Then 
REPORT ERROR

But rule fires twice and error is not reported. Cannot understand the reason.

Could you suggest some way how I could stop to run the rule twice?

gust

Dont now is it a good solutions and will it cause a problem in future but adding condition (in bold) in the first rule works by now.

If Appointment WAS ADDED TO Information.Appointments AND AddedAppointment.Stage IS UNDEFINED AND NOT(EXISTS Appointment WHERE (Appointment.Stage=AddedAppointment.Stage AND Appointment IN Information.Appointments)) Then
CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment

What do you think? Looks fine?

tford

I created a simple BSV with BOs needed for your original rule:

If Appointment WAS ADDED TO Information.Appointments Then CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment

For each new instance of Information I create, the rule only creates one new instance of Stage.

What steps are you performing when you get your rule firing twice? What are the reference relationships between your BOs?

gust

Hi, Tom!
Here are BSV examples

Rule fires twice http://www.2shared.com/file/68ssAarg/Test_notworking_.html
Working example http://www.2shared.com/file/jBD0bJjW/Test_working_.html

Firstly you have to create Information BO and only then

Add there Appointment with stage=anything you type
Add File where you can choose added stage

tford

What do you mean by "working" example?

ACDC

One way of getting around this is to place a rule on the Information Object rather than the Appointment Object

Something like: If Information.Appointment is defined THEN ......

tford

I'm not sure what your issues is with the BSV. When you say the rule fires twice, I would expect that 2 stage instances would be created. I did not look at the logs, but in the test of both my test BSV and your test BSV, only one stage record was created as for each new instance of Information.

gust

Tom, Rule creates two stages in this example (Rule fires twice) http://www.2shared.com/file/68ssAarg/Test_notworking_.html
The rule is:

If Appointment WAS ADDED TO Information.Appointments AND NOT(EXISTS Appointment WHERE (Appointment.Stage=AddedAppointment.Stage AND Appointment IN Information.Appointments)) Then
CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment

Here is screenshot:

In the second example only one instance of stage is created
The rule is:

If Appointment WAS ADDED TO Information.Appointments AND AddedAppointment.Stage IS UNDEFINED AND NOT(EXISTS Appointment WHERE (Appointment.Stage=AddedAppointment.Stage AND Appointment IN Information.Appointments)) Then
CREATE Stage WITH Stage.Stage=AddedAppointment.Stage,Stage.Appointments=AddedAppointment

Working example http://www.2shared.com/file/jBD0bJjW/Test_working_.html

ACDC, The rule is attached to Information BO.

vinsnash

I had several similar instances of rules executing twice and ending up with duplicate transaction records.

The similarity was a rule with a compound condition involving two objects and the rule executing when each object is 'evaluated' for changes.

The solution I found is to always have CREATE functions in separate "stand alone" processes and executed from an object rule or another process rule.

I also broke up compound conditions by testing for one element and if true executing the CREATE process which tests for the second element using that object as "input" to the process to actually execute the CREATE function.

Vins Nash