Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

David_Gallaghe2
David_Gallaghe2New Participant

Let's Talk about Lists -- I would love a List Import Queue (wireframe included)New

We ran into issues with list imports the other day that was due to a cluster issue in the sydney datacenter where our instance is hosted. We had 4 lists that were "being imported" and never finished even after 4 days. This got me thinking, we have a Campaign Queue, why not have a List Import Queue/History... This could get cumbersome with how some of us use lists (campaign Triggering) but if it is either tabbed or categorized, based on the following it should be easy to filter and troubleshoot:Possible List Actions:List ImportAPI List ImportFlow: AdditionFlow: RemovalHere is a quick and rough mockup -- forgive any inconsistencies, I'm writing in stream of consciousness.StatusActionList Name(With List ID and Link)Program/Location Name (With Program/Location ID and Link)Start Day Date & TimeEnd Date & TimeView list of...In ProcessList ImportLI 10 -- Import to Program(LI124488)EVSP 2017-07 -- My Sponsored Event -- MKTO-SFDC (PG2430)7/11/2017 10:00:007/11/2017 10:03:00Leads ProcessedQueuedAPI List ImportLI 10 -- Import to Program (LI12498)PROB 2017-07 -- My Promotional Outbound Lead Gen Program -- MKTO-SFDC (PG2410)7/10/2017 14:00:007/10/2017 14:05:00Leads ProcessedCompleteFlow: RemovalLI -- My Global Static List (LI1244)Lead Database (ML0)7/9/2017 15:05:007/9/2017 15:05:32Leads ProcessedCompleted With ErrorList ImportLI 10 -- Import to Program (LI124401)EGEB 2017 -- My Ebook Program -- MKTO-SFDC (PG2435)7/8/2017 08:00:007/8/2017 08:00:00Leads ProcessedLeads with ErrorsIn Process / StuckImport to ListLI 10 -- Import to Program (LI124307)EMOP 2017-07 -- Operational Email -- MKTO-SFDC (EBP435)7/7/2017 10:00:00AMLeads Processed to DateCompleteFlow: AdditionLI -- Static List (LI1244)Lead Database (ML0)7/6/2017 15:00:007/6/2017 15:01:32Leads ProcessedLastly, this type of view could be helpful for any asset, program, smartlist etc. Could be more widely applied.If this is already on your docket as part of an upcoming release mentioned at summit -- my bad, but I hope it helps Cheers,David

FrederikWerner
FrederikWernerNew Participant

Make default Component Names more readable in Customer Journey AnalyticsNew

Description - Today, default Component Names in Customer Journey Analytics are based on the XDM display name of the field alone. However, that leads to potentially many components having the same name (1) while coming from very different paths in the Schema (2): This makes it hard to understand which, in this example, Type a component really is. To help this, CJA admins have to chose between two bad options: Leave the XDM Schema unchanged (using descriptive display names which only describe the current node) but having to manually change the component name in every connected Data View Changing the XDM Schema display name for all fields to include more information than actually required to avoid having to change many fields in CJA To help with this issue in CJA while keeping the XDM Schema clean, I propose to make the duplicate check smarter. Today, a number is added to the name to make the name unique. Ideally, in case of a duplicate component name, the display name of the field in question would be prefixed with the display name of the parent node, like the parent shown below: In this example, instead of showing up as "Type (3)", the component would be named "Web interaction Type" (field's display name prefixed with display name of parent node), possibly with a delimiter, like "Web interaction > Type". If that is not enough, more parent nodes could be added until the name is unique or the full tree has been traversed, in which case numbers could be used as a last resort. This small change would help users of CJA understand the context of a component, while making admin's lives easier.

skithNew Participant

Allow copy/paste of assets and pages in the same user sessionDeclined

Demande de résumé des améliorations des fonctionnalités (RFE) : There was a functionality on AEM 6.3 that allowed users to copy an asset or a page, then refresh the page (go to another folder by modifying the URL on the browser) and then paste the asset or page to the destination folder. This functionality has been removed on AEM 6.4 to avoid a copy/paste from a module to another one (Assets to Sites for example). But it should still be available when you stay on the same module : copy/paste an asset in the module Assets. Cas d’utilisation : Users used this functionality on 6.3 to avoid going through the whole folder hierarchy when they already know the destination path. It's time saving. Comportement actuel/expérimenté : Select an asset or a page Click on “Copy” In the same window, manually modify the browser URL to go to another folder to paste it Example : From : https://{localhost}/assets.html/content/dam/fr/2022/products/hr To : https://{localhost}/assets.html/content/dam/us/2022/products/hr The window will be refreshed and you’ll be located on the destination folder The button “Paste” is NOT present Comportement amélioré/attendu : Select an asset or a page Click on “Copy” In the same window, manually modify the browser URL to go to another folder to paste it Example : From : https://{localhost}/assets.html/content/dam/fr/2022/products/hr To : https://{localhost}/assets.html/content/dam/us/2022/products/hr The window will be refreshed and you’ll be located on the destination folder The button “Paste” is present Click on “Paste The asset has been pasted Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) : AEM 6.5.12 Nom du client/de l’organisation : Sephora Copie d’écran (si applicable) :   Package de code (si applicable) :  

KeithDavoNew Participant

Exploration weight slider for Recommendations User-based criteriaNew

Description - A slider/setting in Recommendations criteria to tune how much the algorithm should explore items in the catalog.Why is this feature important to you - Our use case is to show some random/less relevant items in a set of User-based recommendations so the they're not overoptimised to what the user has previously browsed e.g. if user only or mostly views pages tagged "Educate me", they can be recommended a few pages tagged "Divert me" or "Inspire me" too (different values of the same attribute/field).It would also help adoption of Target within the business. Assuring Editorial and Product stakeholders that recommendations are not solely decided by an algorithm so less relevant but still important pages can be recommended would help alleviate concern that recommendations are overoptimised (we are a content/media website).How would you like the feature to work - In the Criteria screen, a slider similar to Attribute Weighting between 0% and 100% or 0 and 1 like AWS Personalize's:Current Behaviour - Adobe Target doesn't have this feature but here is briefly how it work on AWS Personalize:AWS Personalize has a hyperparameter called explorationWeight you can configure to set how much the algorithm should explore the recs catalog. Effectively it adds some randomness into the recommendations so new or less relevant items are recommended, e.g. an explorationWeight of 0.3 would include 3 lesser viewed or less relevant items in a set of 10 recommendations. Adobe Target promotions and Attribute weighting are not really the same.AWS Personalize doco:https://docs.aws.amazon.com/personalize/latest/dg/native-recipe-new-item-USER_PERSONALIZATION.htmlhttps://aws.amazon.com/blogs/machine-learning/amazon-personalize-can-now-create-up-to-50-better-recommendations-for-fast-changing-catalogs-of-new-products-and-fresh-content/

Lyndsy-Denk
Lyndsy-DenkNew Participant

Increase list limit OR indicate that there are more optionsNew

Description - Across Workfront are typeahead fields that have limits on how many options they list. I confirmed with support that this is by design and occurs in various places across Workfront. For example, in the Project Overview, the Portfolio and Program fields show only the top 14 (approximately) options. In the case of portfolios and programs, I suspect many Workfront instances have more than 14 active portfolios or programs (or other objects that have a max list). There is no indication that other options exist and that a user can/must type to search for those options.Why is this feature important to you - Users are not always informed of the full breadth of options. If the option is not presented, they sometimes assume it doesn't exist and therefore choose something that isn't appropriate. In the case of Portfolios and Programs, I have project managers who aren't familiar with all the Portfolios we have, so they have to look elsewhere. Some project managers, though, might assume that the best option exists and therefore choose the next best fit. This "next best fit" can throw off our reporting and result in unnecessary housekeeping to bring our data back into alignment. I can't expect my project managers to memorize all our portfolios and campaigns, especially since the options change as our business priorities evolve. To help my projects managers work efficiently, I'd like to empower them with the information at the typeahead field instead of asking them to pause their flow to find the information they need to enter the data.How would you like the feature to work - Either increase the maximum that typeahead fields can present OR visually indicate that there are more options. For example, a "See all" button would open the area that lists all the items available to the user, which then informs them of what to search for in the field.Current Behaviour - Users may choose the wrong option, therefore placing an unnecessary burden on system administration to clean up the mistake. At best, users have to stop what they're doing to look up the options in another area of Workfront—if they have access.