Scheduled for Release on February 2, 2012 after 1:00 AM EST.

This is a routine scheduled version release containing completed feature enhancements and bug fixes.

Users Effected

This release will affect users of Helios Version 12 Enterprise and Helios Version 12 Desktop.

Required User Action

There should be no user action required for Enterprise users in order to update to this release. The Helios Auto-Updater will receive and apply any required file changes. The Helios Application may need to be closed and restarted in order to complete the update.

Helios Version 12 Desktop users will need to download the update and apply the update to each workstation. The Helios Application should be closed before applying the update.

Any Helios users upgrading from a version earlier than 12.3.0 should be aware that several of the cumulative updates included in this release will require additional user action. Please refer to the Resources section of this announcement for a list of the steps required after applying this update.

Overview

Helios Version 12.3.5 Release is a routine scheduled version release containing the accumulation of completed feature enhancements and bug fixes. It will be applied to the Enterprise Network as part of the scheduled overnight maintenance routine to begin on Wednesday, February 1 into Thursday, February 2. Maintenance affecting the regular operation of the Helios Application will not begin until after 1:00AM EST (10:00 PST) in order to avoid impacting subscribers during scheduled operating hours.

New Features

1. Clients who have an active EFT membership which is debited from a credit card can now be given the option to make Point of Sale purchases and charge the purchases to the credit card on file without the need to present the credit card for swipe. The feature may be enabled in the System Defaults on the Client Profile 1 tab. Once enabled, when the employee selected the credit card payment method, the card swipe screen includes a button to use the credit card on file instead of swiping a presented credit card. Privacy and PCI Compliance is preserved because the credit card information on file is never revealed when this option is selected. Additionally, if a fingerprint verification device is available the client can be prompted to verify their identity with a fingerprint scan in lieu of the credit card. If more than one active EFT is found, a screen will present the credit cards with the numbers obscured except for the last four digits for verification. The credit card types are also presented to assist in selecting the desired credit card. EFTs which have not yet begun, are frozen or suspended will not be available for use with this feature. It is important to note that while this feature is secure and compliant with current PCI standards, transactions processed using the credit card on file do not contain additional security information associated with a ‘card present’ transaction and therefore may be subject to a higher interchange processing rate due to ‘card not present’ approval policies. Please check with your merchant processing solution if you are unsure whether ‘card not present’ interchange rates will apply to your merchant account.
2. [Desktop Only] The credit card transaction report is now available for Helios Version 12 Desktop users employing merchant processing through the Zap Payments Network. The credit card transaction report is already available to Helios Version 12 Enterprise users.

Feature Enhancements

There are several feature enhancements included in this release. Some of these feature enhancements were released to Helios Version 12 Enterprise during the 12.3.4 update but are being included for release to Version 12 Desktop:

1. During the End Sale portion of the Point of Sale, the list of available Payment Methods will be presented to include only those payment methods available to the particular client. If the client has no available prepaid dollars or bonus bucks, the corresponding options will not be displayed. If the client’s profile has indicated to not permit payment by check or credit, the corresponding options will not be displayed. If split payment is selected, any payment methods not presented on the Payment Method screen will subsequently be disabled on the Split Payment screen.
2. Added the Avery 5267 Label option to the Inventory Labels and Inventory Wizard. The Avery 5267 offers the 4x20 label format for inventory barcode labels.

Bug Fixes

There are several bug fixes included in this release. Some of these bug fixes were released to Helios Version 12 Enterprise during the 12.3.4 update but are being included for release to Version 12 Desktop:

1. In the EFT Extraction process, the Post Offline submit button was inadvertently disabled during a previous update. The button and its functionality have been restored.
2. Users running Microsoft Windows 7 and Microsoft Internet Explorer 9 have been experiencing a script error when attempting to view a report. This is the result of a recent update released by Microsoft and has now been resolved in the Helios application.
3. In the Access Management rights option under the Special tab, selecting the deny option on the entry ‘Modify Client Suspend’ was not effectively prohibiting an employee from changing the client suspend option on the client account. This omission has been corrected.
4. When attempting to sell an EFT Enrollment which has been configured in the sales code to use the cutoff date + or – option, an error would prevent the completion of the sales code due to an unrepresentable date/time parameter. This error has been resolved.
5. In the Sales Code option, the Bonus Bucks days valid field could not be removed once it had been used. Instead of null, a zero was required and the resulting bonus bucks would be issued with zero days valid. The days valid field has been fixed to permit a previous value to be deleted and a null value to be accepted.
6. In the Package/Membership option, when the Step Matrix is employed there are specific scenarios in which the wrong bed type can be selected due to confusion in the logic which was unable to distinguish bed type ‘A’ from bed type ‘a’. The logic has been improved to prevent future confusion between similar key letter bed types.
7. In the EFT Resubmit option, the summary information being displayed was inaccurate as the result of an arithmetic error. After a resubmit, the summary information could display more than 100% processed which is not possible.
8. Fixed a reporting discrepancy in which the date and time stamp of transactions, particularly master edit transactions, would not agree between the client history and the daily sales report as a result of the computer time and the server time being recorded in different time zones.
9. In the Sales Code option, the Membership Pricing option contained an error in the logic in which an EFT membership set to begin a membership freeze on a future date would no longer receive membership pricing before the freeze has gone into effect. This logic has been corrected to provide members with Membership Pricing for the duration of time that the membership is active.
10. Users employing the Zap Payments Network have encountered problems with transactions in which the zip code format uses the USPS +4 format. This inconsistency has been fixed in the Helios application to prevent future discrepancies in zip code formats.
11. Users employing the Zap Payments Network have encountered problems with transactions in which the account holder’s name is not being submitted with the transaction. This issue has been fixed in the Helios application.
12. The Employee fingerprint register option has been removed from the Backoffice since a fingerprint device cannot be presumed to be available when using the Backoffice application.
13. The Prompt for Inventory check box has been removed from the Sales Code option since the function has never been made available, making the presence of the box confusing.

Known Issues

The following issue is known and will be fixed in a future release:

1. Helios Version 12 Desktop users employing merchant processing through the Zap Payments Network must have an active internet connection available at the time when the Helios application is opened in order for the application to connect to the Payment Gateway and confirm the merchant license is available. Currently if the merchant license cannot be confirmed at the time when the Helios application is opened, a warning message will be displayed warning the user that credit card processing services is unavailable. However, this warning does not require the user to disable the credit verification module and if a credit card transaction is attempted it is not able to be approved but no secondary warning message reiterates the feature is disabled. An update is being developed which will mandate the user disable the credit verification module before proceeding to the point of sale in order to avoid any opportunity to attempt to process credit cards. When the credit verification module is disabled, credit card transactions may be processed offline through a separate merchant terminal or by voice authorization with the merchant processing service provider.

For more Information

Helios Technical Support can be reached at 317-554-9911 or support@gohelios.com.

Resources

This Release notification includes release notes for Helios Version 12 Enterprise and Helios Version 12 Desktop. Version 12 Desktop users will need to download the update and apply the update to each workstation. The Helios Application should be closed before applying the update. If the hyperlink does not work, please copy and paste the following URL into the address bar of a web browser to download the update:

Important Information relating to version earlier than 12.3.0:

In response to the requirements of the Excise ‘Tan’ Tax, Helios Version 12.2.8 included several new options and features which require manual user action. These features will be installed with the Version 12.3.5 release but unless the manual user steps are taken following the update undesired consequences may result.

1. The major change to accommodate a variety of tax situations is the addition of the tax fields to the client EFT profile. Prior to this update, the EFT profile only included the monthly fee and all sales and excise taxes were calculated and added into the draft during the draft submission process. The 12.2.8 update provides fields for the sales and excise taxes to be stored along with the monthly fee on the EFT profile. Memberships that are not subject to either sales and/or excise tax can now be submitted within the same batch as taxable memberships instead of being separated into separate tax-defined batches. Tax fields associated with the Freeze Fee are also available in case the situation occurs that a tax rate would need to be applied to the EFT Freeze Fee.
2. The sales and excise tax options have been removed from the EFT Post Info tab as the applicable taxes are now reflected in the client’s EFT profile.
3. The new Apply Tax Utility tab is available in the EFT Management option in order to apply the appropriate tax(es) to existing EFT memberships. This step must be performed before the next EFT draft submission in order to apply the appropriate tax rates to the EFT profiles.
4. The Sales Code logic has been expanded to include applicable sales and excise taxes for EFT enrollments. The sales and excise tax can be specified on the EFT Enroll option and will be stored in the EFT profile along with the monthly fee in the newly provided fields. Every EFT Enroll Code must be updated to specify the membership’s appropriate tax(es) at the time of enrollment.
5. The TAN code includes intelligence which automatically waives the U.S. Excise Tax on bed types marked as UV-Free if the tan includes a walk-in or upgrade fee.