Product Communities

Description - On a custom form, checkboxes, radio buttons, and dropdowns all have an option to "Hide Choice". This feature allows admins to hide specific choices on the form. For instance, a field called "Pets" might have 3 choices: "Bird", "Cat", "Dog". By selecting the "Hide Choice" option next to the choice "Cat", an admin can hide that choice from displaying to users of the form. However, hiding the choice of "Cat" will hide it on ALL forms that use the "Pets" field. It would be beneficial to have the hidden choices be specific to the form where the setting is changed, rather than on all forms that reference that field.Why is this feature important to you - Currently, if the same field is used on different forms, that field will display the same choices on all forms. Often a form might be designed with a specific audience in mind. Being able to customize the field choices for the specific audience would make the form more user-friendly, while also saving the admin time (by not havi

Description -I would like the ability to change retry parameters directly in O365 modules, including number of retries and period of time between retries.Why is this feature important to you -Currently, adding this type of error handling involves adding at least two modules per retry, becoming large and difficult to manage very quickly, especially if I need to make changes to the module's behaviour and then copy this multiple times in the case there is a connection error while making the request.How would you like the feature to work -Have retry behaviour parameters built into the existing module, even under a form of 'advanced settings'. Alternatively, Adobe could have pre-configured settings for this, to make the current module operation more robust, without any more visible complexity for users.Current Behaviour -It isn't uncommon, even in fully working systems, for Microsoft Graph API to return 504 errors when sending requests. Especially if you are doing operations in excel across

Request for Feature Enhancement (RFE) Summary: Developers should have a read-only view of CRX/DE for debugging purposes Use-case: Debug deployment issues, check paths and properties Current/Experienced Behavior: Currently AEMaaCS has repository browser but it has limitations - It is sometimes not showing few paths/folders even though it is there in author/publisher. It requires separate access via developer console and not all developers may have access to that. Improved/Expected Behavior: Simplifies read-only view of crx/de is a better way to provide access to author and publish repository. Developers should even have this in production so that issue resolution for production content issues or code deployment issues can be expedited. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS author and publish environments Customer-name/Organization name: GSPANN Technologies Screenshot (if applicable):   Code package (if applicable

Description - Adobe Analytics x ACS Integration Monitor  Why is this feature important to you - This would provide better reporting accuracy and allow us to know when there is an issue so that we can work to address it. How would you like the feature to work - A monitor would feature a dashboard that shows:1) Status of the integration2) Alerts users to reporting metric discrepancies3) Account and/or report suite connection issues4) ACS technical workflow errors:     - Share KPIs with Adobe Analytics (kpiSharing)     - KPIs Reconciliation with Adobe Analytics (kpiReconciliation)5) Campaign metrics not being updated in Analytics.  Current Behaviour - No such monitor exists

Hi,  It would be very helpful to be able to edit the proof decisions for groups and/or automated workflow templates.  Currently, these can only be edited for the whole instance which is very inconvenient since groups can have different processes or ways of working.    

Description - Add a comment block/section to each filter condition.Why is this feature important to you - It would provide clarity when looking at a filter with many different conditions.How would you like the feature to work - An optional comment block be added to each condition within a filter. Building off this, an option to also toggle them on or off within each individual filter as some don't have many conditions.Current Behavior - Filter has a label that generally describes filter behavior but not each individual condition.

Hello - I have created a Journal Entry report and it's almost perfect for our needs. The only issue we ran into is that there is no button on the Details tab to export the raw data into an Excel file or CSV. Any assistance with this?

Request for Feature Enhancement (RFE) Summary: I know this was previously available as part of the AEM social package and then unsupported with the move to AEMaaCS, but our organization (and I believe most others as well) would greatly benefit from using a native 5-star rating system on our assets, interactive from the card view and sortable in the list view. Use-case: Particularly with our photography assets, we have a process in place to rank images on a 5-point scale from Best to Worst, which directly translates into how people are discovering and using these assets in other marketing materials. Having the stars on the card and properties view--both to actually apply the rating as well as to immediately have the visual cue (like how it's managed in Adobe Bridge)--would be extremely helpful, and would create the ability to filter out lower rankings, sorting assets in the list view according to ranking, etc. It would also be a very intuitive, user-friendly enhancement as a star-r

Description -  We would like for there to be an external license level that does not get access to any systemwide shared objects. Why is this feature important to you -  We have the need to give external users, like vendors, access to the system so that they can access projects.  However, any license we use gives them access to systemwide shared objects.   These systemwide shared objects make sense internally (all users need access), but out external users should not have access to these objects. How would you like the feature to work -  Either create a new license level that limits systemwide shared objects, or a settings on licenses where you can limit system wide shared objects. Current Behaviour -  all license types get access to systemwide shared objects.

Request for Feature Enhancement (RFE) Summary: AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property. Use-case: AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property. Current/Experienced Behavior: Asset are allowed to publish wit

Description - When exporting data into a CSV, I would love there to be included a URL link to the workspace where the data populated. It would also be nice when exported if it autosaved or ask the user if they wanted to save their workspace view.Why is this feature important to you - This would help when people send me data, I could tell where they got it from and look at how they pulled it. I would also remember the exact workspace I used to create a graph and it would be easy to update.How would you like the feature to work - Just add a line at the top of the download that has the url.Current Behaviour - I manually copy and paste into the excel file if needed.

Today, when you query Marketo's REST API to see the structure of each Marketo activity, you'll notice that Activity ID 37 (Delete Lead) has the following structure:  { "id":37, "name":"Delete Lead", "description":"Delete lead from Marketo database", "primaryAttribute":{ "name":"Lead ID", "dataType":"integer" }, "attributes":[ { "name":"Remove from CRM", "dataType":"boolean" }, { "name":"API Method Name", "dataType":"string" }, { "name":"Modifying User", "dataType":"string" }, { "name":"Request Id", "dataType":"string" } ] }However, the attributes described are not actually returned when retrieving Delete Lead activities from the API; there is no data, and as a result "Remove Fr

It's a pain to check whether someone already started a discussion or submitted an idea.There is no way to search *within* Ideas or Discussions. Can you please add this (would reduce duplicates/noise!)

It would be great if you could change the Landing page fallback on asset expiration. A common use case would be a webinar registration page that is set to expire after the webinar has taken place and then redirect to a page that tells the person that registration is no longer possible.

Request for Feature Enhancement (RFE) Summary: Show an indicator (small lock symbol) also within the List and Column View to give and editor to see at one glance which pages are locked. Use-case: As an editor I want to see "outside" which pages are locked and from whom. E.g. when I do a publish with children this will fail if one child page is locked because version creation is not possible in that case. Current/Experienced Behavior: Only in Card View you have this small symbol which indicates that page is locked. On hover you just get the information "Locked" without the user who is locking it! Improved/Expected Behavior: In every view of the Sites console the information if a page is locked should be displayed. In addition to that the information which user locked the page should be available (on hover for Card and List and as text item in Column view. In the old Classic UI this was in - not sure why in TUI is has been removed. Environment Details (AEM version/service pa

Request for Feature Enhancement (RFE) Summary: Remove limitation how many columns can be shown in the List View. Use-case: As an editor I want to see despite the standard columns also ones showing e.g. translation status or analytics data at on glance. I want to be flexible which columns I want to see according to my field of works. Current/Experienced Behavior: Currently you can only select up to 7 columns which should be shown in the list view. But there are a lot of more columns which could display additional information. So, you can't have all information at one glance or even an additional column to be shown apart from the standard ones. Improved/Expected Behavior: Remove limitation and let user decide how many columns he wants to be displayed depending on the use case he has. We have responsive UI, this should be no problem! Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Scree

Request for Feature Enhancement (RFE) Summary: Cloud Manager Deployment: Add emergency production deployment pipeline Use-case: LGE.com is trying to roll back the deployment after a successful production deployment. Currently, the only way to roll back is to re-deploy the code in Cloud Manager, which takes 2 to 3 hours. Given that they are supporting 24 websites (with more to come in the future), they need to reduce the build time for any rollback operations. The best way to achieve this is to enable re-deployment using an earlier stable built image. Current/Experienced Behavior: The production deployment is completed. After the deployment, the customer discovered blocker issues on one of the 24 websites. They decided to roll back the deployment. They reverted the change that caused the issue and pushed the revised changes to Cloud Manager. They restarted the Stage/Prod build, which took 2 to 3 hours. The customer is trying to minimize this 2 to 3-hour downtime as much as

Request for Feature Enhancement (RFE) Summary: Sort the list of groups in the User Profile alphabetically. Use-case: As an administrator I want efficiently check to which groups a specific user is assigned to. Current/Experienced Behavior: After opening the user profile and selecting the tab "Groups", the list below the headline "Groups that this user is a member of" is not sorted, it just displays the group names randomly. You need to scroll through all the list to check if a certain group is in. Improved/Expected Behavior: The list below the headline "Groups that this user is a member of" should be ordered alphabetically to easily get an overview! 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: When using the new AEM view, the default columns that are available to users in the Configurable Columns settings should be customizable in two ways:1. Admins should be able to add/remove metadata fields (especially custom metadata fields) to the overall list available to users.2. Users should be able to select attributes relevant to their workflow experience and save the configuration. Note: Users being able to save/load multiple configurations for different workflows would be nice. Use-case: Current fields offered in Configurable Columns are limited and not applicable to many of our users. The ability for admins to offer custom metadata in these columns would eliminate bad habits by decreasing the need for users to include these values in asset file names in order to see them easily. Current/Experienced Behavior: Current metadata available to view in Configurable Columns is locked to 9 default values. Improved/Expected Behavio

Request for Feature Enhancement (RFE) Summary: Pickers must remember their last location and start from there  Use-case: Our editors create pages on specific topics and upload assets related to that topic. They very often upload the assets into the same folder to have everything in one place. Then they start to build a page and add the assets to the page.  Current/Experienced Behavior: For the first image asset:  1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Confirm   For the second image asset: 1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Confirm   ... repeat for each asset Improved/Expected Behavior: For the first image asset:   1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Co

Request for Feature Enhancement (RFE) Summary: Introduce a tile where editors can go to see their 15 recently edited pages, assets, experience fragments -etc. incl. links to them and their parent folders. Use-case: Our editors have a newsroom culture. They must quickly put content out there. They can get interrupted to do another task and continue later.  Current/Experienced Behavior: Currently, they just have the option to open all pages, assets -etc. one by one using the various locations in AEM and continue work then. Improved/Expected Behavior: In future they could just go to the Recently Used and re-open all their work from within one single place. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: VERLAG DES ÖGB GMBH Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Need access to old Blue environment after Blue/Green switch Use-case: To evaluate roll-back decision based on the issues found after Blue/Green switch we need to be able to verify issue is introduced due to the change, or existing issue. Current/Experienced Behavior: Currently, old Blue environment is only accessible by Adobe, and not integrated with the rest of the systems. Improved/Expected Behavior: Instead of putting the old Blue environment away, place them into the Green Load-Balancer, so that Green URL can be used after the switch. Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager for AMS deployment Customer-name/Organization name: Go Endo Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add Save as Version to Page Information menu Use-case: Many of our users miss a saving button. We don't promote that. Their need is to: Create page Modify it to their liking Save the page once they reached a "milestone" Colleagues then publish the "milestone" version or use it for approval The main editor continues working on the page Currently, the main editor must leave the page editor, go the Content Tree and create a version from there. They wish to create a version from within the page editor. Current/Experienced Behavior: The menu is not existant yet.   Currently: User must close the page editor User goes to location of page User selects page User switches to the Timeline sidebar User clicks the three dots at the bottom (see screenshot) User clicks Save as Version User fills in Label User fills in Comment User clicks Create System saves Version Improved/Expected Behavior: User clicks Page Information menu (see

Request for Feature Enhancement (RFE) Summary: Add a column with path (/content/...) to the search result list in Sites Console. Use-case: As an editor I want to search for pages which contain a special keyword in the name and/or title. In the Sites console I use the search functionality and enter my keyword to find those pages. Current/Experienced Behavior: The search result contain name and title of the pages (and also other information) but the important information where the pages are located is NOT visible - there is no column or information which is displayed via mouse over. So, I need to open each search result to get to know about location - this is not efficient! Improved/Expected Behavior: Have a column with a path available so that editor sees at on glance the location information Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code pa

Request for Feature Enhancement (RFE) Summary: When text is highlighted (or selected) in the Author view of the content. fragment editor, it would be ideal to see the same highlighted info in Source view. Use-case: 1. In the content fragment editor Author view, select or highlight a link or sentence.2. Go to Source view; the same piece of information should also be highlighted or selected. Current/Experienced Behavior: Text selected in Author view is not selected in Source view Improved/Expected Behavior: Text selected in Author view is also selected in Source view and vice versa Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.19.0 Customer-name/Organization name: Verizon Screenshot (if applicable):   Code package (if applicable):