Skip to main content
Skip table of contents

Release notes V 10.0.6

This version fixes following issues:

1. Deductions are ignored after double-reopening

Given the following circumstances:

  • If the last project report submitted to JS is reopened (full reopening), and

  • a partner certificate included is taken out of the reopened project report and

  • if this certified partner report is reopened back to controller and

  • a) the controller enters (additional) deductions in Expenditure list, or
    b) the controller parks an item with a MA/JS deduction

then, after re-submission of the partner report and its re-inclusion in a project report and submission for MA/JS verification, amounts of the new control deductions are ignored in the project verified amounts  (in Expenditure verification and Financial overviews), if the expenditure item concerned  is never saved in MA/JS Expenditure Verification tab.

The fix will ensure that

a) when a controller enters (additional) deductions in the Expenditure list, the amounts of the new control deductions are taken into account in the project verified amounts

b) the controller cannot park an item with a MA/JS deduction (toggle is blocked)

c) the controller cannot park an item parked by MA/JS in the Expenditure Verification tab (toggle is blocked)

The issue won’t occur in future cases anymore, however, past cases (before hotifx installation) need to be identified and repaired manually as follows:

a) change of deducted amount: After reopening 2 steps back for controller deductions as described above, make sure to save the page Expenditure verification at least once during MA/JS verification in order to update the amounts correctly. Any input in the expenditure item concerned, being it a Comment or even writing 0,00 in Deduction field will make sure the correct amounts are written to the database. Just make sure the "Save" button is clicked and the page is successfully saved.

b) parking of an item with a deduction:

  1. reopen the project report

  2. exclude the partner report with the parked item concerned

NOTE: with the next step, verification work will be reset for this particular partner report, so please make sure to backup related MA/JS verification work before proceeding to the next step!

  1. submit the project report

  2. reopen the project report again

  3. include the partner report with the parked item concerned and

  4. submit the project report again.

2. Closure tab is not available in Final Project report if English is not a system language

Only in case the programme system languages do not include English, the Closure tab in a Final Project report is not displayed correctly. The fix will ensure correct behaviour also for already created Final Project reports.

3. User assigned to a project cannot access it without privilege to view Contracting

For Jems Versions 10.0.0, 10.0.3 and 10.0.4, a user who is assigned to a project via Applications Assignment tab and has privilege for Contracting/Project Reporting Schedule set to “hide” in System Privileges cannot access project overview page, which means there is no way to access the project via the user interface. This constellation could apply for example in case of an Assessor role. The fix will ensure that the privilege for Contracting/Project Reporting Schedule has no influence on the access to the project overview page.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.