Potential issue with reopening of parked items in a partner report stemming from Jems V7
In case
control has been started
and an item has been parked,
and the related partner report has been reopened in Jems V7,
the amounts of total eligible after control are incorrect.
In V8, new partner reports will show correct figures. To correct old reports, the partner report(s) concerned need to be reopened and resubmitted.
lf reopening is not possible anymore, or in any case of doubt, please contact the Jems team via the helpdesk https://jems-eu.atlassian.net/servicedesk/customer/portal/1 !
Payment filtering
To be able to filter inside list of payments, we needed to perform migration of current payments to more proper model. This has only 1 drawback, which is - that project acronyms, which have been changed during a modification might not be up-to-date anymore (only inside payment tables).
Reasoning behind is that filtering can’t be performed on historical data
So only in case there is a payment already made, and linked to project, and this project changed its acronym after this payment has been made, after this migration acronym shown in this payment will be the new one, instead of the old one.
The old acronym is not lost, you can still find it inside application form when changing version to proper old version, and if needed, it can be fixed manually. This is only related to payments, and only to this acronym field, all other fields (especially connected to project) like project identifier will be migrated properly (as those cannot be changed during modifications)
Plugins
New plugin contract were issued, by means Jems V8 introduced more data accessible to plugins - Update Jems standard plugin accordingly (v1.3.6 - included in Jems V8 package)
Note: You can opt to still use your existing plugins, but new functionalities added in V8 will not be accessible.
New translation Keys
System_en - Translation keys introduced in V8
file.table.no.documents.generated=There are no documents generated.
#user partner reports
user.partner.reports=My partner reports
user.partner.reports.info=This section lists all partner reports of partner/projects you are assigned to.
user.partner.reports.table.column.name.project.id=Project ID
user.partner.reports.table.column.name.partner.role=Partner role
user.partner.reports.table.column.name.partner.name=Partner name
user.partner.reports.table.column.name.partner.report.number=Partner report ID
user.partner.reports.table.column.name.status=Status
user.partner.reports.table.column.name.af.linked.version=AF version linked
user.partner.reports.table.column.name.reporting.period=Reporting period
user.partner.reports.table.column.name.creation.date=Report creation
user.partner.reports.table.column.name.first.submission.date=First submission
user.partner.reports.table.column.name.last.submission.date=Last submission
user.partner.reports.table.column.name.amount.submitted=Amount submitted
user.partner.reports.table.column.name.control.end.date=Control end date
user.partner.reports.table.column.name.total.eligible.after.control=Total eligible after control
#user agent
user.agent.info.1=Your browser does not fulfill the minimum requirements of Jems. Some functionality may not work as expected.
user.agent.info.2=Please switch to an officially supported browser:
user.agent.supported.1=Chrome version 85 or higher
user.agent.supported.1.link=https://www.google.com/chrome
user.agent.supported.2=Firefox version 82 or higher
user.agent.supported.2.link=https://www.mozilla.org
user.agent.supported.3=Edge version 84 or higher
user.agent.supported.3.link=https://www.microsoft.com/edge
programme.data.field.technical.assistance.flatrate=Technical assistance flat rate
programme.translation.management.system.description=System translation file covers all sections outside of projects.
programme.translation.management.application.translations=Project translations
programme.translation.management.application.description=The application translation file covers all texts related to a project, including application form, contracting and reporting.
programme.checklists.type.VERIFICATION=Verification
payments.payment.to.project.table.column.payment.type.FTLS=FTLS
payments.payment.to.project.table.column.payment.type.REGULAR=Regular
payments.payment.to.project.table.column.payment.type.both=Both
payments.payment.to.project.table.column.payment.project.report.id.abbreviation=PR.{{id}}
payments.payment.to.project.table.column.payment.claim.submission.date.info=FTLS: payment claim submission date is the date when project was set as contracted in Jems.\n REGULAR: Project report first submission date
payments.payment.to.project.table.column.payment.claim.submission.date.filter.from=Submission from
payments.payment.to.project.table.column.payment.claim.submission.date.filter.to=Submission to
payments.payment.to.project.table.column.payment.claim.approval.date.info=For FTLS this is the date when it was (last) set as Ready for Payment in Contracting \u2013 contract monitoring.\n For Regular, date when Project report verification is finalised (when status changes to Verified)
payments.payment.to.project.table.column.payment.claim.approval.date.filter.from=MA Approval from
payments.payment.to.project.table.column.payment.claim.approval.date.filter.to=MA Approval to
payments.payment.to.project.table.column.total.eligible.amount.info=FTLS total eligible amount approved is the total cost approved by the programme for this specific FTLS.For regular payments this is the total project report amount after verification.
payments.payment.to.project.table.column.authorised=Authorised
payments.payment.to.project.table.column.last.payment.date.filter.from=Date of (last) payment from
payments.payment.to.project.table.column.last.payment.date.filter.to=Date of (last) payment to
payment.detail.table.partner.report.number.abbreviation=R.{{number}}
payments.detail.table.column.payment.partner.report.number.abbreviation=R.{{number}}
call.reporting.contributions.title=Partner reporting Contributions received follow-up
call.reporting.contributions.info=Allow partners to add new contribution sources received directly in the partner report Contributions tab without doing a project modification to adjust the co-financing
only be selected for notifications triggered after the status Approval.
call.detail.notifications.config.tab.project.notification.id.ProjectSubmittedStep1=Step 1 Submitted
call.detail.notifications.config.tab.project.notification.id.ProjectSubmittedStep1.info=This trigger event relates to the step 1 submission of the Application Form during the step 1 phase of the call
call.detail.notifications.config.tab.project.notification.id.ProjectSubmitted=Submitted
call.detail.notifications.config.tab.project.notification.id.ProjectSubmitted.info=This trigger event relates to initial submission of the Application Form (e.g. submission due to modifications does not trigger this event)
call.detail.notifications.config.tab.project.notification.id.ProjectApprovedStep1=Step 1 Approved
call.detail.notifications.config.tab.project.notification.id.ProjectApprovedStep1.info=This trigger event relates to the project decision approval during the step 1 phase of the call
call.detail.notifications.config.tab.project.notification.id.ProjectApprovedWithConditionsStep1=Step 1 Approved with conditions
call.detail.notifications.config.tab.project.notification.id.ProjectApprovedWithConditionsStep1.info=This trigger event relates to the project decision approval with conditions during the step 1 phase of the call
call.detail.notifications.config.tab.project.notification.id.ProjectIneligibleStep1=Step 1 Ineligible
call.detail.notifications.config.tab.project.notification.id.ProjectIneligibleStep1.info=This trigger event relates to setting the project decision ineligible during the step 1 phase of the call
call.detail.notifications.config.tab.project.notification.id.ProjectNotApprovedStep1=Step 1 Not approved
call.detail.notifications.config.tab.project.notification.id.ProjectNotApprovedStep1.info=This trigger event relates to the project decision Not Approved during the step 1 phase of the call
call.detail.notifications.config.tab.project.notification.id.ProjectApproved=Approved
call.detail.notifications.config.tab.project.notification.id.ProjectApproved.info=This trigger event relates to the project approval decision (e.g. approval due to modifications does not trigger this event)
call.detail.notifications.config.tab.project.notification.id.ProjectApprovedWithConditions=Approved with conditions
call.detail.notifications.config.tab.project.notification.id.ProjectApprovedWithConditions.info=This trigger event relates to the project approval with conditions decision
call.detail.notifications.config.tab.project.notification.id.ProjectIneligible=Ineligible
call.detail.notifications.config.tab.project.notification.id.ProjectIneligible.info=This trigger event relates to setting the project decision ineligible
call.detail.notifications.config.tab.project.notification.id.ProjectNotApproved=Not approved
call.detail.notifications.config.tab.project.notification.id.ProjectNotApproved.info=This trigger event relates to the project decision Not-Approved (e.g. rejection during a project modifications does not trigger this event)
call.detail.notifications.config.tab.project.notification.id.ProjectReturnedToApplicant=Returned to applicant
call.detail.notifications.config.tab.project.notification.id.ProjectReturnedToApplicant.info=This trigger event relates to the project action hand-back during project assessment
call.detail.notifications.config.tab.project.notification.id.ProjectResubmitted=Re-submitted
call.detail.notifications.config.tab.project.notification.id.ProjectResubmitted.info=This trigger event relates to the action of re-submitted by the applicant after the project has been handed back during project assessment (e.g. re-submission after the decision Project Approved with conditions does not trigger this event)
call.detail.notifications.config.tab.project.notification.id.ProjectReturnedForConditions=Returned for conditions
call.detail.notifications.config.tab.project.notification.id.ProjectReturnedForConditions.info=This trigger event relates to the action of hand-back after the project has been Approved with conditions (e.g. hand-back in any other status does not trigger this event)
call.detail.notifications.config.tab.project.notification.id.ProjectConditionsSubmitted=Conditions submitted
call.detail.notifications.config.tab.project.notification.id.ProjectConditionsSubmitted.info=This trigger event relates to the action of re-submission after the project has been Returned for conditions (e.g. re-submission in any other status does not trigger this event)
call.detail.notifications.config.tab.project.notification.id.ProjectContracted=Contracted
call.detail.notifications.config.tab.project.notification.id.ProjectContracted.info=This trigger event relates to the action when the project has been set to Contracted
call.detail.notifications.config.tab.project.notification.id.ProjectInModification=In modification
call.detail.notifications.config.tab.project.notification.id.ProjectInModification.info=This trigger event relates to the action of Opening a project for changes to the Application form both before and after setting the project to contracted (e.g. this event is not triggered for project changes before Approval)
call.detail.notifications.config.tab.project.notification.id.ProjectModificationSubmitted=Modification submitted
call.detail.notifications.config.tab.project.notification.id.ProjectModificationSubmitted.info=This trigger event relates to the action of submitting a project after changes to the Application form were made both before and after setting the project to contracted (e.g. this event is not triggered for project changes before Approval)
call.detail.notifications.config.tab.project.notification.id.ProjectModificationApproved=Modification approved
call.detail.notifications.config.tab.project.notification.id.ProjectModificationApproved.info=This trigger event relates to the action of Approving a project modification both before and after setting the project to contracted
call.detail.notifications.config.tab.project.notification.id.ProjectModificationRejected=Modification rejected
call.detail.notifications.config.tab.project.notification.id.ProjectModificationRejected.info=This trigger event relates to the action of Rejecting a project modification both before and after setting the project to contracted
call.detail.notifications.config.tab.project.notification.id.SharedFolderFileUpload=Shared folder upload
call.detail.notifications.config.tab.project.notification.id.SharedFolderFileUpload.info=This file trigger event relates to the action of uploading file to shared folder section of project
call.detail.notifications.config.tab.project.notification.id.SharedFolderFileDelete=Shared folder deletion
call.detail.notifications.config.tab.project.notification.id.SharedFolderFileDelete.info=This file trigger event relates to the action of deleting file from shared folder section of project
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationOngoing=Verification ongoing
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationOngoing.info=Triggered anytime a programme user starts the verification work
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationDoneNotificationSent=Verification done by JS
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationDoneNotificationSent.info=Triggered manually in Project report verification every time button "Notify verification by JS is done" is pressed
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationFinalized=Verification finalised
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationFinalized.info=Triggered anytime a programme user finalises the verification work
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationFileUpload=Verification communication upload
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationFileUpload.info=Triggered every time a user uploads in Verification Communication
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationFileDelete=Verification communication deletion
call.detail.notifications.config.tab.project.report.status.ProjectReportVerificationFileDelete.info=Triggered every time a user deletes from Verification Communication
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportSubmitted=Submitted
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportSubmitted.info=Triggered anytime a partner user submits a partner report
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportReOpen=Reopened
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportReOpen.info=Triggered anytime a partner report is reopened (from status submitted or control work ongoing)
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportControlOngoing=Control ongoing
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportControlOngoing.info=Triggered anytime a controller user starts the control work
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportCertified=Certified
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportCertified.info=Triggered anytime a partner report is certified
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportReOpenCertified=Control Reopened
call.detail.notifications.config.tab.partner.report.notification.id.PartnerReportReOpenCertified.info=Triggered anytime a control report is reopened
call.detail.notifications.config.tab.partner.report.notification.id.ControlCommunicationFileUpload=Control comm upload
call.detail.notifications.config.tab.partner.report.notification.id.ControlCommunicationFileUpload.info=Triggered anytime a file uploaded to control communication section
call.detail.notifications.config.tab.partner.report.notification.id.ControlCommunicationFileDelete=Control comm delete
call.detail.notifications.config.tab.partner.report.notification.id.ControlCommunicationFileDelete.info=Triggered anytime a file deleted from control communication section
call.detail.notifications.config.placeholder.FILE_USERNAME=[fileUsername] - Username of who triggered the action, upload/deletion of a file e.g. jose@jems.eu [Only events involving files]
call.detail.notifications.config.placeholder.FILE_NAME=[fileName] - Name of the file that was uploaded/deleted e.g. test.pdf [Only events involving files]
call.detail.notifications.config.placeholder.USERNAME=[userName] - User triggering the action - e.g. pieter.louwers@interact-eu.net
permission.create.project.reporting=User can edit reports depending on the project privileges.
permission.top.bar.partner.reports=Dashboard section only appears when partner reports exist. Monitoring users need also VIEW/EDIT reporting privileges.
permission.inspect.contracting.partner.section.applicant=Partners can always edit their own partner page if they have project privilege edit.
permission.inspect.reporting.project.verify=User can verify project report
permission.inspect.reporting.project.finalize=User can finalise project report verification. Works only in combination with Edit of Project report verification
permission.inspect.reporting.project.create=User can create new project report depending on the project privileges.
