Refer to the following scenario to answer the question below.
Your organization has these recruiting business requirements:
When an external candidate submits their application, you want them to be able to immediately manage and view their job application.
Recruiters need to view delivered reports in a specific recruiting stage sequence.
You want new hire demographic data to populate from the job application.
What Edit Tenant Setup - Recruiting setting do you need to enable to prepopulate the new hire's gender and date of birth from the recruiting process?
The applicable tenant setting is Copy Personal Information from Job Application on Initiate Hire. It controls the transfer of eligible personal information collected during recruiting into the Initiate Hire transaction. With this setting enabled, information such as gender and date of birth can prepopulate the corresponding new-hire fields rather than requiring an administrator to re-enter the information manually.
''Copy Personal Information when Copying Job Applications'' applies when an existing job application is copied or reused. It does not govern the transition from candidate to worker. Candidate fields in notifications affect communication content, while Require Candidate Home Account governs external candidate authentication. Neither option controls the propagation of demographic information into the hiring process.
The important distinction is the lifecycle event. The source is the candidate's job application, but the destination is the hire transaction. Therefore, the configuration must explicitly act when Initiate Hire begins. This supports Workday's unified-data model by retaining appropriate information across recruiting and staffing without an external integration or duplicate entry. Study Guide reference: Configure Recruiting Functionality --- Edit Tenant Setup--Recruiting, Candidate Personal Information, Initiate Hire, and Candidate-to-Worker Data Transfer. Workday Recruiting datasheet
===============
Refer to the following scenario to answer the question below.
You need to update the Offer business process to accommodate new requirements from the recruiting team. They would like candidates who accept the offer document to automatically move into the Ready for Hire stage. They also want to be able to complete both the Initiation and Propose Compensation Offer/Employment Agreement processes simultaneously.
What documents can you configure for the candidate to review?
The Review Document step can present any eligible Workday document configured on that step. The document does not have to originate exclusively from the immediately preceding Generate Document step, be manually created by a Recruiting Administrator, or reside in Workday Drive.
Generate Document commonly produces the primary offer letter or employment agreement, but the Review Document step is broader. Administrators can configure additional Workday documents that the candidate must review or acknowledge as part of the offer process. Examples can include policy documents, disclosures, contractual attachments, or other materials appropriate to the candidate and recruiting context.
The distinction is between document generation and document presentation. Generate Document creates output from a configured document template. Review Document determines which available documents are displayed to the candidate for review and, when configured, acknowledgment or electronic action. Restricting the step to only generated documents would unnecessarily limit the process and is not how the step is designed.
This flexibility supports a single candidate-facing package while allowing organizations to vary documents through condition rules and process configuration. Study Guide reference: Define Recruiting Business Processes --- Offer, Generate Document, Review Document, Candidate Document Presentation, and Conditional Documents. Workday identifies configurable offers, agreements, and an easy-to-sign candidate experience as Recruiting capabilities. Workday Recruiting datasheet
===============
You created an evergreen requisition and a job requisition.
How do you link them?
An evergreen requisition and a standard job requisition are linked by assigning the same job profile to both. The shared job profile establishes the functional relationship that allows candidates sourced through the evergreen pipeline to be considered for the associated hiring requisition.
A supervisory organization identifies organizational ownership but does not, by itself, define the required connection between the requisitions. Assigning the same position is inappropriate because an evergreen requisition supports continuing candidate pipelines and is not tied to a single position in the same manner as a position-specific hiring requisition. Workday does support linking the requisitions, making option C incorrect.
The job-profile relationship ensures that the evergreen pipeline represents candidates appropriate for the same type of work as the standard requisition. Administrators should still verify other relevant attributes, such as location, worker type, time type, and qualifications, before moving or associating a candidate. Sharing a job profile creates the linkage; it does not mean every candidate in the evergreen pipeline automatically satisfies every requirement of the standard requisition. Study Guide reference: Configure Requisitions and Their Components --- Evergreen Requisitions, Standard Job Requisitions, Job Profiles, Candidate Pipelines, and Requisition Linking. Workday describes evergreen requisitions as a mechanism for building reusable candidate pipelines. Workday Talent Acquisition
You created a new Recruiting Assistant role and security group. You also updated the security policy and activated the changes. Recruiting assistants will move forward or decline candidates that are in the Review stage.
What is the next step to grant them this access?
The security group must be assigned to the Review Decision step in the Review Candidate business process. Review Candidate governs activity while an application is in the Review stage, and Review Decision is the step from which an authorized participant moves the candidate forward or declines the application.
Updating domain or business-process security and activating the policy makes the group eligible for access, but it does not automatically route the Review Decision task to that group. Business-process step routing must also identify the Recruiting Assistant security group.
A completion step on Job Application would not provide the specific decision task required during Review. Job Requisition controls hiring-demand creation and approval and is unrelated to candidate review. Option D identifies the correct decision name but places it on the parent Job Application process rather than the Review Candidate subprocess where the decision is performed.
Workday security requires alignment between domain access, business-process security, and step routing. Missing any one of these layers can prevent users from receiving or completing the action. Study Guide reference: Configure Recruiting Security --- Review Candidate, Review Decision, Recruiting Roles, Business-Process Security, and Step Routing. Workday Recruiting datasheet
===============
A hiring manager notices that when a candidate enters the Offer stage, Workday does not consistently generate an offer letter.
What is the most likely explanation for this inconsistency?
The offer letter is created by the Generate Document step. If the letter is generated for some candidates but not others, the most direct explanation is that a condition rule on that step evaluates differently according to the candidate, requisition, organization, country, or other transaction data.
A condition on Offer Decision could affect whether a decision step executes, but it does not directly explain inconsistent document generation when candidates enter Offer. Request One-Time Payment is relevant only when the offer includes a one-time payment; it is not a prerequisite for producing every offer letter. Review Documents occurs after a document is available and controls review or presentation, not initial generation.
An administrator should inspect the Generate Document step's entry condition, document rule, and template eligibility. A false condition causes Workday to skip the step, producing the observed inconsistency. The document configuration should also be tested against representative candidate and requisition populations to confirm that the intended template and condition are valid. Study Guide reference: Define Recruiting Business Processes --- Offer, Generate Document, Entry Conditions, Document Rules, and Offer Templates. Workday's official Recruiting materials identify configurable offer workflows and document generation as connected elements of offer management. Workday Recruiting datasheet
===============
Currently there are no comments in this discussion, be the first to comment!