Check the Custom Metadata layouts
OndaWorx is configured using Salesforce Custom Metadata. Before you begin changing the Job Board, check that the configurable fields are visible when you create or edit the OndaWorx Custom Metadata records.
← Back to Start HereWhat is Custom Metadata?
Custom Metadata is simply where OndaWorx stores its configuration.
Instead of changing code, an administrator can use these records to tell OndaWorx things such as:
- which Salesforce object contains the jobs
- which fields should appear on a job card
- which filters visitors can use
- which jobs are allowed to appear publicly
- how Job Detail pages are displayed
- how location information is displayed
- how SEO and JobPosting information is created
- how the public Application Form behaves
You do not need to understand the technical structure of Custom Metadata to configure OndaWorx. The remaining guides tell you exactly which records to create and what each setting does.
First, check whether you need to do anything
Open one of the OndaWorx Custom Metadata Types and look at an existing record or click New.
If you can see the normal OndaWorx configuration fields, the layout is already prepared.
If important configuration fields are missing, follow the steps below.
How to add missing fields to a Custom Metadata layout
-
1
Open Custom Metadata Types
In Salesforce Setup, search for and open Custom Metadata Types.
-
2
Click the Custom Metadata Type label
Find the OndaWorx metadata type you want to check and click its Label. Do not click Manage Records for this step.
-
3
Open its Page Layout
Scroll to Page Layouts and open the existing layout.
-
4
Click Edit
Salesforce will open the layout editor. The available fields appear in the field palette at the top.
-
5
Add the missing OndaWorx fields
Drag any missing customer-configurable OndaWorx fields onto the Information section of the layout.
-
6
Save the layout
Click Save.
-
7
Check the result
Return to Manage Records and open or create a record. The missing configuration fields should now be visible.
Which Custom Metadata Types should I check?
You do not need to edit every layout simply because it appears in this list. Check the types used by your implementation and make sure their configurable fields are visible.
| Custom Metadata Type | What it controls |
|---|---|
| OW Job Board Page | The main configuration for a Job Board page, including the Job object, headings, publication rules and general page behaviour. |
| OW Job Board Field | Which Job fields appear on the cards in the public Job List and how those fields are displayed. |
| OW Job Board Filter | Fixed rules that decide which Job records are allowed onto a particular Job Board page. |
| OW Job Board Search Filter | Search and filter controls that visitors can use on the public Job Board. |
| OW Job Board Sort | The sorting choices available to visitors and the default order in which jobs appear. |
| OW Job Board Detail Field | Which fields appear on the individual Job Detail page and how they are displayed. |
| OW Job Location | The Job Location section, including which location fields are used and the optional map button settings. |
| OW Job Detail SEO | SEO settings for public Job Detail pages, including page metadata, canonical URLs and JobPosting structured data. |
| OW Job SEO Employment Map | Maps the customer's employment-type values to the employment types used in JobPosting structured data. |
| OW Job Board Route Dimension | Advanced URL and dynamic landing-page configuration. Most first implementations do not need to change this. |
| OW Application Context | Controls the public Application Form context, including privacy details and application behaviour. |
| OW Application Field Mapping | Maps information collected by the Application Form to the Salesforce Application fields. |
| OW Application Target | Defines the Salesforce target used by the Application submission process. |
Which fields should I add?
Add the OndaWorx configuration fields that an administrator may need when maintaining that metadata type.
In most cases this means adding the available packaged fields that describe:
- the Salesforce object or field being used
- whether the configuration is active
- display labels and headings
- display types and formatting
- filter values and operators
- sort order
- URLs and route settings
- SEO settings
- application settings
Fields you normally do not need to change
Salesforce also displays system and managed-package fields. These are not normally part of the customer's OndaWorx configuration.
-
Protected Component /
IsProtected - Namespace Prefix
- Created By
- Last Modified By
- other Salesforce system-maintained fields
Label and Developer Name should remain available because Salesforce uses them to identify each Custom Metadata record.
Example
Suppose you open:
If you can see the record name but cannot see settings such as the Job field, label, display type, format or display order, go back to:
Add the missing OndaWorx fields, save the layout and return to Manage Records.
Before continuing
You are ready to continue when:
- the OndaWorx Custom Metadata Types you will use have been checked
- the configuration fields described in the OndaWorx guides are visible
- you can open Manage Records and create or edit configuration records normally
- you have not created duplicate fields simply because a packaged field was missing from the page layout
- you have not changed packaged field API names