User role impact: EDITOR

This enhancement updates the user interface (UI) of Editor menus to be modern, usable, and accessible. Font size
and spacing have been increased to improve navigation and legibility. Accessibility has been improved with enhanced keyboard
navigability for existing and new functionality. These updates apply to all Editor menu tabs: Editorial, Proposal Menu,
Production Tasks, and Enterprise View. (Availability of tabs depends on publication configuration and RoleManager permissions.)

Editor Main Menu

In the main area of the menu, folder groups are organized into expandable and collapsible accordions. All sections can be
expanded or collapsed with the links at the top of the page. The expanded or collapsed states are saved for each user. Several
items have been relocated to the left sidebar for quick access and to reduce scrolling. Items on the sidebar can be expanded
or collapsed and retain the selected state for each user. These items (permission dependent) are search functions
(including saved searches), completed reviews grid (now an expandable list), reports, and administrative functions. Availability
of sections, folders, and sidebar items depends on existing RoleManager permissions. See images of new menu
structure on next two pages.

Improved Editor signposts

For publications using the Editor Signposts feature, color-coded status signposts that appear next to folders have been enhanced
to display a tooltip popup with the number of manuscripts in each status (on schedule, need attention, late) when a
user clicks the colored bar. The tooltip can be closed by clicking the X in the corner or clicking elsewhere on the page.
Status texts in the tooltip appear as links. Clicking a status link opens a filtered view of the folder to display only submissions
with that status. For example, clicking Late on the New Submissions signpost will display only the manuscripts in the New
Submission folder that qualify as Late (as defined by the publication on PolicyManager > General Policies > Configure
Warning Thresholds.). Editor roles must have existing RoleManager permission (View Warning Status Signposts).

Detail of enhanced Editor signposts: Clicking the color bar opens a tooltip popup that indicates the number of submissions with each status. Clicking status text link, the user to a filtered version of the folder showing only those submissions.

Detail of enhanced Editor signposts: Clicking the color bar opens a tooltip popup that indicates the number of submissions with each status. Clicking status text link, the user to a filtered version of the folder showing only those submissions.

User role impact: ALL

When an EM/PM system email is undeliverable, the recipient’s email client may send a bounce response. These bounce notifications are sent to the originator of an email sent from EM/PM. The publication code acronym and bounce type descriptions have been added to the notifications to provide additional information.

The bounce type and subtype are shown in the error description portion of the message. There are three bounce
types:

• Permanent: The email was not delivered, and the email address has been added to an inoperative email list. No
  further emails to this email address will be sent. The recipient’s email address should be corrected or removed. Permanent
  bounces fall into three subtypes:
  • General: The recipient’s provider sent a permanent bounce message.
  • NoEmail: It was not possible to retrieve the recipient’s email address from the bounce message. (This will be
    rare).
  • Suppressed: The recipient’s email address is on the Amazone SES suppression list, because it has a recent
    history of producing permanent bounces.
• Transient: The email was not delivered, or an auto-response was received, and a reason is indicated in the subtype.
  Future emails sent to this address will be attempted. This email address is not added to the inoperative email list.
  Transient bounces fall into five subtypes:
  • General: The recipient’s email provider sent a general bounce message. The publication may be able to send
    a message to the same recipient in the future if the issue that caused the message to bounce is resolved.
    Note: This type of notification may be triggered if the recipient has an active automatic response rule (such as
    an out-of-office message). Aries will be providing further information about out-of-office responses in a
    future release.
  • MailboxFull: The recipient’s email provider sent a bounce message because the recipient’s inbox was full. The
    publication may be able to send messages to the same recipient in the future when the mailbox is no longer
    full.
  • MessageTooLarge: The recipient’s email provider sent a bounce message because the message sent was too
    large. The publication may be able to resend the message to the same recipient if the message size is
    reduced, for example, by removing an attachment or reducing the size of an attachment.
  • ContentRejected: The recipient’s email provider sent a bounce message because the message sent contains
    content that the provider doesn’t allow. The publication may be able to resend the message to the same
    recipient if the content of the message is changed.
  • AttachmentRejected: The recipient’s email provider sent a bounce message because the message
    contained an unacceptable attachment. For example, some email providers may reject messages with
    attachments of a certain file type or messages with very large attachments. The publication may be able to
    resend the message to the same recipient if the attachment is removed or changed.
• Undetermined: The recipient’s email provider sent a bounce message. The bounce message didn’t contain
  enough information for Amazon SES to determine the reason for the bounce.

Example of a Transient bounce message format:

From: Email-FailureNotification@editorialmanager.com
Unable to deliver email
Original message Details:
Sender address: [The email address of sender of the email.]
Recipient address: [The email address of intended recipient of the email.]
Subject: [The subject line of the email that was sent to the recipient.]
Journal: [The Aries publication code acronym of the EM/PM site.]
Error: [The bounce type and subtype separated by a dash. Example: Transient – MessageTooLarge]

TO CONFIGURE:

No configuration is required.