Can I stop a rule from being triggered.

BLOMASKY

While this is not my use case, this is an easy way to explain my problem

Assume you have 2 fields. InvoiceTotal and SalesTax

I have a rule whenever InvoiceTotal is changed to compute the sales tax. However, I want to allow the user to enter the sales tax and compute the InvoiceTotal from that. Obviously because of rounding, I would NOT want the change to the InvoiceTotal to re-run the compute salesTax Rule. So, my question is, how can I have a rule that is triggered when the USER changes the InvoiceTotal, but NOT when the USER changes the salesTax which WILL recompute the InvoiceTotal?

Did I confuse you? (hope not)

Bruce

aware_support

Reread this several times. Maybe it's the effect of the early morning but I still don't understand what is required...

BLOMASKY

naaa, probably me... Let me try again
2 fields, A and B
I have a rule that says IF A WAS CHANGED then B = ROUND(A * 0635,0)

However, I want to allow B to be input, and I have a rule that says IF B WAS CHANGED then A = ROUND(B / .0635,0)

So each rule will updated the other field. If someone enters a value into B, I do not want the 1st rule to trigger.

Does this make any more sense?

Bruce

BenHayat

BLOMASKY wrote
naaa, probably me... Let me try again
2 fields, A and B
I have a rule that says IF A WAS CHANGED then B = ROUND(A * 0635,0)

However, I want to allow B to be input, and I have a rule that says IF B WAS CHANGED then A = ROUND(B / .0635,0)

So each rule will updated the other field. If someone enters a value into B, I do not want the 1st rule to trigger.

Does this make any more sense?

Bruce

I've had similar case, and I ended up not using Object rules but do it as two processes with two buttons and two input form for user to enter data. I showed field A & B as read only on the form, but did the formula a process and not Object rule. Very clean and no catch 22.

These dependency rules can kill your performance. That's why I cleaned up my app from these types of rules.

aware_support

So basically you have circular rules.

One other possible solution is to mark the first rule as dynamic, so that it will be executed on a client when the user changes A. Then if you mark the rule as "Do not execute anywhere else" in the Advanced properties of the rule, it will NOT execute on the server. So in this case the server will never have circular dependencies.

But this approach may or may not work depending on your other requirements.

BobK

Bruce,

How about something like:

IF A WAS CHANGED AND NOT(B WAS CHANGED) then B = ROUND(A * 0635,0)

and conversly

IF B WAS CHANGED AND NOT(A WAS CHANGED) then A = ROUND(B / .0635,0)