problem start reiterated rule and macro

[Socra3D]

Bye to all,
work on catia v5 r17/r18 and I would like to create an automatic configuration rescue procedure. I have presented the following problem, which I enlighten you with an example for simplicity: I create a simple parallelepiped; the measurement of the sides is connected to external parameters created by me and appearing on the tree (so that it is easily editable and fitable in formulas). imposed two check on the volume of the solid (on maximum volume and minimum volume). Now I would like the automatic procedure to save me on project table the value of external parameters (side measurements) of configurations passing 2 check. I tried to build the procedure in the following way: entered the check, I created a macro via recorder (I simply used the "add line with current values" function on a project table already created) and then I created a rule that throws that macro if 2 check are soft.
Now the problem is this: the procedure does its duty only when imposed (through the external parameters defined before) a "acceptable" configuration that follows an unacceptable one (i.e. when at least one of the two check from violated becomes verified), while it does not work with consecutive acceptable configurations (i.e. when check is already verified previously).
In other words, the rule that launches the macro is only instigated when one of the parameters that launch it directly (i.e. check) change value, but not when I change the measurements of the parallelepipedo.
How to solve?
Thank you in advance.

 

[peloritano]

can ipostate sample files and macro code?? ?

 

[Socra3D]

Bye!
Thank you for responding!
Unfortunately the model can not post it. . .
In any case I solved, even if with a little luck: the rule behaves differently in two different models: the tree has a similar structure (with regard to the rule), but with unparalleled complexity. in the simplest model the rule works, in the other not.
Alternatively, I could have used, instead of a rule, a reaction that reacts to the variation of a parameter, so be sure that the code that governs the rescue macro is executed every time the change is made (procedure that I personally tested and that appears less dancing than the one that makes use of the rule).