Build better products with our product team
Currently on a comment, you can only mark it "private to my company". This is almost worthless when everyone in your company is....well in your own company. We need to be able to mark comments as private to a team or to individuals.We are an internal creative agency and our "clients" are our marketing partners so we're all in the same company. But there are times we need comments just in our own smaller team or set of individuals.And yes, we have set up security so the marketing teams can only see comments in which they are tagged and we, in the agency, can see all comments. But, even within our agency, we need comments just within our smaller teams...such as project managers, creatives, etc.
As is:The Task Constraint setting of new tasks can only be influenced indirectly using the Start Date setting, as follows:Based on the Project Planned Date -> "As soon as possible"Today -> "Start No Earlier Than (today)" Desired:For our Group Admins it would be useful to be able to set Task constraint options as default for the new tasks created in the projects associated with their group.The ask is to have a setting for the "Task Constraint", in the settings of a Group > Task & Requests Preferences > New Task Defaults section, similar to the "Duration type"
When a risk materializes, it becomes an issue. It would be nice to not have to re-create the risk as an issue, but convert it once it materializes.
Description - Ability to persist splits of an audience Why is this feature important to you - Usage of experimentation within audiences (test/control/holdout) are important to measuring KPI's of an auidence.How would you like the feature to work - When a split of an audience is performed, have the ability to select the persistence of the audience based upon a system and or use defined time based value.Current Behaviour - Audience splits are available in Adobe RTCDP audience compositions, but the split of audiences are not retained after the split is performed.
Description - The abililty to translate the labels associated with custom fields so that when the user is displaying Workfront interface in a browser set to, for example, Chinese-Traditional, we can show them labels that they can read. Currently it appears they can only be displayed in a single language.Why is this feature important to you - We have Workfront deployed globally and manage all of our services centrally. It is important that our clients can view Custom Forms and Fields in the languages that they natively speak, read and write, to ensure that we get high quality intake.How would you like the feature to work - In the "Edit Custom Field" popup, add a new button that enables another popup to appear where translations can be managed by language. They will then surface in the front end depending on browser language, like the main Workfront UI does.Current Behaviour - Labels can only be displayed in a single language and for complex labels like Checkboxes, there is not enough space to list all languages.
Currently, Workfront allows you to limit sharing on fields so that you can determine who is able to view, edit, or delete fields. This is very important, because you can designate globally available fields that cannot be edited by Group Admins. However, the experience for Group Admins are very poor. They can open and edit a view-only access field within a form and then save the form. At that point, an error pops up telling them they are unable to edit that parameter and doesn't save the form. IssuesThe error message doesn't tell them what parameter they cannot editThe field they edited doesn't revert back its previous state Ideal future stateIndividuals with access to custom forms that contain view-only access fields can view the fields on the formThere is a clear indicator in the form designer that the field is view onlyWhen they click the field they can view the field details but are unable to edit any field details (e.g., label, name, options, description, etc.)They can request access to edit the field
Currently Alerts in Adobe Analytics are only sent by email or text message. However with more organisations using tools like Slack, it would be nice to have a feature to notify alerts that occur by webhook. These could then be integrated into multiple different organisational tools.
In reports, we can sort columns, why can we not sort groupings? For example, I have a report with 3 groupings. One of the groupings is our business units. We have reasons why we want to see these groupings in alpha order. WF confirms that we cannot sort our groupings. Odd that this isn't possible even in text mode (if I'm wrong on this, someone chime in). Please upvote!
I'm currently building out a series of custom objects for the explicit purpose of being used with Velocity to get certain custom elements into emails, but I may have to do a 1:N relationship rather than the 1:1 relationship I would have preferred. As such, I'd like a user-friendly (i.e., not having to go into the email script) way of setting a selector to choose which custom object to reference in the email. I'd like to have a variable set by the Marketo campaign name be the selector for the correct object to reference in the email.I'm not even sure if this is a reasonable ask with the current scripting setup but it'd make a huge difference.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK