Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary: Currently when you use Manage Publication functionality to publish/unpublish pages, the timeline does NOT provide information about the target so that you can not see to which target it was published/unpublished. And instead of "Page published" entry like in AEM 6.5.16 on Prem only workflow steps are visible which is confusing. Use-case: Timeline should give the possibility the see what happened to page and it is important to know which target was published. If you have pages which are frequently published a clear overview is needed of editors. Current/Experienced Behavior: Missing information about publishing target. Listing of workflow steps for publication which are confusing. Improved/Expected Behavior: Provide proper information about the target to which the page has been published to. Use clear entries for publication like "Page published to Publish" or "Page published to Preview" instead of listing connected workflow steps

Request for Feature Enhancement (RFE) Summary: Open "Reveal in Sites" and "Reveal in Assets" links in the new browser tab automatically Use-case: AEM author users needs to open several Page's or Asset's language copies at the same time, so that they can compare the content on different locales. Current/Experienced Behavior: "Reveal in Sites" link is not opened in the new browser Tab even automatically. "Reveal in Sites" link is not opened in the new browser Tab even if I press "cntrl" key on the keyboard. Improved/Expected Behavior: "Reveal in Sites" link is always opened in the new browser Tab even (without pressing "cntrl" key on the keyboard). Environment Details (AEM version/service pack, any other specifics if applicable): Tested on the clean AEM 6.5.19 (without our application) Oracle JDK 11.0.20 Customer-name/Organization name: Veeam Software Screenshot (if applicable): Click on the Page or Asset Go to the "References", then "Language copies" Select a langua

Request for Feature Enhancement (RFE) Summary: Enhancement request to add 2 uicontrol elements when a menuscascase is inserted, instead of one. Use-case: Insert menucascade then insert another uicontrol to achive the end goal. Current/Experienced Behavior: When a menucascade is inserted, a single uicontrol is added. Improved/Expected Behavior: When a manucascade is inserted, 2 uicontrols are added. At the preview output, a caret is placed between the two uicontrols. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18SP, AEM Guides 4.3 Customer-name/Organization name: Olu Oladipo / Verizon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEMAACS Enhancement Request to automate reports sending to other AEM Users Use-case: In other Adobe Products (ACS,etc.) there is the ability to send reports to other users with a login. Would like this automated functionality in AEMAACS. When you  Current/Experienced Behavior: Under Tools -> Assets -> Reports -> Create -> Upload (Report of uploaded assets) Unable to automate report to send to other AEM users. I realize this is currently not a feature that I would like included a future feature request. Improved/Expected Behavior: automate reports sending Environment Details (AEM version/service pack, any other specifics if applicable): AEMAACS Customer-name/Organization name: Epsilon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: From Guides, add an option to open dita topics and maps in Source view. Use-case: Navigate to a dita topic or map in Guides; click Options; select 'Edit Source' or 'Check out in Source'. Current/Experienced Behavior: Dita topics and maps are opened in Author view. Improved/Expected Behavior: Provide an option to open dita topics and maps in Source view. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18,  AEM Guides 4.3 Customer-name/Organization name: Olu Oladipo / Verizon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Ask for a confirmation while moving the nodes in CRX/de Use-case: When a node is moved in CRX/de, it will never ask for confirmation. This instead saves the node in the new location. This may have got moved accidentally while trying to open or select any nodes.  Current/Experienced Behavior: Save the move without asking any confirmation. Improved/Expected Behavior: Show a confirmation box before saving the changes. Environment Details (AEM version/service pack, any other specifics if applicable): All versions of AEM Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Multiple requirements arise where table component needs to be created, where it needs to be extendable as data increases or reduces. There needs to be an OOTB component which can have these features Use-case: OOTB Table component to be created with auto-expandable feature Current/Experienced Behavior: No OOTB table component exists Improved/Expected Behavior: Having an auto-expandable table component improves a lot of effort. Multiple variations of simple table, auto-expandable can be implemented Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: NA Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEM VSCode sample tasks.json Use-case: Ease start/stop/logs navigation inside popular editor Current/Experienced Behavior: Double click jar and customize links or crx-quickstart/bin/scripts Improved/Expected Behavior: Developer productivity within editor workbench Environment Details (AEM version/service pack, any other specifics if applicable): AEM 65sp7 archetype 47 org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \ -D archetypeGroupId=com.adobe.aem \ -D archetypeArtifactId=aem-project-archetype \ -D archetypeVersion=47 \ -D appTitle="SP17 TPL47 ReactJS Example Site Project" \ Customer-name/Organization name: Bob Kranson/Perficient Screenshot (if applicable):   Code package (if applicable): /appid/.vscode/tasks.json

Request for Feature Enhancement (RFE) Summary: In AEMaaCS the Manage Publication function does not create a version if editor publishes a page. This is a significant change to AEM onPREM which is nowhere documented. The only way the get the known functionality back is to create an own overlay. This is actually bad solution in regards to future Cloud updates and efforts to maintain overlay. Use-case: Editors want to have backup from the status of pages when they were published. This is also to legal requirements partly. They are used to have this as it was standard behavior in AEM! Current/Experienced Behavior: Using Manage Publication does not create a version. Improved/Expected Behavior: Using Manage Publication (to publish) should create a version. Maybe the ootb workflow "Publish Content Tree" can be made configurable in regards to version creation so that each customer can decide if he needs this or not. Environment Details (AEM version/service pack, any other specifics

Request for Feature Enhancement (RFE) Summary: Field Text Component in AEM Forms Adaptive Forms allows to set rich text attributes, applying custom CSS styles or through Style mode UI: when the form is submitted and Document of Record is generated, all the styles are lost and the Text Field stores only plain texts. The request is to incorporate in DoR all the styles applied to the Adaptive Forms in the UI.  Use-case: Save rich PDF documents DoR similar to XDP forms with  Text Fields created in Adobe Forms Designer  Current/Experienced Behavior: only Plain Text in DoR Improved/Expected Behavior: Rich text saved in DoR Environment Details (AEM version/service pack, any other specifics if applicable): AEM Forms 6.5 SP19 or AEM Form CS Customer-name/Organization name: Unicredit Group Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Reporting capability for activity tab in cloud manager Use-case: We want to understand the number of times the prod pipeline is triggered and who triggered it in a report so that we can use it for our internal auditing purposes and security reasons. Current/Experienced Behavior: Cannot download any report Improved/Expected Behavior: Able to download report of Pipelines from Activity tab Environment Details (AEM version/service pack, any other specifics if applicable): Production - AEM Assets Customer-name/Organization name: Phillips Morris International/Philip Morris International Management SA Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEM as Cloud Service CDN log forwarding to Splunk Use-case: Currently, CDN logs for AEMaaCS are not forwarded to Splunk. Having the CDN logs in Splunk will enable customers to create reports on Cache Hit Ratio and other metrics that the CDN logs provide. Current/Experienced Behavior: Currently, CDN logs for AEMaaCS are not forwarded to Splunk and custom ELK solution has to be setup.  Improved/Expected Behavior: CDN logs should be forwarded to Splunk which is the Adobe Standard for AEM logs. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service latest release Customer-name/Organization name: Abbott Screenshot (if applicable): N/A Code package (if applicable): N/A

Request for Feature Enhancement (RFE) Summary: During Performance Testing, it sometimes becomes important to be aware of memory leak and how resources are utilized Use-case: Would like to prevent autoscale and have visibility into single server resource utilization of the instance to identify to identify incorrect usage in code. Current/Experienced Behavior: No clear view of the code quality in terms of resource utilization. Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEMaacS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The content sync via CTT tool overwrites the existing content folder in AEMaaCS server.  Use-case: Consider a client has 400+ sites, which are being migrated in batches. It can have shared folders thus are actively edited both on AEM 6.4 and AEMaaCS.A regular sync from AEM 6.4 to AEMaaCS would be needed until all sites are migrated Current/Experienced Behavior: CTT tool overwrites the content in AEMaaCS Improved/Expected Behavior: CTT tool should be able to execute Delta migration Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS & 6.4 Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):