Set Variables Actions - Events should have set/no-set logic

[#1]

Events need the same type of set/no-set logic based on the value that is available to sprops and evars within the "Set Variables" action block.

With variables, as it works today, if eVar2 is set to a data element that returns an empty string - it will not set the variable or send the info within the record call (default functionality, that is also optional - great stuff! ).

With events, it doesn't seem like we have this choice.  We should be able to set the value of an event to a data element that can return something like 'False' or an 'empty string' , controlling whether or not the event really gets set with the record.

[#2]

I'm hoping out of the box logic for populating events based on the value of eVar variable. Let's say I'm tracking form submissions and using eVar5 for form name. Based on form name I want to populate event1 if form name was "offer request" and maybe populate only event2 if form name is "contact form". Now I have to use custom code to achieve this, but would be cool to easily choose these kind of settings directly in the UI of rule/launch. This way I can have only one rule for different kind of form submissions. Bit stupid example, but you get the idea.

In this idea you are only talking about "false" and "empty string", but I guess my idea would be pretty much the same thing or did you meant something else?

[#3]

Both our ideas are the same thing, just in a slightly different way.  For your example, I would set event2 equal to a new data-element, then I can use that data element to evaluate eVar5 and return a value (even if that value returned is an empty string, which would sobsequently NOT set the event on the record).

This event2 = %DataElement% approach allows you to do a true/false type thing (which your use case describes), as well as set the event to a value if needed.  It even handles the simple use case where you want the event on any record where eVar5 is present ( event2 = D=v5 ).