Request Queue Form Simplification | Community
Skip to main content
MattMo3
MattMo3
Level 2
March 25, 2026
Question

Request Queue Form Simplification

  • March 25, 2026
  • 2 replies
  • 14 views

Is there a way, maybe based on Routing Rules, Topic Groups, Queue Topics, or something else I’m not considering to either trigger logic inside the request form or skip sections of the request form?

We utilize one master project request queue that routes to a master request form for our entire company. There was reasoning and strategy behind this, but the ultimate result is a form that asks a large amount of qualifying questions before you are routed to the specific section you’re trying to complete.  I’m hoping there’s a way to bypass some of the preliminary routing steps if the projects are intended for my team or possibly my queue topic.

I’m not exactly a power user of Workfront so I apologize in advance for asking questions that may have an obvious answer, I’ve tried my best to research on my own.

2 replies

WibkeKu
WibkeKu
Level 2
March 25, 2026

I believe this can be done on the Custom Form by utilizing Display Logic. For example you have Section 1 and Section 2 but only want Section 2 displayed if a certain field on Section 1 is filled out. You would add logic in Section 2 and tell it Display this section if xyc is selected in the previous section. Here is a link to an article in Experience League that explains it a bit more: https://experienceleague.adobe.com/en/docs/workfront/using/administration-and-setup/customize/custom-forms/design-a-form/display-skip-logic-form-designer

    MattMo3
    MattMo3Author
    Level 2
    March 25, 2026

    Thank you, this is extremely helpful when trying to shorten the form itself.

    What I was hoping for was some way to apply the same skip logic to some of the initial steps of a form based on the queue topic (or some other setting) of the request itself.

    Lyndsy-Denk
    Community Advisor
    Lyndsy-DenkCommunity Advisor
    Community Advisor
    March 25, 2026

    The key to routing is in queue topics. Because topics are THE FIRST thing that happens in a request queue, you’re constrained by having to think of queue topics before anything else. That means, any standard questions that you need to ask across all/most topics need to be replicated for each topic. Here’s how I managed that:

    APPROACH 1

    • We define topics based on where the routing needed to go. (This also applies to Approvals. So if a topic needs to ask all the same questions but be approved by a certain person, we need to build a dedicated topic.) Yes, this can get lengthy. I map it out in a hierarchy flow chart.
    • Each topic has an identical form attached to ask the standard questions.
    • A topic then has a unique form attached beneath the standard form to ask the questions specific to the topic.

    APPROACH 2 → I find this approach unwieldy because managing numerous custom forms that share fields is painful and subject to error, so I avoid it when possible.

    • Topics based on routing or approvals
    • Each topic has a unique form that has standard questions in the upper sections that then branch to unique sections based on input.
      MattMo3
      MattMo3Author
      Level 2
      March 25, 2026

      Thank you.

      Currently we use Approach 1 with each topic having an identical form attached with standard questions. The issue lies in the fact that the group I work with will always answer the first 5 questions the same way; however, I can’t apply skip logic until that 5th question.

      I’m getting pushback due to the redundancy and was hoping to either default the answers to the first 5 or skip ahead to question 6 when my queue topic is selected. Based on my research there doesn’t appear to be a way to do this, but I was hopeful someone here had found a way. 

      I would attach a unique form to my queue topic, but that violates my company’s policies. 

      Oh well, I will accept defeat. Thanks for commenting!!

      Terms & ConditionsAccessibility statement

      Loading footer...