Product Communities

It is current not possible to use risks outside of the Business Case builder and the Risk tab. This inhibits the ability to create custom reports and dashboards that utilize this data to drive focus or decision making. The fields in Risks should be accessible and flexible in the same way Issues are used.

In organisations with Workfront + Proof, a document will typically be added to an issue/task within a project and a proof generated from within Workfront. We should be able to display information (especially information in custom forms) from Workfront relating to the project, task and/or issue with Proof. Otherwise, every proof reviewer needs a Workfront licence even if their only function is to review and approve artwork. They also need a navigation path, as the notification e-mail from Proof and the proof viewer does not provide any reference back to Workfront. One approach would be to allow calculated fields in the Proof custom form builder that references the Workfront data model.

We're currently having a row between our Project Management team and the Production/Proofreading team:One the one hand, the PM team wants to go all-digital with proof routings, including the handling of corrections by the Production and Proofing teams.However, the Production/Proofing teams for years have relied on a composite PDF of the changes from our previous system that takes advantage of Acrobat's "Comments checklist" functionality to make sure they methodically hit every change. This also serves as their digital record of the work.(Personally, when I have complex annotated PDFs to go through, I like the checklist ability too...I think not having it and trying to work on corrections straight out of WF is asking to make mistakes...)However, using the PDF button under Print Summary to get that checklist is cumbersome and takes at least six steps to generate, download, then re-attach to a new Task to get the work done. A huge time suck over our previous way of doing

It would be great if we could upload imagery or screenshots into our custom forms to better illustrate examples. This need came about when setting up a request queue for our Marketo team. Because Marketo programs/emails have many different elements it would be nice to provide a supporting visual to illustrate what we are asking our submitters to identify.

Ability to Save versus Submit a request - many requests are large and require the ability to be built out and saved before final submission. This is becoming more and more important as we push towards having ALL required information in a Workfront request.

Thank you for your feedback. I am glad to let you know that we have removed the limitation of 1 draft per request queue.You can now have as many drafts for a queue topic as needed and the updated interface will still remind you that you can use one of those drafts. You can access your drafts as you're entering a new request, or from the Drafts area. Feel free to review and provide feedback.

Hi Adobe,To download a single freeform table from Adobe Analytics Workspace, we are currently having to download all freeform tables and remove the rest from the excel or collapse all other freeforms tables and panels. It will be great if Adobe can add a feature where we can select and download only the freeform that we are interested in downloading.Thanks,Srujana M

I LOVE the analytics workspace, especially in comparison to Ad Hoc Analytics (which is what I had been using).The only problem I have with it is that it does not allow you to show more than 200 rows of data. Ad Hoc allows up to 50,000, which is most necessary for pulling some reports.Is there any plan to allow for more rows of data? Or at least download a CSV with more than 200 rows of data?Thank you!

In using WF for our Agile teams and applying the Scrum format, we create Epics by entering a Task on the "project" side of the Agile Team which reflects the parent/child relationship of User Stories and Epics in the Backlog. However, the end date of the Epic is controlled solely by the latest Target Date of all the User Stories under that Epic. We would like be able to control the end date of Epics (or just have no end date at all) but by default, they will show an end date of the User Stories under them. Creating a "shell" User Story works to control this end date however those User Stories will show as aging in our reporting. Is there anything on the WF roadmap to have Epics behave/appear similar to other tools?

It would be helpful to allow for batch campaigns to run more than once daily. We have several campaigns that use custom Salesforce objects that can't use the trigger functionality. I need to be able to run these batches more than once a day for timely communications but this option doesn't currently exist. 

Product team, It would be a big time saver if we had the ability to designate one report suite that would always show up by default in the drop down for A4T reporting in Target.Screen-shot showing the drop down we wish to be able to affect with a settings change:Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | 1 (800) 497-0335

Right now, when you create a new user with a proof license, the option "Automatically generate proofs when uploading documents" is selected. This is irksome. It's an easy fix (remove the proofed document, go into the user's settings, and deselect this option. But I cannot imagine that most people's workflows involve automatically generating a proof for every document stored within a project.

Hello,I would love for there to be an ability for the user to be able to control their own email reminder notifications. For example : If a user wanted to, they can create a notification for "deadline for tasks" that could remind them 2 days ahead of time. If it's easier, there can be pre-set amounts of time or the user could customize. Currently this is global feature but this can be disruptive if I had to set this for everyone as only some would want a notification and others would not. This would be a more utilized feature if this was moved to user control.Thanks,Al

Ability to lock a proof at a specific time not matter what is outstanding on the proofs.

Change the time zones for guest users from military time

Our organization's Adobe Analytics instance includes some "template segments," which we have heard from Customer Care cannot be deleted, and can only be hidden via Virtual Report Suite segmentation and Workspace project curation. These segments were not created consistently, and lead to end-user confusion when our Adobe Analytics power users explore raw data/non-curated reports. I'd like to propose that Adobe Analytics admins have the ability to delete these segments. This would bring the following benefits to organizations:- Increased usability and alignment around organizational goals for existing Adobe Analytics segments - Support an organization's control over their governance plan overall.- Simplification of available/managed Adobe Analytics segments for tool admins and users - Remove admin requirements for curating reporting views due to segments that are not needed or desired, and that cause confusion when present.- Further democratize data for Adobe Analytics power users -

Currently in the header bar on the Tasks page within a project, the Planned Completion date is set based on the project schedule. it does adjust if task durations are adjusted, but if a project is ahead or behind schedule, that planned completion date doesn't adjust or can't be manually adjusted. Because it's at the top of the page we're running into issues with people 'trusting' that date which isn't accurate. We would like to see either the option to turn that date field off, or to customize it to either planned or projected due date.

Request Type field normally suffices as title of request form. Would be great to have Subject field as optional.

hi, it would be great if it would be possible that if a contact has submitted a web form and opted-in and when that same person returns and wants to submit another web form Marketo will check whether they have already opted-in in the past the opt-in box will not be displayed anymore. I know this is possible if a contact / person clicks on a link in an email which redirects to a landing page. 

Currently, any planner creating a project can see every single job role in the Workfront instance. Across a large organisation, this can be an extensive list with many similar job roles. It would be great if job roles could be global (as is) or associated with a specific group, and only members of that group could see the job role. The group administrator could also be given the ability to update the rate/name/description of only job roles associated with the groups they administer.

Would like the ability for a Plan License User to have access to the API. Their API access would mirror their in-tool access. This would only give them access to data and actions that they can access in the UI. They would only be able to query projects/tasks/issues/etc. that they have access to see. This would allow them to use the API to access their data for reporting, building custom spread sheets, populating power-point presentations, or whatever they need.

We have some systems that need to consume Workfront data. Currently the only way to give them access is to give them an admin API key that has Read/Write/Delete access. I would feel much better about allowing them to use the API if their API key was limited to Read Only.

We would like the ability to delegate a single task, issue, or approval. For instance, a Project Sponsor would like to delegate individual Approvals on a case-by-case basis, without delegating all Approvals carte-blanche.

When building a template (or assign tasks in a project), it would be very helpful to assign the number of hours to each assigned resource based on a percentage. Think of it as a new "Duration Type." Like "Simple" but where you put in a percentage of hours instead of a fixed number of hours. For example:Task: Create DrawingEngineer (Task Owner) 40%Engineer 20%Draftsman 25%Intern 15%Duration 5 daysScenario 1 : Enter 10 planned hours for the task.Result 1:Engineer (Task Owner) 4 hoursEngineer 2 hoursDraftsman 2.5 hoursIntern 1.5 hoursDuration 5 daysScenario 2: Enter 20 planned hours for the task.Result 2:Engineer (Task Owner) 8 hoursEngineer 4 hoursDraftsman 5 hoursIntern 3 hoursDuration 5 daysTo summarize:Percentages are based on the % of planned hours for that task (not allocation of resources, etc.)You can change the hours, duration and percentage distribution independent of one another.The percentages should be persistent (they shouldn't reset to an even distri

Currently, it is not possible to create a weekday alert which is triggered only on weekdays.If using daily granularity, an alert will be triggered every day even if weekday condition is set due to the granularity. It is also triggered on the weekend stating that the number is 0. This is a false alert, causing unnecessary concerns and checking of the data.