Build better products with our product team
I noticed an update to Workfront's interface recently. When you pin projects to the top tool bar, you used to be able to drag and drop to rearrange their order. Now you have to right click and say "move left" or "move right" Could we bring back the drag and drop feature to pinned projects?? Or maybe drag and drop reordering to our "Favorite" projects list? My projects change all the time and the simple task of keeping them alphabetical in my toolbar for easy access is now extremely tedious 😞
Description - Add field to capture entry date of a dashboard similar to the entry date of an issue, project, task, or user. Why is this feature important to you - This is important because we need to know how long a dashboard has been available to be used. This helps tell the story of high quality dashboards that can be duplicated/copied for other users across my instance and peer customers of Adobe Workfront. If a dashboard has been around for years and was recently modified that highlights importance and emphasizes need to secure it and have it monitored for quality control. The dashboards in Adobe Workfront are often used to drive key business decisions and knowing every aspect about a dashboard is critical to data governance and management. Additionally, this will help us when we are auditing dashboards that may potentially need to be deleted if we can assess how long they have been in the system. How would you like the feature to work - Users should be able to add the field as a column (view), filter or grouping in similar manner as an entry date for a project, issue, or task when reporting on dashboards and that information should be available within the dashboard itself so users can easily identify when the dashboard was created. Current Behaviour - The field is not available in Workfront UI or API Explorer.
Description -Allow the percent change columns of comparing two different time period to update dynamically as the panel date range AND comparison date range update. Additionally, allow for the option/toggle of showing the change in basis points when comparing percentages like conversion rate and bounce rate. Why is this feature important to you -This is imperative as we share reports with business leaders and stakeholders to change the date ranges dynamically and maintain the integrity of the data presented in the report. As it is now without dynamically updating the calculation as EITHER date range changes, the report presents false and misleading data when date ranges are changed for deeper analysis. How would you like the feature to work -Ideally the comparison date range would be set at the panel level and allow for only the percent change column to be present in the table (or the comparison period also, it would allow either way to work), and update based on the dates input in the panel date range function, and continue to update as the date ranges are changed during analysis.It would also be efficient to not have to generate this for each separate metric in the table.Also would be nice when comparing percentages to allow for a toggle of comparing by basis point change rather than percent change. Current Behavior -Currently the percent change period do not update after the initial calculation when the comparison date range is set. If the comparison date range is updated the percent change columns do not update and can present misleading and false data, especially for stakeholders and business leaders who are less familiar with the tool. Currently I have to set the comparison date range 6 times if I have 6 different metrics in my report. This is tedious and inefficient.I also do not have a way within the Analytics UI to calculate a basis point change rather than a percentage change.
Description - We'd like to be able to upload a csv file that has events and their labels/names, so Adobe can assign those labels/names to the right fields without us having to manually update each event label/name. We have thousands of events. Why is this feature important to you - Reduce tedious manual workHow would you like the feature to work - Automate naming of eventsCurrent Behavior - Manually naming each event
Description - The request is for Adobe to create the folder structure based on the year/month/day of the writing of the data. Can the Prefix use special characters that would add the year/month/day information to the Prefix automatically? This is a standard thing with other products. It helps with partitioning of the data. Why is this feature important to you - I understand Adobe does not have this capability. But I would suggest that as a future enhancement Adobe thinks about enabling the creation of subfolders. Most products I work with today have this capability because it is a standard practice to partition data that is written daily into bins for the day. With this limitation in the Adobe Data Feed product, it requires extra processing on our side to move the files into appropriate locations post Adobe’s writing of the data. How would you like the feature to work - Current Behaviour - Feature not available.
Situation: Like with other components, it is possible to set a project to "Approved" status. Other components such as Segments or Custom Metrics, indicate this by showing a little checkmark icon next to the name. Projects are lacking this feature, rendering it less useful. (I'm aware you are able to filter by status though.)Request: Add a checkmark icon (or an additional column) in the Projects overview.
DescriptionThe new embedded Guided Analysis feature in Workspace allows users to save configured analysis for future use. The screenshot below shows what a Saved analysis looks like in the left rail. Unfortunately, once the analysis is created, it cannot be deleted or modified from within the Workspace UI. The only options available are tag, favorite, and approve. If a user wants to make any changes to the analysis, they have to go to the Workspace manager, select "Folders & Projects" as the view, and then enable the "Guided analysis" Type in the filter. This seems to be the only way to rename or delete an analysis. Note that the search function does not look for saved Guided analysis. Most users aren't going to look in Folders & Projects in the Workspace manager, so they won't know how to make adjustments to anything saved. It would be easier for users if Adobe allowed them to delete, modify, and share saved analysis from within the Workspace UI. Why is this feature important to youAny point of friction, such as requiring users to go to a different page (e.g. Folders & Projects) to do something will hurt adoption because it causes confusion. Friction also increases the odds that users will submit tickets that admins have to deal with. How would you like the feature to workMake the saved analysis options the same as the options for components within the Workspace UI. The screenshot below is what appears when a dimension is right-clicked on. Ideally, an "Edit" option will be included in the list (this isn't included for components, for some reason). If this isn't possible, update the tool tip to include the edit option, as we have with calculated metrics and filters. Current BehaviorUsers can only make adjustments to saved Guided analysis via the Workspace manager, which requires them to go to an infrequently used section of a different page.
Description - Where a subclassification is already created as part of copying a report suite, it is currently not possible to identify which report suite the subclassification is attached to. Tags on subclassifications do not appear in the left rail of the classification sets UI, and filtering by report suite does not return subclassifications.Why is this feature important to you - Where there are multiple report suites that have similar classification requirements, it is difficult to identify which one has been most recently updated with the latest classification file.How would you like the feature to work - I would like to be able to use the report suite filters or tag filters available in the classification sets UI to filter subclassificationsCurrent Behaviour - subclassifications cannot be easily identified or filtered by report suite or Tags
Description -It is so easy when expanding a panel to accidentally click on the x and delate it!How would you like the feature to work -Please add a warning popup when the x is hit.Current Behaviour -It deletes the entire panel and you have to press Ctrl-Z to undo.
Description -Currently, when using "flows" in Adobe Analytics or CJA, you are limited to using only individual dimensional items one at a time. It would be super helpful to be able to use a hit-based segment so that you can see flows into a "group" of items (ex: a group of URLs). Why is this feature important to you - Scalability, it will allow the user to see more macro flow visuals. How would you like the feature to work -Allow hit-based segments to be dropped into "flow" displays. Current Behavior -You can only include individual dimensional items.
Description -One of the biggest pain points in Analysis Worskpace for my users is that they don't understand which dimensions and metrics should (and should not) be used together in freeform tables or other visualizations. Having a means to connect related dimensions and metrics so that when a user selects one component, the other related components become immediately visible in the left rail would make this easier for less advanced users. Why is this feature important to you -It would greatly help less experienced users become more familiar with how dimensions and metrics relate to each other and empower them to confidently select the right components for their needs with fewer mistakes and less need for support. It will also cut down on the amount of incorrect data shared company-wide due to misinterperetation of the data or use of the wrong components for their reporting needs. How would you like the feature to work -A UI tab where admins can create curated component collections, selecting the different dimensions and metrics that make sense to use together in reports. When a user pulls one of the components into a report, the left rail would be automatically filtered to show the related components at the top (like a "recommended" or "related content" feature on a website). Current Behaviour -Tags are the closest way to do this, but it's difficult to get users to remember to use them for filtering, and we have so many different tags, it's difficult to know which ones to use for which purpose.
DescriptionOne of the CJA guardrails limits the number of derived fields that can be added to a Freeform Table to five. When a user tries to add more than this, they will see a popup like the one shown below: While the limit itself isn't an issue, it's highly likely that an everyday user will have no idea what a derived field is and how to avoid using an additional one. There are really only three ways to tell whether a component is based on a derived field: The user can look at the component tool tip, which will include a "Field settings" tab if the component is a derived fieldAdmins can indicate that a component is based on a derived field in the component nameAdmins can indicate that a component is based on a derived field in the component descriptionUsers aren't super likely to look at #1 or #3, and organizations probably don't want to clutter up component names. This means that they may see the notification and immediately contact an admin for help. One option to making it easier for users to understand which components are based on derived fields is to include a small icon next to the component name. We already have this for calculated metrics and Adobe standard components. Why is this feature important to youAllows users to quickly see that a metric or dimension is based on a derived field. How would you like the feature to workAdd an icon to the component in the left rail of Workspace if a component is based on a derived field. Current BehaviourThere is no graphical indicator that a component is based on a derived field.
Description of the Business Challenge:Currently, if you are using a virtual reporting suite to provide a controlled clean environment for your analysts, you need to first go to the admin console to assign dimensions, metrics, and segments to the reporting suite. It would be easier to have the ability (as an admin) to assign components to a reporting suite while directly working inside Workspace. Why is this feature important to you - Having this feature will accelerate organizing virtual reporting suites and will also allow assignment of components on the fly. I cannot count the times I have thought "this should be in the VRS" but then didn't have the time and forgot to make the change. How would you like the feature to work - When in the components list view or inside a component configuration, allow a dropdown to be present so you can select what reporting suits the component is applicable to. Current Behavior - You need to back out into the Admin Console to assign components to a virtual reporting suite.
Description -1. AWS Web Analytics product team uploads AWS blog meta data via classification importer feature in Adobe Analytics (AA). Also we use Classification rule builder feature to automatically classify AWS product pages meta data in AA reporting. Unfortunately these classification data can't be sent to downstream AWS s3 location via Adobe Analytics data feed feature. We have a downstream bigger data lake system where we send hourly data feed from Adobe Analytics. Every time my team works on the classification addition or modification needs to be manually worked by AWS downstream data engineering team to add the same details in their database to bring parity to AA and other system reporting. This is time consuming and repetitive task. 2. There are limited eVars (250) available for Adobe Analytics. Classification is a great feature to separate out concatenated data being passed to an eVar and store individual values in different coulmns associated with that eVar. This feature saves number of eVars to be used for this kind of implementation. Unfortunately AWS Web Analytics team can't utilize this feature because we send hourly data feed to downstream data lake where classification data can't be sent. How would you like the feature to work - Classification columns (eVars columns) needs to be included in data feed eVar list. Why is this feature important to you - This feature is important because this will save significant time for AWS data engineering team and also reporting will be in sync automatically.
Adobe - please allow for public Workspace projects to be embedded in third party platforms/websites.Currently, your page includes a Content Security Policy (CSP) directive which prevents the pages from being framed by non-Adobe domains. I can think of a great number of use cases for such functionality, including AA reporting in Tableau dashboard without having to design an entire ETL process for moving the data from AA into Tableau.
Description - Multiple Breakdowns Applying as Time Expands.Why is this feature important to you - It alleviates lots of manual work.How would you like the feature to work - To automatically apply breakdowns with certain dimensions to others as time increases.Current Behaviour - You have to manually add 1 or more breakdown dimensions to each month dimension value that gets added as time goes on.
Description -I set my panel dates and checked the advanced setting "make date range components relative to panel calendar".On my table, i right clicked on my custom metric, did "compare time periods" and "custom date range to this date range". The new custom date range + percent change metrics are correct at first. But when i change the dates on my panel, while i see custom date range metric updating accurately, percent change column always goes to 0%. So the custom date range metric will update dynamically but the % change metric will not. Why is this feature important to you - This to me seems like a defect and can be confusing for other Adobe users who expect that to change. i had to remove % change column from my dashboard altogether to avoid confusion because changing dates in the dashboard is a common use case for this dashboard.
Description - The current limit of 250 eVars and 75 props restricts how many custom dimensions can be tracked and analyzed, making it difficult for organizations with complex customer journeys to capture all the necessary data. This limitation hinders the ability to fully customize data collection and tracking for large-scale implementations. I propose removing these caps on custom dimensions and enabling unlimited eVars and props, similar to what is currently offered in Customer Journey Analytics. CJA provides unlimited custom dimensions by leveraging the Adobe Experience Platform’s Experience Data Model (XDM), which allows for flexible, scalable, and cross-channel data tracking without any variable limitations. Why is this feature important to you - This feature is crucial for us because the current limits on eVars and props in Adobe Analytics restrict our ability to capture the full complexity of our customer journeys across multiple channels. As a business handling large datasets, the cap forces us to make compromises on what dimensions we can track, which limits our ability to get a complete picture of user behavior. Having unlimited custom dimensions would allow us to map all customer interactions, including offline and third-party data, enabling more precise segmentation, richer insights, and better personalization. As our business grows, the ability to scale our data tracking without hitting limits would be invaluable for maintaining a competitive edge in data-driven decision-making and optimizing customer experiences. How would you like the feature to work - Instead of being capped at 250 eVars and 75 props, there should be the flexibility to create an unlimited number of both. This will allow users to define custom variables on demand, without needing to worry about reaching a ceiling. Current Behaviour - Adobe Analytics allows for 250 eVars (event variables) and 75 props (custom traffic variables). These limits constrain how many custom dimensions can be created and tracked.
We would like to show the clicks data by region in Adobe Activity Map extension but it is not supported.I believe this feature would provide visual layout for users who may not be data person. This would be a user friendly for them. This would benefit many users who have similar needs. For me, I am a data person. I can pull it from workspace.
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:
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.
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):
Hello, at the moment, it is not possible to export Details and Summary tab in one document. It is very inconvenient to have two separate documents that are a part of the same report. Especially when there are multiple reports that need to be exported, this issue is even more inconvenient as clients have to manually combine those exports to send it to their stakeholders. It would be great if this could be implemented. Best regards,Sara
Description - Quick reporting to find out which audiences tie back to specific datasets/schemas Why is this feature important to you - This would be extremely beneficial for reporting purposes, along with any changes to datasets, in order to completely understand which audiences will be affected. How would you like the feature to work - Reporting via Audience Overview tab. Or SQL query that can be adjusted to your liking Current Behaviour - Non existent
It's easy to create some libraries to communicate outside Adobe Campaign with the simplicity of Javascript and the HTTPClientRequest class, but as Kafka is not based on HTTP protocol, it's not possible to consume or produce over topics in Campaign. Apache Kafka needs specific libraries (Java, Python, NodeJS) to be used. It would be great to have a specific API into the Campaign javascript environment.I'm sure that question is not new and the R&D team thought about it, and it's won't be technicaly easy, but this question is comming for several of my customers so I'm suggesting here.ThanksCedric
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
