V 13.0.3

This is the first release under the 2025 maintenance phase. It focuses on improving the stability of Jems by addressing numerous bug fixes.

This release introduces major technical upgrades—specifically, MariaDB v10.11 and MinIO 2025 which enhance both performance and security. Be careful updating MinIO, please follow highest standards and never do a migration without a proper backup plan.

There was a new version of the NACE codes released by the European Commission. Jems is therefore also updated. As usual, we do not actively change any codes, old codes remain valid (further information below).

New features:

• Dashboard: filter by Project [MP2-4976]

• Financial living tables: Separate column "Paid" into paid funds and contributions inserted in partner reports [MP2-4979]

• Application Form B1.1 Sector of Activity: Update to NACE 2.1 [MP2-4980]

• Public procurements: Show in what report the procurement was updated [MP2-4957]

• 1-click export on ‘payments/accounts’ section [MP2-4977]

• Limit for attachments in public procurements section is now 120 [MP2-4962]

Migration:

• MariaDB v10.11.1.1 [MP2-4960]

  • Directly via docker-compose file

• MinIO RELEASE.2025-04-22T22-12-26Z [MP2-4987]

  • [IMPORTANT] Update requires manual intervention, see official guide: MinIO Migration

    • It requires manual move of data from old MinIO to a new MinIO because of using different data structures.

• NACE 2.1 [MP2-4980]

  • This is a revision therefore majority of NACES codes are not expected to change.

  • Jems does not modify any of previously/existing partner NACE codes in the system.

  • Jems simply shows warning when existing partner NACE code is no longer found in NACE 2.1

    • In such warning scenario, the change of code should be done via AF modification

    • From Jems v13 onwards, user will only be allowed (drop-down) to select existing NACE 2.1 codes

  • The exceptions (possibly bugs from NACE) are: 20.51, 35.1X, 46.7 and 47.91

    • These codes exist in both versions but have distinct meaning!

• Translations (new and changed translations):

Plugins:

• Jems-plugin-contract v1.8.3

  • Support for new NACE codes [MP2-4980]

• Jems-standard-plugin v1.8.3

  • Job title missing in control export [MP2-4959]

Fixed bugs:

1. Corrections: flat rate helper [MP2-4958]

   • The “Office and administrative costs flat rate based on direct cost” is not correctly calculated by the helper for flat rate corrections.

2. Partner Spending Profile in Partner Report of SPF projects [MP2-4955]

   • The “Total reported so far” includes SPF cost from Project report while “Period target” and “Cumulative target” show only Management budget from the partner budget in the application form. Therefore, the values calculated in “Cumulative target - total reported so far” as well as “Total reported so far / cumulative target” make no sense.

3. Mails are not sent if single mail address in list is not valid [MP2-4956]

   • Notifications might send mail to multiple mail address and if one is not valid, no mail is sent at all.

4. Control report plugin - Job Title field is always empty in PDF [MP2-4959]

5. Corrections (project audit/control) - Not possible to download attached files [MP2-4961]

6. Wrong amount shown for Office and administrative costs flat rate based on direct costs in Partner budget details [MP2-4963]:
   For a Partner using the Office and administrative costs flat rate based on direct costs as the only flat rate (having Staff costs and Travel and accommodation costs as real costs), the amount shown in the Office and administrative costs table in the Partner budget details is wrong. After the first refresh of the page, the amount calculated in the Office and administrative costs table does not take into consideration the Travel and accommodation costs as a basis. The partner budget overview table on the same page still shows the correct amount for Office and administrative costs and also all other budget tables in the application form show the correct amount. So far, no impact on any other section of the system could be noticed.

7. Financial Living table 1 shows wrong amounts in Total deducted by JS/MA and Total parked by JS/MA [MP2-4964]:
   In a project with at least two partners, where certificates of both partners are included in a Project report and Partner one has no parked item and no deductions in the JS/MA verification section and Partner two has one parked item and one MA deduction in the JS/MA verification section, the Financial Living Table 1 of the Partner one shows wrong amounts in the columns Total deducted by JS/MA and Total parked by JS/MA. Also the Project Financial Living Table 1 shows wrong amounts in those two columns. The bug also applies to a project with more than two partners.

8. Programme level ‘List of Expenditure’ (plugin)- The export will always show the last two columns empty (Corrections & Payment to EC) [MP2-4966].

9. MariaDB v10.6.x minor updates are not possible to install [MP2-4967].

10. Dashboard ‘My project reports': Last PR is hidden when status=’re-opened' [MP2-4968]

11. Partner Report financial overview table "Partner Expenditure - breakdown per investment (in Euro)" does not update correctly [MP2-4972]:
    When you have a Partner report in status “Certified” and you reopen the control work and you reopen the Partner report and remove the link to investment(s) from the cost items in the list of expenditures, the table "Partner Expenditure - breakdown per investment (in Euro)" does not update correctly and still shows the amounts under “Current report”. Also in consecutive partner reports, the amounts will be shown under “Previously reported”, even though those costs are no longer linked to the investment.

12. No audit log when a checklist template is changed (on programme-checklists) [MP2-4973]

13. In a reopened correction, the three toggles in section 2 can only be edited after the page has been refreshed [MP2-4974]
    The three toggles

    1. “This correction is related to a clerical/technical mistake OR related to expenditure not yet included in a payment application to EC (see section 4 below)”

    2. “This correction is related to gold plating”

    3. “This correction is related to cases of suspected fraud”
       cannot be changed between “Yes” and “No” in a reopened correction until the page is refreshed.

14. In the Partner financial living tables - breakdown per cost category, the column “Remaining budget” is wrongly calculated for cost categories where no costs were reported yet. [MP2-4988]

15. Rounding of co-financing amount in AF partner section [MP2-5006]
    This is a frontend issue, where, in rare occasions, the co-financing amount is rounded down by an additional Cent in the tab “Co-financing” in the partner section of the Application form. In any other place the value is used correctly since it is correctly stored in the database.