I've had a couple occasions where I set up a long, complex load rule to load a tag under multiple circumstances, with many "or" conditions.
I've found that when I check whether a UDO variable "equals" or "contains" a value, ignoring case, and that value is undefined on the page, the load rule fails entirely.
I'd prefer if the load rule continued checking the other "or" conditions.
What I can do:
1. Check "is defined" for the UDO variable in the load rule first (within the same "or" condition). This makes my load rule twice as long.
2. Set up a pre-loader extension that puts placeholder values in all my UDO variables (of empty string, or something like that)
What I would prefer:
I think that Tealium should perform an "is defined" check automatically for load rule tests on "equals" or "contains" where an undefined variable is currently preventing the load rule from performing all listed tests.
If there is an internal Tealium setting where I can enable this sort of check, that would also work great for me.
Thanks for highlighting this issue and the workarounds. We did fix this at one point but it resulted in changes in behavior for existing load rules for a handful of clients. The fix was rolled back. For a few, this bug had become a feature. :-)
We're working on a plan now to introduce the fix in less-disruptive way. Ideally we're able to update the logic so that you're able to "opt in" to the change and not impact legacy implementations (those clients that have load rules without the undefined checks.)
Please stand by for more specifics and feel free to follow-up on this post. Again, thanks for documenting the issue and workarounds very clearly.