When viewing an invoice's online payment details, the credit card number (last 4 digits) and the Payee Company Name are now displayed. Some of the detail items have also been reordered or renamed for accessibility. Note that we do not store full credit card numbers anywhere within our database.
When duplicating an existing Event, you may now modify Activity Dates and Activity Times and have those changes trickle down through the newly created Activities, Registration Forms (including drop-down controls) and Activity CEU records.
It is now possible to modify the Created On date and time for Tickler Notes. Some clients enter Tickler Notes all at once, and need to be able to specify the date the note applies to. As before this update, if you leave this field blank, the current date and time will be saved.
When duplicating an existing Event, you may now modify Activity Numbers, Titles and Descriptions - and have those changes trickle down through the newly created Activity, Registration Forms (including drop-down controls) and Activity CEU records.
You are probably already aware of the PaidThru date triggers within the invoicing system. These triggers cause the PaidThru date of the Ship-To or Bill-To Contact to be updated once the invoice is paid in full. This provides a handy way to update PaidThru dates automatically, once full payment is received. We recently expanded the trigger fields to include the Category, SubCategory1 and SubCategory2 fields. So when an invoice is paid in full, you can have the system automatically update those category fields. For example, a new membership application may initially create a new Contact with a category of 'Prospective' or 'Pending'. But when it is paid in full, the Category can be updated to 'Active Member'. Contact us if you'd like more details about this new feature. You can also review the on-screen pop-up help text too.
When viewing a Completed (Input) Form, the user interface has been overhauled and updated to more easily be read on mobile devices. The print function also prints a more refined, clean output of the information.
We regularly receive phone calls or emails from clients requesting new features or functionality... only to find out that we already have that functionality built-in -or- available as a custom add-on that we can tailor for your specific needs. If there are things you'd like to be able to do, don't hesitate to contact us at any time. Chances are, that functionality already exists. If it doesn't, we can build it or include it in future improvements to the system.
The Contacts Dashboard report has recently been improved. We made the charts larger, the legends are easier to read and the printed output is ready for distribution. Legend labels are no longer truncated and aren't prefixed by the order rank number. Pie wedge percentages are now shown on the legend, so they are presented when printing the information. (Prior to this change, you had to hover over smaller wedges in order to see the percentages.) Each chart is printed on a separate page and the output may be printed in portrait or landscape (recommended) mode.
When viewing a Contact record, we've added the ability to view login counts by year. Simply click the 'Show History' link next to the 'Login Count:' at the top right side of the Contact screen. The history shows login counts for each year 2013 and later, beginning with the first year that the Contact logged into the system. If the Contact record was created prior to 2013, it is possible that the total login count shown may exceed the sum of each individual year.
When viewing the recipients of an E-Bulletin, you can export a CSV file by clicking the 'Export Data' button in the upper right-hand corner of the screen. We recently added basic Contact information fields to this export, so it is similar to the export found on the View E-Bulletin Stats screen.
Similar to the changes recently made to add improved security measures to the Input Forms module, we've also added similar measures to the Blog Comments screens that are public-facing. The goal is to thwart robots (a.k.a. 'bots') from attempting to submit false data into the database. For more specific details, please refer to the recent post on how we added this functionality to the Input Forms module.
You can now limit access to your website content (e.g. pages, articles, documents, news sections, etc.) to Event Registrants. For example, you may want to only allow access to certain pages or documents to those who are registered for a certain Event. We can now quickly and easily set this up for you. You may also restrict access to certain (News/Calendar, etc.) sections by Section ID. Please call us if you'd like more information.
We recently overhauled the way Committee and Office positions held are displayed within the Contacts module. You'll notice that it is much easier to visualize Committee and Subcommittee participation. When adding or editing positions, the pop-in window appears at the top of the positions held list, rather than at the bottom. When showing or hiding the Committee/Position History, the system now positions that section of the Contact information at the top of your web browser screen too. Our goal is always make minor refinements that don't disrupt your memorized flow of how the information is presented.
Similar to the changes recently made to add improved security measures to the Input Forms module, we've also added similar measures to the Create New Account screens that are public-facing. The goal is to thwart robots (a.k.a. 'bots') from attempting to submit false data in order to set up a new Contact record. For more specific details, please refer to the recent post on how we added this functionality to the Input Forms module.
We've added a double-layer of new security to the Input Forms module. The first layer incorporates Google invisible reCAPTCHA. It is 'invisible' because it automatically detects when bots are entering data into the form without having your members click an 'I am not a Robot' prompt - or having to identify all of the pictures in a mosaic that contain a specific object. The second layer of security is a 'handshake' that is required between the end user's screen and our servers. In other words, a hacker could not set up a form and try to submit data to our server, because each form request contains a unique token that we issue when the form is first requested. Make sense? Well, if not, just know that we are now able to prevent almost all, if not all, of the robot-completed forms from being submitted. Believe it or not, a bot tries to complete a form about every fifteen minutes on one of our client websites. Of course, this only applies to publicly available forms. We plan to add reCAPTCHA to other publicly available prompts, such as online directory prompts, in the near future.
We've added a new report that lists all of the undeliverable E-Bulletins from the prior 24 hours. This report is automatically emailed to your designated System Administrator each morning. It lists each Contact and provides links to jump to the Contact record, as well as a descriptive reason why the message was undeliverable. This report is only sent when you have attempted to send an E-Bulletin to at least one undeliverable recipient. You may use this report to verify and clean up email addresses that are invalid or blocked by the recipient's email provider or server.