We love to hear your feedback. Your suggestions and ideas are important to us. Our feedback forum is a great place to post your ideas and vote on others. Please share your detailed use case and how the proposed enhancements can increase value to your business. We do read all of your posts, but may not be able to respond to all comments.
More information on the status of submitted ideas can be found here
When utilizing the applicant preferred first name in communications via merge field there are times the applicant does not have a preferred first name. This means the merge field will be blank. We would like to request logic with this merge field to know that if the preferred first name field is null, then it will populate the legal first name. Until this is fixed, the applicant merge field of preferred first name is unusable to us at the CSU and I would imagine other clients as well, but not sure.
|
What business value are you trying to achieve?
When utilizing the applicant preferred first name in communications via merge field there are times the applicant does not have a preferred first name. This means the merge field will be blank. We would like to request logic with this merge field to know that if the preferred first name field is null, then it will populate the legal first name. Until this is fixed, the applicant merge field of preferred first name is unusable to us at the CSU and I would imagine other clients as well, but not sure. |
I followed up with PU Support as I was under the impression that applicant communications were already accounting for first name when a preferred name was not provided and the PREFNAME merge field was used in communications (per my testing). This is what they advised:
"Our Technical team advised that https://userfeedback.ideas.aha.io/ideas/PUB-I-582 (created in 2021) doesn't seem to say in which area the applicant name is merged field is blank.
There are multiple areas where applicant communication may be sent from, but so far we found 1 area where the applicant's preferred name is not merged: agency portal > View jobs > Notes > Add Note or Edit > put in a note > Save - which sends an email to the job recruiter when the instance is not set up to use Agency feature is disabled and but feature "Applicant Agency Note" is enabled.
Other areas of the system should use applicant first name in merge field when the preferred name is not provided."
Given the complexity of applying the same preferred name upgrades to the 'apply' and other applicant-facing modules, we've decided to mark this for future consideration. We want to take the time to explore solutions that ensure we maintain a seamless applicant experience whilst mitigating any potential risks.