Product Communities

Would like the ability to filter on week days only when using the date based wildcards in reports. Currently, as a default, they only pull in calendar days so if you have a filter where you only go back 2 days and you run the report on Monday, you won't see any data.

For our request queue custom forms, we have a calculated field for "scoring" that pulls in the value of all the fields in the form. That score is then used for triaging and prioritizing the requests. However, Workfront will not allow you to use the same value for multiple options within the same field, and sometimes 2 options need to have the same score. For example, if someone is selecting between President, CEO, and CFO in a custom field about target audience, and we would want President and CEO to both have a value of 5 and CFO to have a value of 3. I understand the confusion this would cause in Fusion, but then perhaps there should be a third option added for field options - label, value, and score.

Via Marketo UI, Admin should have an ability to import list to create/update/delete the users.

Description - one can now change rule or data element and save it without attaching to particular library. It leads to when second person could work with the same rule or data element and make his own changes then publish it. And publishing to production will release changes from both web-masters due to second person won't have idea idea that he worked with someone's changes.  DTM had such feature. It looked like clocks. If someone saw this active indicator, one would find previous person who commited changes before continuing working with rule or data element. Also we don't have option now to see who commited changes. Which is problematic sometimes. Our company also forced to add Last Names to Libraries to get an idea who last worked with components of property.Why is this feature important to you - to make process of working with Launch more simple. And also to add feature that will help to review last changes and connect them to concrete person in company.How would you lik

I am the project owner and I am going to be OOTO. I want to ensure that my coverage gets notified when tasks are marked complete so the job can move along as planned. Right now, the only way I am able to do this is to update the project owner prior to my departure. It would be great if there was a way to mark someone as interim project owner to ensure they get all the proper notifications while I am OOTO. Right now, we use the Sponsor field for managers so they have insight into a direct reports work, but we have considered doing away with that and using it for OOTO coverage.

The current scheduler allows view "group by role" - clean review of resource availability by role. This functionality is not currently available in workload balancer that could be a nice enhancement.

Our compliance team would love the option to export the print summary for a proof by version. Currently you can select all versions or current versions, but not previous versions. Sometime we have the need to see what comments and edits were made to a specific version and having to comb through multiple versions and comments can be cumbersome for our compliance department.

Description - In the documentation for the BDIA (Bulk Data Insertion API), there are 5 Limitations on uploads. One is the requirement that the report suite be configured as "Timestamp Optional" or "Timestamp enabled."  Last month, my team began uploading files using the BDIA for the first time. After each upload, the API provided a response that suggested the upload was successful (see an excerpt of the API response below). However, our QA efforts showed that the data was not present in Analytics even after days of uploads. We eventually determined through other means that the root cause was that the report suite had not been set to "Timestamp Optional". The data uploads were failing, yet the API response did not reflect this.Why is this feature important to you - The data we were uploading is critical for some of our business processes, and those processes were delayed while we investigated the root cause of the failed uploads. We also spent more engineer time than

Currently, proof email notifications add new comments for the entire comment thread, but there is no way to tell which of the comments are actually new. A date and time stamp to each comment would be helpful when a user is skimming through the email for what is actually new.In a proof, they have the date/time stamp for each comment.But when the email notification comes through, there is no way to tell what is new and what has been added to.

Currently only the libraries in the published column display the date they were published. It would be very helpful if libraries that have been built to development or staging displayed the date they were last built in the same manner. This would save a lot of time since you wouldn't have to go open up each library in order to see what date it was built last. In some of my Launch properties I have 10-12 libraries waiting in the development queue for code fixes from our developers. If this was implemented I could see at a glance which ones needed to be built again and which ones had a more current build.

From a security point of view, it needs to be really clear within the tool who is approving/progressing a library through each of the following steps:Summit for approvalApproved for publishingPublishingAt the moment it is really opaque; Although there is an audit log it's next to impossible to decipher.  Also I would expect this information to be available within the area where you are viewing a particularly library which it is not currently (there is an 'activity log' but this just shows the date when a 'build' occurs and contains no user info)

There is a button to collapse all custom forms but there is no option to expand all custom forms. We would like to see the collapse button also work to expand custom form information.

It would be great to be able to mine Fusion 2 history for trending and root cause analysis. I'd like to be able to report on what module threw an error without opening and scanning through each scenario and to be able to report on where webhook calls are coming from, among other things.

Straightforward request: both the W3C and WHATWG consider nested fieldsets to be valid HTML.   https://dev.w3.org/html5/spec-LC/forms.html#the-fieldset-element https://html.spec.whatwg.org/multipage/form-elements.html#the-fieldset-element I would like the ability to use nested fieldsets inside the Marketo UI for second- and third-level groupings for forms. Having this work inside the UI rather than in custom code ensures marketers can control any level of nesting needed for their forms.

It would be great to be able to customise titles like 'Description' in the request/issue queues

We need the ability to adjust Workload Balancer so the workweek begins on Monday. Having it begin on Sunday doesn't work with our schedules and makes it more difficult to manage resources.

It would be great if Fusion could retain a full-year breakdown of the data loads instead of one month; that would begin to allow us to look at patterns of data usage over time. We can look at a scenario and its 1 monthly view of throughput of data moved and operations executed. But we have a need to analyze this data to see the peaks and valleys over time. We hope to use the full-year results and compare it with and correlated them with our regular operations. Ideally to point out additional efficiencies within our process as well further prove the value of Fusion.

The request here is that, after creating a proof in Workfront that included a Custom Message, if the users want to reply or forward the message, the new message could contain all previous messages/emails information, same as when replying to a regular email thread, so the user receiving the email can see the whole history of the email thread .Attaching picture of where the follow-up message is created. Thanks Francisco Borrego

When a report is embedded on a dashboard, the filters, views and groupings are hidden, and the chevrons must be clicked to expand the menu. Users do not see this on the default dashboard view and don't know that they have to click the chevrons either, so is just poor UI. I suggest moving the filters, views and groupings next to Export. I searched and found this related discussion, but the link doesn't work: https://one.workfront.com/s/question/0D54X00006oNcbgSAC/reports-on-a-dashboard-don't-show-the-filter/view/groupingI also searched similar ideas and found these two, which I have upvoted and think they could be combined if the work is being planned.Option to show report description on Dashboard:https://one.workfront.com/s/idea/0870z000000XhXhAAK/detailMake filter option available in dashboards:https://one.workfront.com/s/idea/0874X000000oOKMQA2/detail

We have a number of repeating tasks that we've configured as such. However, due to the way this works in Workfront, those tasks display in a task list long before they're ready to be worked on. Additionally, we'd like to be able to open up the option for repeating tasks/requests to stakeholders.I've been trying to determine if there's a way to automate submission of repeating requests on a specific cadence. For example, the repeating tasks I mentioned above need to be done once a week. So an option on submission to duplicate the request every week for a specific timeframe (days, weeks, months, years) would solve this perfectly. Admins should have the ability to turn this on or off per queue or queue topic.Unfortunately, this doesn't currently exist in Workfront. I've looked into automating this with iOS Shortcuts and Microsoft's Power Automate, but Workfront supports neither of those.

Hello Team, Can we have the ability to add metadata for the Property, rules, datalements, extension so that we can get to know easily who create it, what's the purpose, under which category the rules, datalement resides. It would be great to know this things to avoid redundancy. This feature have in DTM at the moment and with the help of metadata we can search the things easily. Currently in the list of all properties, I'm not able to see who created that property? when it's published last time and the history overall?

BGHR and RPBGHR do not behave like the other tables we can pull from the API. These should be modernized so they also have unique IDs and the ability to pull an accurate count of records. Pulling budgeted hours out of Workfront currently requires working around these limitations, which obviously causes clients issues.

Description -Allow users to easily expand and collapse all containers when using the segment editor.Why is this feature important to you -Complex segments may require the use of multiple containers, including containers within containers. The segment editor allows us to collapse each container, making it easier to see how the segment is set up. It would be helpful to provide an option to collapse all containers or to have all containers collapsed by default when the segment editor is opened, as this keeps us from having to close each container one by one.How would you like the feature to work -Provide a menu that allows the user to expand or collapse all containers. This would be a similar functionality as what is provided in Analysis Workspace when a user right clicks inside a panel. See screenshot with "Collapse all panels" and "Expand all panels" below. While less useful while editing, an alternative would be to have all containers collapsed by default when the segment editor is ope

I am loving Anomaly Detection and Contribution Analysis. As a feature this is such a helpful thing to have, and I know we'll engage with it often. However, I've noticed there are a few hiccups / usability issues that could improve use of the tool:  Sometimes I can't click an anomaly in the timeline and have it show below, and it's not entirely clear whyWhen I open up the Analysis Queue (which is a little hard to see, honestly), the middle anomaly detection report is only partially fluid to that menu, so although the graphs change in scale, the date-range selector gets partially covered. I think that could get simplified to a single calendar icon so it all fits on-screen (1280 width here)When there are no anomalies found, I would really like to see that metric/those metrics trended so I can validate for myself / check if I should be more sensitive witih my training period. I realize that doesn't fit with the current user flow (see anomaly, click, then see metric trended with anomalies.)

I work in finance.  Our site activity drops very sharply on weekends as people can't take action since markets are closed.  This means that I get anomalies every weekend for certain events and measurements.  Being able to exclude weekends would help me find true anomalies.