Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date

What's Changed

Notes

09 OCT 2018

Oracle Taleo Platform Cloud Service: Define Domains to Embed Career Section URLs

Updated document. Moved feature under Oracle Taleo Career Section Cloud Service.

14 SEP 2018

Oracle Taleo Enterprise Cloud Service – Fluid Recruiting: New Fluid Recruiting Functionalities (17.8)

Updated document. Revised feature information.

10 SEP 2018

Oracle Taleo Recruiting Cloud Service: Evaluation Management – Microsoft Office 365 Integration

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Recruiting Cloud Service: Evaluation Management – Mobile Responsive Questionnaires

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Sourcing Cloud Service: Display User-Defined Fields on Job Details Page

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Sourcing Cloud Service: Streamlined Interface in User Settings

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Sourcing Cloud Service: Employees Sign Up for Job Alerts on Settings Page

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Sourcing Cloud Service: Simplified Job Alert Preferences Management

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Onboarding (Transitions) Cloud Service: New Hires Upload Multiple Files on a Single Task

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Scheduling Cloud Service: Schedule Interviews with Shorter Intervals

Updated document. Feature delivered in OTAC 17.8 quarterly update.

10 SEP 2018

Oracle Taleo Enterprise Cloud Service – Fluid Recruiting: New Fluid Recruiting Functionalities (17.8)

Updated document. Feature delivered in OTAC 17.8 quarterly update.

11 JUN 2018

Oracle Taleo Career Section Cloud Service: Apply with LinkedIn 2.0

Updated document. Feature delivered in OTAC 17.6 quarterly update.

11 JUN 2018

Oracle Taleo Sourcing Cloud Service: Expanded Requisition Data on Job Details Page

Updated document. Feature delivered in OTAC 17.6 quarterly update.

11 JUN 2018

Oracle Taleo Platform Cloud Service: Define Domains to Embed Career Section URLs

Updated document. Feature delivered in OTAC 17.6 quarterly update.

11 JUN 2018

Oracle Taleo Enterprise Cloud Service – Fluid Recruiting: New Fluid Recruiting Functionalities (17.6)

Updated document. Feature delivered in OTAC 17.6 quarterly update.

09 MAY 2018

Oracle Taleo Sourcing Cloud Service: Direct Apply (17.5)

Updated document. Added feature that was removed from OTAC 17.4 quarterly update, which is available with 17.5.

29 MAR 2018

Oracle Taleo Sourcing Cloud Service: Direct Apply

Removed feature from OTAC 17.4 quarterly update.

23 MAR 2018

Oracle Taleo Scheduling Cloud Service: Notify Calendar Owner of Time Slot Unavailability

Updated document. Revised feature information.

12 MAR 2018

Oracle Taleo Recruiting Cloud Service: Confirmed Candidate Accounts

Updated document. Feature delivered in OTAC 17.4 quarterly update.

12 MAR 2018

Oracle Taleo Career Section Cloud Service: Vertical Layout on Login and Registration Pages

Updated document. Feature delivered in OTAC 17.4 quarterly update.

12 MAR 2018

Oracle Taleo Scheduling Cloud Service: Notify Calendar Owner of Time Slot Unavailability

Updated document. Feature delivered in OTAC 17.4 quarterly update.

12 MAR 2018

Oracle Taleo Enterprise Cloud Service – Fluid Recruiting: New Fluid Recruiting Functionalities (17.4)

Updated document. Feature delivered in OTAC 17.4 quarterly update.

29 JAN 2018

Oracle Taleo Enterprise Cloud Service – OBI Reporting: New Reporting Fields in 17.3.

Updated document. Feature delivered in OBI 17.3 quarterly update.

15 DEC 2017

Oracle Taleo Recruiting Cloud Service: Candidate Email Address Verification

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Recruiting Cloud Service: Evaluation Management – Enhanced Security on Candidate Files

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Career Section Cloud Service: Google Structured Data for Job Postings

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Career Section Cloud Service: Enhanced Security on Password Reset

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Sourcing Cloud Service: Hierarchical Location Selector

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Sourcing Cloud Service: User Cookie Acceptance

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Sourcing Cloud Service: Security Settings in Configuration

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Sourcing Cloud Service: User Session Timeout

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Sourcing Cloud Service: Identity Provider Logout for Single Sign-On (SSO) Users

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Sourcing Cloud Service: Exit URL for Single Sign-On (SSO) Users

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Onboarding Cloud Service: Form Snapshots

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Scheduling Center Cloud Service: Interview Reminders to Calendar Owner

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Enterprise Cloud Service – SmartOrg: Legacy SSO Deactivation

Updated document. Feature delivered in OTAC 17.2 quarterly update.

15 DEC 2017

Oracle Taleo Enterprise Cloud Service – Fluid Recruiting: New Fluid Recruiting Functionalities (17.2)

Updated document. Feature delivered in OTAC 17.2 quarterly update.

21 SEP 2017

Oracle Taleo Enterprise Cloud Service: Fluid Recruiting

Updated document. Feature delivered in Release 17.

18 SEP 2017

Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in Oracle Talent Acquisition Cloud Release 17 and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at talent_acquisition_doc_feedback_ww_grp@oracle.com.

Release Feature Summary

Some of the new Release 17 features are automatically available to users after the upgrade and some require action from the user, the company administrator, or Oracle.

The table below offers a quick view of the actions required to enable each of the Release 17 features.

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Oracle Taleo Recruiting Cloud Service

Making Submission User-Defined Fields Available in Recruiting

Using Submission User-Defined Fields in Forms and Files

Using Submission User-Defined Fields to Automatically Move Candidates

Using Submission User-Defined Fields in Message Tokens

Using Submission User-Defined Fields in List Formats

Candidate Email Address Validation

Evaluation Management – Enhanced Security on Candidate Files

Confirmed Candidate Account

Evaluation Management – Microsoft Office 365 Integration

Evaluation Management – Mobile Responsive Questionnaires

Oracle Taleo Career Section Cloud Service

Making Submission User-Defined Fields Available in Career Section

Using Submission User-Defined Fields in Forms and Flows

Remove Requirement of Not Specified Option for Radio Button and Checkbox Format Diversity Questions

Google Structured Data for Job Postings

Enhanced Security on Password Reset

Vertical Layout on Login and Registration Pages

Apply with LinkedIn 2.0

Define Domains to Embed Career Section URLs

Oracle Taleo Sourcing Cloud Service

Site Pages

Remove Requisitions Deleted in Recruiting via Automated Task

Employee and Job Facets for Profile Fields

Populate Single Sign-On ID (SSOID) with Employee Synchronization Data

Hierarchical Location Selector

User Cookie Acceptance

Security Settings in Configuration

User Session Timeout

Identity Provider Logout for Single Sign-On (SSO) Users

Exit URL for Single Sign-On (SSO) Users

Direct Apply (17.5)

Expanded Requisition Data on Job Details Page

Display User-Defined Fields on Job Details Page

Streamlined Interface in User Settings

Employees Sign Up for Job Alerts on Settings Page

Simplified Job Alert Preferences Management

Oracle Taleo Onboarding Cloud Service

Form Snapshots

New Hires Upload Multiple Files on a Single Task

Oracle Taleo Scheduling Center Cloud Service

Interview Reminders to Calendar Owner

Notify Calendar Owner of Time Slot Unavailability

Schedule Interviews with Shorter Intervals

Oracle Taleo Enterprise Cloud Service – SmartOrg

Legacy SSO Deactivation

Oracle Taleo Enterprise Cloud Service – OBI Reporting

New Reporting Fields in the Recruiting Subject Area

New Reporting Fields in 17.3

Oracle Taleo Enterprise Cloud Service Connect Client

Support of Certificate Authentication

Support of TLS 1.2

Oracle Taleo Enterprise Cloud Service-Fluid Recruiting

Fluid Recruiting

New Fluid Recruiting Functionalities (17.2)

New Fluid Recruiting Functionalities (17.4)

New Fluid Recruiting Functionalities (17.6)

New Fluid Recruiting Functionalities (17.8)

Oracle Talent Acquisition Cloud

Oracle Talent Acquisition Cloud family of products drives effective talent acquisition within the modern enterprise. The cloud solution enables scalable approval and management of job requisitions, superior candidate experience (sourcing and branding of modern career sites, relationship management, and job application), candidate selection workflow (qualification, evaluation, and interview), job offer, and employee onboarding.

Oracle continues its ongoing investments around intuitive user experience for external and internal candidates, recruiters, hiring managers, and HR administrators. This includes development of core areas such as modern interfaces with multi-device support, configurable decision and approval workflow processes, actionable business insights and reporting, tighter integration with other HCM functions, and adherence to hiring compliance rules.

Oracle Taleo Recruiting Cloud Service

Submission User-Defined Fields Availability Changes

Submission user-defined fields (UDFs) can now be made available to be used in the following areas of Oracle Taleo Recruiting Cloud Service:

Making Submission User-Defined Fields Available in Recruiting

Submission user-defined fields (UDFs) can be configured to be made available in Oracle Taleo Recruiting Cloud Service.

When configuring the properties of submission UDFs, administrators can now make submission UDFs available for Taleo Recruiting and Career Section, enable history tracking, and specify the OLF structure and staffing type exceptions.

Submission User-Defined Field Properties with New Selectable Options

Steps to Enable

To make submission UDFs available in Oracle Taleo Recruiting Cloud Service:

  1. Click Configuration.
  2. In the Recruiting section, click Administration.
  3. In the Fields section, click Candidate.
  4. In the Show Fields filter, select Submission to display submission fields.
  5. Click a field.
  6. Click Edit Field Availability.
  7. Select Taleo Recruiting.

Tips and Considerations

When upgrading to Release 17, for all customer’s existing submission UDFs, the Taleo Recruiting and Career Section availability options are disabled by default. For any new UDFs that customers create, the Taleo Recruiting and Career Section availability options are disabled by default.

Key Resources

For more information about UDFs configuration, review the following topic in the Oracle Taleo Recruiting Configuration Guide:

Using Submission User-Defined Fields in Forms and Files

When submission UDFs are made available in Oracle Taleo Recruiting Cloud Service, they can be used in forms and files.

This enhancement allows recruiters to capture candidate information that is relevant to a submission. For example, a specific certification or work availability information pertaining to a position can be collected using submission UDFs in the candidate file.

Submission UDFs are available in three types of form:

When administrators create user-defined forms using one of the above types, they can select submission UDFs to design their form.

Submission UDFs Available for Selection in the Form Builder

When administrators create user-defined files, Submission Information forms are available under these blocks:

User-Defined File with Submission Information Block

Submission Information forms can be used in both profile and submission contexts. Depending on which context Submission Information forms are being used, the visibility of submission UDFs is controlled. Even though the form and block contain submission information, submission information is visible to the users only in a submission context. In a profile context, submission information is automatically hidden. Note that in a submission context, if a block doesn’t contain any submission information, the entire block is hidden.

Steps to Enable

Administrators must make submission UDFs available in Recruiting to use them in forms and files.

Key Resources

For more information about the configuration of forms and files, review the following topics in the Oracle Taleo Recruiting Configuration Guide:

Using Submission User-Defined Fields to Automatically Move Candidates

When submission UDFs are made available in Oracle Taleo Recruiting Cloud Service, they can be used to create conditions to automatically progress candidates in the candidate selection workflow.

When administrators create a new condition, submission UDFs are available for selection under Job-specific submission > User-defined Field > Submission Information.

New Condition with a Submission UDF

Steps to Enable

Administrators must make submission UDFs available in Recruiting to use them to create conditions.

Key Resources

For more information about the automatic progression of candidates, review the following topic in the Oracle Taleo Recruiting Configuration Guide:

Using Submission User-Defined Fields in Message Tokens

Submission UDFs can be used as tokens in message templates.

The token format is {Submission.UDF_fieldname} where fieldname is the UDF value.

Submission UDF tokens can be used within the body of the message and also in the To, Cc, Bcc, and, Subject fields.

Submission UDFs Tokens Available in a Message Template

Steps to Enable

There are no steps necessary to enable this feature.

Tips and Considerations

Submission UDFs do not need to be configured as available in Recruiting to be available as tokens in message templates.

Key Resources

For more information about message tokens, review the following topic in the Oracle Taleo Recruiting Configuration Guide:

Using Submission User-Defined Fields in List Formats

When submission UDFs are made available in Oracle Taleo Recruiting Cloud Service, they can be used in list formats.

Submission UDFs are available in the following list format contexts:

Submission UDFs are not available in list formats which are used in profile context.

When administrators configure list formats, they can select submission UDFs in a new group called Submission Information.

New Submission Information Field Group

Steps to Enable

Administrators must make submission UDFs available in Recruiting to use them in list formats.

Key Resources

For more information about list format configuration, review the following topic in the Oracle Taleo Recruiting Configuration Guide:

Candidate Email Address Verification

Recruiters can verify whether candidate email addresses entered in the system are valid. Knowing that candidates have not validated their email address, recruiters can use alternate communication channels to send communications.

When administrators enable the feature, candidates are sent a message asking them to validate their email address. The message contains a link to the career section. Once candidates click the link, they are taken to the career section login page. On successful login, candidates see the message “Email successfully verified”. If the validation fails, candidates see the message "Email verification failed" with a generic explanation. If the email address was already validated, candidates see the message "Email verification failed" with an explanation that their email address was already validated.

Successful Email Address Validation Message in the Career Section

In Recruiting Center, recruiters can see that a candidate’s email address was validated. The Email Validated icon appears in the candidates list. It also appears on the candidate card when viewing the general profile or submission of a candidate. The verification is done once per candidate unless the email address is changed.

Email Validated Icon in Candidates List

A quick filter is also available to display candidates who have validated their email address.

Email Validated Quick Filter

Steps to Enable

Administrators set a threshold for sending the email validation message to candidates. When candidates’ job submissions reach a specific step of the candidate selection workflow, candidates who have not yet validated their email address receive the message.

To set the threshold for sending the email validation message to candidates:

  1. Click Configuration.
  2. In the Recruiting section, click Settings.
  3. Search for the Threshold to Send Email Validation Notification to Candidate setting.
  4. Click the name of the setting.
  5. Click Edit.
  6. In the Value field, select the step of the candidate selection workflow when the notification will be sent.
  7. Click Save.

A new message template is available for the email address validation: Email Address Validation Invitation.

A new column is available to add to list formats: Email Validated Icon.

A new quick filter is available to add to list formats: Email Validated.

Tips and Considerations

When upgrading to Release 17.2, the Threshold to Send Email Validation Notification to Candidate setting is set to Never.

For existing candidates whose email address is yet to be validated, the email address validation message is sent if the candidate is active and when the candidate reaches the step as configured in the setting.

The email validation flag is available for reporting in OBI. It is also available for integration (Connect Client, SOAP, API).

Evaluation Management Enhanced Security on Candidate Files

Interview participants get candidate artifacts as attachments instead of a link. The security is enhanced because it prevents unintended sharing of candidate artifacts and its corresponding indexing in search engines.

Steps to Enable

To enable the feature:

  1. Click Configuration.
  2. In the Evaluation Management section, click Administration.
  3. Click Settings.
  4. Set the Interviewer Notification with Attachment setting to Yes.
  5. Click Save.

Tips and Considerations

When upgrading to Release 17.2, the Interviewer Notification with Attachment setting is set to No by default.

When the feature is enabled and interviews are being rescheduled, interview participants will get candidate artifacts as attachments. Previous emails with links to attachments will not be accessible.

Web forms continue to be available through a link.

Confirmed Candidate Accounts

Recruiters can know which candidates have viewed and confirmed their profile. This feature ensures that recruiters know which candidates have consented to have their information used for ongoing engagement by the organization. It also ensures that candidates had an opportunity to verify their profile content when their profile was sourced through recruiters, referrals, third party applications, or agencies.

When candidates get to the career section Thank You page, the system automatically marks their profile as being confirmed by the candidate. Recruiters are then able to know which candidates have confirmed their profile by viewing the Candidate Confirmed Account icon next to the candidate name.

Candidate Confirmed Account Icon in Candidates List

Steps to Enable

A new column is available and administrators can add it to all candidate list formats: Candidate Confirmed Account Icon.

Tips and Considerations

The candidate confirmed account information can be exported and imported via Connect Client.

Evaluation Management – Microsoft Office 365 Integration

Interview coordinators can view free / busy calendar information of interviewers on their Outlook calendar.

When you organize an interview, you can browse the Microsoft Office 365 directory to add participants to the interview. You are not limited to the Recruiting list of users. Once you added the desired participants and selected a target date and time for the interview, you can view the availability grid to determine the optimal time to schedule the interview.

Interview Availability Grid

Steps to Enable

To integrate Microsoft Office 365 and Azure Active Directory (AD) with Evaluation Management, perform the following configuration steps.

Prerequisites:

Step 1: Grant Integration Permission

To setup the integration, the user must have the “Manage Microsoft Exchange and Active Directory integrations” permission.

  1. Click Configuration.
  2. In the SmartOrg section, click Administration.
  3. Click User Types.
  4. Click a user type.
  5. Under Recruiting > Prescreening and Electronic Feedback, select the permission Manage Microsoft Exchange and Active Directory integrations.
  6. Click Save.

Step 2: Enable Integration Setting

To display the Integrations menu in the Evaluation Management Administration page, you must enable the “Evaluation Interview Integrations Activation” setting.

  1. Click Configuration.
  2. In the Recruiting section, click Settings.
  3. Search for the Evaluation Interview Integrations Activation setting.
  4. Click the name of the setting.
  5. Click Edit.
  6. Select Yes.
  7. Click Save.

Step 3: Register Recruiting on Microsoft Azure Portal

For Recruiting to communicate with Azure Active Directory, you must register Oracle Talent Acquisition Could on the Azure Cloud portal to create a secure connection between Recruiting and Azure Active Directory. This will generate a key that you must copy in OTAC.

  1. Go to the Azure portal and log in to your Azure Account.
  2. Select Azure Active Directory in the left menu.
  3. Select App registrations.
  4. Select New application registration.
  5. Enter the following information:
  6. Click Create. The Client ID and Symmetric Key are generated. These are required when configuring Active Directory for Microsoft Office 365.
  7. Click Settings.
  8. Click Required Permissions.
  9. Select the option Read Directory Data.
  10. Click Save.
  11. Click the Grant Permissions button.
  12. Click Keys.
  13. Add a description and duration for the key.
  14. Copy the key displayed and paste it on a document. You will not be able to see it again later.

Step 4: Configure Microsoft Office 365

  1. Click Configuration.
  2. In the Evaluation Management section, click Administration.
  3. Click Integration Configuration.
  4. Click Create next to Exchange Integrations.
  5. Enter a name for the integration.
  6. Enter the Microsoft Office 365 domain name. This information is provided by Microsoft when subscribing to Office 365.
  7. Set the status to Active.
  8. Select Office365 for the version.
  9. Enter the Exchange Web Services URL. The default value is https://outlook.com/EWS/Exchange.asmx.
  10. Enter the user name of the registered Office 365 user. If you use a vanity domain, use this domain. Example: john.doe@vanity.com.
  11. Enter the password provided for the Office 365 user.
  12. Click Save.

Step 5: Configure Azure Active Directory

  1. Click Configuration.
  2. In the Evaluation Management section, click Administration.
  3. Click Integration Configuration.
  4. Click Create next to Active Directory Integrations.
  5. Enter a name for the integration.
  6. Enter the Active Directory domain name. This information is provided by Microsoft when subscribing to Office 365. Use the full domain name with onmicrosoft.com. Do not use the vanity domain.
  7. Set the status to Active.
  8. Set the active directory type to Cloud AD to enable the supported AD configuration with Microsoft Office 365.
  9. Set the authentication method to NA - Cloud AD.
  10. The Active Directory URL is defaulted to Microsoft’s graph API’s URL for Cloud AD.
  11. Enter the Client ID. The Client ID is generated when registering Oracle Talent Acquisition Cloud on the Azure AD portal. Ask Azure administrator to provide you with the value.
  12. Enter the symmetric key. The symmetric key is generated when registering Oracle Talent Acquisition Cloud on the Azure AD portal. Ask Azure administrator to provide you with the value.
  13. Click Save.

Tips and Considerations

It is the customer's responsibility to have Microsoft Office 365 and Azure AD properly connected. Oracle does not support issues related to Microsoft Office 365 and Azure AD interconnection.

It is the customer's responsibility to choose and activate the correct integration options in Oracle Talent Acquisition Cloud. Oracle does not support integration between products such as Microsoft Office 365 with on premises Active Directory or Azure AD with Exchange server.

It is the customer's responsibility to enable single sign-on to Microsoft Office 365.

Evaluation Management – Mobile Responsive Questionnaires

Interviewers can access evaluation questionnaires and their response for a scheduled interview on their mobile devices.

Two pages have been made responsive:

Evaluation Questionnaire Page

Response Page

Steps to Enable

There are no steps necessary to enable this feature.

Oracle Taleo Career Section Cloud Service

Submission User-Defined Fields Availability Changes

Submission user-defined fields (UDFs) can now be made available to be used in the following areas of Oracle Taleo Career Section Cloud Service:

Making Submission User-Defined Fields Available in Career Section

Submission user-defined fields (UDFs) can be configured to be made available in Oracle Taleo Career Section Cloud Service.

When configuring the properties of submission UDFs, administrators can now make submission UDFs available for Taleo Recruiting and Career Section, enable history tracking, and specify the OLF structure and staffing type exceptions.

Submission User-Defined Field Properties with New Selectable Options

Steps to Enable

To make submission UDFs available in Oracle Taleo Career Section Cloud Service:

  1. Click Configuration.
  2. In the Recruiting section, click Administration.
  3. In the Fields section, click Candidate.
  4. In the Show Fields filter, select Submission to display submission fields.
  5. Click a field.
  6. Click Edit Field Availability.
  7. Select Career Section.

Tips and Considerations

When upgrading to Release 17, all customer’s existing submission UDFs are automatically made available in Taleo Recruiting and Career Section. For any new UDFs that customers create, the Taleo Recruiting and Career Section availability options are disabled by default.

Key Resources

For more information about UDFs configuration, review the following topic in the Oracle Taleo Recruiting Configuration Guide:

Using Submission User-Defined Fields in Forms and Flows

When submission UDFs are made available in Oracle Taleo Career Section Cloud Service, they can be used in forms and flows.

Submission UDFs are available in these types of form:

When administrators create user-defined forms using one of the above types, they can select submission UDFs to design their form.

Submission UDFs Available for Selection in the Form Builder

When administrators create application flows, Submission Information forms are available under these blocks:

Steps to Enable

Administrators must make submission UDFs available in Career Section to use them in forms and flows.

Key Resources

For more information about the configuration of forms and flows, review the following topics in the Oracle Taleo Career Section Configuration Guide:

Remove Requirement of Not Specified Option for Radio Button and Checkbox Format Diversity Questions

Diversity questions no longer require a ‘not specified’ option to be configured for radio button and checkbox format questions enhancing usability for applicants.

Prior to Release 17, diversity questions required the display of a ‘not specified’ option for radio button and checkbox format questions. This was counter-intuitive because ‘not specified’ is relevant to dropdown designs, not radio button and checkbox designs.

Steps to Enable

There are no steps necessary to enable this feature.

Tips and Considerations

The option to display and use the ‘not specified’ option is still there, but is no longer mandatory.

Google Structured Data for Job Postings

Jobseekers searching for jobs on Google will now be able to find jobs in their Google search results. This new feature adds markers in the page layout of the Career Section Job Description page which allows Google to index jobs. A block of code is included in the Job Description page which Google Search tools can index according to its formatting rules. This enables jobs posted on Career Sections to be indexed and searchable on Google Search.

Administrators enable this feature through mapping SmartOrg location levels to Google’s levels. The levels in the new settings reflect the language and levels used in Google’s level concepts. When the feature is enabled, through location mapping, the system will automatically include those fields which are mapped in the code block.

The five new settings represent location level concepts in Google’s data model and reside in the Career Section settings:

  1. Google Structured Data Location Mapping Country – Optional for indexing
  2. Google Structured Data Location Mapping Locality – Mandatory for indexing
  3. Google Structured Data Location Mapping Postal Code – Optional for indexing
  4. Google Structured Data Location Mapping Region – Mandatory for indexing
  5. Google Structured Data Location Mapping Street Address – Optional for indexing

Fields which are optional in the Google Structured Data format are only included in the code block if they are:

Steps to Enable

NOTE: Again, Locality and Region must be configured to enable Google indexing. For the optional settings, Country, Postal Code, and Street Address, the field must be displayed on the Job Description for it to be indexed.

To enable Google Indexing:

  1. Click Configuration.
  2. Click Settings in the Career Section section.
  3. You may refine your search results by Keyword and entering Google.
  4. Select Google Structured Data Location Mapping Locality and click Edit.
  5. Enter a location level in the value field.
  6. Click Save.
  7. Repeat steps 4-6 for Google Structured Data Location Mapping Region.

The steps above are the minimum requirement for enabling Google indexing. To index more fields, continue to repeat steps 4-6 for Country, Postal Code and Street Address.

Tips and Considerations

This feature only applies to external career sections.

At upgrade this feature is disabled. All of the settings are delivered with a value of Not Specified.

For locations, we only show the locations that are mapped in the five SmartOrg location settings.

This feature does not impact the user interface.

Enhanced Security on Password Reset

To enhance security for the password reset functionality, beginning with Release 17.2, all sessions which use an account’s access credentials will be terminated after the password is reset. The user invoking the password reset will have to login once again.

With this new behavior, all concurrent candidate sessions are terminated after a password is reset. This ensures that any unexpected user who may also have a session has their session terminated as well, and is not able to login again.

Users will experience this enhanced security in the following scenarios:

  1. My Account Options Page
  2. “Forgot your password?” link on the Login screen, while not logged in
  3. Password is changed from Recruiting Center or via Integration

Steps to Enable

There are no steps necessary to enable this feature.

Tips and Considerations

It’s recommended that an audit of label customizations is performed to ensure customers have not written any instructions that describe the behavior prior to Release 17.2.

Cases in which a candidate is setting their password for the first time, even against a pre-existing account such as referrals, integration import and Create Candidate flows are not logged out and asked to login once again.

Vertical Layout on Login and Registration Pages

A new setting, Authentication Page Layout is introduced that offers applicants a more modern vertical layout for the Login and Registration pages.

The actions for a returning user, a new user, and a sign-in partner login are stacked in a vertical layout rather than the sign-in partner actions appearing to the right of the sign-in actions. The new layout is more intuitive, and is more conducive for use on mobile devices.

Vertical Layout of Login Page

This new setting is global, impacting all Career Sections. Only the “Or Sign in with” label is not perpetuated into the vertical layout. Also, if OPenID is not enabled, i.e. there are no partners, the Use a Sign-In Partner section is not displayed. All other labels on the candidate interface are unchanged and persist in order to respect customers’ existing label text configurations.

Steps to Enable

At upgrade, the default value is horizontal maintaining the current state. To change the layout to vertical:

  1. Click Configuration.
  2. Click Settings in the Career Section section.
  3. You may refine your search results by Keyword and entering Layout.
  4. Select Authentication Page Layout and click Edit.
  5. Select Vertical as the Value.
  6. Save.

Tips and Considerations

The impact of this feature is limited to Login and Registration pages.

It is recommended that branding files are reviewed which restyle the Career Section for either desktop or mobile optimization to assess how customers’ existing branding files impact the new layout.

Apply with LinkedIn 2.0

To allow job seekers to use their LinkedIn account for both their profile data and authentication, a new button, Apply with LinkedIn, is presented on the Login and Registration pages of the Career Section. This enables job seekers to authenticate into the Career Section using LinkedIn and import their profile in one step; this removes the friction from the steps to register or login with a username and password prior to applying to a job. By using their LinkedIn session, job seekers can create new job submissions without creating a personalized username and password in the Career Section. If the job seeker has an active cookie from LinkedIn on their device, the button displays as Apply with LinkedIn, and allows one-click authentication. In this case, the LinkedIn section displays in the LinkedIn user profile preference language.

If the job seeker does not have an active LinkedIn cookie, the button displays as, Sign in with LinkedIn. In this case, the LinkedIn section displays in the browser language.

A new section on the Thank You page invites users to create a username and password after they complete their job submission. When the user arrives at the Thank You page after completing the application flow, a Create my User Name and Password link displays if they do not have a personalized username and password in place. This LinkedIn feature is solely for creating new job submissions, not viewing or updating new submissions, therefore, users must create a personalized username and password to view or update their submissions, or for signing in to use other Career Section functions.

Those users who do not create a username and password after arriving on the Thank You page will be sent an email inviting them to create the username and password at their convenience. Job seekers that do not reach the Thank You page, but begin a job submission will also receive this email invitation.

The Career Section has scenario handling built in which covers cases such as returning users who may not have created a username and password, and connecting LinkedIn authentication to existing accounts.

Steps to Enable

An Administrator must be logged into a LinkedIn Administrator account prior to enabling the Apply with LinkedIn service in OTAC.

The Vertical Layout of the Login page must be enabled to use Apply with LinkedIn.

To enable Apply with LinkedIn:

  1. Click Configuration.
  2. Click Administration in the Career Section section.
  3. Click Profile Import in the Integration section.
  4. Under Profile Import Services, click the Apply with LinkedIn (applywithlinkedin) link.
  5. Click Edit.
  6. At the bottom of the page, enter your zone in the Zone URL(s) authorized to use this LinkedIn Service field and then click Connect to LinkedIn.
    1. LinkedIn returns and populates the Client ID and the Zone URLs in both http and https formats and a LinkedIn widget is presented.
  7. Click the Request button on the LinkedIn widget.
    1. This populates the last of the needed settings, the Integration Context, in the Profile Import Settings.
  8. Click Save.
  9. Click Activate.

Tips and Considerations

There is no impact to job submissions originating in Sourcing.

Other Profile Import Partners and Resume/CV parsing are suppressed in the application flow when a job submission is initiated with Apply with LinkedIn.

The legacy LinkedIn profile import service is automatically deactivated once the new Apply with LinkedIn is activated.

Service supports multiple zone URLs to enable staging and production zones after refreshes which copy configuration.

Due to how LinkedIn has prescribed their API be used:

Define Domains to Embed Career Section URLs

Define domains where career section URLs can be embedded in frames.

A new setting is available:

Steps to Enable

To enable the feature:

  1. Click Configuration.
  2. In the Career Section section, click Settings.
  3. Search for the Cross Frame Protection Allowed Domains setting.
  4. Click the name of the setting.
  5. Click Edit.
  6. Enter domains where career sections are allowed to be embedded in frames. Example: *.corporation.com|corporation2.com.
  7. Click Save.

The values entered are applied when the setting Cross Frame Protection is configured to Yes.

Oracle Taleo Sourcing Cloud Service

Site Pages

Sites in Sourcing tend to be aligned by brand, vertical, or other recruitment segment to differentiate audiences. Now, each of these audiences can have multiple supporting content pages. Administrators can create and configure multiple content pages associated to specific sites. These Site Pages:

When a site is created in Site Builder, the site automatically displays in the new Site Pages tab. A Create New Page button allows Administrators to create site pages, tailored to each site.

Site Pages Tab in Site Builder

Each page has several attributes. Page Name and Page Link are unilingual while Title, Keywords, and Description are multilingual.

For the multilingual page attributes, there is a usability benefit included in the system in that values will get propagated to all locales from the default locale.

Create New Page in Site Builder

Once a Site Page is created, Administrators can edit the page in Site Builder. Content blocks can be added to the page using the same content block functionality as elsewhere in Site Builder. Referencing the image below:

Site Pages Edition in Site Builder

A Site Page can be edited, cloned and deleted. When a Site Page is cloned it can be used again within the same site using a different name, or the cloned page can be tethered to other sites.

Steps to Enable

There are no steps necessary to enable this feature.

Tips and Considerations

The three legacy Custom Pages are still delivered and are now referred to as Global Pages.

It is recommended that customers review any Custom CSS and Branding HTML for rendering on Site Pages.

Key Resources

For more information about content blocks, language locales and Site Builder review the Oracle Taleo Sourcing Configuration Guide.

Remove Requisitions Deleted in Recruiting via Automated Task

When requisitions are deleted in Recruiting via Automated Task, those requisitions are now removed from the job search results and the list of jobs displayed in Sourcing.

Steps to Enable

There are no steps necessary to enable this feature.

Employee and Job Facets for Profile Fields

Eight new Job Facets and ten new Employee Facets are being introduced which are aligned to standard profile fields in Recruiting. These facets can now be used by Job Seekers to more effectively refine their job search efforts and by Recruitment Marketers to create more focused campaigns.

The ten employee facets being introduced are:

The eight job facets being introduced are:

Steps to Enable

The newly available Employee and Job Facets are delivered inactive and must be activated by an Administrator to use. To activate the facets:

  1. Click Configuration.
  2. Click Facets.
  3. Use the arrows or drag and drop to move the inactive facets, as indicated by red, into the active facets, indicated by green.

Tips and Considerations

It is recommended that data in fields on requisitions and employee profiles in Recruiting is validated prior to activating facets in Sourcing.

To obtain a meaningful dataset for faceting, customers should consider making profile fields mandatory in requisitions and internal submissions.

Customers who edited labels on profile fields in Recruiting to customized values via a Service Request can edit the labels in the Picklist Editor in Sourcing to mirror Recruiting.

Populate Single Sign-On ID (SSOID) with Employee Synchronization Data

Customers can now select one of six values to automatically populate the SSOID with data from the Employee Connector from Recruiting. The chosen value from Recruiting will populate or re-map the SSOID in Sourcing. This allows easier deployment of Single Sign-On, and more choices in implementation.

Customers must choose a single value from the following list of six:

Steps to Enable

A Service Request with Oracle Customer Support is required to use this feature.

Tips and Considerations

It is recommended that customers audit and check data availability in fields in Recruiting before requesting the mapping of the SSOID.

Hierarchical Location Selector

The Hierarchical Location Selector enhances usability by introducing a new user interface pattern which allows the selection of locations through choosing levels such as country, state or province, city, and address.

Customers can choose to display the new hierarchical selector to users that are:

Hierarchical Location Selector – Sign Up for Job Alerts

Users select locations by drilling into the location levels displayed. Locations can be added at any level by clicking Add. Individual levels can be cleared by clicking Clear.

Steps to Enable

A new setting, Hierarchical Location Selector, must be enabled for the hierarchical selector to display.

To enable the Hierarchical Location Selector:

  1. Click Configuration.
  2. Click Users.
  3. Within the User Settings section, select the toggle next to the Hierarchical Location Selector setting to enable the feature.

While the above steps enable the Hierarchical Location Selector, two other existing settings drive which levels display in the hierarchical selector and, in which order those levels display.

The Location User Preferences setting (Configuration > Users > User Settings) determines which levels display in the Hierarchical Location Selector. Only the levels configured here will display in the hierarchical selector as choices for users. However, the order in which the levels are listed in this setting does not determine the order in which they’ll display in the hierarchical selector. Only levels that contain elements will be displayed.

The OLF Locations Levels setting (Configuration > Taleo > Taleo Enterprise Edition) determines in which order the levels are displayed. Having the order of the levels configured with respect to this setting ensures that the Hierarchical Location Selector displays the levels in the same location hierarchy as in SmartOrg.

Tips and Considerations

This feature is disabled at upgrade.

Customers should evaluate custom branding or CSS configured in Site Builder for styling impacts from this new hierarchical selector.

User Cookie Acceptance

Regulatory requirements in various geographies require websites to either passively inform or proactively gain permission from users to store cookies on a user’s device. To enhance regulatory compliance, a new setting, Display Cookie Acceptance, is being introduced that enables customers to either advise jobseekers on the site’s use of cookies or to require jobseekers to agree to the site’s use of cookies prior to using their jobs site.

The new setting allows Administrators to select whether to display the Cookie Blocking Modal, the Cookie Advisory Banner or no cookie policy information at all. The Advisory Banner is informational so users may dismiss the banner and will be able to continue with all actions on the site. The Blocking Modal forces agreement. The user will not be able to continue using the site unless they click Accept. If users dismiss the banner or agree to the modal, another cookie is loaded and the banner or modal will not show again for that site. However, if cookies are cleared from a device, the previously dismissed banner or previously agreed to modal will reappear. All of these actions are site-specific.

Steps to Enable

The new setting, Display Cookie Acceptance, must be configured to display cookie policy information.

To display either the Advisory Banner or the Blocking Modal:

  1. Click Configuration.
  2. Click Site Builder.
  3. Click the Gear Icon next to the site which you want to configure.
  4. In Settings > General, click the Pencil Icon and select either Advisory Banner or Blocking Modal.
  5. Click Save.

Tips and Considerations

This feature is configured to None at upgrade, meaning that no cookie policy content is displayed.

It is recommended that an organizations regulatory needs are reviewed prior to activating this feature.

Default labels should be validated with in-house counsel. Labels may need to be refined using dictionary tags as required to meet compliance needs.

If there is desire for a supplemental page with more policy details, a Site Page with more information can be created. The dictionary tags in the banner and modal accept HTML links to other pages. This allows Administrators to create an HTML link in the dictionary tag to point to the Site Page which can serve as their Cookie Policy Page.

Security Settings in Configuration

A new configuration module, Security, is being introduced which enables customers to configure security settings related to password formats, single sign-on (SSO), and session timeout. This allows customers more autonomy by eliminating the need to log Service Requests with Oracle Support to configure security settings.

The following sections are available in the new Security module:

Steps to Enable

There are no steps necessary to enable this feature.

Tips and Considerations

Customers should anticipate that Oracle Support will no longer process Service Requests for security configurations if they have upgraded to Release 17.2.

User Session Timeout

To enhance security, two new settings, Session Maximum Inactive Interval (Seconds) and Session Timeout Reminder Interval (Seconds) are being introduced that allow Administrators to expire a user’s login session after a particular time period of browser inactivity.

Now, when a user abandons their session without terminating their login session, the session will be terminated unless action is taken by the user. A warning modal displays to the user advising them that their session will be terminated within a particular time period unless they extend their session by clicking OK on the modal. Clicking OK dismisses the modal and resets the timers.

Session Timeout Reminder Modal

If no action is taken, the session terminates within the time configured by the Administrator using the two new settings.

Steps to Enable

There are no steps necessary to enable this feature. The feature is enabled at upgrade and cannot be disabled; a positive integer must be entered in both configurations. The delivered default value for the Session Maximum Inactive Interval is 1800 seconds. The delivered default value for the Session Timeout Reminder Interval is 1500 seconds.

To change the default values:

  1. Click Configuration.
  2. Click Security.
  3. In the Session Timeout Security Settings section, click the Pencil Icon to edit the Session Maximum Inactive Interval setting and the Session Timeout Reminder Interval.
  4. Enter a positive integer in seconds.
  5. Click Save.

Tips and Considerations

Administrators should consult with in-house technical standards for alignment with corporate standards.

Configure a reasonable time delta between the display of the warning and the actual expiration.

Time configurations should be made with consideration to what users will be doing in their sessions and for how long they’ll be engaged.

CSS and branding configured in Site Builder should be reviewed for styling impacts on this new modal.

Identity Provider Logout for Single Sign-On (SSO) Users

A new setting, SSO Global Logout, is introduced and when enabled enhances security by terminating an employee’s session on the Identity Provider (IdP) when their Sourcing session is terminated either manually or through abandonment.

Steps to Enable

To enable the feature:

  1. Click Configuration.
  2. Click Security.
  3. In the SSO/SAML Settings (OIF) section, select the toggle next to the SSO Global Logout setting to enable the feature.

Tips and Considerations

This feature is disabled at upgrade.

Validate that your IdP supports Global Logout prior to enabling this feature.

All concurrent sessions within the browser will be terminated for the user if Global Logout is invoked through session termination in Sourcing. This may cause friction for users with concurrent applications using the network.

Exit URL for Single Sign-On (SSO) Users

To enhance the session management experience, a new setting is introduced, SSO Exit URL, which allows Administrators to enter a configurable Exit URL. Employees who are authenticated through SSO can now be directed to a specific destination page via the Exit URL when they terminate their session. Using this configurable Exit URL also ensures that employees only use the site in the authenticated state.

Steps to Enable

The default value at upgrade is blank; no value is entered in the SSO Exit URL setting. In this state, SSO users are directed to the site’s home page when terminating a session.

To direct SSO users to an Exit URL:

  1. Click Configuration.
  2. Click Security.
  3. In the SSO/SAML Settings (OIF) section, enter a valid URL in the SSO Exit URL setting.
  4. Click Save.

Tips and Considerations

The SSO Exit URL setting accepts a single value which is applied to all users terminating sessions from SSO.

Use of an Exit URL which offers a method to re-authenticate into the application from which the user recently exited is common practice for usability.

Direct Apply (17.5)

The Direct Apply feature set offers jobseekers direct access from the Job Details page on Sourcing to the authentication page on the Career Section. This provides a frictionless experience for job applicants from Sourcing by removing the screen which collects email and first and last name information. This is accomplished by introducing a new View Type, otac_17.4.

Other benefits of this feature set include:

With the otac_17.4 View Type enabled, intermediary data collection by Sourcing ceases. Analytics in Sourcing is now populated with more authentic and accurate data from Recruiting. The new otac_17.4 configuration supersedes the Capture Identification from Applicants setting, i.e. the otac_17.4 View Type makes this data collection screen obsolete.

Sourcing and the otac_17.4 View Type respect all existing paradigms in Recruiting to determine whether a referral is accepted or not. If Recruiting accepts the attempt to apply the referral:

Steps to Enable

NOTE: Please note that the Employee Sync must be run at least once prior to enabling this feature.

This feature set is disabled at upgrade. To enable the feature set:

  1. Click Configuration.
  2. Click Jobs.
  3. In the Apply section, click on the pencil icon next to the View Type field.
  4. Select otac_17.4.
  5. Save.

Tips and Considerations

Sourcing supports only candidate level ownership at this time.

Social job promotion by employees prior to upgrade is supported by this feature.

Both Sourcing and Recruiting must be on Release 17.4 before an Administrator is able to execute the otac_17.4 View Type configuration. There is no upgrade chronological dependency.

If the employee who initiated social job promotion leading to a passive referral does not have an encrypted employee ID to include in the URL, a separate service is used to populate those referral relationships in Recruiting.

Legacy configuration of Image Beacon URLs become benign. However, it is recommended that these configurations be removed after feature adoption.

This feature presents no impact to the Upload Friend’s Resume feature.

Expanded Requisition Data on Job Details Page

Extends the requisition standard fields available for display on the Job Details page in Sourcing to a comprehensive data set. There are four sections on which to display up to twenty fields total for each requisition. Customers can choose which fields to display on job requisitions at the site level and can further specify whether to show those fields to internal, external or both types of job seekers.

This functionality allows job seekers to better evaluate if a job is right for them by learning more details about the job using this additional job-specific information.

A new editor, the Field Display and Layout Editor, is available in Site Builder which provides the interface for Administrators to configure which fields in the various sections display on the Job Details page for each site.

Two new sections are introduced to the Job Details page for a total of four available sections to display fields. These four section titles can be relabeled in the dictionary if desired. Any field can reside in any section. The default sections are:

New fields that are added appear in the Additional Information section and inherit the existing styling, colors and fonts used to show requisition data. Drag-and-drop allows Administrators to easily move the newly added fields to different sections and to reorder the fields within sections. Fields are easily removed by clicking the Trash icon.

Prior to Release 17.6, customers could only display Job Requisition fields to employees. Now, fields can be activated for display to employees, non-employees, or both by using the toggle next to each field. Note that non-employees are defined as users with a relationship of Other, Alumni or Referral.

Steps to Enable

There are no steps necessary to enable this feature.

The existing configuration which allowed a limited number of fields to be displayed to employees is propagated to all sites in Site Builder; there is no change to the front end experience at upgrade.

To access the Field Display and Layout Editor:

  1. Click Configuration.
  2. Click Site Builder and then click the Gear icon (Edit Site Settings) next to a site.
  3. Click the Field Display and Layout Editor Link in the Job Details Page section.

Tips and Considerations

The configuration which enabled the existing capability in the Jobs settings is deprecated.

Fields which are not populated do not appear as blank to job seekers; the label is suppressed.

When a section has zero displayed fields for a user the section title is suppressed.

Customers are encouraged to ensure consistency of data by configuring fields as mandatory on the requisition.

Display User-Defined Fields on Job Details Page

The editor introduced in release 17.6 to configure the display of standard fields on the Job Details page is extended to include user-defined fields (UDFs) with release 17.8. As with standard fields, UDFs can be contextualized to a specific site and to both internal and external job seekers.

This allows job seekers to better evaluate if a job is right for them by learning more details about the job using this additional job-specific information contained in the UDFs.

Recruiters no longer need to repeat data which is in UDFs in the long form Job Description in order to ensure that data displays in Sourcing. Administrators are able to select whether UDFs are to be displayed to employee and non-employee audiences.

Changes to configuration are now reflected in Change Logs for both UDFs and standard fields.

Steps to Enable

A Service Request with Support is required to enable this feature. The request should ask that the User-Defined Field Synchronization between Sourcing and Recruiting is enabled.

Once enabled, the UDFs will appear in the editor for the Job Details page. UDFs with picklists of up to 10,000 elements can be synchronized.

Tips and Considerations

Date format UDFs will have unilingual (English) display, consistent with other dates displayed in Sourcing.

In order to use UDFs in Sourcing, the associated OTAC Recruiting zone must be on Release 17.6 or higher.

Streamlined Interface in User Settings

To streamline the navigation in Settings for job seekers to help them manage Job Alert and email preferences, extraneous fields have been removed from, and clarified language has been added to the Job Alerts section in User Settings.

The following three fields, which appeared in the Job Alerts section in Settings, have been deprecated from the product:

Streamlined Job Alert and Frequency Preferences

In addition, for better clarify, the Email opt-in section for both employees and non-employees has new labels.

Email Settings

Steps to Enable

There are no steps necessary to enable this feature.

Tips and Considerations

Any data which was historically gathered in the deprecated fields is not recoverable by customers.

The Email Settings section (formerly known as Email Job Alerts) is used to determine an overall opt-in to emails from the system, including Referrals on Demand or Automated Referral Marketing campaigns; this checkbox is not an opt-in for Job Alerts.

Any label customizations by customers will continue to supersede the new default values.

Employees Sign Up for Job Alerts on Settings Page

Allows employees to sign up for Job Alert emails and set the frequency of those emails in their account Settings page. Prior to Release 17.8, this setting could be used only to opt-out of receiving emails.

Employee Job Alert Opt-In on Settings Page

The display of this section respects the Allow Employees to Sign Up for Job Alerts setting. This setting must be enabled for the section to display to employees and Administrators.

A user who has opted-in to Job Alerts, will not receive Job Alerts emails unless they have at least one interest selected. They also will not receive the emails if they have opted out of receiving all email from the system.

Steps to Enable

There are no steps necessary to enable this feature. However, the existing setting, Allow Employees to Sign Up for Job Alerts, must be enabled.

  1. Click Configuration.
  2. Click Jobs.
  3. Toggle the Allow Employees to Sign Up for Job Alerts setting to enable.

Tips and Considerations

When the Allow Employees to Sign Up for Job Alerts setting is enabled, the section only displays to employees and Administrators who edit employees.

Simplified Job Alert Preferences Management

Offers existing users the opportunity to add a Job Alert opt-in, or expand their job field and location interests. Both external candidates and employees with existing accounts can now add a Job Alert opt-in to those accounts without signing in. Job seekers can use the Job Alert sign-up capability repeatedly to expand their job field and location interests.

This feature supports all cases of Job Alert opt-in where the user is not authenticated, such as Home pages, Landing pages, Settings and widgets.

Steps to Enable

There are no steps necessary to enable this feature.

While there are no steps to enable this feature, the existing setting, Allow Employees to Sign Up for Job Alerts, must be enabled for employees to take advantage of this new behavior.

  1. Click Configuration.
  2. Click Jobs.
  3. Toggle the Allow Employees to Sign Up for Job Alerts setting to enable.

Tips and Considerations

Respects the existing setting, Allow Employees to Sign Up for Job Alerts.

Opting-out of Job Alerts will still require a user to authenticate.

Removing locations or job fields in the Interests will still require a user to authenticate.

Oracle Taleo Onboarding Cloud Service

Form Snapshots

This feature secures the contents from important forms filled out by New Hires as they go through an Onboarding process. Enabling this feature allows Administrators the ability to create a snapshotin time of a form that can be viewed, printed, or exported and that will remain unaffected by future changes in the data. Two new settings are being introduced:

Example:

A New Hire uses her maiden name as she completes her New Employee Contract as part of the Onboarding process. She later gets married and takes on her husbands last name. Later, while applying for an internal position, she updates her personal information to reflect her new married name. Subsequently, a Recruiter prints out the snapshot of her original New Employee Contract and, as expected, sees that the last name is correctly displayed as her maiden name, not her new married name.

Onboarding steps consisting of a fill user-defined formtask can be configured such that submitting the corresponding form will also collect a snapshot of that form. All the snapshots will be tracked within the Onboarding process itself and will be available in the New Hire’s Onboarding process details. Snapshots will be saved in the language in which the form data was originally entered. All snapshots can be exported using TCC.

When the new Save a Point-in-time snapshot of the form and contents at time of completion setting is enabled, snapshots are created in HTML and contain all the instructions, field labels and data. However, branding, images and other styling is not captured. While images are not captured, information relating to images such as their approximate location in the file, size and name can be included in the Snapshot by enabling the new PIT Snapshot setting. The Snapshot is supplemented with all the relevant information regarding the form and corresponding process, including:

Steps to Enable

The Save a Point-in-time snapshot of the form and contents at time of completion setting should be enabled at each step level of a given process for wherever a Snapshot is wanted. To enable Form Snapshots:

  1. Click Configuration.
  2. Click Administration in the Onboarding (Transitions) section.
  3. Click Processes in the Processes and Task Definitions section.
  4. Select the process that you want to use Form Snapshots with.
  5. Select the step that you want to use Form Snapshots with from the Steps tab.
  6. Click Edit next to Properties.
  7. Select the checkbox next to the Save a Point-in-time snapshot of the form and contents at time of completion setting.
  8. Click Finish.

The ability to include image information in the Snapshots is available, but disabled at upgrade. To enable including image information in the Snapshots:

  1. Click Configuration.
  2. Click Settings in the Onboarding (Transitions) section.
  3. You may refine your search results by Keyword and entering image.
  4. Click the Image in PIT Snapshot setting.
  5. Click Edit.
  6. Select Yes under Value.
  7. Save.

Tips and Considerations

This feature is disabled at upgrade.

This feature does not change the user experience for New Hires.

Because Form Snapshots are enabled and configured by the Onboarding Administrator, no additional steps need to be performed by the Onboarding specialist to create the snapshots.

Activate the feature gradually and verify that the normalized rendering of the snapshots are adequate. Customers may want to modify the layout of some forms in order to optimize the quality of the snapshot.

In addition to Work experience, Education and References, Certifications can now also be rendered on the Onboarding form. Consequently, this information can also all be captured on Form Snapshots.

New Hires Upload Multiple Files on a Single Task

Streamlines the user interface and offers process clarity to new hires when uploading documents in their onboarding process. Tasks can now be configured to allow new hires to upload a file for up to twenty-five categories when completing a single Content Page Task. Up through Release 17.7, only a single file could be uploaded. New hires now select a category when uploading a file. Only a single file may be uploaded per File Category.

A new Category selector shows all the categories which are configured by the Administrator. The list of categories may include both mandatory and optional categories, and appears in an order prescribed by the Administrator. The mandatory categories configured by the Administrator are listed on the page and indicated with an asterisk.

When a category has been fulfilled through the uploading of a file, that category automatically hides from the Category selector. Deleting a file allows the File Category associated to that file to reappear on the Category selector, allowing a new file to be uploaded for that category. A new table shows the uploaded files with a Delete function.

Category Selector and Files Uploaded Table

Content Pages now allow up to twenty-five File Categories to be configured in a new File Categories section. These File Categories now have descriptions with labels in every activated content language. These multilingual labels are displayed to New Hires in the Tasks tab and in the Onboarding Center. At upgrade, the existing unilingual code for each category is propagated to the multilingual translation for each activated content language.

Content Pages File Categories Configuration

Steps to Enable

There are no steps necessary to enable this feature.

While there are no steps necessary to enable this feature, Administrators must configure multiple File Categories on a Content Page Task before new hires can upload multiple files on a single task in the onboarding process.

Tips and Considerations

Ensure that candidate-friendly labels and/or translations are in place for File Categories prior to configuring multiple categories on a single Content Page.

There is no change to behavior at upgrade.

This feature preserves the system paradigm of allowing a single file upload into a File Category and the user interface when there is a single File Category configured on a Content Page Task.

Take note of the value in the Attached File Maximum Number setting. Avoid requiring more files of candidates than the value configured in this setting (pre-existing behavior; no change).

Oracle Taleo Scheduling Center Cloud Service

Interview Reminders to Calendar Owner

Calendar owners can receive daily and weekly reminders for scheduled interviews. Sending periodic automated reminders provides an easy way for interviewers to be aware of upcoming interviews and ensures that interviews are not missed.

When administrators enable the feature, calendar owners receive email message listing appointments scheduled for them over the week or the day. The appointment date and time are indicated as well as the candidate name and email address.

Steps to Enable

Administrators can set weekly or daily interview reminders.

To set the reminder:

  1. Click Scheduling Center.
  2. Click Configuration.
  3. Click the setting Schedule Appointments Email.
  4. Set the setting to active.
  5. Select the frequency that is, weekly or daily.
  6. Click Save.

A new message template is available: Schedule Appointments.

Notify Calendar Owner of Time Slot Unavailability

Calendar owners receive an automated email notification when candidates cannot find a suitable interview time slot while self-scheduling an interview. With this feature, candidates no longer need to send a manual notification to the recruiter.

While scheduling an appointment, candidates click the No Feasible Timeslots button to notify the calendar owner that they cannot find a suitable interview time. The calendar owner then automatically receives an email notification entitled Timeslots Not Feasible which contains candidate information and the calendar name.

Steps to Enable

There are not steps necessary to enable this feature. If desired, you can modify the email template Timeslots Not Feasible.

If you wish to not trigger the email notification, you can disable the feature. Note however that the No Feasible Timeslots button will still be available to candidates.

To disable the feature:

  1. Click Scheduling Center.
  2. Click Configuration.
  3. Click Email Templates.
  4. Click Timeslots Not Feasible.
  5. For the Send Email option, select No.
  6. Click Save.

Schedule Interviews with Shorter Intervals

Calendar owners can schedule interviews with a 5-minute interval.

If shorter intervals are enabled, you can select an interval between 5 and 55 minutes when you add a timeslot to a calendar.

Add Timeslot Page

Steps to Enable

To set interview intervals:

  1. Click Scheduling Center.
  2. Click Configuration.
  3. Click the setting Enable Granular Timeslot Setting.
  4. Set the interview intervals:
  5. Select Yes to set 5-minute intervals.
  6. Select No to set 15-minute intervals.
  7. Click Save.

Tips and Considerations

When upgrading to Release 17.8 or setting a new zone, the Enable Granular Timeslot Setting is set to No by default. Interview intervals are every 15 minutes.

Oracle Taleo Enterprise Cloud Service – SmartOrg

Legacy SSO Deactivation

Customers can deactivate all legacy single sign-on (SSO) configurations and enable the self-serve sign-on.

A new setting is available:

The setting is set to No by default. Changing the setting to Yes has the following effects:

Steps to Enable

NOTE: Deactivating the legacy single sign-on will permanently erase all SSO configurations.

To deactivate the legacy single sign-on:

  1. Click Configuration.
  2. In the General Configuration section, click Settings.
  3. Search for the Legacy SSO Deactivation setting.
  4. Click the name of the setting.
  5. Click Edit.
  6. Set the value to Yes.
  7. Click Save.

Oracle Taleo Enterprise Cloud Service – OBI Reporting

New Reporting Fields in the Recruiting Subject Area

New reporting fields were added to the Recruiting subject area.

More than 800 fields, including template reporting and correspondence fields, were added to the Recruiting contemporary subject area to have a better alignment with the Recruiting legacy subject area.

Steps to Enable

There are no steps necessary to enable this feature.

Key Resources

For more information on the new reporting fields added to the Recruiting subject area, go to the following document on My Oracle Support:

New Reporting Fields in 17.3

New reporting fields were added to the Recruiting, Administration, and Performance subject areas.

Recruiting Subject Area:

Administration Subject Area:

Performance Management Subject Area:

Steps to Enable

There are no steps necessary to enable this feature.

Key Resources

For more information on the new reporting fields added to the Recruiting, Administration, and Performance subject areas, go to the following document on My Oracle Support:

Oracle Taleo Enterprise Cloud Service Connect Client

Support of Certificate Authentication

Improve security by adding certificate support in communications between Connect Client and Oracle Taleo Enterprise Cloud Service zone.

Currently, basic authentication with a user name and password is available to connect to the Oracle Taleo Enterprise Cloud Service environment. With Release 17, a new authentication method using certificates is available. With the certificate based authentication, you generate certificates on both the Connect Client and Taleo environments and you import them in each environment.

The Connect Client administrator generates certificates in Connect Client using the new Certificate Management feature. Once a certificate is generated, the administrator downloads it in the Taleo environment. The Taleo administrator then imports the certificate in the Taleo environment.

Certificate Management in Connect Client

The Taleo administrator generates certificates in Taleo Configuration using the new TCC Security feature. Once the certificate is generated, the administrator downloads it in the Connect Client environment. The Connect Client administrator then imports the certificate in the Connect Client environment.

Certificate Management in Oracle Taleo Enterprise Cloud Service

The requests and responses between Connect Client and Taleo are signed, and the signature is validated before processing the requests and responses. Both certificates are needed for the signing feature to work.

Several certificates can be created on both the Connect Client and Taleo environments. Only one certificate can be valid at a given time. If there is no valid certificate, the job fails and an error is displayed. Certificates must have validity periods that do not overlap.

Steps to Enable

To enable the certificate based authentication method in Taleo, the TCC Security feature must be enabled.

  1. In Taleo, access Configuration.
  2. In the General Configuration section, click Settings.
  3. Search for the setting named Activate TCC Cert Based Authentication.
  4. Click the name of the setting.
  5. Set the value to Yes.
  6. Click Save. The TCC Security feature appears in the Security section of the Configuration page.

To generate a certificate in Connect Client:

  1. In Connect Client, access Certificate Management.
  2. In the Certificate Management window, click Generate.
  3. In the Add Certificate window, provide a start date, end date, and alias.
  4. Click Generate.
  5. In the Certificate Management window, select the certificate you just created.
  6. Click Download.
  7. The Taleo administrator must then import the TCC certificate using the TCC Security feature in Taleo.

To generate a certificate in Oracle Taleo Enterprise Cloud Service:

  1. In Taleo, access Configuration.
  2. In the Security section, click TCC Security.
  3. In the TCC and TEE Certificate Management window, click Generate Certificate.
  4. In the Generate Certificate window, provide a start date, end date, and alias.
  5. Click Generate.
  6. In the TCC and TEE Certificate Management window, click Download next to the certificate you just created.
  7. The Connect Client administrator must then import the TEE certificate using the Certificate Management feature in Connect Client.

Tips and Considerations

The use of certificates between Connect Client and Oracle Taleo Enterprise Cloud Service is optional but recommended for enhanced security.

Support of TLS 1.2

Improve security with the new Transport Layer Security (TLS) 1.2 cryptographic protocol.

TLS 1.2 is now supported for identity verification between Connect Client and Oracle Taleo Enterprise Cloud Service.

Tips and Considerations

Both Connect Client and Oracle Taleo Enterprise Cloud Service must be on Release 17.x for TLS 1.2 to be available between them.

Oracle Taleo Enterprise Cloud Service – Fluid Recruiting

Fluid Recruiting

Fluid Recruiting is an HTML recruiting solution that helps enterprises assess and hire the best talent.

Fluid Recruiting offers a simple and modern user interface usable on desktop, laptop, tablet, and smartphone. Fluid Recruiting works on the Oracle Talent Acquisition Cloud platform, capitalizing on the same user accounts, user types, user permissions, settings, and other configuration. Fluid Recruiting leverages concepts, icons, data, and behavior similar to the Recruiting Center while providing an improved user experience.

The initial release of Fluid Recruiting focuses on reviewing and dispositioning candidate submissions. Users can use Fluid Recruiting in parallel with the existing Recruiting Center. They can process candidates in Fluid Recruiting. If they need to take further actions beyond processing candidates, they can return to the Recruiting Center to complete the tasks.

The following capabilities are provided with the initial release:

Steps to Enable

To access Fluid Recruiting, the following user permission is required. The new permission is available under Recruiting > Other > General.

Tips and Considerations

Fluid Recruiting supports the same set of languages as the Recruiting Center. All languages activated in the Recruiting Center are reflected in Fluid Recruiting.

New Fluid Recruiting Functionalities (17.2)

Fluid Recruiting continues to expand in functionality. As part of the 17.2 release, several new capabilities have been added to the Fluid Recruiting experience.

These new functionalities are similar to those in the Recruiting Center but provides an improved user experience. New functionalities include.

Steps to Enable

There are no steps necessary to enable these features. Customers only need to grant users the permission to access Fluid Recruiting. If users are granted the permission to do these actions in Recruiting Center, they will also be able to do these actions in Fluid Recruiting.

New Fluid Recruiting Functionalities (17.4)

Fluid Recruiting continues to expand in functionality. As part of the 17.4 release, several new capabilities have been added to the Fluid Recruiting experience.

New functionalities include.

New Fluid Recruiting Functionalities (17.6)

Fluid Recruiting continues to expand in functionality. As part of the 17.6 release, several new capabilities have been added to the Fluid Recruiting experience.

New Fluid Recruiting Functionalities (17.8)

Fluid Recruiting continues to expand in functionality. As part of the 17.8 release, several new capabilities have been added to the Fluid Recruiting experience.

When you create a requisition using a template, you first specify the hire type, you then select a template, and you specify attributes such as organization, location, job field. Once this is done, you complete fields in the requisition form.

When you view a requisition, use the Duplicate this requisition action to create a similar requisition. A requisition can be duplicated regardless of its status. When duplicating a requisition, all of the information is duplicated.

When candidates reach the Offer stage, you can create offers. Use the Create Offer action and complete the fields in the offer form. During this process, you can also create an offer letter, set and update the start date and expiration date, and set the start date as tentative.