Build better products with our product team
Admin users could benefit from improved user permission curation hotkeys such as CTRL/CMD/SHIFT + SELECT to quickly setup and create product profiles - the idea being that admins could quickly select a subset of permissions to add/remove in bulk as opposed to individually. This functionality exists already within workspace and would make for a smoother more consistent user experience if shared across products.
Could we have the option for calendar configuration within Virtual Report Suites setting?.... at the moment this is limited to the main report suite under 'Customize Calender'.It would be super helpful for our set up where we have multiple different websites in a single report suite, but some of those businesses are fixed on Sun-Sat reporting windows while others would much prefer Mon-Sun.
11 pixels is really small and hard to read for those without 20/20 eyesight.
Would it be possible to put a fix in one of the next releases to allow for page orientation to be selected when exporting / scheduling PDF reports from Workspace. Portrait and Landscape seems to be automatic based on the dashboard layout, but this is squashing some of the results in tables when the page gets exported in portrait mode.
We need to be able to see calendars on the mobile app
The 'Requests I've Submitted' label is truncated in the left panel menu. Not sure if this is per design, but this has been viewed on various size monitors. Ideally, this field should show the full name. While this does not affect the user experience, it would be better visually if the entire name shows.
Currently, there are set proof dispositions: Approved, Approved with Changes, Reject, etc. It would be nice if we can add additional dispositions. Understandably, the current dispositions point to specific behavior. But what if we were able to add additional dispositions that utilize the existing ones? In one of our use cases, the legal team required specific wording that could not be configured. Had we been able to change the wording, we would have been able to onboard that process. The reject reason is a decent workaround, but it is an extra step that didn't solve our needs.
As part of the project template, it would be nice to have the ability to set a prefix or suffix for a project name. This would make it easier to find, organize, and identify projects. While this field will be optional, it would give System Admins more flexibility and control on the templates.
The ability to sort by the column headings in the Resource Planner. For example, if I am viewing by project and want to see all the projects without planned hours (PLN), it would be nice to be able to click the column heading (PLN) and have it sort. Otherwise, I'm going through a long list - waiting for more results to load - trying to find all projects without planned hours.
In classic when a user picks up a new task they wouldn't know who the PO is for the project. But they could easily find out by hovering over the task name and pop up box would appear with details on the project like PO, Status, Planned Completion Date etc. This is now missing within the new UX and so users have to navigate back to the main project landing page to see the PO name, then click back to home, and click back into the task. This is not a time saving change, it requires more clicks and certainly doesn't simplify the user experience. Please bring back to the hover/pop up box with basic project details.
Adobe Analytics Workspace project's scheduled automatic sending mail format need to customize! The customer wants to customize the following automatic mailing areas.1. Change email address: noreply@omniture.com2. email title : Desired to change the name of the report to more prominently by customization3. main contents texts : "[Name] from [Company] has sent you", this phrase is not translated properly, so it is very awkward. We hope it has changed by customize function.
Adobe Campaign ManagerClassic V7 8889 Request - Ability to manage source code within enterprise source code management and deployment Framework using existing CI/CD stack (bit bucket/bamboo etc..)Business Value - Reduce code conflict and manual deployments causing business interruptions in our shared tenant model
Adobe Campaign Manager Classic V7 8889Use case Description :Limitations to number of API calls from external systems to ACM - Ability to make API calls from AEM and other applications to trigger workflows and delivery template dynamicallyBusiness Value :This has direct impact on the dynamic nature of the solution we are trying to establish for demand gen to build generic workflows and delivery templates
It would be great if System Admins could access the "Sign in as" option from the users profile rather then going to the setup section every time. Also, since the "CNRL+F" does not work anymore in the New Experience, having "Add new user as" as an option on the user profile would be great as well since now one might have to scroll quite a bit to get to the user profile they want to duplicate.
Currently it is not possible to add a date or timeframe dimension to a report in Adobe Target when one doesn't have access to Analytics for Target. See the following forum thread for reference: https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/activity-reporting-get-conversion-and-impression-data-by-date/qaq-p/378938/comment-id/4400#M4399 I'd like to request that it be possible to segment activity reporting by hour, day, week, month, quarter, year, and date. I'm probably missing a level of granularity there.
When using the Pools filter on the Resource Planner, and viewing by project, the AVL hours seems to be capturing much more than just the pool that is being filtered.For example, we have a custom filter set up to show only our Creative department (pool). I would expect the resulting AVL hours value to display the total available hours for the Creative department pool (closer to 1,500 hours when viewing the month of October - 9 users, 21 days, 8hrs/day). However, it's showing 22,030.78 hrs.It turns out that using the Pools filter in this manner filters the number of projects that contain the Resource Pool: Creative Dept., rather than looking at the availability for Creative Dept. users within those Projects. The AVL hours that currently display are the total availability for all users assigned to any Resource Pool attached to that Project.It would be ideal that if a specific pool (or pools) is applied to the Pools filter, that the resulting AVL hours column value displays only the available hours for that given pool (pools), and not all pools.
There is a large learning curve for users when first using the timeline in projects. Other systems can make this set up much more intuitive and also allow for a much more logical predecessor relationship, i.e. using the projects planned completion date as a predecessor. There should be an option to use the projects planned completion date as a fixed predecessor when setting up tasks.
Users have complained that the Custom Forms viewed within the New Experience are more difficult to view than they were in Classic. Everything looks stacked and information is harder to view and understand.The workaround I've given them is to go into the Project's settings and to view the Custom Forms there. However, that's a wonky and clicky solution to something which should be the same as it is in the Project settings. Please make the Forms look within a Project the same as when they appear in the Project settings.
ROLL TIME TRACKED AGAINST AN ISSUE/REQUEST INTO A PARENT TASK.WF allows for issues to be created within projects, which is great. It also allows issues to be nested within tasks, which is even better. When users get issues, they can log time directly on those issues. However, the system does not roll issue hours up to the task hours in which it lives. Issue hours live over in their own pool of hours within the project. I would love for time logged to issues that live within a task to roll up into that task for hours and burn tracking and reporting.
Until this is solved, our rollout and user adoption is going to be very limited. Our roll-out is limited due to the significant confusion around the 'Subject' field. We need each form to have it's own flexibility and not rely on system-wide limitations around this field. Outlined a couple of ideas below.#1 - Preferably, the Subject field would be completely optional.#2 - Optionally, hide the field and then chose which custom form field will be used to autopopulate the contents of the subject field. That way, you can keep the subject field if needed, but in the form designer tool, you chose to hide the field from view and then from a dropdown beside the subject field in teh designer tool, you chose which text field in the custom form will be used to autopopulate the contents of the subject field.
It will be helpful if we can clone just the visibility rule from a form field into another existing form. We have new visibility rule (about 50 of them) that we want to add into all our existing forms. Unfortunately, we have to edit one form at a time and add each rule one at a time.
The struggle is having to create elaborate Rule Names to determine what is included in a rule.The community has created long names to resolve this pain point but it is becoming too long and a huge learning curve for people being onboarded into an implementation.The recommendation would be to create labels and/or folders similar to Google Tag Manager or DTM's feature but with a better UI.Each Rule and Data Element can be attributed to labels and the search will have filters to associate a combination of labels.Suggestion on User Interface:Clicking on Labels will do a filtered search based on the labels. Search can also look for multiple labels at a time. (example: Clicks + Facebook)
We would like to see a feature that would allow users to upload documents from their Home page tasks. Even better wold be if we could upload from a link to Box/GDrive.
It is a huge security risk not to be able to globally delete someone from proofs on which they are the creator. When you hire seasonal contractors, there must be a way to quickly delete them when their contract is up.
As a Launch API user, I would love to have place to attach my own metadata to a Launch resource when creating/updating it. As an example, I might want to create a data element by posting to the standard endpoint, POST /properties/:property_id/data_elementsIn addition to the normal, required parameters, I'd like to have a place to store my own metadata (perhaps a stringified JSON object up to some sane size limit). This would allow for any number of expanded uses. Thanks for the consideration. -Stew
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.
