7.10 - New system events, Reply-To,

New system events

Two system events are now implemented properly:

"Resubmission after technical check": after a technical check, the resubmission is now distinct from a normal submission! This presents several advantages when the author resubmits:
- the corresponding author will not get the usual acknowledgement of receipt
- likewise for co-authors
- and editors will not receive the same e-mail
"Peer review complete"
- this event trigger has been corrected and now works properly: the editor will get notifier when the last scheduled referee provides his report.

For this two events, no default template has been provided, we invite you to create your own. Concerning "Resubmission after technical check", default templates will be provided shortly.

System events: modify the Reply-To header!

In e-mail addressing, the Reply-To header is the address that should be used to reply to the message (different from the original sender). This mechanism can be used for this typical scenario:

Albert Einstein requests a revision from the system
The mail is sent with the following headers:
- From: nestor@edpsciences.org
- Reply-To: albert.einstein@eth.ch
the author replies to the message: Albert is the recipient (not the system), even though he is not the original sender

This mechanism has been extended to specific system events, with the possibility of using Reply-To --> the current editor. Specifically:

when the author gets an acknowledgement of receipt (replies to: current editor)
when the author is automatically reminded to revise (same)
when the referee gets an acknowledgement of invitation (same)
when the referee gets an acknowledgement of decline (same)
when the referee gets an acknowledgement of report (same)
when the referee is automaticallly cancelled (same)
when the referee is automatically reminded (same)

By default, ,none of these events have been configured to use the current editor, they are easy to set in the template config: