Skip to Main Content
Community Feedback

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

Status Future consideration
Categories Recruitment
Created by Guest
Created on Aug 3, 2021

Updating a status of the employment record should not remove the content of it

Updating a status of current/previous employment record in the applicant profile erases all the content. For example, when we change the status of the Employer 2 from “currently employed” to “previously employed”, the content saved in there disappears. This means the staff needs to retype them all over again.

In other words, by changing the employer status, the content in there disappears. The content should not disappear when the status changes.

What business value are you trying to achieve?

Updating a status of current/previous employment record in the applicant profile erases all the content. For example, when we change the status of the Employer 2 from “currently employed” to “previously employed”, the content saved in there disappears. This means the staff needs to retype them all over again.

In other words, by changing the employer status, the content in there disappears. The content should not disappear when the status changes.

  • Attach files
  • Barbara Miska
    Reply
    |
    Apr 29, 2024

    The current method of updating employment status within the applicant profile erases previous content, which is not ideal / user-friendly. It would be more efficient if the content were preserved when the status is changed.

  • Adrienne Smith
    Reply
    |
    Sep 27, 2022

    Confirming original post and comment below are needed. To add to the comment below about adding to the top, this is needed because it's not intuitive that adding new employment at the bottom will rearrange once saved to go into chronological order.

  • Mark Evans
    Reply
    |
    Aug 3, 2021

    Needs an add more at the top that pushes everything else down and updates original entry from current to previously