I have several departments that have varying use cases for freshservice most of which requires the use of the ticket forms section. I manage visibility of the large number of fields using form rules and dynamic sections but now i’ve run into a field limit brick wall that prevents me from expanding the usefulness of this product.
It would be beneficial to not be limited by the current number of fields, I understand there likely is an infrastructure reason as these fields are all probably part of a single table so maybe the solution would be to have multiple forms instead of one segmented by use case. If this would not work due to how automations work then maybe the solution would be multiple portals with their own forms/automations/rules ect. I could see this working in certain cases as not every use case requires integration with others, for example I have certain departments that prefer to have their tickets siloed from the rest of the organization, they have no need to share their tickets with others so having their own form, workflows, rules while not having the ability to integrate with other departments would be fine which would allow me to reduce the number of fields used on the default portal, it would also make my workflow automations and form rules less cluttered and would reduce possible conflicts.
