If customers don’t want to use Enhanced Employee Gender, they can use Dayforce in backward compatibility mode. In backward compatibility mode, customers can keep using custom legacy gender configurations.
Note that there are limitations, and if customers overstep these limitations, their custom configuration will need to be updated or their configuration changes will need to be rolled back.
The following areas of Dayforce are backward compatible after the application is migrated to Enhanced Employee Gender.
- API-based integrations that use Gender or Gender Identity endpoints
- Custom forms containing Gender or Gender Identity drop-down lists
- HR Import 2.0 files using legacy gender or gender identity tokens
- Legacy XML exports using legacy gender or gender identity tokens
- V2 ad hoc reports containing Gender or Gender Identity as custom columns or filters