Updated the Employee Entitlement Balance Import to support end dates for balance periods. Now, the import XML supports the new, optional <EndDate> field. This update was made in conjunction with a new feature that was added in this release where users can end-date balance periods within Dayforce. Users can end-date balance periods by either running the Employee Entitlement Balance Import or by configuring end-date entitlements in Dayforce (see WFM-49814). See the Dayforce Employee Entitlement Balance Import Specification document. | |
Updated the Employee TAFW Import to support more time away balance units. Previously, you could only import values for hourly time away balances. Now, you can also import values for daily and weekly time away balances. Note: This update is intended for use cases where daily and weekly time away durations are calculated in external applications and then imported into Dayforce. To support this functionality, the <NetUnits> field is now available to add to the import’s XML. The <NetUnits> field is optional and must correspond to the value in the <NetHours> field, which represents the number of paid hours for the TAFW request. The <NetUnits> field supports up to five decimal places. For example, to import a TAFW request for a single day using a daily balance, configure the following fields: <AllDay>true</AllDay> <NetHours>8</NetHours> <NetUnits>1.00000</NetUnits> In this example, the 1.00000 value represents a full day of time away. This value corresponds to an 8-hour time away period for hourly balances. To import a TAFW request for a single day using a weekly balance, configure the following fields: <AllDay>true</AllDay> <NetHours>8</NetHours> <NetUnits>0.20000</NetUnits> In this example, the 0.20000 value represents a full day of time away using a weekly balance (that is, one day in a 5-day workweek). This value corresponds to an 8-hour time away period for hourly balances. Important:
See the Dayforce Employee TAFW Import Specification document. |