2017 Release Notes

12/12/17

What’s New

• When creating or editing articles, you can quickly see changes by clicking the “Open” link.
• Previously, invoices had system default address fields for the invoice recipient.You now have the ability to customize the invoice recipient fields in Invoice Settings, giving you the flexibility to add built-ins such as a prefix, custom attributes and text.
• We’ve improved the form submission user experience by auto-scrolling them to skipped required fields.
• When recovering a forgotten username, there is now a self-service workflow for users that have an email address in multiple profiles. Previously, this required administrative intervention to resolve. With this update, users will receive an email with each profile’s username.
• Before, your invoice templates determined the due dates for invoices created by form submissions. We’ve given you the ability to choose a specific invoice due date per form regardless of invoice template settings, giving you more administrative control over when you expect remittance of payment.
• Until now, exporting a registrant list that included discount codes used was not possible. Now, any discount codes used on a form submission can be included in the registrant list export.
• When filtering transactions in the Transaction Report, you can now exclusively filter by “Transaction Status.”

Fixes

• In the message report, the number of click-throughs displayed did not always match the number of profiles when drilling into that report. We now account for these scenarios so the displayed count matches the number of profiles.
• If a profile owner was not able to edit their first name or last name and prefix or suffix was enabled in attribute settings, the profile owner was not able to see their own first or last name. This has been fixed.
• In some cases, invoices that were fully paid were not being marked as Paid. Now they will be.
• When editing forms and configuring attribute security, organizations that only have individual member types were seeing settings that only applied to organization member types, causing some confusion. We’ve created clarity by adding logic around which settings display based on the member types created in each site.
• When re-sending a paid invoice, the original invoice notification was sent which caused confusion for the recipient. We now send the paid invoice notification when a paid invoice is resent.
• When editing form submissions to add guests, the guests were not receiving the same discounted pricing as the original form taker. Now, guests added to existing submissions will receive the same discounted pricing options.
• Members in an attribute-based member type could submit a membership form without actually making a valid selection for the attribute. This has been fixed.

11/29/17

What’s New

• We’ve improved how we communicate within the product. The ‘Need Help?’ section has been renamed ‘Resources’. It’s been given a cleaner look and feel with all the same features: access to the Help Center, contextually relevant tutorials for beginners and quick access to our feedback portal. We’ve also added access to the live product roadmap and we’ll be communicating new feature launches in this updated section.
• Invoices now include additional details about the payment method. Specifically, they now display the last four digits and type for credit card payments and the reference number for offline payments.
• For an admin taking a form on behalf of a member, additional payment options are visible to the admin (e.g., offline payment) that are not visible to the member taking a form. This has created some confusion, so we have added language to the product notifying admins that they are able to select additional payment options that their members cannot.

Fixes

• Previously, the invoice link provided in auto-renewal notifications for Member Types with $0 dues did not work nor was there was an attached invoice in the notification email.  The link now works, and the invoice is attached.
• For members renewing through a form into a period based Member Type with Attribute based pricing, their expiration dates were updating to the date they renewed as opposed to the period end date.  Their expiration dates are now updating to the correct period end date.
• Previously, when clicking the link from a renewal notification email, the due date was one day off.  Now the date is correct.
• The country field was not populating correctly on invoices when viewed through the member portal.  They are now displaying accurately.
• When inserting an image into an article, Contact Center message, form confirmation, etc., the width and height dimensions were not being recognized properly. Now, the dimensions are saving in the html upon an image being inserted.
• Apostrophes in default text fields were mistakenly being represented with “&apos” when a user takes a form. This has been fixed so apostrophes show accurately.
• We corrected a display issue that occurred when a payment was being processed by members; the whiteout did not completely cover the submit payment button, but now it does.
• Previously, when renewing a profile from the administrative interface, it was possible to create the invoice before selecting whether or not the invoice should be emailed or paid immediately. We’ve corrected the issue so admins need to make the choice of how to handle the invoice before creating it.
• We corrected an error that happened when administrators were creating renewal invoices for profiles that were renewing into a member type other than their current member type.

11/14/17

What's New

• Profile Notes! Now you can easily track conversations, call histories, event concessions, etc. within a profile so your staff and product admins are on the same page when interacting with members. To learn more, visit: https://help.memberclicks.com/hc/en-us/articles/115002695312-New-Taking-Notes-on-a-Profile

Fixes

• The emails associated with invoice templates (new invoice, reminder email and payment confirmation) have default content when no custom content is created. Previously, we didn’t show the default values for these emails, but now we do.
• The member view of voided invoices still displayed a value in the balance due column. We’ve corrected this confusion so members won’t think there’s a balance due for voided invoices.
• When viewing more than ten transactions per page on the transaction report, sorting by date did not work correctly in Chrome. Now it does.
• Entering three or more search terms in the instant search caused malformed results. We’ve corrected the problem so the results aren’t broken, even with three or more search terms.
• Administrators without the ability to edit an expiration date attribute, per the settings in attribute security, were also unable to view the expiration date attribute in a profile. We now correctly apply the attribute security settings in this case.
• We removed an unnecessary dash on the summary page of forms that appeared for built-in attributes tied to organizational profiles.
• Quotes in an event section label and apostrophes in form section titles were not being correctly rendered to form-takers. Now they will be.
• The latest changes to attributes view was one day off. We’ve corrected the problem so the date is accurate.
• Previously, when trying to add event guests through editing submissions, the built-in fields were not exporting correctly despite the data being saved in the the submission. Now results are accurate in the registrant list export.
• For $0 member types set up with advanced pricing, renewal invoices were not voiding out when a form was taken. Now the old invoices will be voided when the new one is generated.

10/31/17

What’s New

• You are now able to designate Revenue Accounts as Cash Accounts.  This will allow the import of financial transactions into QuickBooks with Cash Accounting formatting.

Fixes

• When trying to submit payment on a form, a specific set of members received an error message of “Payment declined: Payment Processor not found.” This has been fixed.
• A recent update prevented the downloading of Credit Memos as PDFs. This bug has been fixed so memos download properly.
• Punctuation/spelling/wording updates were made, including:
• In the Committees tab of profiles, “Notifications” was misspelled, and is now correct.
• Changing the term “Membership Renewal Options” to simply “Membership Options” in the form builder’s membership section, since this section applies to people joining and renewing.
• Removing the word “the” from and adding a period to the message located under the new user form login area. Now it appears as: “By providing your email address, you agree to receive emails from YOUR ORG NAME.”

10/17/17

What’s New

• You are now able to make invoices ‘Due Upon Receipt’ in Invoice Templates. Invoice recipients will see 'Due Upon Receipt' for invoices with this setting. On the invoice list and for administrative reporting, the invoice due date is the creation date.
• In member type and invoice template notification editors, you are now able to add an unordered/bulleted list.

Fixes

• The read-only function of forms was not presenting properly, causing fields to appear as if they were editable. This bug has been fixed.
• When a member would renew through a form, the system created a new invoice. This has been updated so that a new invoice will only be created if member type, member type pricing, invoice total, membership duration have changed.

10/3/17

Fixes

• Dropdown selection sets in forms were defaulting to the first available selection causing users to occasionally submit the form without knowingly making that selection. Now, dropdowns lead with “Make a Selection” so the user understands when a selection item needs their attention
• When a user would try to opt out of autorenew, they were not being opted out until after they paid the invoice. This has been fixed so opting out of autorenew is immediate.
• Merged data was not working properly for payment notification communications for BCC’d addresses. This bug has been fixed.
• On the administrative side, when the first listed member type was organizational -- because member types are listed alphabetically -- the attribute security dropdown menu was defaulting to a blank option. This has been fixed.
• In the subject line of a Contact Center message, special characters (e.g., “á, é, ú, ¿, ¡, etc.) were not sending properly. This bug has been fixed.
• When renewing a period-based member type into a lifetime membership, the newly generated invoice was showing the wrong expiration date. This bug has been fixed.
• Correct expiration dates were not properly being assigned to lapsed profiles or profiles with expiration dates in the past for multi-period memberships. For example, a profile with a three-year membership period and with an expiration date before today would expire only one year later upon renewal, instead of three years later. This has been fixed.
• When copying fields in the Form Builder, discount codes and date-based pricing settings did not copy with the field, forcing administrators to recreate the discount schemes.  They are now copied with the field as well as when sections are copied.

9/19/17

What’s New

• Admins can now restrict Individual and Organization name to be “read-only” in forms along with all built-in attributes.  This allows admins to set any field as read-only; previously this was only available on some of the fields in the form builder.
• Customers now have the ability to archive old forms no longer in use, offering a less cluttered view in forms list.

Fixes

• On the front end of the sites, saved searches were returning 0 results despite proper attribute security being in place. This bug has been fixed so the saved searches return accurate results.
• In the forms list, the registrant count was presenting as “0” instead of “View Lists” when the form had multiple events and the first of which had zero registrants. This bug has been fixed.
• The selection set summary report did not include the selection set name on the export, only the selections.  The selection set name has been added to the export.
• Authorize.net payments with a billing address over 59 characters would not process.  The bug has been fixed and these payments can now be processed.
• The form revenue report would freeze when attempting to load certain forms.  This bug has been fixed.
• The Admin bar would change when navigating to certain Community Pages.  This bug has been fixed.
• When attempting to view online connections in the social community an error page would appear.  This was a seldom used feature from a previous version of the product so we’ve removed it to address the issue.
• There were a few workflows that allowed Organization profiles to be changed to Individual profiles.  These workflows have been modified to prevent Organization profiles changing to Individual profiles.

9/6/17

What’s New

• Admins can now send Contact Center messages to users from the actions menu within a profile. This makes contacting a user easier by eliminating the need to go back to the profile list to send a message to the tagged profile.

Fixes

• Electronic Funds Transfer (EFT) payments made through profiles on the front end were not resulting in a paid invoice or showing up in the transaction reports. This bug has been fixed.
• For date-based member types with a multi-year pricing setup, only additional duration pricing was reflected for renewals through the profile. This bug is fixed so the first-year pricing is added to the new duration pricing, resulting in an accurate multi-year price total.
• Prospects with expiration dates (lapsed members that had been converted to prospects) were not being treated as re-joining members when taking application forms. This bug was fixed so these profiles are treated as new members for their price and expiration date calculations.
• Form confirmation emails were coming from the system default email address. This bug has been fixed so notification emails come from the site’s default email address set in Account Settings.
• Transactions in MemberClicks were appearing one penny off from what was showing in Authorize.net. This bug has been fixed, and the transactions are representing correctly.

8/22/17

Fixes

• When a form's event section pricing was being set up with member-type and date-based pricing, the price shown in the submissions list and export was incorrect. Now the pricing is correct.
• When a form's event section pricing was set up with a required single-selection drop-down that did not have a default value, the price was showing incorrectly in the submissions list and export. This has been fixed, and now the pricing is correct.
• Email addresses with certain special characters before the @ symbol were not displaying properly in the directory template. This bug has been fixed.
• When a front-end membership renewal form had a number field, and the member type selected was changed (i.e., toggling between member type options), the value was not getting cleared, causing a price discrepancy on the invoice. This bug has been fixed to reflect proper pricing.
• When trying to renew a profile with multiple renewal paths, the membership duration and pricing was not presenting accurately. This error was occurring only in certain versions of Firefox and Internet Explorer and has been fixed.

8/8/17

Fixes

• A bug was causing per-unit pricing to copy incorrectly on forms with a number field. This has been fixed and now pricing from the original form will copy over.
• When a former-member-turned-prospect attempted to rejoin through a form, a bug was adding only one year to the former expiration date. This has been fixed so the new expiration date is shown.
• The financial dashboard was displaying improperly in Chrome. This has been fixed so the display is accurate.
• When an ad hoc invoice was being paid for with an offline method, the .iif file name was exporting as the organization name. Now, the export properly displays with the individual's first and last name.

7/25/17

Fixes

• Previously, when a member renewed to a different member type that had different duration options, the initial member type’s durations were displayed on the invoice. We now display the correct duration options on the invoice.
• Taking an application form with a lifetime membership option no longer causes the user to be charged for a lifetime membership when they've selected another member type.
• When using advanced pricing for an organizational member type, the renewal invoice would print the words "Organization profile with attribute --" followed by the attribute name. It now displays the attribute name only.
• For customers using Authorize.net for auto-renewals, updating credit card information on a membership form was not updating the card information upon auto renew. This bug has been fixed.
• An error causing number type pricing fields and dollar amounts to calculate incorrectly in form revenue reports has been fixed. This fix applies to number fields in membership sections. A previous fix corrected the same issue in event and general sections.
• On the admin side, an error was causing file uploads in committees to fail. This bug has been fixed.
• A caching issue in Internet Explorer was causing a voided invoice to appear open upon refresh. This bug has been fixed.
• In recent versions of IE (10+), the admin home did not load correctly. Now it does.
• Per-page views were not working properly within committee messages on the front end and admin side. Now these settings are displaying properly.

7/11/17

Fixes:

• Committees:
  • When posting committee messages, we now indicate the number of characters entered so users know when they are at the 1,000 character limit.
  • Pagination behavior has been updated so that desired per-page results remain the same between back and forth browser actions. Additionally, once a per-page number has been selected, the system now remembers that preference as the default display option.
  • The default sort order for both committee files and messages now displays as most recent to oldest.
• A bug that, on rare occasion, caused invoices to not generate when renewing from a user's profile on the front-end has been fixed.
• For profile and admin renewals, a new invoice was being generated even when no changes were made to pricing during the renewal, causing the old invoice to be voided. This bug has been fixed so a new invoice only generates when a change has been made to the member's renewal.
• We fixed a bug that prevented admins from processing renewals when the only renewal path for the member was a different member type. For example, first year members having to renew as professional members.
• In forms, if auto-renew is required in the MT, the checkbox in the membership section was not selectable. Now, it is selected by default, as well as un-editable.
• Number fields with pricing in general sections of forms were not always calculating properly in the form revenue report. Now they do.
• A bug existed that caused email addresses with multiple extensions after the @ symbol to not hyperlink properly in the member directory. This has been fixed.
• When searching saved messages in the contact center, uppercase search terms always returned no results. Searches can now contain uppercase letters and results will return.
• Comment tags in the html of an event were causing the event page—including location and map--to repeat itself in view mode. This bug has been eliminated.
• Event location URLs were not working if "https" was entered. This bug has been fixed.

6/27/17

What's New

• Administrators can now take forms on behalf of other users whether or not the form is published. This improves the workflow when entering onsite registrants into the system after the event.

Fixes

• In a renewal payment confirmation email the "click here to view this paid invoice" link was requiring login, which took the user to their profile rather than the invoice. This has been fixed.
• A bug existed that was causing some users to not properly go into their renewal period. In particular, the user was unable to access a renewal form and the "renew" button was absent in the profile.

6/13/17

What's New

• Revenue account names are now editable regardless of whether transactions are attached to the account or not. Also, changes to revenue account names are retroactive, meaning current transactions tied to a revenue account will receive the updated/edited name.
• Administrators can now access and utilize a spell check function when creating an invoice email notification, much like what exists currently in the Contact Center.
• When a new member type is created using the copy group permissions function, the product will now also allow copy permissions for assigned attributes (both org and linked for org member types), form pricing and e-lists.

Fixes

• A bug in the product causing special characters entered into a form to export as question marks (?) has been fixed so the excel file now shows appropriate characters upon form submission export.
• In form builder, the option to toggle on and off the "enable confirmation section" has been removed, as it had no function behind it.
• Member type names with apostrophes now appear on the administrator's dashboard. Previously, these member types caused load errors.
• When a Contact Name built-in was added as a form field, it would only save the value to the submission if the form taker interacted with the field. If the field pre-populated with the profile value and was not edited by the form taker, the Contact Name did not save to the submission. Now the Contact Name will save to the submission whether or not the form taker edits the field.
• After six failed login attempts, a user is locked out of the system to mitigate a brute-force login attack. Previously, users were not being automatically unlocked after an hour. Moving forward, locked users will be automatically unlocked after one hour.
• On the Admin Home, the link on the Aged Receivables graph was not properly setting the filters in the transaction report. We’ve corrected the link so it sets the filters in the transaction report to match the values represented in the graph.

5/31/17

Fixes

• On the admin home, the event dashboard was not fully loading if there were no past events displaying. It now full loads regardless of whether or not there are past events.
• We corrected the text in the date-based pricing modal. Since our last release, this text referred to discount codes.
• In the editor, the image insert tool at the bottom has been corrected to use top, right, left and bottom margins instead of v-space and h-space. Put another way, the image insert tool will now allow you to set the space between the image and other elements when the image is first being inserted.
• We have made a few minor tweaks to form fields to improve accessibility for screen readers.
• For date-based pricing memberships with proration, if a proration period started before and ended after 12/31, the pricing was not properly calculated for new members. It will now be properly calculated, regardless of where a proration period falls on the calendar.
• For date-base memberships with multi-year pricing, new members were not receiving the correct expiration dates, forcing admins to manually correct them. New members will now receive the correct expiration dates when joining for multiple years.
• For date-based memberships that offer multi-year pricing, renewals through the profile were not generating the correct pricing for the additional year options. Now they do.
• When only one renewal path was specified for a member type and the renewal path was different from the current member type (first year members renewing as second year members, for example), we were generating an invoice for the current member type. We now correctly generate the invoice for the new member type. Note: if multiple member types are in the renewal path, the current member type will still be reflected on the automatically generated invoice.
• There was an occasional error when a Key Contact added a Linked Profile. This error occurred if the Key Contact cancelled out of adding a new profile, then attempted to add the profile again. We’ve fixed the issue so the error no longer occurs.
• The notifications sent through committee management for new files were not properly displaying the user’s contact name that uploaded the file. They do now.
• When assigning attributes to organizational member types, the modal would not always allow admins to save. Now it does.
• When setting up member type notifications, the Font Family drop down would stick in the page from time to time. We’ve permanently unstuck it.
• When a credit memo was generated that had multiple line items, the line items did not update to Paid status on the transaction report, even if the credit memo had been settled. Now they do.
• Users who were not logged in could not see paid invoices, making for a disruptive experience when a non-logged-in user paid an invoice. We now allow people who are not logged in to view paid invoices.

5/16/17

What’s New

• Previously, creating a new member type was a major project. Each area of MemberClicks needed to be updated in order for the new member type’s group to have permissions. Articles, menu items, categories, widget, forms, form fields, calendar events, attribute security, etc all needed to be updated and it was easy to make a mistake. While adding a new member type isn’t an every day task, we’ve made it much easier when it comes up. Administrators now have the option to copy another group’s permission when create a new member type, saving much, much time and confusion.
• When paying an invoice directly with a credit card on the front-end of the site, we now pre-populate the billing section with the primary address of the profile. 
• Similarly, when submitting a form and paying by credit card, we now pre-populate the billing section with the primary address of the profile.
• On the admin home, administrators now have the option to refresh the financial graphs to get updated metrics. Previously, these graphs updated once a day overnight.

Fixed

• There was an issue that prevented message tracking (opens, etc) for automated renewal messages. Moving forward, new automated renewal messages will include the message tracking automatically.
• When updating the email address of a linked profile in an organizational membership, the instant search results in the top right corner didn’t reflect the new email address. Now it does.
• Similarly, updating the name of a member type wasn’t being reflected in the instant search results. The new member type name will now be included in the results.
• When adding a new profile that uses the same username as a deleted profile, we now display a link to the delete profile so it can be more easily changed or restored. This was previously only working when the existing profile was not deleted.
• For member types that include a lifetime membership option, the default option in application and renewal forms was for the lifetime duration. We’ve updated the ordering of options to correspond to the order in member type settings.
• In relatively rare instances when a member in their renewal period had a partially paid dues invoice and the admin changed the member’s member type, we would void the partial paid invoice. We now no longer void partially paid dues invoices when the member type changes.
• We’ve corrected the parameters of the aged receivables link on the admin home. This link will now direct you to the transaction report with report parameters so you can see the individual transactions that comprise the aged receivables report.

5/2/17

Fixed

• Previously, when administrators were paying an invoice on the admin side of the site, the email address displayed on the payment page was ignored; the payment notification was always sent to the profile address. We now respect updates to the notification email address.

4/24/17

What's New

• We've made it much faster setting up member type pricing, discount codes and date-based pricing schemes in forms. You can now add multiple member types to a pricing column, eliminating much duplicate work.
• When entering credit card payments as an administrator, we've improved the validation so invalid characters (letters, for example) are prevented from being entered. Previously, administrators received an error when trying to apply the payment when an invalid character was entered.

Fixed

• We fixed an issue that prevented the default notifications in member type settings from being edited. This issue was introduced in the 4/18 update.

4/18/17

What’s New

• We’ve updated the loading of the admin home for a smoother experience. Each section now loads independently with placeholders during load.
• We’ve updated the payment section of forms in the form builder to better communicate an example payment section. Apologies for any confusion caused by the previous example.
• We cleared up another point of confusion around deleted profiles. When viewing a deleted profile as an administrator, we now display a banner at the top of the profile indicating the status.
• When editing notifications in member type management, we now display the name of the member type at the top of the page as a reminder of which member type is being edited when working on these notifications.
• On the transaction report under the Transaction Type filter, we’ve added a filter to find voided transactions.
• When paying an invoice as an administrator, we now pre-populate the billing address fields from the profile, saving much repetitive data entry. We'll be expanding this to forms and direct invoice payments from the profile soon.

Fixed

• The .iif file used to import transactions into QuickBooks was not properly formatting both sides (debit and credit) of discount transactions, causing an error on import into Quickbooks. We now properly format the .iff file for both sides of discount transactions, resolving future errors.
• The text in the Transaction Report was not always wrapping correctly, making it difficult to read all of the content, especially in the Payment Method column. We now display these fields cleanly.
• We corrected an issue that occurred viewing individual calendar events on mobile devices when the map integration was also enabled for the event. Previously, text could be hidden behind the map. Now the text wraps properly.
• There were a few circumstances where errors on the payment page of forms allowed multiple submissions to the gateway. We now prevent these issues from causing multiple submissions to the gateway.
• When an administrator applied multiple partial payments to a single invoice that had multiple line items, each line item was not properly changing status in the transaction report. Now they do.
• When editing submissions, occasionally dollar signs were displaying next to fields that weren’t set as pricing fields. This no longer happens.
• We corrected another similar issue where a duplicate selection set option was displaying on some fields when editing submissions.

3/21/17

Fixed

We had a series of updates this week focused on the payment features and reporting - fixing several long standing issues, especially around filtering in the transaction report. Details below:

• We corrected an issue that caused the receivables graph on the Admin Home to not update correctly. There were several scenarios which were not being correctly calculated. This graph will now correctly calculate open sale line items, less any discounts and partial payments against those line items for all revenue accounts not set as 'Dues.' The graph updates early in the morning, once per day.
• We fixed several filters on the Transaction Report including ‘Unpaid,’ ‘Refund’ and ‘Discount.’ 
• ‘Unpaid’ displays all sale transactions that have no payments related, and all of the transactions for invoices that have been partially paid. The 'Unpaid' filter will also display unsettled credit memos.
• 'Refund' displays all credit memos.
• 'Discount' displays all discount line items.
• There was an issue where not all of the contact info associated with a profile was being sent to Authorize.net as part of all transactions. This issue has been resolved, so all contact info will appear in Authorize.net moving forward.
• The URL generated by Site Links when inserting a ‘View All’ link pointed to a previous version of the front-end directory. We’ve updated this URL to point to the most recent version of the directory.
• When submitting offline payments as an administrator, the date field is now required.
• Sales transactions that were paid in full by the use of a discount code were remaining in 'Open' status on the transaction report. These items now update to 'Paid.'
• There were two scenarios where email addresses in profiles did not properly link in the directory listing. Domains that contain multiple periods, such as abc.123.com and email addresses that contain a number, such as duncan1@memberclicks.com, were broken. Both of these issues have been corrected.

3/7/17

Fixed

• We’ve improved the validation on payment pages to ensure only valid characters are able to be input in the credit card number field. Previously, users could experience errors on this page without clear messaging about what went wrong.
• We corrected an error that occurred when date fields in forms were typed into, rather than input through the date picker.
• We’ve added pagination to the invoice template list. Previously, it appeared as though some of the templates hadn’t been saved due to the absence of pagination.
• Long event names caused styling issues on the front-end. We’ve corrected the issue so long event names display without breaking the look of the event title.
• In the contact center, when adding a site link to any directory search, there was an additional slash inserted which resulted in a broken link. We’ve removed the extra character so the inserted links function correctly.

2/21/17

Fixed

• When administrators edit a profile’s username, we prevent duplicate usernames from being created. When a duplicate username is found, we now provide a link to that profile so it is easier to make a change, if necessary. Previously, the link was only displaying when profiles were created, not edited. The link now appears on creation and edit.
• There was an issue that delayed or, in some cases, prevented the saving of form fields with field logic applied. We’ve enhanced the field validation when moving from page to page of a form to resolve the issue.
• The form timer was not recognizing moving from page to page as form activity, occasionally causing the timeout warning message to appear too soon. The form timer now respects moving from page to page as form activity.
• Group permissions on pricing fields in the membership section of forms were not fully applying the permissions, making it possible for an invoice line item be generated for a field that didn’t appear to the user. This has been corrected.
• Default values in forms that also had pricing associated prevented pricing from also being included in the merged value in confirmation pages and emails. The price now merges in correctly, along with the selection value.

2/7/17

What's New

• The API can now be used to search for profiles based on event registrant status. Technical details are available here and here. Organizations using the API with webinar software, learning management systems and event apps can now have a tighter, more automated integration. Note: form fields are still not available through the API, but profile attributes of registrants are available.

Fixes

• We fixed an issue that prevented Key Contacts from unlinking profiles within the membership section of forms. Key Contacts will now see the Unlink option during the renewal section of forms.
• When administrators added a new user with the same username as a profile in deleted status, the error message was not displaying. As a result, admins saw an endless spinner. We now show the error message immediately.
• Users taking forms with field limits or registrant limits often saw the form timeout message too early, especially on the payment page. This has been fixed so the correct form timeout period (5 minutes when there's a registrant limit or field limit) is respected.
• We weren't properly validating the format of date fields on forms, occasionally causing internal server errors when form takers typed directly into a date field, rather than using the date picker. We now validate the formatting and alert the user if there are any errors.

1/10/17

Fixes

• In  some instances, the message report would load without properly paginating. This has been fixed.
• The form revenue report was not correctly calculating 'total discounts' and 'revenue less discounts' fields. We've fixed up the report so the revenue fields calculate correctly, with or without discounts.
• Replies in the community forum were not always triggering notifications to all users that had subscribed to a particular forum. Now they do.
• We recently introduced a bug which prevented administrators from updating the revenue account associated with the membership section of forms. The revenue accounts can now be updated as needed.
• We fixed a few rare scenarios where member types that had multi-year join options were not correctly assigning the expiration date.
• When a profile's username was deleted, we were not fully deleting the field from the database, which kept that username reserved. We now fully delete that username from all areas of the database, making the username available again.
• When creating an ad hoc invoice, we now handle commas in the 'Amount' field.