Configure the public Job Detail page | OndaWorx
OndaWorx · Job Board implementation · Step 4

Configure the public Job Detail page

Configure the page that displays one Job, decide which fields visitors see, make sure unpublished Jobs cannot be opened directly, display the Job location and connect the Application Form.

Start with the configuration supplied by OndaWorx. The managed package includes a standard Job_Detail Page configuration and starting Job Detail Field records. For most implementations you should review and adapt these records rather than rebuilding the Job Detail configuration from scratch.

1. Review the standard Job Detail Page

Open:

Setup Custom Metadata Types OW Job Board Page Manage Records Job Detail

The standard record has the Developer Name:

Job_Detail

This record tells the Job Detail component which Salesforce Job object and related configuration it should use.

Setting Standard starting value What to check
Active Checked Leave active for the public Job Detail page.
Object API Name OW_Job__c If the customer uses another Job object, replace this with its API name.
Page Title Job Detail This can normally remain as supplied.
Page Heading Job Detail The actual Job title will normally be supplied by the configured TITLE field.
URL Path job-detail Make sure this agrees with the public Experience Cloud route.
Detail Page job-detail Normally leave as supplied unless the site's detail route is different.
Some Page fields are mainly relevant to Job Lists. Settings such as Page Size and default sorting exist on the shared OW Job Board Page metadata type. You do not normally need to customise those fields for the Job_Detail record.

2. Add the Job Detail publication rule

This is one of the most important parts of the setup.

The Job List has fixed filters controlling which Jobs may appear publicly. The Job Detail configuration must also have its own publication filter.

Do not rely on the Job List filter to protect a direct Job URL. Someone can open a Job Detail URL directly without first visiting the Job List. The Job_Detail Page therefore needs its own rule defining which Jobs are publicly available.

Open:

Setup Custom Metadata Types OW Job Board Filter Manage Records

Create or check the publication filter linked to Job Detail.

Example — checkbox publication field

Setting Example
Page Job Detail
Field API Name Published__c
Operator EQUALS
Filter Value true
Active Checked

Example — status field

If the customer's Job object uses a status field, use the actual stored value instead.

For example: 

Page: Job Detail
Field API Name: Portal_Status__c
Operator: EQUALS
Filter Value: Open
The value must match Salesforce. Do not assume the publication value is true. It could be Open, Published or another customer-specific value.

3. Choose the fields shown on the Job Detail page

Open:

Setup Custom Metadata Types OW Job Board Detail Field Manage Records

The package includes starting records for common Job Detail information, including:

  • Job Title
  • Employment Type
  • Industry
  • Work Location
  • Salary
  • Job Description

If the customer uses the packaged OW Job object, review these records and use them as the starting point.

If the customer uses a different Job object, change the Field API Name values to the equivalent customer fields.

Example detail configuration

Information Example field Display Type Layout Role
Job Title Position_Title__c Text TITLE
Employment Type Employment_Type__c Badge BADGE
Industry Industry__c Badge BADGE
Location Work_Location__c Text LOCATION
Salary Annual_Salary__c Currency PAY
Job Description Job_Description__c RichText DESCRIPTION

For the Salary example, set:

Format = GBP

Keep TITLE and DESCRIPTION simple. Configure no more than one visible TITLE field and one visible DESCRIPTION field for each Job Detail Page.

What the Layout Roles mean

Role What it does
TITLE Main Job heading.
EYEBROW Small text displayed above the main Job heading.
BADGE Pill-style information near the Job title.
LOCATION Location information in the Job header.
DATE A date or grouped date range.
PAY Salary or pay information, including ranges.
DETAIL Additional labelled Job information.
DESCRIPTION The main Job Description block.

Salary and date ranges

If the Job object contains separate minimum and maximum values, they can be displayed as one range.

Give the related Detail Field records the same Group Name and use:

  • START for the first value
  • MIDDLE where a range has an intermediate value
  • END for the final value

For a normal minimum/maximum salary range you would normally use START and END.

4. Configure the Job Location section

OndaWorx includes a separate OndaWorx Job Location component.

This can display additional location information and, if required, a button that opens a map search.

The component is configured using OW Job Location Custom Metadata.

Setup Custom Metadata Types OW Job Location Manage Records

Create or review the location configuration for the Job Detail Page.

Setting What it controls
Page Select the Job Detail Page configuration.
Active Tick to enable this location configuration.
Heading Optional heading displayed above the location section.
Description Optional explanatory wording.
Primary Location Field Main Salesforce field used for the location.
Secondary Location Field Optional additional location field.
Show Map Button Tick if the public page should show a map-search button.
Map Button Label Wording shown on the map button.
Map Search Suffix Optional additional text used by the map search.
The Location component is separate from the LOCATION Detail Field role. A LOCATION Detail Field can show a short location alongside the Job title. The separate Job Location component is useful when you also want a dedicated location section or map link.

5. Add the Job Detail components in Experience Builder

Open the customer's public Experience Cloud site in Experience Builder.

Open the public Job record/detail page.

OndaWorx Job Detail

Add the OndaWorx Job Detail component and set:

Property Value
Record Id {!recordId}
Job Board Page Developer Name Job_Detail
Disable Component JobPosting JSON-LD Leave false / unchecked for the standard OndaWorx implementation.

What does {!recordId} mean? It tells the component to use whichever Job record is currently being viewed. Do not paste the Salesforce ID of one example Job into this property.

Leave JobPosting JSON-LD enabled for now. The next SEO guide explains the JobPosting structured-data configuration. Only disable component-generated JobPosting JSON-LD if another implementation is deliberately providing the structured data instead.

OndaWorx Job Location

Add the OndaWorx Job Location component and set:

Property Value
Job Record ID {!recordId}
Job Board Page Developer Name Job_Detail
The Custom Metadata route does not create the website route. The Experience Cloud Job Detail page must exist and receive the current Job record ID. Always test a real Job link from the public Job List after publishing.

6. Add the Application Form

Applications are part of the standard OndaWorx Job Board setup.

On the same Job Detail page, add the OndaWorx Application Form.

Property Standard value
Record Id {!recordId}
Application Context Configuration Default

The Application permissions, privacy wording and CV-upload settings are covered in the Installation and Guest Permissions guide .

Why use the same recordId? It allows the Application Form to know which Job the candidate is applying for.

7. Publish and test the complete Job Detail page

Publish the Experience Cloud site and test it in a private/incognito browser while signed out of Salesforce.

  • click a Job from the public Job List and confirm the correct Job opens
  • confirm the correct Job title is displayed
  • confirm badges, salary and other configured detail fields are correct
  • confirm the full Job Description is displayed
  • confirm blank optional fields do not leave misleading labels
  • confirm the Job Location section displays the expected information
  • if enabled, confirm the map button searches for the correct location
  • confirm the Application Form appears against the correct Job
  • submit a test Application and confirm it is linked to the correct Job
  • open a published Job directly by URL and confirm it works
  • open an unpublished or unavailable Job directly and confirm public Job content is not exposed
  • refresh the page and confirm the same Job still loads
  • test the page on a mobile-sized screen
Job Detail setup complete Once the public Job Detail page is working correctly, continue to Configure Job Detail SEO .

Advanced Detail Field reference

Most implementations can be completed using the instructions above. The reference below explains the Detail Field settings in more detail.

OW Job Board Detail Field — all fields
Field What it does
Page Select the detail OW Job Board Page record, normally Job_Detail.
Field API Name Exact Salesforce field on the configured Job object.
Label Optional visitor-facing caption such as Salary.
Visible Tick for public display.
Display Order Numeric ordering within the relevant layout area. Using 10, 20, 30 leaves space for later additions.
Display Type Choose a type appropriate to the Salesforce data, such as Text, Date, Currency, RichText or Badge.
Layout Role Select TITLE, EYEBROW, BADGE, LOCATION, DATE, PAY, DESCRIPTION or DETAIL.
Format Additional formatting where applicable. For Currency use a three-letter code such as GBP.
Group Name Shared name for fields that should be displayed together as a date or pay range.
Group Position Use START, MIDDLE or END for fields in the same group. Leave blank when the field is not grouped.
Group Key Leave blank for a standard implementation unless a specific configuration requires it.

Common setup problems

Problem Check first
Job Detail page is blank Record Id, Job Board Page Developer Name, active Job_Detail record and Job object API name.
Published Job opens but unpublished Job also opens The fixed publication filter linked specifically to Job_Detail.
Job title or description is missing Detail Field API Name, Visible, Layout Role, public field access and whether the Job actually contains data.
Salary has no currency symbol Display Type is Currency and Format is GBP or the required currency code.
Salary range appears as separate values Both Detail Fields have the same Group Name and the correct START/END positions.
Job Location does not appear Active OW Job Location record, correct Page, location field API names, component Page Developer Name and public field access.
Application is created against the wrong Job Application Form Record Id is {!recordId}.
Clicking a Job opens the wrong URL Experience Cloud Job Detail route and the Job List/Detail page configuration.

Continue: Configure Job Detail SEO →

Guide updated 10 October 2026. Complete the Installation, Custom Metadata layout and Job List guides first.