Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Use-case: Current/Experienced Behavior: Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Prerequisites Node 8.9.0 - https://nodejs.org/dist/latest-v8.x/ Java 1.8 - https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html Maven 3.5.2 - https://archive.apache.org/dist/maven/maven-3/3.5.2/binaries/ AEM 6.4 with Service pack 2 Use the below cmd to create your project- mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=24 -D aemVersion=6.5.0 -D appTitle="My React SPA Site" -D appId="mysitereact" -D groupId="com.demomysite.react" -D frontendModule=react -D includeExamples=y -D includeDispatcherConfig=n Open terminal and navigate to react-app directory and execute “npm install --save-dev webpack webpack-cli” to install Webpack webpack.config.js file need to be created and paste the following code snippet---- const path = require("path"); module.exports = { entry: "./src", output: { filename: "App.js", path: path.resolve(__dirname, "dist") }, module: { rules: [ { test: /\.js$/, exclude: /(node_modules)/, use: { loader: "babel-loader", options: { presets: ["@babel/preset-react"] } }, enforce: "post" }, { test: /\.css$/, loader: "style-loader!css-loader" } ] } }; In project root add .babelrc file and paste the following configuration { "presets": [ [ "@babel/preset-react", { "pragma": "dom", // default pragma is React.createElement "pragmaFrag": "DomFrag", // default is React.Fragment "throwIfNamespace": false // defaults to true } ] ] } Find and open package.json and add the following under scripts "develop": "webpack --mode development" And add the following DevDependencies section "devDependencies": { "@babel/preset-react": "^7.0.0", "babel-loader": "^8.0.5", "webpack": "^4.28.3", "webpack-cli": "^3.3.0" } Run “npm install” and “npm run develop” to build project. A folder named dist and App.js will be under it (if you don’t have any styles) Take the index.html from public folder of your react-app and place it in your web server’s doc root folder. Update the file to include <script src="App.js" type="text/JavaScript"></script> before body tag close You should see your React application work fine in browser without dev server
Request for Feature Enhancement (RFE) Summary: Horizontal breadcrumb navigation option instead of the drop down version that is the current functionality. Use-case: As a global DAM user, I want a horizontal breadcrumb trail on top of the dropdown navigation in Assets > Files like the horizontal breadcrumb in AEM > Navigation so that I can easily see where I am in the navigation. Current/Experienced Behavior: Improved/Expected Behavior: Situated in the middle of the rail, and always showing the description of the currently selected item, the breadcrumbs display a drop-down listing the levels of the hierarchy of the currently selected item. Click on an entry to jump to that location. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Accenture Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: By having the ability to make fields in inbox notifications non-editable, it will make the notification more secure and can act more as a reference for details and assignments. Use-case: As a user, I want the ability to make fields in the inbox notification to be non-editable so that users won't be able to change the details of the notification. Current/Experienced Behavior: Currently, all fields in the inbox notifications can be edited by multiple users and this can potentially lead to confusion for users. Users can change the content path, assignee, description, priority, etc. Improved/Expected Behavior: Ability to make the fields in the inbox notification to be non-editable for more security and dependability. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable): Inbox notification fields mentioned above: Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Add dir attribute dropdown feature in page properties dialog Use-case: To enable RTL support for arabic sites. Current/Experienced Behavior: Currently there is no dir attribute in HTML element, and also we have written a sling model to dynamically choose the dir attribute based on the url/language choosen. Improved/Expected Behavior: Need to have a dropdown for dir attributes below the language dropdown in 'Advanced' tab of page properties. Also dir="rtl" should automatically be added if we translate our contents (machine translation) from any other language to arabic. Environment Details (AEM version/service pack, any other specifics if applicable): AEM aaCS Customer-name/Organization name: Born Group commerce private ltd. Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: While some assets may satisfy the search requirements of a Smart Collection, they may not be wanted by the user that created the Smart Collection. Use-case: As a user, I want to be able to exclude certain assets from a Smart Collection. Current/Experienced Behavior: Users must make manual Collections or allow unwanted assets in Smart Collections. Improved/Expected Behavior: The option to exclude specific assets from a Smart Collection. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Users would like to 1-click to their saved Collections. Use-case: As an AEM user, I only want to easily see MY Collections And Smart Collections. Current/Experienced Behavior: Manual/visual search of Collections. Improved/Expected Behavior: 1-click filter for self created Collections. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enable page versioning from page editor UI Use-case: A content author is making changes to a page and would like to create a version with its current state before proceeding with editing Current/Experienced Behavior: One should go to Sites navigation UI, switch the left toolbar to Timeline, create the version and return to the editor Improved/Expected Behavior: It is possible to create the version without leaving the editor. I see two ways how it could look: 1) there is a new "Create version" item in the "Page information dropdown"; 2) in "Page information" dropdown, when you select "Start workflow", there is an out-of-the box "Create page" workflow model you can pick. Please see pictures for both options attached. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP8 Customer-name/Organization name: Veeam Software Screenshot (if applicable): Option 1: Option 2: Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Online compaction not that effective and observed repository growth and which is causing slowness in author. Adobe suggesting to run offline compaction. This offline compaction is very unpredictable process, not sure how long it might take. This idea request is to know if there is any way we estimate how much time it will take before we start offline compaction? Use-case: Looking for feasibility of developing something which calculate estimate time offline compaction will take. Current/Experienced Behavior: No way to calculate how long that process take. Improved/Expected Behavior: If this is possible, we can give clear timeline to business about downtime that needed to run offline compaction and it's very very helpful. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.7 Customer-name/Organization name: Hershey's Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Have seperation of duties in the roles so that production pipeline execution can be limited to Program or Business owner roles. Use-case: As per https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/requirements/role-based-permissions.html?lang=en , anyone in the roles Business owner, Program Manager or Deployment Manager can start / approve the production pipeline execution in Cloud Manager. It would be a very beneficial control to have settings limiting production approval to business or program roles as this will allow a more stricter approval workflow to help regulate production pipelines . A deployment manager role that manages all the day to day environment deployments that doesn’t have to go through a business approval makes sense for lower environments. But for production it would be great if this was limited to a Business owner or Program manager. Current/Experienced Behavior: All 3 roles Business owner, Program Manager or Deployment Manager can schedule and approve deployment to production. Improved/Expected Behavior: For production it would be great if approval was limited to Business owner or Program manager role. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.8 (AMS) Customer-name/Organization name: Sallie Mae Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Would like an interface to the Adobe Experience Fragment Export via IMS (enhancement to the export/serve/status of Fragment Export) Use-case: Many orgs have limited bandwidth to troubleshoot the destination of Experience Fragments as they are exported to Target (i.e. workspace destination). Development development team updates the experience fragment incorrectly or a bad config gets installed via the build or is misconfigured via IMS in some way, it would be useful to see the ultimate destination (and potentially where the XF is embedded by Target if possible) within some kind of reporting interface. Current/Experienced Behavior: No visibility into Experience Fragment destination our serving after export Improved/Expected Behavior: Some level of visibility into Experience Fragment "Journey" Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 Customer-name/Organization name: Large Medical Organization Based in Northern California Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Asset Picker should not interrupt user typing Use-case: Searching assets by typing search terms in Asset Picker Current/Experienced Behavior: Asset Picker trims tailing space while user is typing. It is very difficult to type in more than one word in the search input box Improved/Expected Behavior: User typing is not interrupted. Tailing space could be removed when user hits enter key, clicks the search icon, or the input box loses focus. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP7 Customer-name/Organization name: Loblaw Inc, Ltd. Screenshot (if applicable): Code package (if applicable):
Currently, there is no option in AEM collection details UI to add individual assets from one collection to another collection. However, It does have have a feature add entire asset collection to another collection, but not individual assets inside that collection. It would be beneficial to user to combining assets from one multiple collections and perform actions on those assets Thanks,Vineeth
Most of the documentation is hot garbage, and since Adobe takes AEM and makes it the one true source for information, Can we improve the documentation? Almost all of the walkthroughs are rarely show coding through the steps or just skip over it and copy and paste. My mentor always said if the documentation is garbage then the product probably is too....
Currently, editor for the Content Fragments, Metadata Schemas and Folder Metadata Schemas does not have a documented way to add custom components into the editor. This is incredibly restrictive when you want to do things which can be done in standard AEM Dialogs such as:Drive Dropdowns off a list of valuesCreate Multi / Multi-Composite FieldsCustomize Field behaviorIf there was a documented way to extend / customize the fields, this would allow implementors to better meet their business needs.
Description -AEP Segments need to have a way to organize them into folder structure for easy use and maintenance by different Business teams. Why is this feature important to you -Easier to identify and manage different types of segments.How would you like the feature to work -Ability to create folders and then create segments, somewhat similar to campaign workflows in Adobe Campaign. Current Behaviour -All segments show up in the same page.
I hate that the only way to use the Kanban board in WorkFront is by creating an Agile team, as its a great visual management tool that adds value to Traditional teams as well. I'd like to see Workfront also offer "Kanban" as a standard view that can be applied across lists by any user, regardless of team type. e.g. you change the view to Kanban on any list and see the work item as cards (instead of rows) with the columns representing either status, progress status/condition or milestones. Would also love if you could choose whether to show parent tasks only or child tasks only. This type of view option exists on a lot of other similar products include MS Team Planner and Smartsheets. Our users were disappointed that they could not have a Kanban view when we switched to Workfront (as setting up Agile Teams in WF doesnt make sense for us since the rest of the settings/functionality that goes also with a WF Agile Team doesnt align with how we work).
It would be great to have the ability to bulk edit the Default Proof Role and Default Email Alerts for all users within the proof settings. Currently you have to manually go in 1 by 1 to change them individually.
It would be great if after project conversion, if an update is made at the issue level it directly feeds to the project level as well (or essentially becomes 1 Update tab). A lot of times, our submitters are going back to the issue level and writing an update and our team is missing it/confused where it is because we are now working in the Project.
I would be helpful if upon completion of a project, the hours logged automatically update the planned hours when saved as a template.
It would be nice to have a personal kanban or scrum board for tasks/issues in the home view. We've had users who have used products like Asana and have asked about that functionality quite regularly for individual tasks.
Allow a custom field label customizable by custom form. For example, currently in our Education instance there are four custom fields about campus - Campus, Desired campus, MCASOM Campus Support, Select Campus. I'm creating a new form where we like the name to be "Student Home Campus" The Select Campus field has the selection I need, but if I change the label to meet the needs of the form it will change it for any other forms it's on. We are basically re-inventing the wheel each time when we could reduce the number of fields needed.
There was a new feature added that when an update is being made on a task, the user can also change the percentage complete at the same time. It would be nice when the percentage complete is changed, it is then part of the running updates that show. If it went from 0 -20 percent and the user hits save. then in the running updates, it would show "user changed percentage to 20 percent.
Within Adobe Launch, we can have several users go in and contribute in the creation of rules, data elements, custom code in the extensions (like Adobe Analytics). Can we add in the name of the person who made the changes in each version. currently - we know when the last version was saved, but we do not know who made the change. This will help when we need more information on why something was changed.
In DTM, there are two images used in the Status column - a check or a clock with a blue circle - that let me easily know if an item has been modified since its last push to production. This Status image is used across the board on rules, data elements and tools in DTM.In Launch, this concept does not seem to exist.I really like and utilize this feature in DTM. Could this feature please be applied to Launch too?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
