The Vacating Employee and Similar Employee fields of the system (that is, default) Job Requisition form return results for all employees in your organization. Previously, they only returned results for the employees to which you had access in Dayforce. This was done to allow users to select indirect reports in the Job Requisition form.
To support this update, the XML code of the system Job Requisition form in Workflow Administration > Form Builder includes a new XML tag that removes security on the Vacating Employee and Similar Employee fields of the form.
This tag, which is called <ApplyEmployeeSecurity>, is used in the XML code of the Job Requisition form twice, once to remove security on the Vacating Employee field and once to remove location security on the Similar Employee field.
Below is an excerpt of the relevant XML code from the system Job Requisition form, with the <ApplyEmployeeSecurity> tags highlighted for reference:
<!-- Vacating Employee Picker -->
<Label>
<Style>IVLabel</Style>
<Caption>lblJobReq_Details_VacatingEmployee</Caption>
<Row>2</Row>
<Column>3</Column>
<VisibleIf>JobReq_Reasons:Replacement</VisibleIf>
</Label>
<EmployeePicker>
<Style>IVAutoCompleteBox</Style>
<Row>3</Row>
<Column>3</Column>
<ItemForeground>Black</ItemForeground>
<Limit>10</Limit>
<CacheServerAnswers>True</CacheServerAnswers>
<SearchFilter>Contains</SearchFilter>
<BindingProperty>List_JobReq.VacatingEmployeeId</BindingProperty>
<SelectionChangedEventProcess>JobReqVacatingEmployeeSelected</SelectionChangedEventProcess>
<SelectionChangedEventSelectorId>MainSelector</SelectionChangedEventSelectorId>
<VisibleIf>JobReq_Reasons:Replacement</VisibleIf>
<ApplyEmployeeSecurity>false</ApplyEmployeeSecurity>
</EmployeePicker>
<!-- Similar Employee Picker -->
<Label>
<Style>IVLabel</Style>
<Caption>lblJobReq_Details_SimilarEmployee</Caption>
<Row>2</Row>
<Column>3</Column>
<VisibleIf>JobReq_Reasons:New</VisibleIf>
</Label>
<EmployeePicker>
<Style>IVAutoCompleteBox</Style>
<Block>1</Block>
<Row>3</Row>
<Column>3</Column>
<ItemForeground>Black</ItemForeground>
<Limit>10</Limit>
<CacheServerAnswers>True</CacheServerAnswers>
<SearchFilter>Contains</SearchFilter>
<BindingProperty>List_JobReq.SimilarEmployeeId</BindingProperty>
<SelectionChangedEventProcess>JobReqSimilarEmployeeSelected</SelectionChangedEventProcess>
<SelectionChangedEventSelectorId>MainSelector</SelectionChangedEventSelectorId>
<VisibleIf>JobReq_Reasons:New</VisibleIf>
<ApplyEmployeeSecurity>false</ApplyEmployeeSecurity>
</EmployeePicker>
As seen in the XML code above, the <ApplyEmployeeSecurity> tag is set to "false" for the system Job Requisition form. It isn’t possible to change this setting for the system Job Requisition form, because the XML for system forms is read-only. If you want to add security back to the Job Requisition form, you can create a custom version of the Job Requisition form, and replace the "false" in the <ApplyEmployeeSecurity> tag to "true".
<ApplyEmployeeSecurity>true</ApplyEmployeeSecurity>
You would have to do this for both of the instances above (for both the Vacating Employee and Similar Employee fields). Setting these tags to "true" restores pre 8.49 behavior where the Vacating Employee and Similar Employee fields only return employees to whom you have access in Dayforce.
Using This Update in Custom Forms
If your organization already uses custom Job Requisition forms, and you want to remove security for similar/vacating employees in them, you must manually add the <ApplyEmployeeSecurity> tags and set them to “false” in your custom forms, exactly as they appear in the longer XML excerpt provided above.
When you’re creating new custom forms, create a copy of the system Job Requisition form. All of the code from the system form, including the <ApplyEmployeeSecurity> tag, carries over to the custom form.