Welcome, Guest Login
Higher Logic User Group Site Higher Logic User Group Site Higher Logic Support Center

Support and Documentation

Community Email: Discussions & Consolidated Digests

Last Updated: Jan 12, 2016 02:27PM EST
Community content is delivered in email through four specialized templates.  Discussions, the primary "conversation" of a community offers two notification options, real time and daily digest, each with its own template.  All community content can be delivered on a daily or weekly basis through daily and weekly consolidated digests.  These templates have points of configuration for both display and functionality. 

Discussions Templates

Template-based discussion email intend to inform users of recent posts and allow immediate reply. They are a critical engine for engagement on the Higher Logic platform.  Replies within the native email client (such as Outlook or Gmail) and browser-based reply (through reply links/buttons in email which open the reply webpage) generate additional posts in the discussion thread.  Reply posts from the native email client with attachments can generate library entries in the same way as browser-based discussion attachments, but with additional options and points of configuration.  Discussion templates allow configuration checking by email fields below the configuration areas.

The primary configuration page for discussions templates are in the Admin site under Communities>Digest Configuration>Discussion Template. Note that several other pages impact the experiences provided by discussions email.  Allowing users to post via their native email client is established on the Mail Processing Rules page found under Communities>Discussions>Setup>Mail Processing Rules. Changes to the discussions templates should be consistent with other points of discussions configuration under Communities>Discussions>Setup. 

Settings across Discussions Templates

A number of settings are "common" across both discussion templates. 
 
Auto-login
This feature assumes the logged-in state for the user when links to open web content are used. Setting this to "on" does allow recipients of forwarded email to assume the identity of the original recipient. Reply-by-email functionality achieves the goal of immediate posting without posing the risk of passing login credentials.
Logo
This logo area overrides the main-site logo as the source of the primary graphical element of the discussion templates. This can be overridden further for communities with a website on the microsite's content management system admin environment.  An input on the discussion logo area on the Site Setup>Images page for any community microsite will be the final determinant of the logo used in discussion email.
Header
Text to display in the header area of the email is configured here. 
Custom links
Custom links allow links to any webpage to be included in all discussion email.  Popular choices are links to renew membership and links to the main website for an event. 

Real Time Template

Users who set their community notifications to "real-time" will receive an email for each discussion post. These messages utilize the colors, styles and logo configured for the main site, community website, or otherwise configured as described below. 

The following points of configuration can be applied to the real-time discussion email for all community discussions:
  • Logo image location and alignment
  • Advertisement location and alignment
  • Top links
    • Button to post a new message online - via the browser - can be enabled/disabled and display text changed.  
    • Button to post a new message via email - via the native email client such as Outlook or gMail - can be enabled/disabled and display text changed. 
  • Message Buttons - buttons that appear with the post to allow further interaction can be set on or off
    • Reply to Group Online - a button to post a new message online - via the browser - can be enabled/disabled and display text changed.  
    • Reply to Group via Email - a button to post a new message via email - via the native email client such as Outlook or gMail - can be enabled/disabled and display text changed. 
    • Reply to Sender Online - a post just to the sender drafted in the browser.  The button text is also configurable.
    • Reply to Sender via Email- a post just to the sender drafted in the native email client.  The button text is also configurable.
  • Message Content - previous post content can be included or not included in the post
  • Message Links - a button set presenting multiple interaction opportunities can be turned off and position and text configured. 
    • Reply to Group Online
    • Reply to Group via Email
    • Reply to Sender Online
    • Reply to Sender via Email
    • View Thread
    • Recommend
    • Forward
    • Flag as Inappropriate (only shows where self-moderation is established)
    • Post New Message Online
    • Post New Message via Emailk
  • Footer: configurable plain text and HTML footer fields are also presented.

Daily Digest Template

Users who set their community notifications to "daily digest" will receive a single email every day for each community when one or more discussion posts are made. These messages utilize the colors, styles and logo configured for the main site, community website, or otherwise configured as described below. 

The following points of configuration can be applied to the real-time discussion email for all community discussions:
  • Logo image location and alignment
  • Advertisement location and alignment
  • Top links
    • Button to post a new message online - via the browser - can be enabled/disabled and display text changed.  
    • Button to post a new message via email - via the native email client such as Outlook or gMail - can be enabled/disabled and display text changed.
  • Navigation - daily digests have a distinct navigation area to ease following a thread within the email.  These links to access next and past messages in the thread can be
  • Message Buttons - buttons that appear with the post to allow further interaction can be set on or off
    • Reply to Group Online - a button to post a new message online - via the browser - can be enabled/disabled and display text changed.  
    • Reply to Group via Email - a button to post a new message via email - via the native email client such as Outlook or gMail - can be enabled/disabled and display text changed. 
    • Reply to Sender Online - a post just to the sender drafted in the browser.  The button text is also configurable.
    • Reply to Sender via Email- a post just to the sender drafted in the native email client.  The button text is also configurable.
  • Message Content - previous post content can be included or not included in the post
  • Message Links - a button set presenting multiple interaction opportunities can be turned off and position and text configured. 
    • Reply to Group Online
    • Reply to Group via Email
    • Reply to Sender Online
    • Reply to Sender via Email
    • View Thread
    • Recommend
    • Forward
    • Flag as Inappropriate (only shows where self-moderation is established)
    • Post New Message Online
    • Post New Message via Emailk
  • Footer: configurable plain text and HTML footer fields are also presented.

The time and format of daily digest emails is configurable for each community on another page of the Admin site.  Configure aspects of daily digest delivery on the Communities>Discussions>Send Digest page.

Consolidated Digests

More than just discussions, all community content across all communities to which the user belongs is included in consolidated digests. These include community discussion posts, library entries, blogs, announcements and events. Consolidated digests are informational, featuring titles of included items with a preview of discussion bodies and links to the full content on the website.

Core features of discussion email are not included in consolidated digests. Discussion posts are previewed, but many longer posts are not included in their entirety.  Further, discussion posts cannot be replied to directly from consolidated digests. For these reasons, consolidated digests may not be recommended as the default notification for members. 



Consolidated Digests must be enabled by Admins (as described below).  When on, users will see the option to establish their personal consolidated digest(s) via their Profiles on the Community Notifications page.  After a user opts-in to receiving a consolidated digest they will determine which communities are included in the digest.  Users can include any community to which the user is a member.  A user need not include every community in the digest.

Consolidated digests are sent per the time configured for digest delivery on the Admin site Digest Content page found under Communities.  The day of weekly consolidated digest sending is determined by the user when enabling the digest from their profile.

Daily and weekly consolidated digests are configured in the Admin site on the pages under Communities>Digest Configuration>Consolidated Digests page.  The following configuration areas are found on that page:
 
Enable/Disable
Consolidated Digests must be enabled to be be utilized by users.  When enabled users will see the options on the Community Notifications area of the profile. 
Consolidated Digest Emails Configuration
The number of communities and daily rate of content creation can vary greatly across organizations. Settings for the length of included elements allow digests to maximize their benefit for organizations. 

Post By Link

Post by Link functionality allows Discussion posts on a specific web-based topic to be initiated from a link within any webpage or email. For example, “discuss this article” links can be placed on the bottom of every page of the magazine website to facilitate users posting about specific content.  With correctly formatted URLs and the proper page configuration, posts can begin and continue threads from links placed anywhere.  The posts will surface the promoted webpage in the body of the post with a default subject determined by the link.

The functionality is achieved through the eg:PostByLink User Control which performs three functions:
1) Verifies the user can post to the discussion (or any discussion if no community is indicated) by prompting login and checking community status
2) Receives variables passed and formats them for initiating a new post
3) Routes the user to the Post Message or Post Reply page depending on whether the post initiates a new thread or continues an existing thread. 

If the user cannot post per the URL variables passed no routing will occur.  Rather, the postbylink page will render displaying informational content items and prompting other actions.

Microsite Configuration

The configuration on the Microsite is based on a single page with baseline page code postbylink.  The baseline configuration of this page is to include two content items.  One achieves the verification and routing to allow posts are created properly.  The other content item displays messaging seen when the user cannot post to the discussion or the URL has not passed enough information to facilitate a discussion post.

To achieve the baseline configuration:

1) Add a new page through the CMS with the following characteristics:
  a.    Baseline location: a child of the “Participate” main navigation item placed under “Post Message” page folder
  b.    Navigation Title: Post by Link
  c.    Page Title: Rights to Post
  d.    URL Name and Page Code Name: postbylink
  e.    Security Roles Required to View: Authenticated (recommended)
  f.     Show/Hide Navigation: Hide this navigation but leave its content on the site

2)  To the new page add the first of two content items with the following configuration:
  a.    Name: Post by Link
  b.    Show box unchecked
  c.    Type of Content: User Control
  d.    User Control class or path: eg:PostByLink

3)  To the new page add the second of two content items with the following configuration:
  a.    Name: Rights to Post
  b.    Show box unchecked
  c.    Type of Content: HTML
  d.    Text input in HTML editor:  Sorry, it seems you don't have rights to post to this community at this time. It is also possible that the link you used does not provide enough information to initiate a new post. Please consider posting to another community discussion.  (modify this example as desired).  
  e.    Repeat to add other content items if desired.

Link Configuration

When configured correctly, properly-formatted links will open the postbylink page and initiate posts where the user can post.  The message displayed in step three above will display when the user cannot post or the link formatting is incomplete.  

The proper link configuration includes the following elements and syntax:
[website][pagecode][subject][URL][communitykey]
  • Website: the site where the postbylink page is configured
  • Page code: postbylink (this baseline configuration can be replicated on other pages with other page codes as desired)
  • Subject variable: The subject of the discussion post is a string of text with spaces represented by the “+” character.
  • URL variable: the webpage to be promoted in the Discussion Post
  • Community Key variable: The key found in the url when visiting a community landing page on the main site or the community list in the Admin site (among other pages).

The three link variables link elements must be preceded by the proper character per standard URL syntax.  The “?” precedes the subject while “?” precedes the URL and Community Key.

The following is a correctly formatted link to post to the announcements community on HUG (please do not finalize your post by clicking the “send” button - the community is moderated).   

http://www.hug.higherlogic.com/postbylink?subject=example+subject&url=www.nyt.com&CommunityKey=2007f287-a30c-4488-a083-6fc121c8114e  
 
support@higherlogic.com
http://assets3.desk.com/
false
higherlogic
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete