Build better products with our product team
Adobe Analytics should take holidays into account when firing off alerts. Currently, an alert looks at activity over the recent past (30, 60, 90 days) and based on what's predicted, decides if a change in activity is an anomaly. This all makes perfect sense, except for some incredibly predictable days, like New Year's, Thanksgiving, and Christmas. Adobe should offer a setting that takes into account national holidays. A checkbox would enable holiday logic to be put into placeThe admin would choose from a list of countries whose holidays should be taken into accountOnly traffic from those countries would be counted for these holidaysWhen reviewing traffic and determining if an anomaly has occurred, the lookback period will take into account the prior year's traffic around that holiday and see if it is within a similar trendlineIf it is, no alert will fireIf the traffic is outside the expected trendline by the chosen criteria, an alert will fireAlerts are high stress events. Seeing one after every holiday reduces the urgency of them, and should an actual anomaly occur, it will likely be ignored. This will increase the utility of alerts overall.
Description -Why is this feature important to you - Reducing the delay will allow promote newly launched productsHow would you like the feature to work - being able to promote / recommend Adobe Target Recommendations entities as soon as they launch on application for user.Current Behaviour - 15 Delay is present for product to be added to the catalog, and depending on criteria look-up the product can be recommended post next run of the algorithm which is anywhere between 12 - 48 hours.
Description -Why is this feature important to you - it will allow my users to set their approval status's to something that is meaningful to them.How would you like the feature to work - Similar to buttons in Proof. We can rename those buttons. Can we also add more approval buttons?Current Behaviour - users are stuck with what is hard-coded by Wf and cannot be changed.
Description - Be able to set the date field based off an SLA. ie On a specific custom form the date selected can't be less than 5 business days from todayWhy is this feature important to you - SLAs require time to complete work and requests are asking for dates that are unrealistic. If we can prevent them from requesting 2 days turn around when the standard SLA is 5days it will help set expectations better. How would you like the feature to work - On the field we should be able to set the SLA for date selection Current Behaviour - We add a descriptive text outlining the SLA but users select whatever they want when entering the date. Even today's date.
When viewing a project, it would be nice if the user didn't have to re-collapse the task list each time they come back to the project. For example, CREATIVE is a parent task, and PRODUCTION is a parent task, PRINT MGMT, PREPRESS, and so on.... Production team would like to collapse CREATIVE and the others and have it stay that way; they only want PRODUCTION to stay expanded. Prepress team only cares about prepress stage of tasks, and you get the picture...
Description 20 characters generally is no longer enough to serialize events against... System GUIDs are now generally 36 characters, but can be longer... transaction ids from Google Play Store are 24 characters (now, right now, the solution is to strip the gns or gpa designation at the beginning, and all the . and - characters which just gets us to 20; but how long will this solution last?). 20 characters may have been enough at one time, but times have changed and serialization needs to change with it. Why is this feature important to you Being able to properly serialize against User GUIDs or full transaction ids, rather than risking those values starting with the same 20 characters and being ignored is important to anyone dealing with transactions or any sort of need to de-duplicate based on user ids (account registrations for instance) How would you like the feature to work Serialization needs to allow more than 20 characters... while 36 would cover a lot of needs, there could be other scenarios where this isn't enough... increasing to 255 should cover most concerns and then some. Current Behaviour Serialization is currently limited to 20 characters, anything passed above that is truncated and only the first 20 characters are used for serialization.. this poses a risk of multiple values matching in the first 20 characters (but diverging in the last half) being ignore by the system.
Description - We need better and more customizable real-time reportsWhy is this feature important to you - we can monitor live traffic and results on launch daysHow would you like the feature to work - more similar to google analytics, be able to see top page views and number of unique visitors on the page at that moment in time. breakdown of orders, revenue, products sold and locations of purchases.Current Behaviour - current real time reports are limited to three variables, you can't modify the visualizations, and doesn't work for variables that have processing rules. There isn't even a share link available.
Description - Permissions for segments / calculated metrics / etc are explicitly connected to the one suite under which it is created. On the surface, this makes sense... but many companies use Virtual Suites to control access to specific sites or regional variations within their global footprint... however, unless those users are granted access to the main global suite, they cannot use/access components (even when explicitly shared to those users). Being able to explicitly choose multiple suites on a component (particularly something based on completely "global" dimensions or metrics - like a "Referrer: Google" segment, or a PVs/Visits metric that could apply to any tagging profile) should be accessible from multiple suites. At the very least, there should be a way to all all virtual suites created from the main to have access, even if the main suite is not part of the user's permissions. Creating multiple copies of a segment or metric to use on every suite or virtual suite is massive overhead - sure, the component can be copied and a new suite can replace the old; but when an update has to be made, someone has to go through every item to apply the changes (and ensure that those changes are made exactly the same and to all variants). Segments, Calculated Metrics and other components need to be more flexible to allow us to maintain clean, optimized organization and sharing capabilities to ensure we don't have to repeat work and effort unnecessarily. Why is this feature important to you - The Components have come a long way from how they used to be, but there is still room for improvement to allow proper cross suite usage and permissions. Admins shouldn't have to choose between proper suite permission settings or having to duplicate efforts (and making maintenance so much harder) in order to ensure their users can access the segments or calculated metrics they need. How would you like the feature to work - I would like there to be a multi-suite selection available on components... where an item uses something specific to one tagging profile, this would allow only one or 2 suites to be connected. But for truly shared contents, being able to select all matching suite profiles would be best. There could also be an option to "auto-select" all sub-virtual suites from a global suites as part of the permission levels. Current Behaviour - Only one suite can be selected per component... while the components can be used on any suite, they can only be used if the user has permissions to the main selected suite of the component.... The Select Tracking Suite should be a multi-selection list, not just a single selection.
Request for Feature Enhancement (RFE) Summary: in AEM Assets - select renditions you want to download Use-case: when we have many assets selected, to avoid download all renditions, be able to select renditions we want to download Current/Experienced Behavior: in our DAM we have several renditions, we want to be able to select renditions we want to download to be more efficient Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Louis Vuitton Screenshot (if applicable): Code package (if applicable):
We have a requirement to customise headers in multiple different of areas of Workfront (via Layout Template) to support an enterprise Workfront instance globally across multiple solutions. There are two requirements:We can currently customise up to five fields in headers for Projects, Tasks and Issue/Requests but the list of options to choose from is very limited, to allow custom and system fields would be great - our specific requirement at the moment is for Resource ManagerWe have the requirement to add Resource Manager to other areas i.e. Resourcing and Team, but currently no customisation is available for these.
Description - Add the undo button like we currently have in the comment feature to the beta comment featureWhy is this feature important to you - we constantly use undo to correct/revise commentsHow would you like the feature to work - the beta feature should also have the undo buttonCurrent Behaviour - There's currently no way to undo the comment in beta.
Description - When a project owner or PM rejects time at the Project level - the user who submitted the time is notified by email so they can fix the time. Why is this feature important to you - Several of my agencies have the PMs review the time and they are ALL complaining that rejecting the hour and then notifying the user is too much work and takes too much time. How would you like the feature to work - Time is rejected and the user is notified via email and notifications Current Behaviour - The PM rejects the time and the user doesn't know it was rejected (and it isn't reflected in the timesheet either)
Description -Add a new widget that looks like this: Why is this feature important to you - Anything less than what we have now is "Something taken away from us". A LOT of folks depend on this type of "all-in-one" view of their assignments and requests. Losing it would cost us actual money. I posted this on July 7 in the New Home Beta channel but have heard nothing.How would you like the feature to work - Just make a widget that we can drag in to our New Home and use it as our sole widget if we choose.Current Behaviour - A hodge podge of unreliable and disconnected widgets that have zero governance.
Description - With the feature "make date range components relative to panel calendar", if you change the panel date range to a different amount of time (ex, 7 days to 30 days), the number of days in the date ranges in your table stay the same. For example, if I set my panel to a week, and bring in "last week", it works. But if I change my panel range to 30 days, the component in the table still stays at 7 days. Having the option to adjust the amount of days based on the number of days in the panel range would be useful. Why is this feature important to you - This is important because sometimes dashboard users want to look at different time periods, and if we want accurate YoY numbers, then we need to make multiple versions of the same panel. Having the number of days update automatically would prevent us having to make the same dashboard multiple times. How would you like the feature to work - Have an option when creating a preset date range to enable changing the number of days based on the panel calendar. Current Behaviour - Currently this isn't possible.
Description -Why is this feature important to you - this helps in debugging in case of any failures.How would you like the feature to work - File name should be made available in list of fields available so that it can be mapped to a field in schema.Current Behaviour - No such information is available so that we can link a batch to a file name and use that for debugging.
In the current set-up, data files can be sent to the Adobe Data Landing Zone, which in AEP is considered as an external cloud storage.The file there can be sent encrypted and decrypted by AEP.Huge data files (over 1gb) can be zipped. Issue now is that unzipping and decrypting the data files are 2 distinct steps, where ideally both can be handled immediately together.Enhancement request: unzip & decrypting files via 1 command/step
Request for Feature Enhancement (RFE) Summary: OOTB Option to search using tag in AEM Assets view for convenient filtering of assets within the AEM authoring interface. Use-case: OOTB Option to search using tag in AEM Assets view for convenient filtering of assets within the AEM authoring interface. Current/Experienced Behavior: Currently, tags can be added to any asset but searching for assets with a specific tag is difficult from the native UI. One has to generate a query and use custom reports to get this information. Improved/Expected Behavior: There should be an option in AEM Filters to search assets using a tag picker. This feature exists for auto generated tags like Orientation and Style but not for custom tags. PFA. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud service Latest release Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
Description - I didn't see any keyboard shortcut to rotate a proof and the default one from Acrobat doesn't work (Ctrl, Shift, - or +). Our line of work constantly has elements that are horizontal or upside down on envelopes and other flat proofs. I wish WF Proof used the same keyboard shortcut to zoom in and out with the mouse wheel (Ctrl + Mouse wheel) as it is in Acrobat so I don't have to constantly think about which shortcut to use since Proof uses Shift and the mouse wheel. Why is this feature important to you - To easily navigate a proof using the keyboard for those of us who prefer shortcuts over the mouse to do everything. I am much more efficient in Acrobat than Proof. How would you like the feature to work:Ctrl, Shift, - or + keyboard shortcut to rotate a proofCtrl + Mouse wheel keyboard shortcut to Zoom in and out Current Behaviour - No shortcut to rotate. Different shortcut to zoom in and out than Acrobat (possibly a Chrome issue, but it seems like Proof shares other shortcuts with Chrome, it just depends on if you are in the proof itself or not)
Description - Harness the power of data analytics using Workfront Reporting or Fusion to systematically extract and categorize proof comments within a specified timeframe or based on other filters like file name or version. This endeavor aims to pinpoint areas ripe for improvement, refine training modules, and optimize processes by analyzing comment interactions and resolutions at critical stages. Moreover, this will allow us to collect a robust data reservoir to fuel AI-driven insights in the future. Adobe confirmed this isn't possible within Workfront reporting or Fusion's API capabilities. Why is this feature important to you - Collecting data to improve efficiency moving forward How would you like the feature to work - Run a report on all comments using various filters and have native columns available that show comment text, the proof version number and file name associated with the comment (NOT the latest version of the proof like we can see now with custom reports). If we can gather all this data into Excel that can be plugged into AI later to gain insights, this would be really helpful. Current Behaviour - Not possible at the moment per support
When utilising API developers note: the following endpoints: Get Email by Id, Get Email by Name, Get Emails are only able to retrieve the subject line of emails that have been created as a template but does not have the ability to pull the subject lines of campaigns that have been created for A/B testing or a Champion/Challenger test. As per the developer notes below there is currently no way to pull the test subject lines and all these fields are returned as a blank. This is a mission critical reporting metric for any EMS (Email Marketing System) and should be something that comes out the box. The functionality must be available because this function is possible through RCS, however is not possible through the API currently. Developers noteIf an email is part of a program that is using Email Testing (A/B Test, or Champion/Challenger Test), then that email is not available for query using the following endpoints: Get Email by Id, Get Email by Name, Get Emails. The call will indicate success, but will contain the following warning: “No assets found for the given search criteria.”This functionality would improve reporting adding more value to the product and the available data.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.