Skip to main content

Filter by idea status

10000+ Ideas

RobKmiNew Participant

Bulk edit warn displayed for shorter items listApproved

Request for Feature Enhancement (RFE) Summary: We noticed recently the new warning message added to AEM bulk edit scenario, where user attempt to “Select all” and edit these sub-pages in separate tabs. The warning message says that “Bulk action not supported, The selected action Edit(e) will only have effect X selected items currently loaded…”. As we understand, the justification for that warning message is to let user know that not all sub pages might have been lazy-loaded, and that’s fine. That also explains why the massage doesn’t need to appear when pages have been selected manually. The point is that the mentioned logic might be confusing when there are only few sub-pages to be selected by “select all”. In that case lazy logic is not the case and user can be sure that “select all” picks all the sub pages we have on the screen. Please consider extending that logic, because our customers feels uncomfortable with new behavior and confusing warning. (More detail you can find in thread for Case #E-000797571) Use-case: Changing this behavior will lead to better user experience. Also if some users often use Select all and Edit options together for smaller lists of sites it won't be that annoying.  Current/Experienced Behavior: Open Sites Go to list of Pages where you have 6 elements Choose Select all elements Click Edit  Warning about Selecting only visible items is displayed    Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEM OnPrem 6.5.15.0 Customer-name/Organization name: Robert Kmieciak/ Wunderman Thompson Technology Screenshot (if applicable): Code package (if applicable):  

FrederikWerner
FrederikWernerNew Participant

Introduce visualization (or extend existing) for time between eventsNew

Description - In digital analytics, analyzing how long it takes users to complete an action, go through a funnel, or place a purchase is essential. Many optimization efforts focus on time-to-completion and many implementations try to make it accessible through frontend code. In Adobe Analytics, we can use the Cohort Table visualization to get a first idea of this. However, the smallest granularity is "day" and the resulting table is not very friendly to exploration: One of my personal favorite visualizations is the Histogram because it really helps during exploration, as it clearly shows in which bucket users fall and where to look next. Also, we can re-purpose the resulting Segments through showing the table:   With this, I want to propose a combined visualization. Ideally, it would allow us to create a Histogram-style diagram from an input similar to the Cohort table. We would be able to select a "start event" and an "end event" (bonus points if we can select the first/last/every instance in a Sequence, Visit, or Visitor) and the granularity (from seconds to months) and bucket config, similar to the Histogram. Under the hood, again similar to the current Histogram, it would create Sequential Segments with "within" and "after" conditions and some clear names. The result can look something like this, showing a mock of seconds-to-completion of a checkout step: