Discussions

 View Only
  • 1.  Relate one Applicant to numerous Jobs

    Posted 01-22-2018 21:23
    I have an app that will list available job openings (in a "Positions" table) and request applicants to apply.  Currently - when they apply - the app will open the add new record form in the "Applicants" table, and that applicant will be related to that one position. 

    I'm trying to develop a good method for Applicants to enter their personal information once - but have it linked to multiple open Job Positions. 

    There will be multiple Hiring Managers viewing their Position's Candidates.
    On the application form, I'd like to list all of the open positions - and have the candidate select each of the positions they are interested in.
    e.g. Applicant #1 enters all of their personal information one time - then selects Job #1, Job#2, and so on...and each Hiring Manager will see their own related Candidate for their posted jobs.

    I do not want the Applicant to need to enter their information multiple times when applying for multiple Job Openings.

    I'm not sure if I'm looking for a summary report for the positions recordID# - to then link to the child record or if an API or webhook would link each selected job to the individual candidate? 

    Appreciate your opinions/suggestions...

    Thanks,

    Ken


  • 2.  RE: Relate one Applicant to numerous Jobs

    Posted 01-22-2018 21:28
    I would have them enter applicant info that they want to be used for applying to a position but I would make another table called Applications. One Position to many applications and one applicant to many applications would be your relationship setup.


  • 3.  RE: Relate one Applicant to numerous Jobs

    Posted 01-22-2018 21:39
    Well, three tables, actually, which together create a many to many relationship.
    1. Applicants
    2. Positions
    3. Application-Positions: This third table is a master (parent) to Applicant records and also a master (parent) to position records. One Applicant-Position record can be related to one or many Applicants and to one or many Positions.
    On the Applicant form, you would have an "Add Applicant-Position" button (maybe renamed "Apply for a Position"). Clicking this button brings up a form to create a new Applicant-Position record, with basic Applicant info (name, etc) copied from the Applicant record. On the form, the user would select a Position from a dropdown or browseable pop-up for Related Position. After saving it, they would then have to add another positon (technically another Applicant-Position record). So the user-experience will require some careful thought, but it is definitely doable.