Content Pages That Target a Candidate or Employee
Onboarding (Transitions) administrators choose between two different configuration methods to ensure that the right content page is viewed by candidates or employees involved in a process.
The first method consists in the creation of a task that contains a specific content page. The Onboarding (Transitions) administrator selects Display a Content Page in the task's Action list. The Onboarding (Transitions) administrator then chooses the appropriate content page. The content page selected acts as the related source of the task, just as a form acts as the related source of a form task. The specific content page will be displayed to everyone who is assigned the task. Organization, Location, and Job Field (OLF) information specified for a content page is not considered.
The second method consists in the creation of a content page task for which no specific content page is specified. The Onboarding (Transitions) administrator still selects “Display a Content Page” but does not select any content page as the related source. In this case, the Onboarding (Transitions) system determines the most appropriate content page to display to each candidate or employee when the person reaches that step in the process. The Onboarding (Transitions) system examines all content pages (that have Active status) and displays the one whose Organization, Location and Job Field (OLF) is the best match with the OLF specified in the requisition.
The following examples describe when it is best to use each of these methods.Method 1. Administrator-selected content pages for tasks that always display the same content
Often, business requirements are such that different groups of people need to receive different content based on any information that the Onboarding (Transitions) system can track. For instance, user-defined fields can be used to track distinctions such as hourly vs. salaried workers or campus hires vs. experienced hires. All of the task types in Onboarding (Transitions) can be configured so they target different groups based on conditions configured for transitions that are part of a process. This is also the case for content page tasks. Onboarding (Transitions) administrators can create conditions based on UDFs or standard fields such that a task will be displayed to a subset of candidates or employees. If desired, administrators can also create additional conditions based on the “opposite” values in these fields, to show a different task to all the remaining candidates or employees.
When configuring a content page task so it targets a specific group of candidates or employees, it is best to select a specific content page for the content page task. The Onboarding (Transitions) administrator can assign conditions to the content page task such that the task (and associated content page) is assigned only to candidates or employees who satisfy the conditions. Because these conditions can be configured based on any field in the Onboarding (Transitions) system, these conditions are extremely powerful. If a large number of distinctions require their own content page task, the Onboarding (Transitions) administrator must configure many different conditions, transitions and tasks to specify each content page.
Method 2. Content pages for tasks where the system selects the best content page to display
In other business situations, the determination of the most appropriate content is based on Organization, Location, and/or Job Field values. Maps to a specific location, policies for a specific organization, and success stories for a specific job family are some examples of business requirements.
In these situations, the Onboarding (Transitions) administrator does not specify a particular content page for a content task. When no content page is specified, the system will select the most pertinent content page for each content page task assignee. The Organization, Location, and Job Field information of each content page (that has Active status) is compared with the OLF specified in the requisition in the current process, or with the OLF of the candidate or employee when no requisition is involved (for example, a process launched by Taleo Connect on the General Profile). Far fewer conditions, transitions, and tasks are needed. Consequently, the Onboarding (Transitions) administrator has a much simpler job to perform and the process preview diagram is simpler.
Because the system selects the content page that best matches the OLF of the requisition or the candidate, it would make the same selection each time it encountered a context-sensitive content page "no specific content page" content page task in the process. In other words, it would display the same content to the candidate or employee each time. For this reason, it is important to ensure that a process does not include more than one "no specific content page" task.
(CP=content page)
The previous diagram illustrates both methods of configuring content pages. Candidates or employees will see three content pages on their career section's Tasks tab. First, they will see one content page as a welcome message due to Step/Task A. Next, everyone will see the same content page about charitable opportunities, due to Step/Task B which calls the fifth content page as its related source. Later, the process's conditions and transitions ensure that only the salaried people will be assigned Step/Task C1, which calls the salaried content page, whereas only the hourly people will be assigned Step/Task C2, which calls the hourly content page.In the diagram, no specific content page is associated with Step/Task A. This means that the system must determine the content page that is the best match for each assignee. There are currently seven content pages active in the system. Three of them have no Organization, Location, nor Job Field: content pages 4, 5, 6 and 7. Content page 1 has the location Canada, content page 2 has the city-level location New York City within the United States, and content page 3 has the location of United States. Content page 4 is marked as the default content page; no OLF is required. Three additional content pages have no Organization, Location or Job Field: content pages 5, 6, and 7.
When a candidate or employee process begins for a requisition in any city in Canada, the first task in the career section's tasks tab will display content page 1.
When a process begins for a requisition in New York City, the first task in the career section will display content page 2.
When a process begins for a requisition in any other location within the United States, that first task will display content page 3.
When a process begins for a requisition in any location other than the United States or Canada, the first task will display the default content page 4. The default flag ensures that this content page will be displayed even though there are other content pages in the system that have no specified location.
To summarize, the most appropriate content page will be displayed while the Onboarding (Transitions) administrator did not have to configure four specific content tasks, four transitions leading into them, and four more conditions and transitions leading out of them.