There are two ways to get a summary of paper-related information, via Papers:List and Papers:Export . To reduce confusion, you can now also export whatever appears in the listing, by indicating Excel or CSV (comma-separated values) format on the listing page. Eventually, the separate export functionality will likely go away.

When you send email via " People:Email ", duplicates are now removed, so that each recipient only gets one copy. The function tries to be smart about recognizing if the same person gets the same message. For example, if the template contains the variable {papertitle} , authors will get one message for each paper; if it does not, they will get one message for all their papers.

In some conferences, tracks are all the same except for the page limits. (For example, some conferences have demo paper and short paper tracks.) To facilitate maintaining such tracks, the configuration options for page limits, both for review and final manuscripts, have been moved to a separate forms page. That way, you can update all tracks, without having to re-edit the page limits.

You can now insert page breaks before selected sessions, by editing the session configuration (see " Conference:Sessions "). The page break will only show up in the printed version, e.g., using the brochure or print output options.

The internal handling for templates for email and web pages has been changed. This makes it possible to define custom subject lines for each conference, as well as to have more control over what messages get copied to whom. For example, track chairs, web masters and publication chairs can now be copied easily on selected messages. The only user-visible change is that the configuration for setting up cc's for templates has moved to the template definition, rather than the conference email configuration.

Conferences often use EDAS to generate PDF visa letters for authors, confirming the acceptance of a paper. Until now, these visa letters had to be in a small subset of HTML. We have added the ability to use Wiki mark-up, i.e., plain text with a few symbols to denote basic formatting. For example, in Wiki mark-up, bold is indicated by a double-underscore, as in __ bold __, and italics by a two pairs of single quotes, as in '' italic ''. The system automatically detects whether a conference uses HTML or Wiki format. Wiki markup works best for letters with minimal formatting, while HTML markup is better suited for letters where you want to place multiple logos or have more fine-grained control over positioning of elements. Chairs should read the documentation for more details.

If you are using a registration system outside of EDAS, you can now limit the number of papers that can be associated with one registration code. The limit is defined in the track configuration.