I think the goal of what I'm trying to see is ultimately overlaps so
that I can modify them to fire in order correctly. So if there are 1000
overlaps, I'd still want to be able to tell which rules are
overlapping.A low hanging fruit scenario code be that you just include
the order number next to the log with _satellite debug. That way, I
could just use control + F to search if I noticed some overlaps.Ex. Rule
"Utility Functions" fired - Order #20 Rule "Page Load Rule - Global"
fired - Order #21
It would be a a great feature to have something like a "timeline"
showcasing what orders may overlap.Ex. Many page view events all have
the same order. When creating the rule and selecting the event, you can
see what if another rule is set to the same order.DOM Loaded
Event<-----------"order 10" has 3 overlapping rules------"order 20" has
1 rule"------"order 40" has 5 overlapping rules-------DONE->
@Jantzen, That's not what I'm saying.Here's my repro steps:1.
Uninstalled Core2. All old rules weren't working and build wasn't being
built.3. Reinstalled Core4. Ran a new build for the new version of Core
I installed. It failed.5. **I then created all the replacement rules,
adapters, environments, and clicked on build for dev, the Core Extension
still wasn't automatically being added to the first dev build of the new
rules, etc.6. I then manually added the Core Extension into my dev
build. And ...
My Adobe Launch Developer build was hanging for a while and wasn't being
built without an error after I deleted the Core Extension (I like to
stress test). Error message was "core::domready::extension" wasn't
detected.I chose the function manually added the the "Core Extension"
into my Adobe Launch build and that fixed it Just sharing in case that
Hello,I'm working on reporting for a mobile app and I used the OOTB
calculated metric inside of Adobe Analytics in order to reproduce the
value I see in the mobilemarketing.adobe.com site where we have the
Average Session Length.On that site, the value of time looks great and
transformed in units of time.Using the calc metric in Adobe Analytics
reporting (my.omniture.com) though doesn't look like it's even a unit of
time as I've attempted to transform that value into seconds for my