<?xml version="1.0" encoding="UTF-8"?>
<entry>
  <body>&lt;h2&gt;New Features&lt;/h2&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;Portuguese (Continental) has been added to the list of available languages.&lt;/li&gt;
&lt;li&gt;Balance Lookup can now be shown in any of our available languages.&lt;/li&gt;
&lt;li&gt;Online Enrollment now has a CAPTCHA field to stem or prevent bots from submitting junk entries.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Upgrades&lt;/h2&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Online&amp;nbsp;Enrollment&amp;nbsp;emails now say which campaign the new customer was added to.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;line-height: normal; font-family: Helvetica;&quot;&gt;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. &amp;nbsp;A work-around was implemented to the Excel export, where card #s and numbers over 15 digits are displayed as &quot;text&quot; in excel, while still retaining the ability to have sorting and calculations performed on them as though they are numbers.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;font-family: Helvetica;&quot;&gt;&lt;span style=&quot;line-height: normal;&quot;&gt;
&lt;p style=&quot;margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;&quot;&gt;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.&lt;/p&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Bug Fixes&lt;/h2&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;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. &amp;nbsp;To remedy this, rounding of points is now always down to the nearest smaller whole number.&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;line-height: normal; font-family: Helvetica;&quot;&gt;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.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;line-height: normal; font-family: Helvetica;&quot;&gt;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.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;line-height: normal; font-family: Helvetica;&quot;&gt;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. &amp;nbsp;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.&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</body>
  <created-at type="datetime">2009-05-14T10:29:20-04:00</created-at>
  <current-tags nil="true"></current-tags>
  <forum-id type="integer">16256</forum-id>
  <hits type="integer">227</hits>
  <id type="integer">36420</id>
  <is-highlighted type="boolean">false</is-highlighted>
  <is-locked type="boolean">true</is-locked>
  <is-pinned type="boolean">false</is-pinned>
  <is-public type="boolean">true</is-public>
  <organization-id type="integer" nil="true"></organization-id>
  <position type="integer" nil="true"></position>
  <posts-count type="integer">0</posts-count>
  <replied-by type="integer">Tiago Soromenho</replied-by>
  <submitter-id type="integer">34399</submitter-id>
  <title>News - May 14th, 2009</title>
  <updated-at type="datetime">2009-09-15T07:36:27-04:00</updated-at>
  <posts type="array"/>
</entry>
