Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

jlanssie-lnlNew Participant

Make author instace "Preview as Published" navigateableDeclined

Request for Feature Enhancement (RFE) Summary: We would propose to have an out of the box way to always add the "?wcmmode=disabled" url slug to urls inside the author "Preview as published" environment because without it, we experience custom components breaking in the "Preview as Published". If it was always added, the author instance's "Preview as Published" could be fully navigateable for an author, which is good for demo's to stakeholders or business or testing UX flows. Use-case: An author wishes to test or demonstrate a UX flow to stakeholders on the author's "Preview as Published" to include the most recent visual changes. Current/Experienced Behavior: An author clicks a link on a "Preview as Published" page and is redirected to the correct URL, but without the "?wcmmode=disabled". The new page features components that visually break, visually misbehave or do not load content from content fragments.  Improved/Expected Behavior: An author clicks a link on a "Preview as Published" page and is redirected to the correct URL, with the "?wcmmode=disabled". All components on the page render well. The author can gets a perfect visual representation of all components, with the latest changes present. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 6.5.8.0 Customer-name/Organization name: National Lottery Screenshot (if applicable): Code package (if applicable):  

ForgotPassword4TimesNew Participant

Accept tnta values via processing rulesNew

Description -Currently there are two methods to integrate A4T, either via the sdid approach or the data insertion api.The sdid approach is very limited as it has quirks related to first-time visitors. There is also a complete absence of technical guidance or documentation on how to generate an SDID if you are using server-side target on a modern platform that does not support one of the Target SDKs.This is particularly important as the most substantial/performant types of experiments/activities are likely to be run server-side, but server-side analytics lacks feature parity with client-side.The data insertion api approach is very expensive, as it increments an additional server call each time a user has an activity response from Target.  It also introduces significant/unacceptable sequencing issues; either the A4T event arrives before the analytics event, causing misstatements of values related to things like marketing channels or it arrives after the page level hit for which the user actually qualified for the experiment, which requires more complex segmentation.A less expensive and problematic approach would be to enable users to pass the tnta value via context data or an eVar and then map that dimension to tnta within processing rules. This would introduce meaningful flexibility, avoid unnecessary server calls (which is mutually beneficial for clients and Adobe) and mitigate any sequencing issues.Why is this feature important to you -This feature is important as the current A4T implementation choices are limited AND analytics can only support 3 listVars. To be able to analyze users in multiple experiments we need access to the tnta dimensions which behave as listVars.How would you like the feature to work -The tnta dimension would be an option within processing rules. Users would have the ability to map either existing dimensions or context data values to the tnta dimension.Current Behaviour -💢😤

DavidGu1New Participant

Fix Resource Budgeting ToolsNew

Resource budgeting tools are slow to load the larger the data set you're working with. The tool does not appear to be designed to fully support enterprise reporting and doesn't seem to be able to function efficiently with the reality of a larger company's data needs.Improve the efficiency of getting data entered through the project level resource budgeting tool by loading the roles from the resource pool to use in budgeting WITHOUT forcing the massive calculation of data for all available roles. Allow a choice to save the data entry and then run the calculation afterward if a user wants to do this at the project level. It might make more sense for a user to enter data by project but then run the larger planner report for a global look to see which projects need adjusting for which roles.Update the options for the planning tool to allow for retaining history of roles being filled. Right now we see that we lose all budgeted hours for a specific role when the only user gets promoted out of it and before we fill that role again. There are sometimes gaps in filling the same role but we want the reporting data retained instead of deleted.Allow administrative features to let system admins determine if they want to handle budgeting by job role. It would be nice to see the option of entering budgeted hours by job role based on the roles in the resource pool and not the users in the resource pool. the calculation for availability could utilize the current headcount of users with that role rather than the number of users in the resource pool. It's the promotions of users and deactivation of users that starts messing up reporting data.Update the budgeted hour API to include a "last updated" field and ability to detect deleted records to remove.

alyssapurdyNew Participant

Challenge with Folder Location Changing when Working on a Review Task in InboxDeclined

Request for Feature Enhancement (RFE) Summary: We have an challenge with our implementation of Adobe Assets specifically, that when a user is in the system working in a specific folder of the DAM, and then opens an asset via the inbox, when they close the asset, they are taken back to the folder they were originally in, not to the folder of the asset they were just reviewing. Please see below for the steps to recreate, and what we would like to have happen, and why this is a pain point for my company's implementation. This system design has negatively impacted our company because users are uploading their assets with some frequency in the wrong folder, requiring our admins to help get them moved, or deleting the mis-loaded assets and helping the users re-upload the assets. Use-case: A user is working in a specific folder in the DAM, navigates to inbox to complete a review task, and is taken back to the original location when the review task is completed, not the the most recent folder location where they were working on the asset in the review task. Current/Experienced Behavior: 1. A user is working in a folder in the DAM (for example, DAM>content>BusinessA>Images>Birds)2. The user is notified that they have a review task by email or by seeing a new task showing on the inbox icon in the upper right3. The goes to the inbox via the Inbox link in the upper right or link from an email, and opens a review task assigned to them4. The user goes to the Payload, downloads the asset (for review purposes, if an asset is a multi-page PDF or MS file, in order to view and annotate the entire document, it has to be downloaded and uploaded as a new version) from a different folder (e.g. DAM>content>BusinessA>Documents>Brochures), and reviews and annotates it in Adobe Reader or MS application.5. The user is taken to the folder they were working in in step 1. If the user is not observant, they try to upload the asset they were reviewing in step 4 as a new version, but it's in the Images>Birds folder, not in the Documents>Brochures folder, so it's not versioned there, it's created as a new asset in the folder where it's not intended to be. We have confirmed this behavior several times and with our ACS DAM Strategist. We even made sure to navigate to the main screen by deleting all of the URL except the home part of the URL (https://author-yyyy-prod2.adobecqms.net/aem/start.html) between steps 1 and 2 above. Improved/Expected Behavior: 1. A user is working in a folder in the DAM (for example, DAM>content>BusinessA>Images>Birds)2. The user is notified that they have a review task by email or by seeing a new task showing on the inbox icon in the upper right3. The goes to the inbox via the Inbox link in the upper right or link from an email, and opens a review task assigned to them4. The user goes to the Payload, downloads the asset (for review purposes, if an asset is a multi-page PDF or MS file, in order to view and annotate the entire document, it has to be downloaded and uploaded as a new version) from a different folder (e.g. DAM>content>BusinessA>Documents>Brochures), and reviews and annotates it in Adobe Reader or MS application.5. The user is taken to the folder they were working in in step 4 (e.g. DAM>content>BusinessA>Images>Birds), where they most recently interacted with the system and assets. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5, SP9 Customer-name/Organization name: 3M Screenshot (if applicable):   Code package (if applicable):