Build better products with our product team
Description - I would like requestor to have the option to always receive an email notification when the status of their request is changed when converting their request into a project.Why is this feature important to you - In quick turn-around projects, some of our clients like to see the progression of their requests being converted.How would you like the feature to work - During the process of converting an issue to a project, we set the status of the project to in-progress on creation of the project. When submitted, this currently changes the status of the issue to in-progress, but does not send the email notification to the requestor. In the user profile, we have turned on the email notification "The status changes on my request" and set to instant. (screenshot added)Current Behaviour - The requestor will only receive a status change email notification when the status of the project is manually changed, which updates the resolved issue.
Request for Feature Enhancement (RFE) Summary: Enterprise level applications with the option to be able to upload binaries require anti-malware protection. Also, most enterprise policies require "Anti-malware" to be implemented to be compliant. AEM does not provide any means of Anti-Virus OOTB, but there are solutions which can be used in "on-premise" and AMS (managed Service) scenarios.However, in AEMaaCS (Cloud Service) there is no option, and no way to create a "customization" to be able to implement anti-virus/malware-protection. In the AdaptTo()-2020 several ways to implement "Anti-Malware in AEM" were proposed [0][2]. The solution by Oliver Lietz (Sling Contributor) has the charm, that the malware scanning would be implemented on SLING level using SlingJobs (which would work across the Author Cluster in AEMaaCS), with a "CloudService" which is used to scan the binaries outside of the AEM instances - which seems to be compatible with AEMaaCS and it's Cloud-Services (Cloud-Blob-Store, Asset Microservices etc, ... ) . This solution, if implemented, could likely use a very scaleable "Anti-Malware scanning Backend" within "Containerization", which would be massively scalable, and though HTTP-requests very loosely oupled to AEM. [0] https://adapt.to/2020/en/schedule/scanning-for-malware-in-apache-sling-and-aem.html [1] https://github.com/apache/sling-org-apache-sling-clam [2] https://adapt.to/2020/en/schedule/aem-virus-scan.html Use-case: Cloud-based "OOTB Anti-Maleware Scanning as a Service" in AEM Cloud Service (similar to "Asset Microservice").Each larger customer is required to have "Anti-Malware-protection/scanning" for compliance as well as to be save to deliver "assets" to customers and users. Current/Experienced Behavior: NO solution to scan for Malware is available on AEM Cloud Service (AEMaaCS) - neither OOTB nor custom! Improved/Expected Behavior: AEM Cloud Service should can each binary (and possibly strings) for malware - best as "Service within AEM Cloud Service". Environment Details (AEM version/service pack, any other specifics if applicable): AEM Could Service Customer-name/Organization name: Many Cloud Service customers (really, many!) Screenshot (if applicable): Code package (if applicable):
Why is this feature important to you? Currently, understanding Adobe documentation in Experience League requires reading through lengthy content, which can be time-consuming. A summarization feature would make it easier to grasp key concepts quickly, save time, and enhance learning efficiency.How would you like the feature to work?A “Summarize” button on each documentation page should generate a concise summary of the content, highlighting key points, definitions, and steps. This summary should be clear, structured, and easy to read, helping users quickly absorb the essential information without going through the entire document. Current Behavior:Users need to manually read and navigate through long and detailed Adobe documentation in Experience League to understand concepts. There is no built-in summarization feature, making it difficult to extract key information quickly.
Description - currently, you can only update proofing summaries manually at the contact level in Proofing HQWhy is this feature important to you - Every reviewer in the Workflow needs to be manually adjusted and can easily be missed. Defaulting to a daily summary can be problematic when the user has set their daily summary for 7am, we offer up a proof at 8am on a Friday and the Reviewer or Approver in the proof doesn't see the Daily summary until 7am on Monday.How would you like the feature to work - Ability to default to Hourly or the ability to mass update the setting in Proofing HQCurrent Behaviour - manually adjust the Workflow drop down to Hourly or manually adjust a Contact's default in Proofing HQ.
Description: I would love to have a dashboard where you can both select the date range (as it is currently) and have a second date range picker for a "compare date range". this way, user can easely compare any date ranges they want just by select one of the date ranges. Why is this feature important to you: almost in every dashboard the people would love to have more than just 1 date comparison, sometimes there are 4-6 different comparisons. currently we need to pre-build every different comparison in advance, wich is both a lot of work and makes the dashboard more complex How would you like the feature to work: I would love to have an additional date range picker at the top of the panel. the second date range picker would be for the "compare date range". each "date range" can be relative either to the main date range (default) or to the "compare date range" (as a flag). or there are completely new date ranges just for comparison. however, the workspace would look like this (simple project, sorry for bad painting) at the top there are the 2 date range picker. whenever the user changes either the main date range or the compare date range, the corresponding fields get updated accordingly. means with this dashboard the user could compare whatever he wants - he is not restricted to the given comparisons and he does not need to "build something" (multiple times) Current Behaviour: currently there are different approaches to solve business requirements, but all are not close to good. either we build the different comparisons (like "last week", "last month", "3 month ago", "12 month ago") directly in the dashboard. and you need to educate the users, that if he changes the date range, the comparison will most likely fail (even with relative date ranges). Or we make copies of the exact same dashboard with different comparisons (like have one dashboard for "short term view" and another for "long term trends").
Currently, setting up connections to third party data sources is the most time consuming, difficult, and costly aspect of a CJA implementation. Having a native connector that allows for easy setup of connections to Salesforce and other common third party applications would bring down costs, reduce the time needed, and generally make the transition to CJA more attractive.
Description:Enhance the Adobe Analytics API 2.0 to include the start date and end date fields as part of the API response payload. Currently, these fields are only present in the request body.Why is this feature important to you?Data Context and Completeness:Including the date range directly in the API response provides essential context for the data being retrieved.It ensures that the data is self-contained and complete, eliminating the need to cross-reference with the original request.Simplified Data Processing:Currently, users must extract the date range from the request body and manually add it to the processed data.This enhancement would automate this process, simplifying data processing and reducing the risk of errors.Improved Data Integration:When integrating Adobe Analytics data with other systems, having the date range readily available in the response facilitates seamless data integration.It eliminates the need for external data mapping and lookups.Increased Efficiency:By including the date range in the response, it will reduce the amount of processing needed on the user side, and make the data more readily available.How would you like the feature to work?Date Range Fields in Response Payload:The API response should include two new fields: "Start Date" and "End Date."These fields should contain the start and end dates of the data range used in the request.The date format should be a standard format, like ISO 8601.Consistent Inclusion:The start and end date fields should be included in all API responses that involve a date range filter.Current Behavior:Date Range in Request Only:Currently, the start and end date information is only present in the request body, within the "globalFilters" section.The API response payload does not include this information.Manual Data Processing:Users must manually extract the date range from the request and add it to the processed data, which is inefficient and error-prone.Desired Behavior:Date Range Fields in Response Payload:The API response should include two new fields: "Start Date" and "End Date."These fields should contain the start and end dates of the data range used in the request.In the image, the date range is present at the top right of the image, as "Jul 1, 2024-Jul 31, 2024". This date range should be present in the API response.Consistent Inclusion:The start and end date fields should be included in all API responses that involve a date range filter.
Description:Enhance the Adobe Analytics API 2.0 to include the itemId value from the parent request in subsequent multi-level breakdown responses. This will facilitate seamless data joining across API responses.Why is this feature important to you?Simplified Data Integration:Currently, multi-level breakdowns require external data management to link parent and child response data due to the absence of the parent itemId in child responses.This feature would enable direct and efficient data joining, reducing complexity and potential errors.Improved Data Analysis Efficiency:Many analytical use cases rely on combining data from multiple API responses.The proposed enhancement would streamline this process, enabling faster and more accurate data analysis.Enhanced API Usability:The lack of itemId persistence makes multi-level breakdowns cumbersome.This feature would make the API more intuitive and user-friendly.How would you like the feature to work?itemId Inclusion in Child Responses:When a breakdown request is made, the response should include the itemId from the parent request that triggered the breakdown.This itemId should be included as a field within the response payload, allowing for direct linking of data.Example Scenario:If a first-level request (Resp1) returns a list of page URLs with itemIds, and a second-level request (Resp2) breaks down a specific page URL by marketing channel, Resp2 should include the itemId from the corresponding row in Resp1.Current Behavior:itemId Absence in Child Responses:Currently, the itemId value from the parent request is not included in the child (breakdown) response, even though it is used in the child request's metricFilters.This necessitates external data mapping and lookup tables to link parent and child data.Data Joining Challenges:One has to manually store or track and associate itemIds across multiple API responses, increasing the risk of errors and complicating data integration.As shown in the image, 2nd level response, the marketing channel breakdown does not contain the first level information i.e. evar27, or the itemID that it is related to. -
Description:Enhance the Adobe Analytics API 2.0 response structure to include actual metric names as column headers or labels instead of, or in addition to, numerical indices (0, 1, 2, 3, etc.) when requesting single or multi-level breakdowns. This will improve readability, usability, and automation capabilities.Why is this feature important to you?Readability and Usability: Currently, the numerical column names make it difficult to quickly understand the data without referencing the original request or external documentation. This adds unnecessary complexity and slows down analysis.Automation and Efficiency: Automating data processing and analysis is hindered by the need to map numerical indices to metric names. This requires additional logic and increases development time.Debugging and Maintainability: Debugging becomes more challenging as it's not immediately clear which metric corresponds to which column index. Code relying on these numerical indices is less maintainable and prone to errors when metric selections change.Data Clarity: Providing metric names directly in the response enhances data clarity and makes it easier to interpret the results.How would you like the feature to work?Include Metric Names as Column Headers: The API response should include the actual metric names (e.g., "Visits", "Page Views", "Revenue") as column headers or labels, either directly within the data structure or in a dedicated metadata section.Provide a Mapping (Optional): If maintaining numerical indices is necessary for backward compatibility, include a clear mapping between the numerical indices and the corresponding metric names within the response, possibly in a separate metadata section.Consistency: Ensure consistent naming conventions for metrics across the API.Current Behavior:Request:--{"rsid": "globalprod","metricContainer": {"metrics": [{ "columnId": "0", "id": "metrics/pageviews" },{ "columnId": "1", "id": "metrics/visits" },{ "columnId": "2", "id": "metrics/visitors" },{ "columnId": "3", "id": "cm538_5e65f9850a999d7b5aa3f26d" },{ "columnId": "4", "id": "cm_average_time_on_site_defaultmetric" },{ "columnId": "5", "id": "metrics/bouncerate" }]},"dimension": "variables/marketingchannel"} Current Response:--{"columns": {"columnIds": ["0", "1", "2", "3", "4", "5"]},"rows": [{"value": "Direct","data": [105.0, 92.0, 53.0, 0.0, 84, 0.70]},{"value": "Organic Search","data": [28, 21, 19, 0., 7, 0.2]},// ... other rows ...],"summaryData": {"filteredTotals": [15, 13, 85, 0, 82, 0]}}Key Issue: Notice that the columns.columnIds array contains numerical indices ("0", "1", "2", etc.). The rows.data array uses these indices to represent the metric values. You have to manually map the numerical index back to the metric ID from your original request.Desired Behavior:The columns section should include the actual metric names, not just the numerical indices. The rows.data array should ideally use metric names as keys, or the columns section should provide a mapping.Option 1: Metric Names as Keys in rows.data{"columns": {"columnIds": ["metrics/pageviews", "metrics/visits", "metrics/visitors", "cm538_5e65f98sdfghgfdsdf", "cm_average_time_on_site_defaultmetric", "metrics/bouncerate"]},"rows": [{"value": "Direct","data": {"metrics/pageviews": 10,"metrics/visits": 92,"metrics/visitors": 53,"cm538_5e65f9850a999d7b5aa3f26d": 0,"cm_average_time_on_site_defaultmetric": 84,"metrics/bouncerate": 0.7}},{"value": "Organic Search","data": {"metrics/pageviews": 28,"metrics/visits": 21,"metrics/visitors": 19,"cm538_5e65f9850a999d7b5aa3f26d": 0.04,"cm_average_time_on_site_defaultmetric": 77,"metrics/bouncerate": 0.26}},// ... other rows ...],"summaryData": {"filteredTotals": {"metrics/pageviews": 156,"metrics/visits": 130,"metrics/visitors": 857,"cm538_5e65f9850a999d7b5aa3f26d": 0.02,"cm_average_time_on_site_defaultmetric": 82,"metrics/bouncerate": 0.6}}}Option 2: Metric Names in columns with a Mapping{"columns": {"columnIds": ["0", "1", "2", "3", "4", "5"],"metricMapping": {"0": "metrics/pageviews","1": "metrics/visits","2": "metrics/visitors","3": "cm538_5e65f9850a999d7b5aa3f26d","4": "cm_average_time_on_site_defaultmetric","5": "metrics/bouncerate"}},"rows": [{"value": "Direct","data": [10, 92, 53, 0.0, 84, 0.7]},// ... other rows ...],"summaryData": {"filteredTotals": [156, 130, 857, 0.02, 82, 0.6]}}Option 1 is cleaner and more direct, while Option 2 maintains backward compatibility by keeping the numerical indices but adding a mapping.Key Point: The essence of the request is to eliminate the need for developers to manually map numerical column indices to metric IDs, improving the API's usability.
A tool that can go into reports, calculated metrics and segments/filters that can programmatically find and replace old or deprecated assets with new ones. Why is this feature important to you - This would make asset management much easier for admins to update assets as new ways of reporting and data collection comes out. How would you like the feature to work - A page in the tools dropdown where an admin can look for a dimension or metric, locate and replace some or all instances of it with another dimension or metric. Very similar to how a find and replace works in Microsoft office. Current Behavior - No tool exists, a user would need to replace these manually after finding all instances of it.
Building in the 'Task - % complete' to the bulk update feature would save us lots of time in having to manually update % complete individually
Description - How would you like the feature to work - attempted testing to change the user ID in the Fusion scenario, but it can't be updated. The Fusion Admin name appears because it is part of the API table.The ownerID represents the Primary Contact, which is separate from the enteredByID field, and therefore, it can't be used to override it.Current Behaviour - Workfront API does not currently support passing "Entered By" information for these types of calls. The API does not have the capability to act on behalf of another user when making requests, meaning that any changes, updates, or requests made via API will always be attributed to the user through which the connection is established (in this case, the Fusion Admin).
Description -Why is this feature important to you - This feature is causing a huge issue where our licensees are able to update feedback given by the brand assurance team and able to manipulate the feedback by editing issue comment details. How would you like the feature to work - Give admins to customize issue field level customization privilege so we can update access what licensee can edit and what they cannot We want licensee to update status of an issue as well as let them upload documents but we dont want them to update the feedback. Current Behaviour - Currently its all or none access. Meaning we allow edit access for an issue they can edit all the fields within issue there is no middle ground where we can hybird edit/read only field access. This could cause a legal issue.
We have more and more customer using the Fluter Development Platform for their Mobile Apps. The lack of OOTB supported integration is a blocker to adoption of Target on Mobile and even a deterrer for using Target company wide (as most companies would want to use the same optimisation solution across all their channels - web, mobile, emails, etc. We either need a well documented way of customising the existing SDK to allow for the integration between Target and Flutter or a supported way of integrating the two.
We require the ability to filter custom object data more effectively. Currently, our filtering options are limited to link and dedupe fields, which do not adequately meet our needs.See details in ticket E-001529804
Request for Feature Enhancement (RFE) Summary: Enhance aem-upload library to accept sourceUrls instead of current local filePath and blob only. Use-case: After Adobe deprecated the legacy Asset Upload APIs the alternate solution suggested was Open-sourced upload library aem-upload. Unfortunately alternate solution is NOT fully ready. The library allows only local filePath and blob to be uploaded. Does allow external sourceUrls. This was possible with previous AssetManager API which is now deprecated. Current/Experienced Behavior: aem-upload does not allow sourceUrl as input Improved/Expected Behavior: aem-upload must allow external https sourceUrl as input and must automatically download and upload into AEM. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: SGWS Screenshot (if applicable): Code package (if applicable):
Description - When creating an audience within audience builder, we sometimes will use other audiences as a baseline. When we go to look at the available options to use, it does not group them by the folder structure that we have created, meaning the audience you’re looking to use is harder to find. We want to make the folder structure available for use within the builder search menu Why is this feature important to you - A big part of RTCDP for my team is the ability to reuse audiences. We have created a folder structure to make it easier to find the audiences that we want to use as "building blocks" in our new audiences that we create. If we cannot navigate the folder structure in the Audience Builder (AB) UI, then it becomes almost obsolete. Additionally, since we will have multiple teams operating and creating hundreds of audiences in our platform, it is much too difficult for our users to look for the correct audience "building block" in an unstructured AB. How would you like the feature to work - When a user clicks "build rule" and then clicks "audiences" to use a reusable audience, there will be a list of all the folders that audiences fall under. Current Behaviour - User clicks "build rule" and then clicks "audiences" an unstructured list of every audience available pops up.
Hello dear community,I have a question regarding the Quick Actions on the start page under “my tasks”.Is it possible to remove or uninstall the time tracking as an icon? We do not need this function and therefore our users should not see it.In addition, there are certain legal reasons why this should not be used in our company.I am grateful for any help.I have attached a screenshot so that you understand exactly what I mean thank you very much best jasmin
Description - Would love to see the ability to assign a default view for a project's tasks and issuesWhy is this feature important to you - Managing multiple views and switching between the views takes a lot of time. When collaborating, the users need to be on the same view.How would you like the feature to work - When creating a project new or from a template, the creator can assign a default view. Other users inherit that view or can change to their own. But at least it would be a starting point for collaboration.Current Behaviour - Users have to select views.
Description - Long values, particularly when paired with multiple metric columns, get truncated visually with an ellipses. While this is okay in a live Workspace report where the user can hover over the row to see the full value, when in a rendered PDF the values are completely lost, leaving stakeholders with missing information. It would be of great value to allow long values to wrap (similar to how there is an option to wrap headers). Why is this feature important to you - Data will be easier to see, with less information being lost when presented to Stakeholders. Having the wrapping be optional allows for people to control when and if they want their data to wrap or to truncate. How would you like the feature to work - Add an option to the settings on the dimension to allow the values to wrap, or not to wrap. Current Behaviour - No option to wrap, and PDF generation doesn't allow for hover states to see the full value
Description - One of the great things about Adobe Analytics is the rich set of components that come out-of-the-box, like Bounce Rate, First Time Visits, Mobile Traffic, etc. Today, Customer Journey Analytics doesn't have that but, IMHO, can and should. Why is this feature important to you - So customers don't have a "huh, feels empty around here" experience when starting with CJA and novice users have something to start with. How would you like the feature to work - Based on the Adobe-provided XDM Schema Field Groups used in a Dataset for CJA, creating a Data View should have the option to add Adobe-provided Components, like Calculated Metrics or Segments, that fit the underlying Field Groups. For example, using the Web SDK Field Group should come with a Bounce Rate Metric, Mobile Traffic Segment, etc. Current Behaviour - 👁️👃👁️ 👄
Description / Why is this feature important to you / Current Behaviour - Workfront has the ability to separate labor costs between what was budgeted, what is planned, and what are actual labor costs. While there is an ability to separate expenses between what expenses are planned and what are the actual expense results, Workfront does not have the ability to separate expenses between what was budgeted and what was planned. A project's baseline / approved budget in terms of expenses must be stored outside of Workfront. Planned expenses entered on the Expenses dashboard tab and/or on Tasks get automatically updated on the Business Case. If a project manager adds planned expenses that weren't budgeted, how would we report a variance between budgeted and planned expenses? Answer: Workfront users are not able to report a variance between budgeted and planned expenses. How would you like the feature to work -Similar to how a budget is entered on the business case for labor, allow the expenses entered there to be the baseline budget separate from planned expenses. Planned expenses would be separate and change to reflect what is expected to happen, whereas the budgeted expenses would remain equal to the baseline approved budgeted expenses. Users would then be able to report between budgeted expenses, planned expenses, and actual expenses, similar to how users are able to report between budgeted labor, planned labor, and actual labor.
The email sent when a new request is submitted states the following:"Hi,[Request Submitted Name] just requested your team to work on [Name of Request]. It's all yours." This is a problem because many of our requests are set up so they are sent to a TEAM and not to an individual user. The wording of "It's all yours." implies that the recipient of the email is responsible for working on the request. We want to promote Workfront as easy to use and this adds additional unnecessary confusion. It confusion because it is not an accurate or necessary word choice to use in the email. We'd like to have Workfront run changes like this past a group of experienced users so they can provide input. This may seem like a small mistake to make but would have been caught by the community if shared in advance of launch. Please have those three words removed because they are a unnecessary part of the email communication.
Description -In the Omniture Legacy UI, there is an option to expire a user after a set amount of days (see screenshot). It would be helpful to be able to utilize the same functionality within the Admin Console, specifically Adobe Analytics, to ensure that external users are expired after a certain number of days (ideally 6 months), but ONLY if they haven't had any activity in the last 6 months. Why is this feature important to you -By having to expire every external user after 6 months, we are facing many users being locked out every 6 months, requiring our User Admins to unlock them, as well as not allowing them within the tools in the interim. If we changed the solution to only expire the inactive users, we would prevent time lost and would properly expire only those who required it. How would you like the feature to work - Have an editable expiry date for users within Admin Console who haven't had activity in the tool in x number if days Current Behaviour - no way to expire users except in the Legacy Omniture tool, which only allows a date; doesn't take into account active users.
Currently Marketo - LinkedIn Audience Match integration only uses email address to match audiences in LinkedIn. This causes small match rates and smaller audiences than when manually importing customer lists or using rival tools. LinkedIn Integration should be enabled to use all the possible data points to get higher match rates and better audiences. These include: email, firstname, lastname , jobtitle, employeecompany, country.
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.
