This thread is resolved. Here is a description of the problem and solution.
Problem:
Client wants to connect job applications to job vacancies. One of the requirements is that when looking at a job vacancy post in the backend it should be easy to see the linked applications and the name of the person who submitted the application.
Solution:
If you create a one-to-many relationship between vacancies and applications, then when editing a vacancy post in the backend the linked applications will be listed. The small cog can be used to customise which custom fields from the linked application are displayed, so that the name of the applicant is shown in the list.
Relevant Documentation:
https://toolset.com/documentation/user-guides/how-to-create-custom-searches-and-relationships-for-users/
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | - |
| - | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | - |
Supporter timezone: Europe/London (GMT+00:00)
This topic contains 2 replies, has 2 voices.
Last updated by 6 years, 3 months ago.
Assisted by: Nigel.
Hi Nigel
I suggest you read the following for background about one way of handling situations such as this: https://toolset.com/documentation/user-guides/how-to-create-custom-searches-and-relationships-for-users/
You will have a one-to-many relationship between jobs << applications (even if applicants can apply to more than one job they will surely need a separate application for each).
I understand your requirement is that on the post edit screen for a job, that the applications are listed and include the name of the applicant?
In the screenshot I have a project << tasks relationship, and the tasks post type has a custom field "assignee", so while editing a project I can see the child tasks and see the assignee of the task. (You can use the cog to customise which fields are shown here. You can only show custom fields, so if the applicant were the post author of the application you couldn't show that, unfortunately, you need a name field, but presumably your applications would include such a field.)
I think that should cover your use case.
