Build better products with our product team
When I share an object, whether it's a project, report, view, or otherwise, I'd like to be able to add a short comment for the recipient(s) of the share notification to provide additional details about what is being shared, where to find it, etc.
I'm stealing this from Microsoft SharePoint, but it would be great if there was a spreadsheet mode on the task list for a project. This would allow us to copy from excel (if the columns matched) and would allow us to copy things like Duration, Assignments, and Planned Hours from one task to another task easily.
Many Analytics server applications are now offering 'embed codes' for custom web apps. This works by clicking on the dashboard. A dropdown comes up with embed code that includes a custom iframe or script +div code. Tableau, Domo and others are now offering this feature. The embedded code in the web app will prompt you to log in through SSO, keeping the data secure. Adobe Analytics should incorporate this feature for use in custom applications. We are building a simple reporting dashboard and were surprised that Adobe doesn't have it. In fact Adobe blocks any attempt to host a chart when the source URL is not the same as the host. If you look at this article it provides a really intuitive experience with a GUI for users. This one is best in class: https://plotly.com/chart-studio-help/embed-graphs-in-websites/
Description - In the Flow visualisation, when you mouseover the steps' dimensions, the visualisation expands to show the individual dimensions in each step. But the "Eventual Path" / "Next Hit" line is above these dimension listings.Why is this feature important to you -I consider this to be basic user experience. Reading from top to bottom for each step, the visualisation should first show what that step comprises of. After that, then the "Eventual Path" / "Next Hit" can be shown to "link" that step to the next step.The current behaviour forces the eye to move back up to see which of "Eventual Path" / "Next Hit" has been selected for the next step.How would you like the feature to work -Move the "Eventual Path" / "Next Hit" to after the dimension listings. See graphic.Current Behaviour -The "Eventual Path" / "Next Hit" are before the dimension listings.
The API documentation needs to be improved overall. There are things missing from it, and there are references to v4 and v5, without notes about whether or not they're still relevant. It's hampering our integration efforts.
One of the main topics in terms of acceptance of the NWE is that the task description and the updates are divided into two tabs.My colleagues keep referring to Classic, where that was possible at a glance.Please find a solution to display the update stream at the same time as the description again.
Hi, I have a problem. We have set up lead gen form in Marketo and the submissions for these forms from LinkedIn to Marketo are working fine. Fields are mapped, all good. Problem: I have set up a trigger campaign that says: Person is created filled out form = lead gen form fills out form = lead gen form and then a flow step to change some data values Issue: The leads that are created via API lead gen form do not flow through this campaign. I dont understand why? The campaign should check if a person is created and filled out the form then do the flow step but it does not work. If I create a filter campaign with the same criteria I find all of the newly created leads and can perform the flow. I dont understand why this does not work with a trigger?
This is something most Adobe users do not know nor expect nor does it make much sense: Marketing channels have a rolling 30-day expiration, whether a channel was touched or not. Tracking codes have an expiration based on when the variable was defined. https://helpx.adobe.com/in/analytics/kb/comparing-tracking-codes-and-marketing-channels.html "Expiration differences: Marketing channels have a rolling 30-day expiration, whether a channel was touched or not. Tracking codes have an expiration based on when the variable was defined. For example:The campaign variable is set to expire after 30 days; your marketing channel visitor engagement expiration is also set to 30 days.A user arrives on your site via the tracking code promotion3, then leaves.They come back three weeks later without a tracking code or marketing channel, and exit the site again.Another three weeks later, they come back without a tracking code or marketing channel, then make a purchase.The user ultimately made a purchase beyond 30 days but was never inactive for more than 30 days. Therefore,Marketing channels attribute revenue to the campaigns channel, since the visitor engagement is reset each time they return to your site.The tracking code report would attribute revenue to "None," since the purchase event occurred beyond the variable's expiration."Example:See this user for example: He came through Channel "Paid Search G. Shopping" on Jun 3 (M Channel Instances was set). That was also his last Marketing Channel Instance.However when we look at this user's data on Nov 3, it is STILL attributed to Paid Search Shopping even though 30 days since his last Channel Instance have long passed!This is - imho - absolutely not what a Marketer would expect. It is also unnecessarily inconsistent compared to eVars logic (tracking codes etc.). It is furthermore not documented on the Marketing Channels Expiration page, where just some fuzzy sentence concerning "First Touch Channels" is found. In Marketing, you usually want to usually acquire someone once and then you want to see how many of those who were acquired return by themselves (e.g. via "Direct"). Your hope is that you do not have to re-acquire them again and again through Paid Channels. In the example shown above, Marketing will draw the false conclusion that they are re-acquiring this customer over and over again through Google Shopping, which is NOT the case. A user who has returned directly for almost half a year is still attributed to Google Shopping just because he never had more than 30 days between visits... Adobe needs to change this logic to be in line with eVars expiration. I bet most clients do not expect Marketing Channels to work like that. Even better would be a toggle option in the Expiration Settings like 'Expire xx days after most recent marketing channel instance' or 'expire xx days of visitor inactivity'.
Description - The current ACS APIs available does not provide a way to fetch the deliveries and workflows informationWhy is this feature important to you -1. There are some features like heat map which is available in ACC but not in ACS and it can be built if the workflows execution information can be fetched through API in Firefly project but the API isn't available2. Currently in ACS there's not quite a lot flexibility in terms of what information can be displayed (limited to available dimensions) on Dynamic Reports. A lot of times it's needed to generate a custom report about the deliveries like number of sent, delivered, bounced, opened, clicked messages, etc. and display that on the UI outside ACS similar to dynamic reports. There isn't any API related to Deliveries.How would you like the feature to work - Exposing Deliveries and Workflows data via APICurrent Behaviour - API does not exist for workflows and deliveries.
Content Fragments are now used widely in AEM project majorly in headless and hybrid model. But still there are some features that can be added in content fragment that can make it more valuable:1) Use of Multifield. Currently the multifield works fine when there is one level of child but for some cases we require multlevel multi field that does not work fine as it works in the component level.2) Live Copy Inheritance in Content Fragment is not supported.3) Asset level versioning shows the version number , it should also show the date of version so this will help to track the exact revision as well.4) Dialog level clientlibs instead of override dam.cq one for dialog level events.
Hi,A nice feature to implement will be a standard "trash-bin" functionality for AEM Assets. Right now we have customization (implemented on AEM 6.3) as described herehttps://kbwebconsult.com/2020/07/21/the-enigma-of-aem-apache-sling-filters/ Best,Krass
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