Configure OndaWorx Job Board Pages, Fields and Filters
OndaWorx · Job Board implementation · Step 3

Set up pages, list fields and filters

Configure what appears on the public Jobs page, which jobs are allowed to appear, what information is shown on each job card, which filters visitors can use and how the results can be sorted.

You are configuring records, not building code. OndaWorx uses Salesforce Custom Metadata records to control the Job Board. In most cases you will work under: Setup → Custom Metadata Types → [OndaWorx type] → Manage Records .

Before you start

Complete the installation and Custom Metadata layout check first.

You should also know:

  • which Salesforce object contains the jobs
  • which field determines whether a job may appear publicly
  • which fields contain title, location, salary and other public information
  • which fields candidates should be able to search or filter
  • the public URL you want to use for the main Jobs page
Page Defines the Job Board page and Job object.
Fixed filters Decide which jobs are eligible to appear.
List fields Decide what appears on each job card.
Search filters Let visitors narrow the results.
Sort options Let visitors change the result order.
Publication rules are important. A visitor-facing search filter is not a security or publication rule. Every public Job List page must have the correct fixed filter that limits its results to jobs the customer has approved for publication.

Start with the standard Jobs page

The OndaWorx managed package includes a starting Job Board configuration called Jobs.

For a straightforward implementation, start by reviewing and adapting this configuration rather than creating a completely new Job Board page.

Setup Custom Metadata Types OW Job Board Page Manage Records Jobs

The packaged configuration provides a useful starting point, including:

Setting Standard starting value
Developer Name Jobs
Job Object OW_Job__c
Page Heading Current Jobs
URL Path jobs
Detail Page job-detail
Page Size 20

If the customer uses the packaged OW Job object, many of the starting records can simply be reviewed and adjusted.

If the customer uses a different Job object, change the Page record and related field/filter records to use that object's API names.

What is a Developer Name? It is Salesforce's permanent internal name for the configuration record. For example, the standard Jobs page uses Jobs. Related OndaWorx records use this Page record to know which Job Board configuration they belong to.

1. Review the OW Job Board Page record

The Page record is the main configuration for one Job Board page.

Open:

Setup Custom Metadata Types OW Job Board Page Manage Records

For the standard page, open Jobs.

Field What to enter
Active Checked when this Job Board page should be available.
Object API Name The API name of the Salesforce object containing the jobs, for example OW_Job__c or Job__c.
Page Title The title for this logical page, for example Jobs.
Page Heading The main heading shown above the Job Board, for example Current Jobs.
Intro Text Optional introductory wording shown above the jobs.
URL Path The intended public path, for example jobs. The matching Experience Cloud route must also exist.
Detail Page The public Job Detail route, normally job-detail.
Page Size Number of results loaded per page. 20 is a sensible starting value.
Sort Field Fallback sort field when no metadata-defined default Sort option is configured.
Sort Direction ASC or DESC.
Count Label Template Optional wording such as {count} jobs found.
Dynamic Heading Template Optional heading that can change when selected search filters provide Heading Tokens.
SEO fields on this record The Page record also contains list-page SEO settings. These can be used for landing pages, but the more important Job Detail SEO configuration is covered separately in the Job Detail SEO guide.

2. Set the fixed filters — especially the publication rule

OW Job Board Filter records are rules applied by the Job Board itself.

Visitors cannot turn these filters off.

The most important fixed filter is the rule that decides whether a Job is allowed to appear publicly.

Setup Custom Metadata Types OW Job Board Filter Manage Records

Example: checkbox publication field

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

Example: status field

If the customer uses a text or picklist status instead of a checkbox, use the actual stored value.

For example:

Field API Name: Portal_Status__c
Operator: EQUALS
Filter Value: Open
Do not assume the publication value is “true”. It must match the customer's actual Salesforce field and stored value.

Supported fixed-filter operators include:

  • EQUALS
  • NOT_EQUALS
  • CONTAINS
  • GREATER_THAN
  • GREATER_THAN_OR_EQUALS
  • LESS_THAN
  • LESS_THAN_OR_EQUALS
Several fixed filters can be used together. For example, a permanent-jobs landing page could require: Published = true and Employment Type = Permanent. Only Jobs satisfying both conditions would appear.

3. Choose what appears on each Job card

OW Job Board Field records control the information displayed for each Job in the public list.

Setup Custom Metadata Types OW Job Board Field Manage Records

The package includes starting field records for the standard Jobs page.

Review them and change the field API names where necessary for the customer's Job object.

Typical information Display Type Layout Role
Job Title Text TITLE
Employment Type Text or Badge BADGE
Industry / Profession Text or Badge BADGE
Location Text LOCATION
Salary Currency PAY
Short Description Text SUMMARY

Important field settings

Field Meaning
Page Select the Job Board Page this field belongs to.
Field API Name The Salesforce field containing the value.
Visible Tick to display the field.
Display Order Controls the order of fields within their layout areas. Values such as 10, 20, 30 leave space for later additions.
Label Optional visitor-facing label.
Display Type How the value should be formatted, for example Text, Currency or Date.
Layout Role Where the value appears on the Job card.
Format Formatting where applicable. For Currency use an ISO code such as GBP.
Display Type and Layout Role are different. For example, a salary would normally use Currency as its Display Type and PAY as its Layout Role.

Salary or date ranges

If the customer has separate minimum and maximum values, OndaWorx can display them as one range.

Give both field records the same Group Name, then set:

  • minimum field → START
  • maximum field → END

Example:

£40,000 – £55,000

OW Job Board Search Filter records create the controls visitors use to refine the Job List.

Setup Custom Metadata Types OW Job Board Search Filter Manage Records

Typical search controls include:

  • Industry or Profession
  • Employment Type
  • Region
  • County
Setting Example
Page Jobs
Active Checked
Field API Name Industry__c
Label Industry
Filter Type PICKLIST
Operator EQUALS
Display Order 10
URL Parameter industry
For the simplest implementation, start with PICKLIST filters. OndaWorx metadata also supports TEXT, DATE and NUMBER filter definitions, but these should only be added when the installed release and public component have been tested for that requirement.

Dependent filters — for example Region → County

If the customer has a Salesforce field dependency such as Region controlling County, OndaWorx can use the same relationship.

  1. Configure the normal Salesforce field dependency on the Job object.
  2. Create the Region OndaWorx Search Filter.
  3. Create the County OndaWorx Search Filter.
  4. On the County Search Filter, set Parent Filter to the Developer Name of the Region Search Filter record.
  5. Leave Parent Filter blank on the Region record.
Parent Filter expects an OndaWorx Search Filter Developer Name. Do not enter the Salesforce field API name such as State_Region__c in that box.

5. Configure the Job Board sorting options

OW Job Board Sort records control the sorting choices available for a Job Board page.

Setup Custom Metadata Types OW Job Board Sort Manage Records

You can create options such as:

Label Field Direction URL Value
Newest Jobs CreatedDate DESC newest
Oldest Jobs CreatedDate ASC oldest
Job Title A–Z Position_Title__c ASC title-a-z
Sort field What it does
Page Select the Job Board Page this option belongs to.
Active Tick to make the sorting option available.
Label The wording visitors see.
Field API Name The Salesforce field used to order the jobs. It must be a sortable field.
Direction ASC or DESC.
Display Order Controls the order of the choices shown to visitors.
Default Tick the one option that should be used automatically.
URL Value A short value used to identify the option in the public URL/state, for example newest.
Only one Sort option can be the Default for each Job Board page. URL Values must also be unique for that page and should use only lowercase letters, numbers and hyphens.
You do not have to create lots of sorting options. For many Job Boards, a single default such as Newest Jobs is enough. Add more choices only if they are useful to candidates.

Creating extra landing pages

Once the main Jobs page is working, the same configuration can be used to create focused pages such as:

  • Permanent Jobs
  • Temporary Jobs
  • IT Jobs
  • Construction Jobs
  • Jobs in London
  • Jobs in Yorkshire

Each additional logical Job Board page has its own OW Job Board Page record and related records.

Worked example — Permanent Jobs

Create a Page record:

Setting Example
Label Permanent Jobs
Developer Name Permanent_Jobs
Object API Name OW_Job__c
Page Heading Permanent Jobs
URL Path permanent-jobs
Page Size 20

Then create the fixed filters:

Field Operator Value
Published__c EQUALS true
Employment_Type__c EQUALS Permanent

Finally create or copy the required:

  • Job Board Field records
  • Search Filter records
  • Sort records
Keep each page focused. A Permanent Jobs page normally does not need an Employment Type search filter because every result is already restricted to Permanent. Only add filters that are useful within that page.

Connect the landing page in Experience Builder

Creating the Custom Metadata record does not create a website page by itself.

In Experience Builder:

  1. Create or open the public page/route.
  2. Add the OndaWorx Job List component.
  3. Select the component.
  4. Set Job Board Page Developer Name to the exact Developer Name of the Page record, for example Permanent_Jobs.
  5. Publish the site.
URL Path and Experience Cloud route must agree. Saving permanent-jobs in the Page record does not itself create an Experience Cloud page or route.

Test the Job List while signed out

Open the published page in a private/incognito browser while signed out of Salesforce.

  • a published eligible Job appears
  • an unpublished Job does not appear
  • the title and other Job card information are correct
  • each search filter changes the results correctly
  • Clear Filters works
  • selected filters are reflected correctly when the page is refreshed
  • dependent filters such as Region and County work correctly
  • the default sort is correct
  • any additional Sort choices work
  • the View Job link opens the correct Job
  • the page works on a mobile-sized screen
Job List setup complete Once the main Jobs page works correctly while signed out, continue to Configure Job Detail .

Advanced field reference

Most implementations can be completed using the instructions above. The sections below provide a fuller reference for administrators and implementation partners who need to customise the Job Board further.

OW Job Board Page — field reference
Field Purpose
Active Controls whether this logical Job Board page can be loaded.
Object API Name Exact API name of the Job object. Related OndaWorx field references must belong to this object.
Page Title Configured title for the logical Job Board page.
Page Heading Default visible heading above the results.
Intro Text Optional introductory copy above the Job List.
URL Path Intended relative path. The corresponding Experience Cloud route must also exist.
Detail Page Relative Job Detail route.
Detail URL Field Optional precomputed Job Detail URL field. Leave blank for the standard implementation unless required.
Page Size Default number of Job records per page.
Sort Field Fallback default sort field when a metadata-defined default Sort option is not available.
Sort Direction ASC or DESC.
SEO Title Configured search title for the list page.
SEO Description Configured meta description for the list page.
Canonical URL Optional preferred absolute URL for the list page where the installed release uses this setting.
Count Label Template Results wording using {count}, for example {count} jobs found.
Dynamic Heading Template Optional heading built from Search Filter Heading Tokens.
Apply Mode Apply behaviour where used by the relevant consuming component.
Apply Target Optional apply anchor or URL where supported.
Apply Label Optional wording for the apply action where rendered.
OW Job Board Filter — field reference
Field Purpose
Page Select the Job Board Page this rule belongs to.
Field API Name Salesforce Job field used by the fixed rule.
Operator The comparison OndaWorx performs.
Filter Value The actual stored Salesforce value to compare against.
Sequence Optional order of the configured fixed conditions.
Active Only active filter records are applied.
OW Job Board Field — field reference
Field Purpose
Page Select the Job Board Page this field belongs to.
Field API Name Salesforce Job field containing the value.
Visible Controls whether the value is displayed.
Display Order Controls ordering within the configured layout area.
Label Optional visitor-facing caption.
Display Type Text, Badge, Currency or Date formatting as appropriate.
Format Additional formatting such as GBP for Currency.
Layout Role Controls where the value appears on the Job card.
Group Name Shared identifier used to display related values as a range.
Group Position START, END or ITEM.
Group Key Leave blank for a normal implementation unless specifically required.

Layout Roles

Role Used for
TITLE Main Job title and card link.
BADGE Pills such as Employment Type or Industry.
LOCATION Location information below the title.
DATE Date information or date range.
PAY Salary or pay information.
SUMMARY Short description paragraph.
DETAIL Additional label/value information.
OW Job Board Search Filter — field reference
Field Purpose
Page Select the Job Board Page containing this search control.
Active Controls whether the search filter is available.
Field API Name Salesforce Job field being searched.
Label Visitor-facing filter label.
Display Order Position among the search controls.
Filter Type Metadata supports PICKLIST, TEXT, DATE and NUMBER.
Operator Search operator such as EQUALS, CONTAINS or INCLUDES.
Parent Filter Developer Name of the parent OndaWorx Search Filter record.
Heading Token Optional token used by the Page Dynamic Heading Template.
URL Parameter Stable public query-string key such as county.
OW Job Board Sort — field reference
Field Purpose
Page Select the Job Board Page this Sort option belongs to.
Active Controls whether the option is available.
Label Visitor-facing description of the sort.
Field API Name Sortable Salesforce field on the configured Job object.
Direction ASC or DESC.
Display Order Order of the options shown to visitors.
Default Tick only one active Sort option per Page as the default.
URL Value Optional unique public value using lowercase letters, numbers and hyphens.

Common setup problems

Problem Check first
No jobs appear Fixed filters, actual stored Salesforce values, active Page, public field access and a known published test Job.
Unpublished jobs appear Publication fixed filter is present, Active and uses the correct field/value.
A Job card value is missing Field API Name, Visible, Guest User field access, sample data, Display Type and Layout Role.
Salary appears without £ Display Type is Currency and Format is GBP.
Minimum and maximum salary appear separately Both PAY records have the same Group Name and use START/END.
County filter does not depend on Region Salesforce field dependency and OndaWorx Parent Filter Developer Name.
Sort configuration fails Sort field is sortable, Direction is ASC/DESC, only one option is Default and URL Values are valid and unique.
View Job opens the wrong page Experience Cloud Job Detail route and Job List component configuration.

Continue: Configure Job Detail →

Guide updated 10 October 2026. Follow the Installation and Custom Metadata layout guides before completing this configuration.