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 is the business process you are 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. |
