Employee data API: effective date enforced in work table update

The effectiveDate field in the Work Table update API is now correctly enforced as mandatory, preventing silent failures or unexpected behavior.

What's new

We fixed a validation issue in the Work Table update endpoint where the effectiveDate field was mistakenly treated as optional. When the field was omitted, the API defaulted to the current date, which could result in a new row being created instead of updating the intended one, along with incorrect audit logs.

With this fix, effectiveDate is now correctly required for all update requests.

Why it matters

When effectiveDate wasn’t provided, the system used the current date by default.

This could lead to:

• An unexpected new Work Table row being created
• Updates being applied to the wrong entry
• Incorrect or misleading audit logs

Requiring effectiveDate ensures updates target the intended Work Table entry and behave predictably.

Best practice for updates

• Always read the existing Work Table entry first
• Modify only the fields that need updating
• Write the full entry back, keeping the same effectiveDate value

If you need to change the effective date, use the appropriate create or delete endpoints instead of an update.

Action required

Review your integrations to make sure all Work Table updates include the correct effectiveDate that preserves the original value.

To learn more, see Update a work entry in the employee's work history table.