All customers are migrated to Enhanced Employee Gender automatically. However, you must examine the following areas of Dayforce to make sure that you can use the enhanced employee gender functionality fully.
| Area of Dayforce | Does the area use any of the following legacy gender functionality? |
|---|---|
| API-based integrations | Gender or Gender Identity endpoints. |
| Custom forms | Gender or Gender Identity drop-down lists. |
| HR Import 2.0 | Gender or Gender Identity entities. |
| Legacy exports | Gender or Gender Identity entities. |
| V2 reports | Gender or Gender Identity in custom columns or filters. |
If your instance of Dayforce uses any of the legacy gender functionality described in the preceding table, you must make a few updates before you access and configure the new gender functionality.
To adopt Enhanced Employee Gender:
- Analyze your configurations using the SQL script provided by Dayforce. See Analyze Customer Data.
- After the script has been executed, Dayforce lets you know if you need to make any configuration changes:
- No configuration changes needed: If the script indicates that no updates are needed, go to Step 3.
- Configuration changes needed: If the script indicates that changes are needed, see Configuration Changes Needed and then return and continue to Step 3.
- Engage with the Enhanced Employee Gender features. See Enhanced Employee Gender Features and Updates.