stewarts16448458 , thanks for pointing it out - I tried a few possibilities today.  Seems to always set the event, no matter what the returned value is.I've tried using data elements that return 0, a blank string, and false, but they all unfortunately still result in the event getting set.

I agree with this, seeing it a little late.  It would also be possible to accomplish this and allow data element logic at the same time.Link to the other thread, could be grouped in with this depending on how they decide to implement it: Set Variables Actions - Events should have set/no-set logic

Whoa, I didn't know this was an option in DTM.  This is such a streamlined way to interact with data layers without having to utilize a new data element or making sure you are being really defensive in your coding.Thanks for bringing this up Stewart - a great feature/idea that I wish I knew back wit...

Again, this isn't the most flexible optimal solution (meaning it doesn't allow for any combinations of nested AND / OR operators), but could allow most of the functionality within the way Launch operates today.  It'd be better than nothing, with less room for error...Using a new feature: "Add condit...

I agree, this and the ability to have nested conditions would be a huge enhancement for the current system.Allow for nested conditions in Launch rules Condition1 AND Condition2OR Condition3 AND Condition4From a purely functional perspective (if adobe takes the easy way), it may be possible to have a...

If your rule consists of 2 action blocks:Go into the custom code block, copy that code.Then open the Set Variables action block, scroll to the bottom and paste it in the custom code section at the end.Now your custom code will be executed at the end of the Set Variables action, without needing to be...

^this, exactly!From my standpoint of usage, there are only two big roadblocks remaining. These are the last obstacles that stop eVars from completely taking over the world:1. Workspace pathing     a. It still uses a querying shortcut, so it doesn't compute correctly when hit based segments are used ...

You may not be getting any data collected to your variables because of the timing that data elements are evaluated for SetVars.Based on what you said here:Adobe launch handles Data Elements in a very specific manner when they are referenced in the GUI (like a setVars action block or within the analy...

Hi Anitha,The delay that you're experiencing is not due to the "Rule Order" (rule order is only effects a process within a single trigger - you are using two different triggers: DOM Ready, and Direct Call('value') ). Instead, the strange delay is actually due to the cascading effect of using a Custo...

Thanks for the update.  This is going to make a lot of people happy!