Product Communities

Description - The derived fields UI to grab and persist a URL query parameter, for instance UTM parameters like "utm_source", "utm_medium", etc. seems rather counterintuitive, at least I have not managed to set it up successfully to assign a utm_source grabbed on pageA to pageB.  Which functions to use is a little unclear, and setting the persistence does not seem to work as expected. From what I have read, you will somehow need to check if the query param is set on pageB and if not, return the previous value?   It would be amazing if a working approach could somehow be baked into CJA derived fields function templates and call it something like "Get and persist query parameter" or whatever.   Why is this feature important to you - The UI should be as simple as possible and self explanatory. If there are multiple steps needed to come to a result, it would help to provide guidance or a template to avoid making "beginner" mistakes.   How would you like the feature to

Resumen de la solicitud de mejora de funciones (RFE): Currently, AEM’s XSSProtection configuration (/libs/cq/xssprotection/config.xml) does not allow several accessibility-related attributes such as aria-label, aria-hidden, role, and tabindex.We propose including these attributes by default in the configuration to improve accessibility support and reduce the need for overlays or custom configurations. Caso de uso: Developers using HTL expressions like: ${property @ context='html'} cannot render accessibility attributes defined in component properties, since they are filtered by the XSSProtection mechanism. This limits the ability to build fully accessible components following WCAG and ARIA standards. Comportamiento actual/experimentado: When rendering properties that contain ARIA or accessibility-related attributes, these attributes are removed by XSSProtection because they are not listed in config.xml. The only current workaround is to overlay /libs/cq/xssprotection/config.xm

Our PMs would like to have the ability to edit the Template field on a project. Sometimes they need to switch out the template that's used via the Attach Template feature (because they don't have permission to delete the project and re-create it with a new template); however, the project relationship doesn't reflect this. This causes inaccurate reporting in some cases - when the project duration is compared to the template duration, for example.

For most normal dimensions you can only generate dynamic columns for the top 5 items.  5 is a very small number (I needed 8 the other day and was stuck!) - is there any chance of increasing this? If there are performance worries, even a small increase to 10 or 20 would be very useful! The feature can be seen here: Dynamic Columns In Analysis Workspace Freeform Tables | Adobe Analytics - YouTube

To be able to export from the Updates TabWe are archiving projects, and this is one more piece of project informationTo Export in PDF format (landscape or portrait)Current there is no option.

Description -the document upload notification email to say what folder the document was uploaded to. It would be nice to see that the document was uploaded to the "internal review" folder (in our case) and the project status doesn't need to change without having to go into the job and look each time.  Why is this feature important to you -This would save our traffic team a lot of time. We wouldn't need to go into the project only to see that there is no action required from us yet. How would you like the feature to work -the document upload notification email to say what folder the document was uploaded to. Current Behavior - The notification email just says a document was uploaded to the job. I have to go in to the job and click to several different screens to see what folder its in to know what action I need to take.

One of my biggest issues when it comes to coding landing pages/ emails is the white screen that plagues the Marketo Designer. It would be really cool to add the option to switch on "dark mode" to make coding easier as the black screen helps with coloring and finding/fixing errors. I'm not entirely sure if this already is a feature - but I haven't been able to find it and I think it would be an awesome asset to add for people who tend to code a lot and don't have the resources outside of Marketo. What do you guys think?  

When developing email templates that work with both light and dark mode, using <picture> and <source> tags with a fallback <img> inside it is a clean way to set both light and dark mode images without having to assign the image a conditional media query show/hide via CSS. However, the TinyMCE editor today will strip this markup rather than allow it to be in editable areas. Can this please be updated to no longer have this behavior?

Request for Feature Enhancement (RFE) Summary: display number on assets in list view Use-case: to have an easy way to know how many asset we select Current/Experienced Behavior: today we have a clear view of the total amount of assets in list view, but if we need to select only 35 assets (because of limitation on other flows for ex) then it's quite complex to do Improved/Expected Behavior: if in each line we have the number of line, then it's easier to do the selection Environment Details (AEM version/service pack, any other specifics if applicable): display number on assets in list view Customer-name/Organization name: Louis Vuitton Screenshot (if applicable):   Code package (if applicable):  

Description Love the Company Folder and the ability to share a group of projects across your organization, but want to potentially share only relevant projects for users and / or want to hide non-relevant templates and folders?  Current state, the Company Folder is an all-or-nothing holding ground for placing reports and enforcing automatic sharing privileges.  However, there are situations where you want only a certain team or group of individuals (maybe even product profile) to access a certain folder or even see that folder.     I'm proposing the idea of allowing users to create a "Shared Folder" that will let you set-up your own sharing permission that allows you to create a project and move to the folder and all members of the group will be able to access, but will not have to give carte blanche access to all members of your company.     Why is this feature important to you I often have a team of core people I work with for certain projects

Request for Feature Enhancement (RFE) Summary: Possibility to schedule the production deployment via Cloudmanager for Blue/Green deployment type. Currently, this feature is not available for Blue/Green deployments via Cloudmanager Use-case: The deployments via cloud manager takes too long, and we also don't want to start this in the evening a day before as then it doesn't leave much time for the next day for the new Green instances. Green instances stay active only for 24 hours. With scheduled deployment capability, we will schedule this to run early morning before the working hours start so that we are ready for next steps when the working hours start. Current/Experienced Behavior: This capability is not present Improved/Expected Behavior: Scheduled Cloud manager deployment for Blue/Green deployment Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5, Cloudmanager Customer-name/Organization name: Eurowings Screenshot (if applicable

The recent calendar look/feel upgrade from May 2025 no longer allows multiple entries (more than 2) from displaying for each date. Instead, the user needs to click on the "more" option which appears on any date with more than 2 entries. The text is light grey, blends in with the background, and is easy to miss. It's causing confusion among our users who do not see their entry and are unaware of the "more" functionality. We would like the option in Setup to turn off "more" and simply display all the entries, which was the standard prior to the May 2025 update.

Description - Currently, when you share a document folder on a project template with a group / team / individual, or choose to not allow inherited permissions, when you create a project those same permissions set do not carry over. However, part of the purpose of templates is determining permissions to be on the created projects, so this setting not carrying over doesn't make sense...Why is this feature important to you - We need the ability to restrict access to certain document folders and should not have to do it on each project, but rather at the project template levelHow would you like the feature to work - Created projects should receive the same folder permissions set on the project templateCurrent Behaviour - Projects created from templates do not retain the same folder permissions set on the project template when created

Request for Feature Enhancement (RFE) Summary: Do not open Page Properties in fullscreen  Use-case: Users provide images in the page properties to be used by teasers, og:image, etc.   Current/Experienced Behavior: In AEM page editor, when one opens the page properties, the dialog is opened full-screen. I.e. It covers the Asset selector on the left rail. This means a user cannot use the search, filter and drag&drop capabilities the asset dialog offers. If more than one page is to provided with the same image, a user has to open each page and browse to the asset individually. Improved/Expected Behavior: Keep the left editor rail visible and open the properties dialog in a modal lightbox or only covering the page. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest and AEM 6.5 Customer-name/Organization name: all Screenshot (if applicable): Desired behavior:   Code package (if applicable):  

DescriptionWe have dozens of Roles, and hundreds of Teams, Reports, and Dashboards. The only tool that is built into Workfront to help us document and govern these objects is the Description field.  The absence of custom parameters on these objects is limiting in what and how we are able to document their usage.We would like to attach custom forms on these object types so we can spend less time tracking down all the people and places throughout our instance that are impacted by updates to these objects.This was enabled last year for other objects like Groups and Billing Records. The efficiencies gained by those enhancements should be further expanded to these additional object types. Why is this feature important to youIt is challenging to track and document governance-related details on these objects because we have only the description field to do so, and that field is exposed to all users. How would you like the feature to workFor Teams, Roles, Reports, and Dashboards, we would

It would be nice to be able to programmatically access the QA URLs for a current running AB test.  We run a small subset of front end tests in our CI pipeline and we need the tests to be deterministic.  The way we do that now is manually retrieve the QA URL from the adobe target GUI.  We'd like to have the test determine the experience without having to retrieve the QA URL manually.   I have two suggestions:First:  Add it to the existing `Get AB Activity by ID` Second:  Create a new API to `Get AB Activity QA URLs by ID` Suggested response:    "experiences": [ { "experienceLocalId": 0, "name": "Experience A", "visitorPercentage": 34, "qaUrl": "at_preview_token=g5xKOs9QjAl3KN%2BwvyAAmnWEFq%2Br1NJA9GWwjZnLpb4%3D&at_preview_index=1_1&at_preview_listed_activities_only=true&at_preview_evaluate_as_true_audience_ids=1100025", "offerLocations": [

Description - It would be extremely helpful to have the ability to remove individuals from the Workload Balancer tab of a Workfront project once they are no longer assigned to any tasks. Why is this feature important to you -This creates unnecessary clutter and makes it harder to focus on the actual project team members who are actively contributing to the work. Having a way to automatically or manually remove unassigned users would streamline resource planning and ensure that only relevant team members are visible when reviewing project resourcing. How would you like the feature to work - View Description.  Current Behaviour - Currently, even after reassigning a user's tasks to another user or job role, their name still appears in the Workload Balancer. 

Description - We would like the ability to upload a structured document (e.g., Word, PDF, linked SharePoint file) to a Workfront object (like a tactic or project) and have Workfront’s AI extract key data points and populate designated custom form fields. This would streamline the setup of records that rely on structured metadata already captured in offline templates. Why is this feature important to you - This functionality would eliminate redundant manual entry and improve data consistency across Workfront objects. It is especially important for our marketing team, which uses Workfront tactics to manage a content inventory. Each tactic has structured metadata that already exists in a completed Word template. Currently, this information must be copied and pasted into custom form fields, which is time-consuming and error-prone. How would you like the feature to work -Allow users to upload a structured document (e.g., .docx or .pdf) to a project, task, or tacticWorkfr

It would be great to be able automatically un-sync a program from a SFDC campaign when the program is archived. 

Description - only proof approvals are currently sorted by the deadline set within the my approvals widget. Confusion with users thinking there is not anything for them to approve because the urgent ones are sitting on the last page of the widgetWhy is this feature important to you - enable users to better manage their assigned approvals directly from the home pageHow would you like the feature to work - task and document approvals are sorted by the deadline that is set, enabling users to see the most urgent approval on the first page of the widgetCurrent Behaviour - document approvals appearing within the my approvals widget sorted by entry date

Description -Why is this feature important to you - in most cases UPSERT flag is required for a dataset. the option to enable upsert flag can be done only through API. it will be good if we have this option in UI.How would you like the feature to work - enabling UPSERT flag in UI as a toggle button.Current Behaviour - currently UPSERT flag can be enabled only through API.

Description - We would like a more intuitive way for requestors to clear out data in irrelevant form fields when they change their selections in a request form. Why is this feature important to you - We want to eliminate confusion for requestors and prevent errors in automated processes and reporting. Currently, our Fusion scenario triggers messages based on a calculated field, and retained data from previously selected options can cause false positives. Requestors often believe they’ve submitted the request correctly, unaware that hidden fields still contain outdated data. How would you like the feature to work - When a requestor unselects an option, any data entered in fields associated with that option’s conditional logic should be automatically cleared. This would ensure that only relevant data is retained and reduce the risk of errors caused by hidden, outdated inputs. Current Behaviour - Our request intake form uses extensive conditional logic. Occasionally, a

Currently, Workfront calendars lack the "Run this report with the Access Rights of" setting that exists in Workfront Reports. Without this feature, every user must be granted access to every relevant project in order to view the calendar.  It would be extremely beneficial if Workfront Calendars could adopt the same access rights as Reports. Calendars offer a more intuitive and visual way to communicate timelines compared to reports. For use cases like tracking launch dates across multiple teams and departments, calendars provide a clearer, more accessible view that supports better planning and coordination. Our department—and the company as a whole—heavily relies on Workfront calendars for their visual clarity and ease of use. We've built department-wide launch calendars to track email deployments and web production go-live dates. I spoke with a support representative today who confirmed that this feature previously existed. I recall this as well—it was a key reason

I would like the ability display a field solely on whether a previous fields was filled in. For eample I have a situation where I need to enter in up to 5 supplier names but only want the next supplier field to appear if the previous was entered.

Request for Feature Enhancement (RFE) Summary: Wildcard DV certificates and wildcard subdomains Use-case: For DEV and STAGE environments often a common publish domain is being used. As the default Adobe one (https://publish-pxxx-eyyy.adobeaemcloud.com/) does not allow subdomains the individual sites are addressed via subdomains of that common domain to have a similar setup as PROD (1 domain = 1 website). That allows even automatic mapping of content paths to sites without needing setup costs for additional sites. Current/Experienced Behavior: Cloud Manager does neither support wildcard domains in the domain settings (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/custom-domain-names/introduction#usage-notes) nor does it allow wildcard DV Adobe-managed certificates. Therefore each subdomain requires - Configuration via the Domain - Domain verification via additional TXT record - Set up a dedicated DV manager c