V 14

This release focus on improving the security and longevity of Jems by updating the core framework of the system: SpringBoot 3.5.7.

Since there were critical changes in the system, it’s suggested to give a try in the test environment (with real data) before deployment in production.

Minor releases (inc. hotfixes):

V14.0.2 Fixed bugs:

Project Report - Partner Spending Table does not correctly update to 0,00 upon report resubmission [5019]
If all Certificates of one project partner were excluded from the project report, the amounts in column “Current report” were not correctly updated to 0,00 during re-submission of the project report. This also affected the column “Total reported so far”. Also in consecutive project reports, the amounts already excluded from the previous project report were shown in the column as “Previously Reported”.
For already submitted project reports with this bug, the amounts will not be updated by the fix. However, in any newly created project reports, the amounts in the column “Previously Reported” are correctly calculated.

Payment applications to EC: Project reports table sort/pagination broken [5039]
In the “Projects flagged Art. 94/95” tab: the “Project reports” table pagination/sorting function does not work and it was limited to only 25 items.

Expenditure verification table: LoE cannot be saved when items > 150 limit [5023]
While the limit for the List of Expenditure was increased from 150 to 250 cost items, changes in the “Expenditure verification” table of the Control report could not be saved, if there were more than 150 cost items.

The total % of co-financing is not always calculated the same in table D1 as in A3 of the Application form [5008]
Table D1 “Project budget per co-financing source (fund) - breakdown per partner” rounding issue was changed to same rounding down methodology as it is in table A3 of the Application form.

One click export on Project report “Expenditure verification” table with wrong cost item ID [5011]
The cost item ID’s were wrong for the items that were previously parked.

Accounts “Summary” tab: Refresh needed to see saved data [5017]
Browser refresh was required to see saved data in the “Summary” tab of the Accounts, despite data was being saved properly

Allow AF NUTS link to be translated [5005]
common.hint.nuts=Information about NUTS codes and how to identify your region:
common.url.nuts=https://ec.europa.eu/eurostat/web/nuts

Deliverable deactivation does not show in Project reports [5027]
Deactivation icon of a deactivated deliverable was not shown accordingly in project reports

Standard programme project report indicators data export - 1.0.7 sheet 3 and 4: Projects in modification or modification rejected not correctly exporting values [5043]
After starting a modification, no data (Output / Result target) was shown in the export
After rejecting a modification, no data (the whole row) was shown

Account activation not possible due to broken link [5040]
When 'register new account' successful leaded to a broken web page.

URL not found [5041]
Some users bookmarks stop working.

All plugins version changed to v2 [5044]
In order to easily identify the successfully load of plugins in major release in v14, we increased the major version of all plugins to v2 and kept the minor version details
As example: v1.1.3 → v2.1.3)

Increase size of Notification [5046]
Initial notification from system could take large size of text and could prevent boot of Jems.

Standard programme partner report data export fail in v14.0.1

New features:

SpringBoot 3.5.7
- Jems is now compatible up to Java 25. Nevertheless, we recommend Java 21.

Fixed bugs:

< V14 major release did not fix bug but see above v14 minor releases bug fixes>

Plugins:

Migration:

⚠️ Plugins

Due to Sprinboot update existing plugins developed by programmes might not be compatible!
Interact official plugins were updated accordingly (can be found in v14 release package)

In case your plugin is no longer compatible with Jems V14, please take as reference the follow guide that was used for Interact official plugins adaptation:

CODE

1. Update dependencies versions in the libs.versions.toml file:
  clf-platform-spring-version = "2.5.1-rc.2"
  clf-autoconfigure-gradle-version = "1.1.2"
  kotlin-reflect = "2.2.0"
  kotlinx-coroutines = "1.8.1"
  
  # Align JUnit Platform with Jupiter used by Spring Boot/Cloudflight BOM
  junit-platform = "1.11.4"

  #Also before the [plugins] (after kotlinx-coroutines) you need to add 
junit-platform-launcher = { module = "org.junit.platform:junit-platform-launcher", version.ref = "junit-platform" }

2. build.gradle at the end of the dependencies block:
  testRuntimeOnly libs.junit.platform.launcher

3. In the buildSrc/build.gradle we need to increase all 3 versions so that we have
  dependencies {
      implementation "org.jetbrains.kotlin:kotlin-gradle-plugin:2.2.0"
      implementation "org.jetbrains.kotlinx:kotlinx-serialization-json:1.7.1"
      implementation "io.gitlab.arturbosch.detekt:detekt-gradle-plugin:1.23.6"
  }

4. If TemplateEngineConfig is used, remove: it.addDialect(Java8TimeDialect())

5. Update the SpringTemplateEngine import to use spring6 instread:
  import org.thymeleaf.spring6.SpringTemplateEngine