- Revision History
- Overview
- Feature Summary
- Recruiting
-
- Recruiting
- Candidate Experience
- Candidates and Candidate Job Applications
-
- Advanced Job Application Filters
- Deep Link to the Find Candidate Page
- Latest Job Applications and Interactions in Grid View in Search Results List
- Manually Send Request Information Notifications
- Prefill Legislative Info in Job Applications
- Select All Check Box for Bulk Actions on Search Results List
- Simple One-Step Process to Change Start Date of Candidates
- Candidate Interviews
- Candidate Pools
- Job Requisitions
- Job Offers
- Screening Services
- Opportunity Marketplace
- Autocomplete Rules
- HCM Data Loader
- HCM Extracts
- Recruiting Replaced or Removed Features
- Recruiting Booster
- Transactional Business Intelligence for Recruiting
- Recruiting
- IMPORTANT Actions and Considerations for Recruiting
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Module | Feature | Notes |
---|---|---|---|
26 MAY 2023 | Created initial document. |
HCM Cloud applications have two types of patches you can receive that are documented in this What’s New:
- Release Updates (23A, 23B, 23C, and 23D)
- Optional Monthly Maintenance Packs to each update
It is important for you to know what Release Update your environment is on. You can find this in your Cloud Portal.
____________________
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our products better, please let us know. To enter an idea go to the Ideas Lab on Oracle Customer Connect. In this document wherever you see the light bulb icon after the feature name it means we delivered one of your ideas.
____________________
Suggested Reading for all HCM Products:
- HCM Common What's New - In this What's New you will find feature that are used across applications.
- Human Resources What’s New – In the Global Human Resources section you will find features on the base application in which other application are built upon.
NOTE: Not all Global Human Resource features are available for Talent and Compensation products.
- Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1). These documents identify bug fixes and possible known issues. You will also need to review these documents based in the release update version you are currently on or will be moving to.
- Oracle Help Center – Here you will find guides, videos and searchable help.
- Release Readiness – New Feature Summary, What’s New, Feature Listing Spreadsheet, Spotlights and Release Training
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.
We’re here and we’re listening. If you have a suggestion on how to make our products better, please let us know. To enter an idea go to the Ideas Lab on Oracle Customer Connect. In this document wherever you see the light bulb icon after the feature name it means we delivered one of your ideas.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
---|---|---|---|---|---|---|
Feature |
Report |
UI or |
UI or |
|
||
Simplified Activation Steps to Set Up Oracle AI Apps for Talent Management |
||||||
Oracle Recruiting Cloud provides tools for hiring managers and recruiters to source and nurture candidates, create and manage job requisitions, screen and select candidates, create and manage job offers, and onboard new employees into the organization. It also provides career sites for employees and external candidates to search, discover and apply to jobs using a frictionless application process.
Simplified Activation Steps to Set Up Oracle AI Apps for Talent Management
Set up Oracle AI Apps for Talent Management with the new and simplified activation steps. You can now activate the AI Apps feature you want from the Application Administration page in your Oracle Cloud application.
Here’s the Application Administration page where you can select the AI Apps features you want to activate.
With this enhancement, activating AI Apps features is much simpler.
Steps to Enable
To activate AI Apps for Talent Management, go to the Tools tab and click the quick action AI Apps Administration. For details, see Activate Oracle AI Apps for Talent Management.
Tips And Considerations
- On the Application Administration page, from the Product Family list, select Human Capital Management to view only features within Oracle HCM Cloud. This makes it easier to find the feature you’re looking for.
- You may have to activate more than one feature on the Application Administration page for a feature to work. For example, to activate Dynamic Skills, you also have to activate AI Talent Best Match. For details, see Welcome to Oracle AI Apps for Talent Management.
- When you complete the activation steps for any AI Apps feature, it takes about 5 to 20 minutes for the status to change to Active.
Key Resources
Oracle Recruiting Booster enables hiring managers and recruiters to engage candidates at scale via conversational experiences and two-way messaging; create and manage hiring events with registration flows, pre-screening questionnaires and scheduling capabilities; manage shared interview schedules, sync with calendars to automate interview scheduling, distribute interview guides and collect feedback from the interviewers. This product requires a separate license.
Resume parsing is now available in Recruiting Booster subscription.
With this enhancement, customers who subscribe to Recruiting Booster will save cost on the resume parsing feature. The enablement process is simplified as there is no need to find a partner and sign a direct agreement. Everything is managed through Oracle by entering a service request.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
The Service Request (SR) must be logged under the “Oracle Fusion Recruiting Booster Cloud Service” SKU for appropriate routing.
Tips And Considerations
Several languages are supported. Verify which languages you want to implement. Additional languages might be added later on.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Module | Feature | Notes |
---|---|---|---|
28 APR 2023 | Created initial document. |
HCM Cloud applications have two types of patches you can receive that are documented in this What’s New:
- Release Updates (23A, 23B, 23C, and 23D)
- Optional Monthly Maintenance Packs to each update
It is important for you to know what Release Update your environment is on. You can find this in your Cloud Portal.
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our products better, please let us know. To enter an idea go to the Ideas Lab on Oracle Customer Connect. In this document wherever you see the light bulb icon after the feature name it means we delivered one of your ideas.
____________________
Suggested Reading for all HCM Products:
- HCM Common What's New - In this What's New you will find feature that are used across applications.
- Human Resources What’s New – In the Global Human Resources section you will find features on the base application in which other application are built upon.
NOTE: Not all Global Human Resource features are available for Talent and Compensation products.
- Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1). These documents identify bug fixes and possible known issues. You will also need to review these documents based in the release update version you are currently on or will be moving to.
- Oracle Help Center – Here you will find guides, videos and searchable help.
- Release Readiness – New Feature Summary, What’s New, Feature Listing Spreadsheet, Spotlights and Release Training
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
---|---|---|---|---|---|---|
Feature |
Report |
UI or |
UI or |
|
||
Oracle Recruiting Cloud provides tools for hiring managers and recruiters to source and nurture candidates, create and manage job requisitions, screen and select candidates, create and manage job offers, and onboard new employees into the organization. It also provides career sites for employees and external candidates to search, discover and apply to jobs using a frictionless application process.
Questions Available in Job Application Print Feature
When you print a job application using the Print action, you can now select these 3 items:
- Prescreening
- Request More Info Questionnaires
- Interview Questionnaires
By default, these 3 options aren't selected.
With this enhancement, users have the entire job application content in a single file, without having to navigate back to the application to retrieve answers to questions.
Steps to Enable
You don't need to do anything to enable this feature.
Recommended Jobs Based On Resume
Allow candidates to upload their resumes, and receive a recommended jobs list that is weighted and tailored for their current job title, location, and skills. Candidates can either drag-and-drop their resumes to the new widget, or they can click Upload Resume.
Once uploaded, a congratulations message is displayed, and candidates are shown weighted job results based on their current job title, location, and skills.
Candidate experience first looks for job title, then location, and then skills. Let's say a candidate uploads a resume that states that they are a Product Manager located in New York. The jobs that display higher in the list will be those for product managers with the job location in New York.
Click the View All Jobs button to reset the search results.
Resume information is only stored on a per-session basis. Resumes aren't permanently stored. Once candidates click View All Jobs, in order to see weighted search results again, they would need to re-upload their resumes.
Admins can configure the look and design, as well as the call to action and success message for the widget.
Typography and style are configurable. As with other widgets, the messaging typed here is supported by the translations tab.
This feature reduces friction for the candidate performing a job search by displaying recommended jobs based on their uploaded resume/CV.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- This feature is enabled by default.
- In order to use this feature, your site must have the Resume Parsing functionality set to active. If Resume Parsing isn't active, the feature is still enabled, but it won't display.
- The element can be placed on any page except for the Job Details page.
Key Resources
For additional information on customizing career sites, see https://rebrand.ly/yeejip6.
Oracle Recruiting Booster enables hiring managers and recruiters to engage candidates at scale via conversational experiences and two-way messaging; create and manage hiring events with registration flows, pre-screening questionnaires and scheduling capabilities; manage shared interview schedules, sync with calendars to automate interview scheduling, distribute interview guides and collect feedback from the interviewers. This product requires a separate license.
Notify Hiring Team of Inbound SMS Replies from Candidates
Hiring team members can now be notified through email immediately when candidates send replies to their SMS messages. These emails notifications are sent in real-time as soon as an SMS is received from the candidate.
A conversation is initiated when the hiring team sends an SMS to the candidate. When the candidate replies to the SMS within a specific duration configured by the administrator, which is known as the active conversation period, an email notification is sent to the recruiter, hiring manager, or collaborators, or to all of them, depending on the configuration settings.
In addition, if you send an SMS message from the candidate’s profile or through candidate pools, you will be notified when the candidate sends a reply SMS.
The email notification contains a deep link that takes the recipient to the Messages tab in Recruiting.
Email Notification Template
A new notification template is available in the Recruiting Content Library in the Setup and Maintenance work area. This template is used in email notifications sent to hiring team members:
- Content Item Name: Email Notification To Hiring Team for Incoming SMS
- Category: Hiring Team Notifications For Incoming Candidate Messages
- Code: ORA_INBOUND_SMS_NOTIFICATION
Webhook Functionality
Email notifications are sent in real-time using the Webhook functionality, which has the capability to read incoming SMS messages instantaneously from the SMS provider. The existing scheduled process, Process for Inbound Messages, also reads and processes incoming SMS messages, but it runs once in 15 minutes. Webhook addresses this lag time and ensures that messages are processed instantaneously.
Note: Even though the Webhook functionality is now available, it’s recommended to continue to run the scheduled process to offset any sync issues that Webhook may experience due to application unavailability or spikes in application usage.
Configuring Email Notifications
You can configure who is notified and under what conditions they are notified when candidates send SMS replies to the hiring team.
- In the Setup and Maintenance work area, go to:
- Setup: Recruiting and Candidate Experience
- Functional Area: Recruiting and Candidate Experience Management
- Task: Recruiting Messaging Configuration
- In the Hiring Team Notification for Text Message Replies section, click Edit.
- Decide if you want to notify everyone who had an active SMS conversation with the candidate. You can include recruiters, hiring managers, or both, for job-application or prospect-based active conversations.
Note: When anyone sends a message from the candidate profile or candidate pools pages, they will receive an email notification when the candidate replies to their message. The decision to include or exclude recruiters and hiring managers from receiving notifications doesn't affect this.
- Enter the maximum number of days an SMS conversation between a candidate and a hiring team member is considered active. For example, let’s say you specify 20 days here. If a hiring team member sent an SMS to a candidate in the last 20 days, and the candidate replied to it, an email notification will be sent to all those hiring team members who initiated a conversation with the candidate during this active conversation period. Additionally, if you choose to notify recruiters and hiring managers, they will also receive an email notification if they are a part of a requisition that’s related to the active conversation.
Note: The default value for this setting is 15 days and is configured in the seeded profile option ORA_IRC_INBOUND_SMS_ACTIVE_CONVERSATION_PERIOD.
- Enter the number of hours within which a reply received from a candidate is considered for sending an email notification. For example, let’s say you specify 120 hours here. If a candidate’s reply SMS is received within this timeframe and is processed by the scheduled process, an email notification will be sent to the hiring team. Let’s say the candidate sent an SMS message earlier than 120 hours and it was missed during the previous Webhook sync with the SMS provider. When the scheduled process runs next time, it will bring the SMS message into the application, but won’t trigger an email notification to the hiring team because the reply received from the candidate doesn't fall within the timeframe configured here.
Note: It’s recommended to keep the number of hours setting shorter and lesser than the maximum number of active conversation days. The default value for this setting is 120 hours and is configured in the seeded profile option ORA_IRC_INBOUND_SMS_NOTIFICATION_PERIOD.
- Click Save.
This feature enables hiring team members to take faster action on candidate processing tasks by receiving real-time notifications when candidates send SMS replies.
Steps to Enable
Here are the prerequisites to use this feature:
- Set up an active SMS provider in Recruiting Cloud.
- Enable SMS communications.
- Enable two-way SMS communication for the active SMS provider.
- Ensure that the profile option ORA_IRC_2_WAY_SMS_LAST_SYNC_TIME is set up.
Note: You must use a business phone number that supports two-way messaging and not use a short code number.
To enable users to access Webhook, follow these steps:
- Create a job role.
- Add the following functional privilege to it:
Name: Use REST Service - Inbound SMS Webhook
Code: IRC_REST_SERVICE_ACCESS_INBOUND_SMS_WEBHOOK_PRIV
- Create a user account for the SMS provider, and add the job role to the account.
Note: The user account that’s set up to access Webhook must not have any other privileges or roles associated to it, except the job role that you just created.
- Apply security roles by running these scheduled processes:
- Import User and Role Application Security Data
- Retrieve Latest LDAP changes
- Configure the Webhook functionality in the active SMS provider's account. For details, refer to the Doc ID 2936718.1 on My Oracle Support.
Tips And Considerations
- This feature currently works with Twilio and Syniverse providers only.
- It’s recommended to set the default value as five days in the profile option ORA_IRC_2_WAY_SMS_LAST_SYNC_TIME. Note that for Twilio, if you add more than 400 days, it will default to 400 days.
Key Resources
For more information, refer to the following topics in Oracle Help Center:
- Recruiting Content Library
- Set Profile Option Values
- Create Roles in the Security Console
- Set Up Two-Way SMS Communications
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Module | Feature | Notes |
---|---|---|---|
29 SEP 2023 | Recruiting / Candidates and Candidate Job Applications |
Latest Job Applications and Interactions in Grid View in Search Results List | Updated document. Revised feature information. |
30 JUN 2023 | Recruiting / Candidates and Candidate Job Applications |
Manually Send Request Information Notifications | Updated document. Revised feature information. |
26 MAY 2023 | Recruiting / Candidates and Candidate Job Applications | Deep Link to the Find Candidate Page | Updated document. Revised feature information. |
26 MAY 2023 |
Recruiting / Job Offers | Fast Formulas: Workplace in Offer Info Section of Job Requisition | Updated document. Revised feature information. |
26 MAY 2023 |
Recruiting / Candidates and Candidate Job Applications | Simple One-Step Process to Change Start Date of Candidates | Updated document. Revised feature information. |
28 APR 2023 | Recruiting / Recruiting Replaced or Removed Features | AddThis Services End of Life | Updated document. Feature delivered in update 23B. |
31 MAR 2023 | Recruiting Booster / Hiring Events | Enhanced Search and Filter Capabilities for Events on Career Site | Updated document. Revised feature information. |
03 MAR 2023 | Created initial document. |
HCM Cloud applications have two types of patches you can receive that are documented in this What's New:
- Release Updates (23A, 23B, 23C, and 23D)
- Optional Monthly Maintenance Packs to each update
It is important for you to know what Release Update your environment is on. You can find this in your Cloud Portal.
____________________
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our products better, please let us know. To enter an idea go to the Ideas Lab on Oracle Customer Connect. In this document wherever you see the light bulb icon after the feature name it means we delivered one of your ideas.
____________________
SUGGESTED READING FOR ALL HCM PRODUCTS
- HCM Common What's New - In this What's New you will find feature that are used across applications.
- Human Resources What’s New – In the Global Human Resources section you will find features on the base application in which other application are built upon.
NOTE: Not all Global Human Resource features are available for Talent and Compensation products.
- Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1). These documents identify bug fixes and possible known issues. You will also need to review these documents based in the release update version you are currently on or will be moving to.
- Oracle Help Center – Here you will find guides, videos and searchable help.
- Release Readiness – New Feature Summary, What’s New, Feature Listing Spreadsheet, Spotlights and Release Training
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback regarding the HCM Cloud What’s New in the body or title of the email.
any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
---|---|---|---|---|---|---|
Feature |
Report |
UI or |
UI or |
|
||
Latest Job Applications and Interactions in Grid View in Search Results List |
||||||
Select All Check Box for Bulk Actions on Search Results List |
||||||
Requisition Approval Rules: Workplace in Offer Info Section of Job Requisition |
||||||
Fast Formulas: Workplace in Offer Info Section of Job Requisition |
||||||
Enhanced Internal Candidate Experience Through Opportunity Marketplace |
||||||
Autocomplete Rules: Workplace in Offer Info Section of Job Requisition |
||||||
Enhanced Search and Filter Capabilities for Events on Career Site |
||||||
Enhancements for Event Details Pages in Candidate Experience Sites |
||||||
Oracle Recruiting Cloud provides tools for hiring managers and recruiters to source and nurture candidates, create and manage job requisitions, screen and select candidates, create and manage job offers, and onboard new employees into the organization. It also provides career sites for employees and external candidates to search, discover and apply to jobs using a frictionless application process.
When external candidates search for jobs using a location, they can now discover locations using alternate names.
In this example, a candidate found California by typing the alternate location name of "California", instead of the usual abbreviation of "CA".
a
With this enhancement, you can use commonly known alternatives for city and state level locations.
Steps to Enable
Here are the steps to enable the feature.
Step 1: Enable the Profile Option
To enable the use of alternate location names, you need to enable the new profile option ORA_IRC_SEARCH_LOCATION_INCLUDE_ALT_NAMES. By default, the profile option is set to N, and only primary location names are displayed.
- In the Setup and Maintenance work area, search for the task Manage Administrator Profile Values.
- On the Manage Administrator Profile Values page, search for the profile option code ORA_IRC_SEARCH_LOCATION_INCLUDE_ALT_NAMES.
- Set the profile value to Y.
- Click Save and Close.
Step 2: Create Alternate Location Names
To create alternate location names, you use the Manage Geographies task in the Setup and Maintenance work area.
Here’s an example of how to add alternate location names for the state of California in United States.
- In the Setup and Maintenance work area, search for the task Manage Geographies.
- On the Manage Geographies page, search for United States. Then go to the state of California (CA)
- Add alternate location names. In this example, one alternate location name was added.
Step 3: Re-index Master Geography Hierarchy or Update Geography Names
This step depends on the default location search mode configured on your career site. For details, see Configure Career Site Location Search.
If your career site is using the All locations search mode, you need to run the Load and Index Master Geography Hierarchy scheduled process to recreate the location index. Don’t set any parameters upon first activation.
You need to run the Load and Index Master Geography Hierarchy scheduled process every time you make a change to geographies on the Manage Geographies page. You can use parameters. In the above example, you could use US for country, and CA for state.
If your career site is using the Recruiting locations search mode, you need to update the geography names on your active recruiting geography hierarchy.
- In the Setup and Maintenance work area, search for the task Geography Hierarchies.
- On the Geography Hierarchies page, open active geography hierarchy.
- In the Actions menu select Update Geography Names.
Tips And Considerations
This feature works with Oracle Search only.
This feature applies to the Near Location search and Job Location search.
Career Site Configuration: Additional Row Layouts
When you configure a career site page using the Career Site Design Editor, you can now select two additional row layouts when adding a row:
- 25% by 75% (1/4 x 3/4)
- 75% by 25% (3/4 x 1/4)
With this enhancement, you can create more engaging career sites.
Steps to Enable
You don't need to do anything to enable this feature.
Career Site Configuration: Global Header Settings
When you configure a career site theme, you can now configure a global header for your career site. A new section is available: Global Header.
You can configure these header elements:
Header Options: You can select the horizontal or hamburger navigation.
Hide Logo: When you select this option, the logo isn’t displayed.
Hide I'm an employee button icon: When you select this option, the icon next to the text "I am an Employee" isn’t displayed.
I'm an Employee Text: Enter the text you want to display. Leave the field blank if you don’t want to display any text.
Hide profile button icon: When you select this option, the Manage Profile icon isn’t displayed.
Profile Text: Enter the text you want to display. Leave the field blank if you don’t want to display any text.
NOTE: If you enter custom text in the I'm an Employee Text and Profile Text fields, you can then translate the text in the Translations tab.
With this enhancement, you can create more engaging career sites.
Steps to Enable
You don't need to do anything to enable this feature.
Career Site Configuration: Increased Link Limit
When you configure the header links of a career site, you can now define up to 25 links and sub-links to be used in the global header.
With this enhancement, you can create more engaging career sites.
Steps to Enable
You don't need to do anything to enable this feature.
Contextualize Career Sites with Job Requisition Flexfields
Add job requisition flexfields as career site context filters. There are two new fields on the General tab for Career Site Configuration.
First select the context in which your DFF resides, and then select the appropriate DFF. Once selected it's added to the site context filters. Select the appropriate values from the drop-down list.
This lets you post requisitions to career sites based on a flexfield value.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Only independent DFFs are supported.
- Custom filters are not visible on the tiles for site lists.
- Candidate Experience site context DFFs are not honored in job recommendations. This means if Similar Jobs and Recommended Jobs are enabled on the site, some jobs not matching the set DFF site context can be recommended. For example, if the DFF value you selected as a context filter is “Alumni”, you may see a job in the Similar Jobs section on that site that does not have that Alumni DFF value.
External candidates who found a job opportunity on Indeed can now benefit from an optimized job application experience. A candidate's data from Indeed is used to set up the candidate's profile and prefill application form fields.
When Apply with Indeed is enabled, two new settings in the Setup and Maintenance work area control the optimized job application experience.
- Optimized Indeed Experience: When you select the Active check box, the optimized Indeed experience is enabled.
- Trust Indeed authentication: When you enable this setting, the identity verification process on the career site is bypassed for those candidates who are verified with Indeed.
- Candidates coming from Indeed and identified as returning candidates are automatically verified and can proceed further without verification.
- Candidates coming from Indeed and identified as new candidates are automatically verified and don’t need to go through the 6-digit identity verification process.
- Indeed Domains: When you enable Optimized Indeed Experience, candidates coming from specified Indeed domains will benefit from the optimized Indeed experience.
With this enhancement, the drop-off rate for external candidates who apply for jobs is reduced.
Steps to Enable
You need to enable the Apply with Indeed feature before configuring the new optimized Indeed job application experience.
- In the Setup and Maintenance work area, go to:
- Offering: Recruiting and Candidate Experience
- Functional Area: Recruiting and Candidate Experience Management
- Task: Recruiting Category Provisioning and Configuration
- On the Category Provisioning and Configuration page, go to the Profile Import section and click Edit.
- On the Profile Import Partners page, go to the Social Media section.
- In the Indeed section, you need to enable Apply with Indeed. Enter the Client ID and Client Secret Key and select the Active check box.
- You can now configure these new settings. If you enable these settings, the job application flow changes to give a better user experience to external candidates. If you don’t enable them, the job application experience is unchanged.
- Optimized Indeed Experience
- Trust Indeed authentication: You can enable this setting only if the Active check box of the Optimized Indeed Experience option is selected.
- In the Indeed Domains field, enter the referrer domain “indeed.com”. This is the default value. In the event that the domain changes, you can enter the new domain here.
- Click Save.
Candidates and Candidate Job Applications
Advanced Job Application Filters
You can perform more complex, targeted searches on the job applications list with advanced filtering capabilities when Oracle Search is enabled.
When you navigate to the job applications list, you can access new advanced filters by clicking the Show Filters link, then the Personalized Filters icon.
You can select job application questions and answers, skills, employers, positions, degrees, majors, schools, interview feedback questionnaires, and extra info fields to find the right candidates faster.
With these filters, you can select multiple values.
When you select multiple job application questions and answers:
- An AND operator is used between questions
- An OR operator is used between answers for the same question
An OR operator is used when you select multiple values for these filters:
- Skills
- Candidate labels
- Employer
- Position
- Degree
- Major
- School and school name
- Interview questionnaires
- Extra Info
An AND operator is used when you select filter values across filter categories.
Also, the Keywords field on the job applications list has been enhanced to search against job application attachments assigned to the resume category.
NOTE: Boolean search in the Keywords field isn’t yet supported. If you search for "product manager", you’ll get job applications that have resumes including the word "product" or "manager".
The Extra Info filter only supports independent flexfield segments. It’s not possible to filter segments which are configured as dates. Flexfield segments types which aren’t supported:
- Dependent
- Subset
- View Object
- Table Based Dependent
With the addition of advanced filters on the job applications list, you can find the right candidates faster.
Steps to Enable
This feature requires Oracle Search.
Step 1: Enable Profile Option
By default, the Job Application Filters on Oracle Search feature isn't available. To enable them, you need to enable the new profile option ORA_IRC_JA_ORACLE_SEARCH_ENABLED.
- In the Setup and Maintenance work area, search for the task Manage Administrator Profile Values.
- On the Manage Administrator Profile Values page, search for the profile option code ORA_IRC_JA_ORACLE_SEARCH_ENABLED.
- Set the profile value to Y.
- Click Save and Close.
Step 2: Enable Job Application Attachment Indexing
If you didn't have Oracle Search enabled for job application filters prior to 22D, you need to first enable job application attachment indexing, prior to running the initial ingestion of the search index.
- In the Setup and Maintenance work area, search for the task Manage Administrator Profile Values.
- On the Manage Administrator Profile Values page, search for the profile option code ORA_FND_SEARCH_ATTACH_ENABLED.
- This profile option isn't unique to Recruiting and may already be enabled.
- Set the profile value to Yes.
- Click Save and Close.
- In the Setup and Maintenance work area, search for the task Manage Global Search Configurations.
- On the Manage Global Search Configurations page, click the Configure Attachment Search button.
- Click the Create button to add a new row and select the index name fa-hcm-jobapplication.
- In the Content Type field, you can use the Create From Sample button to see content types or enter */* for all content types.
Step 3: Schedule New Process
You need to run the scheduled process ESS job to create index definition and perform initial ingest to OSCS. The index name to reingest is fa-hcm-jobapplication.
Deep Link to the Find Candidate Page
Create a deep link to the Find a Candidate page. There are new links available for the hiring manager and the recruiter.
These links can be positioned on other web pages, or saved as a browser favorite for quick access to candidate lookup.
This feature makes it easy to quickly access the Find a Candidate search page.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Refer to the Deep Links topic in the Implementing Recruiting guide to get information on adding deep links.
Access Requirements
Users need the function privilege Search for Candidates (IRC_SEARCH_FOR_CANDIDATE_PRIV) for deep links to work.
Latest Job Applications and Interactions in Grid View in Search Results List
Understand where candidates are currently active on job applications from the search results list, by viewing job applications and interactions information in the list view. You can now view a candidate's 3 most recent job applications, and the 3 most recent interactions taken against job applications. The first 120 characters display for each interaction, but you can hover over them to see more content.
If there are more than 3 applications, the number of applications is displayed at the bottom of the list in parenthesis.
There is also a Resume Preview link.
You can log an interaction against a candidate profile, or against a pool member, but only job-specific interactions are shown here.
The illustration below is just one example of how you could configure a view.
Recruiters can quickly understand recent candidate activity on job applications while managing candidates on a search result list. This helps with operational efficiency and more informed candidate interactions.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
-
For additional information on grid view, refer to the topic called Candidate Pool Grid View in the Using Recruiting Guide.
- For information on creating personalized views, refer to the topic called Create a Personalized Grid View in the Using Recruiting Guide.
Manually Send Request Information Notifications
You can now manually send request information notifications to candidates. This is useful when the Request Information Notification is automatically triggered when candidates reach a specific phase or state and you want to send a notification earlier in the process. It can also be useful when candidates didn’t reply to the request.
When you select one or more candidates on the Job Applications list, a new action is available: Request for More Info. The action is also available within the candidate application.
On the Request for More Info page, you can select the notification you want to resend. Only the Request Information Notification configured within the candidate selection process is displayed.
When the notification is sent, it’s logged in the Interactions tab.
You can manually send the Request for More Info notification more than once, as long as the candidate has not completed it.
With this new feature, you can send a notification to candidates if they've missed the notification triggered automatically through the candidate selection process.
Steps to Enable
Provide the required access before using the feature. Details are in the Access #Requirements section.
Access Requirements
To manually send Request Information notifications, you need the privilege Request More for Information from Candidates. This privilege is granted by default to the Recruiter.
Privilege Name | Privilege Code | Job Role |
---|---|---|
Request More Information from Candidates | IRC_REQUEST_MORE_INFORMATION_FROM_CANDIDATES_PRIV | Recruiter |
Prefill Legislative Info in Job Applications
You can capture more legislative information at the job application level.
When the feature is enabled, legislative information is automatically saved while creating applications on behalf of a candidate and is pre-filled for returning external candidates applying for a job.
With this enhancement, diversity reports will be greatly improved and be more meaningfulness.
Steps to Enable
To enable this feature for external job applications, you need to activate the setting Prefill Legislative Information in Candidate Applications in the Setup and Maintenance work area.
- In the Setup and Maintenance work area, go to:
- Offering: Recruiting and Candidate Experience
- Functional Area: Recruiting and Candidate Experience Management
- Task: Enterprise Recruiting and Candidate Experience Information
- Expand the Recruiting Management section and click Edit.
- In the Prefill Legislative Information in Candidate Applications field, select Yes.
- Click Save.
This feature is always enabled for creating applications on behalf of a candidate.
Select All Check Box for Bulk Actions on Search Results List
Select all candidates on a search results list by using the Select All check box. This check box becomes available for use when search results are 500 or fewer.
Clicking Select All selects items even if they're not immediately available on the page. You can click Load More Items to show more.
Once selected, you can choose an action from the Action menu and apply it to the candidates in bulk. This means you can send a message to up to 500 candidates at a time, or move up to 500 candidates at a time to a pool.
When you apply a bulk action to more than 50 candidates, the action is added to a batch queue, and you'll be notified on the bell icon when the batch is ready.
NOTE: When the action is applied to 50 or fewer, it's performed synchronously (immediately). If it's applied to 51-500 candidates, the process runs asynchronously as a batch.
This feature lets you quickly apply bulk actions to 500 candidates at a time.
Steps to Enable
You don't need to do anything to enable this feature.
Simple One-Step Process to Change Start Date of Candidates
In previous releases, the Change Start Date action was available only for internal candidates, from the Manage Job Offers page, when their job applications was in the HR phase. You can now change the start date of both internal and external candidates in a simple one-step process using the new Change Start Date action from Oracle Recruiting.
The Change Start Date action is available in the Job Applications and Offers lists Actions menu when job applications are in the Offer or Post Offer (custom) phase, and on the Job Offers page (Manage Job Offers quick action) when job applications are in the HR phase.
You can change the start date multiple times. The Offer team and candidate are notified of this change. You can track these start date changes in the notification date time stamps in the Messages tab of the job application.
With this enhancement, you can change the proposed start date of both external and internal candidates from Oracle Recruiting in a simple one-step process. You also save time and increase productivity of Recruiting users.
Steps to Enable
A notification is available in Alerts Composer to inform the Offer team that the start date has been changed for the candidate. You can use the notification as is or personalize it for your needs.
- IRC_ChangeStartDate_Internal_External
A notification is available in the Recruiting Content Library to inform the candidate that the start date has been changed. You can use the notification as is or personalize it for your needs.
- Job Offer Start Date Changed (ORA_JOB_OFFER_STARTDATE_CHANGE)
Tips And Considerations
General notes:
-
No approval is required for changing the start date, for any business reasons.
-
You can't change the start date of an external candidate from the job application or Manage Job Offers area when the job application is in the HR phase and the employee record becomes active (start date has been reached).
- You can't change the start date of an internal candidate from the job application or Manage Job Offers area when their record in Oracle Recruiting is converted (manually submitted from Manage Job Offers page, or submitted automatically using the profile option setting).
-
The Change Start Date action can be used only during the window period where the redraft of an offer is allowed. This window period is specified in the Redraft and Cancel Offers section of the Enterprise Recruiting and Candidate Experience Information task.
- This table explains the behavior where exactly the start date change will occur for various scenarios.
When |
Start Date (Hire Date) Update | Comments |
---|---|---|
Offer and Post Offer Phase | In Offers area (OR) | Start date will be updated in the Job Offers page. |
Pending Worker Record Created (HR Phase) | In Pending Worker Record only | Start date will be updated in the Pending worker record but a banner will be displayed with the new start date for recruiting users on the Job Offers page. |
Employee Record Created (HR Phase) | In Employee Record only | Start date will be updated in the Employee record only. |
Notes specific to individual compensation plans:
- In Update 21C, we introduced the ability to synchronize the payment start and end dates of individual compensation plans with projected start date included in an offer and expanded to pending worker in 21D. All such plans configured with this date option of Projected Hire, Start, or Submission Date will be automatically synchronized with projected start date as long as the recruiter hasn’t overridden the dates.
- For plans configured with other date options, the start date will be updated only when the new start date is later than the old date. When the new start date is earlier than the existing start date, the plan start dates remain unchanged.
Key Resources
For more information, refer to these topics in the Implementing Compensation guide:
- Sync Individual Compensation Plan Dates with the Projected Hire Date in an Offer
-
Examples of How Payment Start Dates in an Offer Sync with the Projected Hire Date
-
Payment End Date Considerations for Individual Compensation Plans
Access Requirements
To see the Change Start Date action, the Change Job Offer Start Date duty role and function privileges are required. These new privileges are granted by default to the Recruiter and Recruiting Manager roles through those 2 new duty roles:
Duty Role | Duty Role Code | Role |
---|---|---|
Change Job Offer Start Date |
ORA_IRC_CHANGE_JOB_OFFER_START_DATE_DUTY |
Recruiter |
Change Job Offer Start Date by Recruiting Manager |
ORA_IRC_CHANGE_JOB_OFFER_START_DATE_BY_RECRUITING_MANAGER_DUTY |
Recruiting Manager |
Note that the aggregate privilege Address Job Offer has been converted into a duty role. The Change Job Offer Start Date (IRC_CHANGE_JOB_OFFER_START_DATE_PRIV) privilege has been granted to it. The Human Resource Specialist role automatically inherits this capability. Customers who don’t want human resource specialists to change the job offer start date can create a copy of the Address Job Offer duty role and remove the Change Job Offer Start Date privilege.
Additional Interview Durations
As an administrator, you can now configure additional interview meeting durations and make them available to users when they schedule interviews with candidates.
The meeting duration lookup was enhanced as follows:
- It contains more duration values and additional 15-minute blocks. The lookup contains these values:
- 15 minutes
- 30 minutes
- 45 minutes
- 1 hour, 1 hour 15 minutes, 1 hour 30 minutes, 1 hour 45 minutes
- 2 hours, 2 hours 15 minutes, 2 hours 30 minutes, 2 hours 45 minutes
- 3 hours
- 4 hours
- 5 hours
- 6 hours
- 7 hours
- 8 hours
- It’s now a user-defined lookup. You can select which values you want to make available. Note: It's not recommended to create custom values as the product won't know how to interpret the values.
- New values are disabled by default. Except the 1 hour 30 minutes value which is enabled by default.
The values you enable for the Meeting Duration field are available everywhere the field is displayed. For example:
- When users define slots in candidate-managed interview schedules.
- When users request interviews to be scheduled for candidates (available in Recruiting Booster).
- When interview coordinators modify the meeting duration of an interview using the Send Interview Invite action (available in Recruiting Booster).
With this enhancement, you have more flexibility for interview meeting duration.
Steps to Enable
You can define the meeting duration values in the lookup ORA_IRC_IS_MEETING_DURATION.
- In the Setup and Maintenance work area, go to:
- Offering: Recruiting and Candidate Experience
- Functional Area: Recruiting and Candidate Experience Management
- Task: Recruiting and Candidate Experience Lookups
- On the Recruiting and Candidate Experience Lookups page, search for the lookup type ORA_IRC_IS_MEETING_DURATION.
- In the Lookup Codes section, you can see all the duration values available. Select the ones you want to enable. You can also change the meaning of a value. For example, you might want to change 1 hour to display as 60 minutes.
- Click Save and Close.
Manage candidate follow-ups by creating follow-up tasks with a due date. Follow-up tasks can be anything a recruiter wants to make reminders for with regard to candidate nurturing. Examples may include things like remembering to call a candidate on a certain date to see if they're available for work, or sending an email message to a candidate to see how they liked a job fair.
There is a new Tasks tab at the candidate level for candidate pool members.
Click it to view and add a follow-up task.
To add a new follow-up task click Add.
Assign a future due date, and use the Note field to enter the pertinent follow-up information. Click Save and Close.
You can edit, delete, or mark follow-up tasks as complete.
You can filter the pool member list to identify follow-up tasks that are overdue, due today, due in the future, or within a range of dates.
Follow-Up Tasks data is now available for use in Grid View. There is a new Pool Member Follow-Up Task Info/Follow-Up Task Info compound field. The following is an example of how this field could appear in Grid View.
The follow-up task displays the first 120 characters. You can rest your cursor over the task to show up to 500 characters. Only tasks in active status display in grid view.
NOTE: There could be more than one follow-up task associated with each candidate. Only one displays at a time, but you can click the candidate name to display them all.
You've got the ability to view follow-up tasks related to candidates.
When you select Related to Pool Member, you view follow-up tasks related to the current pool. When you select All Other Follow-Up Tasks, you can view follow-up tasks for the candidate in the context of other pools in which they're also members.
This feature lets you keep track of tasks related to candidates.
Steps to Enable
Provide the required access before using the feature. Details are in the Access #Requirements section.
Key Resources
- For additional information on grid view, refer to the topic called Candidate Pool Grid View in the Using Recruiting Guide.
- For information on creating personalized views, refer to the topic called Create a Personalized Job Application Grid View in the Using Recruiting Guide.
- For information on roles and privileges, refer to the Securing HCM Guide.
- For information on the security privileges related managing candidate pools, refer to "Provide Access to All Pools" in the 23B What's New.
Access Requirements
There are new aggregate privileges to secure the visibility of follow-up tasks. The following privileges are granted by default to the Recruiter role.
Aggregate Privilege Name |
Aggregate Privilege Code | Job Role |
---|---|---|
View Candidate Follow-Up Task |
ORC_IRC_VIEW_CANDIDATE_FOLLOW_UP_TASK |
Recruiter |
Manage Pending Candidate Follow-Up Task |
ORC_IRC_MANAGE_PENDING_CANDIDATE_FOLLOW_UP_TASK |
Recruiter |
The following is granted by default to the Recruiting Manager role. This privilege includes the ability for a recruiting admin to delete already completed follow-up tasks for the purposes of cleanup or other reasons.
Aggregate Privilege Name |
Aggregate Privilege Code |
Job Role |
---|---|---|
Manage Completed Candidate Follow-Up Task |
ORC_IRC_VIEW_CANDIDATE_FOLLOW_UP_TASK |
Recruiting Manager |
NOTE: You need to add these aggregate privileges to any custom Recruiter roles that you created prior to the 23B Update. These privileges will be included with any new custom roles created after the 23B Update.
The above aggregate privileges handle candidate follow-up tasks for which they are owner. Additionally, your organization might need to give some specific people a super-user access to follow-up tasks so that they can view and manage tasks for which they aren’t the owner.
As an IT Security Manager, you can grant access to all follow-up tasks through data security using the Security Console for manage or view Candidate Follow-up Task.
Using the Security Console, edit the data role to which you want to grant full access to candidate follow-up tasks, and create a new data security policy. In the Create Data Security Policy, configure the fields as follows:
- Data Resource: Candidate Follow Up Task
- Data Set: Select All values for the data set
- Actions: Select the actions you want: Manage Candidate Follow-Up Task, View Candidate Follow-Up Task
Modifications to Candidate Pool Data Security
To support data security for candidate pools and allow some roles to view, report, or select all pools, a new aggregate privilege has been introduced: Manage Candidate Pool. This aggregate privilege contains both the existing functional privilege and the new data privilege. While the seeded roles Hiring Manager and Recruiter have been adjusted accordingly, custom roles containing only the functional privilege Manage Candidate Pool will need to be adjusted to get the aggregate privilege under the role hierarchy. The functional privilege alone is no longer sufficient, the aggregate privilege Manage Candidate Pool is now required.
You organization might need to give some specific people a super-user access to candidate pools so that they can perform any action related to any candidate pools, though the person isn’t an owner of the candidate pool.
As an IT Security Manager, you can grant access to all pools through data security using the Security Console for managing, selecting, or reporting candidate pools.
- New security business object: Candidate Pool
- New aggregate privilege: Manage Candidate Pool (ORA_IRC_MANAGE_CANDIDATE_POOL)
- New data privilege: Manage Candidate Pool Data (IRC_MANAGE_CANDIDATE_POOL_DATA)
- New data privilege: Choose Candidate Pool Data (IRC_CHOOSE_CANDIDATE_POOL_DATA)
- New data privilege: Report Candidate Pool Data (IRC_REPORT_CANDIDATE_POOL_DATA)
Using the Security Console, edit the data role to which you want to grant full access to candidate pools and create a new data security policy. In the Create Data Security Policy, configure the fields as follows:
- Data Resource: Select Candidate Pool as the business object
- Data Set: Select All values for the data set.
- Actions: Select the actions you want: Choose Candidate Pool, Manage Candidate Pool, Report Candidate Pool.
With this new feature, you will no longer have ghost candidate pools which can't be accessed after the pool owner has left or changed role. You will be able to access all pools at all times, perform global reporting, and efficiently manage talent community pools by a super user.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Reporting users can only report on their own pools and global pools by default. While global pools were visible in the user interface to all users before 23B, they weren't reportable outside of ownership. Now the same harmonized access exists in the product and reporting. When the All Values option is added to the data role, it can be applied as well to both the product access and reporting access. One trick to get specific access to a global pool without having to grant All Values access is for the user to mark the global pool as a preferred pool. This add the user in the list of owners indirectly and will grant reporting access without requiring a view all and report all access.
Before granting access to report all, you need to grant the aggregate privilege Manage Candidate Pool.
Contextual Journey for Create Job Requisition
As an administrator, you can now configure contextual journeys for the Create Job Requisition action. A journey comprises a checklist or a set of tasks that help automate routine or special processes effectively in your organization.
Based on the contextual journey setup, when users click the Create Job Requisition quick action from either My Team or My Client Groups, a single contextual journey or a list of eligible contextual journeys are displayed and users can launch the contextual journey to accomplish the action.
This feature enables you to orchestrate the different activities that need to be done as part of a business process.
Steps to Enable
To enable contextual journeys, you need to enable the profile option ORA_PER_CONTEXTUAL_JOURNEYS_ENABLED.
- In the Setup and Maintenance work area, search for the task Manage Administrator Profile Values.
- On the Manage Administrator Profile Values page, search for the profile option code ORA_PER_CONTEXTUAL_JOURNEYS_ENABLED.
- Set the profile value to Y.
- Click Save and Close.
To configure contextual journeys, you need to create a checklist template using the Checklist Templates task in the Setup and Maintenance work area.
- In the Setup and Maintenance work area, search for the task Checklist Templates.
- On the Checklist Templates page, click the Create button.
- On the Create Checklist window, select the Contextual Journey category.
- Click OK.
- On the General tab, complete the fields.
- Context: Select the context where the quick action will appear: My Team or My Client Groups.
- Action Name: Select Create Job Requisition.
- Status: Select Active.
- Click Save.
- On the Tasks tab, you need to configure an application task so that the user can perform the quick action as part of the contextual journey.
- Click the Create button and select Create Task.
- On the Task page, complete the fields.
- Required: You need to select this option.
- Performer: The person who will perform the task. If you select Line Manager, the task will be displayed under My Team. If you select Areas of Responsibility, the task will be displayed under My Clients Group.
- Task Type: Select Application Task.
- Application Task: Select Create Job Requisition.
- Status: Select Active.
- Click Save and Close.
Tips And Considerations
- You can configure Contextual journeys only from the Checklist Templates setup page.
- You can’t change the category of an existing journey to Contextual Journey. Instead, define a new contextual journey.
- The attributes available for configuring a contextual journey are different than the regular journey setup. For example, you can’t configure an eligibility profile at the checklist or task level for contextual journeys.
- The attributes in the Configure Criteria section will vary for each contextual action.
- The DocuSign, I-9, and OPA task types aren’t supported in contextual journeys.
- The processing mode for contextual journeys is set to Alerts based notifications by default and BI Publisher notifications aren’t supported.
- Continue Without Journey button on the Contextual Journey Gallery page is controlled using a security privilege. See the Role section.
- Contextual journeys won’t be displayed in the Explore, My Journeys, and Assigned journeys tabs.
- The My Tasks Tab in Journeys displays tasks from contextual journeys.
- The Create Journey button in the Explore tab doesn’t support creation of contextual journeys.
- Only a limited set of quick actions are currently supported for configuring contextual journeys.
- The application task configured within the contextual journey is always launched in the context of the primary assignment. This is true even if a non-primary assignment is selected for the quick action which triggers the contextual journey.
Key Resources
For more information, refer to these resources on the Oracle Help Center:
- Chapter Checklists and Journeys in the Using Global Human Resources guide
- Chapter Checklists and Journeys in the Implementing Global Human Resources guide
For more information on contextual journeys, see Quick Guide: Contextual and Guided Journeys on Customer Cloud Connect.
Access Requirements
You must be granted the Manage Journey (PER_MANAGE_CHECKLIST_TEMPLATE_PRIV) function privilege to work on checklist templates.
This table shows the function security privilege that supports this feature and the predefined role that inherits this privilege.
Function |
Duty Role |
Job or Abstract Role |
---|---|---|
Bypass Contextual Journeys PER_BYPASS_CONTEXTUAL _JOURNEYS_PRIV |
Manage Contextual Journey by HR ORA_PER_MANAGE_ CONTEXTUAL_JOURNEY_ BY_HR |
Human Resource Specialist |
Requisition Approval Rules: Workplace in Offer Info Section of Job Requisition
You can create job requisition approval rules using conditions based on the values of the Workplace field in the Offer Info section of job requisitions.
Here are the values that you can configure for the workplaceTypeCode attribute to create condition expressions:
- On-Site
- Hybrid
- Remote
With this enhancement, the use of approval rules simplifies the approval of job requisitions.
Steps to Enable
You don't need to do anything to enable this feature.
Fast Formulas: Workplace in Offer Info Section of Job Requisition
You can now configure recruiting fast formulas based on the Workplace field in the Offer Info section of job requisitions.
You can create fast formulas for these formula types:
Fast Formula Type | Database Item |
---|---|
Recruiting Candidate Selection Process |
IRC_CSP_REQ_WORKPLACE_TYPE_CODE |
Recruiting Job Application Computed Field |
IRC_CSP_REQ_WORKPLACE_TYPE_CODE |
Recruiting Job Requisition |
IRC_REQ_WORKPLACE_TYPE_CODE |
With this enhancement, using Recruiting fast formulas for job requisitions simplifies the requisition creation process.
Steps to Enable
You don't need to do anything to enable this feature.
Job Application Flexfields for Additional Partner Results
You can allow your screening partners to send additional screening results using candidate job application flexfields.
Discuss with your assessment, tax credit, and background check screening partners if they want to support additional job application flexfields for screening results. If that’s the case, your administrator will need to configure these additional job application flexfields for the result payload per partner.
When the flexfields are configured, the additional results and values are displayed in the job application’s Screening Results tab.
Recruiters can add these additional fields to the job application grid view and filters. The fields aren’t available in the candidate detail’s view, where only assessment standard fields are displayed.
In the grid view Compound Field section, all segments including hidden ones are displayed when the context is selected.
NOTE: In the job application’s advanced filters, hidden fields (PROVISIONING_ID and PACKAGE_RESULT_ID) aren’t shown, but flexfield segments are displayed.
With this feature, users will have additional local information to help them decide on the next action to take with a candidate. Users will save time by having screening data visible within the application and also using filters. Users won’t need to access the partner’s portal to get additional results, which is time-consuming.
Steps to Enable
The configuration of this feature requires interaction with the screening partners.
Step 1: Create Multi-Row Flexfield Context for Job Candidate Application Usage
To support additional results, you need to create a multi-row flexfield context using the extensible flexfield called Person EIT Information.
- You can only select one multi-row context per partner.
- You need to create the hidden fields PROVISIONING_ID and PACKAGE_RESULT_ID to support the partner and package.
- You can create up to 25 additional result fields for each context.
- You can only use text, number, and date format:
- Date time isn’t supported.
- Date must be sent by the partner using the ISO-8601 format YYYY-MM-DD
In this example, the context has the 3 required hidden fields and 1 additional results field.
Here's how to create a multi-row flexfield context:
- In the Setup and Maintenance work area, search for the task Manage Person Extensible Flexfield.
- On the Manage Person Extensible Flexfield page, select the extensible flexfield called Person EIT Information.
- Click the Edit icon.
- On the Manage Person Extensible Flexfield page, click Manage Contexts.
- On the Manage Contexts page, you create one multi-row context per partner supporting those additional result fields.
- In the Context Usages tab, click the Create icon and select this usage: Usage code for candidate application.
- In the Context Sensitive Segments section, click the Create icon.
- Create the mandatory segments in the context using values provided in the following table.
- Click Save and Close.
NOTE: PROVISIONING_ID and PACKAGE_RESULT_ID must be configured as hidden.
Name | Code | API Name | Unique Key | Enabled | Data Type | Table Column | Value Set | Prompt (Label in UI) | Display Type |
---|---|---|---|---|---|---|---|---|---|
Partner Name |
PROVISIONING_ID |
provisioningId |
No | Yes | NUMBER |
PEI_INFORMATION_NUMBER1 |
PartnerNameLovValueSet |
Partner Name | Hidden |
Package Result Identifier | PACKAGE_RESULT_ID |
packageResultId |
Yes | Yes | NUMBER |
PEI_INFORMATION_NUMBER2 |
15 Digit Number |
Package Result Identifier |
Hidden |
Package Name | PACKAGE_CODE |
packageCode |
No | Yes | CHARACTER |
PEI_INFORMATION1 |
BGCPackageNameLovValueSet or AssessmentPackageNameLovValueSet or TaxCreditsPackageNameLovValueSet |
Package Name |
List of values |
In addition, you can create up to 25 result fields, using those 3 supported formats:
- Date Segments: You can use the ORA_FND_FLEX_DEFAULT_FORMAT_ONLY_DATE value set, or you can define your own value set with minimum and maximum date validation. Date time isn’t supported. The partner needs to send date data in the ISO-8601 format YYYY-MM-DD.
- Number Segments: You can use the FND_NUMBER15 value set, or you can define your own with different precision/scale to support integer and decimal numbers.
- Char Segments: You can use the FND_CHAR100 value set, or you can define your own value set. The maximum number of characters allowed is 150.
Step 2: Create Value Sets
You need to create value sets for the Partner Name, Package Name, Package Result Identifier.
- In the Context Sensitive Segments section, select the context sensitive segment you created and click Edit.
- Click Create Value Set.
- Enter the required values as indicated in the following tables.
- Click Save and Close.
Partner Name table-value set |
|
---|---|
Module |
Recruiting |
Validation Type |
Table |
Value Data Type |
Number |
FROM Clause |
FUSION.IRC_TP_PARTNERS PRTNR,FUSION.IRC_TP_PARTNER_PROVISNGS PRTNR_PROV |
Value Column Name |
PRTNR_PROV.PROVISIONING_ID |
Description Column Name |
PRTNR.NAME |
WHERE Clause |
PRTNR.PARTNER_ID = PRTNR_PROV.PARTNER_ID |
Assessment partner package LOV value set for AssessmentPackageNameLovValueSet |
|
---|---|
Module |
Recruiting |
Validation Type |
Table |
Value Data Type |
Number |
FROM Clause |
(SELECT DISTINCT A.PACKAGE_CODE,A.PACKAGE_NAME,B.PROVISIONING_ID FROM FUSION.IRC_ASMT_ACCT_PACKAGES A,FUSION.IRC_TP_PARTNER_ACCOUNTS B WHERE A.ACCOUNT_ID=B.ACCOUNT_ID) PKG,FUSION.IRC_ASMT_PARTNER_CONFIG PC |
Value Column Name |
PACKAGE_CODE |
Description Column Name |
PACKAGE_NAME |
WHERE Clause |
PC.PROVISIONING_ID =PKG.PROVISIONING_ID AND PC.RESULTS_FLEX_CONTEXT_CODE=’ASMT_FLEX_CONTEXT’ Note: ASMT_FLEX_CONTEXT is the context code for which you're creating segments. It will vary depending on the context code you created. |
Order By | PACKAGE_CODE |
Background check partner package LOV value set for BGCPackageNameLovValueSet |
|
---|---|
Module |
Recruiting |
Validation Type |
Table |
Value Data Type |
Number |
FROM Clause |
(SELECT DISTINCT A.SCR_PKG_CODE,A.SCR_PKG_NAME,B.PROVISIONING_ID FROM FUSION.irc_bc_acct_sp_assgmnts A,FUSION.IRC_TP_PARTNER_ACCOUNTS B WHERE A.ACCOUNT_ID=B.ACCOUNT_ID) PKG,FUSION.IRC_BC_ACTIVATION_CONFIG PC |
Value Column Name |
SCR_PKG_CODE |
Description Column Name |
SCR_PKG_NAME |
WHERE Clause |
PC.PROVISIONING_ID =PKG.PROVISIONING_ID AND PC.RESULTS_FLEX_CONTEXT_CODE=’BGC_FLEX_CONTEXT’ Note: BGC_FLEX_CONTEXT is the context code for which you're creating segments. It will vary depending on the context code you created. |
Order By | SCR_PKG_CODE |
Tax credit partner package LOV value set for TaxCreditsPackageNameLovValueSet |
|
---|---|
Module |
Recruiting |
Validation Type |
Table |
Value Data Type |
Number |
FROM Clause |
(SELECT DISTINCT A.PACKAGE_CODE,A.PACKAGE_NAME,B.PROVISIONING_ID FROM FUSION.IRC_TC_ACCOUNT_PACKAGES A,FUSION.IRC_TP_PARTNER_ACCOUNTS B WHERE A.ACCOUNT_ID=B.ACCOUNT_ID)PKG, FUSION.IRC_TC_PARTNER_CONFIG PC |
Value Column Name |
PACKAGE_CODE |
Description Column Name |
PACKAGE_NAME |
WHERE Clause |
PC.PROVISIONING_ID =PKG.PROVISIONING_ID AND PC.RESULTS_FLEX_CONTEXT_CODE='TAX_RESULTS_FLEX_CONTEXT’ TAX_RESULTS_FLEX_CONTEXT is the context code for which you're creating segments. It will vary depending on the context code you created. |
Order By | PACKAGE_CODE |
Step 3: Associate Context to Partner
When the context configuration is done, you need to associate the context to the partner.
- In the Setup and Maintenance work area, go to:
- Offering: Recruiting and Candidate Experience
- Functional Area: Recruiting and Candidate Experience Management
- Task: Recruiting Category Provisioning and Configuration
- On the Partner Integration Provisioning page, locate the partner and click the Edit icon.
- Select the context in the Context for Additional Results field.
- Click Save.
Step 4: Input Payload for Partners
With this newly associated context, the partner can start to send additional results into those defined segments. For details, refer to the Partner Integration technical briefs (Doc ID 2627681.1) available on My Oracle Support.
Enhanced Internal Candidate Experience Through Opportunity Marketplace
Use Opportunity Marketplace by default for the internal candidate experience. With this release, Opportunity Marketplace for Jobs has been enabled for all. Users are now automatically taken to Opportunity Marketplace when they click Current Jobs.
All existing job applications, posted jobs, and referrals are also available in the newer Opportunity Marketplace candidate experience.
Saved Searches
Opportunity Marketplace users can now save and share search settings.
All Opportunity Marketplace users can:
- Create and save personal searches.
- Mark their personal searches as their default search, which loads each time they open Opportunity Marketplace.
- Enable their personal searches for sharing, and share it with others. They can also copy a search link to share.
- Browse through and use any of their own personal searches, as well as Admin-created system searches.
Additionally, Admin users can:
- Create system searches that are made available to all users.
- Mark any of the system searches as default for all users.
NOTE: User default searches override admin defaults on load.
- Opportunity Marketplace provides a newer UX experience for internal job seekers.
- Using saved searches, users can come back to their previously searched for search results. Saved searches also help users to share and promote pre-filtered sets of opportunities.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- You must run the scheduled process called “ESS job to create index definition and perform initial ingest to OSCS” after the 23B upgrade. This ensures that all jobs and gigs that already exist in the application are fully indexed for search. Specify “fa-hcm-requisition” in the Index Name to Reingest field.
-
You must also run the scheduled process called “ESS job to create index definition and perform initial ingest to OSCS” after the 23B upgrade to ensure that saved search index definitions are set up for usage. Specify “fa-hcm-savedsearch” in the Index Name to Reingest field.
-
Opportunity Marketplace for Gigs is optional and must be enabled separately. Instructions can be found in the Implementing Recruiting guide.
-
If you have set up Dynamic Skills, you can enable skills advisor for gigs so that gig creators can associate skills related to a gig. This is a separately sold product.
Key Resources
- Refer to the Using Recruiting and Implementing Recruiting guides for complete information on Opportunity Marketplace.
- Refer to the Implementing Recruiting guide for instructions on enabling the optional Skills Advisor for Gigs.
Autocomplete Rules: Workplace in Offer Info Section of Job Requisition
You can write autocomplete rules for the Workplace field available in the Offer Info section of the Job Requisition business object.
Here is the field in Offer Info section in Job Requisitions and Supported rule type in Autocomplete.
Field name | Object Defaulting | Object Validation |
---|---|---|
Workplace | Yes | Yes |
Using autocomplete rules for creating, editing, and copying requisition fields simplifies the requisition creation process and helps enhance the overall recruiting process.
Steps to Enable
You don't need to do anything to enable this feature.
HCM Data Loader Enhancements for Recruiting
Extend your data loading capabilities with these enhanced business objects:
ENHANCED BUSINESS OBJECTS
Business Object |
Changes |
---|---|
Candidate |
|
Candidate Job Application |
You can now redraft offers from the following offer phases and states:
|
Job Requisition |
You can now update the Descriptive Flexfield (DFF) segments of a job requisition, regardless of the requisition's phase or state. |
BUSINESS OBJECTS WITH NEW ATTRIBUTES
Business Object |
Component |
New Attributes |
---|---|---|
Content Library |
Version |
Note: These attributes can only accept files with a maximum of 50,000 characters. |
Content Library Version Translation |
|
|
Job Requisition |
Job Requisition |
|
Job Requisition Template |
|
For details, refer to the feature entitled Business Object Enhancements documented in the HCM Common – HCM Data Loader 23B What’s New.
Extend your bulk-loading capabilities with these new and extended objects available with HCM Data Loader and HCM Spreadsheet Data Loader.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Use the View Business Objects task to review and download the latest business object information.
Extract Remote Fields on Job Requisitions
Using the Job Requisition extract in HCM Extracts, you can now extract Remote fields on job requisitions. A new field IRC_EXTRACTS_REQUISITIONS_WORKPLACE_TYPE_CODE has been added to the user entity IRC_EXTRACTS_REQUISITION_DETAILS_UE.
With this enhancement, you can easily extract remote fields on job requisitions.
Steps to Enable
You don't need to do anything to enable this feature.
Recruiting Replaced or Removed Features
From time to time, Oracle replaces existing features with new features, or removes existing features.
Replaced features may be put on a path of removal, the features below will let you know what update you will have to have moved to the newer feature. As a best practice, you should move to the newer feature as soon as possible for full support and to stay up with the latest updates that the product offers.
Any feature that is removed, will have an Update in which that feature is no longer available. Please make necessary plans to move off the feature by the Update indicated, as it will no longer be available.
Note that beginning May 2023, Oracle will begin removing the Addthis service for all customers. This means you will no longer be able to use Addthis to share, follow, and recommend content on external career sites. All active Addthis configurations will be removed from Oracle Recruiting Career Sites, and with the 23B update it will no longer be possible to configure AddThis. If your site used AddThis share buttons, they have been replaced by a copy link icon.
Oracle has made the decision to terminate the use of AddThis services as part of a periodic portfolio review.
Steps to Enable
You don't need to do anything to enable this feature.
Oracle Recruiting Booster enables hiring managers and recruiters to engage candidates at scale via conversational experiences and two-way messaging; create and manage hiring events with registration flows, pre-screening questionnaires and scheduling capabilities; manage shared interview schedules, sync with calendars to automate interview scheduling, distribute interview guides and collect feedback from the interviewers. This product requires a separate license.
Interviewer Preferred Availability for Automated Scheduling
Interviewers can now define their preferred availability to be used in addition to their Microsoft 365 calendar availability when candidates are scheduling interviews based on the interviewers' availability.
When you configure a candidate managed interview schedule that uses automated scheduling (the "Candidates schedule based on interviewers' availability" setting is selected), you can now define that the preferred availability of interviewers must be requested. A new setting is available: Request preferred availability from interviewers.
This setting becomes available when you select the setting Candidates schedule based on interviewers.
A notification is automatically sent to interviewers selected on the schedule. This includes both named users and hiring team member types. The notification explains to the interviewers that they’ve been identified as an interviewer for a requisition and they're invited to update their availability if needed. Information about the requisition is provided as well as a link to define the availability. The link goes to a new tab called My Availability. This tab is available in the Interviewers work area (under Me > Interviews quick action) and the Coordinators work area (under My Client Groups > Coordinate Interviews).
NOTE: Interviewers are requested to define their preferred availability when creating a new schedule on a requisition and when adding a shared schedule on a requisition.
Two options are available:
- Use my Microsoft 365 calendar availability: This is the default option.
- Use both my preferred availability and my Microsoft 365 calendar availability: With this option, interviewers can define their availability for each day of the week. Interviewers can change their availability at any time.
When proposing time slots to candidates invited to schedule an interview on a candidate managed schedule that uses automated scheduling (the "Candidates schedule based on interviewers' availability" setting is selected), both calendar availability from Microsoft 365 and the preferred availability defined by interviewers are considered. For a given time slot to be proposed to candidates, the interviewer must be available in both places (Preferred availability and Microsoft 365).
The preferred availability provides interviewers with more control over their schedule, allowing them to decide when they're available for interviews.
Steps to Enable
This feature is available if your organization:
- Uses Recruiting Booster
- Enabled the Microsoft 365 integration
You can configure the display of the setting Request preferred availability from interviewers by creating a rule in Transaction Design Studio with the Recruiting - Create Interview Schedule action. By default, the setting is set to Visible.
You can also configure the display of the My Availability tab by creating a rule in Transaction Design Studio with the Recruiting - Coordinate Interviews action or the Recruiting - Interviews action. By default, the tab is set to Visible.
The notification sent to interviewers to define their availability is available in Alerts Composer: Interview Availability Notification to Interviewer (IRC_Intrv_Availability_Interviewer).
- By default, the notification is sent to interviewers only. A token is available to define the interviewers.
- By default, a token is included in the content of the notification to link to the page allowing the interviewers to define their availability. This link always navigates to the My Availability tab in the Interviewer work area, even if the user also has access to the Coordinator work area. For this reason, the privilege Access My Candidate Interviews and Feedback for the Interviewer work area must be granted to coordinators as well. Note that as of 23B, this privilege is granted to the Recruiter role by default.
- You can use requisition-related and schedule-related tokens in the notification.
NOTE: When a user creates a job requisition using an existing requisition to which a schedule is attached (and this schedule has the "Request availability" setting enabled), no request for availability notification will be sent to interviewers.
Key Resources
For information on how to create rules in Transaction Design Studio, refer to this topic in the Implementing Recruiting guide on Oracle Help Center:
Overlapping Time Slots for Automated Scheduling
When candidates are scheduling interviews for a schedule that uses the automated scheduling (the "Candidates schedule based on interviewers' availability" setting is selected on the schedule), more time slots are proposed to candidates because different interview start times are proposed based on the interviewers' availability.
In the previous release, the system proposed time slots with start times matching the selected meeting duration. If the meeting duration was 1 hour, the proposed time slots were 8 AM, 9AM, 10 AM, and so on. As a result, candidates couldn't select a time slot starting at 8:30 AM, even if the interviewers were available.
Now, the system proposes time slots with different start times to provide more choices to candidates. This means that overlapping time slots might be proposed to candidates. If the meeting duration is 30 minutes or less, the system will propose time slots with a start time interval matching the actual meeting duration.
Meeting Duration |
Examples of Proposed Time Slots |
---|---|
15 minutes |
8AM, 8:15AM, 8:30AM, 8:45AM, etc. |
30 minutes |
8AM, 8:30AM, 9AM, 9:30AM, etc. |
If the meeting duration is 45 minutes or more (45 min, 1 hour, 2 hours, 3 hours, 4 hours, 6 hours, 8 hours, etc.), the system will propose time slots with a start time interval of 30 minutes.
Meeting Duration |
Examples of Proposed Time Slots |
---|---|
45 minutes |
8AM, 8:30AM, 9AM, 9:30AM, etc. |
1 hour |
8AM, 8:30AM, 9AM, 9:30AM, etc. |
2 hours |
8AM, 8:30AM, 9AM, 9:30AM, etc. |
Here’s are some examples.
Example 1: An interview schedule is configured with a meeting duration of 1 hour. The interviewer's calendar for a given day is completely booked with meetings, except for 1 block from 1:30PM to 2:30PM. For this day, one time slot will be proposed to candidate, from 1:30PM to 2:30PM.
Example 2: An interview schedule is configured with a meeting duration of 1 hour. The interviewer's calendar for a given day is completely free, and the interviewer's work day starts at 8AM. For this day, time slots will be proposed to candidates, starting at 30 minutes intervals: 8AM, 8:30AM, 9AM, 9:30AM, 10AM, 10:30AM, and so on.
When a candidate schedules an interview using a proposed time slot, the system also ensures that two candidates don't select time slots overlapping each other. For example, if the meeting duration is 1 hour:
- Proposed time slots for candidate A are 8AM, 8:30AM, 9AM, 9:30AM, 10AM, 10:30AM
- Candidate A schedules interview at 8:30AM
- Proposed time slots for candidate B will be 9:30AM, 10AM, 10:30AM
The system also validates that the interviewers are still available for that time slot before scheduling the interview. This is to prevent having two candidates schedule an interview with the same interviewers at the same time. If a time slot is no longer available, the candidate will be asked to select a different time slot.
With this enhancement, more time slot choices are proposed to candidates, which helps finding a time which works for them.
Steps to Enable
This feature is available if your organization uses Recruiting Booster.
Add Questions to Event Registration Flow
Allow administrators to add a questions block to the event registration flow. Once added, the questions are available to candidates on career sites.
Event questions can be used to prescreen or disqualify candidates. Disqualified candidates see a message letting them know they didn't meet the requirements for the event.
As an event owner, you can view event audience member responses by clicking the new Questions tab and filtering by question type.
This feature lets you gather more information from the event registrants prior to events, and lets you automatically reject candidate registrations based on the responses provided for disqualification questions.
Steps to Enable
Add the Question Block to the Event Application Flow
- In the Setup and Maintenance work area, go to:
- Offering: Recruiting and Candidate Experience
- Functional Area: Candidate Experience
- Task: Job Application Flow Configuration
- On the Job Application Flows page, click Create.
- Enter a name and a code for the event.
- In the Application Flow Type field, select Event.
- Enter a description.
- Click Save and Continue.
- You now need to create versions of the flow and select information blocks for the registration flow, including the new Event Registration Questions block.
- Add the Event Registration Questions block to the Event Registration section.
- Select the One page registration flow check box if you want this flow to appear to candidates on one page. When it is two pages, the Event Registration Questions section will appear on the second page.
- Activate the flow so that it can be selected when events are created.
Add Questions to the Event Layout
When you create or edit a new event on the Event Page Layout tab and you add an Event Registration form containing the Event Registration Questions, an Event Registration Questions section displays. Click Edit to add questions to the section.
You can add prescreening questions and disqualification questions. You can rearrange the order of the questions. When an event is an in-person event, questions are automatically filtered to those that apply only to the country in which the event is happening. Virtual events will have a separate country selector.
Tips And Considerations
To use this feature you must have the following privileges:
- HRT_REST_SERVICE_ACCESS_QUESTIONNAIRE_LOVS_PRIV
- PER_REST_SERVICE_ACCESS_HCM_COUNTRIES_LOV_PRIV
- IRC_VIEW_CANDIDATE_JOB_APPLICATION_PRIV
- IRC_MANAGE_JOB_REQUISITION_QUESTIONNAIRE_REQUEST_PRIV
Key Resources
For complete details on using Hiring Events, refer to the document on My Oracle Support (MOS) called "Hiring Events" (Document 2918997.1)
Calibrate Event Success Through Hired and Applied Metrics
Measure the number of hires and applications your event has generated by using the new Hired and Applied metrics.
These metrics are tallied once an event starts, and includes both the timeframe of the event plus the number of days indicated for your measurement. For example, if the event lasts 2 days and you're measuring successful hires within 30 days, the actual length of time counted for the metrics is 32 days.
By default, Applied is set to 30 days, and Hired is set to 90 days. You can adjust the number of days on each of the metrics to suit your organization's needs.
This feature lets you measure the success of your events during a particular assessment period.
Steps to Enable
NOTE: Before you can use this feature, you must opt in to Recruiting Booster and enable Hiring Events.
To change the default number of days used for the metrics, you can do the following.
- In the Setup and Maintenance work area, go to:
- Offering: Recruiting and Candidate Experience
-
Functional Area: Recruiting and Candidate Experience Management
-
Task: Enterprise Recruiting and Candidate Experience Information
-
Expand the Events section.
- Click Edit and update the metrics according to your organization's needs.
- Click Save and Close.
Any changes you make here affect only new events going forward.
Tips And Considerations
- Candidates must be audience members to be counted in the Hired or Applied metrics. They can be in any state (Invited to Attend, Registered, Attended) as long as they are attached to the event.
- Adding an event audience member as a prospect isn't counted towards the Applied metric. The audience member must have an application or you can create a manual application for the candidate to have them count toward the Applied metric.
- Applied metric is a count of the number of people who have applied for requisitions and not the number of applications placed for requisitions from that particular event. This means even if an audience member applies for more than one requisition, the candidate is only counted once in the Applied metric.
- Candidates who apply outside of the metrics assessment window don't count toward the metrics. For example, if a candidate applies 33 days after an event ends, and you are measuring application success based on 30 days, the candidate won't be added to the Applied metrics. However, if they are hired within the Hired metrics window, they will be counted there.
- Once a candidate has moved to the HR phase on a requisition, they are considered hired.
- If a candidate later declines an offer, the metrics are decremented only if they decline during the assessment period
- If you change the default number of days for either of these metrics, it only affects new events going forward. Previous and current events are not re-calibrated using the new number of days. They continue to use the old durations for calibrating their metrics.
Key Resources
Refer to "Set Up Hiring Events" in the 23A What's New document for instructions on opting in to Recruiting Booster and Enabling Hiring Events.
Enhanced Search and Filter Capabilities for Events on Career Site
Take note that in addition to event name and number, candidates can now search for events on career sites based on event category, and short and long descriptions. Autosuggest lists events where the search term matches the event name or the event category. Suggestions for jobs and events are now listed separately under either a Jobs or an Events header in autosuggest.
Candidates can also filter the events list based on:
- Event Categories - categories listed on this filter correspond to posted events. If there are no posted events for a particular category, that category won't appear in the filter.
- Event Locations - values on this filter correspond to the locations of posted events. If there are no posted events for a particular location, that location won't appear in the filter.
- Start Dates - by default all events are sorted by the event start date in descending order, beginning with the date farthest into the future. Candidates can further filter events by the following timeframes:
-
Next 7 Days - Events that start during 7 days from the current date.
-
Next 30 Days - Events that start during 30 days from the current date.
-
Greater than 30 Days - Events that start after 30 days from the current date.
-
NOTE: Note that values on the filter correspond to events that are currently available on the career site. If a career site has a combination of events that took place in the past and that are taking place after the next 30 days, then the only option in this filter will be Greater than 30 Days.
- Event Format - like the rest of the filters, values on this filter correspond to events which are posted on the career site. The values which are supported on the filter are:
- In Person
- Virtual
When candidates search by keyword, the results are automatically sorted by relevance. Relevancy is calculated based on where a search term appears for an event. For example, events with matching search terms in the event name are given a higher placement in the results list than those with the same term in the short or long description. The order in which relevancy is assigned is:
- Event Name
- Event Number
- Event Category
- Short Description
- Long Description
A candidate who searches for a "QA Analyst", may find more relevance in events which have that term in the event name, than those that randomly mention the term listed amongst many other items in a long description.
NOTE: Note that searching on Location will return events corresponding to that location, but searching on My Location and Postal Code is currently not supported for events and returns results for all locations.
This feature allows candidates to retrieve events through additional search parameters and advanced filtering capabilities.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
You must run the scheduled process called "ESS Job to create index definition and perform initial ingest to OSCS" after the 23B upgrade. This ensures that all hiring events that either already exist in the application or those that will be newly created are fully indexed for search. Specify “fa-hcm-irc-hiring-events” in the Index Name to Reingest field.
For additional information about running scheduled processes, see the chapter called "Overview of Scheduled Processes" in the guide called Oracle Fusion Cloud Applications Using Common Features on Oracle Help Center.
Enhancements for Event Details Pages in Candidate Experience Sites
Take note of the following enhancements in Candidate Experience sites where events are enabled:
A Copy Link button which lets you share the URL for event details.
This lets candidates copy the link to the event to their clipboards.
In addition, the Register button label changes to Already Registered for events in which a user has already registered. If a candidate hasn't yet confirmed their registration, the button label changes to Confirm Your Event Registration.
This feature provides a better UX for candidates. The Copy Link button also encourages the sharing of events, which can result in more potential candidates being interested in the event.
Steps to Enable
You don't need to do anything to enable this feature.
Render Events in Multiple Languages on Career Site
Select event languages during event creation. If you believe that candidates from more than one region will attend your events, you may want to enable multiple languages for the events. There is a new Languages drop-down in the Event Information section that lets you do this. The default language which is selected in the Languages drop-down list is the session language of the user. The default language can't be de-selected.
Once you've selected languages, you can translate certain fields for the event. There is a new Translate Event option in the Action menu.
When you select it, the Translate Event page opens. The languages you selected in the Event Information section display here.
Click the Edit icon next to a language, and enter the event name, event long description, and event short description in that particular language.
NOTE: You or someone in your organization enters the translated text. It isn't automatically translated.
Event users can preview the translations using the Languages drop-down list on the preview section.
When the event is posted, candidates who have selected the same language on the career site as one of the event languages will see the event translated into the language of their choice. In addition, the check-in page for the event will also display in their preferred language. Upon registering for the event, the candidate's language preference is remembered and all subsequent event related notifications are sent in the candidate's preferred language.
NOTE: Translations must be entered for notifications using the Translation Editor on the Recruiting Content Library so that the notifications can be sent in the candidate's preferred language.
The feature allows users to translate events into multiple languages so that candidates can view the event detail in the language of their choice.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For additional information about translations see the topic called Translate a Career Site in the Implementing Recruiting guide.
Recruiting Booster and Enable Easy Apply
Oracle Recruiting Assistant (ORA) is a 24/7 chat bot that helps candidates every step of the way with finding the right jobs.
Using ORA, candidates can search for jobs based on location, job category, or function, view recommended jobs, check their job application status, withdraw their application, or join a talent pool to get regular updates. ORA includes the Candidate Experience V2 skill, which provides enhanced job search capabilities and helps candidates receive contextual guidance at the right time.
With Recruiting Booster, candidates can see job recommendations based on their resume and get answers to job-related questions. In addition, they can quickly apply for certain jobs from the chat bot interface instead of navigating to the career site, when an easy-apply flow is configured and enabled in Recruiting.
This example illustrates a job with an easy-apply flow configured, which includes the Contact Information and Review blocks.
When a candidate applies to this job, the terms and conditions associated with the job are first displayed.
When they accept the terms and conditions, they provide their name and email address, according to the configuration in the Contact Information block.
On submitting the application, a code is sent to their email. When they enter the correct code, the application process is completed.
When you opt in to Recruiting Booster, the easy-apply feature is enabled in ORA by default.
To enable or disable this feature:
- In the Setup and Maintenance work area, select these options:
- Setup: Recruiting and Candidate Experience
- Functional Area: Recruiting Assistant
- Task: Manage Recruiting Assistant Configuration
- On the Configure Recruiting Assistant page, select or clear Enable Easy Apply.
- Click Save and Close.
Take advantage of the enhanced features in the CEV2 skill in ORA by opting in to Recruiting Booster. This helps candidates get a seamless experience on the job search, get answers to job-related questions, and apply to the job quickly from the chat bot interface.
Steps to Enable
- In the Setup and Maintenance work area, select the Recruiting and Candidate Experience offering.
- Click Change Feature Opt In.
- On the Opt In: Recruiting and Candidate Experience page, enable Recruiting Booster.
Tips And Considerations
Candidates can experience the easy-apply feature only on those job openings that have a job application flow configured with a maximum of five information blocks. When they apply for the job, the extent of information they need to provide depends on the configuration of these information blocks.
You configure the job application flow using the Job Application Flow Configuration task in the Setup and Maintenance work area. You then add it to the job requisition using the Details > Configuration section in Recruiting.
Key Resources
For more information, refer to the following 23A What's New feature under Recruiting:
Two-Way Communication for Internal Candidates
Recruiters and the hiring team can have conversations with internal candidates using Two-Way Communication using email. This is an extension of the two-way communication functionality already available for external candidates. The rules that are applied to external candidates are now applied to internal candidates. Note that if the internal candidate doesn’t have a work email, the alternate email is automatically used.
Two-way communication will make recruiting conversations easier with internal candidates.
Steps to Enable
This feature is available if your organization opted in to the Recruiting Booster offering.
You can enable two-way communication for external candidates, internal candidates, or both. This allows Recruiting users to compose messages for candidates. When you don’t enable the two-way communication, a worklist notification is sent to candidates.
- In the Setup and Maintenance work area, go to:
- Offering: Recruiting and Candidate Experience
- Functional Area: Recruiting and Candidate Experience Management
- Task: Recruiting Messaging Configuration
2. On the Recruiting Messaging Configuration page, go to the Email Communications section.
3. Select one or both options:
- Enable Two-Way Email Communications with External Candidates
- Enable Two-Way Email Communications with Internal Candidates
NOTE: Only one email provider needs to be Active for two-way communication with internal candidates.
Key Resources
For more information on two-may communication, refer to this 23A What’s New feature:
Transactional Business Intelligence for Recruiting
Oracle Transactional Business Intelligence is a real time, self-service reporting solution offered to all Oracle Cloud application users to create ad hoc reports and analyze them for daily decision-making. Oracle Transactional Business Intelligence provides human resources managers and specialists, business executives, and line managers the critical workforce information to analyze workforce costs, staffing, compensation, performance management, talent management, succession planning, and employee benefits.
Don’t want to start from scratch building a report or analytics? Check out the library of sample reports for all products on Customer Connect on the Report Sharing Center.
When you create gig reports using the Recruiting - Opportunity Marketplace Real Time subject area, you can now you can now get the total number of openings and the filled count.
With this enhancement, reporting capabilities are aligned with the content in Opportunity Marketplace.
Steps to Enable
You don't need to do anything to enable this feature.
Display Name Added to Source Tracking
The various subject areas containing the source name now include a new field: Display Source.
The Display Source is available in these subject areas where sources are available:
- Recruiting - Recruiting Real Time
- Recruiting - Recruiting Events Real Time
- Recruiting - Sourcing Real Time
With this feature, it's easier to group and sort reports where sources are included.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
If you have reports where you count the number of sources using the name, you might want to change them to use the display name. The delivered Recruiting to Hire report has not been adjusted. The top ten sources based on the name might differ from the real top ten sources where sources like xxx.domain.com/jobs, yxz.domain.com/longurl, abc.domain.com/multipleparameters are now listed as display name "domain.com".
Recruiting Campaign Subject Area Adjustments
HCM Communicate campaigns are no longer available in the Recruiting - Sourcing Real Time subject area.
There are no changes in the available list of metrics and dimensions, the same fields are available. But the reporting content is now exclusively coming from the user recruiting campaigns.
With this enhancement, there are less confusion for users using both Recruiting campaigns and HCM Communicate employee campaigns.
Steps to Enable
You don't need to do anything to enable this feature.
Enhanced External Candidate Tracking Activities
Get more details and precision with the enhanced Candidate Tracking Real Time subject area. You can now find out where external candidates stopped during their application process and how many candidates submitted their applications after starting the application process.
In the previous release, you could already discover the jobs external candidates were searching for, the number of job searches done by external candidates, the job requisitions that were viewed by external candidates, and the jobs to which external candidates applied to.
You can now report on additional details and track more actions. For example, with the number of successful submits, you can compare the number of applications that were started and the drop rate. Also, counting the number of pages reached in a multiple pages application flow will give you useful tips on where candidates might be struggling and where they might decide to leave the site.
Here are the new metrics and fields.
New metrics:
- Number of Candidate Cancelled
- Number of Successful Submits
- Number of Unique Visitors (based on temporary user ID)
New Candidate - Tracking Activity - Details:
- Candidate Application Identification
- Source Name
- Source Medium
- Referrer Header
- Campaign Code
- Career Site Number
- Candidate Country Code
- Candidate Region
- Candidate Municipality
- Candidate Settlement
- Number of Pages in Flow
- Current Page
- User Identifier
New actions under the Action field:
- PIN: Job added to favorites by clicking the star icon.
- UNPIN: Removing the requisition from the list of favorite jobs.
- VERIFY: Clicking or performing the verification action.
- VALID: Entering a valid code and confirming the candidate.
- ID_NEXT: Clicking NEXT in the Identification Page.
- ID_CANCEL: Canceling instead of moving forward in the Identification page.
- APPLY_FLOW_VISIT: Visiting the application flow after clicking Next.
- SUBMIT_SUCCESS: Clicking the Submit button.
- ASSESSMENT_START: Clicking the Inline Assessment button, or the Post Apply Assessment link.
- ASSESSMENT SUCCESS: A candidate being returned to the application by the partner after starting the inline assessment.
- TAXCREDIT_START: Clicking the Take Tax Credit Assessment button in the application flow, or the Post Apply Assessment link.
- TAXCREDIT_SUCCESS: Candidate returned from the partner site in the application flow.
With this enhancement, you can know more about the behavior of external candidates, improve your career sites, and reduce friction points.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
If you run the scheduled process Purge Processed Internal Recruiting Data, the candidate tracking data retention is 180 days. Data older than that will no longer be in the database and you won't be able to report on it.
If you use a single-page application flow, counting the number of visited pages won't work. The system always counts one visited page but is considering that there are 3 pages in the flow, which isn't true. Since the number of visited pages doesn't matter for a single-page application flow, you should ignore the number of pages marked as 3. For application flows having 2 pages and more, the counts are working properly and are meaningful.
IMPORTANT Actions and Considerations for Recruiting
REPLACED OR REMOVED FEATURES
From time to time, Oracle replaces existing Cloud service features with new features or removes existing features. When a feature is replaced the older version may be removed immediately or at a future time. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.
Product |
Removed Feature |
Target Removal |
Replacement Feature |
Replaced In |
Additional Information |
---|---|---|---|---|---|
Recruiting | Recommend for Rehire Filter Removed | 23A | |||
Recruiting | Recruiting Replaced or Removed Features | 23B | Removed in 23B |
_________________________
RECRUITING PAGES IN TRANSACTION DESIGN STUDIO
Rename actions in Transaction Design Studio to personalize Recruiting pages. The prefix Recruiting was added to recruiting actions to easily identify and select the pages.
_________________________
KNOWN ISSUES / MAINTENANCE PACK SPREADSHEETS
Oracle publishes a Known Issues document for every Update to make customers are aware of potential problems they could run into and the document provides workarounds if they are available.
Oracle also publishes Maintenance Pack and Statutory Maintenance Pack documentation of bugs that are fixed in the monthly or statutory patching.
To review these documents you must have access to My Oracle Support:
Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1)