Release Notes

v5.26.13 on the GitHub

Improvements

Rule Services:

  • New Rule Services UI.
  • Serialization of Decimal Numbers to Non-Scientific Notation in REST Responses.
  • Integrated Accept-Language header support in OpenAPI schema.
  • Support OpenL projects without Excel files inside
  • Optimized logging to capture only OpenL method arguments and result objects, reducing the verbosity of logs.

WebStudio:

  • OpenL Logo and Icons redesign.

Demo:

  • Java Security Manager usage in the DEMO is dropped.

Fixed Bugs

Repository:

  • Git Large File Storage (LFS) issues with Microsoft Azure Repositories.
  • Git Large File Storage (LFS) issues with Bitbucket Repositories.

Webstudio:

  • Unresponsive user interface issue triggered by text searches using quotation marks.

Rule Services:

  • JDBC Connections is not closed properly if exception is happening during persist operation.

Core:

  • Parsing issues with the dates with the invalid characters.

Fixes Vulnerabilities:

  • CVE-2023-34054 - Reactor Netty HTTP
  • CVE-2023-34062 - Reactor Netty HTTP
  • CVE-2022-1471 - SnakeYAML

Updated Libraries

  • Spring Framework 5.3.31
  • Spring Boot 2.7.18
  • Netty 4.1.101.Final
  • Reactor Netty HTTP 1.1.13
  • Log4J 2.22.0
  • Slf4J 2.0.9
  • Jetty 10.0.18
  • AWS SDK 1.12.604
  • Azure BLOB SDK 12.25.0
  • MSSQL JDBC 12.4.2.jre11
  • JGit 6.8.0.202311291450-openl
  • HikariCP 5.1.0
  • Mockito 5.8.0
  • Testcontainers 1.19.3
  • GreenMail 1.6.15
  • Commons Compress 1.25.0
  • Commons IO 2.15.1
  • Commons Lang3 3.14.0
  • Bouncycastle 1.77
  • Groovy 4.0.16
  • POI 5.2.5
  • Jackson 2.16.0
  • Swagger Core 2.2.19
  • Swagger Parser 2.1.19
  • SnakeYAML 2.2
  • Kotlin StdLib 1.9.21
  • Okhttp 4.12.0
  • Swagger UI 5.10.3
  • Spring Security 5.8.8
  • Guava 32.1.3-jre
  • XMLSec 2.3.4

Migration Notes

  • Now, OpenL Rule Services will output Double and Float type numbers in a more readable format. Instead of displaying numbers like "3.1415E-5", it will show them as "0.0000031415.
  • The date parsing functionality has been enhanced for greater accuracy. Previously, erroneous components within a date input were disregarded. In contrast, the updated system now generates an error. See the examples below
    Text Actual in UTC Expected in UTC Expected in UTC+3
    10/20/20 17 20 October 2020 00:00:00.000 Error Error
    10/20/2017 18:00 20 October 2017 00:00:00.000 20 October 2017 18:00:00.000 20 October 2017 18:00:00.000
    10/20/2017 09:00 20 October 2017 09:00:00.000 the same the same
    10/20/2017, 10/20/2018 the first date is parsed only an array of dates an array of dates
    2017-10-20T09:00:00 20 October 2017 09:00:00.000 the same the same
    2017-10-20T09:00:00.9876 20 October 2017 09:00:00.000 20 October 2017 09:00:00.987 20 October 2017 09:00:00.987
    2017-10-20T09:00:00.9876Z 20 October 2017 09:00:00.000 20 October 2017 09:00:00.987 20 October 2017 12:00:00.987
    2017-10-20T09:00:00Z 20 October 2017 09:00:00.000 20 October 2017 09:00:00.000 20 October 2017 12:00:00.000
    2017-10-20T09:00:00GMT+3 20 October 2017 09:00:00.000 20 October 2017 06:00:00.000 20 October 2017 09:00:00.000
    2017-10-20T09:00:00+03:30 20 October 2017 06:00:00.000 20 October 2017 05:30:00.000 20 October 2017 08:30:00.000
    2017-10-20T09:00:12.1212+03 20 October 2017 09:00:12.000 20 October 2017 06:00:12.121 20 October 2017 09:00:12.121
    2007-04-05T24:00 5 April 2007 00:00:00.000 6 April 2007 00:00:00.000 6 April 2007 00:00:00.000

  • © Copyright OpenL Tablets, 2004-2024