Build better products with our product team
We have discovered a strange ting that happens when we are pasting text into a fragment. If we are cleaning up the text in Notepad, and uses the text in a fragment we are running into some issues. It seems like if the text from Notepad has several paragraphs something strange happens. The first paragraph is recanalized as a paragraph and is placed inside a P-tag <p>. But the other paragraphs that is pasted in is for some reason placed into div-tags <div> This causes problems with the design of the content. Explained in code this would look something like this:Notepad text:Here is our paragraph text oneHere is our paragraph text twoHere is our paragraph text treeIn our fragment in AJO the code for this would look like this: <p>Here is our paragraph text one</p><div></div><div>Here is our paragraph text two</div><div></div><div>Here is our paragraph text tree</div>As you can see the tree paragraphs are acting in different ways, one as a pragraph tag, the two others as div-tags. And it seems like there is used a div-tag to create line space between the paragraphs -where Notepad has space.This causes some problems with styling if you are using customized style classes since a p-tag and a div-tag isent the same thing - and in most cased has different classes. It would be great if pasting of plain text with several paragraphs could have the same tag conected to each of the parapraphs - like <P> is been used for all.
Description -We recently customised our calendar so that week now starts on a Monday and ends on a Sunday.However, the descriptions in the data dictionary haven't updated and include the sentence: "By default, this refers to the time period that starts on Sunday and ends on Saturday prior to the current week.".We cannot edit these descriptions in the UI as they are "Adobe provided components".We feel that the existing definitions are likely to mislead users. Why is this feature important to you -The current behaviour is misleading. How would you like the feature to work - Either: a) The descriptions of Adobe provided components such as "Last Week" can be edited by users, orb) If users customise their calendar to change the start date of a week then the definitions for these date ranges are updated automatically. Current Behaviour -The descriptions cannot be edited as they are "Adobe provided components".
Issues:1) No horizontal scroll to see all the milestones. 2) Milestones names are missing when scrolled to the bottom to see horizontal scroll.3) Updating the filter breaks the page.
Request for Feature Enhancement (RFE) Summary: Currently when reprocessing assets, a popup displays and informs the users that they will be notified when their async job finishes. However, no notification is sent. Use-case: Content authors should be notified of successful job completions, especially if they are told they will receive a notification. Current/Experienced Behavior: Popup says a notification will be sent when the async job completes. No notification is sent. Improved/Expected Behavior: Popup says a notification will be send when the async job completes. Notification is sent. Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud Customer-name/Organization name: Netjets Screenshot (if applicable): Code package (if applicable):
Being able to add a risk at the task level would allow team leads to gain deeper insights into specific workflows, assignees, etc. that may need to be looked into further. Right now, they rely on project managers to add risks to the task description which they can't pull into a categorized report. This would allow team leads to gain feedback from their team members that it would help them better track and manage risks directly within the workflow.
Description - Ability to export custom forms into an excel formatWhy is this feature important to you - Users often ask to export information on projects into excel format for analysis on fields and / or for presentation purposes. How would you like the feature to work - Export the custom form from the admin view including field name, field description, and field display logic. Also export a filled out custom form on a project / task / issue with the field values for end users.Current Behaviour - Custom forms can only be exported in PDF format. The PDF is not presentation ready and is hard to navigate. Users can not easily copy / paste from the PDF or use the data in analysis.
Request for Feature Enhancement (RFE) Summary: In CloudManager label menu item "View current execution" when the execution is running Use-case: Current/Experienced Behavior: In CloudManager when the execution is running, the label in menu item says "View last execution" - this is semantically wrong/confusing. Improved/Expected Behavior: Current/Experienced Behavior: In CloudManager when the execution is running, the label in menu item says "View current execution" Environment Details (AEM version/service pack, any other specifics if applicable): latest Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: CloudManager: Status: Failed Use-case: Current/Experienced Behavior: In CloudManage, when the last pipeline execution failed, the status is "Running". Improved/Expected Behavior: In CloudManager in the dashboard and on the Pipeline view, show Status: Failed when the last execution failed (as do other CICD systems) Environment Details (AEM version/service pack, any other specifics if applicable): any Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable): n/a
Request for Feature Enhancement (RFE) Summary: API to get variation of Content Fragment Use-case: There is content fragment. Have to create variation of CF eg: FB , LinkedIn. Want to automate variation creation. Suppose we send content along with params like audience, Tone etc. On API hit we get the variation data. Current/Experienced Behavior: We have editor where we input data and get dariation. This variation we can copy paste or export as variation. Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud service Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - There was an update in Workfront on 10/22 which changed the request page to a new experience. Previously there was an ability to copy requests. Now we don't see that function. Please add this back.Why is this feature important to you - This was used daily by our marketing teams. We want to use the new experience but can't toggle it on until this is added.How would you like the feature to work - Add a "copy request" button that works the same as the old one in the old requests pageCurrent Behavior - There is no copy button on the new requests page
Request for Feature Enhancement (RFE) Summary: Environment configuration copy between the environments. Example: Stage to Development Use-case: We have two Development environment and on a requirement basis we would like to have the similar configuration between the environments. Current/Experienced Behavior: We cannot copy the configurations between the environments Improved/Expected Behavior: Similar to content copy feature, having this configurations copy will be added benefit Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: McAfee Screenshot (if applicable): Ticket No: E-001871093 Code package (if applicable): Ticket No: E-001871093
Request for Feature Enhancement (RFE) Summary: Currently, Cloud Manager and Splunk dashboards do not provide visibility into leader pod restarts in AEM as a Cloud Service environments. Identifying when and why a leader pod restarts is essential for understanding system stability and troubleshooting potential performance or replication issues. Having this visibility directly in Cloud Manager (or accessible via Splunk logs) would help operations and development teams proactively monitor environment health, correlate incidents, and improve root-cause analysis without needing Adobe support intervention. Use-case: Leader pod restarts can affect replication, workflows, or cache invalidation, but currently there is no easy way for customers to detect or audit these events. Providing this visibility would reduce investigation time during incidents, enhance transparency, and empower teams to maintain stable AEM Cloud environments. Current/Experienced Behavior: There is no visibility or alert mechanism in Cloud Manager or Splunk for leader pod restarts. Customers must rely on Adobe Support to confirm such events. Improved/Expected Behavior: Display leader pod restart events in Cloud Manager’s monitoring section, with timestamps and pod names. Alternatively, include this information in the Splunk logs or provide an API endpoint to query pod restart history.Optional alerting mechanism (email or webhook) when leader pods restart unexpectedly. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service – SDK version 2025.9.22758 (build: 20250928T092442Z) Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Migrate Content Hub configurations like Search Filters and Asset Metadata details across environments Use-case: Setting up of Content hub across program Current/Experienced Behavior: Need to configure all the settings including setting up of several custom search filters and asset metadata mappings manually across all environments. Improved/Expected Behavior: Need a self service way to import and export configurations for each environment or a mechanism to migrate the configurations from one environment to the other. Environment Details (AEM version/service pack, any other specifics if applicable): 2025.10.22943.20251009T135918Z Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Improve multilingual content management in AEM by enabling a single content fragment to support multiple languages/locales through a tabbed or variant-based interface. Use-case: Our content authors manage over 500,000 content fragments across 12 languages. Currently, each language requires a separate content fragment, resulting in significant manual effort and complexity when performing routine tasks such as updates, moves, deletions, and publishing. Current/Experienced Behavior: AEM requires a separate content fragment for each language or locale. Authors must manually replicate actions (e.g., move, update, unpublish, delete) across all language versions. Shared fields must be updated individually in each of the 12 language-specific fragments. This leads to a high risk of inconsistency, increased maintenance overhead, and a time-consuming authoring experience. Improved/Expected Behavior: Enable a single content fragment to support multiple languages/locales using a tabbed or variant-based structure. Allow shared fields to be updated once and reflected across all language variants. Provide built-in tools or automation to manage language-specific content more efficiently (e.g., bulk move, update, unpublish, delete). Reduce manual effort and improve consistency across multilingual content. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Version: 6.5 Service Pack: 6.5.22 Deployment:On-premise Content Volume: Over 1 million content fragments across 20 languages Customer-name/Organization name: Hyatt Hotels Corporation Screenshot (if applicable): Code package (if applicable):
DescriptionWe are requesting an enhancement to Workfront’s Proofing tool to allow greater flexibility in review workflows. Specifically, we would like the option for proofs marked as “approve with changes” to be sent back to the proof creator for updates before progressing to the next review stage.Why is this feature important to youSome internal teams currently use other project management tools because they offer more adaptable review workflows. The inability to send proofs back to the creator for updates after an “approve with changes” decision in Workfront creates challenges for teams that need to revise content before further review. This feature is crucial for meeting compliance requirements and would facilitate broader adoption of Workfront across our organization.How would you like the feature to workWe would like a configurable setting within automated proofing workflows that, when enabled, routes proofs marked as “approve with changes” back to the proof creator. The creator would then have the opportunity to make the necessary updates before the proof continues to the next reviewer. This should be an optional workflow step that administrators can enable or disable based on team needs.Current BehaviorCurrently, when a reviewer selects “approve with changes”, the proof automatically moves forward to the next stage in the workflow. There is no built-in option to send the proof back to the creator for updates first. Our only workarounds are either manually uploading a new version and adjusting the workflow, or creating multiple automated workflows for different scenarios, both of which add complexity and risk errors.
Similar to the recycle bin idea but more of a real time snap back to your last action. I know there is some functionality for this but our PM's accidentally delete tasks accidentally because they are moving so fast and it would be great if there was a button similar to other products out there so you can undo / redo your last several actions within a project. Having to go to a recycle bin to restore work is a multi step process that would cause frustration in times of fire drills.
Description - It would be wonderful if Workfront could identify duplicate values natively (without Fusion) when entered into a field.Why is this feature important to you - It would safeguard we don't have duplicate project numbers for future reference (we have customers that provide their own customer numbers/purchase order numbers, etc).How would you like the feature to work - A warning would come up if a specific field does not allow duplicate values.Current Behaviour - No way to identify if a duplicate project number is entered. Thus, if two users use the same project number, when searched, both would come up. It is very confusing for not only searching in WF, but also on our file server.
DescriptionAllow users to manually update or reassign the Group associated with a custom form in Adobe Workfront after the form has been created.Why is this feature important to youAs a System Admin, I often collaborate across multiple departments and groups. Custom forms are a key part of our intake and project tracking processes. However, when forms are created by users in one group, they become locked to that group—even if the form is intended for broader use. Being able to reassign the group would:Improve cross-functional collaboration.Streamline form governance and updates.Ensure forms are managed by the correct stakeholders.How would you like the feature to workI’d like to see a “Group” field editable by system admins or users with appropriate permissions. Ideally:The field could be updated in the form settings.A dropdown would allow selection from available groups.A confirmation prompt would warn about access changes or dependencies.Audit logs would track changes for accountability.This would mirror how other Workfront objects (like projects or templates) can be reassigned or shared across groups.Current BehaviorCurrently, the group is automatically assigned based on the home group of the user who created the form. The only workaround is to recreate the form using a user from the desired group, which is time-consuming and error-prone.
Request for Feature Enhancement (RFE) Summary: The Preview environment should be in Sync with the Publisher, to be able to preview the changes and see only the needed modifications. At the moment, AEMaaCS relies on the publishers to replicate the changes to both environments (Preview and Publish) this could lead into errors, leaving the Preview environment out of sync and breaking the purpose of it. The request is to have a service running that triggers replication to the Preview environment as soon as one page gets published. Use-case: Improve usability of Preview instance since the publishers will see only the content modified Current/Experienced Behavior: The Preview and Publish instances relies on manual user input to be in sync (publish twice) Improved/Expected Behavior: Preview and Publish should be updated at the same time during replication Environment Details (AEM version/service pack, any other specifics if applicable): AEM SDK 2025.10.22943.20251009T135918Z Customer-name/Organization name: UBS Screenshot (if applicable): Code package (if applicable):
The existing time dimensions (day, hour, minute) in the DWH are not fine-granular enough for a few clients' use case.Therefore, they are collecting the user-timestamp in milliseconds in a custom prop as a workaround for this issue. But this workaround has some disadvantages:a) User timestamp collected in the frontend is local and sometimes incorrect (days or years in the future/past)b) For some server calls, the prop is not collected / missingc) This workaround depends on the data collection (server-side timestamp would be independent of front-end data collection).Can this be considered a possible enhancement, making the server-side hit timestamp available as a dimension in the data warehouse?With my basic understanding, since DWH is the post-processed data. Any data on the DWH is the outcome of the raw data.Hence, this particular enhancement should first be in the data feed because the current data feed shows second-level information.
We have got ourselves into a situation where we have made many revisions to rules/elements which we have not published and no longer intend to publish. What is live and what is in our elements/rules are very different and it is now very difficult to get back to a clean baseline within rules and elements. The only way to do this is to manually revert every changed rule/element to match the current live version - very time consuming and prone to error. Please can you consider introducing a way to quickly update multiple elements/rules to match the live version?
Description - it is currently too cumbersome to commit to a new date. Users have to open the task to commit to a new date.Why is this feature important to you - users commit to new dates often so streamlined functionality is importantHow would you like the feature to work - from the My Tasks widget, open the summary area under quick actions and see the commit date field. OR have a commit date field as a column in the My tasks widget. Current Behaviour - Users have to open the task and select a new date from the commit date field.
Description - Many times database connection on Query Service get disconnected due to various reasons (limit of users reached being one of it). This affects the focus work as it disrupts the query execution, to avoid it User should have a connection refresh button which will allow the Database connection to be re-established without having to refresh the entire browser multiple times.Why is this feature important to you - Helps users to continue important focus query time without disruptionsHow would you like the feature to work - A simple refresh button the page should reestablish the connection to the database.Current Behaviour - Users need to copy the entire query and refresh the browser, it clear all the query results previous queries might have returned on the browser.
Description - We would like the option to be able to somehow setup repeatable deliverables in Workfront Planning. As it is now, if you want to repeat a campaign, etc. you need to manually copy any relevant record or develop something using Fusion or the API. Why is this feature important to you - Many of the initiatives that use Planning are inherently repeatable, from annual product launches to repeatable ad-spots, but there is no way to replicate a specific plan in order to be re-used for future plans. How would you like the feature to work - We would like to be able to either copy/ clone a record type and have all connected records also copy or the ability to create a Planning template from a specified record. Current Behaviour - Currently you can copy individual records but connections are not maintained so if you have an involved plan, you will need to manually copy each relevant record and add the connections or you would have you use Fusion or the API.
In the new unified approvals, you can't see the what was selected once a new version goes up. You have to flip back to the previous version to see who 'rejected' (needs work). You used to be able to see the approvals without having to flip between versions. Can be time consuming with a ton of documents to proof.
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.
