Build better products with our product team
My organization is pretty good about not bothering folks with emails on Holidays or Weekends, however our Workfront emails still come through from the system even on days when we aren't open for business. This just leads to additional clutter in inboxes to sort through for users who are assigned to a lot of objects. My organization is pretty good about not bothering folks with emails on Holidays or Weekends, however our Workfront emails still come through from the system even on days when we aren't open for business. This just leads to additional clutter in inboxes to sort through for users who are assigned to a lot of objects. We have holidays identified in our corporate calendar in Workfront so the system knows folks aren’t working on these days. With that same logic we should be able to suspend emails on these days
Retain Simple Formatting When Exported to Excel such as having Two Columns Combined.
Right now the only way to extend work on a task into the next sprint is to move it. We want to keep track of the points and work completed in the last sprint, but move the task into the next iteration. When doing this we lose all of the update history but need that to continue work.
Description - This is something I continue to be frustrated by when I have to break out data in Workspace. I created Classifications so I could break out my data, but it's a highly time-consuming challenge to constantly break out the data to make it consumable on a larger scale. Instead of a limited set of results, I am requesting for Adobe to simply blow out the full breakdown for a specific table that we build in a Workspace.For instance, if I have THREE fields from a Campaign Tracking code I would want to break down, it would be a lot easier to drag them into the Table Builder and hit BUILD than to individually drag my fields into the Freeform table, even if I have multiples highlighted to enable a certain level of mass updates. Why is this feature important to you - This is about saving a LOT of time and tedium. How would you like the feature to work - Drag the necessary fields into the Freeform Table, and instead of being limited to 5 items in my breakdown, it would breakdown ALL items appropriately, as demonstrated by the fields selected. Current Behaviour - Currently, the interface only allows a maximum of 5 items to be broken down at each level and barely scratches the surface for what is often needed when a breakdown is being attempted at this level.
When is Marketo going to support AVIF images?You can upload an AVIF image but when selecting images to use, no thumbnail is displayed (it just shows no preview available). Once you select the AVIF image, you get a system error. Dismiss the error and everything is fine, but this is really annoying and makes it harder to select the proper image.Here is the error:
Please create a way for me to update the field label of a field when it is in use! We have fields that we are using throughout our instance that are too deeply integrated to update with the current workflow. Our specific use case is related to attribution tracking. We are adding and changing some UTM fields and would like to update our field labels to denote 'First Touch' and 'Last Touch'. We are using global forms but the fields are still too intimately tangled with our programs, filtering, etc. for us to be able to remove the field from use in order to update the name. Its not critical to the business but it would make my life a whole lot easier if we could do this!
For audience composition, enrichment with a lookup dataset is a useful feature. However to generate the lookup dataset, either an external data load or a scheduled query in Data Distiller is needed to populate the dataset.Quite often this data is of a "refresh" nature, i.e. the best way to handle is to purge the dataset, and reload the fresh data - as record links may also be deleted in the new load.Dropping the dataset, and creating a new one with CTAS is not an option, since the reference link for enrichment in the Audience Composition would need to be restored. Why is this feature important to you - we have multiple use-case scenarios where we have to enrich a certain segment with extra data for personalization in AJO.- we have also use-cases where the rule segment builder is insufficient to design the query - a designated more complex query (via query service) is needed to prepare extra data which can be used in to filter on. Adding this extra data to the profile could bloat the profile at the end (if multiple of these scenario's are needed). How would you like the feature to work- the ability to run a CTAS "replace" query, where the previous inserted batch is deleted before the new batch is inserted Current Behaviour- batch deletion is only possible via API, and needs an external process to manage. We would like to have an option which is part of Data Distiller and does not require an external process.
Can a feature be added to make the name of an already established proof static? Now when a revised proof is added, if it is a single document or multiple documents added to a combined proof this is not the case. If a single document is added as a new version, and the user does not edit the document name, the proof is renamed to match the new document. Why? If new documents are added to a combined proof then the proof asks the user to add a new name. It would make the user experience better if once a proof is started, the default should be to pick up the previous name automatically. There can still be an option to edit the name but that should be secondary. It seems like the default should be to always use the name of the previous proof and not default to renaming a new single proof based on the file added.How would you like the feature to work?It would be great to flip the default behavior to not rename a revised proof. Current BehaviourWF Proof defaults the proof name based on the file being added. For revisions to an already established proof, the default is to rename the proof based on the file being added. For combined proofs, it makes sense that users have to add the initial proof name but revised proofs have a blank field to name revised proofs.
Description - We have a business use case where users need to export CJA Reports to DLZ. Currently, the exported file names appear as follows: cja-export-CDE-9a9DDD-e6bd-456b-a1e6-f99b9fb1d622-173111111537-0.csv.gz. With this naming convention, it's challenging to identify which user exported a specific CJA report when multiple users are exporting files to DLZ.Why is this feature important to you - If multiple users are exporting the files its hard to understand who exported the file and what type of export it is.How would you like the feature to work - What we need:1. Is there a way to prefix the report with the (user ID) and a timestamp during export2. As soon as a scheduled (or manually) report is exported, an alert email should be sent to the end user, indicating that the report CNID_DATESTAMP_REPORTNAME... has been exported to DLZ. Current Behaviour - file export to DLZ just shows this: cja-export-CDE-9a9DDD-e6bd-456b-a1e6-f99b9fb1d622-173111111537-0.csv.gz
Request for Feature Enhancement (RFE) Summary: Since the Dispatcher doesn't support ETags it creates unnecessary traffic between the Dispatcher and the CDN by sending unchanged content. Use-case: The page is cached on both CDN and Dispatcher. CDN sends a request to the Dispatcher with the f-None-Match header. The Dispatcher responds with HTTP 200 and the content in the body, even though the content hasn't changed and the CDN already has the latest version. Current/Experienced Behavior: The Dispatcher is always returning HTTP 200 code when delivering cached content. Even when the cache ETag header value matches the value of the If-None-Match header in the request. Improved/Expected Behavior: The expected behavior would be for the Dispatcher to return HTTP 304 code with no body when ETag matches the value of the If-None-Match header. Environment Details (AEM version/service pack, any other specifics if applicable): Latest AEMaaCS - 2024.10.18311.20241017T104455Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable):
Description - At the moment you can't map fields from an incoming XDM object to the data object. Why is this feature important to you - We want to be able to have a 'clean' XDM object sent from the client to the Datastream, and then in the Datastream map values to the data object to populate Adobe Analytics. As we can't do this at the moment, we have to duplicate things client-side. e.g. we put the value in XDM for the RT-CDP and duplicate that value in the data object for Adobe Analytics. This causes the most pain on mobile apps where we are more reliant on developers to do the setting of variables. How would you like the feature to work - When mapping fields in a Datastream, I want to be able to set paths in the data object as the 'Target Field' Current Behaviour - Currently it returns an error "Invalid schema path"
Description - I would like to "watch events" for specific user in Fusion, or converse exclude from watching specific userID. Why is this feature important to you - This would be huge resource saver and performance improvement for Fusion scenarios. Any upgrade to filtering capabilities limits the number of when scenario gets triggered. This saves customers operations, Fusion/Adobe resources, so the benefit is mutual. How would you like the feature to work - have an option to include/exclude updates made to a given object type by a userID. This field is available in watch event output bundle, so I'm guessing adding this as filter option should be easy. Current Behaviour - We use service account to perform tons of operations in Workfront. Excluding this account in watch event modules is critical to limit the number of times scenarios are being triggered without a need. Worst case scenario is where ~90% of times scenario is triggered by service account updates and I can only filter that after first module.@gevorg_kazaryan
機能改善要求（RFE）概要： When editing a live-copied Content Fragment, please enable breaking inheritance directly in the New Editor. ユースケース： The author localizes the values of the live-copied Content Fragment. 現在／体験した動作： We have to switch editing modes to break inheritance, which is very inefficient. 改善／期待される動作： In the New Editor, I would like all the features covered by the traditional editor to be available, with additional new features added. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM As a Cloud Services 顧客名／組織名 Kyocera スクリーンショット（ある場合） コードパッケージ（ある場合）
Request for Feature Enhancement (RFE) Summary: This feature will enable organizations to define metadata validation rules based on compliance or guideline requirements and extract detailed reports for discrepancies. This will facilitate better data governance and streamlined updates to metadata across the organization. Use-case: Organizations often face challenges ensuring metadata adheres to evolving compliance regulations or organizational guidelines. Manual validation processes are time-intensive and error-prone, leading to non-compliance risks and inconsistencies in metadata quality. This feature addresses the need for automated validation and actionable reporting. Current/Experienced Behavior: Metadata validation is performed manually or using scripts, leading to inefficiencies. There is no unified interface or reporting mechanism to validate metadata against dynamically defined compliance rules. Discrepancies or outdated metadata are identified late, causing delays in remediation and compliance violations. Improved/Expected Behavior: Provide an intuitive interface for users to define validation rules for metadata (e.g., required fields, formatting, values adhering to controlled vocabularies). Automate metadata validation against these rules and generate detailed discrepancy reports. Offer configurable outputs (e.g., exportable reports in CSV/Excel formats) for review and remediation. Integrate with workflows for updating and re-validating metadata. Include support for recurring or scheduled validation processes. Ensure compatibility with diverse metadata structures and schemas. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Currently we are unable to see the user who last modified the asset. There should be field where the user who last modified the asset should be captured. Use-case: Current/Experienced Behavior: Unable to see the user who last modified the asset. Some hard coded value like "dam-workflow-service" is seen for now. Improved/Expected Behavior: Instead of "dam-workflow-service" username or user email who last modified the asset should be there. Environment Details (AEM version/service pack, any other specifics if applicable): Prod/Stg/Dev Customer-name/Organization name: Signify Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Allow customize wywisyg inline and richtext. At the moment is limited the wysiwyg and only allow some actions instead to use the full power of the wysiwyg. Use-case: Current/Experienced Behavior: Improved/Expected Behavior: With universal editor at the moment is imposible to customize or extend buttons for wysiwyg inline and richtext component. Should be fantastic to have configuration to allow hide/add new buttons in the wysywig. One simple thing as a color picker. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Santander Screenshot (if applicable): Code package (if applicable):
機能改善要求（RFE）概要： This is a consultation about applying custom CSS when authoring with AEM. The core component is designed so that you can only change the ID and cannot add classes.In terms of html validation, I don't think you can use the ID of each component when there are multiple identical components. However, in this case, the ID name will be unique and the same style will be written in CSS. Request the addition of the Class property in the core component dialog. ユースケース： Add Custom class CSS in core component dialog 現在／体験した動作： 改善／期待される動作： 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： 顧客名／組織名 Mitsubishi Electric Corp. スクリーンショット（ある場合） コードパッケージ（ある場合）
機能改善要求（RFE）概要： About the menu for text components As attached, only 5 icons are displayed at the top of the text component editing screen. If you display it in full screen, more icons will appear. With the current specifications, you cannot tell if there are multiple icons unless you use the full screen.Very difficult to understand. Request that all types of icons be displayed even if it is not full screen. ユースケース： menu for text components 現在／体験した動作： 改善／期待される動作： view all icon 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： 顧客名／組織名 スクリーンショット（ある場合） コードパッケージ（ある場合）
Request for Feature Enhancement (RFE) Summary: Rework the Translation Projects in a way that also normal users (and not only administrators) can see the members which are also assigned to the project in the tile "Team". Use-case: As a user who starts translation projects, I want to see who else is member of the translation team. And, with which rights. Current/Experienced Behavior: Only member of administrators group can see all members in the "Team tile". The member itself are just seeing one member here - that's his account. System shows always "Team (1)" as title of the tile, which is wrong in this case. So, for the normal user this tile is completely USELESS (and shows actually wrong information in case there are more members). Improved/Expected Behavior: Tile "Team" in the Translation Project should show all members which are assigned to the team also for non-admin users! And, would be quite helpful if there would an hover effect on the avatar icon showing details of the person. With that you save the click to open the whole overview page. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Rework the functionality how settings, which user can adjust, are saved. The current way to do that with a cookie avoid an efficient way of working for editors if they are switching devices and or browsers. Use-case: As an editor, I configure my AEM UI to my needs so that I can work most efficiently. So, e.g. I set up the left pane to show always the content tree. If I use another browser or switch the device, I'm working with, those settings should be still effective. Current/Experienced Behavior: Setting are not kept as the are stored not in the user account in AEM but in a cookie (which by the way expires also at next day, I think) Improved/Expected Behavior: Make those settings persistent in the user account within AEM so that it is not necessary to set them up every time. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Develop graphql sorting feature Use-case: If I want to sort graphql results by a name/number field alphabetically, current graphql doesnt support. Current/Experienced Behavior: If I want to sort graphql results by a name/number field alphabetically, current graphql doesnt support. Improved/Expected Behavior: Graphql should support sorting features for text or number or dates fields Environment Details (AEM version/service pack, any other specifics if applicable): All Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Idea Summary: The new Cloud Manager Content Fragment (CF) Editor does not support displaying custom field types such as ColorField, TextArea, and PathField, which were previously replaced in the classic editor. This lack of support significantly impacts users relying on these customizations for structured content authoring. We propose adding native support or a UI extensibility option to render these field types appropriately. Business Use Case: Organizations using AEM depend on custom field types to maintain structured content entry consistency. The inability to render these fields in the new CF Editor forces users to revert to the classic editor, limiting their ability to leverage new UI features. Providing native support for custom client-side renderers would enhance usability and encourage migration to the new UI. Current Behavior: The CF Editor does not recognize or display custom fields such as ColorField, TextArea, and PathField. Custom client-side renderers are ignored, making values stored in these fields inaccessible. Users must use the classic editor to maintain content integrity, reducing the adoption of the new UI. Expected Behavior: Support for rendering custom field types within the new CF Editor. The ability to register and reference custom client-side renderers for field visualization. Improved UI extensibility to maintain parity with the classic editor’s capabilities. Steps to Reproduce: Replace a single-line text field with a ColorField, TextArea, or PathField. Open the Content Fragment in the new CF Editor. Observe that the field does not render as expected. Open the same fragment in the classic editor and see the expected rendering. Impact & Benefits: Ensures a seamless transition from the classic editor to the new UI. Improves content authoring experience by maintaining structured field visualizations. Encourages adoption of the new CF Editor without sacrificing customization. We appreciate Adobe’s continued improvements and request consideration for this enhancement in a future release. Thank you for reviewing this proposal.
Request for Feature Enhancement (RFE) Summary: a feature to let the user "pin" (save) a specific path on AUP as a starting point when choosing assets or content links within AUP. After pinning a location, next time the user has to browse to an asset or content element, the pinned location is used as a starting point. Use-case: when editing pages on elements such as: - content grids (articles, case studies) - content grids (people) - page configuration (selecting hero banner image, selecting featured image, selecting thumbnail) - configuring links (CTA buttons, text links etc.) Current/Experienced Behavior: Expanding the directory path from the starting point is very time consuming, and it needs to be done multiple times - Country branches are not sorted in a meaningful way, which makes it very difficult to find the needed folder in the directory tree Improved/Expected Behavior: Example scenario 1 (non-exhaustive of the use cases): In a content grid, the user clicks to add a new item. They click the folder icon which opens the content structure starting at the "EY Unified Site" level. The user finds the directory which they want to be the new starting point for adding content to content grids and they "pin" and save this directory location. Once this is enhanced, in content grid, when clicking the folder icon, it starts browsing from the saved (pinned) location. The user has the option to unpin the folder and pin a new one if needed. Example scenario 2 (non-exhaustive of the use cases): Similar thing happens in the Page Properties / Images tab, where the user defines the assets to be used as page thumbnail and featured image. The "Pick" and "Select image" links open a dialog window which starts at the pinned location for assets. Note : the pinned locations for assets and for content are different. The user can pin a location for each of the different use cases – for content fragments, for links, for images and for documents Environment Details (AEM version/service pack, any other specifics if applicable): 2025.1.19149.20250116T154450Z Customer-name/Organization name: Aneesh.KM@gds.ey.com / Hans.vinje@nl.ey.com / EY / EY.COM Screenshot (if applicable): NA Code package (if applicable): NA
Description - Improve the speed of deleting projects Why is this feature important to you - Because the time of deleting projects takes a long time, the last one I deleted 6 copies takes 1 day to delete. How would you like the feature to work - The changes in our dashboard of projects will be fast in real time. Current Behaviour - It slow aprox 1 day.
Description - As the subject field is mandatory and Adobe does not provide the possibility to deactivate it, it would be good to be able to rename this field or modify the label Why is this feature important to you - The name subject is not enough for a briefing form and this name does not make sense for all briefings. This leads to misunderstandings. How would you like the feature to work - The best solution would be to be able to deactivate this field, the others would be to be able to rename it or at least setup a label / instructions for it. Current Behaviour - not possible
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.
