It would be nice if we didn't have to create 3 copies of each forms, so that when a form is filled out during a queue, the data in the form automatically carries over when the issue it creates is converted to a task or project. Currently, we have to create 3 versions (issue/task/project) of each form, and then the supervisor doing the conversion/assignment of an issue to a staff member, has to ensure they are adding the task or project version of the form when they convert that issue and assign the task, so that the data the person input during the queue process isn't lost.
Currently, group admins aren't able to assign layout templates to a role or team. They can do it by user and group only. This feature is important to allow group admins to use this functionality to manage layouts by roles or team in the group they support. It would be ideal to work very similar to how it does for system admins.
Description - We wish to be able to create a table and line chart that contains a break-down by day which includes metrics to look back at the unique visitors for the past 30 days and 365 days, as well as including a user stickiness metric which will be defined as MAU/YAU. For example: Why is this feature important to you - Active users indicate that people are interacting with our app/website. Determining the number of active users over time helps us with assessing the effectiveness of our marketing campaigns and the customer experience.How would you like the feature to work - Out of the box Active User metrics (DAU, MAU [rolling 30 days], YAU [rolling 365 days]); Out of the box user stickiness metrics (DAU/MAU; DAU/WAU, WAU/MAU, MAU/YAU); Out of the box Workspace template that has the key active user and stickiness metrics trended over time; Ability to create custom active user metrics based on custom time frames - including rolling amounts and custom user stickiness metrics with the ability to trend per day based on the rolling amount. Current Behaviour - While we can use the Unique Visitor metric broken down by one of the out of the box date date breakdowns, it seems that it isn't possible to calculate the active users for a rolling date range, for example rolling 30 days up to and including the date that the UVs is broken up by. Trying to achieve this via the Cumulative Average Function doesn't dedupe Visitors that revisit the website within the same period.
In Adobe Launch / Tags I want to have a full-text search for code and/or notes across all available properties to quickly identify if a specific code snippet / keyword is used anywhere. At the moment, search is only available per property.Having a full-text search across all properties would dramatically decrease the time required to find relevant rules/code. The full-text search should cover: - custom code- rule names- data elements- extensions- notes- library name- modified by- property name
Description -In the past, there was the capability to select "Private to my company" in the side panel "Summary" view of an update. That was removed in the latest release.Why is this feature important to you - Our team uses "private to my company" frequently when communicating in Workfront. Having this capability in this view is was an easier and quicker user experience.How would you like the feature to work - Similar to how it was prior to this recent release.Current Behaviour - The option is no longer available. Nerw comment threads started in this view are viewable to all.
Description - Add more default system fields to the setting of the portfolio optimization tool. Why is this feature important to you - I need to be able to show particular projects fields and be able to filter by project fields too, since each field represents a special project characteristic. How would you like the feature to work - I want to be able to show particular projects fields and be able to filter by project fields too, to present/filter special project characteristics. Current Behaviour - Default fields that are available to show on the page through the setting are very limited and I need to create calculated custom fields of the default fields to show in the tool which is extremely redundant and needless since the field already exists but is just not accessible through the tool. Also, filters that can be set on the page are very limiting and only work on status.
Description - It would be great to be able to reorder the columns order in the filter area. Why is this feature important to you - Sometimes we need to reorder the columns in the view. How would you like the feature to work - When in the portfolio optimization tool, I would like to be able to reorder the columns in the view from the settings\filter area without having to delete all the columns and add them again in the order that I wish. Current Behaviour - I am aware that I can drag and drop columns in the order I wish; however, every time I do that and I add a new column from the settings the order is reset to what it shows in the setting and there is no way for me to reorder them in the settings except if I delete them all and add them again in the order I wish. This is very time consuming and honestly does not make sense why it is programmed this way.
We would like to have the option to color code cards on a Board, similar to how we can apply conditional formatting to tasks in the List view of a project. Having this option would allow our users to quickly see task statuses, categories, etc. without having to read the card text. It could work similarly to how conditional formatting is applied in the List view, by having the option to apply a specific "view" to the board overall.
As a technical solution provider, I would like to provide detailed information on where Marketo assets are stored in instances where users have deployed workspaces. While Marketo's REST API offers string labels for workspaces on most of its calls, this is inconsistent. Calling a form by ID for details results in workspaceId being returned in lieu of the workspace name; however, there is no call to associate a workspace's ID to its in-platform label. Is it possible to update this call to act like other Assets so the workspace name is retrieved as a string instead?
Request for Feature Enhancement (RFE) Summary: In the Adobe SaaS platform, product detail and recipe detail pages are implemented using the CIF framework, meaning there are no physical pages for recipes and products. The current issue is the inability to identify internal references to specific recipe detail and product detail pages. Use-case: When we try to unpublish SaaS says there are Referenced pages but does not give the list of referenced pages, this is a serious limitation. This feature existed on the previous D2 platform. In Unilever platform some brands have over 800 pages and webmasters keep adding and removing pages on a very regular basis. There are many pages where Product URLS are also referred. Whenever a page or product is deleted or removed we do add 301 redirects. If there is an internal link if we don’t update those links then when user clicks on the link it redirects a new page url, This is being flagged by SEO error. Before unpublish a page the System is showing error but it is not showing which pages have reference and we have no way of knowing and it results in SEO ranking. In D2 the PDP Pages were published as pages and we used to unpublish before deleting. In SaaS there is no PDP page unpublish as we don't have any physical pages for recipe and products , hence when a PDP is deleted or renamed we have no way of knowing. Current/Experienced Behavior: Currently we get notification that there is a reference for a page but the list of references are not provided Improved/Expected Behavior: Need a way to identify the internal references for a product and recipe detail page. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release :2024.6.16971.20240628T122619Z Customer-name/Organization name: Unilever Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Currently we do not have any end point from where we can get all details of the article data .A few brands use the search api endpoints to fetch article data for a brand-locale but that only gives limited data ( title , body text , url ) .Currently we have systems like AIBA which use article data to train their models to generate dynamic recommendations . To do so we need some end point from article which when hit , directly provides all data in the body content of the article Use-case: A structured data feed with a periodic synchronization enables AiBA recommendation engine and AiBA LLM engine capability to have latest content and avoid any incorrect recommendations and also avoid a manual process for feeding the latest updates in article content.Other initiatives currently being discussed for LLM and AI engine revamp may also benefit from this implementation. Current/Experienced Behavior: Currently there is no provision in the product for exposure of content feed outside AEM. The engineering team should review and implement this based on the priority for future releases. Improved/Expected Behavior: We need some end point from article which when hit , directly provides all data in the body content of the article Environment Details (AEM version/service pack, any other specifics if applicable): AEM release 2024.6.16971.20240628T122619Z Customer-name/Organization name: Unilever Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Implementation of global find and replace functionality on TouchUI (AEMasCS) Use-case: Globally search & replace contents to helps during situation incorrect migration, Batch modification of content, clean up junk data injected from various Adblock browser plugins. Current/Experienced Behavior: Not Implemented in AEMasCS but this feature was there in classic UI. AEM 6.5(previous version) Improved/Expected Behavior: Globally search & replace contents on AEMasCS Environment Details (AEM version/service pack, any other specifics if applicable): AEMasCS Customer-name/Organization name: Raja.T Screenshot (if applicable): Screenshot of AEM 6.5(previous version) Code package (if applicable): com.day.cq.wcm.core com.day.cq.wcm.core.impl.servlets Servlet Name: FindReplaceServlet.java
Request for Feature Enhancement (RFE) Summary: Implementation of Private Folder for AEM Pages. Use-case: We want to enable our Stakeholders option to assign privileges (read, edit) by their own. Think of it as a secondary ACL management, which is for individual stakeholders and is completely managed by them, for that we are looking for Private Folder option similar to AEM Assets. Current/Experienced Behavior: Private Folder feature only exists for Assets. Improved/Expected Behavior: Option for creation of Private Folder in AEM Pages. Environment Details (AEM version/service pack, any other specifics if applicable): AMS AEM (6.5.17.0) Customer-name/Organization name: Bhuwan Bhaskar Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Fail AEM cloud build if any critical or major code severity found Use-case: There should be a checkbox to enable or disable to fail the build if code severity found to keep code vernability free Current/Experienced Behavior: Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
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: 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):
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.
