Skip to main content
New Idea

Ability to hide old fields on Employee Onboarding

Related products:Freshservice
  • April 7, 2024
  • 6 replies
  • 75 views

Forum|alt.badge.img+8

Over time, fields on the Onboarding form are no longer required, but deleting them deletes the actual object and so all previously logged forms will loose that data.

Is there a way to HIDE fields on the form? This is possible on Service Requests, but cannot find in Onboarding. 

This seems like a very simple request, but it’s frustrating have old unrequired fields on an Onboardiong form that we have to try and label to inform people not to fill in….

6 replies

Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Over time, fields on the Onboarding form are no longer required, but deleting them deletes the actual object and so all previously logged forms will loose that data.

Is there a way to HIDE fields on the form? This is possible on Service Requests, but cannot find in Onboarding. 

This seems like a very simple request, but it’s frustrating have old unrequired fields on an Onboardiong form that we have to try and label to inform people not to fill in….

Archiving fields would be good to have  as well. 


Forum|alt.badge.img+8
  • Author
  • Skilled Expert
  • April 8, 2024

Over time, fields on the Onboarding form are no longer required, but deleting them deletes the actual object and so all previously logged forms will loose that data.

Is there a way to HIDE fields on the form? This is possible on Service Requests, but cannot find in Onboarding. 

This seems like a very simple request, but it’s frustrating have old unrequired fields on an Onboardiong form that we have to try and label to inform people not to fill in….

Archiving fields would be good to have  as well. 

Absolutely! (kinda what I was thinking too)


Forum|alt.badge.img+8
  • Author
  • Skilled Expert
  • August 28, 2024

Any update on this one?

This is making our Onboarding module very ‘dirty’ with lots of old fields still existing on the form that we have to try and inform users not to use.


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

But onboarding dose not use the fields in the same way as service items. They get static values on the ticket.  Should be ok to remove them. Have you tested ?


Forum|alt.badge.img+8
  • Author
  • Skilled Expert
  • August 28, 2024

But onboarding dose not use the fields in the same way as service items. They get static values on the ticket.  Should be ok to remove them. Have you tested ?

Oh ok...I did not realise that. I will have to test.

Do you find it’s static on yours? Seems odd that everything else in Freshservice is lookup values, but onboarding is static data on the form. It would be great if we could also edit the content of the form AFTER it’s logged, and sometimes the manager gets the info wrong as don’t want to have to get them to log the whole thing again


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

But onboarding dose not use the fields in the same way as service items. They get static values on the ticket.  Should be ok to remove them. Have you tested ?

Oh ok...I did not realise that. I will have to test.

Do you find it’s static on yours? Seems odd that everything else in Freshservice is lookup values, but onboarding is static data on the form. It would be great if we could also edit the content of the form AFTER it’s logged, and sometimes the manager gets the info wrong as don’t want to have to get them to log the whole thing again

Downside with the static data, it can’t be edit after it’s submitter like a service item. 
You see the form from the Onboard fields are in blue and the service item are under it.