Build better products with our product team
Request for Feature Enhancement (RFE) Summary: When using asset-link, I can search for and use assets out of AEM directly in Creative Cloud Applications. But when I found an asset, I might want to check it's metadata, or check the folder it's in for other assets, and such. The asset-link UI is not good for such activities, and cannot do them.As such, it would be great to be able to directly open the asset directly in AEM - using the information asset-link already has to open the asset in the browser in AEM-ASSETS.Searching though cloudmanager for the right environment, then searching for the right asset inside of AEM is cumbersum and error-prone. Use-case: check/edit metadata of files used in asset-link review the folder the asset used in asset-link is in preview the edited asset in AEM with renditions etc. preview the edited asset in the experience the asset is for (website, etc.) Current/Experienced Behavior: The asset cannot be opened in AEM using asset-link Improved/Expected Behavior: Being able to open the asset in AEM ASSETS in the browser directly from asset link. Environment Details (AEM version/service pack, any other specifics if applicable): all AEM versions, but especially Cloud Services. Customer-name/Organization name: Adobe Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: searching fo all licensed adobe stock assets with the adobe stock connection in Assets Use-case: searching & saving all licensed adobe stock assets to internal DAM structure. Current/Experienced Behavior: no search filter for licensed assets vailable in stcok interface Improved/Expected Behavior: filter "licensed " assets Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Assets , adobe stock integration Customer-name/Organization name: EON Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: it is not possible to remove users from AEM Groups after the have been removed from IMS groups Use-case: we are using AEM usergroups to send out email Informations to users. if the user leaves out company we remove the user from IMS groups. consequentely the user dont have access to AEM any more. but user is still part of AEM Usergroup , so will still receive emails Current/Experienced Behavior: As the user can't log in, no "sync" has been initiated to remove him from AEM groups. Consequently, the user in AEM is still part of all the groups he was in before being deleted from all IMS Groups. Improved/Expected Behavior: find a way so that users can be remove from AEM groups- manualy or automatic cleanu / sync not relativ to users login Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Assets Customer-name/Organization name: eon Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Add Priority Queue in AEMaaCS Use-case: The customer is publishing bulk content via content tree workflow. When the bulk contents are in the queue, there is a delay if we publish any content directly via the quick publish button option. Current/Experienced Behavior: Delay in publishing the priority content Improved/Expected Behavior: Content publishing will be faster for priority content Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: LGE - APAC Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: enhance feature set for AEM Asset Reporting Use-case: We propose the implementation of a new features in Adobe Experience Manager (AEM) that allows users to create custom report templates for asset management. These templates can be saved and scheduled to run at user-defined intervals, such as monthly. The primary purpose of this feature is to facilitate the generation of reports that scan for assets scheduled to expire within a specified timeframe and defined meta data parameters. Key Features: Custom Report Template Creation: Users can create and save custom report templates and use again. Templates can include custom metadata fields configured by the user. Scheduling: Users can define a schedule for the report to run automatically, such as daily, weekly, or monthly. Email Delivery: Users can register one or more email addresses to receive the generated report. The report can be sent as a PDF attachment or as a link to a dashboard in AEM. Interactive Reports: The report includes thumbnails of the assets. Users can interact with the report by clicking on links that direct them to the respective assets in AEM. This can be implemented as an interactive dashboard within AEM or as clickable links in a PDF report. Use Case Example: A marketing team schedules a monthly report that identifies assets due to expire within the next specific parameters. The report includes thumbnails and key metadata fields such as asset name, expiration date, and usage rights. The report is sent via email to the team, and they can quickly review the assets and click on links to access them directly in AEM for further action. Current/Experienced Behavior: Not able to save templated reports and can only schedule once or execute now. Report need to be reconfigured each time used. Report not interactive. If exported from system thumbnails of images are lost. Improved/Expected Behavior: Create recurring report that has thumbnails of images and has live links to the assets in AEM. 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: Currently, Web Tier and Frontend pipeline deployments are not supported on AEM Cloud RDE instances. Use-case: AEM RDE instances make faster deployments possible but if team is using Web Tier and Frontend pipeline then there is additional change needed to maintain different configurations for RDE v/s non-RDE instance. e.g. Deployment to RDE mandates running full-stack build to deploy frontend and dispatcher code which would otherwise be going through separate pipeline on non-RDE instance. Current/Experienced Behavior: Currently, Web Tier and Frontend pipeline deployments are not supported on AEM Cloud RDE instances. Improved/Expected Behavior: Web Tier and Frontend pipeline deployments should be supported on AEM Cloud RDE instances. Environment Details (AEM version/service pack, any other specifics if applicable): Latest AEM Cloud version Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: When a server fails to successfully deploy the pipeline aborts leaving servers in various states of deployment. Instead when a publisher fails, the failed publisher/dispatcher pair should be left out of rotation and the deployment should continue to the next server. A notification/incident is sent/created to CSE and customer. In an environment where there are 10 publisher/dispatcher pairs one server or even multiple servers failing can be left out of rotation and still serve proper traffic. The aborted pipelines in this case cause 8-9 hours of delays, sometimes days to resolve. This costs all parties a significant monetary and time loses. Please create a JIRA ticket and request for this. Keep me posted on when that is created and share regular updates on the progress of the request Use-case: In large infrastructures deploys can take 9-10 hours to completed. One failure can cost hundreds of thousands of dollars in delays that can take anywhere from 12 to days of additional deployment hours, leaving part of the infrastructure in varying states of deployment. Rolling back or manually deploying to the remaining servers is not an option as content over 9-10 hours already has a delta, and manually deploying 30 packages across 21 servers takes even longer. This feature would reduce hours, and cost significantly as well as reduce the production server downtime caused by deployment failures due to infrastructure reasons. Current/Experienced Behavior: There are 10 publish/dispatcher pairs. The deployment fails on publisher 3 because publisher 3 is experiencing an issue or high load, when this happens the entire deployment is aborted. This leaves publisher/dispatcher pair 4 thru 10 un-deployed, so now we have author, pub1 and pub 2 serving traffic using new code and the rest of the stack serving traffic on old code. To redeploy the pipeline again using the re-execute feature can take another 10 hours. Improved/Expected Behavior: When a non author server fails to complete deployment, keep that publish/dispatcher pair out of rotation and continue the deployment to the rest of the infrastructure. Alert custom and CSE that a publisher/dispatcher is out of rotation due to a deploy failure. Add a feature into the CM pipeline that allows the ability to deploy to a single dispatcher publisher pair, or any server in your infrastructure. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 : 21 server infrastructure, 1 author, 10 publishers, 10 dispatchers. Customer-name/Organization name: Undisclosed Screenshot (if applicable): N/A Code package (if applicable): N/A
Request for Feature Enhancement (RFE) Summary: Determining the content of zip files solely from their title or file name can be challenging. It would be beneficial if marketers could attach images to the zip files (for thumbnails), as this would enable quicker visual identification. Use-case: Visually identifying the content of a ZIP via a thumbnail Current/Experienced Behavior: All zip files has same generic thumbnail. Thus, marketers need to check read through Titles/names. Improved/Expected Behavior: Associate Image with a ZIP to identify contents by looking at the thumbnail Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5/Cloud Customer-name/Organization name: Mondelez Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enhancing AEM Assets Reports with additional metadata fields that marketers can choose or deselect for generating reports would be advantageous. Furthermore, allowing marketers to create various asset report templates based on selected metadata and other criteria would provide even greater utility. Use-case: AEM Asset reports come with a predefined list of metadata that can be selected/deselected. Though custom metadata option is also available, but its technical. It would be good: - if the fields in the Asset Reports could be configured. - if a user could create an Asset Report template similar to Saved search and execute it when needed. Current/Experienced Behavior: - Cannot add custom metadata as checkboxes as it lies in Internal Area - Custom fields can be added buy defining exact property on Asset Report UI. Its too technical. Also, the configuration does not persist, thus one needs to configure it again before execution. Improved/Expected Behavior: It would be good: - if the fields in the Asset Reports could be configured. - if a user could create an Asset Report template similar to Saved search and execute it when needed. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5/Cloud Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Search Result Landing Page Use-case: Improve Search UX Current/Experienced Behavior: When a term is searched in the header/search component a list of links is returned Improved/Expected Behavior: When a term is searched in the header/search component a landing page with the search result is returned. In that page is possible apply filters and sort the results. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Adobe AEM Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Automatic Deletion of Merged Feature Branches from Adobe Git Use-case: We have a sync job that syncs organization-specific branches to Adobe Git. This job performs deployments to AEM Cloud as a Service Dev instances for testing and validation. Once the testing is complete, the corresponding feature branches are merged into the Main branch, which triggers deployment to AEM Cloud as a Service stage/Prod. However, the feature branches are not being deleted from Adobe Git after the merge, leading to clutter and potential confusion. Current/Experienced Behavior: After merging feature branches into the Main branch, these branches are automatically deleted from our organization’s repository. However, they remain in Adobe Git, which creates unnecessary clutter and can lead to potential errors. Improved/Expected Behavior: Feature branches should be automatically deleted from Adobe Git once they have been merged into the Main branch, mirroring the behavior in our organization’s repository. This would streamline branch management and ensure consistency across repositories. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud as a Service / Cloud Manager Customer-name/Organization name: Allianz Technology Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Rollout config "Activate on Blueprint activation" does not work for preview publisher node Use-case: Publishing Language Master instance of a page doesn’t publish the children/live copies. The children (IE, NI) need to be published individually to replicate to preview."Activate on Blueprint activation" rollout config has been set up but this only replicates to publish nodes. Current/Experienced Behavior: By default, any activation from the author only goes to publish and not preview. Improved/Expected Behavior: The replication must occur for preview node as well as this is also a publisher instance. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Customer-name/Organization name: Brown Thomas Arnotts Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: I have implemented permission-based caching for our secure site. The site will perform user authentication before serving any secure content. I have followed the document for configurations and implementation-https://docs.adobe.com/docs/en/dispatcher/permissions-cache.html For initial request/cached content not available, the Dispatcher directly calls AEM resulting in displaying the secure page without authentication. Use-case: Use Case 1: The user must be authenticated via the Dispatcher Auth Checker Servlet before serving secure content. Use Case 2: If the user's authentication via the Dispatcher Auth Checker Servlet fails, the dispatcher will not forward the original request to AEM. Current/Experienced Behavior: Current Behaviour for Use Case 1: When the requested content is not cached, the Dispatcher Auth Checker sends the request directly to the AEM publisher for page rendering, allowing the user to access secure content without authentication. Current Behaviour for Use Case 2: If user authentication fails, the dispatcher forwards the original request to the AEM publisher for page rendering without authentication. Improved/Expected Behavior: Expected Behaviour for Use Case 1: The user must be authenticated via the Dispatcher Auth Checker Servlet before serving secure content.Expected Behaviour for Use Case 2: If the user's authentication via the Dispatcher Auth Checker Servlet fails, the dispatcher should not forward the original request to AEM. Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Release - 2024.8.17465.20240813T175259Z Customer-name/Organization name: Boston Scientific (BSC) Screenshot (if applicable): Code package (if applicable): @gurjotsingh @akashramchandani
Request for Feature Enhancement (RFE) Summary: I have implemented the composite Multifield in Content Fragment by referencing https://jimfrenette.com/aem/content-fragments/composite-multifield In this implementation, we have added custom Client-Libs for composite multifield and show/hide target functionality based on dropdown selection. These custom Client-Libs are loading correctly and working as expected in the old content editor. However, in the new content editor, the custom Client-Libs are not loading, causing the functionality to break. Use-case: We have a dropdown, and on 3rd selection of the dropdown, multifield should show, and min value of multifield is 1 and max value is 5 Current/Experienced Behavior: When we open a new content fragment editor multifield is not getting hidden and giving a warning to add at least one item, as custom Client-Libs not loading Improved/Expected Behavior: In the New content fragment editor dropdown show/hide should work and also on the dropdown selection multifield items should show, Whereas in the old content fragment editor custom client libs are loading hence on the dropdown multifield is hiding and didn't get a warning Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Release - 2024.8.17569.20240822T203847Z Customer-name/Organization name: Bosten Scientific (BSC) Screenshot (if applicable): Code package (if applicable): @indrajitsi @gurjotsingh
Request for Feature Enhancement (RFE) Summary: Log Forwarding Option available for Amazon CloudWatch Use-case: Our client is using internally Amazon CloudWatch https://docs.aws.amazon.com/cloudwatch/ for all applications and would like to use that solution as well for AEM logfiles. I am well aware that AEM supports logforwarding using Splunk. On recent documentation https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding more logging destinations are documented. In case this will be part of an early adopter program, our client is interested in participating. Current/Experienced Behavior: No options are available for Amazon CloudWatch logforwarding Improved/Expected Behavior: An option will be made available Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Valtech. (Client doesn't want to be named in public) Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Here are some feature enhancments, these can be together or even just one of these implemented would solve a lot of problems 1.) Allow the selection of artifacts to deploy to production as one of the steps before deploying to production 2.) Decouple Stage and Production deployment pipeline. Ability to deploy to Prod independently of deployment to stage 3.) Ability to start at production deployment simply by selecting previously built artifacts instead of having to start every time at the beginning of the pipeline. Use-case: Our product can contain ~171 modules which crashes the Adobe CM pipeline running the server out of resources. If the production publishers are overloaded the CM deployment fails to just one publisher it aborts the entire deployment. In the above use cases if we can start from where we left off, or select the artifacts and maybe remove failing artifacts without starting over at the beginning of the pipeline that would improve efficiency. Sometimes ou CM pipeline runs for 12 hours while it builds and deploys to production Current/Experienced Behavior: Unable to deploy to production and lack of robust pipelines Improved/Expected Behavior: Ability to deploy to stage and prod in parallel. Ability to select artifacts to deploy to production without starting hte entire pipeline over again. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 Customer-name/Organization name: N/A Screenshot (if applicable): Code package (if applicable):
Hello, within a Workfront project there is the ability to minimize the parent task with the carat so that it pulls in all of the tasks below it and hides them within the minimized task. This helps to make the project smaller and hide the amount of tasks that are in there in order to navigate to the tasks that are still open. When logging out of Workfront, it removes the tabs that you minimized in each project forcing you to have to go and click all of those again in order to make the project more manageable. For example, if there are 5 months of content that you are providing to a client, and you want to minimize the first 3 months of it since you are already done with those tasks, this makes the project smaller so you can quickly look at the tasks that are still remaining. I would love for there to be a way to "Pin" the parent tasks after you minimize them so that every time you enter the project it is easier to navigate within it, instead of having to manually minimize the parent tasks each time.
When setting calendar availability in Dynamic Chat you can only choose availability by day of the week, this request is to enable controlling availability by specific dates i.e. instead of choosing every monday you can specify which mondays you are available
I would like to see increased filter functionality in the Assigned Work area of the Workload Balancer to include AND and OR statements.This would allow Assigned Work filters to pull tasks from a specific Portfolio (Client A) and for a specific Job Role (Strategic Planner).For example, we are trying to see all Client A's tasks assigned to a Strategic Planner. However, there can be different Strategic Planners supporting Client A's work so we cannot set the filter to specific USER IDS as this would be too limiting.Currently, when filtering Client A's tasks assigned to Strategic Planners, it lists all Strategic Planners even those that have have no Client A tasks. So there are many Strategic Planners showing with zero Planned Hours or empty rows.I would like to filter out those Strategic Planners with zero Planned Hours or empty rows for a specific Client or Portfolio but that functionality is not possible at this time.
Description - Workfront uses a banner functionality to let customers know that they are approaching their annual contract renewal date. Why is this feature important to you - There are announcements that as a system admin I would like to share across our Workfront instance as a banner for all users to see. How would you like the feature to work - For Workfront to offer the banner functionality to the customer facing side of the application for system admins to use to share out information as a banner across the top of all Workfront pages. Current Behaviour - Customers can send Announcements or Notifications that trigger an email or can be viewed via the Notification icon in the upper-right corner of the Workfront interface but there is not a banner functionality that would be visible to users from any page in Workfront.
The "Updates" tab of a project should serve as a feed of all activity - including comments made on proofs related to the project. Currently, you have to look in multiple places to get the full picture of what's going on.
If we can attach a custom form to each issue as we can do today, I want to be able to attach a custom form to each document uploaded so the user can fill up additional information for the document. Hopefully, this can be turned on/off as needed per project or issue.
Description - We would appreciate advance notice of when a new version of the Proof Viewer app is released.Why is this feature important to you - Our users are not able to install the update themselves due to security reasons and the app must be packaged and deployed by our IT department. Without notification, we rely on the users to inform Admin team when a new version has been released which causes a delay in the new version being available to our users.How would you like the feature to work - Our IT and Admin team receives notification which allows them to package and deploy the update proactively so users are not impacted.Current behavior - When a new version of the app is released, users get a pop-up window when they are proofing alerting them to a new version. The pop-up window is persistent and needs to be dismissed multiple times and impacts their ability to work.
This is a pretty simple optimization, but I would love to be able to just click on a smart list and see how many people there are just like in a static list or smart campaign. Just having it appear somewhere in the "Status" tab. Having to click on the "People" tab in a smart list and wait for all the leads/contact information to load when I just need a number seems unnecessary.
Current situation: when releasing assets to my stakeholders, on the Open Summary pane, the comment window (where I tag my stakeholder) appears only when I select I document. Problem/solution: The comment window (where I tag my stakeholder) doesn't appear when I select multiple documents Solution: To have the comment window appearing when I select multiple documents so that I can generate 1 notification (1 link) that includes all the documents on the same Asset Release folder. Is this possible?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
