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
Merging Applicant Accounts - Allow user to identify contact information to retain on primary account
When merging duplicate applicant accounts, it is not always the most recent account the one that we need to keep as the primary account. This is usually because the person was originally hired using the older profile and the applicant ID is already linked to the employee ID on our HR system, and updating that will create additional, unnecessary work on the backend. Therefore, it would be ideal to retain the original applicant ID, while also keeping the most current contact information. Perhaps allowing the user to select which contact information to retain, and/or provide the choice on which applicant ID to apply to the primary account post merge would help ensure the most relevant information is applied to the primary account.
|
What is the business process you are trying to achieve?
Merging Applicant Accounts - Allow user to identify contact information to retain on primary account When merging duplicate applicant accounts, it is not always the most recent account the one that we need to keep as the primary account. This is usually because the person was originally hired using the older profile and the applicant ID is already linked to the employee ID on our HR system, and updating that will create additional, unnecessary work on the backend. Therefore, it would be ideal to retain the original applicant ID, while also keeping the most current contact information. |
