Skip to main content

Filter by idea status

10000+ Ideas

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) :  

KeithDavoLevel 2

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/

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.

Fix Exception in Web SDKNew

Description - An exception is thrown and processing halts when using the WebSDK extension and there are two instances of the adobe_mc in the query string. Note:  this was reported in Support Case E-001008770, and even though it does not seem to be a Analytics-related problem I was asked to also enter it here.  For good measure, it was also reported in the Alloy extension github as issue #346.  Hopefully one of these will get it fixed. Why is this feature important to you - While there should not be two instances of the adobe_mc parameter in the query string when attempting to pass identity between domains, the WebSDK extension should deal with the situation better than throwing and exception and halting processing.  When this happens, no tracking occurs, no test propositions are returned, etc. How would you like the feature to work - When there are two instances of the same parameter, the results of a parse operation are returned as an array, not a string.  The extension code that is looking for the identity parameter needs to be aware of this, check the type and proceed accordingly instead of assuming it will be a string and throwing an exception when attempting a split operation. Current Behaviour - The following error popped up in the console:Uncaught (in promise) TypeError: [alloy] [Identity] An error occurred while executing the getIdentity command.Caused by: [Identity] An error occurred while executing the onBeforeRequest lifecycle hook.Caused by: o.split is not a functionThis kept the page from working. Investigation showed the root of the problem was the adobe_mc parameter had been appended to the URL twice (by accident). The code that parses the parameter value does not do a type check after getting the parameter, and when there are more than one instance of a parameter it is represented by an array instead of a string. The code attempts to do a split() operation, but since the type is Array the exception is thrown. To recreate, simply duplicate the adobe_mc parameter on any link and load it.The extension needs to be updated to check the type and take appropriate action if it is an Array and not a String.

sgarrisNew Participant

Controlling for Word Counts in Custom Form Text FieldsNew

There is no way to control for or enforce a custom word or character count within the various custom form text fields. While there are native character limits in the various fields available (https://experienceleague.adobe.com/docs/workfront/using/basics/update-work-items-view-updates/character-limits-in-fields.html?lang=en), none are customizable and each field has its own unique strengths and weaknesses. This functionality would be particularly valuable for the text field with formatting as we are using these forms to author content and the text often needs to fit within a predetermined amount of space within a report's template or on a webpage. We are using a Fusion integration to move the text from these text fields to AEM Assets, and need a way to flag to the creatives who are authoring the text within Workfront how many words they can author to control for publication errors before they submit their content. We've explored a lot of different options and are surprised there is no way at all to enforce a limit or even highlight the word count to authors within the form. We've explored calculated fields as well and think the LEFT or LEN functions could be interesting, but they are incapable of referencing rich text fields. Is there any plan to include the optionality to enforce a word or character count within custom form text fields or show a word count to users using the field within the form?

ctroLevel 2

Workspace: Add a way to group related reports and visualizationsNew

Description -Add a way to group related reports and visualizations. It could be as simple as a container box, like in the attached image. Other options, change background colors, change border colors, etc. Why is this feature important to you -We have a few 'snapshot' dashboards that have many summaries, and it would be great to be able to group and differentiate them. This way, you can glance at it, see the overall picture, and not go cross-eyed. We've been adding in text visualizations to give some separation but sometimes it just makes the report long instead of easy to scan. BTW, we don't rely on these for takeaways and/or alerts, but they are handy for quick glances and answering frequently occurring questions. Some of other dashboard would benefit from this as well, but those are typically more specific. How would you like the feature to work -Add a method to group, define, or visually separate two or more reports and/or visualizations. Select the items to group, right click, and have the option to group in a box, change background color, change border color, or whatever method is implemented to do this. While multiple ways to differentiate would be okay, I think only one is needed. Current Behaviour -The only distinguishing feature currently is the description.  Sample data: obviously just the same two summaries in each 'group' but it's easy to see in this display that there are four separate chunks of information.