Skip to main content
Not Taken : Idea will not be considered

** New properties for fields **

Related products:Freshservice
  • December 1, 2021
  • 5 replies
  • 98 views
vijay_2am
Skilled Expert
Forum|alt.badge.img+6

Custom field properties

 

As of now when we add custom fields to the forms, we get the below properties.

 

 

In addition to this, it would be great to have additional properties like

  1. Hide when <<condition>>
  2. Required when <<condition>>

 

This will provide more functionality to the usability of the custom fields. If we extend this to the code/ootb fields, that will be an added advantage.

 

Thanks

Regards | Vijay

5 replies

rashmi.nag
Skilled Expert
Forum|alt.badge.img+9
  • rashmi.nag
  • Skilled Expert
  • May 12, 2022
Updated idea statusNew→Open
Cheers, Rashmi || Team Freshworks
alyssia.correa
Skilled Expert
Forum|alt.badge.img+8
  • alyssia.correa
  • Skilled Expert
  • February 21, 2024
Closed for Voting→Not Taken : Idea will not be considered
Ally, Freshworks Community Manager
alyssia.correa
Skilled Expert
Forum|alt.badge.img+8
  • alyssia.correa
  • Skilled Expert
  • February 21, 2024

Hello Community members, this idea can be achieved through business rules. Should you have any further questions, please add them in here.

Ally, Freshworks Community Manager
Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Can’t this be done with Business rules, but it would be great to have on the field it self. 

Synerity | Your Nordic Freshworks Partner | Seamless Support & Solutions | www.synerity.eu
    aseemaishwarya
    Community Manager
    Forum|alt.badge.img+1
    • aseemaishwaryaCommunity Manager
    • Community Manager
    • February 21, 2024

    Can’t this be done with Business rules, but it would be great to have on the field it self. 

    Thanks @Daniel Söderlund . Feedback taken. I believe as of now all these configurability along with other configurations are possible with business rules. We will take into consideration if we can enhance the fields to support this in future.

      Terms of UseAccessibility statement