Build better products with our product team
Request for Feature Enhancement (RFE) Summary: The CF picker that was in the old CF editor is not available in the new CF editor, so I would like it to be added. Use-case: A modal can be launched to allow category and product selection. Current/Experienced Behavior: The new CF editor does not have a CF picker. Improved/Expected Behavior: The new CF editor has a CF picker. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 2025.7.21772.20250730T182007Z Customer-name/Organization name: IBM Digital Service Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: I would like the new CF editor to be able to specify the full path when specifying the link destination, just like the old CF editor. Use-case: Specify an external site in the link path. Current/Experienced Behavior: Cannot specify anything other than the content path within AEM. Improved/Expected Behavior: Full path specification possible, including external sites. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 2025.7.21772.20250730T182007Z Customer-name/Organization name: IBM Digital Service Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: In Adobe Experience Manager (AEM), when promoting a Launch back to the source page, certain page properties—such as title, description, alias, and tags—are not being promoted as expected. This behavior appears to be a limitation (or bug) in the default roll out configuration and affects both customized and fresh AEM instances (e.g., 6.5.22 with We.Retail content). Use-case: A content author creates a Launch to prepare updates for a press release page. They modify several page properties in the Launch version, including metadata and visibility settings. Upon promoting the Launch, the content updates are applied, but many of the page properties revert or are lost—leading to inconsistencies and manual rework. Current/Experienced Behavior: Current Behavior Launch promotion excludes certain page properties due to default rollout configuration. The configuration at /libs/msm/launches/rolloutconfigs/launch/contentUpdate includes an exclusion rule: cq.wcm.msm.action.excludedprops = jcr:.* This rule prevents properties like jcr:title, jcr:description, cq:tags, and sling:alias from being promoted. Steps to Reproduce Create a new page (e.g., press-release-may.html). Create a Launch for the page using default settings. Modify page properties in the Launch version: Basic Tab: Title, Navigation Title, Description, Tag, Hide from Navigation. Advanced Tab: Alias, Article Date. Add basic content to the page. Promote the Launch using standard promotion steps. Observe the result: Navigation Title is promoted. Title, Description, Tag, and Alias are not promoted. Content updates are correctly applied. Improved/Expected Behavior: Page properties modified in the Launch should be fully promoted to the source page, including: Title Description Tags Alias Any other relevant metadata Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.22 Adobe team a workaround to directly make changes in "libs," and be cautious about doing so and keeping track of the impact during service pack upgrades. After discussing with our internal technical team, /libs path must remain unchanged. Since Adobe proposed a solution that involves modifying the rollout configuration, we will look forward to enhancement fix for this issue. It will likely involve updating the location where the rollout config is applied to use the resolver (which prioritizes /apps over /libs) instead of relying on a hardcoded /libs path. Other references - E-001650598 / E-001772942 Customer-name/Organization name: Shell Screenshot (if applicable): attached for reference Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Provide a way for the "Asset Compute microservice extensibility"/Asset Compute workers to access the default renditions for an Asset so the custom worker can use those as a baseline for further conversions. Either: Pass a default rendition to the worker (instead of, or in addition to, the original). Or: Defer worker invocation until default renditions are generated (opt-in), so the worker can fetch them reliably. Or: Allow non ARM64 containers and installation of custom binaries like imagemagick for the Asset Compute microservice Use-case: We need to generate custom renditions (e.g., square JPEGs with white borders) from assets like .ai (Adobe Illustrator), .psd (Adobe Photoshop), .svg, .eps, etc. These file types are already supported by AEM’s default rendition generation, but not by Asset Compute workers directly (see below for reasons). If workers could use AEM’s default renditions as inputs, they could reliably transform these assets without needing external tools. Current/Experienced Behavior: AEM Assets and the generation of (default) renditions already supports a wide range of file types. However, the "Asset Compute microservice extensibility" is fairly limited in the filetypes it can process. There currently is no way we and Adobe Support found to support mentioned filetypes (ai, psd, ...).There is no way of reliably accessing the generated (default) renditions which then could be used as a baseline for the actual conversion from within the microservice, as they are not generated at the time of invocation microservice Technical details/background: The "recommended" library "JIMP" which is referenced in the demo project is super limited in the filetypes it can support (currently only jpeg, png, bmp, tiff, gif) Using other image conversion libraries wasn't successful either, as they always rely on binaries (like imagemagick) which don't work on the ARM64 containers the microservice runs on As mentioned previously, trying to access the default renditions and using them as a baseline for the conversion doesn't work either, as they are not generated/available at the time of the invocation of the microservice In summary: Asset Compute microservice currently only works for a very limited set of filetypes. Improved/Expected Behavior: Three possible solutions (either would solve the problem): Allow default renditions or custom defined renditions to be passed into workers instead of only the original Asset binary Invoke custom workers only after default renditions exist (opt-in, via processing profile checkbox), so the worker can fetch and transform them. Allow non ARM64 containers and installation of custom binaries like imagemagick for the Asset Compute microservice Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service (2025.8) with Asset Compute microservice running on Adobe AppBuilder/Runtime) Customer-name/Organization name: (private), see support case E-001769596 for customer specific details Screenshot (if applicable): N/A Code package (if applicable): N/A
Request for Feature Enhancement (RFE) Summary: Word doc re upload option not updating sub assets folder Use-case: When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word document. Due to this there is mismatch in the images in word document and sub assets folder.This is a priority issue and we need to resolve on urgent. Could you please check and let us know on this issue.1. Navigate to Assets console, files option2. Upload a document with some images. update metadata.3. Change the images/remove one or two images in the word document.4. Upload word document with Create Version option5. Check the sub assets folder , observe mismatch with source word document . Current/Experienced Behavior: When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word document. Due to this there is mismatch in the images in word document and sub assets folder. 6.5.22, 6.5.20, and 6.5.18, and the behavior is consistent across all of them. Improved/Expected Behavior: When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word document. Due to this there is mismatch in the images in word document and sub assets folder.Sub assets folder need to be updated even with create version option . Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP20 6.5.22, 6.5.20, and 6.5.18, and the behavior is consistent across all of them. Customer-name/Organization name: CISCO Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Use-case: ChatGPT and most AI crawlers do not support JavaScript. The Dynamic Media viewers are all built relying on JavaScript. Given the end user market is going to continue to grow and adopt the usage of AI tools as their primary source of information, Adobe should plan for the future and figure out some way to have some measure of support for AI. If you give ChatGPT this question for this Adobe URL, then it demonstrates the issue: I want you to evaluate one URL: https://s7d9.scene7.com/s7viewers/html5/FlyoutViewer.html?asset=Scene7SharedAssets/ImageSet-Views-Sample Is there an image on this URL? Current/Experienced Behavior: Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: RTE support for <strong> and <em> tags Use-case: We are running an accessibility improvements project right now and our 3rd party a11y consultants reported some issues with they way RTE work.Right now RTE has an option to bolden a part of a text or to make it italic style. For that purpose it is using <b> and <i> standard HTML elements and this is perfectly fine. We have learnt that in some cases instead of these tags it is advisable to use <strong> or <em> tags as they also bring more context for a screen readers so that they can emphasise how to read that section of text.The <strong> tag is read by screen readers as an indication that the text enclosed within it carries strong importance. When a screen reader encounters a <strong> tag, it typically emphasizes the text, often by changing the tone or pitch of the voice, or by adding a pause before and after reading the text. This helps users who rely on assistive technologies understand that the content is significant or has a higher priority in the context of the surrounding text.Using <strong> instead of <b> not only provides visual emphasis but also enhances the semantic meaning of the content, improving accessibility for users with disabilities.We would love to have na option to define which tag is used for particular place in text. It should sometimes be simply <b> and in other cases we would love to have a choice to pick <strong>.There is no such functionality right now in RTE and I would like to ask if there is any active feature request for such functionality and if this could be planned to be developed. Current/Experienced Behavior: We can only place <b> and <i> tags in RTE Improved/Expected Behavior: There should be a way to pick <b> or <strong> tag for selected text. There should be a way to pick <i> or <em> tag for selected text. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.23 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - If you go to settings > interface and then try to edit a filter or a view, there is no responsiveness when you click "save filter." Though this is the tiniest thing, I get no confirmation visually that my changes have actually been applied and I have to close the window/open the filter or view back up to verify or just trust that it was applied. Why is this feature important to you - Would improve UX when editing views and filters. How would you like the feature to work - 1) Ideally when I hit "save filter" the window would close, and I'd get the little pop up confirming my changes have been applied, similar to when you save a custom form edit. 2) But I'd take anything really! A check mark to appear upon hitting save. A pop up confirming my changes have been applied. Anything! Current Behaviour - When you click "save filter" nothing happens- I therefore end up clicking it like 5 times thinking it isn't responding to me 😉
Description -Why is this feature important to you - Some users with a contributor license can more easily navigate by going directly to a specific Portfolio or Program to view relevant projects.How would you like the feature to work - Contributor access levels can navigate to Portfolios and Programs from the main menu.Current Behaviour - Contributor users can be given access to Portfolios and Programs and can navigate to them if the objects are pinned at the top of the page in their layout template. The layout template allows an administrator to add these icons to the main menu but they are not visible when logged in as that user or by the user themselves. This is a gap in access permissions that should be resolved.
We would like to enter additional details for a given assignment. Currently, the available options, assignee, allocation, and role, do not provide enough information. Our employees support products in multiple languages and have different levels of expertise, so we’d like to enter this info and display it in a Power BI dashboard. We would require assignment custom form and a feature to add more columns as shown in my screenshot.
Description - Please add Revenue Type options for issues so we can distinguish between issues that are billable and not billable to our client. Why is this feature important to you - Some issues, such as risks or bugs, need to have hours logged toward them, but those hours may not always be billable to the client. In order to work around the current behavior, we have to convert issues to tasks and make the task not billable, which defeats the purpose of having them be an issue. Or we have to work the issue, but have the user log their hours onto a nonbillable task. This limits our ability to report on issues accurately and creates extra effort when logging time. How would you like the feature to work - Add the option to select Revenue Type on issues, just like it's available for tasks. Current Behaviour - Only tasks can have Revenue Type adjusted individually, making some billable and not billable. Issues are always billable if the project is billable. I
Description - Show Child task updates visible under Parent Task updatesWhy is this feature important to you - This would help in seeing all the updates of child task in one place against the parent TaskHow would you like the feature to work - Like how all the project updates are visible under updates at project level, all child task updates should be visible under Parent task updatesCurrent Behaviour - All child task updates are visible under Project level Updates fields
Description - We have WF set up so that all users are working off central time zone. When anyone in a different time zone enters a day off on the Time off Calendar in WF, their one day off spans two days. Why is this feature important to you - WF should go off the settings of the individual in Workfront (central) and our Workfront Instance (also central) instead of defaulting to the time zone that the individual is working from. How would you like the feature to work -I would like the time off calendar to show the one day off that they are taking, instead of appearing as two days off. Current Behaviour - WF currently shows two days off for anyone working outside of the central time zone.
Description - Right now, you are not able to move an approver in the loop when setting up a project. Instead you can only add an approver to the end of the loop or create a new loop. It would greatly enhance my experience if while in an approval task I can drag and drop or move up and down approvals rather than remaking an approval loop. For example, if the loop is "Proofreader > editorial > sponsor > owner" and I want to rearrange to "Proofreader > owner > sponsor > editorial" I should be able to just flip flop them in edit mode rather than delete the loop and add a new one or manually adjust by adding approvers to the end. Why is this feature important to you - This would make updating approvals while in a project faster saving time. How would you like the feature to work - While editing an approval loop be able to click and drag users from one step to another as well as reorder steps. Current Behaviour - You can only remove users from the approval and then add back in the order you want.
Description -Why is this feature important to you - instead of have 1 annotation for each of my 100 report / VRS, having this feature will allow 1 annotation. A specific annotation may be applicable to 100 out of my 200 RSID/VRSHow would you like the feature to work - Ability to select which report suites to be added to.Current Behaviour - Currently allowed to add to 1 or ALL
Currently, tokens are only permissible within the Flow Steps of Smart Campaigns (in some instances, even that's not possible - and you must hard-code the actual value). It would be a huge time-saver - especially as we templatize our programs - if tokens could also be used within the Smart Lists (triggers and filters) of Smart Campaigns.
This might sound unusual, but I request custom form for HOUR object. On hour records, such as on January 1, we would like the option to enter more information along with the comments.There is where the custom form should be available:
DescriptionThe proposal is to integrate quantum computing capabilities into Adobe Target’s personalization and optimization workflows. Quantum computing enables processing of exponentially complex datasets and can solve optimization problems faster and more accurately than classical AI. By embedding quantum-inspired or quantum-hardware-accelerated models into Adobe Target, businesses can achieve ultra-precise personalization and superior optimization outcomes. Why is this feature important to youNext-level personalization: Today’s AI-driven personalization is powerful but constrained by classical computing limits. Quantum computing can unlock new levels of accuracy and context-awareness.Faster experimentation: Reduce time-to-confidence in A/B and multivariate testing, helping businesses act on insights faster.Competitive edge for Adobe: Adobe would become the first mover in merging marketing technology with quantum innovation, increasing adoption of Adobe Target.Revenue impact: Superior personalization drives higher conversions, customer engagement, and long-term loyalty, directly benefiting Adobe’s clients and Adobe itself. How would you like the feature to workIntegration Layer: Introduce a “Quantum Optimization” mode within Adobe Target, where certain algorithms (e.g., multi-arm bandits, constrained offer orchestration, journey optimization) can run using quantum-inspired solvers.Opt-in Pilot: Allow businesses to enable quantum acceleration as an experimental strategy for specific activities or recommendations.KPIs for Measurement:Accuracy lift in personalizationReduction in regret/time-to-confidence for testsConversion rate improvementsArchitecture Suggestion:Start with quantum-inspired algorithms on classical hardware (D-Wave, IBM Qiskit simulators, etc.)Provide extensibility to connect with actual quantum hardware backends in the future. Current BehaviourCurrently, Adobe Target relies on AI and machine learning models running on classical infrastructure for personalization, testing, and optimization. These models are effective but face computational limitations when handling:Very large audience segmentationHigh-dimensional testing with multiple offers and constraintsReal-time, privacy-safe personalization across billions of signalsQuantum acceleration does not exist in the current system, leaving unexplored potential for ultra-precise personalization.
DescriptionWe would like an API in Adobe Journey Optimizer (AJO) that allows us to preview an email template for a given profile. The API should return the rendered HTML of the email as it would appear when sent to that specific profile. Why is this feature important to us?We have existing tools that measure email quality, score campaigns, and validate templates before sending. How would you like the feature to work?An API endpoint where we can pass:Profile ID / Attributes to generate a personalized preview.Email Template ID or campaign details to specify which template to render. The API should return:Fully rendered HTML of the email as it would appear for the given profile.Any errors or warnings if there are missing personalization fields or rendering issues. Current BehaviorCurrently, AJO does not provide an API to fetch a personalized email preview for a profile.
Description -Why is this feature important to you - - We need to share an annual receipt with our customers for tax purposes. The file needs to be in a format that is not easily editable. - Not all customers have an account, so the requirement to create and account to access the PDF is not an option. How would you like the feature to work - - We need to be able to pick up the appropriate version of the PDF from a server based on customer ID and attach the version to the email and deliver to the customer. This is possible in other Email Solutions (Acoustic, SendGrid, MailGun) - A url to the PDF is not acceptable....unless the URL could locked down to only that email address, with no ability to guess/hack/scrap and determine the location of the other files for the customer. Current Behaviour -Need to engaged Third-party tools
Description:The current capabilities of Adobe Workfront and Fusion do not fully support the need to restrict users from changing proof decisions after a stage has been locked. This poses a risk to the integrity of the proofing workflow, as it allows proof creators to unlock stages and alter decisions, potentially affecting the outcome of the proofing process.Why is this feature important to you:This feature is essential for ensuring the security and reliability of our proofing workflows. By preventing unauthorized changes to proof decisions and stage locks, we can maintain the integrity of our decision-making process and ensure that all stakeholders have confidence in the final outcomes. This is particularly important for teams that rely on accurate and consistent proofing processes to make informed decisions and maintain accountability.How would you like the feature to work:Restrict Stage Unlocking: Implement a feature that allows administrators to set permissions that prevent any user, including the proof creator, from unlocking a proof stage once it has been locked. Only users with explicit system administrator rights should have the ability to unlock a stage after it has been locked.Enhanced Decision Change Tracking: Develop a feature that allows for tracking and reporting on changes to proof decisions. This could include:A new "Decision changed flag" field that is automatically filled out when a decision is changed, allowing for easy reporting on changed decisions.A notification system that alerts relevant stakeholders when a decision is changed after a stage has been locked.Current Behavior:Proof creators can unlock proof stages and change decisions after a stage has been locked (regardless of their proof permissions level), which poses a risk to workflow integrity.Fusion does not reliably track changes in proof decisions, especially when the overall proof status does not change.Workfront lacks specific reporting capabilities to filter and identify changed decisions, making it difficult to track and report on decision changes.
Description - Some users (either on accident or on purpose) list the tasks of a project by percent complete, start date, due date, etc. instead of by the task number. This leads to them requesting help or questioning if Workfront has had an update that then blocks them from seeing "+ Add More Tasks" below the list and the inability to nest task only discover that those features aren't allowed because the tasks aren't listed by their number. They were unaware that not listing the tasks by their numbers would disable those features. Why is this feature important to you - It would be helpful for people to know that the way the tasks are currently ordered in will block certain actions to the tasks or projects. While the text and icons for those actions are missing for them, it has caused them to question if there's a bug, did something change with their access level to the project, did something change with their account, or if clearing their cache and cookies is the fix. If they had a visual indication that features are blocked due to the current sorting, that would cut down on the amount of confusion and calls system admins field when listing the tasks by the number ends up being the solution. How would you like the feature to work - Enabling some sort of visual indication or warning on either the project or tasks that features like nesting aren't allowed with the current ordering of tasks would help users understand what is going on when they try to perform those actions. Something similar to when you try to assign a user to a task when their access level won't let them complete it. Current Behaviour - There's currently no visual indication that some features are blocked when the task list is not listed by the task number.
Description - Right now, users with "Team Monitoring" access cannot view WF module configurations or datastoresWhy is this feature important to you - With our governance model, only a few individuals can develop in PROD while other devs work in lower lanes. But when it comes time to troubleshoot their PROD scenarios, Team Monitoring doesn't allow them to see WF Module configurations or datastores. Making it near impossible for accurate troubleshooting so they can fix in Sandbox and promote to ProductionHow would you like the feature to work - Team Monitoring access should allow users to VIEW EVERYTHING without the ability to make changesCurrent Behaviour - Team Monitoring restricts users to only seeing Fusion scenarios at a high level without going into the details
We can set tokens a first level folder level, but it is impossible to set token on the root folder.And yet this would be awesome as we could set company defaults.When using workspaces, these would become workspace level tokens.
Make the Field Manager more useable! I hate that I have to download my entire list every time I just want to look up the API value of a field. Would love to see the field manager tab show the API names. Don't really care as much about where it's used, especially since the "And More" button does nothing. Show us useful info: what kind of field is it, what are the API names.
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.
