
💡 Introduction
One of the most common customization requests in Oracle Recruiting Cloud (ORC) Career Sites is the ability to rename section headings or fields on the job requisition display page. While organizations want more control over the language and branding presented to candidates, Oracle does not provide a native option to rename fields only within Career Sites without affecting other areas of the system.
⚠️ The Challenge
- The User Interface Text tool in Oracle Fusion allows renaming text, but changes apply system-wide, affecting recruiters, hiring managers, and internal dashboards.
- Customers want to rename fields only in Career Sites while keeping the original field names intact elsewhere.
- Oracle does not provide a configuration setting to make these changes exclusively for external candidate views.
🔍 Real-World Scenarios Where UI Text Tool Fails
While the User Interface Text tool is useful for global text updates, it falls short when changes are needed only within the Career Site. Here are some real-world examples where organizations struggle with UI customization:
- Renaming “Job Info” to “Job Details” – Candidates see Job Info as a vague label, whereas “Job Details” is clearer.
- Changing “Apply” to “Start Application” – Some companies prefer a more engaging call to action.
- Updating “Resume” to “CV” – In some regions, “CV” is the preferred term, but recruiters internally still use “Resume”.
- Modifying “Phone Number” to “Mobile Number” – To avoid confusion for candidates who only have a mobile number.
- Changing “Desired Salary” to “Expected Compensation” – A better alignment with salary transparency policies.
🔍 Cases Where UI Text Tool is Not Needed
For some fields within the requisition display page, Career Sites, or job application flow, Oracle Recruiting Cloud allows lookup-based configurations to change field values at the setup level. These cases do not require a workaround, as changes can be applied directly in Oracle Fusion settings.
However, this JavaScript-based workaround is specifically for seeded fields where no configuration option exists except the User Interface Text tool.
🚀 The Workaround: JavaScript-Based Approach
Since ORC Career Sites allow JavaScript customization within Themes, we can dynamically rename fields only on the Career Site job requisition page without impacting internal Fusion pages. This provides an effective workaround for businesses looking to tailor their candidate experience without disrupting internal workflows.
For the purpose of this blog, we will take the “Category” filter as an example and demonstrate how to rename it using JavaScript without using the User Interface Text tool.
Note: To implement this solution successfully, a basic understanding of JavaScript is required.
🎯 Working Example: Renaming “Category” to “ORG”
A common example of this challenge is the “Category” filter, which appears as a standard field on the job requisition display page. Many organizations want to rename it to something more relevant, such as:
- “ORG”
- “Department”
- “Business Unit”
- “Functional Area”
By following the JavaScript approach outlined below, organizations can rename this section only in Career Sites, ensuring a seamless experience for candidates while keeping internal labels unchanged.
📝 Step-by-Step Implementation
🔍 Step 1: Navigate to the Career Site and Inspect the Field
- Open Oracle Recruiting Cloud Career Site and navigate to the page where you want to rename the field.
- Locate the “Category” filter that needs to be renamed.
- Right-click on the field title and select Inspect from the pop-up menu.
- The browser’s Developer Tools panel will open, displaying the HTML code for the field.
- Identify the class or ID associated with the label that needs renaming.
<span class="search-filters__header-content" data-bind="css: { 'search-filters__header-content--selected': selectedCount }" aria-hidden="true">
<!-- ko text: title -->Categories<!-- /ko -->
<span class="search-filters__pill-counter search-filters__pill-counter--vertical search-filters__pill-counter--hidden" data-bind="text: selectedCount, css: { 'search-filters__pill-counter--hidden': !selectedCount }" aria-hidden="true">0</span>
</span>




🔧 Step 2: Build the JavaScript Code to Rename the Field
- Create a JavaScript snippet that dynamically renames the field by targeting the identified HTML class or ID.
- Below is the JavaScript code to rename “Category” to “ORG”:
document.addEventListener("DOMContentLoaded", function() {
function updateCategoryText() {
let categoryElements = document.querySelectorAll(".search-filters__header-content");
categoryElements.forEach(function(element) {
// Find the first child node that contains "Categories"
element.childNodes.forEach(node => {
if (node.nodeType === Node.TEXT_NODE && node.textContent.trim() === "Categories") {
node.textContent = "Org";
}
});
});
}
// Run initially when the page loads
updateCategoryText();
// Use MutationObserver to detect when Oracle re-renders the page dynamically
let observer = new MutationObserver(function(mutations) {
mutations.forEach(function(mutation) {
updateCategoryText();
});
});
observer.observe(document.body, { childList: true, subtree: true });
// Run periodically to ensure Knockout.js doesn’t reset the text
setInterval(updateCategoryText, 500);
});
🌍 Step 3: Place the JavaScript in ORC Career Site
- Navigate to: ORC Career Site Configuration ➔ Themes.
- Open the current active theme.
- Locate the section for Custom JavaScript.
- Paste the JavaScript snippet from Step 2 into the placeholder section.
- Enable the checkbox to activate JavaScript functionality.
- Click Publish to save and apply the changes.

🌟 Step 4: Verify and Validate the Change📅 Placeholder for Screenshot (Updated Career Site displaying the renamed field)
- Refresh the Career Site job requisition page.
- Confirm that “Category” is now displayed as “ORG”.
- Test across different browsers and devices to ensure consistency.
- If needed, adjust the CSS selector to match the actual class structure in your Career Site.

🚀 Final Thoughts
By leveraging JavaScript customization, we can rename specific fields only on the Career Site, without altering internal recruiter-facing interfaces. This workaround is ideal for organizations that want a branded and candidate-friendly experience without impacting other Oracle Recruiting Cloud functionalities.
📢 What Do You Think?
- Have you faced similar challenges in ORC Career Sites?
- Would a native Oracle solution be more beneficial?
💬 Drop your thoughts in the comments below and let’s start a discussion! 🚀






Leave a Reply