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 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.
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 to a requisition template, users would no longer be prevented from creating a requisition from scratch.
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.
A different worker-related field can be selected for each offer within a same requisition.
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.
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.
After a file is attached, the system validates if the file format is supported.
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 When creating an offer, the recruiter can specify a worker location whether or not it was originally identified in the requisition.