ENC-30953 Improved performance of V2 Email Metric API Recipients call to address reported time outs.

Profile Forms

ENC-30059 - Resolved an issue causing profile forms to refresh the last step instead of submit and exit to the Finish Page. In order to resolve the issue the "Finish Page" option will no longer be available in Form Exit options on profile forms. If a profile form had this configured it will automatically be changed to the default option "Community Homepage." Alternatively, form exit options can be changed by the admin to another option prior to the December 11, 2017 release and those forms would no longer be affected.

ENC-2217 - Removed an unnecessary "Search Job Postings" button from the job posting results page.

ENC-13683 - Improved error reporting for the Gmail integration to list out the reason an email address can't be added. The error types are now "This name already exists", "Reserved name", and "General error".

ENC-28305 - Resolved an issue causing username and password fields to not display when shibboleth login was configured as an option.

ENC-29160 - Resolved an issue for users in time zones UTC+2:00 or higher that caused newly created events start date to default to the incorrect time zone.

ENC-30048 - Resolved an issue causing the save button to submit populated form data and exit the form.

ENC-30192 - Resolved an issue causing login lookup to display an error page because an encrypted field had been set as the first login lookup result field.

ENC-30482 - Change all reconciliation reports to include any privacy protected records that submitted relevant forms.

ENC-30250 - Enabled new distributed caching system for campaign progress indicators to prevent values from randomly increasing and decreasing on each page load.

To comply with the latest industry standards surrounding merchant-secure communications, iModules has discontinued support for TLS 1.0 and 1.1 encryption protocol. This means that we have eliminated support for certain older and less-secure forms of TLS, and will respond only to those using TLS 1.2. These changes require clients to ensure that their computing environments are compatible with TLS 1.2, and may require users to upgrade or configure their browsers.

The current industry standard version is TLS 1.2. It has been determined that TLS 1.0 has significant enough vulnerabilities that the PCI Standards Council, along with other security bodies, have decreed that web providers remove support for TLS 1.0 by June 2018.

For more information about TLS/SSL support history, review the "Web Browsers" section of the Wikipedia article "Transport Layer Security". Don't see your browser listed? Feel free to check your browser's TLS compatibility using SSLLabs.com.

Page Properties Visual Update

Page properties that is accessed by selecting the "Page Properties" or while modifying a page in the site map window, received a slight visual update. This new layout allows for longer text boxes to improve the visibility of long values being entered into those text boxes.

Product Functionality

Issue Resolutions

ENC-29755 (GIVING): There is known issue with our Campaign Admin right that is unfortunately preventing access to the new giving transaction export. Once addressed the following admins will have access to this export:

ENC-29241 (MEMBERSHIP): The last emailed date on the membership auto-renewal grid will now be appropriately updated when a user gets an email about an expiring credit card.

ENC-23981 (Profile): Member email addresses that contain more than 10 characters in the TLD (Top Level Domain) were not supported. Now email addresses can contain up to 15 characters in the TLD.

ENC-27758 (Giving): Designations that were selected in the designations pop-up were not displaying a check mark when selected.

ENC-29580 (Forms): Forms with a query string hyperlink in a rich text field were actually using the full admin URL, preventing non-admin users from accessing the hyperlink.

ENC-29591 (Forms): Form fields were allowed to change to Volunteer Management Agent type, which was causing an error during form submission.

ENC-29645 (Directory): Directories were displaying a generic error if the Advanced Search fields had not been configured. Now an informative error is displayed instructing the user to configure the Advanced Search field before a directory module can be added to a page.

ENC-29704 (Forms): When the user selected the Cancel button in the ICP popup the "Please Wait..." message was displaying on the form in place of the Cancel, Next and Submit buttons preventing the user from proceeding in the form.

ENC-23981 (Email Marketing): The email system now acknowledges addresses with extra long suffixes as valid. For example: bob.longlastname@123.extralongsuffix

ENC-30145 resolves an issue where clients using Shibboleth for single-sign on capabilities where receiving a page not found message after logging into the Encompass backend.

ENC-29900 - A misconfiguration with display options inadvertently presented a link that allowed admins to the "Send Request to Update Payment Information" on-demand. While enabled, admins who clicked the new link sent an email (given a valid billing email address) to the respective constituent prompting them to update their credit card information. Cards updated via this process would update as expected for the respective record/transaction commitment.

NOTE: We have removed the option so that we can further refine additional features and expected behaviors of this new process. Look for this to make a proper reappearance in upcoming releases.

ENC-29906 - A number of settings were not applied in order to display some of the items listed in our September 25th release notes. This would have impacted functionality in following areas, that should now be resolved:

Product Functionality

Issue Resolutions

Due to unforeseen complications with this release, it was rolled back on 9/21 as communicated via the iModules status page incident. http://status.imodules.com/incidents/291hnfvqf81f

ENC-29754 resolves an issue with database connection errors. The issue was most often noticed when tokens intermittently failed to populate in email marketing or emails failed validation because of a mis-configured / duplicate system token field. (ENC-29747).

This export is for clients who would like to have both the gift and designation details of a transaction consolidated into one export. This export type will be available across all GIDs and is designed to only combine all giving form transaction data within a specific GID.

Where can I access additional information about this product and/or submit feedback?An additional page listing known issues and product functionality can be found here on our FAQ. If you would like to provide feedback on this product you may access the form here.

Where can I access this new export?

A new menu item will display under the admin option of Donations --> Report. You can also access a new tab under Reconciliation Reports from the admin tab interface.

How will this export work?

A new recon exporting option will be present below the current reconciliation tab that will launch a new table and option for the setup wizard. The wizard will allow for additional configurations including: date filtering, scheduling, notification emails and SFTP file retrieval if this option is enabled on your site.

Will this export allow custom fields to be added?

Additional Export Field list option will allow admins to add both Profile and Re-usable Instance fields to their export. Once the configuration of fields has been selected, this will establish a standard for all giving transaction exports to include these fields. This can be a unique configuration per GID, not per export within the same GID.

Will Adjustments and Offline Transactions display in this export?

This export will pull in giving transactions across multiple campaigns for the date range defined. By design it will not include offline transactions for reconciliation purposes and because adjustments for giving are extremely rare and commonly keyed into a client's offline database when they occur, adjustments will not display in the file.

Will fields marked as "Allow export of this field: = false" be exportable in this export?

Fields marked at GID=1 to not allow exporting will not be accessible in this recon regardless of admin type.

Why does the donation amount repeat on the designation rows for that transaction?

The donation amount repeats on each respective row to provide the total amount available for selected designations. If a client would like to sort on this field for a specific transaction ID, they will know the amount drafted today 'Order Total', amount available for allocation for all designations 'Donation Amount', and amount allocated to each designation 'Designation Allocation'.

If recurring transaction, you would expect to see amount drafted today 'Order Total', total gift amount that is available for allocation for all designations 'Donation Amount', and current collected amount allocated to each designation 'Designation Allocation':

What column layout can we expect for this export?

What are supported special characters for Designation and Commerce Identifiers names/column headers?

Any characters used for naming purposes outside of this list runs the potential risk of creating errors in SQL to successfully export data.

Events

Events with Donations

Email Marketing

ENC-29267 Resolves an intermittent issue where one or more batches (emails are sent in groups of 1,000) would fail authentication and not successfully send. With this fix, batches with authentication failures will retry for 5 minutes. In this way, brief connectivity issues will not result in send failures.

Forms

ENC-29333 Resolves an issue where errors were displaying on profile forms that contained CEEB values.

Viewing campaigns that are tied to events now displays a new prompt, as shown below.

Clicking the "Show More" link will display the full list of links to each event that utilizes the selected campaign, as shown below. Selecting a link in the list will navigate to the event's form.

As part of our continued commitment to security, and an important part of our PCI compliance, effective with the July 31 Product release, we will no longer be able to allow iFraming of Encompass-served pages to external sites.

iFrames are a convenient tool to show external content within a frame on a webpage; however, this functionality allows for malicious behavior. As a result, we will no longer allow iFraming of Encompass-served pages. You can read more on our "From the Desk of the CTO."

If you have questions as to whether this affects your or not, please contact Application Support.

Issue Resolution

Web Services

ENC-28962 - Resolved an issue where a member with multiple event registrations was causing errors in GetMembersChanged web service.

Profile

ENC-28923 - Resolved an issue causing edits to College information to not be saved in Profile Forms.

ENC-28721 - Resolved an issue where profile forms were not honoring the SSL setting.

ENC-28256 - Resolved an issue causing member counts to not be displayed in the sub-communities grid.

Donations

ENC-28792 - Resolved an issue where clicking Save on Review/Finish pages of Donation forms wasn't exiting the form.

Confirmation Emails

ENC-28739 - Resolved an issue causing documents in confirmation emails to be unavailable for download.

ENC-26463 - Resolved an issue causing admin confirmation emails tied to recurring payments to be sent even if the admin had deactivated the email.

Events

ENC-28700 - Resolved an issue where Event Reporting Admins could not access Event Reconciliation Reports

ENC-28010 - Resolved an issue where the remove guest icon wasn't being displayed to non-admin users.

ENC-26168 - Resolved an issue where the continue button on pre-populate forms was not immediately responding to the admin's click.

ENC-20854 - Resolved an issue where roles weren't being applied to the next step in an event registration.

Schedules

ENC-27793 - Resolved an issue causing code to be displayed above schedule content blocks.

CMS

ENC-29022 - Fixed scenarios where the user site map module listed pages or groupings of parent/child pages twice.

Membership

ENC-28681 - Verified that class names are not duplicating when logged in or on various membership campaign configs.

Class Notes

ENC-28591 - Resolved the issue with the back button periodically not working on class notes pages.

The Advanced HTML workflow in email marketing was designed for clients who have the expertise necessary to generate html for email and do not want that code modified or altered in any way before send. The new workflow is superior to the Telerik Editor that re-writes and re-formats html in ways that are not email client friendly. The enhancement eliminates the Telerik email editor and the wrapping of provided html in a table. A unique text only version is also defined as a part of the workflow.

Opens by device helps administrators who want to understand device share for their audience and adjust email marketing techniques accordingly. Up and to this point, user agent string information was only available through the Email Metric API.

Please Note: Institutions identified as potentially being affected by this item have been notified.

During the July 17 Product Release, iModules will be deleting unnecessary code from the Encompass system tied to a product we no longer offer or support (DonorForce). When DonorForce was initially enabled on a client's site, it automatically added a column into all commerce reports; this column will now be removed. Clients who have been identified as having DonorForce enabled in the past and also have automation configured for commerce reports could potentially experience an error after the July 17 Product Release. We recommend that clients update any necessary processes before the July 17 Product Release.

Issue Resolutions

Directory

E-Commerce

Email Marketing Reporting

Events

Profile

Reporting

TransactionEmails

CMS - News, Events, Campaign Modules

Class Notes UI Update

Revamped design to support mobile ready templates, update of user interface and improved integration with Profile Page system. One functional change is that the default / home view of Class Notes now displays a reverse chronological listing of Class Notes, instead of first requiring users to conduct a search.

Events Data Entry Admin

New admin role created for purpose of operating within Events system but only interacting with data entry tasks. Admin is able to interact with event module functionality but will not have overall event admin access.

Where do I assign the administrative option for this?

You will access the Gold Key --> Administrators and assign the right same as you would for any Community admins. You will have to same community options you may assign as well.

What menu options are available in the nav for this administrative right?

The admin will be able to view and access widgets on the dashboard. Content will be available so the admin can return to the CMS side of the site. Events and sub menu Events Home will be accessible as well.

Once logged in, what administrative options are available in the Manage Events tab?

Most traditional event administrative options have been removed from this right including: Ability to 'Create New Event', Event History and Reports tabs, and the gear icon which contains options to Edit, View the Attendees List, Review Commerce Fees or Reports, Adjustments, Deactivate and Delete Event.

New admin right can access the search filter to look for a specific event or clink a link to an event found in the grid.

What options are available for this admin on the registration form?

When the form initially loads, we will provide a message that indicates you must "Find a member to begin.". Until a record has been selected the form will be disabled and the admin will be unable to submit the steps. You must find an existing record to begin registration for the event and will not be able to create a new record with this right. Guest records will be new non-member records; however, the main registrant must be tied to an existing record in your site. Field and manage form options have been disabled as well.

Can this admin skip required fields on the form?

Yes, this admin can skip fields found on the registration form regardless of their requirement to a user.

Will this admin be able to submit registrations on the constituent side?

While we do provide access to the event details and registration options via the 'View Content' button, we do not allow this admin to submit registrations on the constituent side. To prevent this we have disabled form navigation buttons. Appending the URL with a MID will render the admins information as the intended purpose of this right is to key in registrations on the administrative side.

Can Data Entry Admin register for all event types?

Yes, this admin can RSVP registrant and guest(s) respectively as well as key in credit card information on the billing step.

Can this admin adjust registrations or resend confirmation emails?

No, this admin will not have access to the Event History or Submission pages. Event and Super Admin can make these changes for registrants.

Cross Email Metrics: Beta Email Marketing Reporting

For clients who want to understand email performance across messages over a given time range or for a specific category.

How is this an improvement?

FAQ

What is the default date range?

Last 30 days (including today)

How many email subscription categories can I filter by at one time?

One

What happens if I change the name of an email category?

For reporting purposes, an email will stay with the name of the category it had at the time of send.

Why median not average (mean)?

Both median and mean are measures of central tendency. Median is a better choice because open and click rate data is likely to have outlier values from emails that went to significantly different list sizes.

Import Non-Member Merge File - Bypass Member Merge Checks

A site settings that allows admins to queue multiple non-member records to be merged into a single constituent record using a single Non-Member Merge File.

Click here for more details on this site setting.

Commerce

Email Marketing

Events

Giving

Profile

Reporting

Sitemap

Transaction Emails

Profile

Performance Optimizations - Currently Available

Several enhancements targeting an increase in performance have been placed into production. Included in these enhancements:

Admin dashboard improvements - Optimization of queries behind Admin Dashboard widgets have been implemented, resulting in large performance gains. Functionality of some widgets has been adjusted to be more reflective of their original intent.

Placing content blocks in CMS editor - Improved speed of placing content blocks while using page-editing CMS.

Optimized content query - Enhanced load times of more robust modules featuring listing and archive capabilities.

Giving & Membership: Query String for Payment Types

Now clients can append a new URL parameter to support various payment types on both Giving and Membership forms. This added functionality is also extremely beneficial for clients who use this with email campaigns, and targeted recurring giving campaigns. Simply appending &paymenttype=

For Giving:

For Membership (on applicable levels):

What happens if a payment option is not configured on the form and used in the query string? (i.e. perpetual is not enabled and is used in the URL as &paymenttype=perpetual or &paymenttype=perpetualonly)

When used on forms that do not have the supported payment method, form should load as it normally would showing all applicable payment options and ignore the URL parameter.

Is &paymenttype= case sensitive?

Yes, in order for this to properly work you will need to use in the URL as seen on this page.

Will scheduled payments be available on all membership levels even if the level does not have it enabled?

&paymenttype=scheduled and &paymenttype=scheduledonly automatically render scheduled payments control only on applicable membership levels. A difference you will see on these levels is that "I would like to make scheduled payments..." checkbox is editable with &paymenttype=scheduled and not editable with &paymenttype=scheduledonly. Both options default the scheduled payments box to open and will become grayed out when a level is selected that does not have scheduled payments configured.

Where will the URL not be persisted?

The appended url does not persist-

From Event, Giving or Membership Center (aka landing pages): http://www.odd-responsivepub.imodules.com/s/1732/index.aspx?sid=53&gid=1&pgid=710&content_id=468

i.e. http://www.odd-responsivepub.imodules.com/s/1732/index.aspx?sid=53&gid=1&pgid=710&content_id=468&paymenttype=xxx = won't work

If form has custom url: http://www.odd-responsivepub.imodules.com/customnew&paymenttype=xxx = won't work

Will this remain in the URL if using prep-pop?

Yes, you can use this URL parameter on your pre-populate links and the new tech will be supported.

Sunset Task Manager

Historically, the adoption of Task Manager has been very low among our client base. By removing this functionality from the tool, we have eliminated additional complexities associated with Task Manager's interactions with the rest of the platform. Clients who have tasks created will be notified of those details before they are removed from the system. On April 18th, you will no longer see this tab or any task references in data viewer.

Data Viewer No longer Auto-selects Everyone by Default

Data Viewer will not have a radio option selected by default. The change prevents administrators from unintentionally including every database record in a query.

More Helpful Tab and Page Titles

To improve the user experience, we've the revised the text of breadcrumb navigation and tab titles across the administrative tool set.

Before

After

The following issues have been resolved

Administrative Dashboard

ENC-1782 ensures iModules articles drop off the dashboard when the display date range has ended.

Administrative Rights

ENC-27919 addresses inability of credentialed administrators to edit event listings.

Authentication

ENC-26334 corrects issue preventing constituents from authenticating with yahoo credentials.

CMS

ENC-27484 resolves an issue with hyperlinking that caused class notes and job posting module links in emails to direct to the homepage instead of the intended destination.

ENC-27405 addresses issue with hyperlinking that caused event module hyperlinks to white screen instead of directing to the event details

ENC-27817 ensures that individuals who attempt to visit deactivated event forms, donation forms, membership forms are redirected to detail page content instead of a blank page.

Email (Field Tokens)

ENC-22445 restores population of the preferred first name field token for upcoming charge emails sent to constituents in advance of recurring transaction processing.

ENC-23160 ensures the first name token in member support emails is replaced with the first name value not the community name value.

Events

ENC-25181 removes the legacy event guest name column from being visible on attendee lists.

Online Giving

ENC-21760 prevents the "bledit" query string parameter from loading designations belonging to a different sub-community than where the form is hosted.

Reporting

ENC-26953 corrects designation report date filter to utilize the same date time stamp as the donations report (transaction date vs. designation selection date). The issue was encountered on transactions where the form was started, abandoned and then completed on a separate calendar day from start.

ENC-27363, ENC-27761, and ENC-27762 ensure that incomplete submissions are included in and export when an administrator selects the incomplete submission checkbox.

ENC-24997 solves an issue where reusable instances fields would not return on reconciliation reports if the transaction date was not included as an export field.

Security

ENC-27600 re-enforces strong password requirements for administrators who only have content editing rights (CMS Admin).

ENC-27689 removes support for legacy encryption methods for passwords created over five years ago that have not been modified since.

Reporting-only Admin Rights

As part of a series of usability enhancements, reporting-only admin rights will be able to be assigned to admins starting on April 10th. These rights will be for reporting in Giving/Campaigns, Events, Forms, and Membership.

Campaigns Reporting Admin will see the following options in the Donations menu:

From the admin view, this admin will see the campaigns with the reporting icon as well as the tabs to access Saved and Scheduled Reports as well as Reconciliation Reports.

Events Reporting Admin will see the following options in the Events menu:

From the admin view, this admin will see the events with the reporting option in the gear menu as well as the Reports tab.

Forms Reporting Admin will see the following options in the Forms menu:

From the admin view, this admin will see the forms with the reporting icon as well as the tabs to access Saved and Scheduled Reports as well as Reconciliation Reports.

Membership Reporting Admin will see the following options in the Forms menu:

From the admin view, this admin will see the membership forms with the reporting icon as well as the tabs to access Saved and Scheduled Reports as well as Reconciliation Reports.

Event Audit/Transactional Report

A completely revamped new audit detail export of all the registrant activity that displays edits, adjustments, and additions behind each primary and guest registration will be available February 27, 2017.

Where can I access the Audit/Transactional Export?

From Events --> Reports you can access the 'Create New Export' button under the Optimized Report heading. From the new window you can select an additional Custom Event Data Export type called Audit/Transactional Export once the flag[EnableAuditEventExport] has been enabled.

Will I be able to Configure Data by defining an Export Type (i.e. Specific Activities, Main Event, Event data with all related activities...)

This export type by design will pull all event data with all related activities (if applicable) and categories. Report will also be supplied with canned fields at the beginning of file: Const ID, Member ID, First Name, Last Name, Action Date, Registration Count, Registered By, Order Total, Email Address.

What is the Action Date column and what does it track?

Action Date will date stamp when the action for that row occurred. If a constituent registers on 1/3/16 and later changes their registration on 1/4/16, each row will give you the details that occurred on those respective dates. This feature is great for admins who want to track when an influx of registrations came in or if multiple people canceled on a certain date - admins can tie it back to what may have triggered the action.

Will this report show the user/admin who adjusted/submitted a registration?

This report is designed to show you any user (constituent, admin) who submitted or changed an existing registration; however, this feature is only meant to track things moving forward from when the flag is enabled. Pulling a report today will not have data populated in the new "Updated By" column.

What column can I use to group submissions together?

If an admin adjusts a record, the 'registered by' column will be blank for that row as it does not apply in that scenario. For grouping purposes, admins can use the 'Submission ID' column for a unique ID that groups all registrations/edits that were done for that party.

What is the purpose of the Submission History ID?

The 'Submission History ID' column's intended purpose is to provide the same ID for records submitted together while registering. This can allow for easy grouping as well as provide great metrics on when people may have registered for certain things since date stamps are provided for each action. Each new submission will have contain a shared ID value for that party.

What is the purpose of the Adjustment ID?

Adjustment ID column will display a unique ID for each adjustment for admins who want to mark off line by line, or is a great way to report progress that they have processed adjustment ID 1614-1700, for example.

What happens to the export output when I merge a guest/non-member record with their constituent record?

This row will now contain a value for Constituent ID (Client's Primary Key) and member ID will change but their registration details will remain the same.

Can I add additional member fields or change the sort order of them in my export?

If you would like the field to be available on your export, you will need to add those respective fields to the event form. Once added (in Admin or Constituent facing categories) it will then be available in your export. Field order is determined and follows the order in which they display on your form... from start to finish.

When applying a date filter on when users submitted the form, which rows should I expect to see?

The export will provide any rows with the action date that met your date range criteria regardless if the row is a registration, adjustment, etc. If the row reported has an associated (debit or credit), it will pull in that row in this file in order to properly reconcile despite being out of the date range you indicated. Below we applied a date range of 11/16 through 11/18:

(Even though Omar registered on 11/17 and canceled on 2/8, both transactions will display for Audit purposes so you never have to chase down when associated rows may have occurred.)

Scheduled Payment UI Change

If the scheduled payments option is enabled on your giving or membership forms, you are most likely used to constituents having to indicate their total payment breakdown less one. We understand this can cause confusion among various users and have incorporated a new flow for this option that allows a more intuitive and user friendly breakdown of their gift/membership to your organization.

On January 31, 2017 the scheduled payment option (not perpetual) will change to allow a constituent to indicate the total number of payments they intend to break their payment into. As seen in the giving screenshot below a donor will receive a clear breakdown of payments remaining as well as the amount that is due today.

Check out our friends at Fordham University who are one of the first adopters on this new UI change!

As well as our friends at Purdue who are using a new UI flow on their membership forms.

NOTE: On January 31st the UI will change for all Giving and Membership instances of scheduled payments site wide. This change will still function as expected for clients who have a defined first payment of X set up for these forms or use Promo codes for Membership. Also, if you have current styling on your form you should not experience any disruption with the design on your form.

Checkbox Export Ignores Custom Values

Effective January 31, 2017, the export will now respect the field setting through which a client specifies the desired export value (can be 0/1, true/false, or yes/no). Currently there may be some clients who expect the ignored format that currently display as True/False. Organizations with scripts that process scheduled exports should address their process of correcting these incorrect values or enlist in support from iModules to help remedy prior to the January 31st launch of this item. This defect can be further referenced with ticket ENC-25033.