A WFPro Exploration into Request Management

Question

Happy Monday Community! Do you use "Requests" in Workfront? If not, I suggest you get started today because streamlining the capture of unplanned work is a crucial first step towards getting organized, saving time & resources and reducing costs. In my opinion, a request is our first opportunity to negotiate work before wasting any time planning it. At Truist, we rely heavily on requests in our workflow, beginning with this user interface: After some careful navigation through these menus, we eventually find the "right" topic to submit. This is pretty straight-forward in new instances, but with over 500 queue topics distributed across 20+ request types with complex hierarchies, we needed a better solution at Truist. As it stands today, requesters can't easily identify answers to these questions when submitting requests:Who (team, user) will receive this request?How long (default duration + verbose explanation) before I can expect a response?What queue (project) will the issue land in and who owns it (group)?What approvals (default approval) will be required for fulfillment?Other context, such as possible alternative request topics that might be a better fit, links to policies, procedures, dashboards to view existing requests, etc.For administrators, our configuration options are limited because of how "custom" this part of Workfront is. Key limitations we've experienced are:We're unable to delete or deactivate queue topicsUnable to move queue topics or topic groups to different request typesNo queue topic search in "Requests". If you don't know where to look, good luck!Queue Topics can't be "Favorites". When we want to submit new requests, we have to start all over.No configured interfaces where we can zero in on subsets of topics and exclude everything else from view.What do you think about my list? Am I missing anything that you think we need? Do you face similar challenges? If so, how have you solved for them? I'd be interested to hear your thoughts! Okay, now on to the fun stuff... In the interest of giving our requesters (my customers) a pleasant, familiar and intuitive experience, I've drafted a dashboard for submitting requests using the package manifest as the foundation for the design. I'll be integrating this into the existing "WFPro Request Queues" package since this is a missing piece to the WFPRo request management puzzle. Here's this piece to the solution so far, and more is to come! 1. Admins, Group Admins, Configuration Experts Control the Manifest in "Solution" Project - Whether they're queue topics or topic groups, if we capture their unique URLs in the manifest, then we can use these URLs later. If you're unfamiliar with WFPro Package Manifest, this "WFPro Tuesday Trivia" topic is a good place to get an introduction. 2. Requests Area - Users Head to WFPro Requests and access the new dashboard. If you're administering the topics, you head over to the "Solutions" area.3. Choose a Topic - Request Topic Groups and Topics are Rendered using task reports with clickable links taking users directly to...  4. New Request - When Clicked, "Submit Request" takes users to the familiar queue topic or topic group, depending on the preference:  Now with queue topics and topic groups managed as configured tasks in a project, we have endless opportunity to extend the functionality to fit our unique needs. I've said it before, Workfront can't possibly provide every customer with all the features we can think of. But what they did provide us with is an excellent report and dashboard engine that allows us to take control of requests along with every other area of Workfront. #TheWFProWay What do you think?

Doug_Den_Hoed_AtAppStore · Answer

Outstanding work Narayan,

With this technique, you've unlocked several familiar reporting advantages that will improve how a request is made:

reduce the frustration of trying to guess which queue topic leads to the queue they need
instead, allow end users to broadly search for a keyword (eg via a Prompt, Filter, Ctrl+F, and/or Alt+F) then quickly scan the results on mass to find the Right Queue
the descriptions will also be searched (bonus: which allows for less verbose Queue Topic names) which can help them decide on the Right Queue, and remind them in advance what they'll need in order to enter a Request (vs submitting incomplete and/or Best Guess information)
those Right Queue requests can then be routed correctly, and processed more efficiently
for easy future reference, users can choose to access those Right Queues with a Workfront Favorite, a report Filter, or even a saved hyperlink shortcut that could be emailed and/or included in training/reference material
technically, you could leverage the Workfront security model to further restrict (eg users in these groups see only these Queue Topic task rows) or expand (allow these restricted users to Run As a user with rights to see more Queue Topics than that restricted user could see using their rights)
because you've wisely chosen Tasks as the foundation of your report, you could even leverage their native "indent" feature to replicate the hierarchical nature of the native Request window, but in a more efficient (eg collapse/uncollapse) and transparent (eg "see" the hierarchy via indentations), should that be advantageous
and finally (for now), you could extend this technique to add (searchable/visual) additional information about each Queue Topic (eg created by, created for, when created, required fields, typical response time, images, etc) for additional context

Great stuff! I look forward to hearing how your end users like/prefer it, and to seeing it in action in a future WFPro Live session/video.

Regards,

Doug

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded