After Enhanced Employee Gender is enabled, customers can keep using custom forms with legacy gender and gender identity fields. Through backward compatibility, these forms continue to work with Enhanced Employee Gender. Some configuration notes and limitations are described below.
What Are Custom Forms?
Custom forms are built by customers or Dayforce internal teams in the Form Builder feature. These aren’t to be confused with system forms, which are built by Dayforce for customers. If a significant change is required to a custom form, someone has to do the update as Dayforce can’t mass update custom forms for individual customers due to potential risks.
What Is Backward Compatibility?
With backward compatibility, customers can keep using existing gender and gender identity elements with the new Enhanced Employee Gender functionality.
The legacy Gender and Gender Identity fields on forms continue to work until customers start using the Enhanced Employee Gender grid. However, customers should update their custom forms to support Enhanced Employee Gender because the legacy Gender and Gender Identity fields provide limited Enhanced Employee Gender functionality.
Note that the legacy Gender and Gender Identity fields on forms will cease to function if some prerequisites are not fulfilled.
Backward Compatibility Limitations
Backward compatibility has some limitations. With certain configurations, backward compatibility doesn’t work and the form either doesn’t show information, or the workflow fails. If this happens, the customer must update their configuration to use the Enhanced Employee Gender Gender grid on custom forms for gender information.
The limitations for backward compatibility are described below.
Display Enhanced Employee Gender Last Modification Information and Effective Dating client property is enabled
If the Display Enhanced Employee Gender Last Modification Information and Effective Dating client property is enabled, effective dated gender records can be assigned to employees. The legacy gender fields on forms don’t accept effective dated records, so errors will occur or forms won’t function properly if this client property is enabled.
See Enabling the Display Enhanced Gender Last Modification and Effective Dating Client Property.
| Employee | Legacy Gender Field | Legacy Gender Identity Field |
|---|---|---|
| 0001 | Male | Male |
Result: The Display Enhanced Employee Gender Last Modification Information and Effective Dating client property isn’t supported in backward compatibility, so this form fails during workflow.
The Gender module is configured for a country, state, or province
After the migration, if you change any of the following settings for a country, state, or province in HR Admin > Employee Gender Admin > Gender, this information won’t be available on forms:
- The Collect Assigned Sex Information checkbox is cleared
- The Make Assigned Sex Mandatory checkbox is cleared
- The Gender Identity checkbox is cleared
- You add custom-assigned sex values (not system M or F) for a country, state, or province
If you change any of the above settings, the following will happen on forms that contain the legacy fields:
- The legacy Gender drop-down list shows only Male and Female.
- The legacy Gender Identity drop-down list shows only Male, Female, and any other options that were added before the migration to Enhanced Employee Gender.
Germany is an exception because U and D are additional options for that country.
See Enhanced Employee Gender Administration Screen and the Compliance Framework.
An employee has multiple gender records
With Enhanced Employee Gender, employees can have a gender record for each location they live in, work from, or want to be reported in. However, multiple gender records aren’t backward compatible in forms. If an employee has multiple gender records, the form either fails in workflow or it doesn’t post a value to the legacy gender fields.
See Confidential Information Updates.
| Employee | Country | State | Assigned Sex | Gender Identity |
|---|---|---|---|---|
| 0001 | Germany | N/A (blank, not applicable) | Male | Male |
| 0001 | United Kingdom | N/A (blank, not applicable) | Male | Male |
An employee in the United States or Canada has state or province gender records
With Enhanced Employee Gender, an employee in the United States or Canada must have a state or province value assigned to their gender records. They also have a country gender record. In this case, the form either fails during the workflow or it doesn’t post a value to the legacy gender fields.
| Employee | Country | State | Assigned Sex | Gender Identity | “isFederal” Flag |
|---|---|---|---|---|---|
| 0004 | United States | N/A (blank, not applicable) | Male | NULL (blank) | 1 OR 0 |
| 0004 | United States | Florida | Male | Female | N/A (blank, not applicable) |
The following diagram shows the mapping between legacy fields and the Enhanced Employee Gender fields:
The following tables contain examples of the mapping shown in the preceding diagram.
| Legal Entity | Legacy Data - Eample | Enhanced Employee Gender Entity | Enhanced Employee Gender Data - Example |
|---|---|---|---|
| Pay Group | United States | Country | United States |
| State/Province | NULL | ||
| Gender | Male | Assigned Sex | Male |
| Gender Identity | Male | Gender Identity | Male |
| is Federal flag | 0 |
| Legal Entity | Legacy Data - Example | Enhanced Employee Gender Entity | Enhanced Employee Gender Data - Example |
|---|---|---|---|
| Pay Group | United Kingdom | Country | United Kingdom |
| State/Province | N/A | ||
| Gender | Female | Assigned Sex | Female |
| Gender Identity | NULL | Gender Identity | NULL |
| is Federal flag | N/A |
Other Resources
- For information about system forms and Enhanced Employee Gender, see System XML Forms for Enhanced Employee Gender.
- For customers who want to use all of the Enhanced Employee Gender functionality, see See Migrate Custom Forms.