Build better products with our product team
Description - Documents added on the Task Level currently show on the Project Level by default; it would be beneficial for organization for the folder that they relate to on the Task Level to show on the Project Level as well. Why is this feature important to you - We require folder structures on projects to organize documents, but don't want the users bouncing from the Task Level where they are completing the work to the Project Level just to put the document in a preset folder. How would you like the feature to work - If a document is in a folder on the Task Level, it pushes both the document and folder to the Project Level and not just the document. Current Behaviour - Documents push to the Project Level without a folder
To be able in a easy way to use different sender e-mail addresses it would be nice if it where possible to pick a address from a pre defined list of legible addresses. If you want to have a B2C address and a B2B address and maybe you would like to have different addresses used for different tings like: sales emails, support emails, sales campaigns, Newsletters, webinars or transactional emails, you would today need to create a own surface to be able to do that. If all addresses was able to pick from a dropdown list when creating a email that has been a better work flow.
Request for Feature Enhancement (RFE) Summary: Can we give contribution access in Content hub to our external users without giving them access to our AEM instance. Use-case: We have around 500 external users having their own domain email addresses, we can not give access to users with external domains to our AEM instance. We would want the external users in Content Hub to be able to upload assets without giving them access to AEM just like Brand Portal. Current/Experienced Behavior: To upload assets, external content hub users must have AEM access. Improved/Expected Behavior: External users could upload assets without having access to AEM. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: SBR Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Folder Structure/Hierarchy in Content Hub Use-case: We are doing a POC on content hub to replace Brand portal. While going through the documentation we have observed that Content Hub provides only flattened structure. We want to use content hub for different vendors, so each vendor will have its own space or folder where the assets for those vendors will be placed. This request is to enable folder structure in Content Hub Current/Experienced Behavior: No folder structure, all assets at one place Improved/Expected Behavior: Folder structure enabled for assets, Assets appear in folders as they do in DAM Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: SBR Screenshot (if applicable): Code package (if applicable):
Description - Create the functionality to have a custom form field be searchable on an Issue Report without having a column for that field. Why is this feature important to you - It's common where we need to search for information related to a request that was put on a custom request form, but we do not have that column in a report. One example would be is we get a request for adding a pixel on a form, we ask for the URL on the request form, but on the request report, we do not have a column for URL since it would make the report very lengthy. How would you like the feature to work - Type the word or field name into the search bar on a report, and have related values pull up on linked requests (without having the column for that field on the report). Current Behaviour - Currently, it is only searchable if it is a column on the report. Screenshot shows that you must have the Page URL column on the issue report in order to search for URLs. This new feature of allowing an object field search function without having that column on a report would allow you to search for Page URLs associated with the issue when it is not a column on a report.
Description - It appears that with last week's UI update to the Forms Composer, some of the logic changed to where you cannot apply the same audience to more than one location in the Forms Composer.Why is this feature important to you - We often use audience refinements for audiences such as isolating to lower environments. So, if I have 2 locations in one experience, I want to be able to apply the same, saved 'lower environment audience' to both locations.How would you like the feature to work - Like it did in the old UI. Allow for a saved Library audience or an activity-only audience to be applied across multiple locations in an activity.Current Behaviour - Similar to when you try to apply the same audience to multiple experiences, it errors out and says duplicate audiences are not allowed.So, you have to recreate the audience from scratch and give it a different name. That is very inefficient.
Description -Why is this feature important to you - Because occasionally we want to publish promotional (or other content) updates that are unrelated to an experiment but need to be published at a future time in a live experiment.How would you like the feature to work - Same as regular scheduling except allowing for the current Activity to be live Current Behaviour - Presently if you schedule an update to a Live experiment it gets deactivated. This feature would allow for that to not happen.
I noticed the WF view of calendars has been updated. It does make it look very clunky by having to click on an item and have it appear in a side bar vs being able to hover over it. In addition, when placed on a dashboard it takes up way too much space when a monitor is vertical.
Description - Milestone View reports are out-of-the-box view from Workfront and we're unable to customize the sorting/ showing of dates Why is this feature important to you - to be able so show different dates to stakeholders How would you like the feature to work - add in project completion dates (planned & actual) + start (actuals) as options to show in the milestone pathCurrent Behaviour - allows you to only see planned start dates and projected start dates as options to show/ sort the milestones
Request for Feature Enhancement (RFE) Summary: Appling resources built in front-end pipeline on preview or page-diff of versioning. Use-case: Build resources (css, JavaScript, etc) with front-end pipeline. Create a version for some page, and show a preview or page diff with the current page. Current/Experienced Behavior: Currenlty the resources (css, JavaScript, etc.) build in front-end pipeline are not applied on preview or page-diff of versioning. The "link" element for the resources does not exist on the preview of the "versioned" page. Improved/Expected Behavior: The resources (css, JavaScript, etc.) build in front-end pipeline are applied on page diff or preview of versioning. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service ( AEMaaCS ) Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Due to a Salesforce input error, we need to find emails from outside the United States ending with a local email domain in our database. Can we add a filter into the Email Address for "ends with" ? such as .co.uk .fr . de . see .it etc to identify Country. As often, only two letters using the "contains" filter brings in too many additional addresses where the letters are part of a name or company. This will also help with reporting, personalisation and target audiences. Thanks, Zoe
The conditional content feature is a strong and must wanted feature in the email designer. But it has some limitations when it comes to usability. We would like to be able to see the actual conditional code somewhere - like a button when you have the open the inline menu with the conditional content choice. The only way to see and access that code "wrapped" around a email module is to close the template, go back, open it - and in the preview before editing you can actual see the code. This code should have been possible to se, even edit in an advanced mode like with expressions, in a own window when working with the content inside an open template. This is especially important if you want to place your logic inside the HTML code, inside the email module you self, and not on the whole block. The you might need to code this your self.
Currently, WF administrators have no way of establishing an organization level structure for reports. Only individual users can specify their own organizational structure for reports. There are TOO many reports for individual users to know what is or isn't important unless specifically told to favorite specific reports. It would save a lot of everyone's time if administrators had the ability to organize reports into shareable folders to groups of users or an entire instance. True you can circumvent the need by putting specific reports on dashboards, but that's not the issue at hand. This targets making reporting for accessible.
Description:We need a feature to filter out automatic email open events that are not caused by recipients or users. This would enable more accurate reporting and evaluation of email campaign performance.Why is this feature important to you:Filtering out non-human interactions is essential for providing accurate open rate metrics, ensuring campaign performance insights reflect genuine user engagement. Additionally, identifying and including non-human interactions (e.g., automatic opens by Apple Mail Privacy Protection - MPP) would help evaluate email address activity and inactivity more effectively.How would you like the feature to work:The feature should detect and exclude automatic opens caused by non-human actions, such as MPP or similar mechanisms, from standard open rate calculations. Simultaneously, it should log and make these automatic opens identifiable for separate reporting purposes, allowing for better analysis of email address activity patterns.Current Behaviour:Currently, all email opens, including those triggered automatically by non-human actions like MPP, are counted equally. This inflates open rates and makes it challenging to distinguish genuine user engagement from system-generated interactions.
DescriptionThe guided analysis feature in Workspace allows users to configure several different types, including active growth, conversion trends, and frequency. The tooltip for each of the options gives some information about what the guided analysis does, and includes a link to the Adobe documentation for that type (see screenshot). Once a guided analysis has been created,the tooltip for the saved item contains no information about what the type was. If the naming convention of the saved guided analysis doesn't reference the type, people will be less likely to know what the guided analysis will show once used. The recommendation is to update the tooltip for saved guided analyses to include the type and a link to the Adobe documentation. A separate request for guided analysis updates can be found at https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-ideas/cja-add-description-field-to-guided-analysis/idi-p/748973. Why is this feature important to youProviding type information in the tooltip will make it easier to people to see what the guided analysis is about. How would you like the feature to workAllow a type field in saved guided analyses tooltips. At the very least it should include the type name (e.g. Active growth, Frequency), and ideally would include a hyperlink to the documentation for that type on the Adobe side. Current BehaviourThere is no type information field available in the tooltip for saved guided analyses.
Description - When a dashboard is added to an object (left nav) make it so I can choose whether it's global (all objects of the same type) or local (only this object). If I add it to a template only projects created from the template show the dashboard. Why is this feature important to you - Similar to the issue with global filter/view/grouping settings a dashboard may be for a very specific case - or for a certain type of project. E.g. I'd like to add a special dashboard to my configuration project; another one to all request queue projects; every project created with the "creative execution template" need the exec dashboard etc. How would you like the feature to work - When a dashboard is added to an object (left nav) make it so I can choose whether it's global (all objects of the same type) or local (only this object). If I add it to a template only projects created from the template show the dashboard. Current Behaviour - If you add dashboard X (eg project summary) to a project, it displays on ALL project regardless whether it applies or not. In the above example all projects would show - configuration dashboard - queue dashboard - exec dashboard
Description - Store the selection of Filter/View and Grouping with the current objectID Add the ability to combine Filter, View and/or Grouping into a "Scene" Why is this feature important to you - Often different personas use different combination of view/filter/grouping. The chosen view/filter/grouping depending on what a "project" or "task" or "issue" represents. Example: Take "issues" on a project. In a creative execution project the issues might be change requests. So i need to see description, status, enteredBy, and group it by parent task. I might filter to open-only In a planning project issues might be items on a ROAM board. Here I what to see a mix of basic and custom fields grouped by status Example: Take "tasks" on a project. A project is a configuration project where a task represents a configuration entry. I have a specific set of custom fields to display On project A I am a contributor so I want to see MY open tasks, grouped by week (plannedStartDate) On project B I am the project owner so i need to see the standard task view How would you like the feature to work - Scenes can be created/named (save current scene) and edited (each of View/Filter/Grouping is a dropdown of available options). Selecting a Scene sets the Filter/View and Grouping. Allow setting a scene as default. Store the selected view/filter/grouping (not the scenes) with the specific object ID (project ID, programID) instead of being global to the object type (all projects etc) This allows me to have a set view for the examples above my config project scene my todos scene my PM scene my change-requests scene my ROAM scene Current Behaviour - The Filter/View/Grouping combination is stored for the objectType, meaning the filter/view/grouping I selected on project A follows me when I visit project B For power users this is a nuisance An every user has run into this issue: A brief moment of panic when we don't see the expected items, only to find that a filter (used on the project I was on previously) needed to be unset. The current behavior (storing UI choices based on object type) adds no value at best, and can at times be a hindrance.
Description - Increase the maximum number of custom forms that can be added to an object. Why is this feature important to you - As we've redesigned a request process, we've been severely limited by the maximum of 10 custom forms. Our process collects request at the program level, which will always result in multiple projects - and 10 forms is not enough. We have had to create over-complicated forms as a workaround, which is not user-friendly from a configuration perspective OR from an end user perspective. How would you like the feature to work - The maximum form limit should be increased to a number higher than most will need (for example, 500 field limit on a form - most people don't put that many fields on a form - we'd like to have more options than we would ever need to add forms). Current Behaviour - System does not allow you to add more than 10 forms to any object.
I have clients who would like the ability to edit the exported custom forms before they are downloaded. It would be great if this was something you could templatize, so that no one has to go in each time and make those edits. It would help out our client with guest facing visibility.
Description -Currently in the journey expression editor, batch instance ID is not available in properties. It would be ideal to have batch instance ID and use it for reporting purposes. Why is this feature important to you -Not every customer would rely on Data Distiller query to fetch batch instance id from journey step events dataset. Batch Instance ID is helpful to identify different cohorts in a recurring batch audience triggered journeys. How would you like the feature to work -Provide ${journeyBatchInstanceId} property in the journey expression editor. Current Behaviour -${journeyBatchInstanceId} is not available.
When creating emails in the email designer it is possible to lock parts of the email for editing. It is imported for me as i user to be able to lock content for other, if I act as a administrator for the templates, but they should be able for others with my role to edit and publish. Todays feature with content locking is a little to narrow when it comes to use cases. It should be possible to lock on you user for personal editing, but there should be a "admin" user group the can overrun this, and it should be possible for a admin user group to lock content so ordinary users cant change critical content. More role, and user group possibilities to admin the lock feature is needed.
Description Currently, the profile attributes are not allowed to configure URL tracking parameters at channel level. This would help to add tracking parameters from profile level attributes. Why is this feature important to you?This would allow you to track and collect additional parameters at the tracking logs. How would you like the feature to work?Allow profile attributes to configure URL tracking parameters at channel level. Current Behaviour - Currently, the profile attributes are not allowed to configure URL tracking parameters at channel level.
We have started to use variables in Fragments in a advanced way to control links on head logo, language differences, design possibilities like background color, choice between CTA txt link or a button etc. This variables can be set in each Fragment when dragging them into the email. To optimize we she that is would be nice if this can be done for the whole email from the email "preview" window where you define the subject. If we here could reflect the defined variables that is possible to use, they could be set in this page as a default when you start editing. And you could change the variable setting locally in one fragment if you want to afterwards. You could f ex choose to enable or disable the variables you need in this unique email. The variables with name and value possibilities might be stored in a own page - or you as a admin can add this so it fits the logic that is build into each fragment.
This is a suggestion from the Summit Technical Support Booth, on behalf of Questrade. Batch deliveries should have a final deduplication step similarly to what is done in Campaign to safeguard profiles from receiving more than one email. Questrade is using a non-stitch merge policy which is resulting in multiple emails to the same address, due to multiple profiles with the same email address. Caleb Hill AJO T3 Americas
Description - Currently, our platform only supports single-page forms, limiting our ability to create comprehensive, multi-step feedback or survey wizards.Marketing forms are scattered across various third-party Content Management Systems (CMS), complicating data ingestion into Adobe Experience Platform (AEP). Why is this feature important to you - Streamlines the process of collecting detailed feedback and survey data.Eliminates the need for external CMS platforms for marketing forms, simplifying data ingestion into AEP.Enhances marketing personalization capabilities by providing a centralized data source.Improves user experience by creating a more intuitive and structured form submission process. How would you like the feature to work - Implement a multi-page form wizard feature. This would allow users to create forms that span multiple pages, capturing detailed feedback data step-by-step.Enable seamless data storage within AEP from these multi-page forms, facilitating marketing personalization.Centralize all marketing forms within our platform at the AJO level. Current Behaviour - The existing system only supports single-page forms, preventing the creation of multi-step wizards.There is no data context retained between different form submissions, limiting the ability to build comprehensive user profiles.
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.
