Logical Expressions in Groovy

[vitaliy_kh]

I assume using logical equations in Groovy is a real time execution but I have to be 100% sure this is true. For insdtance, in statement like this:
if ((a == true) and (b == true)) then
{
c = true;
}

my good guess, the IF expression will be evaluated right at a time of the C assignment.

I am asking this question because in RM "Use the Required Expression" stament, used for gating unwanted Trggers is too far from being real time. Another words, the evaluation of the Required Expression in RM is not done at time when Trigger Event happens. This results in ether getting unwanted Trigger or missing wanted one and rule behavior becomes unexpected.

The upcoming changes to the RM (removig "do not trigger while running" option) finally pushing me to start coding in Groovy. I am thinking about creating Virtual Trigger custom driver. Pretty much this should be something like the existing Virtual Switch but must be automatically Reset while hub is rebooting and ideally should/must have a real time customizable gating logic. The Virtual Trigger will be set by customizable existing hub triggers but will be reset by very last rule action.

As of now I am aready using Virtual Switch as rule trigger. This approach works very well for preventing unwanted triggers (much better than using PB) but because VS resets by the rule itself the Required Expression and Conditional Trigger options cannot be used. I hope, my Virtual Trigger custom driver will solve rule triggering related problems.

[bertabcd1234]

@vitaliy_kh

the IF expression will be evaluated right at a time of the C assignment.

Wouldn't it make more sense to assume it's evaluated right before? It should be pretty fast, fast enough that a and b are unlikely to have changed since the evaluation at the time of your assignment, but it's not impossible. Is there a real-world scenario where these refer to specific values where this matters? (They aren't even used as a value in the assignment here, so I'm having a hard time understanding even after the explanation comparing things to rules.)

[vitaliy_kh]

@bertabcd1234

It should be pretty fast, fast enough that a and b are unlikely to have changed since the evaluation at the time of your assignment, but it's not impossible.

My wording maynot be enough clear.
When PB is used for preventing multiple triggers in the Required Expression and a very first action sets the PB to false to false, the Required Expression according to the rule logs may/will become false with up to a second delay. This behavior makes a PB usage next to useless. I am thinking about creating a Virtual Trigger custom application which will set a Virtual Switch or Boolean Variable based on super fast customizable (like in RM) Required Expression and existing selections of triggers.
This Switch or Variable will be a Trigger for the RM rule but rule itself will reset this Switch or Variable. The mechanics is very similar as using a PB + Required Expression except the evaluation of the Required Expression must be blazing fast (which is not a case with current implementation in RM). My hope the decoupled from the RM dedicated app will do a right job.