The current Workfront functionality intermixes Project level updates with those made on included tasks and issues. It includes even more breadth of topics at the Program level.This causes updates to the project or program record itself to be hidden in the noise.Please create an ability to filter down to just those updates for the object itself (none of its children/sub-items). This should be able to be toggled on/off by the user - similar to the system updates.
We are in desperate need of a "like" button in Workfront Proof. We had this button in our previous system and it is the one thing ALL reviewers/approvers keep asking to bring back, especially our Leadership team.Reviewers leave comments in a proof but the decision to act upon the comment, or not, is dependent upon cross functional business partners as well as our VP's approval. When these folks are in a proof, if they agree with the requested change they click LIKE. That is the green light for the designers to move forward with the update.We've tried using the resolve button however that is used for other situations and it got way too confusing. I fear leadership will will start to challenge if WF is the right system for us. It may seem small and insignificant to many out there but it is essential to our process.
Request for Feature Enhancement (RFE) Summary: Hi Adobe team, Opening up an enhancement request to have the capabilities of flushing dispatcher cache for non-prod pipelines, similar to the production pipelines. This will greatly help us automate our build process. Use-case: Flushing dispatcher cache with client libs and content after some dev and qa builds Current/Experienced Behavior: Non prod pipeline does not have the capability to flush dispatcher cache like the prod pipeline Improved/Expected Behavior: Non prod pipeline have the capability to flush dispatcher cache, just like the prod pipeline (with the same UI options ideally) Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager with AMS AEM Customer-name/Organization name: TD / Accenture Screenshot (if applicable): Code package (if applicable):
The issue we're trying to solve for is that users in the new experience under requests can select a request under the Name Column and leave comments/upload files there. Because those comments/files don't appear in the converted project they can get lost causing confusion/project delays. We'd like to be able to separate Requests from Converted Projects or allow us to manage the view on the request page to remove the Name Column.
We would like to have the ability to enter in a number (x) as a total time spent for the week, and have the system calculate the average (x/5) for each day of the week.
Description -Our org changed email addresses for everyone, and in a few months our old emails will not forward to our new ones. While we can update emails in bulk via csv in the admin console, we still need to transfer assets one by one because if you change the email in the admin console, you still have to change it in Analytics. I wish those systems could talk to one another better so that we could make the bulk change and it would reflect everywhere for the user.Why is this feature important to you -We have to manually, individually migrate hundreds of accounts, and there should be a better way to do this.How would you like the feature to work -using bulk upload in the admin console should work as expected, and edit the selected fields in all Adobe productsCurrent Behaviour -manual, one by one 😞
The idea is to have the original custom message that was sent to be part of the thread when sending an addtl message directly to the recipient from within the workflow. Use Case:Proof Owner sends proof to recipient with a custom message. The proof deadline passes and the proof owner sends a follow up message from with the workflow to the recipient. The follow up message does not contain any of the original custom message and the proof owner ends up copying and pasting that original message into the follow up message. This is similar to this idea if you would want to combine the ask.https://one.workfront.com/s/idea/0874X000000oOQyQAM/detail
DescriptionToday when we use an update activity in a workflow, we force the targeting dimension to change from the actual dimension to the one set in the update activity. It would be great to be able to NOT change automatically the targetting dimensionWhy is this feature important to youThis feature would help to have, visually, a less complex workflow and to encourage best practices in order to use this OOTB activityHow would you like the feature to workA checkbox option, in the update activity, that would allow us to stay on the actual targeting dimension. This would prevent to complexify actual workflows for nothingCurrent BehaviourToday, We have to use a change dimension activity after the update activityOr use a fork activity before the update and join activity after itOr worst: use SQL code activity as it's generally more performant (but less resilient) and it keeps the actual targeting dimension
Description - I'd like to be able to always view the horizontal scroll bar in debuggerWhy is this feature important to you - to facilitate exploration of the values collectedHow would you like the feature to work - I'd like the vertical scrollbar to always show at the bottom, regardless of where I am in the rows collected.Current Behaviour - I have to vertically scroll all the way to the bottom to find and reach the horizontal bar.
We can input tokens in Preheader, however these tokens do not work correctly in some cases.Tokens aren't supported in the WYSIWYG preheader, so please consider to warn us when there are token strings (e.g. {{ or }} ) in Preherder.Referencehttps://nation.marketo.com/t5/Product-Discussions/Problem-with-Lead-First-Name-Token-in-an-email-Preheader/td-p/164478https://docs.marketo.com/display/public/DOCS/Email+Editor+v2.0+OverviewTokens do not work in the Preheader when using the email editor.
While setting up the audience for a Target activity, the experience cloud interface provides two options (create audience under) – 1. Audience Library or, 2. Activity-Only Audience.It would be instrumental to add a new option while dealing with audience creation for your Test where user can move the audience from ‘Activity-Only Audience’ group to the ‘Audience Library’.This feature will be helpful in case user inadvertently creates audience under ‘Activity-Only Audience’ for a Test setup and later realizes that the created Audience will also be utilized by other Target Test Activities. In this situation, user looks for some option that will make this task easy to move their audience from ‘Activity-Only Audience’ to ‘Audience Library’ which will ultimately set this audience available to other Target Activities.Current interface only facilitates with a flow of actions where user might have to delete this audience from ‘Activity-Only Audience’ list and then will have to recreate it under ‘Audience Library’. Apparently, this would not be effortless if you are setting up a composite audience. An instance where user might have faced recreation of their Test Audience based on Geo-locations with 40+ values. The movement from Test specific audience to account library will not only ease such situations but will also allow users to combine with other audiences present in the library. Since, with the option Combine Multiple Audiences, user can only combine audiences present in Audience Library but if user is also looking to add Activity-Only audiences in this combination then this will certainly allow them to achieve the goal. This may not support how combined audience works but I hope the option to expand the audience accessibility from ‘Activity only’ to the ‘Activity Library’ will help users.Thanks,Khushboo Kalia
Hello, We are doing a lot of high level email performance reporting and because we are also ditching leads from Marketo, in order to keep our database clean and of course, because of the size cap we have. In order to properly do this, we use Email Insights but there are a few things that would make our lives way better if changed. 1. It would be gold if we could select "by quarter" in the "by time" filter of the main graph. We usually have to export as "by month" and then have to bundle 3 months together. I understand that fiscal quarters might be different from company to company but not having it at all is not good. 2. Because our email activity is split between Email Marketing and Email Nurturing, we have naming conventions in place, in order to make the difference but for example, when I want to select all the Nurturing programs in the main filter and write "DRIP", I then have to go and select one by one all the programs that contain the word DRIP. It would be super awesome if I could select in one click all the programs that contain a particular key word. All in all, some a proper BI experience when reporting on email would make our lives way easier. Thank you, Dan
It would be great to be able to CC a single email address, rather than having to use a token. Our events teams CC an internal inbox for all of their sends for record keeping purposes. Alternatively, if we could create a Program Member field with an email type and CC that, it would work also. We have trouble with Person fields for this because a person may get invited to more than one event and end up CC'ing the wrong inbox.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.