Settings and Sharing per Queue Topic

Hi @jon_chen, could we bring the likes from this Idea over to this one? Same concept, but this Idea above goes into more detail to covers the linked one and more.

Sorry for the delay @madalyn_destafney. The older idea and it's likes have been merged into this one.

This idea is currently being investigated by the Workfront Product Management team. An official response will be provided by the end of May. Thanks for your patience!

@trevor_nolde 

@madalyn_destafney 

@rick_macduffie 

@galenma 

@roxannelu 

@nrynr 

@brianmc1 

Hi Everyone,

This is a great feedback and we are aware of this.

We are working now on improving the end-to-end work intake and requesting process in Workfront and we will make sure to consider this request as well.

Thanks a lot for your patience!

This is also a feature frequently requested within my org, and would greatly help consolidate our request queue clutter as well as streamline some of my Fusion automations. Hoping for good news soon! 

Hi everyone,

We have launched the new intake/requests service for Workfront Planning object requesting. Starting from Q2-Q3 2025 we will start working on expanding the new service to cover Workfront object requests as well. Topics and Topic Groups handling is a top priority for us and we are considering to also add per topic level permissions.

We will provide more details once we have the final solution ready.

Thanks for the idea!

Hi everyone, as previously mentioned we are working on a new request service that will replace the current requests system at some point in the future. We are considering considering not including topics and topic groups in the new system but rather represent each topic as a separate request form or representing each topic as a section in the request form, where you can apply skip display logics and control sharing settings for each section.

As we hear from many customers, topics are pretty limiting and new intake service aims to move away from this idea but instead allow you to build routings, conversion object creation automatically based on a pre-defined rules (like Fusion but native).

I am curious to get your feedback on this and happy to chat more around this topic.

Our use case for using Topics is:

We have request queues where we have a topic for each department in our company. Then when the requestor submits a form, they have to choose which department they are from. Based on that it is routed to an 'intake' person to vet.

So, in this case, how would it work as you are describing? A separate form for every department? Or skip/display logic on one form? Maybe I misunderstood but doing this in our case would increase the amount of our forms a great deal. We are a big company with a lot of departments. If we use the skip/display logic, then it will greatly increase the size of our one form and make it difficult to manage.

That is an excellent question @marladr . No need for multiple request forms. You could just create one form, where you have different sections representing different topics, and apply display logic to show only relevant ones based on the selection of the user. Regarding routing, we imagine routing  to be based on the data submitted by the end-user and not the topic (e.g. If Business Unit 1 is selected in BU field AND Creative Request is selected in Request Type field, then route the request to X person, assign Y person as an approver of the request AND send a notification to X, Y, Z stakeholders). No need to tie anything to a group of topics or ask your end users to choose a routing path during the submission. You would define all the scenarios in the background and the end-user would just need to enter the data into the form.

@jon_chen is there an update on this please? and where could I find it?

Thank you!