Feature Release 6.12.0

Public Notification Emails

This release contains the ability for the public to enter their email address to receive notifications of published agendas.  Each email will contain a link to quickly access the agenda as well as the ability to click a link to remove their email address from being notified. 

The notifications will go out automatically when using "File" => "Publish Agenda".  If you manually change the status of your meeting via meeting properties it will not trigger the notification email.

Registering is super easy to do. When viewing the "Agendas" section of the public portal there is a text field at the top of the page with a button where anyone can put their email address in.  Behind the scenes we are verifying email address to check risk of emails being used and anything deemed to be a risky or a catch all email won't be allowed to register.  This is done in order to prevent spam flags.

Meetings

You can now specify a term for the meeting type on every scheduled meeting without having to create separate boards for all of them.  To specify a type simply open the meeting.  Click "Edit" => "Meeting Properties" and you will see the "Meeting Type" text field.

You can type whatever you wish in this field.  The wording you use here will be used throughout the app and public portal.

When you schedule a new meeting it will automatically use the name of the board by default to start out with.

We also changed the wording from Board to Meeting Type on the tables and filters

Video

• Added video player support when incorporating your archive of videos that don't have any metadata (chapter info) associated them
• We now support multiple live streams at the same time so if you are running meetings in more than one room at a time each room can utilize it's own live stream

Bug fixes

• If a meeting was told to "Force Adjourn" and the web page was left open, the socket was staying connected to the server and could potentially send another force adjourn due to how the logic was handling reconnects on the open socket.  We have updated the code to close that socket and destroy it once a meeting is told to force adjourn removing the potential for this happening.