Release Notes - April 18, 2016

Print Friendly and PDF Follow

Product Functionality

Profile View Limit
Some iModules clients seek to restrict the number of member profile pages that a constituent can view in a 24 hour period. The new Profile View Limit option will allow clients to:
1.    Restrict the amount of information farming of other members' personal information that can be done by their constituents
2.    Identify constituents that have attempted to view an excessive number of different profile pages.
The new Profile View Limit configuration option is found in the Community administrative tools for the Profile Page system. Super Admins and Profile Admins will have access to this option. This is a per-sub-community admin setting that allows admins sets a limit for how many Profile Page Member Information sections can be viewed by a non-administrative user in any 24-hour period.

Once the limit is reached that constituent will no longer be able to view the Member Information sections of any other Profile Pages and will instead receive an error message telling them they have reached the view limit. Users will still be able to see the Profile Page header information, and be able to view and navigate to any available system links for Class Notes, Photo Albums, etc.
A tracking action will enable clients to go into the Member Site / Statistics tool to see if any members have reached the limit.

Profile View Limit Admin Tool
The Profile View Limit admin tool is a simple text input box that allows you to set the 24 Profile Page Member Information section view limit for your community.


•    Default is zero, which means there is no limit enabled
•    The limit can be set to any whole number from 1 - 500
•    The limit applies to all means and avenues of viewing Profile Pages - including Directory Search, links from class notes, job postings, classifieds, message boards, etc.
*The limit system is based on the member ID of the authenticated user - unauthenticated users will not be trackable / limitable
•    Once the limit is hit / matched by the user in any 24 hour period, then they are precluded from viewing the member information section of any profile pages for the next 24 hours.
*The system is based on a rolling 24 hour period - i.e. Tuesday 10:15 PM to Wednesday10:15 PM
•    The Profile Page header information and the available user system links that are enabled - Class Notes, Photo Albums, etc - can still be viewed and navigated to.
•    The error message is "You have reached the maximum number of profile page views in a 24 hour period."

User Exceptions
•    The setting does not apply to any authorized administrators in the community / sub-community.
•    The user's views of their own profile page do not count toward the limit
Sub-community Rules
•    The Profile View Limit setting is unique per sub-community.
•    The running count for the user is unique per sub-community - the user will have to reach the limit in each community to have additional profile views disabled in that specific sub-community.
•    The system will not count the views cumulatively across sub-communities.  For example, 15 views in GID3 and 35 views in GID 5 will not trigger a set limit of 50 in either of those sub-communities.
•    The lockout for the member will only be in the sub-community in which they reached the defined limit.
•    The setting inherits down from GID 1 in the enterprise model when a sub-community is first created.

Profile View Limit Message to Users
When limit is reached by the user, they will see an error message above the Profile Page header section telling them they have reached the 24 hour limit for views.  The message disappears after 30 seconds and the profile information remains hidden.  Profile Header information and enabled system links for Class Notes, Photo Albums etc. are still viewable and accessible.


Tracking Action
When a user hits the defined limit in the sub-community a new tracking action report called "Profile Page - Reached View Limit" is available in the Member Site / Statistics tool in that particular community
•    This tracking action will also display in the Tracking action tab in the Encompass admin view of the user.
•    Tracking actions reporting is an overnight process so any limits hit during a day will appear in the Member Site / Statistics tool the next day.
•    The row returned in the tool contains:
-First Name
-Last Name
-Constituent ID
-Date / Time
-Tracking type: Profile Page - Reached View Limit
-The tracking description: "User reached Profile Page view limit" and the "Extra Values" column will display the limit setting that was reached by the user.

NOTE:  This Tracking Action does not appear if there is no Profile View Limit enabled in that community.

Email Bounce (Kickback) Reporting Changes
The Email Kickback Report has been renamed to the Email Bounce Report to align with industry standard naming conventions.  In addition, Email Bounce reporting has been enhanced to give more clear reasons that the email bounced back and give clients a better idea of how to fix the issue.

New Definitions for Bounce Types in Email Bounce Reporting
Email bounce reporting will now include more specific information on the type of bounce that occurred.  The Bounce Type column (formerly Kickback Type) in the Email Bounce report will now display the following bounce reasons:  deferred, dropped, blocked, hard bounce and soft bounce.

•    Deferred - Recipient’s email server temporarily rejected the message.  The email should resolve to either delivered or bounced.
•    Dropped - The message was suppressed to protect your sender reputation by avoiding duplicate spam or bounces.  This is treated as a hard bounce.
•    Blocked - Recipient’s email server rejected message for a reason related to the message.  The error message will let you know how to revise the content.
•    Bounced - The receiving server could not or would not accept the message.

*Hard Bounce - A hard bounce is an e-mail message that has been returned to the sender because the recipient’s address is invalid.
*Soft Bounce - A soft bounce is an e-mail message that gets as far as the recipient’s mail server but is bounced back undelivered before it gets to the intended recipient.

NOTE:  This change will not be retroactive and will not change the historical value of any previously recorded kickbacks.

How should I respond to each type of bounce?



Have more questions? Submit a request