Build better products with our product team
Description - It is a known issue that the Recommendations UI cannot be trusted. This is problematic. Why is this feature important to you - Without accurate data, troubleshooting and set-up is incredibly difficult.How would you like the feature to work - The counts and data should be accurate.Current Behaviour - It shows incorrect counts, it shows expired products, the data is mismatched. At a minimum, it should be made known that the UI is incorrect in the solution. Target can be used to put banners on websites, how about a banner on the catalog page that the data can't be trusted?
There is no native integration between Marketo and Instagram. Marketo Engage should either provide a native integration or enhance the Facebook integration to also support Instagram requests.
How many times a trackAction is activated with an ID that is not registered or is entered incorrectly within the native app code.Taking into account that the development cycles for the deployment of applications within the different STORES (Android & IOS) can take months, these trackActions are dirtying the data and can sometimes increase the useless consumption of SERVER CALLS in your company.This can cause unwanted SERVER CALLS billing.Currently, the "CONTEXT DATA" data in the event we want can be modified through Adobe Launch, enriching the event from "Adobe Launch", but we cannot prevent a "SERVER CALL" from being executed even if we do not need it in our implementation. How would you like the function to work?Ideally, to avoid unwanted "SERVER CALLS", we would include an option in the "MOBILE CORE" where we could prevent the execution of a "trackAction" or a "trackState", conditioning based on its "action name" and/or contextData (in Adobe Launch UI). Current behaviorThere is no way to prevent a "SERVER CALL" from being consumed and counted, even if it is not controlled, or has been included by mistake within the source code of the mobile application through the "trackAction" / "trackState" events. There are some issues in the community regarding this that are quite old.This feature should be a "MUST" to better control the data that reaches the Report Suites, it would give a lot of flexibility and control over the data.
Description - Allow the Widget options on the homepage to be sticky, i.e., Collapsed vs Expanded, "Showing" number, etc.Why is this feature important to you - Most of my projects are long-term, so I like seeing all my project names without the tasks unless I'm working on that specific project.I change "Showing" from 25 to All and collapse all the projects so I only see the project names. This is better visually (not as overwhelming when I don't see all the tasks under the project) and helps me prioritize at a glance and recognize new projects that I might have a one-and-done task instead of multiple tasks.How would you like the feature to work - If I change "Showing" from 25 to All and expanded to collapsed, make those changes stick unless I change them again. Also, make the widget window resize automatically to fit the displayed content instead of leaving a big white space. Current Behaviour - The My Tasks widget defaults to "Showing" 25 and all projects are expanded and the widget window doesn't resize after I collapse them. I do this multiple times a day. Also, after changing "Showing" All, it doesn't give me the original options again, i.e., 25, 50, 100, All. Thanks for considering!
Hi Team,I hope this message finds you well. I would like to propose an idea for a new feature that could enhance our document access management.Feature Proposal:The proposed feature would allow document access to be automatically managed in two steps:Initial Access: Grant public access to external users, allowing anyone with a public link to view the document.Automatic Change as per selected date: After a defined date or time automatically change the access settings to restrict visibility so that only specified users on the access list can view the document.Benefits:Enhanced Security: Ensures that sensitive documents are not permanently accessible to external users.Improved Workflow: Simplifies the process of managing document access by automating transitions.Time Efficiency: Reduces manual effort required to update access settings.I believe this feature could significantly benefit our team by allowing temporary public access while ensuring privacy and security after the designated period.I would love to hear your thoughts on this idea and discuss its feasibility for implementation. Please let me know if you need any additional information or clarification.Thank you for considering this suggestion. Best Regards,Saurabh Birwadkar
We would like to have a direct link between a Slack channel and the Workfront update feed of a project (and other work items).When sending a message in the Slack channel, an update is automatically posted on the related project in Workfront. This would work in both directions. When writing an Update in Workfront, the Slack channel gets updated.With this feature no important information will get lost in a Slack channel, but to be found where it is needed the most!
Currently, when you upgrade an extension, you get this notice:This has scared quite a few clients off of upgrading, because there really is NO going back. Especially for Adobe extensions, there is a strong need to be able to revert in case of issues (not to be snarky, but appMeasurement/VisitorID code updates have a history of finding major problems in the first month after release). Issues like Re: What are possible reasons why ClearVariable fails? make it clear why someone may want to move back. If you upgrade and you do see something break in staging during testing, you'd have no way to go back/compare/undo.
Current Behavior: When a proof is created and a custom proof message is used, by default it will be used for every version of that proof. Sometimes the custom message is very specific to the round of proof. When that message is sent out in additional versions it can cause confusion. By defaulting it between rounds users can forget to uncheck it when creating new versions. This has caused confusion with some of my groups.Proposed Behavior: Include a setting that would reset the use of a custom notification for additional rounds of a proof at an instance level. If active it would uncheck the “Add custom message” radio button at each additional round of proof. They can reselect it and add a new message if it is needed.
Description -Enable any URL to be added as pin on the layout template page.Current Behavior -Currently, from the layout template, we can only pin dashboards or standard pages also accessible trough the "Waffle Menu".Why is this feature important to you -This has introduced the need for admins to go in to every new user and manually pin a specific board to their home page.How would you like the feature to work -At the layout template page, allow users to enter a URL to the pins.
The new Update Variable action in the AEP Web SDK extension would be a lot more helpful if you could start with an existing XDM data element and update that, rather than having to start with an empty XDM object every time.In the scenario where you’ve got a lot of fields that you want to set on every event (e.g. domain, customer id, whatever), I’d want to start with an XDM object that’s already got all those fields populated, and then update that. Likewise, if I've got a lot of ecommerce events, I would want to start with an XDM object where the basic productListItems array is already defined, and then just update that with the relevant additional fields for the particular event (product view, basket add, etc)Currently, you have to start with an empty object in every rule, so you end up repeating a lot of work if you have rules that share a lot of fields.Another, perhaps better, option would be if you could just do the equivalent of the Merge Objects data element in rules. For example, if I've got some default 'global' fields that I want to set in every event, and I've got some standard ecommerce fields that are set on all ecommerce events, a simpler workflow would be:Create an XDM data element that contains all my global dimensions.Create an XDM data element that contains all my standard ecommerce fields.In my 'cart add' rule:Start with the 'global' XDM data elementMerge it with the 'ecommerce' data elementUpdate it with a few fields that are specific to the cart add (e.g. carts adds metric)Then I could just duplicate this rule for all my ecommerce events, and just tweak the final 'update' action depending on if its a product view, cart remove, etc. This would be much cleaner than the current situation where you eitherHave one XDM data element per rule, where you're repeatedly setting the same 'global' and 'ecommerce' XDM fields.Have layers of 'merge object' data elements, where you build up the object before putting it in the rule (e.g. global + ecommerce + cart add)Use the Update Variable action where, again, you're repeatedly setting the same XDM fields over different rules.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK