Being able to click on an "Open Summary" preview (like you can in the Timeline level when you click on a task) at the reporting-level (or other objects potentially) would make things much easier to be able to easily view and respond without having to leave the report view itself. (Rather than opening a new tab or having to go back to the report every time)
Looking for a way to control the default view setting so that timelines with more than 100 tasks automatically show all tasks without having to choose “all” from drop-down
The feature inside Analytics called Views Mobile Scorecard is a nice way to create mobile dashboard and it instructs curators of Adobe Analytics data on how to configure and present mobile scorecards for executive users. Video Tutorial: https://experienceleague.adobe.com/docs/analytics-learn/tutorials/additional-tools/analytics-dashboards/adobe-analytics-dashboards-in-app-experience.html?lang=en Doc: https://experienceleague.adobe.com/docs/analytics/analyze/mobapp/create-scorecard.html?lang=en Could you please implement this feature using Single Sign-On? At the moment this feature is not working with SSO. Benefits: Analytics users can use this feature with SSO
Anyone else find it strange that when you select specific folders to include in a report the old program icons are still used?
Part of Marketo Engage's platform involves encoding tracking email links so the platform can accurately associate email activity with records. However, the method that makes this work involves sending a 302 redirect link without any additional HTTP header content; it defaults to Cloudflare's standard instead. This makes it complicated for technical solution providers to determine safe 302 redirects from Adobe and more problematic unencoded 302 redirect links. Would it be possible to put a custom header for technology providers to check against? I'm thinking something as plain as "x-generated-by: adobe-marketo-engage" or similar; this is also straightforward to implement on the CF side.
Request for Feature Enhancement (RFE) Summary: Add typical .json characters to Environment Configuration Name field. Use-case: See attached screen-shoot. Current/Experienced Behavior: Current behavior does not allow dashes, colons, semi-colons, etc. Improved/Expected Behavior: We would like to be able to use .json identifiers, which contain more then the current list of allowed alpha-numerics. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Chipotle Screenshot (if applicable): Code package (if applicable):
Description - AEP debugged doesn't show any events, data or anything really usefulWhy is this feature important to you - Well, for starts I'd like to to show me network events, logs and the basics that I could get from Cloud debugger.How would you like the feature to work -Current Behaviour - Showing me nothing at the moment. It connects, let's me sign in and stuff, but it does not populate any data at all in the debugger itself. Adding Adobe Analytics and all relatable products through Adobe Launch. Does it not work with the standard way of adding AA as an extension in Launch?
Description - Product request: Add the time of error to the error email. The data exists (visible in Fusion) so this should be a trivial change. This would help us distinguish between late deliveries and new errors. Why is this feature important to you - During Fusion "outages" (eg recently the datastore system failed and scenarios couldn't initiate) Fusion queues a ton of error notifications. In our case the emails kept coming in many hours after the issue was resolved. When the Notifications contain the date of the error occurrence we can better filter "noise": Eg in above example I could filter out notifications for Oct 1, and still see all errors (even is same type) that occur on Oct 3. How would you like the feature to work - Add the time of error to the error email. The data exists (visible in Fusion) so this should be a trivial change. Current Behaviour - For the same error type, error message queued from a week ago is identical to the error occurring today. No way to distinguish
There have been many times when Workfront users will enter comments into a project and forget to include the right people or any people. This has caused so much frustration, delays, etc. that could have been avoided if Workfront had an option to send all comments on a project to the Owner and Sponsor. This can be a setting in the email notification per user, or at the admin level.
Description - The Initiative name column is too narrow it only allows 23 characters. Please allow this column width to be adjusted Why is this feature important to you - In order to prioritize projects we need to be able to read more of the name. How would you like the feature to work - Allow the column width to be adjustable Current Behaviour - Its locked at 23 characters.
The fact that you cannot embed screenshots in the description or updates is a major flaw. I get that you can attach them as documents in a different tab, but they are difficult to open (you get either a tiny thumbnail that you cannot see or open it in a new window). Especially for bugs it is nice to say, "it looks like this: [X] " and I expected this: [X]" using inline images. We basically post these images and full description in Microsoft Teams because there is no other way.
I would like the typeahead field to be linked to whatever was selected. For instance, if the field was for project, someone types in a project. After that field has a saved entry, I'd like that text of the project name to now be an active link back to that project. It would be a great reference. I wanted to put it in our request queues as a link to a previous project they want us to reference in creating a new project. But with no active link, it doesn't make any sense to use that field.
Description - Deactivated users should not come up when you're tagging someone in a Workfront proof or searching for a user. There are a lot of common names out there and it makes it harder for users to select the correct user when tagging. Why is this feature important to you - Avoid the risk of tagging or searching for a user no longer with the company due to similar names/same first names How would you like the feature to work - Don't show deactivated users except for in the user field with the deactivated filter on Current Behaviour - all active and deactivated users show up when tagging someone or searching for someone.
Marketo was recently updated to support setting HTTP headers for landing pages, including setting HSTS. This is great! However, additional standard security headers should be set for Marketo Landing Pages; this is onerous to do and requires proxy work outside of the platform. Would it be possible to add support for the following header items: x-content-type-options referrer-policy x-frame-options content-security-policy permissions-policy Additionally, the following three headers are upcoming and should have future support: cross-origin-embedder-policy cross-origin-opener-policy cross-origin-resource-policy This helps harden security for Marketo landing pages and may be required for infosec reasons.
Description - We try not to edit Scenarios when live, but there are times when we do. And invariably, we replace the module and neglect to update a filter. This causes lots of error spam. It would be good to see the same little number one sees on a module on a filter so we can fix the issue before it becomes a visible error.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.