New Features

• When recording a transaction, if the customer has an email address on record, an option is shown to send them an email with the transaction details and their new balance.
• Portuguese (Continental) has been added to the list of available languages.
• Balance Lookup can now be shown in any of our available languages.
• Online Enrollment now has a CAPTCHA field to stem or prevent bots from submitting junk entries.

Upgrades

• Online Enrollment emails now say which campaign the new customer was added to.
• When exporting an Excel file from a report, the export now includes all available fields / data, even if not show on the on-screen report.
• MS Excel restricts numbers to an accuracy of only 15 digits. This means that when entering a 16-digit card # in excel, the last digit is dropped and replaced by a zero. 24-digit numbers have 9 zeros for the last 9 digits.  A work-around was implemented to the Excel export, where card #s and numbers over 15 digits are displayed as "text" in excel, while still retaining the ability to have sorting and calculations performed on them as though they are numbers.

• In Points campaigns, the promotions pull-down is now shown even if no promotion has been defined. Previously, nothing was shown, leading clients to forget it was available as an option.

Bug Fixes

• Previously, points were rounded (up or down) to the nearest whole number. However, this created instances for clients who award, for example, 1 point for ever $100 spent, where rounding up seemed to imply that they had more points then they actually had.  To remedy this, rounding of points is now always down to the nearest smaller whole number.
• Previously, in certain situations, non-administrators were not able to see campaign lists (like in import tool, or adding customers to other campaigns). This is now fixed.
• In certain instances, importing transactions did not trigger a billing level change (when appropriate) when the transactions import list contained customers with IDs or card #s that were not previously entered. Now those customers are recorded as new customers, and the billing level is adjusted correctly.
• Previously, when some of our earlier clients' employees with non-admin-level logins updated a customer's information, the account id / card # would be replaced by a new random number.  This was due to a migration of the database structure from an earlier, simpler model to a more sophisticated one, and an internal unique ID and the account ID / card # were being swapped. This affected only a small number of accounts, no data was lost, and the bug has been fixed.