Product ideas | Community
Skip to main content

10000 Ideas

jeff_bloomer
jeff_bloomerNew Participant

Key Metric Summary (Please Revert to Original Formatting - OR, Make it Dynamic)New

Please remember to hit the LIKE button to vote for this idea! Description - When the Key Metric Summary was first introduced, it originally displayed the metrics with the number larger, ON TOP, larger, with the percentage smaller, and ON BOTTOM, like this: Now that some significant changes have been made (sometime after the new year), and the feature has finally been repaired (after work I just completed with Customer Care), the formatting has also been changed so that the percentage permanantly displays OVER the number, with no ability for us to swap their positions. This is frustrating, because it used to display just the opposite, and we have no abilty to change how it's displayed. Consequently, I am proposing the following:Not only should we have choice whether to emphasize the percentage or the number, but we should ALSO have the option to decide which number displays on top, which means the display should be dynamic, based upon the user's choice.Why is this feature important to you - Data storytelling remains important, and the way numbers and other elements appear in a certain manner is relevant to the flow of anyone's Workspace.  What may feel nitpicky to one will feel huge to another, and this was a big change! How would you like the feature to work - Adobe is already fairly close by providing us the choice to "Emphasize the number" vs. "Emphasize percent change."  All they need to do is then add the option to say, "Show emphasized item on top," OR they could simply bypass that option and simply place the emphasized item on top automatically. Current Behaviour - Currently, the emphasized number or percent change displays larger, but they remain in place, which is not ideal.    

ChargotraNew Participant

Show Value of Lookup Fields NOT GUID for Dynamics CRM IntegrationNew

The current integration between Dynamics CRM and our CRM system displays the GUID (Globally Unique Identifier) for all synced lookup fields. This approach provides no practical value to the Marketing team, as the GUID is a technical identifier that does not convey meaningful information. Instead, presenting the actual values of these lookup fields—such as customer names, product names, or campaign titles—would significantly enhance the usability and effectiveness of the CRM system for the Marketing team.By displaying the actual values rather than the GUIDs, the Marketing team can quickly and easily identify and interact with the relevant data. This change would facilitate better data analysis, improve decision-making processes, and ultimately increase productivity.Moreover, seeing actual values instead of GUIDs aligns with the way the Marketing team uses the CRM system in their daily operations. For instance, when tracking customer interactions or managing marketing campaigns, being able to see the actual names and details at a glance is crucial. This enhancement would make the CRM system more intuitive and user-friendly, leading to a more seamless and efficient workflow.In summary, replacing GUIDs with meaningful values in the CRM system is a straightforward yet impactful improvement. It addresses the practical needs of the Marketing team, transforms the usability of the system, and ensures that the CRM data is presented in a way that maximizes its value and utility.

csatoNew Participant

Improve Replication Queue not to block other queues when "Blocked Replication Queue" occursInvestigating

機能改善要求(RFE)概要: Improve Replication Queue not to block other queues when "Blocked Replication Queue" occurs ユースケース: When an error occurs in the replication queue and the queue is blocked, subsequent queues cannot be processed until the blocked queue is removed by someone.With this limitation, we'are facing a critical challenge in our operation such as;- when a block occurs on weekends or at midnight, there is no one who can remove the blocked queue, so any pages and/or assets cannot be published until next business day.- when a block occurs on a Brand A's site, that also blocks other replication queues for Brand B.   Can you please change the behavior? such as skip the error queue instead of blocking all queues after an error occurs? 現在/体験した動作: When an error occurs in the replication queue and the queue is blocked, subsequent queues cannot be processed until the blocked queue is removed by someone.Notification is sent from Action Center, so that someone in administrator can notice. But when a block occurs on weekends or at midnight, there is no one who can remove the blocked queue, so any pages and/or assets cannot be published until next business day. 改善/期待される動作: Want only the queue with the problem blocked and the other queues running. 環境の詳細(AEM バージョン/サービスパック、もしあればその他の詳細): AEM Cloud Service 顧客名/組織名 Nissan スクリーンショット(ある場合)   コードパッケージ(ある場合)     @hiroshiorihara1 

jeff_bloomer
jeff_bloomerNew Participant

Copy and Paste Format in Analytics WorkspaceNew

Just a reminder to everyone, a LIKE means a VOTE for this idea.It always confuses me when I see tons of views for ideas, but hardly any "likes." Description - How many times have any of you spent creating a Workspace in Adobe Analytics, only to have any number of Visualizations that you would now like to format similar to one you have recently updated?  What do you do?  Do you delete the old ones, and copy the new one so you may then tie them to the data table?  Or, do you simply proceed to each and use that new visualization as your guide to update the others?Why is this feature important to you - This would be a productivity UPLIFT.  There are plenty of times when I'm adjusting components in a workspace that I would love to simply apply changes I just made to related items. How would you like the feature to work - For this specific feature, I would simply like to go to the Visualization I like, right-click on it, select "Copy Visualization," select the Visualization I wish to update, rightl-click on it and have a choice available that says, "Paste Formatting."  When I do, the component/Visualization "snaps" to emulate the formatting of the component I just copied, with all of the data intact. EXAMPLE:   AND THEN: Current Behaviour - At this time, there is no functionality provided to perform this kind of activity.  I would either have to copy the new component multiple times and connect it to the appropriate data; OR, I would have to simply update individual components to match the new component I just updated, one at a time.

garryp16846478New Participant

Build Models for AI features (Auto-Target, Auto-Allocate etc) based on specific environmentsInvestigating

Description - We have been trialling a number of Auto-Allocate/Target activities and we have unearthed that due to our geographical position we are unable to separate specific market/environment activities from the default environment when there are multiple environments present. The attempts to trial market specific activities results indicate that AI does not have an impact and the added reports (Pers. Insights/Important Attributes reports) not present. With the current documentation outlining that any activity that incorporates the default and another environment that it outlines the hits and conversions are 'Considered' but essentially requests are all served by the default environment. Why is this feature important to you - It is important to be able to run the AI tools within Target that are not reliant on using and including the default environment which is a huge limitation for us. This enables market separation when launching a new AI delivered activity.  How would you like the feature to work - When creating a new Auto-Target/Allocate/Personalisation activity having the option to determine which markets/environments for the activities models to be based on(Single or Multiple). Currently any test has to include the default, each of the activities should be dependant on the environment/market you want to run an activity on or on multi environment activities to select what environment is the decisioning source.  Current Behaviour - We are currently using Auto-Allocate and Auto-Target, and whilst we have seen success in these tools we've observed and proven that the tools are not usable if you use within markets other than the default environment. For those users who work geographically and want to launch specific experiences for specific markets we are unable to without including the default environment, even then the data from the market is only 'Considered' as apart of the model not a decisioning element.