Build better products with our product team
Currently the send sample email functionality is only available to users with the "approve email" permission. Send sample needs to be its own separate permission. When we onboard new users in Marketo we start them on a restrictive permission set so they can edit emails, but not approve anything. For their first few weeks they need to get their emails and programs reviewed before approving. Part of the review is sending sample emails. Right now they can only send samples if we give them approval ability.
Could the proofing tool have some old ways of showing the proof creator when proofs have the decision on them? It used to show on a 1-2 step way by clicking on the review, then seeing it on the right-side pane, allowing a quick view. Now there is about 4+ steps to get to even see the decision only.
It should not be possible to delete an Experience Cloud login that is linked to an analytics login, without FIRST deleting the Analytics login. That would prevent the situation we currently have where users' Experience Cloud logins have been deleted - presumably by an admin elsewhere in the business - when they still require Analytics access. The user then sees an error when they try to login, telling them their account is no longer linked to an EC login, and we have to re-add that user's Experience Cloud login.
The current Project Specific Dashboard does not allow for exporting the project status, key decisions & Issues, risks and milestones as one page. The user can only export individual sections which is not useful for reporting to management in a concise, meaningful manner. I am not an expert but I believe this to be a fairly straightforward fix via mapping to one export screen. If this is achieved, users would have a handy one page update to produce directly from Workfront as a PDF. Please prioritize this idea. It would be an excellent selling point for Workfront. (note, adding a small budget or expense field in the same report would be great)Thank you.
Description - When a variable has nested classifications (i.e. classifications that are more than 1 level deep), Classification Rule Builder is unable to operate on those nested classifications.Why is this feature important to you - It is common to have classifications that are nested. Furthermore, the Rule Builder's interface implies that it can operate on nested classifications, when in reality, it cannot. This is the biggest bug.How would you like the feature to work - When there is a rule that operates on a nested classification, then that rule should work in the same way as with top-level classifications.Current Behaviour - Nested classifications cannot be classified with the Rule Builder, even though the Rule Builder interface implies that it can be done.
We have seen many issues with copied projects that lead to incorrect/missing tasks, assignments, irrelevant documents getting carried over etc to name a few.Disabling the copy feature would help ensure all the projects created in Workfront are in sync with the latest enhancements and updates that are in place.
We have dashboards with multiple reports (e.g. arranged like quadrants). To provide end users an unique experience independent of the report result (row count), we would be able to set a fixed height for reports. Even more then we would be able to align reports placed next to each other.
Two situations: We have several reports which are used multiple on different dashboards. And we have reports with a technical name and would like to provide them to end-users via dashboards.Thus we would like to be able to define alternative report titles / labels for the individual dashboards. At the moment always the report name is used as title on the dashboard.
Hi Team, We have tracking URL, which is not enforcing HTTPS, upon clicking it is throwing 404 error . I understood from Marketo support guys that the Marketo tracking URLs cannot enforce HTTPS. They said "at this point in time we do not have HSTS flag for tracking links on the feature list yet". Hence, I am posting this suggestion on this idea page and request you to please review it internally and implement it. Regards, Rohan
Description - add a 'filter' ability to the tickets table on the my cases' screen in the Customer Care portal , for easier searches when looking through ticketsWhy is this feature important to you - would make it easier and faster to search through the long list of tickets in Customer Care portal, My Cases screen.How would you like the feature to work - add a 'filter' ability to the tickets table on the my cases' screen in the Customer Care portal , for easier searches when looking through ticketsCurrent Behaviour - can only 'sort' the columns in the tickets table currently, which, if you have 10 pages of tickets, isn't easy to find the specific ticket you're looking for, (like how you can filter in excel)
Would like to see improved proofing functionality that allows more than just basic markup and commenting on proofs. The vision here is that it becomes truly collaborative where multiple users can documents or spreadsheets together to more quickly get to a final approved product. The edits would have an audit trail as well as email notifications when changes are made. Also consider including shadow/backup copy functionality.
In Classic Workfront, if you navigated to an object (task, issue, project, program etc) that had multiple custom forms on it, you had the ability/option to edit just one of those multiple forms. However, in the New Workfront experience, if you begin editing one of the custom forms and there are multiple, the system actually has you editing all of the custom forms; whether there are 2 or 20. This causes problems if you have a custom form that has a required field that you don’t have the information for yet and where anticipating/planning on adding that information at a later date. I am really not sure what the purpose of this change is since it only serves to remove flexibility.
We have recently moved to New Workfront Experience and one of the big features we miss from Workfront Classic is being able to see the Document's custom form data from the Summary side bar on the right. In New Workfront Experience, there is a link to see the custom form data but there are often times when we want to do a quick comparison of custom form data across multiple documents on a project. It was very easy in Workfront Classic to be able to move back and forth between the custom form on multiple documents and now we have to have several tabs open at once to do that comparison.
It would be nice to be able to display a field in a custom form based on a previous date field. Use case example: There's a date field called Requested Due Date. Display a secondary field called Priority Justification that is displayed only if the requested due date is 5 or less days after today's (request entered) date.
When using weekly charts the business should see the dates in the charts as they are used to .... and since our calendar starts with "Monday", I would expect that the charts also show the dates of all mondays in given time period. Here is an example of a weekly line chart to show the current issue:as you can see, the data points perfectly match the calendar setting (showing a dot on each monday). but the dates on the x-axis are showing "Sundays", as well as the vertical lines above the x-axis-dates. so there is a "gap" between the data points and the chart description which makes it hard to read (and I think it just looks aweful ...) IDEA: Align chart description (dates on x-axis) to match the data points While this "works as designed" I hope this can be changed very soon - I know Adobe can do charts better than thisThanks!
Description - To save up time, allow segments to be applied to multiple panels of a project at once.Why is this feature important to you - It saves time, a lot.How would you like the feature to work - I'd drag the segment on an aread at the top of the project, and it will be applied to all panels below.Current Behaviour - this is not possible.
It would be great to have these feature available: 1. See if a token is in used in any assets or campaigns 2. When changing a token name, token names are dynamically changed in assets/campaigns. Pain point: If I'm to refresh token naming conventions, there's no way to know where the token is used. And since token name doesn't change dynamically in existing assets/campaigns (as opposed to the process of email name change), it's very likely that I'd miss some assets/campaigns, causing the old token to stop working.
To be honest, most users don't even notice commit date until it starts messing with their projections. In the innovation lab there have been numerous requests to change commit date behaviour, that either haven't been implemented, or have been marked implemented when the solution doesn't actually resolve the issues users are experiencing.The historical requests to fix commit date include:1. Give system admins an option to remove "Commit Dates" from the system ‚Äì 2100 points https://one.workfront.com/s/idea/0870z000000PSAKAA4/detail2. New Home: Admin ability to customize left side Work List ‚Äì 970 points https://one.workfront.com/s/idea/0870z000000PSgfAAG/detail3. Viewing Planned Completion vs. Commit Dates ‚Äì 510 points https://one.workfront.com/s/idea/0870z000000PSB0AAO/detail4. Commit Dates Approvals follow the same flow as all approvals ‚Äì 180 points https://one.workfront.com/s/idea/0870z000000PSaMAAW/detail5. Ability to reject a proposed new date (commit date) ‚Äì 150 points https://one.workfront.com/s/idea/0870z000000PSZRAA4/detail6. change the view for "Assigned To" view to use planned completion date instead of commit date ‚Äì 100 points https://one.workfront.com/s/idea/0870z000000PSG1AAO/detail7. Home: Make Commit Date Field Editable ‚Äì 90 points https://one.workfront.com/s/idea/0870z000000PSmAAAW/detail8. Provide option in set up area to turn off automatic set commit date ‚Äì 70 points https://one.workfront.com/s/idea/0870z000000PSlQAAW/detail9. Allow clearing / deleting a commit date on a task ‚Äì 60 points https://one.workfront.com/s/idea/0870z000000PSShAAO/detail10. Progress Status on Commit Date Later than Planned Completion Date ‚Äì 70 points https://one.workfront.com/s/idea/0870z000000PSlKAAW/detail11. Allow change of commit date by PM after team member clicks "Work on it" ‚Äì 60 points https://one.workfront.com/s/idea/0870z000000PSpdAAG/detail12. Commit Date User Control ‚Äì 40 points https://one.workfront.com/s/idea/0870z000000PScwAAG/detail13. Ability to batch update commit dates ‚Äì 30 points https://one.workfront.com/s/idea/0870z000000XiFvAAK/detail14. Users with Manage it Access to Projects/Accepting Commit Dates ‚Äì 20 points https://one.workfront.com/s/idea/0874X000000sYLlQAM/detailSo here is one idea that address all of the above, without impacting any current instances that are actively using commit dates.1. Under ‚ÄòSettings’, ‚ÄòProject Preferences’ there is a default setting for how projects handle commit dates. Sys admins can set this to:¬∑ Set to planned when edited If ‚ÄòTrue’ or enabled, (default) Workfront continues to function as it currently does If ‚ÄòFalse’ or disabled, changing the status, percentage complete, actual start date etc does NOT populate a commit date ‚Äì the field continues to be blank¬∑ Calculate progress status on Commit Date (default) Workfront continues to function as it currently does Projected Completion Date Workfront ignores commit date unless accepted by someone with manage rights to the project (which would update the planned date and thus the calculations anyway)¬∑ Commit date editable by If set to ‚Äòassignees’ (default) Workfront continues to function as it currently does If set to ‚Äòassignees and project owner’ all commit dates are editable by the current project owner or the assignee(s) If set to ‚Äòassignees and project managers’ commit dates can be edited by the assignee OR anyone with manage rights to the project¬∑ Commit date changes approved by If set to ‚ÄòProject Owner’ (default) all commit date approvals go to the project owner ‚Äì current functionality If set to ‚ÄòProject Managers’ commit date approvals can be accepted or rejected by anyone with manage rights to the project2. Under ‚ÄòProject Details’, have the same fields as ‚ÄòSettings’, ‚ÄòProject Preferences’ Note that this fields can be hidden (deselected) in layout templates, meaning if they are set a particular way in project preferences (and/or templates), sys admins can choose whether project owners can change them or not3. If you have permission to edit the commit date, you have permission to simple delete it. Doing so will have Workfront perform the same calculation for projected completion date that it would if a commit date had never been entered.4. If you have permission to edit the commit date, it is editable anywhere it is displayed ‚Äì home page right pane, any dashboard/report, and view that includes the commit date field, task details pane etc. This includes selecting multiple tasks in a view/report and bulk editing to update or remove it.5. Commit date becomes an option in areas dealing with dates¬∑ A date field option on calendars¬∑ The ‚Äòsort by’ drop-down on the home page¬∑ Left side worklist of the home page (planned for implementation)6. If a commit date is generated that is different to the planned completion date, it shows in the home screen along with task/issue/project status change approvals and proof approvals. The workflow is a single stage with only one approval needed, and either contains just the project owner or all people with manage rights to the project (depending on the setting in project preferences)7. The Project owner and/or users with manage rights to the project can reject a commit date. While the commit date will still be on record, the planned completion date and progress status will NOT be based on the commit date.
Color coordinate Parent tasks so it is easier to track deliverables in a large project. There can sometimes be different tasks that have different times to be reviewed/proofed so color coordinating them would help us to find the "grouped" parent tasks in a project that has 300+ deliverables.
I would love to connect user names and the custom forms. That way when submitting a project, the requester can choose the users within a custom form and those users would be alerted that the request is submitted or project created.
Ability to assign every member of a team to a task without having to enter each of the members names manually - The use-case here is tasks that represent meetings. In these cases, we need to assign every member of a team and have the hours allocate across all of them. We want to assign the team and have everyone on the team assigned, not just the first to pick up the request/task.
Imagine a scenario where lead IDs 4 and 5 are merged together in a Marketo instance. 5 is the "winning" ID, so querying the lead via the REST API returns data. However, if you query for data on lead ID 4, a successful API query is returned with no data in it. This means reconciling that 4 was merged into 5 difficult, and leaves a stray ID. Would it be possible to update results on merged records so that they pass something like "mergedInto" : 4 when this occurs? Bonus points if the winning record also got a note like "mergedWith": 3,4,7 -- something that concatenates all records which have been merged into this winning record; this would be nice to help verify on both ends that a merge was successful.
We wanted to make sure that everyone on our "team" was getting instant notifications, not just daily updates onmost of the sub-categories under notifications. I asked and there was no way to set this for the entire team vs. each one having to check their settings...so I did this manually for my entire team. Thank you for considering this idea to update this process.
Display traffic volume in Occurrences rather than in Page Views on the Traffic Management Overview page to help administrators to estimate the server calls volume.
For every project, there should be a checkbox setting that allows for ignoring a user's schedule in the timeline.For example, if a project has a 5-day schedule and one user on the project has a 7-day schedule, there should be a setting on the project to only use the project schedule and ignore the user schedule.
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.
