Skip to content

Use the engine clock when converting periods and durations to dates - #4316

Open
filiphr wants to merge 1 commit into
flowable:mainfrom
filiphr:stabilize-call-activity-type-conversion-test
Open

filiphr wants to merge 1 commit into
flowable:mainfrom
filiphr:stabilize-call-activity-type-conversion-test

Conversation

@filiphr

@filiphr filiphr commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

The DefaultVariableValueConversionHandler used the system clock when converting ISO 8601 periods and durations (e.g. P10D) to a date or local date. It now uses the clock of the engine configuration, in the same way as the business calendars, so the conversions respect a configured clock.

The type conversion tests now use a fixed clock and assert the exact values. This also makes CallActivityTypeConversionTest stable around DST changes: a period is added in calendar days, so it is not always a multiple of 24 hours when the next days cross a DST change.

Check List:

  • Unit tests: YES
  • Documentation: NA

The DefaultVariableValueConversionHandler used the system clock when converting ISO 8601 periods and
durations (e.g. P10D) to a date or local date. It now uses the clock of the engine configuration, in
the same way as the business calendars, so the conversions respect a configured clock. The type
conversion tests now use a fixed clock and assert the exact values, which also makes
CallActivityTypeConversionTest stable around DST changes.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant