Understand settings for a request flow
The video explains the request flow process in Workfront, focusing on queue management, routing rules, topic groups, and queue topics. 鈥 It emphasizes the importance of organizing the request queue by answering three key questions:
- What topics will I need? 鈥 - These are queue topics that categorize submitted requests, making them easier to manage and customize. 鈥
- Can I organize my topics further? 鈥 - Topic groups help group related queue topics for better organization (e.g., brochures, business cards, and billboards under 鈥淧rint鈥). 鈥
- Who should the request be assigned to? 鈥 - Routing rules automatically direct submissions to specific teams, roles, or users, ensuring requests don鈥檛 go unnoticed. 鈥
By addressing these questions, users can effectively plan and configure their request queue in Workfront. 鈥
Transcript
In this video, you鈥檒l learn about the request flow process specific to queue management and creating and utilizing routing rules, topic groups, and queue topics. It is important to organize the needs of your request queue before you build them out. The three basic questions you need to answer are, what topics will I need? Can I organize my topics further? And who should they be assigned to? The first question that we asked was, what topics will I need? In Workfront, this translates into a queue topic. Queue topics will allow the submitted request to be organized into topics and provide users with the dropdowns needed to define what the request or issue is about. Start off by thinking about all of the different types of requests that you want users to submit to this queue. You will notice that some of these requests can be grouped together into categories. Each of these topics is a queue topic and will allow you to organize similar requests in one spot and customize who these requests are assigned to and what kind of information they will be asked to fill out. On the Workfront front end, this is where your queue topics will appear. If you have a large number of queue topics, you may want to consider organizing those further by creating topic groups. Topic groups essentially group together your queue topics so that they are easier to find. Essentially, answering our second question, can I organize my topics further? In this example, I can see that brochures, business cards, and billboards would fit nicely under print. And social media and websites would fit well under digital. The last question we asked was, who should the request be assigned to? In Workfront, this question translates into routing rules. Routing rules allow submissions to be automatically directed to teams, job roles, and or users within the organization. If we do not create a routing rule, the submission will sit in the issues tab in the request queue project and go unnoticed unless someone is checking that tab every day. You can use a different routing rule for each queue topic. Now that we鈥檝e answered each of our questions, we can map out our plan and configure our request queue.
Key takeaways
- Queue Topics: Define and organize different types of requests into queue topics to streamline categorization and customization. 鈥
- Topic Groups: Use topic groups to further organize queue topics, making it easier to locate related requests (e.g., grouping 鈥淧rint鈥 and 鈥淒igital鈥 categories). 鈥
- Routing Rules: Set up routing rules to automatically assign requests to specific teams, roles, or users, preventing submissions from being overlooked. 鈥
- Planning is Essential: Organize the needs of your request queue before building it out to ensure efficient management. 鈥
- Avoid Unnoticed Requests: Without routing rules, submissions may remain in the issues tab and go unnoticed unless manually checked regularly. 鈥
Recommended tutorials on this topic
recommendation-more-help
c9fbcf61-6d19-481e-a9ab-f54a0ae0ee8a