Skip to main content
New Idea

More Flexibility in Service Request Forms

Related products:Freshservice
  • May 5, 2026
  • 2 replies
  • 30 views

Forum|alt.badge.img+2

Service Request Forms have very rigid limitations.

You can’t add dynamic sections for checkboxes.

Dynamic Sections can’t be added under other Dynamic Sections, which make it impossible to create multi-layered forms.

Max. 9 paragraph fields can be added to a form.

This limitations make harder to create forms for specific user needs.

Thus, it would be better if the service request forms have more flexibility.

2 replies

Forum|alt.badge.img+10
  • Skilled Expert
  • May 5, 2026

You can use dependencies but that only does so much and doesn’t allow you to add multiple fields under a selection just another drop down option based on your selection. The multi-layered dynamic sections would be very beneficial and mean less business rules. 

 

I would also suggest being able to add the same option into multiple dynamic sections. For example, you only want these fields to be visible for this section but you want these fields visible if that same selection AND another selection was made. That way you don’t have to either create the same field in two sections or put the field outside of the dynamic selection and then create business rules on top of it.

 

You should be able to do more from the Service Item itself instead of having to go out and go to Business Rules to create when to show, hide, mandate, non-mandate fields. You should be able to dot his from the Service Item itself in the field itself. That way you can see what rules apply to that one field and if it having an issue it is easier to work out what rules apply to that field and that form.


kpatterson
Top Contributor ⭐
Forum|alt.badge.img+8
  • Top Contributor ⭐
  • May 13, 2026

If I could upvote this a dozen times I would!  

Please, please add the ability to nest dynamic fields!  Our service catalog is far larger than we really need it to be simply because we can’t first as something like “is this for an employee or a contractor” and then use dynamic fields within that initial dynamic field!  Inevitably this leads to confusion among our staff who see the form for “employees” first and try to apply it to a “contractor” rather than using the contractor specific form.

Mind this is only one of many examples where we’ve been forced to use multiple forms where only one should be needed.