Migration

Secured Audit database (ElasticSearch)

there is now possibility to use secure connection between Jems and ElasticSearch, which is a storage used for audit log
if you do not need this option, there is no action needed and everything will work for you like before
we used this opportunity also to update to latest version of ES 7.17.9
in case you want to install it, you need to
- enable xpack.security.enabled: true and setting default password for elastic user by environment variable e.g. ELASTIC_PASSWORD=[your_password] when starting ElasticSearch
- Jems will use this user, but you need to inform him/her about your password by setting environment variable AUDIT_ELASTICSEARCH_PASSWOR=[your_password] or alternatively start with -Daudit-service.password=[your_password]
in case you use Docker - before proceeding with this make sure your volumes are explicitly specified
- if they are not specified, changes in configuration might result into creating new volumes and therefore causing loss of all your audits

MariaDB Upgraded

MariaDB was upgraded to 10.6.12 which will provide long term support until 2026

See MariaDB Release notes: https://mariadb.com/kb/en/mariadb-10-6-12-release-notes/
If you have MariaDB via our docker-composer file, make sure the flag MARIADB_AUTO_UPGRADE: 1 is active so that the upgrade is automatic (nothing to do).
In case you are using MariaDB as isolated system, you shall upgrade the system accordingly to 10.6.12 before Jems v7 starts for first time (see https://mariadb.com/kb/en/mysql_upgrade/).
Jems MariaDB-Java-connector was also updated to 3.1.2

Notifications

This release introduces the possibility of automatic notifications to e-mail. This requires the upload of the mail HTML template (notification.html) into MinIO (you can find it in the release package /resources). All provided HTML templates can be customized.

Rounding issues for Partner contribution in Partner reporting Financial overviews

Who is potentially affected?

You are only affected if your system has FTLS set to Ready for payment (in Contract monitoring section) and first partner reports by projects in status Submitted, please continue reading this section.

The issue may occur in two colums of Financial overview table in partner reports:

1. Rounding in connection with FTLS payments in column Previously reported

In rare events there may occur a rounding difference - maximum 0,01 EUR if there is 1 fund involved, 0,02 EUR in case of 2 funds etc. - in column Previously reported, rows Partner contribution and Total in Financial overview table of Partner level reports.

Such issue can occur in some cases if FTLS (Lump sums e.g. for preparation) have been paid.

2. Rounding of current partner report, partner contribution values

Further, in column Current report, row Partner contribution may show a rounding deviation as well.

How to fix:

The correct calculation of all columns in Financial overview is:
Total (from reports) - Funds (rounded down) = Partner contribution

In case a rounding deviation is identified for a project partner, please follow the steps below:

Step 1: In order to correct issue no. 1 in current and future partner reports, please reset FTLS according section 2 under “Migration” of Release notes v6.0.7. However, in already submitted partner reports, this issue will persist.

If this step is not undertaken, the difference will remain in Previously reported in all future partner reports. Project reports are not affected, these figures will be correct.

Step 2: To remove the issue no. 1 from existing draft reports, they need to be deleted first.

Step 3: In the last submitted report for a partner, which is also the last one created (after deletion of eventually later draft reports in Step 2), reopening and resubmission will fix the rounding difference in column Current report (issue no. 2 above). For any submitted reports created before the last one, the financial figures cannot be updated anymore (reopening is further restricted in this case).

Step 4: Deleted draft reports can be recreated and will have correct figures for Partner contribution in column Previously reported.

What if you do nothing:

If you do not redo FTLS (Step 1), the small deviations of Partner contribution in column Previously reported will persist for the project partners affected in all future reports. As for column Current report, the next following reports will always contain correct figures. Also future FTLS payments will be recorded correctly in Financial overviews.

Steps 2-4 can be undertaken to correct existing reports. Regardless of these steps, next reports created will contain correct figures.

We would like to know and eventually support you. Please inform Interact in case you encounter the above issues!

HIT Checklists

During Jems v7 starting, a total of 7 checklist from HIT will be generated and will appear in Programme Setup → Checklists. These checklists are meant to be renamed (and even customized accordingly). Alternatively, if your programme don’t find any usage from it, please delete them asap (before they are instantiated by some user).

Croatian partners

From January 2023 onwards Croatian partners have adopted the EUR. This impacts Jems, we have updated the currency in the database. Old submitted partner reports will stay with HRK currency and the correct exchange rate. Draft reports will not have any migration. Please ask partners with a HRK currency and a Draft report open to change their procurements and List of expenditure currency to EUR as HRK is no longer supported from January.

Intermediary versions of Jems

If your programme is installing versions of Jems which are not officially released (from repository), you might get into the problem of migration script being blocked (V202211250745_*.sql), in order to fix the issue you need to run the follow query:

CODE

UPDATE flyway_schema_history SET CHECKSUM = 404440929 WHERE VERSION = '202211250745'