Documentation
Fields and field mapping
A field reaches the public page only if you have enabled it. That is the whole model, and it is the reason a confidential value cannot appear by accident: the page can only show what has been granted, and the grant is checked again when the page renders.
Where to go
Two screens, two jobs
| Essential Fields | Set during connection. The handful a job page cannot do without: title, location, the basics |
|---|---|
| Fields | W3Bullhorn → Fields. Which Bullhorn fields are available to the page at all |
| Field mapper (Pro) | W3Bullhorn → Field mapper. Put one of your own Bullhorn custom fields onto the page, without code |
Field mapper
Adding one of your own custom fields
Pro. No code, and you see the result before a visitor does.
- Open W3Bullhorn → Field mapper.
- Choose the Bullhorn field. The list comes from your own Bullhorn configuration, so it shows your field names rather than generic ones.
- Choose where it appears on the job page, and whether it is for display, for filtering, or both.
- The screen validates the choice and previews it. A value Bullhorn will not give, or a field that is not permitted, is refused here rather than silently producing an empty row.
Picklist fields arrive with your own tenant’s labels, and follow a rename in Bullhorn on the next page view. If you withdraw a field, it leaves the page on the next view too — there is no cache to wait out.
Keeping a value off the public page
A field that is not enabled is not merely hidden: it is never asked for. The page cannot render a value it was not granted, and the grant is re-checked at render time, so typing a field name into a template or a builder widget by hand prints nothing. This is the control to rely on for client names and any other confidential detail.
Tracing
Where a value on the page came from
W3Bullhorn → Record tracking, under Advanced.
When something on a job page looks wrong, the usual question is whether Bullhorn said it or the site did. Record tracking answers that: it shows where a value came from, which turns an argument into a lookup.
It is under Advanced because most sites never need it. When you do need it, it saves a long afternoon.