Taleo 13B Latest Features

Up & Running Tutorials
September 2013
SaaS Customer Lifecycle Management
Oracle Confidential. Copyright 2013, Oracle. All rights reserved.
This information is not a commitment to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
13B Up & Running Tutorials

OU Feature Video Demos here Knowledge Exchange
New topic category Enterprise Release Info
Product Features
Onboarding & Transitions - Launching a Process for Candidate without Email Addresses Evaluation Management SmartOrg User Picker Enabling Mobile Tap Recruiting Center - Additional Auto-Progression Rules Recruiting Center - Automatic Posting to Mobile Career Section Onboarding and Transitions Synchronizing a Zone from Onboarding to Transitions
Pages 3 - 16 17 - 28 29 - 56 57 - 90 91 - 109 110 - 135
Leaders Jodie Holway Jessica Reilly Ali Moosvi Nicolas Pelletier Nicolas Pelletier Jodie Holway
Video Min
20 10 N/A 30 15 25
13B Up & Running Tutorial, Onboarding &Transitions:
Launching a Process for Candidates without Email Addresses
September 2013 Release 13B

The following is intended for information purposes and may not be incorporated into a contract
Fallback Email Addresses: Overview

Transitions process can be run on anyone, even Candidates who provided no email address Each zone configures what to do when launching Transitions process for candidate with null email:
Admin can provide one fallback email address for everyone If no fallback provided, process wont launch: gives an error
Candidates with an existing email address will receive any correspondence/reminders as usual
Recruiter Perspective
Recruiter Perspective: Error if no Fallback

Actions to launch Transitions:
Start Transitions New Hire Process (anytime in CSW) Start Transitions Pre-Hire Process (anytime in CSW) Extend/Send E-Offer (in RSOffer step, in status Extended)
For candidate whose user account has email address:

Transitions will launch fine.
For candidate whose user has no email address:

If no default: Recruiter will receive an error, process will not launch. With default: Recruiter will be successful, process will launch.
Recruiter Perspective: Error if no Fallback

The action cannot be applied to 1 of the candidates selected. The field Email Address is mandatory. Candidates not processed
Same error visible when launching Advanced E-Offer Same error visible in Taleo Connect tool when launching any process type
Candidate Perspective
Candidate Perspective: with Email Address

Get Transitions-configured communications in inbox:
1. 2. 3. 4. Correspondence tasks Notifications of assigned tasks Reminders of upcoming/overdue tasks Passport-triggered invitations/messages
Also, see some tasks on Career Sections Tasks tab:

1. 2. 3. 4. YES: NO: NO: YES: Correspondence tasks Notifications of assigned tasks Reminders of upcoming/overdue tasks Passport-triggered invitations/messages
Candidate Perspective: without Email Address

If fallback email address is configured, no email can go directly to candidate. Some tasks appear on Career Sections Tasks tab:
1. 2. 3. 4. YES: NO: NO: YES: Correspondence tasks Notifications of assigned tasks Reminders of upcoming/overdue tasks Passport-triggered invitations/messages
If fallback email address is not configured, Transitions process cannot launch at all.
10
My Task List, from Candidate Perspective
11
Administrator Perspective
12
Administrator Perspective: Settings

Configuration > SmartOrg Admin > Transitions > Settings Choose a universal fallback email address if desired By default, no value exists when 13B arrives
13
Administrator: Important Notes

Some companies may NOT want to allow running processes on candidates/new hires without email address
For these zones, leave the fallback setting blank. Error will occur when trying to create user to launch the process.
Some companies have a dead-letter email address or can set up one, for receiving any stray email messages
This could be Do_Not_Reply@company.com They can manage (or ignore) any communications that arrive (There is no validation of the format of this address)
Even if Transitions is configured to send NO messages to candidates, this is still necessary for running any process.
14
Background: SmartOrg vs. Candidate

Transitions process relies upon a User in SmartOrg
Candidate accesses all tasks in Career Section But a SmartOrg user must exist, linked with the Candidate TCC can link a candidate with an Employee in advance If Transitions process creates the user, it wont be Operator nor an Employee: it will be a new type Transitions (new 13B)
To launch a Transitions Process, user needs email

All users in SmartOrg must have an email address If an existing user is linked to candidate, it already has an email If Transitions creates the user, it tries to take Candidates email
Fallback address doesnt get stored in Candidate record; it becomes part of the linked User record
SmartOrg email addresses dont need to be unique
15
Thank You
16
13B Up & Running Tutorial Evaluation Management: SmartOrg User Picker

Jessica Reilly
17
SmartOrg User Picker: Overview

Users will be able to search and select evaluators from a list of SmartOrg users and no longer have to manually input first/last name and email address each time they send out an evaluation Users can still manually input evaluators who are outside of SmartOrg, and they are retained for future use Users can now manage evaluators at the requisition and job submission levels
18
New Permissions to Manage Evaluators

Users will need one or both of the new permissions:
Recruiting > Requisitions > Evaluation questionnaires in requisitions > Add and remove evaluators Recruiting > Candidates > Evaluation questionnaires in candidate submissions > Add and remove evaluators
Users granted those permissions will see the Add and Remove buttons in the Evaluator section on the Questionnaire tab
19
How to Add Evaluators

1. To add evaluators to a requisition or job submission, navigate to the Questionnaires tab and click the Add button in the new Evaluators section
20
How to Add Evaluators (contd)

2. Clicking the Add button opens the evaluator selection modal 3. Use the Internal Evaluators list to search for system (SmartOrg) users 4. Manually enter the first name, last name and email address for evaluators who are outside of the system
21
How to Send Feedback Requests

Evaluators who have been added to the requisition/job submission will now be available for selection when sending out questionnaires
22
Notes on Permissions
23
Permissions and Adding Evaluators

If the user has both permissions or only the requisition level permission, adding an evaluator at the requisition level attaches them to the requisition and all associated job submissions If the user ONLY has the job submission level permission, adding an evaluator at the job submission level attaches them to only that job submission
24
Permissions and Removing Evaluators

If the user has both permissions, the evaluator is removed from the requisition and all job submissions.
Active requests and results remain listed at the job submission level, however the evaluator would need to be added again to send another request.
If the user ONLY has the requisition permission, the evaluator is removed from the requisition.
All existing/previously created job submissions are not affected. However, new job submissions created after the evaluator has been removed will not have that evaluator.
If the user ONLY has the job submission permission, the evaluator is removed from that job submission.
25
Recommendations for Users
26
Important for Users to Note

There is a known API limitation with the Internal User list only returning 100 users. To find a user who is not displayed in the list, make use of the quick filters.
Even after applying filters, the list will only display the first 100 users (if that many were applicable to the filter applied) or less.
There is validation in place that will prevent users from entering existing internal/SmartOrg users in the external user input fields. The user will be directed to find the evaluator in the SmartOrg list.
27
Thank You
28
Up and Running Tap for Taleo on TEE 13B

Oct 2, 2013
Enabling Mobile Tap Overview
TEE 13B provides support for: iPhone and iPad iOS 6.0+ SSO and non SSO English Only
In 13B, administrators have the ability to enable the mobile setting. Customers no longer are required to file a support ticket in order to enable this capability (as in 13A). To enable users to access Taleo (Recruiting Center and Performance Management), administrators can follow a few easy steps: Enable the mobile setting on Tap Create a User Type/modify an existing User Type/duplicate a User Type and enable this User Type for mobile Associate user names with this User Type Distribute address of mobile configuration site to mobile users (e.g. hiring managers):
https://your zone name/mobile
Once the email is received by hiring managers, the hiring managers can quickly get started with Tap by: Navigating to: https://your zone name/mobile and follow the instructions to:
Download and install Tap Configure tap
30
31
1. Navigate to Configuration section of TEE Oracle Confidential. 2. Select Settings under General Configuration section
Copyright 2013, Oracle. All rights reserved.
32
1. Set Refine By drop down to Keyword 2. Type Mobile in the text field and click Refresh 3. Click on Enable Mobile under Settings
33
1. On the Enable Mobile settings page, notice that Value is set to No 2. If the Value is set to No, click Edit 3. If the Value is set to Yes, skip to User Type configuration Oracle Confidential. Copyright 2013, Oracle. All rights reserved.
34
1. Under Properties, check the box labeled Value 2. Click Save 3. The Mobile setting will now be enabled for the zone. Oracle Confidential.
35
1. Navigate back to the to Configuration section of TEE 2. Select Administration under the SmartOrg section
36
1. Select User Type, under the Users section

37
1. Search for a desired User Type that will represent a mobile User Type. This User Type can either be either duplicated (recommended approach) or edited. 2. Once the User Type is located, click Duplicate to duplicate the User Type 38
Oracle Confidential. Copyright 2013, Oracle. All rights reserved. This information is not a commitment to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
1. Enter a new code in the Code field. E.g. Mobile_Enabled_user_Type 2. Enter a new name in the Name field. E.g. Mobile_Enabled_user_Type 3. Click Save, to save the changes Oracle Confidential. Copyright 2013, Oracle. All rights reserved.
39
1. Expand the Mobile sub-section under the Functional Domains section 2. Click Edit under the Mobile sub-section
40
1. Check the Access Mobile property under the Permissions section 2. Click Save
41
1. Navigate back to the SmartOrg Administration page 2. Click User Accounts
42
1. Search for users that should receive the mobile permission (e.g. users who should be able to use Mobile Tap for Taleo) 2. Click the target username
43
1. Click Show on the User Type sub-section 2. Notice that no Mobile Enabled User Type is associated with this user 3. Click Edit under the User Type sub-section Oracle Confidential. Copyright 2013, Oracle. All rights reserved.
44
1. Click Add to add additional User Types to this user

45
1. 2. 3. 4. 5.
Search for the mobile User Type. Set the Refine by drop down to Key Word, and enter in the desired key word Click Refine to search for the Mobile enabled User Type Check the desired User Type Oracle Confidential. Copyright 2013, Oracle. All rights reserved. Click Select
46
1. Click Save to save the newly added User Type

47
1. Notice the newly added Mobile User Type is present under the User Type sub-section for this user 2. This user should now be able to access Tap for Taleo
48
Hiring Manager Perspective
49
1. Navigate to the Tap URL: https:// your zone.com/mobile, on either you iPad or iPhone 2. Tap the first link Download the mobile application, to be redirected to the Apple App Store where you can download the application
50
1. Download the Oracle Tap application for either your iPad or iPhone
51
1. Return to the browser, https://your zone/mobile 2. Tap the second link, Configure the mobile application
52
1. The user will be redirected to the Tap application that was just downloaded and installed on the iPhone or iPad 2. Click Confirm to confirm the configuration 3. Once you tap Confirm, the Tap application will be configured withCopyright the correct URL to access Taleo Oracle Confidential. 2013, Oracle. All rights reserved.
53
1. Enter TEE username into the Username section 2. Enter users TEE password into the Password section 3. Tap Login, to log into Tap for Taleo Oracle Confidential.
54
SSO Support The Oracle Tap for the Taleo Cloud now supports SSO in TEE 13B. Users can now use the Tap client without any additional configuration to login using SSO. SSO support is automated, no additional setup is required. In the case SSO is enabled at your organization, the Tap client opens an embedded browser window and navigates to a login page where you will be able to enter in your credentials. After 55 Oracle Confidential. Copyright 2013, Oracle. All rights reserved. successful login, the embedded browser window is closed automatically by Tap client, and the user will be able to use Tap.
Thank You
56
13B Up & Running Tutorial, Recruiting Center :
Additional Auto-progression rules

57
Overview
Additional possibilities have been added to the Automatic Progression of Candidates functionality, which makes it possible to automatically progress candidates based on certain values being present in their submission.
58
How it works
It is now possible to create auto-progression rules based on the value of specific fields Only fields of specific data types can be used for auto-progression:
Boolean Text Number Single Selection Multiple Selections
59
How it works
These fields can be either Standard fields or userdefined fields All user-defined fields of a supported data type are available to create auto-progression conditions For standard fields, a specific list of fields is supported to create auto-progression conditions
60
How it works Standard Fields available for AutoPersonal progression

Information
Accepts Job Posting Notifications Address (line 1) Address (line 2) Advance Notice Anonymous job submission Application Medium Cellular Number City Cover Letter Currency Education Level Email Address Employee Number Employee Status Fax Number First Name Home Phone Number Internal Candidate Job Level Job Type Last Name Middle Name Minimum Annual Salary Pager Number Place of Residence Preferred Job Preferred Location Preferred Organization Prefix Primary Number Resume Schedule Shift Social Security Number Suffix Travel Website Address Work Phone Number Zip/Postal Code
61
How it works Standard Fields available for AutoWorkprogression Conditions Work Experience Education
Currency Achievements Expected Hourly Pay Rate Current Job Hours per week willing to May we contact the work supervisor? Hours per week, preferred Name During Employment GPA out of Willing to work on Supervisor's Email Graduated from High holidays Address School or GED Willing to work on Supervisor's Name Location weekends Supervisor's Phone Student name while attending the program Supervisor's Title City Education Level (Achieved) GPA
Certifications
Location Number/ID Organization
62
How it works Standard Fields available for AutoReferences Contingent Other progression
Staffing
Email Address Agency Requisition Number Prescreening score
Evaluation Management
All requested evaluations have been completed (which can be true or false) Questionnaire Average Score
First Name Last Name Location Middle Name Organization Phone Number Relationship Title Type
Hourly Rate Paid to the Worker Sales tax must be charged Staffing Agency Hourly Rate Worker ID Worker Type
ACE candidate Background Check Consent eSignature complete Application State
63
How it works
Depending on type of field, different operators are available to create the desired conditions
64
How it works Operators by field type

Text
Is Contains Is empty Is not empty
Number
Equal to Not equal to Less than Greater than Less than or equal Greater than or equal
Boolean
Is True Is False
Single Selection
Equals (allows selecting only one value) Not equals (allows selecting only one value) Included in (allows selecting multiple values) Is empty
Multiple Selections
Contains (allows selecting multiple values) Does not contain (allows selecting multiple values) Contains at least one (allows selecting multiple values) Is empty
65
Composite fields, fields for which there can be multiple instances (fields that are part of the Work experience, Education, Certification and Reference categories) have an additional operator This operator makes it possible to specify how to evaluate the condition against the multiple instances of the field The two possible values for this operator are:
All values
For the rule to be considered True, the condition must be True for all instances of the composite field. (AND)
How it works Additional operator for composite fields
At least one value

For the rule to be considered True, the condition must be True for at least one instance of the composite field. (OR)
66
The evaluation of the auto-progression conditions that have been configured can be triggered by various events:
Field value updated by a candidate Field value updated by a recruiter Field value updated by an integration script Field value updated in Transitions, Performance management or Evaluation Management Candidate being moved in the candidate selection workflow
Except for the Revert action, which does not trigger the autoprogresson rules evaluation, in order to avoid going back immediately to the step-status from which the revert happened. The next time an event triggers the evaluation of the rules, the candidate may be going back to the step-status it was reverted from.
How it works Auto-progression rules evaluation
67
When the user is opening or closing a candidate file, auto-progression occurs immediately for this one. In other situations, a task runs every 10 minutes to progress candidates If candidate fields are modified (not fields related to the submission), auto-progression rules are evaluated for all submissions of this candidate. Conditions using a Job-specific submission field are only considered for completed submissions. Submissions that are not completed will not be automatically progressed, even if the condition is met.
How it works Misc. information
68
69
The only change visible to Recruiters is that the current step and status of a candidate may be different after a change in the candidate or submission information or a progression in the CSW
70
71
No functional impact for candidate
72
73
Administration & Setup

Auto-progression configuration is part of the Candidate Selection Workflow configuration Recruiting Administration > Candidate Selection Workflow
Select the step containing the status you want to automatically progress candidates to
74
Select the status you want to automatically progress candidates to
75

Select this checkbox to enable auto-progression of candidates to this status, then click Create Condition to specify the conditions that must be met for auto-progression to occur
76
In the first dropdown, select Job-specific submission in order to access the field-based conditions
77
In the second dropdown, select either Standard field or User-defined field depending on the type of field to use in the condition
78
In the third dropdown, select the field category. This narrows down the list of fields displayed in the fourth dropdown
79
In the fourth dropdown, select the field on which to create the condition.
80
Depending on the data type of the selected field, an operator needs to be selects (ex: greater than for numeric fields). Here, as it is a boolean field, only the Is operator is available
81
In the last dropdown, select the value with which to create the condition. Depending on the type of condition being created, this may be a dropdown, a text box or a selector
82

Example of a condition on a text field
83

Example of a condition on a numeric field
84

Example of a condition on a single selection field
85

Example of a condition on a multiple selection field
86
Multiple conditions can be defined. Either all conditions must be true (AND), or at least one of them (OR)
87
Recommended Practices
88
System administrators must design and test new auto-progression rules thoroughly as they may lead to undesired behavior if not used correctly. For the same reason, it is not recommended to use the auto-progression functionality in order to automatically reject candidate submissions, it should only be used to progress candidates in the selection workflow
89
Thank You
90
13B Up & Running Tutorial, Recruiting Center
Automatic Posting to Mobile Career Sections
October 2013 Release 13B

91
Overview
Before release 13B, a recruiter wanting to have a job listed on a standard career section (standard CS) as well as on a mobile career section (mobile CS) had to remember to select both career sections when posting. It was also necessary to remember to unpost from both career sections. This enhancement automates this process for the user
92
How it works
Posting and unposting
It is not anymore possible to manually post on mobile career sections linked to standard career sections (through Recruiting Center and integration) Requisitions posted on a standard CS will be automatically posted on the linked mobile CS (if there is one) Requisitions unposted on a standard CS will be automatically unposted from the linked mobile CS (if there is one)
93
How it works
Synchronization
Configuration changes can trigger a synchronization of linked standard and mobile career sections When linking a mobile CS to a standard CS, all requisitions currently posted on the standard CS will be automatically posted to the mobile CS When unlinking a mobile CS from a standard CS, all requisitions that are only posted on this standard CS will be automatically unposted from the mobile CS When a linked mobile CS is activated (because it was inactive before), a synchronization occurs to ensure that the mobile CS has the same postings as the standard one(s) When migrating a Taleo zone to 13B, a synchronization occurs to ensure that postings having been made manually are removed and that the mobile CS has the same postings as the standard one(s)
94
How it works
Timing
When posting/unposting a requisition on a standard CS linked to a mobile CS, the job is automatically and immediately posted/unposted on the mobile CS (no delay) When a synchronization is triggered by a configuration change:
Synchronization is scheduled to start 30 minutes later When the synchronization begins:
All requisitions that are on the mobile CS but not on the standard CS are unposted from the mobile CS All requisitions that are on the standard CS but not on the mobile CS are posted on the mobile CS
The time needed to complete the synchronization depends on the volume of requisitions to post and unpost (could take a few hours when linking to a career section with several thousand postings)
95
How it works
Posting dates
As requisitions are automatically posted, the posting start and end dates are determined by the system. If the mobile CS is linked to a single standard CS:
The start and end dates of the standard CS are used
If the mobile CS is linked to multiple standard CSs and the same requisition is posted on more than one standard CS:
The earliest start date among the standard CSs start dates is used The latest end date among the standard CSs end dates is used If the standard CSs have different dates including a gap in the middle (a period where the req is not posted), only the start and end dates from the standard CSs on which the req is currently posted are considered
96
How it works
Configuration mismatches
If the system is not able to automatically post a requisiton on a linked mobile CS due to a configuration mismatch with the standard CS:
No warning or error message will be displayed The posting will just be ignored
Some aspects of the configuration of the linked career sections (standard and mobile) can lead to such situations:
OLF configurations are not identical Radius search is enabled on one CS and not on the other (when radius search is enabled, only requisitions with work locations can be posted)
97
98
Posting
It is not anymore possible to manually post on mobile career sections linked to standard career sections Linked mobile career sections are not listed anymore when posting a requisition
99
History
Linked mobile career sections are completely invisible for Recruiters. Only administrators can see linked mobile career sections in the configuration area. Posting/unposting on linked mobile career section is not tracked in the requisitions history
10 0 This information is not a commitment to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
It is still possible for Recruiters to manually post and unpost requisitions on mobile career sections that are not linked to a standard career section
As no automatic posting occurs on these career sections, they are still available to be manually posted to (through Recruiting Center and integration)
No changes for candidates, they can access and use mobile career sections as before

In the list of career sections, a new column identifies which career sections are mobile ones:
In the list, there is no distinction betwen mobile career sections that are linked and those that are not

As before, to link or unlink career sections together, edit the standard CS properties and change the Linked Mobile Career Section property
Mobile career sections should have the same context settings as the standard career sections they are linked to
As jobs are posted automatically and silently (no UI), different context settings could result in jobs being posted on the standard career section and not on the mobile one. If automatic posting is not possible on the mobile career section due to the coverage options, there is no warning, the posting is just ignored (not posted on the mobile CS) Pay close attention to the following context settings to ensure they are configured the same in both standard and mobile career sections:
Job Fields Location Organizations Enable the radius search (which only accepts jobs with work locations)
Thank You
13B Up & Running Tutorial, Onboarding & Transitions
Synchronizing a Zone from Original Onboarding to Transitions

Sync Onboarding to Transitions: Overview Current Onboarding customers can upgrade their configurations into Transitions Get prepared for when customer is ready to launch new candidates into new processes Saves time and prevents errors vs. recreating processes and forms and UDFs manually Packaged Service Offering is recommended, though customers could do it self-service
Sync Onboarding to Transitions: Background

New product Onboarding & Transitions is unified with Recruiting, shares almost all database info, unified candidate portal Career Section, integrates with Learn, handles offboarding, etc. etc. All licensed Onboarding customers can turn on Transitions in 12C and beyond, no new license fees Customers can start from scratch to define processes 13B Synchronization tool allows copying most of the Onboarding process investment into Transitions Services can transform the rest, and can optimize overall portals, processes, integrations as needed
Sync to Transitions: What is it?

Automated copy of most Administrative objects from Onboarding into Transitions within a single zone Wherever Onboarding had a copy of a field, now Transitions can access and share the real field! So each object gets transformed to use different tokens:
Before using: Onboarding has lots of processes, tasks, forms, message templates, documents, UDFs After using: Transitions now gets all the same processes, tasks, forms, message templates, documents, some UDFs Other UDFs are now shared with Recruiting, no longer duplicated
Some areas are so different that they must be manually revised by consultants and/or Transitions Administrators
Sync has No Effect on New Hires nor WebTop

Each process starts and ends in its place
Running Onboarding processes are not moved anywhere Completed new hire Onboarding data is not moved anywhere After migration, new Transitions processes can be launched New Transitions processes run and finish in Transitions
Candidates/New Hires/Employees are unaffected

Onboardings tasks still appear in new hires New Hire Portal New Transitions tasks appear in candidates Career Section
Oversee processes in WebTop vs. Center

Onboarding WebTop oversees all original Onboarding processes These do not move into the Transitions Center Transitions Center oversees Transitions processes, when launched
A Note about Reporting

Onboarding is fully reportable using Business Objects Transitions will be fully reportable using Oracle Business Intelligence (OBI)
This is coming soon: planned in 13C timeframe, early 2014
Until then:
Transitions shares most candidate data with Recruiting, so BO reporting could be used for any candidate reports Transitions process progress and task assignee data is not yet reportable until ~13C timeframe, but Taleo Connect today can export and access this data
Consider syncing processes now, to get ready!
Administrator: Synchronization Tool

Appears for users with Transitions Admin permissions Only in zones that have Onboarding activated
Run the Synchronization Tool
Admin starts the synchronization Takes approximately an hour Almost everything from Onboarding is created in Transitions Admin must make adjustments in Synchronization Report
Create LUDS / SUDS for Use in Transitions

Admin must choose a cut-off number for Sync tool, for transforming Onboarding UDFs into Recruiting UDFs Sync creates the right kind of UDS in Recruiting:
Onboarding UDSs w/more selections become Recruiting LUDS Onboarding UDSs w/fewer selections become Recruiting SUDS
Every Type of Object Gets Synced

Creates the Transitions-accessible version
User-defined selections User-defined fields Images E-signatures Documents Message Templates Forms Tasks Processes and Subprocesses
Report Shows What Happened

Most things are Missing in Transitions so theyre Added
Most configurations and formatting are identical Fields are switched to use shared Recruiting or Transitions tokens
If an object having the same code Exists in Transitions, the Onboarding object gets Skipped
In case Transitions Admin has already configured some forms In case the sync tool has already been run
Report Shows any Adjustments Needed

Some Onboarding editable fields become read-only
Offer, Req, Department data editable only in Recruiting

Some Onboarding editable fields become read-only Some pages of forms are left blank in Transitions
Certain fields are obsolete, such as E-Verify from 2008

Some Onboarding editable fields become read-only Some pages of forms are left blank in Transitions Some fields become placeholders to be fixed
Onboardings EEO fields are not supported in Recruiting
Errors are not Self-Service

Rarely, the sync stops running due to an error Usually Admins cant resolve it: file SR with Support
Beyond the Synchronization Tool: Work to be done by Services Package and/or Transitions Admin
Creative Consulting Decisions Needed

Product settings must be revisited, if not unified

Product settings must be revisited, if not unified PDF documents must be manually updated
Replace Onboarding tokens in PDFs with Transitions tokens

Product settings must be revisited, if not unified PDF documents must be manually updated New Hire Portal must become Content Pages
Can have several rich content tasks on Career Section

Product settings must be revisited, if not unified PDF documents must be manually updated New Hire Portal must become Content Pages New Passports must be deployed
Enhancements for easier configuration and troubleshooting Some prior partners and some new partners available

Product settings must be revisited, if not unified PDF documents must be manually updated New Hire Portal must become Content Pages New Passports must be deployed Integrations with HRMS for new hires or employees
Imports/exports should be examined by a Connect consultant

Product settings must be revisited, if not unified PDF documents must be manually updated New Hire Portal must become Content Pages New Passports must be deployed Integrations with HRMS for new hires or employees Reports in Business Objects must be redone in OBI
Summary
Consider When and How to Take Transitions

Current customers can upgrade Onboarding configurations into Transitions in a zone Consulting can help run the synchronization tool and optimize all other areas Get prepared for when you are ready to launch new candidates into new processes
Thank You

Taleo 13B Latest Features

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Taleo 13B Latest Features

Încărcat de

Drepturi de autor:

Formate disponibile

Up & Running Tutorials

SaaS Customer Lifecycle Management

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

13B Up & Running Tutorials

Pages 3 - 16 17 - 28 29 - 56 57 - 90 91 - 109 110 - 135

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

13B Up & Running Tutorial, Onboarding &Transitions:

Launching a Process for Candidates without Email Addresses

September 2013 Release 13B

Fallback Email Addresses: Overview

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Recruiter Perspective: Error if no Fallback

For candidate whose user account has email address:

For candidate whose user has no email address:

Recruiter Perspective: Error if no Fallback

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Candidate Perspective: with Email Address

Also, see some tasks on Career Sections Tasks tab:

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Candidate Perspective: without Email Address

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

My Task List, from Candidate Perspective

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Administrator Perspective: Settings

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Administrator: Important Notes

Background: SmartOrg vs. Candidate

To launch a Transitions Process, user needs email

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

13B Up & Running Tutorial Evaluation Management: SmartOrg User Picker

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

SmartOrg User Picker: Overview

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

New Permissions to Manage Evaluators

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

How to Add Evaluators

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

How to Add Evaluators (contd)

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

How to Send Feedback Requests

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Permissions and Adding Evaluators

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Permissions and Removing Evaluators

Recommendations for Users

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Important for Users to Note

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Up and Running Tap for Taleo on TEE 13B

Enabling Mobile Tap Overview

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

1. Select User Type, under the Users section

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.

Oracle Confidential. Copyright 2013, Oracle. All rights reserved.