The STEP 2026.3 Update adopts the Java platform default locale data, based on the Unicode Common Locale Data Repository (CLDR), in place of the legacy COMPAT locale data provider previously set by default in JVM arguments. This change aligns STEP with current Java platform standards and prepares the system for a planned future move from Java 21 to Java 25, where COMPAT locale data provider is not supported.
Important: This change applies to all environments, not only those with customized java.locale.providers.
Up to STEP 2026.2, STEP’s default JVM configuration used the COMPAT locale data provider. With the STEP 2026.3 Update, the COMPAT default has been removed. Formatting for dates, times, and numbers may change if it relied on Java’s default locale patterns.
In STEP, some locales, formatted values that use the JVM's default locale patterns may differ, including values in STEPXML and other exports or integrations. Differences may include:
-
Separators and punctuation marks in dates and times (for example, periods, commas, and other separators)
-
Month abbreviations instead of numeric date patterns
-
Different decimal or grouping separators for numbers
Exact output depends on the locale(s) used by the environment, the export, or the integration. The most likely systems to be affected are those that parse formatted date / time or number strings from STEP (rather than using ISO / canonical formats).
Action steps before and after the update
-
Identify integrations, exports, and receiving systems that consume formatted dates, times, or numbers from STEP (especially STEPXML).
-
Compare sample output from a non-production environment on 2026.3 with current production output for the same locale and export.
-
Update parsers, mappings, or tests if the string format has changed
-
Change integrations to use stable / canonical formats where possible
Temporarily keep the COMPAT locale data provider behavior
Important: Stibo Systems recommends validating and updating integrations on 2026.3 while a temporary COMPAT locale data provider override is available.
If you need additional time to adapt receiving systems, submit a JVM argument change request in the Stibo Systems Service Portal for the affected environment to restore:
-Djava.locale.providers=COMPAT (or COMPAT,SPI)
Important: Legacy COMPAT locale data provider is not supported on Java 25. Retaining COMPAT only postpones adaptation since COMPAT will not be allowed after the planned Java 25 upgrade.