Skip to main content

Filter by idea status

10000+ Ideas

jeff_bloomer
jeff_bloomerNew Participant

Analytics Workspace: Friendlier Title Entry for VisualizationsNew

Description - I have simply reached critical mass on this one, and I really can't believe no one else has cried uncle yet.  So, I will do it.  Here is an #AdobePainPoint.Entering a Visualization Title when the component is small: I mean seriously ADOBE!!  Why should I have to resize the entire visualization just to enter a title??  Would it not be easier for you make it easier for the dialogue to resize for us so it is readable while we enter text? Why is this feature important to you - As opposed to typing my titles elsewhere, then copying and pasting them in, OR, resizing my visualization just to view the title so I can type in my title.  The first requires forethought to either set up titles in a different document.  The second often causes the Workspace to recalculate when I change the size and shape of visualizations and move things around. How would you like the feature to work - When I place my cursor in the Title Bar of a visualization, if text already exists, then visibility of the text will extend far enough so I can see the entire value, plus a little more.  If no value exists, it should still provide space for at least 10 to 15 characters of visibility by default. Current Behaviour - Current behavior is as pictured above and below.  When the cursor is placed in the Title Bar of a smaller visualization, only a single character is displayed, followed by elipses obscuring the rest of the title, along with a mouseover display of the value currently in the title:  

Use segment tags as dimension/grouping in Workspace tableNew

DescriptionThe ability to use tags assigned to segments to bring all related segments in a workspace visualizationWhy is this feature important to youWe frequently have to create segments that are just OR groups of other segments, especially for cross-market (eg EMEA region or APAC region) or cross-product (eg Category A or Section X) analysis. This is time-consuming and imperfect since we have to update the grouped segments.How would you like the feature to workWe already have the option to add tags to segments. Ideally, these tags should translate to an OR segment grouping in Workspace so we can quickly pick all relevant segments for a report. For example, I could tag all relevant regional segments as EMEA and then be able to report on individual regions as well as the cumulative view by simply dragging the "EMEA" tag in the report. I could also group segments that are used frequently as panel filters by tag, for example by tagging all segments for excluding internal visitors or potential bots under one tag. This also means that if I create a new segment and tag it accordingly, the report will automatically update. Ideally, I should also be able to choose if I want to use a tag or if I want to display the segment breakdown.Current BehaviourNo current behavior is enabling this. The workaround is manual and involves creating "grouped" segments and/or reusing the same set of segments in similar reports.

User Activity Dashboard for Real-Time "Active User" Monitoring in AEMNew

Request for Feature Enhancement (RFE) Summary: We propose a User Activity Dashboard within Adobe Experience Manager (AEM) to track recent user interactions, enabling administrators to view active users and their activity within the AEM Author environment. This feature would display user interactions over defined time intervals (e.g., 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, and 1 day), providing insights into both current and historical usage trends. Use-case: Outage Communication: During system outages or maintenance windows, administrators can quickly identify and proactively inform active users of the disruption. This can reduce the number of support tickets, emails, or inquiries related to unexpected access issues. Performance Monitoring: By understanding the volume of requests by user or group, teams can better anticipate peak usage times and address potential performance issues. This data could help identify when system resources are under strain due to high user activity. Security and Compliance Auditing: Tracking recent activity at a granular level can assist in identifying unusual patterns that might indicate unauthorized access or misuse of the system, supporting security and compliance audits. Usage and Engagement Metrics: This dashboard would offer insights into which users or groups are most engaged, enabling better targeting of communications, training, or enablement efforts. Teams can also gauge the effectiveness of new features or updates by observing changes in interaction patterns. User Behavior Analysis for Content Optimization: By identifying which users frequently access specific content or assets, the dashboard can guide content optimization efforts, ensuring high-value assets are readily accessible and system workflows are aligned with user needs. Current/Experienced Behavior: AEM Cloud Service currently lacks a built-in dashboard to monitor real-time user activity within the AEM Author environment. This limitation means administrators cannot view which users are active, track recent interactions, or analyze access patterns over time (e.g., last 1 minute, 5 minutes, etc.). Any tracking of user activity requires external log analysis tools, such as Splunk, to manually generate insights based on access logs. Improved/Expected Behavior: We propose a native AEM Author dashboard to display user activity in real-time, segmented by user, country, and role, with time-based filters (1m, 5m, 15m, 30m, 1h, 1d). This would enable administrators to quickly see which users are active, manage communication during outages, monitor performance, and detect unusual behavior. Interactive visuals like graphs and heat maps could further enhance usability, helping administrators proactively manage system usage and performance. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable): Dashboard generate by SPLUNK out of access.logs. The AEM Dashbaord should contain something similar.   Code package (if applicable):