Oracle Recruiting Cloud Fast Formulas — The Fast Formula Guide Every HCM Cloud Consultant Needs

CSP formulas are the automation engine behind Oracle Recruiting Cloud. They evaluate conditions at every stage of the candidate journey and decide what happens next.

Every formula follows the same skeleton: read DBIs and context, run your logic, return Y (condition met) or N (skip). The rest of this post shows you how to build each of these patterns.

Formula type: Recruiting Candidate Selection Process. Return CONDITION_RESULT with Y to indicate the condition is met. Optionally return CONDITION_MESSAGE for debugging (max 255 chars).

DBI = a named variable that reads from Oracle's database. Context = tells the engine which record to fetch. You never write SQL in the formula.

Every DBI for Recruiting CSP and Computed Field formulas across 16 domains. A = Array (use DBI[i] + .EXISTS(i)), D = Date, N = Number. Source: MOS 2723251.1, Release 23C.

When you configure a CSP action to fire on Interview Updated, Oracle doesn't just tell you "something changed." It passes a specific operation value into the formula's context, telling you exactly what happened to the interview. This is not a DBI — you can't reference it like a database item. You read it using GET_CONTEXT.

The value returned will be one of the following, depending on what the recruiter or candidate did:

In practice, COMPLETED is the one you'll use in 90% of interview-based CSP formulas. The typical pattern is: check if the operation is COMPLETED, then optionally verify the feedback score or schedule status using the Interview DBIs before returning Y.

One important detail — these context values are only available when the CSP action is triggered by an Interview Updated event. If your formula is attached to a different trigger (like a manual move or assessment completion), GET_CONTEXT will return the default value you specified.

When no seeded DBI exists, build a Table-type Value Set (Module: Recruiting). Specify FROM, Value Column, and WHERE with bind params like {PARAMETER.SUBMISSION_ID}.

If either job is not scheduled, formulas and notifications silently do nothing.

Other types: Recruiting Job Requisition (auto-unpost) and Recruiting Job Application Computed Field (grid values via CONDITION_MESSAGE + EFF).

This formula loops through all prescreening answers for a job application. If the candidate actually answered at least one question (not just skipped it), the formula returns Y. This is used to auto-advance candidates who completed the prescreening questionnaire.

DEFAULT_DATA_VALUE — Prescreening DBIs are arrays. When a candidate skips a question, Oracle doesn't leave the field null. It fills it with the default value you specify here (a space character). This is important for how we check the data later.

WHILE .EXISTS(j) LOOP — Loops through each prescreening question. Index 1 is the first question, index 2 is the second, and so on. When .EXISTS returns FALSE, we've gone past the last question and the loop ends.

WAS_DEFAULTED() = 'N' — This is the key check. WAS_DEFAULTED returns 'Y' if the value came from the DEFAULT (meaning the candidate skipped the question), and 'N' if the value is real data (meaning the candidate actually answered). When it returns 'N', we know we have a genuine response.

Early RETURN — The moment we find one valid answer, we return Y immediately and stop. No need to scan the rest. The message tells you exactly which question had the response — useful when a recruiter asks "did the formula actually check the answers?"

Fallback RETURN — If the loop finishes without finding any real answer, the formula returns N. The message confirms how many questions were checked, so you can verify the formula ran through the entire questionnaire and didn't exit early by mistake.