Renaming Termination fields in the termination flow.

Hey 

Is it still the case that these fields are hardcoded? I was hoping this would have changed by now as its quite frustrating to not be able to call them what we want and have it appear with the name we want in the termination flow also.

What are the drop down in leave type? Is that the reason for leaving? or a type of leave like gardening or parental?

Hi @almabrowne, the ‘leave type’ field in the termination flow refers to the termination type, for example voluntary or involuntary termination.  The reasons can then be further specified in the ‘termination reason’ field. For example dismissal, resignation due to workload/compensation, etc.

In the leave flow, ‘leave type’ can refer to parental leave or sick leave etc. Unfortunately at the moment, the ‘leave type’ field is the same in all flows, so you will see the same options in all these flows which might make it a bit confusing.  

Hope this answers your question!😊

Do you know when there will be a fix for this, seems this will affect reporting?

I don't know, it was already a known limitation when I pointed this out about a year ago. It shouldn't affect reporting though.

In your reports you can filter on lifecycle status, which is based on the flow that you use (termination/leave/parental leave).

And on the dashboard configuration page in the Analytics module you can make sure that the right types are included in the attrition rate. 

Yes I think our issue is around using the word ‘termination’ which doesn’t sound great or respectful of its connotations.

Also not good when the automated Slack comms tell us an employee has been ‘terminated’ rather than that they have simply left the company, and are in actual fact, still alive.

Hi @Sophie Longyear , sorry my answer was to @almabrowne 's question 😊.

Regarding your question, I assume they are still hardcoded. If not, we would definitely make some changes there as well. 

Confirming on above, yes these are still hard-coded. 

Thanks, ​@Ross Symons  🙏🏻

Confirming that you're correct. The termination flow field names are still hardcoded at this time. We appreciate you jumping in and helping clarify!

​@Netta Brodsky Is there any plan to change this so it’s no longer hardcoded please? And if so, are you able to confirm what’s the timeline for this / what stage is it in please?

We would also like to edit the order that these fields appear in the flow (so we can use field dependencies to try minimise confusion with the mixed leave types), it looks like there isn’t currently a way to do this either