A specific Position can be assigned to a standard job requisition but not to an evergreen requisition. A standard requisition represents defined hiring demand and can therefore be associated with the position that the successful candidate will fill.
An evergreen requisition is designed for continuous sourcing and candidate-pipeline management. It may exist when no immediate vacancy is available, so tying it to a particular position would conflict with its purpose. Instead, evergreen requisitions use broader attributes such as job profile, location, and supervisory organization to identify the type of candidates being sourced and to support linkage with appropriate standard requisitions.
When an opening becomes available, the candidate moves from the evergreen pipeline to a linked standard job requisition. That requisition contains the definitive staffing information, including the position when the organization uses position management. This separation prevents a sourcing pipeline from consuming or representing a specific vacancy prematurely. Study Guide reference: Configure Requisitions and Their Components - Evergreen Requisition Restrictions, Position Management, Job Profiles, Locations, Supervisory Organizations, and Linked Requisitions . Workday distinguishes evergreen candidate pipelines from the specific requisitions used to fulfill actual hiring demand. Workday Talent Acquisition

Automatic rejection of unsuccessful applicants requires Disposition Remaining Candidates to be enabled in Maintain Recruiting Dispositions. This setting instructs Workday to disposition other active candidates when the requisition or applicable opening reaches the configured completion point.
The Ready for Hire subprocess can establish when the successful candidate advances, but it does not independently activate tenant-level dispositioning of all remaining candidates. Enable Candidate Fields in Notifications affects communication content and has no effect on disposition logic. A condition rule in Hire is not the delivered configuration for this requirement. "Disposition Remaining Jobs" does not correspond to the candidates who must be rejected.
Dispositioning is more than closing a posting. It assigns an outcome to unsuccessful candidates, removes them from active processing, and can trigger configured notifications. Administrators must also verify the applicable disposition reason, notification behavior, and any exceptions for candidates attached to multiple requisitions. The setting should be tested with a filled requisition to ensure only the intended remaining candidates are affected. Study Guide reference: Define Recruiting Business Processes - Ready for Hire, Maintain Recruiting Dispositions, Disposition Remaining Candidates, Automatic Rejection, and Candidate Notifications . Workday lists automated workflow and automatic candidate dispositioning among its Recruiting capabilities. Workday Recruiting datasheet

Under position management, each worker occupies a distinct position. If the approved hiring requirement increases from eight to thirteen, the existing job requisition should be edited so that the number of openings equals thirteen .
Changing the staffing model to job management would be a fundamental organizational-design change and is neither necessary nor appropriate for increasing the number of openings. Hiring multiple workers into one position conflicts with the one-worker-per-position structure of position management. An Additional Data step can capture supplemental information but does not increase the requisition's authorized openings.
Editing the original requisition retains a single hiring record for the same staffing requirement while increasing its capacity by five positions. The transaction remains subject to the configured Job Requisition business process, including any approvals required when the number of openings changes. Administrators should also confirm that the necessary positions exist or are created through the applicable staffing configuration and that budget or headcount controls support the increase. Study Guide reference: Configure Requisitions and Their Components - Position Management, Number of Openings, Editing Job Requisitions, Position Capacity, and Approval Routing . Workday identifies job-requisition creation, management, and fulfillment as integrated Recruiting and HCM functions. Workday Recruiting datasheet

Configure Consolidated Template provides the combined interface needed to initiate the offer or employment-agreement activity while entering the associated compensation components in one coordinated experience. The template can consolidate base compensation, one-time payments, and stock information that would otherwise require separate initiation and proposal activities.
Configure Optional Fields determines which additional fields appear or are required, but it does not combine separate business-process activities. Editing the business-process security policy controls which security groups may initiate or participate in the process. Maintain Step Conditions determines whether a configured step executes. Neither task creates a consolidated compensation-entry experience.
The requirement explicitly states that Initiation and Propose Compensation Offer/Employment Agreement must be completed simultaneously. This points to configuration of the consolidated template rather than routing, security, or conditional execution. Consolidation reduces duplicate entry and ensures that compensation-related offer data is captured within a consistent transaction context. It also supports Workday Recruiting's integrated connection between candidate offers and compensation. Study Guide reference:
Define Recruiting Business Processes - Offer and Employment Agreement, Consolidated Templates, Propose Compensation, One-Time Payments, and Stock . Workday describes offer management as combining configurable workflows with a seamless connection to compensation. Workday Recruiting datasheet