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  ...

Hi everyone, this is a great idea but unfortunately it is not included in our plans for this year. 

Hi @MaceyM1 , you should be able to achieve the desired result with our new advanced validation logic. You can look into this thread that showcases a lot of use cases for the logic, including character limit.

Thanks for sharing this idea. We do not have hard commitments for this but we will try to address this during H2 2025

Hi everyone, we do not have any commitments for this idea for the next 6 months due to current priorities. We will get back to this after that. Thanks for the idea!

Hi guys, we do not have hard commitments for this feedback yet but we will try to prioritize it for H2 2025

Hi everyone, thanks for the feedback. We will try to address this in H2 2025.

@KierstenKollins yes, we will not ask you to move to the new service completely until we have the migration plan. Historical data will not be lost, but you would create new request forms and submit requests through the new service.

We are investigating this use case in scope of the new work intake / requesting service. Will provide more updates once we start the solutioning phase

Hi everyone, during H2 2025 we are going to add support for Workfront request in our new work intake / requesting service. We will consider this in scope of the new service.