Oracle Talent Acquisition Cloud. What s New in Release 15B

Transcription

1 Oracle Talent Acquisition Cloud What s New in Release 15B September 2016 Revised: November 2016

2 TABLE OF CONTENTS REVISION HISTORY... 4 OVERVIEW... 5 Give Us Feedback... 5 RELEASE FEATURE SUMMARY... 6 RECRUITING... 8 File Formats for Correspondence Attachments... 8 Automatic Approval Reminders... 9 Separate Date and Time Correspondence Variables for Offer Expiration Disabling the JavaScript API Fifth Section Added to Offer Form Job Submission Completed Date in Candidate Lists Disabling Icons in the Rich Text Editor Pay Basis Enhancements Requisition Creation from a Position not Linked to a Requisition Template Ability to Specify a Position in Offers Ability to Specify a Worker Location HRMS Worker Information Integration Additional Worker Correspondence Variables Evaluation Management Enhanced Integration with Microsoft Exchange Server 2010 SP Secure LDAP and Active Directory Connections Recruiting Embedded Reporting Scheduling Reports Report Notifications Monitoring Scheduled Reports Monitoring Report Activities Searching for Reports Exporting Reports CAREER SECTION Perpetual Display of Partner Import Services Login Information Layout Change Resume Block Layout Change Facebook Feature No Longer a Career Section Property Faceted Search Auto-Suggest - Two Characters Facets Reflect Faceted Search OLF Selections New User Registration Using Third-Party Credentials SMARTORG Masking Newly Created User Password SOURCING Locale Name Harmonization with Recruiting Languages Locale Harmonization Migration Language Toggle on All Pages and Refactored Navigation Browser Language Determines Session Language Multilingual Custom Content Blocks Geolocation Customization Backup and Restore Sort and Filter Locations in Geolocation Editor Location Search Fallback to Keyword Search

3 Edit Font Style and Size in Content Blocks Upload Custom Fonts Extend Use of Customer Name Display Apply Button for Recruiters and Administrators Role-Specific Links to My Profile and My Submissions Career Section Job Description URL s Target Specific Sites Self-Service Facet Management for Standard Facets Date Override on Manual Job Synchronization CONNECT CLIENT Removal of the User Name Token Authentication Method Export of Historical Fields Tied to Equal Employment Opportunity HCM MOBILE CLOUD New Mobile Hiring

4 REVISION HISTORY This document will continue to evolve as existing sections change and new information is added. All updates are logged below, with the most recent updates at the top. Date What s Changed Notes 21 NOV 2016 Recruiting: Recruiting Enhancements for the Out-of-the-Box Integration Solution Removed the feature Recruiting Enhancements for the Out-of-the-Box Integration Solution. Enhancements done for the future OOTB solution Version 2 such as pay basis, position, worker location and worker related fields are described within specific features of the document. 01 OCT 2016 Recruiting: Report Notifications Added details on message template triggering events for report notifications. 01 OCT 2016 Platform: RCC Supports Automatic Upgrade to Weblogic Removed the feature RCC Supports Automatic Upgrade to Weblogic because RCC is an internal tool. 06 SEP 2016 Initial document creation. 4

5 OVERVIEW This document outlines the information you need to know about new or improved functionality in Oracle Talent Acquisition Cloud Release 15B. 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. The Oracle Talent Acquisition Cloud What s New document, formerly called Taleo Release Notes, covers new or improved functionalities for Recruiting, Career Section, Sourcing, Onboarding, Reporting, Platform, and Connect Client. For new functionalities related to Taleo Performance, please refer to the Oracle Taleo Performance Cloud What s New document. NOTE: These documents can be found on the Oracle Help Center at: under Human Capital Management Release Readiness, Talent Management. In the Taleo Recruiting Center, the Communications tab has been revamped to provide users a direct link to the Oracle Talent Acquisition Cloud What s New located on the Oracle Help Center. This change will allow you to obtain new information at a faster rate. Bug fixes documentation for the 15B release can be found on the My Oracle Support, on the Taleo Enterprise Documentation Homepage (document ID ). 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. 5

6 RELEASE FEATURE SUMMARY Some of the new Release 15B 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 15B features. Feature Recruiting File Formats for Correspondence Attachments Automatic Approval Reminders Separate Date and Time Correspondence Variables for Offer Expiration Disabling the JavaScript API Automatically Available Action Required to Enable Feature End User Administrator Action Action Required Required Oracle Service Request Required Fifth Section Added to Offer Form Job Submission Completed Date in Candidate Lists Disabling Icons in the Rich Text Editor Pay Basis Enhancements Requisition Creation from a Position Not Linked to a Requisition Template Ability to Specify a Position in Offers Ability to Specify a Worker Location HRMS Worker Information Integration Additional Worker Correspondence Variables Enhanced Integration with Microsoft Exchange Server 2010 SP3 Secure LDAP and Active Directory Connections Scheduling Reports Report Notifications Monitoring Scheduled Reports Monitoring Report Activities Searching for Reports Exporting Reports Career Section Perpetual Display of Partner Import Services Login Information Layout Change Resume Block Layout Change Facebook Feature No Longer a Career Section Property Faceted Search Auto-suggest Two Asian Characters Facets Reflect Faceted Search OLF Selections New User Registration Using Third-Party Credentials SmartOrg Masking Newly Created User Password Sourcing 6

7 Feature Locale Name Harmonization with Recruiting Languages Locale Harmonization Migration Language Toggle on All Pages Browser Language Determines Session Language Multilingual Custom Content Blocks in Site Builder Geolocation Customization Backup and Restore Sort and Filter Locations in Geolocation Editor Location Search Fallback to Keyword Search Refactored Navigation Edit Font and Size in Content Blocks and Campaigns Upload Custom Fonts Extend Use of Customer Name Display Apply Button for Recruiters and Administrators Role-Specific Links to My Profile and My Submissions Career Section Job Description URLs Target Specific Sites Self-Service Facet Management for Standard Facets Date Override on Manual Job Synchronization Connect Client Removal of the User Name Token Authentication Method Export of Historical Fields Tied to Equal Employment Opportunity HCM Mobile Hiring New Mobile Hiring Automatically Available Action Required to Enable Feature End User Administrator Action Action Required Required Oracle Service Request Required 7

8 RECRUITING FILE FORMATS FOR CORRESPONDENCE ATTACHMENTS System administrators can define which file formats are supported for files attached to message templates and correspondence sent to candidates. Supported file formats are: Any File Format (default value) Excel (.xls,.xlsx) Hypertext Markup Language (.htm) Hypertext Markup Language (.html) OpenOffice Writer (.odt) Portable Document Format (.pdf) Rich Text Format (.rtf) Text (.txt) Word (.doc,.docx) Word Perfect (.wpd) Zip Format IMPORTANT: The value Any File Format includes all the above file formats as well as any other format. Using the setting Attachments Format Filter in Correspondence, system administrators select which file formats are supported. The selected file formats will restrict the types of files that can be attached to message templates for both the Recruiting and Onboarding (Transitions) products and also in correspondence sent manually using the Send Correspondence action in Recruiting. After a file is attached, the system validates if the file format is supported. The validation is performed whether the file is attached by the system administrator on a message template or by a recruiter on a correspondence. If the file format is not supported, the system prevents the operation and an error message is displayed listing the supported file formats. This functionality helps prevent unsafe files from being maliciously or inadvertently sent to candidates. It also helps avoid the use of file formats that are not desired or not supported based on corporate policies or best practices. To specify supported attachment file formats: 1. Click Configuration. 2. In the General Configuration section, click Settings. 3. Search for the setting named Attachments Format Filter in Correspondence. 4. Click the name of the setting. 8

9 5. Click Edit. 6. Select the file format to be supported from the Available Values list and click Add. The file format appears in the Selected Values list. Repeat this step for each supported file format. 7. If you want to remove a supported file format, select the file format in the Selected Values list and click Remove. 8. Click Save. Clicking the Reset button will change the configuration back to the default setting which is Any File Format. TIPS AND CONSIDERATIONS When upgrading to release 15B or when a new customer zone is being created, the default value of the Attachments Format Filter in Correspondence setting is Any File Format. Files attached in previous releases and files attached while the setting was set to Any File Format will continue to be supported even if their format is no longer supported. To prevent future undesirable attachments, system administrators should remove any file formats that are not desired by their company. They should also go through existing message templates and, if applicable, remove any undesirable attachments that may be used. AUTOMATIC APPROVAL REMINDERS System administrators can configure an automatic reminder so that s are sent to approvers to remind them to review and approve offers and requisitions. In prior releases, users were sent a notification to approve offers and requisitions. However, if users lost the message or forgot about the approval, they were not reminded that they had to provide their approval. In release 15B, system administrators can configure an automatic reminder to remind approvers that they need to review and approve offers and requisitions. Two settings are available: Requisition Approval Automatic Reminder Offer Approval Automatic Reminder System administrators configure these settings by defining the number of days after which a reminder is sent to remind approvers to review and approve offers and requisitions. When an approval task is created and a notification is sent to a user by , the system automatically sends a reminder to that user if a decision has not yet been taken within the time span defined. The system continues to send the reminder at the defined frequency (number of days) until the approver provides a decision on the approval request. Note that after one year, reminders are no longer sent. As an example, if the setting is set to 1 day, reminders will be sent every day for a period of one year or until the approver provides a decision. If the setting is set to 7 days, a reminder will be sent every week. 9

10 This functionality decreases the likelihood of approvers holding up the approval process. It also reduces the approval process duration. To enable the requisition approval automatic reminder: 1. Click Configuration. 2. In the Recruiting section, click Settings. 3. Search for the Requisition Approval Automatic Reminder setting. 4. Click the name of the setting. 5. Click Edit. 6. In the Value field, indicate the number of days after which you want to remind approvers to provide a decision on requisition approvals. The maximum value is 365 days. Setting the value to 0 does not send any reminder. 7. Click Save. To enable the offer approval automatic reminder: 1. Click Configuration. 2. Search for the Offer Approval Automatic Reminder setting. 3. Click the name of the setting. 4. Click Edit. 5. In the Value field, indicate the number of days after which you want to remind approvers to provide a decision on offer approvals. The maximum value is 365 days. Setting the value to 0 does not send any reminder. 6. Click Save. TIPS AND CONSIDERATIONS When upgrading to release 15B or when a new customer zone is being created, the value of the Requisition Approval Automatic Reminder and Offer Approval Automatic Reminder settings is set to 0. No reminder is sent. The following message templates are used for both the notifications and automatic approval reminders. Since the same message templates are used, it might be beneficial for system administrators to make adjustments to the content of the four message templates. Standard Notification for an Offer Approval Request Standard Notification for an Offer Approval Request (E-Share) Standard Notification for a Requisition Offer Approval Request Standard Notification for a Requisition Approval Request (E-Share) Sending of reminders is tracked in the requisition and offer History tab. 10

11 KEY RESOURCES For more information on approvals, review the following topic in the Oracle Taleo Enterprise Recruiting Configuration Guide: Requisition and Offer Approvals SEPARATE DATE AND TIME CORRESPONDENCE VARIABLES FOR OFFER EXPIRATION The offer expiration date and offer expiration time variables can be used together or separately in correspondences. In prior releases, the {Offer.ExpiryDate} correspondence variable provided both the date and time of the offer expiration. In release 15B, the {Offer.ExpiryDate} only provides the date. To display the time of the offer expiration, a separate variable is available: {Offer.ExpiryTime}. System administrators can choose to include the date, the time, or both for correspondences using these variables: {Offer.ExpiryDate} will show the offer expiration date. {Offer.ExpiryTime} will show the offer expiration time. {Offer.ExpiryDate} {Offer.ExpiryTime} will show both the offer expiration date and time. There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS This functionality provides a slightly different behavior than in previous releases. System administrators may want to reconfigure message templates that are using the {Offer.ExpiryDate} variable so that the expiration time remains included and displayed as it was (or maybe displayed in a different manner). DISABLING THE JAVASCRIPT API System administrators can enable or disable the JavaScript API functionality in Recruiting. A JavaScript API can be used by customers to dynamically extract information from fields displayed in specific pages of the Recruiting Center, send the information to an external system, and capture the information back into the Taleo fields. In prior releases, the JavaScript API was always active. In release 15B, the JavaScript API can be disabled if the customer is worried about various security threats. A setting is available: Enable JavaScript API. If the setting is set to No and a recruiter creates a method in JavaScript and attempts to run it, the system will see that the JavaScript API is disabled and it will not execute the method. This functionality prevents malicious extraction or insertion of information with scripting from the Recruiting product. 11

12 To configure the JavaScript API: 1. Click Configuration. 2. In the Recruiting section, click Settings. 3. Search for the Enable JavaScript API setting. 4. Click the name of the setting. 5. Click Edit. 6. Select Yes to activate the API or No to deactivate it. 7. Click Save. TIPS AND CONSIDERATIONS When upgrading to release 15B or when a new customer zone is being created, the Enable JavaScript API setting is set to No. This represents a change of functionality for customers because the JavaScript API was always enabled before release 15B. FIFTH SECTION ADDED TO OFFER FORM A new section is available in the offer form to provide more flexibility in the organization of offer information. The offer form originally provided four sections to organize offer information: Top Section, General Terms, Bonuses, Details. In release 15B, a fifth section called Other Terms is available. Moreover, the name of the offer form sections (categories) can be customized to better align with a company s terminology. Offer Form Layout Configuration Page System administrators can configure the Other Terms section just like any other sections in the offer form. To customize the name of offer form sections, a Service Request to Oracle Support to modify TextTool resources is required. Below are the resource IDs of the section names: 12

13 KEY RESOURCES Top Section: General Terms: Bonuses: Details: Other Terms: For more information on configuring offer form sections, review the following topic in the Oracle Taleo Enterprise Recruiting Configuration Guide: Configuring the Offer Form JOB SUBMISSION COMPLETED DATE IN CANDIDATE LISTS When configuring list formats, system administrators can add a column, called Submission Completed Date, in requisition-specific candidate lists so that recruiters can view and sort candidate submissions based on the date when a job submission was completed. Once the column Submission Completed Date is added to a requisition-specific candidate list, the title of the column in Recruiting is displayed as Submission Complete. Information in the Submission Complete column appears as follows: A blank value means that the submission has not yet been completed. Dates are displayed using the format configured in Regional Settings, under the SmartOrg Administration (used throughout the system). Ascending sorting (arrow pointing upwards) displays the oldest submissions at the top of the list. Note that when sorting on the Submission Complete Date column, blank values (incomplete submissions) are always displayed at the bottom of the list, whether sorting in an ascending or descending order. Submission Complete Column in Candidates List Job submissions are considered complete when: A candidate completed a job submission and clicked the Submit button. A candidate (usually internal candidate) refers someone when creating or updating a submission. An agent refers someone when creating or updating a submission. 13

14 A recruiter matches a candidate to a requisition (when creating a new job submission or when a match is done with an incomplete job submission). An import is done on a job submission. A candidate is hired on a job submission. System administrators can add the new Submission Completed Date column in list formats just like any other columns. TIPS AND CONSIDERATIONS This feature was developed to allow recruiters to look through a list of candidate submissions from top to bottom, where the candidate submission on the top is the oldest and the one at the bottom is the most recent. In some companies, this way of screening is mandatory as selection is performed in a first come first serve manner. To do this, the recruiter must see and sort on the submission completion date (ascending order) such that the oldest submissions are displayed on the top and the recruiter goes down through the list one candidate at a time. In addition to this, the correct filter must be activated in order not to include submissions that are not completed. System administrators should verify if they were using the Submission Creation Date column in list formats to accomplish a behavior similar to the new Submission Completed Date column. If this is the case, it is recommended to use the new Submission Completed Date column instead because the Submission Creation Date column can include candidates that have not completed their submission (either because they saved as draft and never came back or simply because they simply dropped out of the process. All candidate (submission) list contexts support the new Submission Completed Date column except for the following: KEY RESOURCES All Candidates by Folder All Candidates by Offer All Candidates by Talent Pool Candidate Capture/Possible Duplicates List of automatically pooled candidates Search results/advanced search Search results/ Conceptual search Search results/ Quick search For more information on configuring lists, review the following topic in the Oracle Taleo Enterprise Recruiting Configuration Guide: Configuring List Formats 14

15 DISABLING ICONS IN THE RICH TEXT EDITOR System administrators can disable icons in the rich text editor to reduce complexity or prevent users from including JavaScript code into requisition descriptions, notifications or correspondence. Using the setting Rich Text Editor Disabled Icons, system administrators can disable any or all icons except for the Enlarged view icon. Rich Text Editor Toolbar To disable icons in the rich text editor: 1. Click Configuration. 2. In the General Configuration section, click Settings. 3. Search for the setting named Rich Text Editor Disabled Icons. 4. Click the name of the setting. 5. Click Edit. 6. Enter the icon code name of the icons you want to disable, separated by a comma. 7. Click Save. TIPS AND CONSIDERATIONS When upgrading to release 15B or when a new customer zone is being created, no icons are disabled. The setting Rich Text Editor Disabled Icons prevents users from using the deactivated icons in future text creations only. This setting does not affect any existing requisition descriptions, notifications or correspondences. IMPORTANT: This configuration applies to the rich text editor in Recruiting and Onboarding. It is not supported in Evaluation Management, Performance Management and Sourcing. KEY RESOURCES For more information on the rich text editor functionalities, review the following topic in the Oracle Taleo Enterprise Recruiting Configuration Guide: Rich Text Editor PAY BASIS ENHANCEMENTS Pay Basis information found in requisitions and offers has been enhanced to provide new functionalities. 15

16 Pay Basis values are available in the Recruiting Administration menu, under Pay Basis List where Oraclesourced values can be deactivated. For backward compatibility reasons, the values Yearly (default value) and Hourly cannot be deactivated. Pay Basis values can also be imported from an external HRMS system. Contrary to Oracle-sourced values, deactivation of imported Pay Basis values is possible only through integration. For each pay basis, the following information is available: Code of the pay basis (mandatory and must be unique). Name of the pay basis in all the languages used in the company. Annualization factor (mandatory). Currency (imported pay basis values only). Worker legal employer (imported pay basis values only). Status. IMPORTANT: Oracle-sourced values cannot be configured to contain currency and worker legal employer information. Pay Basis List Configuration Page Recruiters define a pay basis when creating requisitions or offers. When a Pay Basis value is selected, the corresponding annualization factor is displayed under the Pay Basis field. When mousing over the value in view mode, a window displays details such as name, code, and annualization factor. When only Oracle-sourced Pay Basis values are available in the system, the recruiter selects a pay basis using a drop-down list. 16

17 Pay Basis Drop-Down List in Requisition When Pay Basis values have been imported in the system, the recruiter selects a pay basis using a selector which provides auto-suggest capability. The Pay Basis Selector page contains both Oraclesourced values and imported values. The selector provides quick filters and displays the code, name, and annualization factor of each pay basis as well as the worker legal employer and currency if those values are set for the selected pay basis (and if these fields are configured as available). Pay Basis Selector in Requisition The annualization factor is obtained by calculating the annualized salary off of a salary based on the selected pay basis (or vice versa). For example, if the pay basis is weekly, the annualization factor is 52 since there are 52 weeks in a year. When creating an offer, the recruiter enters a salary in the Salary (Pay Basis) field. The recruiter can specify a Pay Basis value different than the one defined in the requisition. The recruiter can click the calculator icon to calculate the corresponding annualized salary. The system fills-in the calculated value based on the annualization factor. If currency information is available for the selected pay basis, the Currency field automatically populates with that value and cannot be edited. If no currency was configured, the Currency field is empty and is editable. Pay Basis Field in Offer Form 17

18 To activate an Oracle-sourced pay basis: 1. Click Configuration. 2. In the Recruiting section, click Administration. 3. In the General Configuration section, click Pay Basis List. 4. Click Activate next to the pay basis you want to activate. The only way to deactivate an imported pay basis, even after it has been used, is via integration. Once deactivated, an imported pay basis will remain displayed on the Pay Basis list but marked as Inactive. For backward compatibility reasons, the values Yearly and Hourly cannot be deactivated. They are always activated. TIPS AND CONSIDERATIONS When configuring the offer form, system administrators should position the Pay Basis, Salary (Pay Basis), Annualized Salary and Currency fields together as a group since they are linked via calculation. Ideally, these fields should be laid out in the sequence order that most users would expect to enter the information. When a candidate is hired, the pay basis included in the offer can be exported to the HRMS system for a New Hire record to be created. REQUISITION CREATION FROM A POSITION NOT LINKED TO A REQUISITION TEMPLATE When recruiters create a requisition from a position, the position no longer needs to be linked to a requisition template. In prior releases, the requisition creation wizard would display either the Requisition Template selector or the Position selector and positions were linked to requisition templates. In release 15B, when recruiters create requisitions and positions are activated, recruiters can select a position that is not linked to a requisition template. If positions are activated, recruiters see the Positions selector (instead of the Requisition Template selector) in the requisition creation wizard. The list of positions displayed depends on the recruiter s permissions. If the recruiter can create requisitions without any restriction, then all compatible positions are displayed and available (even if not linked to a requisition template). If the user s permission is limited to template-linked positions, then only those are displayed. For this new functionality to work, the concept of position must be enabled by system administrators. To enable the position concept: 1. Click Configuration. 2. In the Recruiting section, click Settings. 18

19 3. Locate the setting Enable Position. 4. Click on the setting name. 5. Click Edit. 6. Select the Yes value. 7. Click Save. To enable the creation of requisitions from a position: 1. Click Configuration. 2. In the Recruiting section, click Settings. 3. Locate the setting Select a Position when creating Requisitions (if concept of Position is activated). 4. Click on the setting name. 5. Click Edit. 6. Select the Yes value. 7. Click Save. For this new functionality to work, the constraints for the Create Requisition permission have been modified. The "Only from a requisition template" constraint that applied to the Create Requisition permission was originally meant to prevent users from creating a requisition from scratch. In release 15B, since a position can be used without being linked to a requisition template, users would no longer be prevented from creating a requisition from scratch. Consequently, the constraints were updated to ensure that, if a position is used to create a requisition, then the position must be linked to a requisition template. When this constraint is enforced, positions without a requisition template will not be available in the selector. The new Create Requisition constraints are: Only from a requisition template or template-linked position (all requisition types, except contingent) Only from a requisition template or template-linked position (contingent recruitment) ABILITY TO SPECIFY A POSITION IN OFFERS The Position field, traditionally available only in requisitions, can be added to offers. System administrators can configure the Position field to appear in the offer form. Once available in the offer form, the recruiter can specify a value for the Position field when creating an offer. The recruiter can copy the value originating from the requisition if one exists or select a different value. A different position can be selected for each offer within a same requisition. 19

20 Position Field in Offer Form To configure the Position field to appear in the offer form: 1. Click Configuration. 2. In the Recruiting section, click Administration. 3. Under Fields, click Offer. 4. Click the Position field. 5. Click Edit Field Availability. 6. In the Offer Field Editor - Position page, select Taleo Recruiting, specify if the Position field content is required for saving or not, and define the security level. 7. Specify any relevant Organizations, Locations, or Job Fields (OLF) contextual information. 8. Click Save. 9. Go back to the Recruiting Administration page. 10. Under Fields, click Offer Field Layout. 11. Locate the Position field. 12. Specify where in the offer form the Position field will appear (category and line). 13. Click Apply. TIPS AND CONSIDERATIONS When a candidate is hired, the position included in the offer can be exported to the HRMS system for a New Hire record to be created. Specific positions can be included in new hire s offer within a multi-hire requisition. KEY RESOURCES For more information on configuring the offer form, review the following topics in the Oracle Taleo Enterprise Recruiting Configuration Guide: Configuring Offers Positions 20

21 ABILITY TO SPECIFY A WORKER LOCATION The Worker Location field is a new field available in Recruiting. The worker location is used as an employee (post-hire) function whereas the primary location (in OLF) is meant for recruiting purposes. For example, a primary location could be 100 Main Street and a worker location could be Sector 44 or Cubicle A. Worker locations cannot be created in Taleo Configuration. Worker locations are typically imported from an external HRMS system. Once worker locations are imported, worker locations can be mapped to the SmartOrg Location structure via Integration or by the system administrator in Taleo Configuration. Any Location element can be given the Worker Location property and a physical address. System administrators can then configure worker locations to appear in requisitions, offers, correspondences, requisitions lists, and candidates lists just like any other fields. When creating a requisition from scratch, the recruiter can specify a worker location if the field is available in the requisition. When the recruiter clicks the selector icon, the Worker Location Selector displays all the worker locations configured by the system administrator. Worker Location Field in Requisition When a recruiter creates a requisition and selects a Primary Location for the requisition, the Location Selector provides a new option to display only worker locations. If the recruiter selects a location that is a worker location, both the Primary Location and Worker Location fields will be populated in the requisition. On the other hand, if the recruiter selects a location that is not a worker location, only the Primary Location field will be populated in the requisition. The Worker Location field will be empty. However, the recruiter will be able to click the selector icon next to the Worker Location field and manually select a worker location. By default, the Worker Location selector will be pre-filtered to show only worker locations which are compatible with the Primary Location if one has been specified. The recruiter can cancel this pre-filtering and select a worker location even if it is not compatible to the Primary Location. 21

22 Show only worker locations Option in Location Selector When creating an offer, the recruiter can specify a worker location whether or not it was originally identified in the requisition. Also, if a worker location was specified in the requisition, it is possible to specify a different value in the offer. A different worker location can be selected for each offer within a same requisition. If the worker location contains a physical address, mousing over the worker location will display the address. One important benefit with the ability to specify a worker location in an offer is in the case of multi-location requisitions. Worker Location Field in Offer Form System administrators can configure the Worker Location field to appear in requisitions, offers, correspondence, requisitions lists, and candidates lists just like any other fields. 22

23 TIPS AND CONSIDERATIONS When a candidate is hired, the worker location included in the offer can be exported to the HRMS system for a New Hire record to be created. Specific locations can be included in new hire s offer within a multi-hire requisition. Since the worker location is closely related to the primary location (OLF), system administrators should position both fields close to each other so that users more easily understands the relation and why, potentially, the worker location became populated right after a primary location was selected. KEY RESOURCES For more information on configuring fields, review the following topic in the Oracle Taleo Enterprise Recruiting Configuration Guide: Fields HRMS WORKER INFORMATION INTEGRATION The following HRMS worker-related fields can be imported in Recruiting for use in requisitions, requisition templates, offers, correspondence, requisition lists and candidate lists: Worker Business Unit Worker Grade Worker Job Worker Legal Employer Once values are imported, they are available to be viewed in Taleo Recruiting Administration, under General Configuration. When a recruiter creates a requisition, the selection of worker-related values is performed via a selector. The selector provides quick filters to quickly filter the list down to relevant information. When mousing over a selected value on the requisition, a pop-up window containing details such as name and code is displayed. When creating an offer, the recruiter can decide to specify a worker-related field whether or not it was originally identified in the requisition. Also, if a worker-related field was specified in the requisition, it is possible to specify a different value in the offer. A different worker-related field can be selected for each offer within a same requisition. System administrators can configure worker-related fields to appear in requisitions, requisition templates, offers, correspondence, requisition lists, and candidate lists just like any other fields. 23

24 TIPS AND CONSIDERATIONS If worker-related fields are used, they should be positioned together as a group on the requisition and the offer. When a candidate is hired, the worker-related information included in the offer or requisition can be exported to the HRMS system as part of the New Hire export. KEY RESOURCES For more information on configuring fields, review the following topic in the Oracle Taleo Enterprise Recruiting Configuration Guide: Fields ADDITIONAL WORKER CORRESPONDENCE VARIABLES The following new variables are available to system administrators when they create message templates: {Offer.Position} {Offer.WorkerLocation} {Requisition.WorkerLocation} {Offer.WorkerBusinessUnit} {Offer.WorkerGrade} {Offer.WorkerJob} {Offer.WorkerLegalEmployer} {Requisition.WorkerBusinessUnit} {Requisition.WorkerGrade} {Requisition.WorkerJob} {Requisition.WorkerLegalEmployer} There are no steps necessary to enable this feature. KEY RESOURCES For more information about correspondence variables, review the following topic in the Oracle Taleo Enterprise Recruiting Configuration Guide: Adding a Variable in a Message Template 24

25 EVALUATION MANAGEMENT ENHANCED INTEGRATION WITH MICROSOFT EXCHANGE SERVER 2010 SP3 A broader set of Microsoft Exchange integrations is supported to view free/busy calendars of interview team members. In prior releases, the Evaluation Management Interview Scheduling feature was supporting Microsoft Exchange 2007 SP1, SP2 and Microsoft Exchange 2010 SP1, SP2. In release 15B, Microsoft Exchange 2010 SP3 is now supported. Microsoft Exchange 2010 SP3 will first be rolled out in controlled availability and eventually be made available to a broader audience. Prerequisite: You must have the Manage Microsoft Exchange and Active Directory permission. To set up the integration for Microsoft Exchange: 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 a domain name for the integration. You can get this information from your IT department. 7. Set a status, either Active or Inactive. 8. Select a version for the Exchange Server used for the integration. Supported versions are: Exchange Server 2007 SP1, SP2 and Exchange Server 2010 SP1, SP2, SP3. 9. Enter the Exchange Web Services URL. You can get this information from your IT department. The URL must start with " 10. Enter a user name and a password for the read-only user account configured to access Exchange. Your IT department should create the necessary read-only user account. Note that in Evaluation Management, passwords are masked. 11. Click Save. TIPS AND CONSIDERATIONS Microsoft Exchange 2010 SP3 will first be rolled out in controlled availability and eventually be made available to a broader audience. 25

26 SECURE LDAP AND ACTIVE DIRECTORY CONNECTIONS HTTPS and LDAPS protocols are supported to establish a secure connection. In prior releases, the Evaluation Management Interview Scheduling feature was using an unsecured HTTP connection and was requiring customers to use VPN. In release 15B, we are enabling a secure connection to the company LDAP server and Active Directory server. These servers are used to pull information on interview team members to be scheduled for interviews as well as information on their free/busy schedule. Customers can now securely connect to the Interview Scheduling feature with their Exchange and Active Directory environments and they can connect without VPN. This enhancement will first be rolled out in controlled availability and eventually be made available to a broader audience. Prerequisite: You must have the Manage Microsoft Exchange and Active Directory permission. To set up the integration for 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 a domain name for the integration. You can get this information from your IT department. 7. Set a status, either Active or Inactive. 8. Select an authentication method. Options available are: Simple and None. 9. Enter the Active Directory URL. You can get this information from your IT department. The URL must start with "ldap://". 10. If an https secure connection is not used (e.g. a secure URL is not used in the Active Directory URL), a warning message is displayed to let you know that the connection is not secured. 11. Enter a user name and a password for the read-only user account configured to access Active Directory. Your IT department should create the necessary read-only user account. Note that in Evaluation Management, passwords are masked. 12. Click Save. TIPS AND CONSIDERATIONS This enhancement will first be rolled out in controlled availability and eventually be made available to a broader audience. 26

27 RECRUITING EMBEDDED REPORTING SCHEDULING REPORTS Report users can schedule reports to be run at a set schedule. After a report has run and its status is Ready, you can create a schedule to run the report at a specific frequency. A new Create action in the My Reports window is available. A gray clock icon next to the report name indicates the reports that are scheduled to run. Create Action in the My Reports Window When scheduling a report, you define the following properties: Name: Name of the scheduled report. Description: Description of the scheduled report. Notification: A notification can be sent once the scheduled report is generated. Recurrence: The frequency at which the report will be run. Options are: o Hourly: The report is run every hour on the hour. o Daily: You can choose the days and time when the report will run. o Monthly: You can choose the day of the month and time when the report will run. You also have the option to choose the last day of the month. Only one day can be selected for a monthly execution. Start Time: Time when the report will start running. Available only for Daily and Monthly reports. You must specify a time zone. By default, the time zone set for the zone is used (Configuration > General Configuration > Settings > Time Zone). Expiration Date: Available only when a scheduled report is being edited. By default, the expiration date is set to three months from the creation date. Status: A scheduled job can be active or inactive. 27

28 You can view the list of reports that have been scheduled to run in the Scheduled Report List. In the Status column, the green icon indicates that the scheduled report is active while the red icon indicates that the scheduled report is inactive. When a scheduled report is expired, a gray clock icon is displayed next to the report name. When a scheduled report is set to expire in the next 14 days, a red clock icon is displayed. Scheduled Report List In the Scheduled Report List, you can perform the following actions: Edit a scheduled report. Duplicate a scheduled report. Delete a scheduled report. Activate a scheduled report (note that a report inactivated by the system administrator cannot be activated). Deactivate a scheduled report. Renew a scheduled report (only available if the scheduled job is expired or will expire in the next two weeks). There are no steps necessary to enable this feature. KEY RESOURCES For more information about scheduled report notifications, refer to the following topic in this What s New document: Report Notifications REPORT NOTIFICATIONS Report users can receive notifications upon the generation of a report. Notifications are sent for scheduled and adhoc reports. When a report is set to run or is scheduled to be run, you can specify using the Send Notification option that a notification will be sent for that report and you can choose who will receive the notification. If you do not select a recipient, the notification will only be sent to you. You can specify external recipients 28

29 (users who do not have access to Recruiting) by entering their addresses separated by a semicolon. A notification is sent to recipients when the report runs successfully. If the size of the report file is smaller than or equal to the allowed attached file size, you and the recipients will receive the notification with the report attached. If the size of the report file is greater than 10 Mb, you and the recipients will receive the notification with a link to the report. If the report generation fails, you will receive a notification with an error message. External recipients (users with no access to Recruiting) will not be able to act on notifications because the link will not grant them access to Recruiting. There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS The setting Attached File Maximum Size is used to determine the maximum size of the report file. Notification templates are not provided by the system. Notification templates must be created and configured by the Reporting system administrator using the Message Templates feature in Recruiting Administration. Templates can be created to cover the following triggering events: Notification for completed reports Notification for completed reports with attachments Notification for completed reports without attachments or links Notification for reports not created due to errors Notification for scheduled report near expiration MONITORING SCHEDULED REPORTS System administrators can monitor reports that were scheduled to run to see if the reports have been executed or are still in the process queue and to make modifications to scheduled reports. The Scheduled Reports Monitoring feature available under Recruiting Administration > Embedded Reporting allows you to see all scheduled reports. You can search for a particular scheduled report using these criteria: 29

30 Job Name: name of the job running the scheduled report. Job Status: the job status can either be active or inactive. Owner: user who scheduled the report. Execution Status: possible values are Error, In Progress, Interrupted, Ready. Executed After: reports executed on or after a certain date. You can change the priority of a scheduled job by selecting Low, Medium or High on the Priority menu. You can deactivate existing jobs to stop any request that is currently executing and to prevent any further execution (note that a report inactivated by the system administrator cannot be activated). You can also delete existing jobs if you wish to remove the job from the system. Note that when a job is deleted, the history of the job is also deleted. You can consult the history of executed jobs and assign a higher priority to some jobs. There are no steps necessary to enable this feature. MONITORING REPORT ACTIVITIES System administrators can monitor report activities to get information when reports are run and to get detailed error information when reports fail. In Recruiting, under Reports > Generated Reports > My Reports, the report user can click the Error link next to a report to obtain the Error ID. The user then provides the Error ID to the system administrator or Oracle Support so that they can obtain additional information about the failure. In Recruiting Administration, under Embedded Reporting > Activity Monitoring, the system administrator or Oracle Support can enter the Error ID provided by the report user and view details about the report that failed. There are no steps necessary to enable this feature. SEARCHING FOR REPORTS Report users can search for reports using the report name. In Recruiting, under Reports > Generated Reports > Report List, a search tool is available. You can search for reports using the report name. The search is not case sensitive and no wild card is needed. There are no steps necessary to enable this feature. 30

31 EXPORTING REPORTS Report developers can export reports for future reference. In Recruiting Administration, under Embedded Reporting > Export Reports and Data Models, you can choose report definitions. The data model used in the report definition is automatically selected for the export. You can also choose individual data models. After clicking the Export button, an export.xdrz file is created and you can either open it or save it for future reference. There are no steps necessary to enable this feature. 31

32 CAREER SECTION PERPETUAL DISPLAY OF PARTNER IMPORT SERVICES Customers can configure their career sections to always display partner import services (i.e. even if there is candidate information already in the system). Profile Upload Section Displaying Icon for a Partner Import Service Prior to 15B, when candidates started a job submission flow or candidate profile flow and there was already candidate data (even a single value) in both the Education and Work Experience sections, the entire Resume Upload block including partner import services was hidden from view. Starting in 15B, customers can enable a setting to display partner import services such as LinkedIn and Indeed even if there is Education and Work Experience information on file in the customers zone. Whenever candidates choose to import data from one of these partners (and they can do so as often as they wish), any new structured data will be added to the system while, in the case of Indeed, any existing structured data will be updated accordingly. The substantial usefulness of this feature resides in the fact that candidates typically keep their profile information up-to-date on sites such as LinkedIn or Indeed, rather than updating their information on each customer s zone. 32

33 To display partner import services even if there is candidate information already in the system: 1. Click Configuration. 2. In the Career Section section, click Settings. 3. Find the Always Display Profile Import Services setting and click it. 4. Click Edit. 5. Click Yes. 6. Click Save. TIPS AND CONSIDERATIONS If upload a resume or text-based parsing sections are included in flows, those sections continue to be hidden from view if there is already Education and Work Experience information on file for the job submission. KEY RESOURCES For more information on profile import services, review the following topic in the Oracle Taleo Enterprise Career Section Configuration Guide: Candidate File Import LOGIN INFORMATION LAYOUT CHANGE Login information on the My Account Options page is organized into three separate sections: User Name, Password and (if enabled in the career section) Security Questions. Each section includes an Edit link that displays an edit page specific to that section. New Layout on My Account Options Page 33

34 This change is a usability benefit for all users, with notable wins for visually-impaired candidates using a screen reader. When a candidate clicks one of the Edit links, only the information that is relevant to the section is displayed. For example, clicking the Edit link next to Password displays the following section. New Password Page Prior to 15B, when candidates clicked the My Account Options link, the following section was displayed. Login Information Section Prior to 15B There was no indication that the section might include security questions that could be edited. In addition, if visually-impaired candidates using a screen reader clicked the Edit link, the candidates had difficulty interpreting all the information in the section. 34

35 15B My Account Editing Page There are no steps necessary to enable this feature. RESUME BLOCK LAYOUT CHANGE If a job-specific application flow or candidate profile flow contains the Resume Upload block, when candidates proceed to the resume page, the field for comments is displayed immediately before the Attach button. This is a usability benefit for all users. Visually-impaired candidates who use a screen reader are now aware there is a field for comments regarding the file they are about to upload before they advance to the next step in a flow. 35

36 Comments about the file Displayed Before Attach Icon Prior to 15A.5 and 15B, the Attach icon was displayed immediately before the field for comments. This order was not ideal because visually-impaired users using a screen reader might have attached a file without realizing that further down the page there was a field for entering comments. There are no steps necessary to enable this feature. FACEBOOK FEATURE NO LONGER A CAREER SECTION PROPERTY The "Enable Facebook feature" was removed from the career section Properties section. This feature is no longer supported. There are no steps necessary to enable this feature. FACETED SEARCH AUTO-SUGGEST - TWO CHARACTERS If candidates type two or more characters in the Organization, Location or Job Field fields in the search bar on the Faceted search page, the system suggests values that correspond to the typed characters. Similarly, if candidates click See all locations or See all job fields in the left pane of the Faceted search page, and type two or more characters, the system suggests corresponding values. The candidates can make a selection from the list of displayed values or they can type additional characters (and the list of suggested terms is modified accordingly). 36

37 While all candidates (whichever language they use) benefit from this change, it is important to note that in Asian languages, two characters often offer sufficient context on which to base a list of suggested terms. In addition, some important words in Asian languages have only two characters. If the system required a minimum of three characters (which was the case prior to 15B), the two-letter words would necessarily be excluded from suggested terms. There are no steps necessary to enable this feature. KEY RESOURCES For more information, review the following topic in the Oracle Taleo Enterprise Career Section Configuration Guide: Faceted Search FACETS REFLECT FACETED SEARCH OLF SELECTIONS Facets on the Faceted search page are consistent with the OLF selections made on the Faceted search configuration page. Prior to 15A.8 and 15B, as candidates entered values in OLF fields on the Faceted search page, the suggested terms that appeared were determined by the administrator s OLF selections both the levels and the number of levels for the Faceted search page. If candidates clicked the See all locations or See all job fields links, the Filter records field also displayed suggested terms consistent with the Faceted search configuration page OLF selections. However, the OLF selections on the configuration page had no effect on the number of levels displayed in the facets (panel) of the Faceted search page. Starting in 15A.8 and 15B, the number of levels displayed in the facets panel of the Faceted search page is consistent with the number of levels the administrator selects on the Faceted search configuration page. There are no steps necessary to enable this enhancement. TIPS AND CONSIDERATIONS The levels and the number of levels displayed in the facets panel is consistent with the levels displayed in suggested term lists. 37

38 KEY RESOURCES For more information, review the following topic in the Oracle Taleo Enterprise Career Section Configuration Guide: Faceted Search NEW USER REGISTRATION USING THIRD-PARTY CREDENTIALS Visitors to a career section can register (create) a Career Section account (i.e. candidate profile) using third-party credentials such as Yahoo and Google. Since 15A, candidates have been able to log into career sections using some third-party credentials. Starting in 15B, visitors to career sections who click the New User button will be able to create a candidate profile in the same manner, using third-party credentials such as Yahoo and Google, from the New User Registration page. It is an Oracle best practice to activate this feature, especially in external career sections because it is a great time-saver for candidates. If the third-party credentials are not linked to a candidate profile in the Taleo customer's career sections, the system verifies if the address from the third-party application is an address or user name in a candidate profile in the customer's career sections. If no duplicate address is found, the system creates a candidate profile in the career section automatically, using the address (from the third-party login process) as the user name and generating a password that conforms to the security policies configured for the career section. If a security question was enabled for candidate profiles, the candidate is asked to provide this information. If a duplicate address is found in a candidate profile, the system displays the login page from which candidates can log into their account in the Career Section. Visitors select one of two options: If candidates select "Yes, I have a Candidate Profile and I would like to associate it to my single sign-on", the third-party account credentials are linked to the candidate profile in the career section. This option enables candidates to later sign into the career section directly (provided the candidates selected "Keep me logged in" or similar setting in the third-party product) by simply clicking the third-party icon on the career section. Candidates can choose to create a candidate profile. Thereafter, the third-party account credentials are linked to the new candidate profile in the career section and the candidates can sign into the career section directly (provided the candidates selected "Keep me logged in" or similar setting in the third-party product) by simply clicking the third-party icon on the career section. IMPORTANT: For this solution to work, the Career Section must not be configured for single sign-on (SSO), which usually only affects Internal Career Sections. If SSO is turned on for a Career Section, then the property Display the OpenID Option must be disabled or the visitor will receive error messages. 38

39 To enable candidates to create their candidate profile using third-party credentials: 1. Click Configuration. 2. In the Career Section section, click Administration. 3. In the Global Security section, click External Career Sections. 4. Click Show next to Default Values. 5. Click Edit next to Sign In. 6. Next to Display the OpenID option, select Yes. 7. Click Save. To enable OpenID Authentication for a specific third-party partner: 1. Click Configuration. 2. In the Career Section section, click Administration. 3. In the Global Security section, click OpenID Authenticaton Configuration. 4. Click the provider s code and configure the properties and other values. OpenID Authentication Page Showing Two Partners TIPS AND CONSIDERATIONS Display the OpenID Option can be set at the global level and at the career section level for external and internal career sections. If the Allow new users to register in the system Career Section Sign-on property is set to No, then it is recommended that the Display the OpenID Option for the career section also be disabled. This feature is particularly relevant for customers who use Social Sourcing. Candidates who apply for a job through Social Sourcing and who do not exist yet in Taleo Enterprise are directed (via a deep link) to the New User Registration page directly where they can use the Google and Yahoo authentication. 39

40 SMARTORG MASKING NEWLY CREATED USER PASSWORD When system administrators generate a user password in SmartOrg Administration, the newly created password displayed on screen is masked with asterisks to protect the information from potential shoulder surfing attacks. System administrators can momentarily select the Show password check box to view the password when it is considered safe to do so. New Password Generated in SmartOrg Administration There are no steps necessary to enable this feature. 40

41 SOURCING In 15B, Sourcing focuses its enhancements around globalization and multi-language capabilities, improved candidate experience and self service capabilities. LOCALE NAME HARMONIZATION WITH RECRUITING LANGUAGES Prior to 15B, Sourcing referenced languages as country names labeled as locales. Release 15B unifies the language naming to reduce confusion and provide better parity with Recruiting. Sourcing now uses the proper language name to refer to a language, which aligns with how Recruiting references languages. Still in 15B, Sourcing configuration continues to refer to these new languages as locales whereas Recruiting refers to them as languages. Each Sourcing locale has a corresponding Recruiting language. Sourcing will display the locale names in the local language, e.g. English, Deutsch, Espanol, etc. Locales from Sourcing which do not have a pairing in Recruiting have been deprecated. These deprecated locales are: Canada Mexico Australia Singapore Spain (English) Latin America (Argentina) There are additional locales that do have a Recruiting pairing, however, they do not have translated content nor are contained within the Placefinder search library. These deprecated locales are: Denmark Malaysia The locale preference resides in the User Info in Settings (Admin > Settings > User Info > Language/Locale) and displays the new names and removes the deprecated locales. 41

42 Language/Locale Selector The updated locales are also presented in a new language toggle (documented in detail later in this document) with the locale choices translated into the target languages. New Language Selector on Home Page 42

43 The new language names for locales are also available in Site Builder. Activated locales display at the top of the Language dropdown menu in Site Builder and are in bold lettering and marked with an asterisk. Site Builder Language Dropdown Menu There are no steps necessary to enable this feature. 43

44 TIPS AND CONSIDERATIONS Ensure that no locales are activated in Sourcing which are not activated in Recruiting. KEY RESOURCES For more information about these enhancements, refer to the following topics in this What s New document: Locale Harmonization Migration Language Toggle on All Pages and Refactored Navigation LOCALE HARMONIZATION MIGRATION This feature pairs with the Locale Name Harmonization with Recruiting Languages feature and its purpose is to provide a smooth cutover process for both the configuration and user preferences to the deprecation of locales. This feature describes the process and logic that will be invoked when managing customers that are using deprecated locales. It is highly recommended that customers using a to-be-deprecated locale be identified early and then change their default locale to a supported locale prior to upgrade. Again, the list of locales to be deprecated in 15B is: Canada Mexico Australia Singapore Spain (English) Latin America (Argentina) Denmark Malaysia Users who have the above locales set as their preference will automatically have their locale preference changed to the Default Locale at first login after upgrading to 15B. If the Default Locale is configured to one of the to-be-deprecated locales at the time of upgrade, it will be changed to English-US. If English-US is not an active locale, it will automatically be added as an active locale in addition to being set as the Default Locale. As this behavior is automatic, customers will not be informed of the change at the time of login. The Default Locale setting is located on the Company settings of configuration (Admin > Configuration > Company > Application). 44

45 Default Locale Setting in Company Configuration There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS It is recommended that customers disable all to-be-deprecated locales prior to upgrading to 15B to prevent candidates from setting a deprecated locale as their preference. KEY RESOURCES For more information about these enhancements, refer to the following topics in this What s New document: Locale Name Harmonization with Recruiting Languages LANGUAGE TOGGLE ON ALL PAGES AND REFACTORED NAVIGATION There is a new language toggle available on all pages of Sourcing that allows all users to clearly see the languages available to them and to change that language in their user interface. This language toggle only displays if there are two or more languages, or locales, enabled in the system. If there is only a single locale, there are not different locale choices, so the language toggle does not display in the UI. 45

46 The three social media icons (Facebook, LinkedIn and Twitter) and session management components (Sign Up and Sign In buttons) have been moved from the main menu and onto the same navigation bar as the language toggle. Language Toggle and Refactored Navigation Wherever there was previously a link into the Settings area, on the Jobs page for example, in 15B this has been replaced by a Settings button. Settings Button On the Job Details page, the locales enabled on the language toggle are limited to the languages that are enabled on that specific requisition. If there is a delta between the number of locales enabled in Sourcing and the number of languages enabled on this requisition in Recruiting, a message indicating this displays next to the language toggle. There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS Advanced branding work that customers have configured may be impacted by the introduction of the language toggle and refactored navigation. Custom branding developed prior to 15A may not upgrade cleanly. If this is the case, branding experts should be engaged to rework the HTML and CSS in Site Builder. Customers should first assess the impact of their custom branding on the layout changes in staging, and make the necessary adjustments and then apply them to production in order to ensure the branding renders the navigation changes optimally. 46

47 Customers should audit the locales which are activated. It is recommended to align the list of active locales to only those languages which are also active in Recruiting. It is recommended and considered best practice for customers to audit all content in locales beyond the default locale as all locales will be much easier to access with the new language toggle readily available. BROWSER LANGUAGE DETERMINES SESSION LANGUAGE Sourcing now automatically presents the Sourcing site in the users expected language using their browser language. This allows users to experience Sourcing in their expected language without having to change the language with the newly introduced language toggle. With 15B, Sourcing loads into the user s browser and is able to identify the language configured for that browser. If that language is an active locale in Sourcing then the system is able to show Sourcing in that language. If the browser s language is not an active locale in Sourcing, the system will then show Sourcing in its configured Default Locale. If there is no Default Locale configured, Sourcing is presented in English-US. There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS Once a user authenticates, their personal locale preference in their settings supersedes their browser language settings. This behavior is as it was in 15A; there is no change here. However, now if for whatever reason users want to change their Sourcing session language it can be easily done by using the new language toggle. It is recommended to audit which locales are activated in the zone. Some customers may have more locales enabled than needed and the browser default language may reveal Sourcing in locales not expected. For this reason, content across all languages should be reviewed for completeness. MULTILINGUAL CUSTOM CONTENT BLOCKS In 15A, the custom content blocks used in Site Builder were unilingual, meaning that no matter the locale/language the user viewed the site in, the content in the custom blocks remained in whatever language in which the block was created. This caused language cross-pollination if the site was viewed in any language other than the one which was used to create the content blocks; the content block would be in one language while the rest of the site in another. Now, with 15B, custom content blocks are multilingual enabling Administrators to configure the content blocks in Site Builder with content that can be translated to each locale and can be unique to each locale. When site users toggle their language preference, the content in the custom content blocks will display in that language, provided the blocks have been configured in the locale/language selected. 47

48 For new custom content blocks that customers add after migrating to 15B, it is mandatory for content to be entered into the Default Locale. If for whatever reason content is not entered into an active locale, these locales with missing content will borrow the content from the Default Locale. This ensures that users will see actual content, although perhaps not in the language of their choice, instead of the placeholder Lorem Ipsum text and the placeholder image delivered with the blocks. All of the system locales, including inactive ones, are available to select in Site Builder to allow Administrators to immediately configure the multilingual content blocks. Content blocks in inactive locales can be pre-configured to make efforts more scalable. Administrators can freely create content in inactive locales without risk of exposing incomplete or inaccurate content as that content remains internal until that locale is activated. There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS At upgrade all existing unilingual content is propagated to all locales and ready to be configured for those locales. This allows customers using Site Builder in a multilingual mode a smooth migration as they ll only need to translate the content, not create it. Configuration and completeness of content blocks should be carefully audited given the new language toggle and browser language detection feature, which makes non-default locales more easily accessible. GEOLOCATION CUSTOMIZATION BACKUP AND RESTORE When a full refresh of all jobs via the Job Connector is performed, all new locations are imported and previously entered Geolocation customizations are removed. With 15B, this behavior remains, however, now Administrators have the option to backup and save their custom Geolocation latitude and longitude values for job locations to eliminate the need to reconfigure customizations. This backup feature creates a single cloud-based file for geo-coded locations which can be used to easily restore the customizations. Only a single file is created and saved in the cloud and previous backups are not available. For this reason, Administrators have the option to export each file into an Excel format that can be saved for later reference. After entering geolocation customizations, Administrators click the Backup Job Geolocation Data button. Their customizations are saved in the cloud until another backup is performed. When another backup is performed this file gets overwritten, so if Administrators want to keep each of their backups, they must export the cloud files into Excel. This is done by clicking Download backup file. Once a job refresh is run, the customizations are removed, and can then be restored by clicking the Restore Job Geolocation Data button. 48

49 Geolocation Editor Job Locations Geolocation Editor Company Offices IMPORTANT: Remember that only one cloud-based file is saved at a time. Clicking the Backup Job Geolocation Data button overwrites the existing backup file. To preserve this data, the file must be exported to Excel. Although this feature resides in Sourcing Configuration, it is automatically available with upgrade. There are no steps necessary to enable this feature. It is found in Configuration > Geolocation > Geolocation Editor > Click here to view the editor. 49

50 TIPS AND CONSIDERATIONS It is recommended that a backup is performed after every Geolocation change. It may take several minutes for the changes to apply once the Restore Job Geolocation Data button is clicked. If you are unsure whether you want to restore a previously saved backup and overwrite your geolocations, then it is recommended you export the existing backup, inspect it, and then determine that you actually want to restore your geolocations from that backup. If you restore your geolocations from a previous backup, there is no undo feature. SORT AND FILTER LOCATIONS IN GEOLOCATION EDITOR To facilitate the editing work done by Administrators, locations are now easy to find using new filters and sorting capabilities in the Geolocation Editor. Administrators can now filter and search job locations and company offices as well as sort the locations in either ascending or descending order. The filter criterion available differs depending on whether you are searching for job locations or company offices. Geolocation Editor Filters and Sort Job Locations 50

51 Geolocation Editor Filters and Sort Company Offices Although this feature resides in Sourcing Configuration, it is automatically available with upgrade. There are no steps necessary to enable this feature. It is found in Configuration > Geolocation > Geolocation Editor > Click here to view the editor. LOCATION SEARCH FALLBACK TO KEYWORD SEARCH In 15B, if users enter a location search that is not found in the Placefinder directory, they are presented with the option to run a keyword search using their location criterion. This feature enables the user to search for jobs at locations outside the usual geosearch library by converting the invalid location into a keyword search that may yield jobs. 51

52 Keyword Search from Location If users select Yes, the location entered is copied to the keyword field and a keyword search is performed. All results, if any, containing that keyword are displayed. There are no steps necessary to enable this feature. EDIT FONT STYLE AND SIZE IN CONTENT BLOCKS To simplify and enrich custom content block editing, two new tools, Font and Size, have been added to the Rich Text Format Editor for use directly within Site Builder and Campaigns. Rich Text Format Editor Font and Size There are no steps necessary to enable this feature. 52

53 UPLOAD CUSTOM FONTS Customers can now align the Sourcing interface even more closely with their corporate identity with the ability to upload custom fonts to be used in Site Builder and in campaigns. The fonts must be uploaded using CKFinder. The custom font upload formats supported are: eot woff ttf svg The custom fonts will not be available for use in the new Font dropdown menu in the RTF editor, but can be consumed through the use of Advanced CSS. Administrators can upload custom fonts in the same way they upload images in Site Builder. Once these fonts are uploaded, they are available for use. These fonts can only be referenced through branding, and are not surfaced through the standard font selector in the content block editor. 1. In Site Builder, temporarily insert a content block using a template that has an image. 2. Click the image button to select an image to upload. 3. Instead of uploading an image, upload a font. 4. You may now delete the temporarily inserted content block. 5. Add advanced CSS to configure the custom font family. a. The following code should be used as a guide and added to the Advanced CSS panel in Site Builder (Site Builder > Edit Site > [Branding] > Advanced { font-family: 'FONT NAME HERE'; (example, "Arial", "MyFont", "Helvetica") src: url('font_url.eot'); src: url('font_url.eot?#iefix') format('embedded-opentype'), url('font_url.woff') format('woff'), url('font_url.ttf') format('truetype'), url('font_url.svg#font_name_here') format('svg'); 6. For the path to the uploaded fonts, ensure the path set in the Advanced CSS matches the path in the CKFinder window. This can be confirmed by right-clicking on an existing image file (in the same folder) in CKFinder and selecting View, then right-clicking on the image and selecting Open in New Tab. 7. Configure custom font as Body Text Normal. Save the Advanced CSS and publish the site. 8. Navigate to Edit Site Branding for your site and add your font name to the Fonts section under Body Text Normal. 53

54 TIPS AND CONSIDERATIONS Career Section, used for the application process, does not have this ability to upload custom fonts. EXTEND USE OF CUSTOMER NAME DISPLAY To reinforce customer ownership of the system content, 15B Sourcing replaces two Oracle Taleo labels with tokens so that the name of the customer displays instead. The two dictionary tags impacted are apply.helptext.privacy and apply.helptext.upload_resume.privacy. Currently, the statement that will use tokens in 15B reads: Oracle Taleo collects the information you provide for the sole purpose of considering your interest in employment by Oracle Taleo. Oracle Taleo to be Replaced by Customer Name After upgrade to 15B, Oracle Taleo will be replaced by the customer name using tokens as follows: [(Customer Name) ##D.global.nameclient##] collects the information you provide for the sole purpose of considering your interest in employment by [(Customer Name) ##D.global.nameclient##]. There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS It is important for customers to understand that their name will now be inserted into this statement. 54

55 APPLY BUTTON FOR RECRUITERS AND ADMINISTRATORS Prior to 15B, Recruiters and Administrators did not have the capability to apply to jobs; their actions were limited to job promotion activities. To increase the pool of candidates, with upgrade to 15B, Recruiters and Administrators (users of privilege class 3 and higher) can apply to jobs using the Apply for Job button. Job Details Page New Apply for Job Button for Administrators and Recruiters There are no steps necessary to enable this feature. TIPS AND CONSIDERATIONS Customers may want to anticipate and address any change management for those people who will now gain this capability. Some customers may have implemented workaround solutions previously, which could now be remediated after upgrade. 55

56 ROLE-SPECIFIC LINKS TO MY PROFILE AND MY SUBMISSIONS The links Go to Profile and My Submissions will now target career sections configured for their Sourcing privilege class, or role, and users will be directed to the appropriate profiles and submissions (external and internal) based upon those privileges. To accomplish this, two settings have been renamed and two new settings are being introduced in the Site Builder TEE Account URLs settings for 15B. The settings that allow candidates to go through the targeted flows are: Submit Profile URL Guests My Submissions URL Guests Submit Profile URL Employees My Submissions URL - Employees Configuration Site Builder Settings There are no steps necessary to enable this feature. At upgrade, the value from the single setting from 15A is populated into both settings in 15B. TIPS AND CONSIDERATIONS For customers who tether multiple career sections with different application flows to a single Sourcing site, the following is recommended: 56

57 For the career sections which are targeted by these new Site Builder settings, it is best practice for customers to configure the Always force this Career Section s job-specific application flow setting in Career Section to No. Having this setting configured to No, ensures that candidates who edit their job submissions using the deeplink in Sourcing will be directed to the correct application flow; the flow in which the submission was originally created. A value of No here translates to saying, Force the application flow on which this submission was originally created. This configuration mitigates any perceived need for multiple links to multiple career sections for accessing the My Submissions page. Career Section Configuration > Administration > Career Sections > Select a career section > Properties (not Application Flow Properties) > Scroll down to Application Flow Properties Career Section Configuration Career Section Properties CAREER SECTION JOB DESCRIPTION URL S TARGET SPECIFIC SITES With 15B, candidates that come to Sourcing from job boards can experience an end-to-end targeted branded experience between Sourcing and Career Section. Prior to 15B, candidates could only be directed to the default Sourcing site from Career Section URL s as opposed to a uniquely branded site in Sourcing that paralleled the Career Section. Now, candidates accessing a Career Section job URL which targets a Job Description page can be redirected to the Job Details page for that same job in Sourcing, on a targeted Sourcing site. The Job Description Redirect URL setting on each Career Section is to be populated with the URL for the appropriate Sourcing site. The site URL fragment you need to include in the URL which is entered in this Career Section setting is found in the Sourcing configuration. To access this URL fragment: In Sourcing: 1. Click Configuration. 2. Click Site Builder. 57

58 3. Click Edit Site Settings (Gear icon) for the site you wish to link. 4. Under General, you will see the Site URL setting. That value will be included in the URL string. In Career Section: 1. Click Configuration. 2. In the Career Section, click Administration. 3. In the Career Sections section, Click Career Sections. 4. Click on the name of the Career Section you wish to modify. (Note that it must be inactive to display an edit option). 5. In the Properties section, click Edit. 6. Scroll down to the URL section and enter the appropriate URL in the Job Description Redirect URL field. To direct candidates to a targeted Sourcing site, enter the URL obtained from Sourcing, i.e., URL/taleo/jobdetails. To target the Sourcing default site, use URL format: NOTE: You will want to switch out customer and referrals as needed to target the correct zone. NOTE: This ability to direct users to the default site using the URL format already exists in 15A. 7. Save. TIPS AND CONSIDERATIONS On each Career Section which is tethered to a Sourcing site, be sure to target the correct Sourcing site you wish job seekers who come from Career Section URL s to be directed to. Ensure that the site you are targeting is also tethered to that site for the Job Connector API. SELF-SERVICE FACET MANAGEMENT FOR STANDARD FACETS Sourcing 15B eliminates the need to enter a Service Request for the configuration of standard facets by transferring this capability to customers and partners. Employee/Referrer, Job and Talent Community facets are all now managed by a new Facet setting in Sourcing Configuration. The facets in the configuration are color-coded; user-created facets are in blue, default facets are green and inactive are red. Facets are easily managed using the gear icon, up and down arrows or by dragging and dropping them into place. 58

59 Configuration Page - Facets Although this feature resides in Sourcing Configuration, it is automatically available with upgrade. There are no steps necessary to enable this feature. It is found in Configuration > Facets. DATE OVERRIDE ON MANUAL JOB SYNCHRONIZATION If it is discovered that a job that resides in Recruiting did not come over into Sourcing through the scheduled Job Synchronization, a new Manual Job Synchronization feature enables the Administrator to correct this error. The scheduled Job Connector requests requisitions with a last modification time and date since the last time it ran. With 15B, if there are jobs, which for some anomaly did not synchronize into Sourcing, the Manual Job Synchronization can be invoked to retrieve the missing jobs. Administrators enter a date into the Manual Job Synchronization and the synchronizer will request all jobs that are currently posted on the tethered career sections with a last modification date on or after the date selected. 59