Genesys Cloud - Developer Announcements!

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Update to duration property validation in Worktype create and update APIs

  • 1.  Update to duration property validation in Worktype create and update APIs

    Posted 6 hours ago

    Summary

    The Create Worktype and Update Worktype APIs currently reject requests when the defaultDueDurationSeconds value exceeds the defaultExpirationSeconds value. This validation is being removed.

    After this change, the defaultExpirationSeconds field can be set to any duration greater than 3600 seconds, independent of the defaultDueDurationSeconds value. This update provides greater flexibility in configuring workitem expiration through the worktype default configuration while preserving lifecycle constraints.

    Affected APIs

    HTTP Method

    API

    Description

    POST

    /api/v2/taskmanagement/worktypes

    Create a worktype

    PATCH

    /api/v2/taskmanagement/worktypes/{worktypeId}

    Update the attributes of a worktype

    Effective Date

    Thursday, March 19, 2026

    Details

    Workitems dateDue and dateExpires properties are calculated at creation time from their worktypes defaultDueDurationSeconds and defaultExpirationSeconds properties. The change here aligns the validation rules on the worktype properties defaultDueDurationSeconds and defaultExpirationSeconds to match the validation rules on the workitem properties. This will allow greater flexibility when configuring default values.

    With this update, customers can configure a worktypes defaultExpirationSeconds independently of the defaultDueDurationSeconds, as long as defaultExpirationSeconds is less than 3600 seconds.

    Customer Impact

    Previously, requests where defaultDueDurationSeconds was later than defaultExpirationSeconds were rejected with an error similar to the following:

    {
  "message": "defaultDueDurationSeconds cannot be greater than defaultExpirationSeconds. defaultDueDurationSeconds: 7000, defaultExpirationSeconds: 8000",
  "code": "pre.check.value.greater.than",
  "status": 409,
  "messageWithParams": "{name1} cannot be greater than {name2}. {name1}: {value1}, {name2}: {value2}",
  "messageParams": {
    "name1": "defaultDueDurationSeconds",
    "name2": "defaultExpirationSeconds",
    "value1": "2026-02-06T00:00:00Z",
    "value2": "2026-02-05T00:00:00Z"
  }
}

    This validation is now removed. Requests will no longer fail when defaultDueDurationSeconds exceeds defaultExpirationSeconds, provided that defaultExpirationSeconds meets the following criteria:

    • Is at least 3600 seconds (one hour)

    No breaking changes are expected for existing integrations.

    Impacted Resources

    Create a worktype: POST /api/v2/taskmanagement/worktypes

    Update a worktype: PATCH /api/v2/taskmanagement/worktype/{worktypeId}

    Contacts

    @Padraic Rowley  

    Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.



Related Content