Yes, this is a really big issue for anyone using a Virtual Report Suite to "curate" their components. If I create a new segment, not only do I need to do the standard sharing to make it accessible to my peers, I have to also go into the VRS editor and make sure that segment is on the "include" side....

On another note, this also impacts getQueryParam functionality- I believe s(.Util.)getQueryParam takes advantage of s.pageURL, so unless you're updating s.pageURL currently, you might inflate tracking on query params.

In addition to the need for an "OR" operator (Allow for "OR" conditions in rules ), being able to nest conditions would be very powerful. For instance, I just did this custom code condition for a client:This would allow us to move out of custom code conditions, and possibly reduce redundant rules fo...

Currently, multiple conditions seem to always take an "AND" operator- for anything "OR", I go to custom code. It would be very helpful to be able to use "OR" conditions.For instance, if I needed to have a condition like "if the pagename is 'home' OR the page type is "product details", I would have t...

Add my votes to:crossVisitParticipationtimeParting (note- the DST values need to be updated, we're going in to 2019)getPercentPageViewed (not my favorite, but lots of folks still want it)appendListhitGovernorgetPreviousValue (see my note above as to why I still see this as needed)getValOnce (I'm sur...

Beautiful list!I do disagree on one point, though:  I'd say getPreviousValue is NOT replaced by data element persistence, unless you're VERY careful about timing- if I want to set the previousPageName, my PageName data element is going to return the CURRENT pageName, regardless of how long I told it...

Right now, in both DTM and Launch, if I need to troubleshoot, I can see which Rules have fired with a debugging tool. If I do a search in my console for "prop3", I can look at the code and trace it upwords until I find the rule name (in yellow, below), which helps a lot with troubleshooting.Unfortun...

The diff idea is perhaps covered here: Rule & Data Element Revision Comparison

This is strictly a convenience/aesthetic thing, but it would be great to see the full name (or at least more of the name) of Data Elements (specifically in the Adobe Analytics extension in rules). Right now it's something like this: It would be nice for it to instead be like this:(for the record, I ...

This is similar (not identical, but related) to Enhanced Search & Global Search