Scheduled Processes in Oracle Recruiting Cloud
Scheduled processes are available for specific business needs in Oracle Recruiting Cloud. You can schedule and run processes in the Scheduled Processes work area (Tools > Scheduled Processes).
|
Process Name |
Description |
Recommended Frequency |
|---|---|---|
|
Classify Contingent Workers in Recruiting |
Classifies contingent workers as external candidates or internal candidates in the recruiting process. When contingent workers are classified as internal candidates, they submit job applications with Opportunity Marketplace. When they're classified as external candidates, they apply using the external candidate experience site. |
Run this process when there's a change to how contingent workers are classified. For example, internal versus external using the IRC_TREAT_CWK_AS_EXTERNAL indicator. |
|
Complete the Recruiting Process |
Performs automatic closeout activities when a person is hired for a job or an assignment, or when a person is terminated from employment. Closeout activities can include changing their candidate type in Recruiting, copying data into their Person/Talent Profile, and copying attachments into Documents of Record. |
Daily |
|
Convert Candidate Search Logs for Reporting Purposes |
Converts candidate search logs into readable columns for reporting purposes. This scheduled process is used for OTBI reporting, for the Recruiting - Recruiting Real Time subject area. |
Manually run as needed, in preparation to generate OFCCP reports. |
|
Delete Archived Candidate Searches |
Deletes entries in the candidate search archive table that are older than the specified number of years. This process helps cleaning the database when data is no longer needed. This has an impact on the OTBI Recruiting subject area in the candidate search dimension. |
Manually run when such data is no longer required. |
|
Generate Recruiting Job Offer Letters |
Tries to regenerate a recruiting job offer letter if BI Publisher was unable to generate it when a job offer was accepted by the candidate. |
Manually run as needed for a specific job offer, by providing a requisition number and a candidate number in the Basic Options area. |
|
Index Candidate Attachments |
Indexes candidate attachments for use in candidate searches. |
Run at a regular frequency. It's recommended to schedule every 15 minutes. |
|
Load and Index Candidates |
This scheduled process creates the index for searching all candidates. When the process is run using the Drop and Recreate indexing mode, it deletes the existing index, then reindexes all the data. During this time, candidates might not be found or intermittently users can't see any candidates. Note that the Upgrade Current Index indexing mode creates no downtime. Parameters to use:
Note: The name of the person signing in to run this process
must not exceed 32 characters. This is the maximum length set in IRC_CANDIDATES
table, LAST_UPDATE_LOGIN column. To change this limit, go to Tools
> Security Console > Users.
|
One time when Oracle Recruiting is set up, or when you find something is incorrect and you want to start clean. |
|
Load and Index Job Requisitions |
This scheduled process creates the index for searching all job requisitions. When the process is run using the Drop and Recreate indexing mode, it deletes the existing index, then reindexes all the data. During this time, jobs might not be found or intermittently users can't see any jobs. Note that the Upgrade Current Index indexing mode creates no downtime. Parameters to use:
Note: The name of the person signing in to run this process
must not exceed 32 characters. This is the maximum length set in IRC_CANDIDATES
table, LAST_UPDATE_LOGIN column. To change this limit, go to Tools
> Security Console > Users.
|
One time when Oracle Recruiting Cloud is set up, or after more job requisitions are added by a data load, or when you find something is incorrect and you want to start clean. |
|
Load and Index Master Geography Hierarchy (previously called Load and Index TCA Geographies) |
This scheduled process creates the index for the master geography hierarchy. Parameters to use:
Prerequisites: Set up the Geogrgaphy Hierarchy Structure and Geography Hierarchies. Note: The name of the person signing in to run this process
must not exceed 32 characters. This is the maximum length set in IRC_CANDIDATES
table, LAST_UPDATE_LOGIN column. To change this limit, go to Tools
> Security Console > Users.
|
One time when Oracle Recruiting is set up. |
|
Load Workers into the Candidate Table |
This scheduled process brings employee records (employees, contingent workers, ex-employees, ex-contigent workers) from Core HR into the candidates table (IRC_CANDIATES) in Oracle Recruiting Cloud. This scheduled process allows employees and contingent workers to search for jobs internally and to refer other employees as internal candidates to a job requisition. This scheduled process isn't associated with any alerts and there are no emails triggered to the employees when the process is run. There are no options to choose which internal candidates are to be imported into Recruiting. This process will look at any active employees in HR. Note: The name of the person signing in to run this process
must not exceed 32 characters. This is the maximum length set in IRC_CANDIDATES
table, LAST_UPDATE_LOGIN column. To change this limit, go to Tools
> Security Console > Users.
Note: You should run this scheduled process for people
hired outside of Recruiting, for example, those hired directly in HR. The
Maintain Candidates and Job Requisitions for Search scheduled process will
then index them for Recruiting.
|
One time when Oracle Recruiting is set up. |
|
Maintain Candidates and Job Requisitions for Search |
Incrementally updates the search indexes for job requisitions, candidates, and locations. Common for requisitions, locations, candidates. |
Every 15 minutes |
|
Manage Expired Interview Feedback Requests |
Updates the interview feedback request status to expired when the expiry date is past the current date. |
Daily |
|
Manage Recruiting Job Offer Letters (previously called Restore Recruiting Job Offer Letter Layouts) |
Cleans up any unused recruiting job offer letter layouts in BI Publisher. On demand, it imports offer letter layouts again in BI Publisher from the Job Offer Letter Templates in the Recruiting Content Library if any were mistakenly deleted. |
For customers using Adjusted Offer Letters, the frequency should be every 15 minutes. It's not usually necessary to restore job offer letter templates from the Recruiting Content Library, so the parameter in the Basic Options section of this scheduled process should be set to No. You can manually run this scheduled process with the parameter set to Yes if any offer letter templates were manually removed from BI Publisher by mistake. This might also be needed after the environment is updated. |
|
Perform Batch Recruiting Actions |
Performs actions on many objects selected by a recruiting user. Note: Consider the limit of 40 characters for the user name of the recruiting
user performing the bulk action. This applies to bulk actions like moving
job applications.
|
No scheduling needed. Occurs automatically whenever a user takes an action on many candidate job applications at once. |
|
Perform Recruiting Candidate Selection Process Actions |
Performs pending actions set to automatically be executed in candidate selection processes. |
Every 5 minutes |
|
Perform Recruiting Candidate Selection Process Offer Actions (previously called Complete the Candidate Move to HR) |
Performs pending offer and HR-related actions in the candidate selection processes. |
Every 15 minutes Relevant for extending and accepting offers, and for actions triggered during the HR - Pending Automated Processing and Terminate Assignments statuses. Most of these actions are automatically performed immediately, but might occasionally need to be retried. |
|
Prepare Campaign Email |
Populates the recruiting campaign audience list and the campaign's email subject, body text, and tokens for each recipient. This process is used by job alerts to generate the recipient list. However, the Send Campaign Email process is what actually sends the job alerts out. |
Every 30 minutes |
|
Publish Job Requisitions |
Publishes or removes job requisitions based on a start date and end date. It also verifies if the automatic unpost condition is met. |
Every 15 minutes |
| Purge Processed Internal Recruiting Data |
Purges processed internal non-transactional recruiting data older than 90 days. It also purges candidate tracking data older than 180 days, data available in the Recruiting - Candidate Tracking Real Time subject area, and campaign recipient information of closed campaigns older than 180 days. The later is impacting Recruiting – Sourcing Real Time subject area. Internal non-transactional recruiting data is non-transactional recruiting transient data used internally for tracking or processing expired data. This non-transactional data isn't visible to users in the application or OTBI. This job is to be scheduled and run periodically by purging aged and expired data to help optimize application performance. As examples:
|
Weekly for optimal performance. Schedule when usage on the system is low. For example, scheduling every Saturday at 10:00 pm. |
|
Recruiting Job Offer Expiration Date Alert |
Sends alerts about recruiting job offer's expiration date. |
Daily |
|
Send Campaign Email |
Sends recruiting campaign emails to the campaign audience. This scheduled process sends out job alerts. |
Every 30 minutes |
|
Send Candidate Screening Requests to Partners (previously called Send Candidate Assessment Requests to Partners) |
Sends requested candidate assessments and tax credit screening to selected partners. Sends all screening notifications to all partners supporting notifications. The process sends notifications to the partner for job application or candidate deletion for example, and notifications for REST end points if configured for the partner. It doesn't trigger screening services for background checks. |
Every 10 minutes |
| Send Draft Application Reminder Notifications and Automatically Confirm Applications |
Sends notifications to recently saved draft job applications. Two notifications are sent: after 60 minutes and 3 days of candidate's inactivity. This scheduled process is also used for confirming completed job applications that were interrupted because of connectivity issues, or other technical reasons, during confirming applications by candidates. |
Every 5 minutes |
|
Send Interview Feedback Respondent Request Expiring Notification |
Sends a reminder notification to feedback respondent a day before the feedback request expires. |
Daily |
|
Send Interview Reminder Notification |
Sends the interview reminder notifications to candidates and interviewers 24 hours before the scheduled interview. |
Daily |
|
Send Job Application Notification |
Sends the customer configured automated job application notifications to candidates, recruiters, and hiring managers when job applications are in a specified phase and state in the candidate selection process. This process also sends out the recruiter and hiring manager review notifications configured in the candidate selection process. |
Every 5 minutes Scheduling every 5 minutes could cause the recruiter or hiring manager review notification to be sent more often than once per day (as it was originally intended). |
|
Send Requisition Posting Expiration Date Notification |
Sends notification to agents about the requisition posting expiration date. |
Daily |
| Synchronize Interview Details with External Calendars | This scheduled process is used for capturing interviewer responses from integrated calendar systems, like Office 365. | Every 10 minutes |
|
Synchronize LinkedIn Recruiter System Connect |
Synchronizes data between LinkedIn Recruiter System Connect and Oracle Recruiting. |
Every hour |
| Synchronize Recruiting Activity Center Action Item | Generates and updates the action items in the Recruiting
Activity Center. It's not required to set these parameters to run or schedule the process:
The Subscriber Type Code to Process parameter is useful if changes are made to the activity configuration in the Setup and Maintenance work area. For example, the activity is enabled or disabled, or the timing of the triggering of the condition is changed (was predefined as 3 days but you changed it to 1 day). Choosing just the subscriber code for the rules that were changed would reprocess the activities for just that object potentially saving time compared to a full reprocessing of all activities. |
Daily |
|
Synchronize Recruiting Data for Candidate Recommendations |
Synchronizes recruiting data for candidate recommendations. |
Every hour |
|
Track Campaign Email Delivery |
Tracks the delivery status of recruiting campaign emails. |
Every 30 minutes |
|
Update Date When Last Retrieved |
Updates the date when candidates were last retrieved in a candidate search. |
Daily, to support generating reports for OFCCP. |
|
Update Job Application Questionnaire |
Updates job application questionnaire for job requisitions when context such as organization, location, job function, job family are changed in the question library. |
Daily |