isd software release notes - maintenance page

ISD Software Release Notes

Chevron

Ruby/Sapphire/Topaz Suite Version CVXPAK 6.00.15

Release Level Production

EPSPAK Version 1.66.16

ViperPay Version 1.03.00

V910 Version 3.09.08

HPV-20 (Dell) Version 4.03.03 or higher

HPV-20 (Dell Rev. 4) Version 4.03.03 Rev. 4 or higher

HPV-20 (V950) Version 5.04.01 or higher

SMS Version 1.10.03

iOrder Kiosk Version 1.01.02

GSD Version 2.1

Loyalty Version 5.0

GemPro CPU Configuration CPU-6

Base Change Version 166

Shift Configuration 3-Shift/12-Shift

Previous Production Version 6.00.11

Reference Set CVX Reference Set: Version 6.00

Release Date August 1, 2012

Publication Date August 1, 2012

CVXPAK 6.00.15 Production VeriFone ISD Software Release Notes

2

ContentsAttention ----------------------------------------------------- 3New In This Release: 6.00.15------------------------------ 5

Resolutions ----------------------------------------------- 5New In Previous Release: 6.00.11 ------------------------ 5Installation Options ---------------------------------------- 46Upgrade Summary ------------------------------------------ 47Minimum Requirements ----------------------------------- 58Fuel Hardware Peripherals Supported ------------------ 60Ruby/Sapphire/Topaz Options Supported -------------- 76Important Information------------------------------------- 83


3

Attention

Additional Software and DocumentationSee the the VeriFone Premier Portal in the CVXPAK Sapphire and Topaz areas for additional installer software and documentation.

Electronic Manual Sale (EMS) and Store and Forward/Offline Authorization (SAF/OA)

When upgrading CVXPAK sites from version 5.XX.XX and earlier be aware that the Electronic Manual Sale MOP does NOT exist in versions 6.00.11 and later. EMS transactions are now automatically processed by the V910 EPS. If the imported payment configuration is older than version 6.XX.XX, the EMS MOP will become Manual Entry, which acts very similar to the old EMS MOP. Please do not import the MOP file for this reason and be sure to reassign former softkeys and Topaz buttons that were used for the old manual EMS MOP.

Automated EMS becomes active when a site is back online. In version 5.08, the site would have to manually send up, via EMS, all their special handled credit transactions that were done while offline. In version 6.00, this process is automated, and all transactions performed offline will automatically get sent to the host, once back online. In both software versions, the site needs to call and get an authorization number and imprint the card on a S-28 form. If a site would like to perform Credit sales while offline without having to call for authorization, they can start using Store and Forward/Offline Authorization (SAF/OA). The only exceptions while processing offline is that Debit and Gift Cards are not allowed and the maximum dispenser limit is usually lower, so the pump may stop sooner.

By default, all sites have SAF/OA disabled. If a site would like to enable SAF/OA they need to be referred to their Chevron Business Consultant (BC) to have this done. If a site does not know how to contact their BC then refer them to the Chevron Helpdesk RTSC 800-435-7277.

Terminal ConfigurationsThis software no longer supports the ability to use a Ruby and Topaz on the same Sapphire.

Cisco ASA 5505 RouterThe Cisco ASA 5505 router is required by Chevron to be used at the site with CVXPAK 6.00.00 and higher. The ASA 5505 router meets PCI requirements to provide firewall protection to segment the Chevron network, the POS system, and the customer network.


4

New (NACS) Product Codes********************************************************************************************

WARNING:Not updating the new NACS product codes, will cause the POS to report incorrect product codes to the network.

********************************************************************************************

The NACS product codes must be changed in the PLU File, Department File, Combo File, and (Fuel) Product Code Setup. If using Sapphire Management Suite, the following files are affected:

■ PLUs.xml — PLUs

■ poscfg.xml — Product Codes/Departments

■ fuelsite.xml — Fuel Configuration

Any previous product code lists or files cannot be imported to the POS, because they will be invalid.

MOP CodesWhen upgrading from version 5.XX.XX and older to 6.XX.XX, the MOP code 25 Electronic Manual Sale does NOT exist in the 6.XX.XX version. Do NOT use this MOP code.

Topaz Report Configuration (Grouplist)When upgrading from version 5.XX.XX and older to 6.XX.XX, do not import the "grouplist" dataset. It is required to reconfigure any Topaz reports manually.

V950 Installation and ConfigurationNOTE: If your site has CVXPAK v6.00.15 already installed and currently running

HPV-20 v5.02.00 on the V950, a full installation of CVXPAK v6.00.15 is NOT required, only upgrading the V950 is required.

The installation of CVXPAK 6.00.15 requires HPV-20 / V950 image software updates and corresponding Security Overlays as follows:

■ HPV-20 5.04.01 Production Software Release

■ HPV-20 Security Overlay 1.15.00 for HPV-20 5.04.01

■ PDReceiver Overlay (Located within CVXPAK 6.00.xx Suite Production CD)

■ CVXPAK V6.00.XX Production Suite CD

It is required that you follow the installation and setup instructions for above software packages found in the CVXPAK V6 Installation and Setup Guide available on VeriFone Premier Portal.


5

New In This Release: 6.00.15

NOTE: Versions 6.00.12 through 6.00.14 were skipped.

RESOLUTIONS

Ruby/Sapphire/Topaz

Dispenser Card ReadersPreviously, the Secure PumpPAY and Wayne DCR graphic display ROM could not be configured through SMS. This was corrected.

Network 1. Previously, network transactions were taking longer than expected at the

DCR. This was corrected.

2. Previously, there were corrupted STAN transactions in the Unconfirmed Log of a batch. This was corrected.

SystemPreviously, an error in the Auto Upgrade caused registration problems. This was corrected and now if the problem reoccurs, the alarm message “E9068 NOTIFY HELPDESK” displays on POS workstations.

New In Previous Release: 6.00.11

CHEVRON FEATURES/ENHANCEMENTS

NACS Product Code SupportThe application now uses the 3-digit NACS product codes. The product codes can be listed at the POS terminal.


6

File BroadcastOnce the Chevron PD-Receiver Overlay is installed on the HPV-20, software upgrades can be delivered to the sites via the Chevron network instead of using Suite CDs. The Auto Upgrade functionality then allows sites to initiate an install without the need for a VeriFone Authorized Service Contractor (VASC).

Network ReliabilityThe application now captures and sends communication outages to the Chevron Host Authorization Network for troubleshooting and statistical purposes.

Invoices NumbersInvoice numbers are now linked in the batch report.

Chevron / Texaco Graphics at DCRsThe Chevron graphic logo now displays in the lower right-hand corner of a graphics DCR during the payment and fueling promotion screens.

Automated EMSThe transactions stored in the “Pending EMS Repository” will now be managed by the EPS. The EPS will send the transactions to the Chevron Host Authorization Network in a First In First Out order. This is considered the automated EMS process.

Partial Approval Message at the DCRThe EPS now provides the ability to display a partial approval amount at the DCR returned by the Chevron Host Authorization Network before allowing the customer to begin fueling at the DCR.

Debit and Credit Cash BackChevron now offers cash back with credit and debit cards. This feature is controlled by the parameter download and only applies to card that are currently support cash back. See Chevron for supported cards. Cash back with prepaid cards is not supported. The credit card transaction must be initiated indoors at the POS. The parameter “Allow without sale” has been added to the payment file (paymentcfg.xml) for Debit, Credit, and EMS MOPs. Debit Configuration has been removed from Network Manager > Configuration in the Ruby terminal and now can only be accessed through SMS.


7

RFID ContactlessRFID Contactless support has been added for the OP 4100, inside at the MX 800 Series PINpad, and Gilbarco DCRs.

ENHANCEMENTS

Ruby/Sapphire/Topaz

Car Wash

Affordable Car Wash

After fueling at the DCR, the Affordable Car Wash feature will prompt the customer for car washes that keeps the total sale within the approved card limit.

Dispenser Card Readers

Approval Amounts

The DCR will now display a network approved amount when the approval amount is less than the requested amount.

Gilbarco

DCR debit transactions using the Gilbarco EPP keypad without a GSM are now supported.

Secure PumpPAY and Dresser/Wayne

1. Inside Cash and Inside Credit softkey payment options have been added on Secure PumpPAY and graphic Dresser Wayne DCRs.

2. The debit PIN prompt message “ENTER PIN” has been modified to match the graphics fleet card prompt messages on Secure PumpPAY and Dresser/Wayne DCRs.

ZIP Code

The DCR now prints the store’s ZIP code on the receipt header. The ZIP code is entered in Network Manager > Configuration > Dealer Configuration.

Fuel ManagerAfter prepaying with cash inside, a customer can now receive a fuel receipt at the DCR. (Fuel underruns still require the customer to see cashier.) The new parameter, “Cash Prepay Receipt Outside [Y/N]?”, is found in Fuel Manager > Site Parameters > DCR Site Parameters.


8

ManagerThe number of taxes has been increased to eight definitions and the number of ID checks has been increased to six definitions across all platforms.

Network

Authorization

The authorization time for DCR transactions has been reduced when full service attendant or Mannatec cards are used.

Cash Back

The application now supports cash back for fuel prepays and cash back without sales.

Financial Requests

The Clerk ID and Cashier Level is now included when sending Financial requests to the network.

Sales

Autodisapproval

The autodisapproval feature at Fuel Manager > Pump Configuration is now supported for fast credit transactions.

Safe Drop Corrections

Safe drops have been enhanced to allow corrections. If a cashier enters the wrong amount by mistake, the Safe Drop Report will be incorrect. This enhancement, which is available only to the store manager or a person with a higher security level, allows the safe drop amount to be corrected and reported.

On the POS, security is set using the “Safedrop correction security level” parameter at Manager > Configuration > Sales Config. To correct the safe drop amount, the store manager enters the original ticket number along with the correct safe drop amount at Sales > Other Func key > Safe Drop Correction.

New Alarm messages for Safe Drop Corrections:

E1298 INVALID SAFE DROP TICKET NUMBER

E1299 SAPPHIRE REQUIRED

E1300 SAFE DROP ALREADY CORRECTED

In Sapphire Management Suite (SMS), the security level for making safe drop corrections is set using the “Safe Drop Correction Security” parameter at Configuration Manager > Manager > Sales. The store manager can then make the corrections on the Ruby or Topaz.

The Safe Drop Report includes the correct and the incorrect safe drop amounts.


9

System

Cash Drawer

The cash drawer now opens only if a non-zero safe drop related MOP is present in the Electronic Cashier Register (ECR).

Fuel Price Display

A single fuel product can now be associated with more than one fuel price display ID. The primary purpose for this enhancement is to allow the cash and credit price for one fuel grade to be shown on a fuel price display.

Gemstall

1. In Gemstall, the DCR-specific keypad choices have been divided into two groups under the DCR Keypad Gemstall option.

2. A site brand Gemstall option has been added to support Tokheim and Schlumberger debit prompts.

3. A site brand Gemstall option has been added to support Tokheim and Schlumberger debit prompts.

OpenSSL 0.9.8L

The application supports OpenSSL 0.9.8L.

PA-DSS

Sensitive card information for fuel transactions is now secured during time period between authorization and completion.

PINpad

The application uses MX 800 Series PINpads with ViperPay. These PINpads communicate to the EPS directly over Ethernet instead of RS-232 serial. The Gemstall option for PINpad has been removed.

Ruby/Sapphire

Dispenser Card Readers

Keypads

When a DCR has a single [Pay Inside] key on a 4 x 5 keypad, the default MOP is used for the fuel price level when approving the dispenser.


10

System

Functions

The following Ruby/Sapphire functions can now be accessed through normal security levels.

■ Clear Pumps On Hold

■ Car Wash Display Order

■ Reset Tank Delivery

Gemcom

The PLU promotion Gemcom dataset no longer reads the PLU file for every record.

Sapphire

Reports

Fuel Price Change Report

Support has been added for the Fuel Price Change Report on the Sapphire to provide data on a hourly basis. The details of the report include:

■ Date of Price Change

■ Price Change NACS Product Code

■ Service Level

■ New Price

■ Time of Price Change

Sales

Money Order

The Sapphire now supports and prints Moneygrams from the Travellers Express money order terminal.

Sapphire Generic Loyalty

Topaz Support

Sapphire Generic Loyalty now supports Topaz.

Validation

Validation has been added to the “date” field of the Loyalty refund authorization message.


11

Sapphire Management Suite (SMS)

Configuration

1. If the Breakpoint tax table is enabled in Sapphire Management Suite (SMS) Configuration Manager > Payment > Tax Rates, the Breakpoint table can now be printed from Tools > Configuration Data.

2. A security level may now be set in SMS for correcting an error during a transaction with the [ERROR CORR] key on the Topaz.

3. Sapphire Management Suite has been enhanced to make information that is shared between forms available for immediate selection. For example, if a department is added in the Configuration Manager > Manager > Merchandise Manager > Department form, the open Price Lookup Manager (PLUs) form is immediately updated and the new department can be selected. Previously, the PLUs form would have had to have been closed and reopened to see added or edited information.

Import and Export

The Import and Export functionality of the Sapphire Management Suite (SMS) has been enhanced to populate the file list according to the users’ login permissions.

Network

Cookies that print to the Java Console are now masked when the Network Applet is pulled from SMS.

Report Navigator

1. The EBT MOP has been added to the Cash Controls section of SMS > Report Navigator > End of Day.

2. The Network Journal Browser and Network Journal Report has been modified to support multiple network payment lines within a single transaction. This handles split tender with one or more prepaid cards and a credit or debit card.

System

Fuel Inventory Data and Rents Sales Data

The Sapphire can now send Fuel Inventory Data and Rents Sales Data to the EPS on demand on a network period close.

HPV-20

The HPV-20 UpTime now performs the Sapphire CPU-5 to CPU-6 conversion.

Https

When accessing index.html directly, such as http://sapphire/NetworkJournalBrowser, the protocol is now changed from “http” to “https.”


12

Journal Browser

Instructions have been added to the Journal Browser online help on how to access the Network Journal Browser.

Money Order

The Sapphire Site Controller now supports money order devices via the “Newpro” board ports (previously, only the GemPro com ports were supported). Before installing the application onto the Sapphire, determine which money order device should be connected to the system.

■ Western Union ICE6000 Terminal (Ethernet enabled device)

The following information is needed for installing this option:

– The terminal ID

– The terminal’s IP address

The following two money order devices have been added:

■ Western Union T7E Terminal (Serial port device)

The following information is needed for installing this option:

– The terminal ID

– The NewPro port number (1 - 16)

■ MoneyGram/TravelersExpress DeltaNetwork terminal (Serial port device)

The following information is needed for this option:

– The terminal ID

– The NewPro port number (1 - 16)

During the application installation, the prompt “option codes or press enter to restart the system” displays. Enter only one of the following:

NOTE: If there are no money order devices connected, press [ENTER] to continue with the installation.

If an option was entered, answer all prompted questions with the information from above. After entering the information, press [ENTER] when prompted to restart the system.

Option Codes Description of this option

wuice Western Union ICE6000 Terminal

wut7e Western Union T7e Terminal

mgdelta MoneyGram/TravelersExpress Delta Network Terminal


13

Site Asset Data

Sapphire and Topaz now supports collecting site asset data and forwarding it to the EPS. Also, SMS will display and print the site asset data. The site asset data will include information about the site and the details of each terminal.

Synchronization

The GemPro time now synchronizes automatically with NewPro time at the top of each hour.

TLog

1. The TLog has been updated to secure sensitive encrypted information to meet PA-DSS requirements.

2. TLogs have been enhanced to allow the user to configure number of days the TLog is stored. The maximum allowable amount is 365 days. Also, the deletion of TLogs has been enhanced to meet PA-DSS requirements.

White List Processing

White List Processing is a new feature that enables the Transaction Set Archiver server to connect to the Sapphire to retrieve data after receiving the event notification through a proxy server.

Topaz

Network

Incomm TOR Processing

Incomm TOR processing and open denomination product support to Incomm is now supported.

Reports

Corrections

The Topaz Cashier Report and Safe Drop Report have been modified for electronic safe drops and safe drop corrections.

Flash Reports

1. The FP Hose Test Report can now be run from Topaz Flash Reports.

2. Topaz Flash Reports have been enhanced to include PLU Promo Report, Deal Report, and POP Discount Report.

3. The PLU Exception Report, Safe Drop Report, and POP Definition Report can now be printed from the Topaz.


14

In-House Accounts

In-House account names now print on the Topaz Pay In receipt and SMS House Account Report.

Sales

Car Wash Pay Point

Customers at sites with Sapphire and Topaz POS can now pay for a car wash at the car wash entry system or bay using cash or any card type (credit, debit, fleet, and so on) supported by the application. This new feature is configured on the Car Wash Pay Point Configuration form in Sapphire Management Suite (SMS) Configuration Manager > Device Manager > Car Wash Pay Point Configuration. Up to four (4) car wash bays can be configured and up to four (4) car wash packages may be made available for purchase at each bay. A new reporting period, Car Wash Pay Point period, has been added, which is used in the Car Wash Pay Point Reconciliation Report. The report generally covers several days and shows the amount collected and the amount dispensed as change.

Discounts

Two additional options have been added for amount and percent discounts in the touch-to-modify menu that appears when a line item is touched on the Topaz.

PA-DSS

The PA-DSS secure user functionality has been implemented on the Topaz. Sensitive functions can only be accessed using a secure used ID and password.

PLU Not Found Department

A new feature has been added to disallow 'PLU not found' sale on the Topaz. Currently, if the “PLU Not Found Department” parameter is set to ‘0’, the Topaz prompts the user to select a department from a list of all configured departments. A new Sales Configuration parameter has been added that determines whether to prompt for a department on each PLU not found sale. If this property is disabled and the Sales Configuration > “PLU Not Found Department” parameter is ‘0’, the Topaz disallows the PLU sale and does not prompt the user for “PLU not found department” to be used on the item during the transaction.

Taxes

The Topaz now has an option to separate each tax configured instead of combining all the taxes together.

System

Cashier Display

The Topaz cashier display now shows the authorized amount for partial credit authorization transactions.


15

Corporate User

The “Corporate User” is now available for site use on the Topaz.

Electronic Safe

Electronic Safe is now supported by Sapphire for use with Topaz. With an IP connection to the safe hardware, the entered safe drop amounts are retained and totaled to compare with the total amount in the safe upon shift close. Electronic Safe is configured in Sapphire Management Suite (SMS) > Configuration Manager > Device > Electronic Safe. The Electronic Safe has an assigned ID that must be selected before the specific IP information is entered on the form. A combination of manual and Electronic Safes may be used, but the E-Safe Configuration form allows “Use E-Safe Only” to be selected. The unique Employee Safe IDs that are entered are mapped to the cashier IDs.

The E-Safe Cashier Report, generated at cashier close, reconciles each cashier’s safe drop amounts with amounts recorded on the Electronic Safe. The E-Safe Day Report, generated at shift or day close, reconciles all cashiers’ safe drop amounts with amounts recorded on the Electronic Safe for the period. Whenever money is removed from the safe, an E-Safe Content Report is automatically stored. The reporting period (Period 1 = Shift, Period 2 = Day) can be selected in SMS > Configuration Manager > Report Manager > Report Configuration.

Modifiers

The dismissal of the modifier menu can now be enabled or disabled based on the property setting “topaz.sales.allowDismissalOfModifierMenu” in Sapphire Properties. An entry is made in the log if the modifier menu is dismissed.

Partner

Line rotation support has been added for the Partner customer display CD7220 and CD6420.

Support

The Sapphire/Topaz POS solution now supports up to 12 Topaz workstations.

RESOLUTIONS

Ruby/Sapphire/Topaz

Cash AcceptorsPreviously, if the [Cancel] key pressed while the bill was stacking, the bill was not counted. This was corrected.


16

Dispenser Card Readers1. Previously, a DCR prompted for PIN for a Mannatec swipe even though

“No” was selected for “Debit Y/N?”. This was corrected.

2. Previously, the POP Discount codes caused the DCR Help and Cancel functions to be handled incorrectly. This was corrected.

3. Previously, when the Armed Forces Restriction parameter was enabled and the “Are You Authorized [Y/N]” message appeared on the DCR, the “Yes” or “No” was not working. This was corrected.

4. Previously, the Clear function was not working at the DCR if the POP Discount code was incorrect. This was corrected.

5. Previously, the Gilbarco Graphics CANCEL key sent a “Timed Out” message to the network instead of an “Aborted” message. This was corrected.

6. Previously, the Canceled and Timed Out Mannatec prompts on Gilbarco and Tokheim DCRS were not canceling the transactions. This was corrected.

7. Previously, when a proprietary card was swiped at the DCR and the Cancel key was pressed at the Debit Y/N prompt, the DCR displayed incorrect messages. This was corrected.

8. Previously, the incorrect outside DCR cancelation message was sent to the network. This was corrected.

9. Previously, when the Cancel Key was pressed during the “Enter PIN” prompt, it required additional cancel key presses before the transaction canceled. This was corrected.

10. Previously, the outside cancellation was sent without any data to the network. This was corrected.

11. Previously, Mannatec cards were not recognized at Gilbarco DCRs. This was corrected.

12. Previously, when the cancel key was pressed at a DCR prompt, it did not cancel the transaction. This was corrected.

13. Previously, when downloading to a single Tokheim graphics DCR, the DCR locked up.

14. Previously on Secure PumpPAY and Dresser/Wayne DCRs, when one DCR transaction was in progress and swiping a card incorrectly three times on another DCR, caused the swiped DCR display did not return to the idle prompt. This was corrected.

15. Previously, a potential bootfix would occur on the Ruby terminal when loading the Dresser/Wayne graphic logo on the DCRs. This was corrected.

16. Previously, when downloading to a single Tokheim graphics DCR, the DCR locked up.

17. Previously on Secure PumpPAY and Dresser/Wayne DCRs, when one DCR transaction was in progress and swiping a card incorrectly three


17

times on another DCR, caused the swiped DCR display did not return to the idle prompt. This was corrected.

18. Previously, prompts longer than 16 characters on Dresser/Wayne DCRs caused the prompt to be incorrectly displayed. This was corrected.

19. Occasionally, the “No Printer Response” message would display on the Ruby alarm line for Secure PumpPay or Dresser/Wayne sites even though the receipt printed at the DCR. This message was removed.

20. Previously, the Armed Forces prompt did not have Gilbarco graphic soft keys available for Yes and No. This was corrected.

21. Previously, when the Gilbarco PAM was power cycled and the battery was bad, the PAM lost its 6-digit currency configuration and reverted back to 5-digits. This was corrected and now the configuration isre-sent to the PAM from the POS.

22. Previously, Tokheim DPT Poll Errors may remain on alarm line after communication was restored. This was corrected.

23. Previously, fuel and DCR alarms would remain on the POS even after communication was restored. This was corrected, and now they disappear.

24. Previously, when the Default Service Level was set to “MINI” for Gilbarco dispensers, the fuel grade at the end of a transaction was incorrect. This was corrected.

25. Previously, Secure PumpPAY on Dresser/Wayne DCRs displayed only four of eight car washes. This was corrected.

26. Occasionally, the prompt for each menu of car washes on Gilbarco and Tokheim graphic DCRs displayed briefly. This was corrected and now each menu displays for a minimum of 30 seconds.

Network1. The Journal Masking parameter at Network Manager > Configuration >

Dealer Configuration has been removed and only the first six and last four digits of the account number display on journal.

2. Previously, the inside proprietary network transactions were not updated in the Proprietary Report. This was corrected.

3. Previously, open batches were auto forced settled. This was corrected.

4. Previously, when there were no pending transactions, two batch folders displayed in the current directory after a batch close. This was corrected.

5. Previously, the EPS formed an incorrect DCR time-out response. This was corrected.

6. Previously, when the EPS was offline, the Station ID has to be re-entered to bring the EPS back online. This was corrected.


18

7. Previously, the EPS sent a malformed DE 63 if the quantity was zero but the price was non-zero. This was corrected.

8. Previously, the POS sent a zero dollar completion 2220 instead of a reversal 2420 for a canceled indoor prepay. This was corrected.

9. Previously, manual entry still prompted for Credit or Debit on the PINpad. This was corrected.

10. Previously, offline authorized transactions took longer to complete if the site remained offline for a long duration. This was corrected.

11. Previously, the Electronic Batch Close message was sent to the host before the last sale was completed for the batch causing the host to reopen the batch. This was corrected.

12. Previously, the 2644 / 899 response message with DE 72-56 optional reply message received an E16 packet error. This was corrected.

13. Previously, with the RAN Flag Off, the POS allowed administrative transactions to be sent to the host. This was corrected.

14. Previously, if the EMS was older than eight days, EOD would not close preventing the EMS from being purged.

15. Previously, outside VISA online transactions were approved with the DCR fueling limit set to zero. This was corrected.

16. Previously, when VISA was used at the DCR, it allowed a fueling limit of zero. This was corrected.

17. Previously, the Store and Forward count included “all + admin.” This was corrected and now it only contains the approved Store and Forward transactions. This was corrected.

18. Previously, the Sapphire was not adhering to the OA/SAF CAT Velocity limit set by the SAFTABLE in the PDL. This was corrected.

19. Previously, an offline transaction was not following the initial default throttle value in the PDL when sent to the host. This was corrected.

20. Previously, offline Store and Forward transactions were not following the offline authorization throttle sent back in the 2230 DE #72. This was corrected.

21. Previously, the POS was not purging unresolved offline approved transactions. This was corrected.

22. Previously, a cancelled Store and Forward DCR transaction caused problems with the “Offline Authorized” Batch Report. This was corrected.

23. Previously, offline transaction received an “890 time out” response and is journaled in the unconfirmed logs. This was corrected.

24. Previously, the “899 RAN Flag Off” message was not using fallback on authorization and capture. This was corrected.


19

25. Previously, on Topaz site configurations, the terminal type in the 2804 message reported as “VSAPH DE#41” instead of “VeriFone Topaz.” This was corrected.

26. Previously, the “2304 RENTS” message was not formatted correctly per the specification DE 72. This was corrected.

27. Previously, the EMS Unconfirmed Log Batch Reports was missing both ASSOC INV# and EMS INV# for every transaction. This was corrected.

28. Previously, an invalid Invoice number (00) was sent in a financial transaction. This was corrected.

29. Previously, the Topaz XL printed a receipt that contained a split tender using two gift cards and an older fleet card network transaction. This was corrected.

30. Previously, when a American Express card was manually entered, the “2200 Authorization and Capture” message received a E15 Card Error. This was corrected.

31. Previously, when a transaction was entered manually in an offline condition, it was not approved. This was corrected.

32. Previously, the first offline approved transaction was placed into the Credit Batch Report and the EMS Batch. This caused the transaction to be added twice. This was corrected.

33. Previously, when logging into “EPS Secure Reports”, the message “Function Not Supported” was displayed. This was corrected.

34. Previously, when the Host returned a 0005 action code in DE 39 and the card type did not allow offline authorization, the transaction was denied by the EPS instead of using exception processing. This was corrected.

35. Previously, a “call 4 auth” was not performed by the POS when action code 0004 was returned from the Host. This was corrected.

36. Previously, an MasterCard prepay offline approved transactions was sent to the Host with the wrong receipt flag. This was corrected.

37. Previously, the POS was not masking track data in non-original transactions. This was corrected.

38. Previously, the ViewCards webpage displayed the incorrect title for the card table. This was corrected.

39. Previously, the ViewCards webpage displayed the incorrect VISA title in the card table. This was corrected.

40. Occasionally, the RENTS data was not sent to the network. This was corrected.

41. Previously, when Mannatec transactions allowed manual entry, the EPS sent a “Manual Entry Not Allowed” message to the POS after the transaction completed. This was corrected.

42. Previously, the “Stn#” on indoor and outdoor receipts was missing the first three-digits in the card information section. This was corrected.


20

43. Previously, POS workstations were unable to exit at the “Call for Authorization” message. This was corrected.

44. Previously, an error occurred if the trackdata was misread. This was corrected.

45. Previously, the “Outdoor Cashier Message Supported” option was not found on EPS Admin Web Page. This was corrected.

46. Previously, the incorrect error message was displayed when the host was disabled before the confirmation response was received for the PDL download. This was corrected.

47. Previously, the EPS was not sending Data Element 104 sub element 20 in the Gift Card Activation and Reloads. This was corrected.

48. Previously, batches older than 31 days were not deleted. This was corrected.

49. Previously, “Card Not Allowed” was not displayed when an unsupported card was swiped. This was corrected.

50. Previously, when communication was offline and the Sapphire was rebooted, the RAN FLAG was disabled. This was corrected.

51. Previously, Network Batch Close message screen displayed only the last 2-digits of the batch number even if the batch was 3-digits long. This was corrected.

52. Previously, multiple entries appeared for the same transaction in the “Credit Unconfirmed Log Batch” section. This was corrected.

53. Previously, the gift card balance was not displayed on the POS during the gift card activation and reload. This was corrected.

54. Previously, the credit totals printed in batch reports were incorrect if the batch had “Reversal” transactions. This was corrected.

55. Previously, the POS was unable to process Track 1 American Express cards. This was corrected.

56. Previously, the EPS was not sending data element 104 sub element 20 in the gift card activation and reloads. This was corrected.

57. Previously, the POS was not adhering to a response from the network to process transactions offline. This was corrected.

58. Previously, the Change Price data was not sent to the network. This was corrected.

59. Previously, the POS terminal sent multiple reversal transactions after it came back online. This was corrected.

60. Previously, the POS system took 10 minutes to establish communication after it was lost with the network. This was corrected.

61. Previously, the application version was reported incorrectly in the echo message to the network. This was corrected.


21

62. Previously, the POS reported the gallons incorrectly to the network if under one gallon was dispensed. This was corrected.

63. Previously, the “Card Expired” message displayed after only one bad card swipe for Track 1 only credit cards. This was corrected.

64. Previously, the POS communication parameter was not enabling with the admin message. This was corrected.

65. Previously, the fuel sales hourly message 2304 sent only one grade if one grade was sold during the hour period. This was corrected.

66. Previously, no indication was displayed on the POS terminals when the Offline Authorization port could not connect. This was corrected.

67. Previously, if the Offline Approval Dollar Limit was set to a zero dollar amount by the PDL, then it could only be changed manually at the POS terminal. This was corrected and now the value is set at one dollar even if the PDL contains a zero amount.

68. Previously, when a debit card that did not follow mod 10 checks was swiped at the Credit/Debit prompt inside, “E15 Card Error” displayed. This was corrected.

69. Previously, the outdoor completion 2220 message on an outdoor 2100 message receipt parameter was a ‘0’ instead of a ‘2’. This was corrected.

70. Previously, the PDL specified an “R” for Read Track Two of the mag stripe, but the POS ignored it and the network rejected the transaction. This was corrected.

Reports1. Occasionally, offline sales displayed in the Pending EMS Summary Batch

Report, but not in the Pending EMS Detail Report. This was corrected.

2. Previously, the NW Batch Detail Report printed zeros. This was corrected.

3. Previously, when there was no Pending EMS Report, the POS displayed “Chevron Initialization Error.” This was corrected.

4. Previously, the cash MOP was displayed in the “ALL DCR Report” for non-cash acceptor sales This was corrected.

5. Previously, the department sales totals were not the same as the sales totalizers. This was corrected.

6. Previously, errors in a batch caused the Close Daily to fail and credit processing errors. This was corrected.

7. Occasionally, large negative numbers displayed in the Department Report. This was corrected.

8. Previously, the Network Batch Summary totals did not match the totals in the Network Batch Detail. This was corrected.


22

9. Previously, when the Close Daily was performed successfully and then the Batch Report was printed, the Batch Report displayed “Close Pending”. This was corrected.

10. Previously, the host total and host date was not displayed in the Electronically Closed Credit/Debit Batch section if the batch close was sent from Store and Forward. This was corrected.

11. Previously, the Activation/Reload Unconfirmed Log section does was not listing the unconfirmed activation/reload transactions on the printed Network Batch Detail Report and Terminal Batch Detail Report. This was corrected.

12. Previously, the Close Daily locked up due to continuous journal entries sent by the EPS to NewPro for a host offline state. This was corrected.

13. Previously, the Fuel Sales Hourly message had the incorrect starting hour of ‘23:00.’ This was corrected.

14. Previously, The Debit Batch Total Approved of the Network Batch Detail Report was displayed as “Debit Batch otal Approved.” The was corrected and now it displays correctly.

15. Previously, a Mannatec DCR transaction with a car wash promotion displayed the actual price of the car wash in the proprietary product report section of the shift report instead of the discounted price. This was corrected.

16. Previously, the POP Discount totals for Pre-dispensed and Post-dispensed amounts were not reported correctly in the All Registers section. This was corrected.

17. Previously, if a fee was assigned to a PLU and was sold as part of a Mix ’n Match, the PLU and Summary totals were incorrect. This was corrected.

18. Previously, if the last transaction in the period was a fast credit with merchandise, it was not added in the close period. This was corrected.

19. Previously, the count and amount of the overrun was not reported in the memo section of the Summary Report. This was corrected.

20. Previously, when there was a fuel overrun on a fast credit prepay, it caused the fuel deposit department and the category report to be negative. This was corrected.

21. Previously, Mannatec transactions were printing the product code “split tender” in the shift report when it was cancelled at the DCR. This was corrected.

22. Previously, card names were not printed correctly in the Proprietary Report. This was corrected.

23. Previously, when the Cashier Report and Summary Report were printed from both Ruby and Sapphire Management Suite Report Navigator, the void tickets amounts were different. This has been corrected.


23

Sales1. Previously, the ForcePost and PostEntry MOPs were not working correctly

when the POP by Card Type parameter was enabled. This was corrected.

2. Previously, when a tax was exempted for a PLU during a prepay, the tax was applied at completion. This was corrected.

3. Previously, when merchandise was entered in a Fast Credit with Merchandise transaction, the merchandise was not included in the total. This was corrected.

4. Previously, when a tax was exempted for a PLU during a prepay, the tax was applied at completion. This was corrected.

5. Previously, when a fuel prepay was entered as cash and tendered as credit, the POS sent a sale completion and not a preauthorization to the network. This was corrected.

6. Previously, “MUST TENDER TO CASH” was not displayed if a negative department transaction contained a zero dollar completion. This was corrected.

7. Previously, a manual discount applied during a fuel prepay was not accounted for during prepay completion. This was corrected.

8. Previously, after the cashier pressed the credit MOP, the PINpad requested information from the customer. If the customer took longer than 45 seconds before entering the information, the PINpad displayed the approval, and then the POS took 43 seconds to complete the transaction. This was corrected and now the POS completes the transaction immediately after the PINpad displays the approval.Previously, when “Fuel Only” fleet cards were used in split tender sales, the error message “INVALID PRODUCT” displayed. This was corrected.

9. Volume prepays greater than 100 gallons are now allowed on Gilbarco dispensers.

10. Previously, when a pump prepay failure occurred due to fuel communication errors, the pump could remain in a reserve state. This was corrected.

11. Previously, a prepay transaction on a pump could not be moved to another pump with the handle removed. This was corrected.

12. Occasionally, a fuel sale would become stuck and it gave a false impression that it was a fast credit sale. This was corrected.

13. Previously, POP by card type would incorrectly give a discount to a card following a qualified card. This was corrected.

14. Previously, with POP Discount set at “Coupon Only”, the coupon did not print at the DCR. This was corrected.

15. Previously, if a percent discount using the [DISC] key was applied to a PLU having a promotion, the total transaction amount is different in both the Ruby and Topaz. This was corrected.


24

16. Previously, for a PLU with multiple modifiers (0,1,2,3), if the “Not For Sale” flag was set for modifier 1, you could not use the [MODIFY] key to perform a sale of modifier 1 or the modifiers greater than 1. When the system encountered the “Not for Sale” flag, it terminated the sale. This was corrected. Now, if that flag is set for modifier 1 and you press the [MODIFY] key, it skips over modifier 1 and goes to the next modifier.

17. Previously, invalid dollar signs could appear at any position on the 32-icon display. This was corrected.

System1. Previously, a new V910 had to be rebooted in order to set the Site ID. This

was corrected.

2. Previously, when a newer version replaced an older version of EPS software, the Station ID or SAC had to be re-entered even though it displayed correctly. This was corrected.

3. The transaction file download mechanism has been removed from the EPS web page.

4. Previously, the PINpad screen is not updated with “Please Wait” after the Credit or Debit prompt was answered by the customer. The credit or debit prompt remained on the screen. This was corrected.

5. This use of the FTP protocol by Sapphire GemPro, Ruby controller, and workstations while the application is running in a non-upgrade mode (e.g., sales, manager, reports) has been eliminated.

6. Previously, the PLU Totals were not cleared during the Auto Upgrade. This was corrected.

7. Previously, the Auto Upgrade incorrectly detected an open report period when prompting operator. This was corrected and also name of reporting period is now displayed instead of the period number.

8. Previously, the POP was not displaying “WAITING FOR CASHIER” after the card was swiped three times for a bad mag-stripe. This was corrected.

9. Previously, after “Sale Declined” was displayed, errors that followed were displayed for less than one second. This was corrected.

10. Previously, when a card type was assigned to a POP discount definition and then the card type was deleted from the network card parameter table, another card type was assigned to the existing POP discount definition. This was corrected and now the POP discount definition is not assigned a card type and will not function.

11. The “Legacy Loyalty” option has been removed from Gemstall.

12. Previously, when the fuel controller returned an incorrect fuel grade for a transaction, this caused the POS terminal to continuously request the transaction. This was corrected.


25

13. Previously, the POS did not silence the buzzer when the calling pump was viewed with the “View buzzer off” parameter set to ‘Y.’ This was corrected.

14. Previously, sensitive data that may have been left inside temporary data files for non-DCR fast credit transactions has now been removed to meet PA-DSS requirements.

15. Previously, debit receipts printed a signature line. This was corrected.

16. The Gemstall option “Select Media Graphic Dcr” has been removed.

17. Previously, after a fuel price change, the “Fuel Prices Pending” alarm message remained. This was corrected.

18. Previously, when Gemstall was used to install an application, without using an automatic CPU5 to 6 Upgrade, on a CPU-6 Sapphire and the HPV-20 feature was selected, the files on an existing CPU5-formatted JEIDA card were erased. This was corrected.

19. Previously, the Apache log was filling up with “file-not-found” entries when Gemcom32 1.08.07 or later was used. This was corrected.

Ruby/Sapphire

Dispenser Card Readers1. Previously, cash prepay receipt was prompting incorrectly even though the

prepay transaction was fully dispensed. This was corrected.

2. Previously, partial SPP/Dresser Wayne messages were displayed while the DCR was being authorized for fueling. This was corrected.

3. Previously, postpay transactions initiated at the DCR were approved with the incorrect limit. This was corrected.

4. Previously, the message “Downloading crind tables” continued to display on Ruby terminals after DCRs had been initialized. This was corrected.

5. Previously, when Dresser/Wayne graphics were enabled along with the Enable Debit Y/N prompt in Fuel Manager > Site Parameters > DCR Site Parameters, pressing NO in response to the prompt “Is This a Debit Card?” would occasionally cause the credit transaction to not complete. This was corrected.

NetworkPreviously, a network message event in the detail of the SMS Transaction Viewer displayed as “N2002 UNKNOWN” for Mannatec transactions from the Ruby terminal. This was corrected.


26

Reports1. Previously, credit cash backs were reported as “DEBIT” cash backs in the

Ruby reports.

2. Previously, the Ruby displayed the “Please update POP Card List” message during a Gift Card Activation/Reload. This was corrected.

3. Previously, items sold as part of a combo were not reported on the PLU Report, Department Report, or Category Report. This was corrected.

Sales1. Previously, when a PLU had no assigned modifiers, the parameter “May

be sold” was set to ‘N’, and the sale of the PLU was attempted, it caused an error and a potential bootfix on the Ruby terminal. This was corrected.

2. Previously, the tax was calculated incorrectly on a Ruby if the food stamp was tendered after the special discount MOP. This was corrected.

3. Previously, the “Dollar” count increased by 1 under the “Cash” MOP in the Ruby reports if change was given from the sale.

4. Previously, the Ruby opened the cash drawer on a zero cash sale. This was corrected.

5. Previously, the fee description did not print on Ruby receipts. This was corrected.

6. Previously, if the following transaction occurred on the Ruby in this order: a sale item, a fueling point move, another sale item — the Ruby workstation locked up. This was corrected.

7. Previously, when an EPS failure occurred before a prepay transaction, the Ruby printed the first half of the prepay transaction on the receipt. This part of the transaction became part of the next transaction’s receipt. This was corrected and now the incomplete transaction is voided.

System1. Previously, on Ruby/Sapphire setups, the terminal type in the 2804

message reported a Topaz instead of a Ruby. This was corrected.

2. Previously, when a fast credit merchandise on Ruby was tendered for $0 and the transaction contained no items, it caused a “stuck” fuel sale with no subsequent fuel sales. This was corrected.

3. Previously, when fast credit with merchandise was initiated on the Ruby and the dispenser handle was lifted and put down without dispensing fuel, the sale did not complete resulting in free merchandise. This was corrected.

4. Previously, a DBException error occurred in Gemcom when attempting to delete the DCR Promo Message from NewPro. This was corrected.


27

5. Previously, the word “FAILED” was missing from “SITE CONFIG DATA REQUEST FAILED” message on the Ruby display. This was corrected and now the message displays as “SITE CFG REQUEST FAILED.”

6. Previously, if the dealer address exceeded 18 characters, the Ruby terminal displayed errors during each credit and debit transaction. This was corrected.

7. The Gemcom Softkey dataset now supports the REST IN GAS (RIG) softkey type code. Additionally, the existing Ruby POP MEMBER CARD (PME) softkey type code will now also apply to Topaz. However, all Topaz-only softkey types (i.e., those not usable on Ruby) are still not supported by this dataset and will cause Gemcom to stop with error code 20.

8. Previously, the Auto Upgrade completion message was easily overlooked due to the short amount of time that it was displayed. This was corrected and now the alarm message stays active for five minutes when the upgrade completes successfully. Also, the Ruby user will not be allowed to enter into [Sales] until the upgrade completes successfully.

9. Previously, the Ruby terminal was incorrectly reporting the application version as Vx.x.x in stead of xx.xx.xx. This was corrected.

10. Previously, the Gemcom “version dataset” displayed the incorrect base version. This was corrected.

11. Previously, Gemcom16 SUMTOT dataset failed with an “Error 64” after heavy GemLAN traffic in non-Sapphire Ruby systems. This was corrected.

12. Previously, occasional control characters appeared in the Gemcom output files causing Gemcom parsing to terminate prematurely. This was corrected.

13. Previously, the Gemcom cashier totals produced an incorrect pay in and pay out detail when retrieved directly from the Ruby or Sapphire GemPro via RS-232 serial connection. This was corrected.

14. Previously, the Ruby terminal was not clearing the entire loyalty message on the operator display. This was corrected.

Sapphire

Car WashThe default network timeout has been changed to 60 seconds on the car wash Pay Point configuration screen.

Kiosk1. Previously, claimed kiosk iOrders that were not settled could not be

purged from the system. As a result, claimed orders could eventually fill the queue and prevent new orders from being added on the Sapphire. This


28

was corrected and now the amount of delay before purging is the value configured in SMS plus 60 minutes.

2. Previously, if a kiosk iOrder contained a “PLU not found,” the item's department number was hardcoded to 9001 and its product code number was hardcoded to 7. If the hardcoded department and product code numbers did not exist, the order could never be completed from any workstation. This was corrected and now it uses the “PLU not found department” set at Manager > Configuration > Sales Configuration.

3. Previously, items in an iOrder menu on the Topaz were not displayed or totaled correctly on the MX Series PINpad. This was corrected.

Reports1. Previously, an “&” sign in the tax name generated an invalid XML

(transactionSet). This was corrected and now the “&” is allowed.

2. Previously, the POS displayed an error at the end of a Close Daily on the Sapphire.

3. Previously, Sapphire Journal Printer was not printing the last digit of the reference number for Topaz transactions. This was corrected.

4. Previously, Unit of Measure in GemPro is reflected an invalid value. This was corrected.

5. Previously, the grouplist.xml in SMS did not have entries for FP Hose and FP Hose Running Reports in the groupsMasterList element.This was corrected.

6. Occasionally, large negative or positive numbers were displayed in the Sapphire Department Report. This was corrected.

Sales1. Previously, department totals would be incorrect if a Match using a single

mix was sold using the [QTY] key. This was corrected.

2. Previously, PLU totals were incorrect for PLUs when a fee was included. This was corrected.

3. Previously, the discount percentage on a combo item could not be set on Sapphire systems. This was corrected.

Sapphire Generic Loyalty1. Previously, when there was a loyalty PPG prepay and then the pump was

stopped, the loyalty refund was not sent to the network. This was corrected.

2. Previously, the loyalty functions menu was not displayed on the Ruby when the [NETWORK FUNC] key was pressed in [SALES]. This was corrected.


29

3. Previously, when there was loyalty with a Fast Credit with Merchandise transaction, the messages were inconsistent on the POS. This was corrected.

4. Previously, the price of the second PLU was printed incorrectly on the Ruby receipt when two items were involved in a line item loyalty discount. This was corrected.

5. Previously, the prices of the PLUs and the transaction totals were printed incorrectly on the Ruby receipt for a multiple item loyalty refund. This was corrected.

6. Previously, tax adjustments were not performed for a refund involving a PLU with tax and loyalty discount on the Topaz. This was corrected.

7. Previously, when a loyalty card was scanned on a Topaz with Sapphire Generic Loyalty, a “Card not registered’ error displayed. This was corrected.

8. Previously, when a Fuel Tax Exemption or Addition was added to a postpay, it was not reported to the loyalty network. This was corrected.

9. Occasionally, the loyalty network would return a gallon limit for the fuel discounted by a PPG discount. If the customer declined the discount, the POS still enforced the gallon limit. This was corrected.

10. Occasionally, the POS terminal would fail during a loyalty transaction if the loyalty program name was greater than 18 characters. This was corrected.

11. Previously, when there was a prepay involving credit or debit with loyalty, the pump was approved for the maximum gallons and not for the discounted dollar amount. This was corrected.

12. Occasionally, the POS terminal would fail during a loyalty transaction if the loyalty program name was greater than 18 characters. This was corrected.

13. Previously, the fuel grade was incorrect when the loyalty card was swiped at the DCR and completed on the Topaz. This was corrected.

14. Previously, the PPG totals were incorrect when the loyalty card was swiped at the DCR and completed on the Topaz. This was corrected.

15. Previously, when a prepay with loyalty enabled was performed and the [CASH] was double pressed after the amount and then [No] was pressed to the loyalty prompt, this resulted in a system error. In order to clear it, the Topaz had to be power cycled. This was corrected.

Sapphire Management Suite (SMS)1. Previously, the Transaction Viewer displayed entries for DCR sales as

“Price Over by Orig Unit Price” indicating that the price was overridden. Price Over is used only for PLUs. This was corrected.

2. Previously, the default parameters at SMS > Fuel Manager > Fueling Positions were disabled when “Allow Access” was enabled. This was corrected.


30

3. Previously, the SMS Proprietary Network Applet displayed the Network Enabled parameter as disabled even though it was enabled. This was corrected and now it is correctly displays as enabled. )

4. Previously, the network configuration applet would not allow removal of the “Dial Access Code” using the applet’s graphic user interface. This was corrected.

5. Previously, when multiple network MOPs were used in the same transaction, the SMS Card Type Product Report displayed the incorrect count and amount. This was corrected.

6. Previously, when a user attempted to delete a category in Configuration Manager > Merchandise Manager > Categories, a run-time error occurred. This was corrected.

7. Previously, some reports in SMS displayed a closed date even though they were still open. This was corrected.

8. Previously, when the Transaction Manager grid was sorted by monetary or miscellaneous transactions, the first item in the grid was deleted. This was corrected.

9. Previously, the “Archive New Transactions at Log On” setting was not enabled until the application was restarted. This was corrected and now it is enabled when the user logs out.

10. Previously, when the Sapphire Transaction Manager was left open after 15 minutes of inactivity had expired and the user attempted to archive transactions, it caused a runtime error. This was corrected.

11. Previously, in Sapphire Transaction Manager > Transaction Viewer, if a new sales transaction was completed on a Ruby or Topaz and then the user selected Archive New Transaction, the new sales transaction was not displayed. This was corrected.

12. Previously, the E-Safe menu option in SMS was always enabled even though the function was not available in the credential. This was corrected.

13. Previously, a runtime error occurred if the file extension of a screencfg import file was not XML. This was corrected.

14. Previously, when the “rotate” parameter in the SMS > Register Configuration > Banners form was unchecked to disable it, it remained enabled. This was corrected.

15. Previously, when the Group Options or Report Definitions Maps in SMS > Report > Report Preferences were modified when the items were already in the group Report Navigator, it caused a runtime error. This was corrected.

16. The minutes value at the Manager > Restrictions > PLU Promotions tab is now properly saved.

17. Previously, when the Report Manager > Cashier Tracking form was opened to create departments and categories, not all of them were displayed after the form was closed and then opened. This was corrected.


31

18. Previously, a runtime error occurred when the user logged into the Transaction Manager without entering an ID and password. This was corrected and now a user name or password required message displays.

19. The following changes were made to SMS:

– The description “Save Raw Data” has been changed to“Save T-Log Data”.

– “Saving Register Totalizers” message is now fully displayed at Maintenance > Maint Configuration Form.

– The Feature Information Form in Maintenance has been changed to open fully.

– Clicking on an empty row in User Administration > Users List and clicking the delete button no longer results in an error.

– The [CANCEL] key now works on the “Change password” screen for the “New Password” line.

– The new Menu Form commands have been added to the importCfg.xml document.

– Fuel Service Level, Fuel MOP, and Fuel Blend Type are now view only on the fuel site form.

– “Error Correct Security Level” value can no longer be set higher than ‘9’ in Manager > Sales Configuration.

– The POP Discount Membership Card option is now grayed out or inactive when it does not meet certain criteria.

20. Previously, when the date and time was changed in SMS, it was immediate on NewPro, but not on Topaz. This was corrected.

21. Previously, after Tier 2 fuel pricing was enabled on SMS, it could not be disabled. This was corrected.

22. Previously, Topaz soft keys were not displaying Menu Chain items or a Multi-Select menu. This was corrected.

23. Previously, when an employee was deleted from the database and there was data left in the Payroll Report, this caused an error in the Payroll Report. This was corrected.

24. Previously, if any network card based MOP safe drops were performed and a Card Type Product Report was processed in SMS, zeros were the result and an error displayed. This was corrected.

25. Previously, when fuel or DCRs were initialized in SMS after 15 minutes of inactivity had expired, an error and then a successful message was displayed. This was corrected and now the user must log in before initialization and the successful message no longer displays.

26. Occasionally, the logon session did not occur automatically in SMS after a password change. This was corrected.


32

27. Previously, the SMS touchscreen preview/edit form was not loading if a Topaz XL touchscreen key was set to inactive. This was corrected.

28. Previously, SMS was not sending a properly formatted document to the Sapphire for menu configuration that caused the Sapphire not to synchronize the menus with the Topaz. This was corrected.

29. Previously, the Sapphire Management Suite (SMS) > Transaction Manager > Transaction Viewer > View Detail did not show the category number for combos. This was corrected.

30. Previously, it was possible for a cashier's error corrections to appear multiple times in the Sapphire Management Suite > Report Navigator > Cashier Transaction Indicators Report if the date stamp was the same for each correction. This was corrected.

31. Previously, when the Fuel Tax Exempt Report was printed from Sapphire Management Suite > Report Navigator, the descriptions were missing. This was corrected.

32. Previously, when a user of Report Navigator attempted to add a report that has the Report Requirements dialog box and clicked Cancel, the report was added to the “Reports to be Processed” box anyway. This was corrected.

33. Previously, in Sapphire Management Suite > Configuration Manager > Manager > House Account, accounts could not be added if there were no previously configured accounts in the SMS database. This was corrected.

34. Previously, in Sapphire Management Suite > Configuration Manager > Fuel Manager > Fuel Prices, after a price change was made and saved, selecting another product produced an error message. This was corrected.

35. Previously, the SMS POP Discount form was not saving PLUs properly. This was corrected.

36. Previously, when a change was made in Sapphire Management Suite > Configuration Manager > Maintenance Configuration and the change was cancelled, a message box reported a successful save. This was corrected.

37. Previously, no more than 32 employees could be configured through Sapphire Management Suite. This was corrected and now up to 60 employees can be configured through SMS.

38. Previously, when a Transaction Manager user selected Options and clicked “Archive New Transactions at Log On,” the archive folder was not created and Transaction Manager attempted to write to a non-existent folder. This was corrected.

39. Previously, when the user logged into Sapphire Management Suite, Report Navigator and received an error message, the status displayed as “Connecting.” This was corrected and now “Not Connected” appears if an error occurs during log in.

40. Previously, attempting to print from Transaction Manager produced an error message and printing did not occur. This was corrected.


33

41. Previously, printing from Sapphire Management Suite (SMS) > Configuration Manager > Tools > Print Configuration Data > Fuel Prices Config produced erroneous department and product code data that should not have been included in the printout. This was corrected and now the printout shows only fuel prices.

42. Previously, the HTTP response header 'Content-Type' in NAXML maintenance requests was not 'application/xml'. This was corrected.

43. Previously, HTTP notifications failed in certain instances. This was corrected.

44. Previously, if a button on the SMS Configuration Manager’s Touch Screen > User Panel Preview/Edit screen was set to inactive, it displayed as active and the inactive check box was unchecked. This was corrected.

45. Previously, the Transaction Viewer in the SMS Transaction Manager did not display the transaction amount for autocollect transactions. This was corrected.

46. Previously, when the menu item “View XML” was selected in Transaction Viewer, there was not an option to return from it. This was corrected.

47. Previously, the user name at SMS > Sapphire > User Administration could not be changed if no name was entered before moving out of the name field. This was corrected and now a name has to be entered.

48. Previously, deal configuration changes were saved in SMS, but were not sent to the Sapphire. This was corrected.

49. Previously, there was no limit to the amount of characters that could be entered for Username, Password, Report Display Name, and Department Group Name in SMS Report Navigator; however, entering more than 255 characters caused an error. This was corrected and now the maximum length is 255 alphanumeric characters.

50. Previously, the SMS Report Navigator locked up when a report group with no reports was modified. This was corrected.

51. Previously, the SMS Configuration Manager’s Fuel Manager > Fuel Configuration contained non-fuel product codes. The non-fuel product codes were removed.

52. Previously, when a user exited from the SMS Configuration Manager’s Touch Screen > User Panel Preview/Edit screen, the fuel panel was resetting to default settings. This was corrected.

53. Previously, the Safe Drop Security setting in SMS’s Configuration Manager Manager > Sales Configuration form was not limited to the values ‘0’ through ‘9’. This was corrected.

54. Previously, the selection of a menu item under SMS > Network Manager, was not disabling the rest of the menu items. This was corrected.

55. Previously, when the combo parameters on the SMS Deal Form were checked and then the user unchecked them, the change was not saved. This was corrected.


34

56. Previously, the user was able to disable the TLog in SMS Report Navigator > Report Configuration for periods 1 and 2. This was corrected and now the user can only disable one of them.

57. Previously, the Topaz money order “Auto-Split” feature and void tickets involving money orders were not supported in transactionSet and Transaction Log. This was corrected.

58. Previously, an error message displayed in SMS when the car wash PayPoint form loaded even though PayPoint was not configured. This was corrected.

59. Previously, when there were over 10 items on a menu in SMS, the sort function did not work. This was corrected.

60. Previously, the Sales Configuration form in SMS restricted the Register Timeout Timer value to ‘74’ instead of ‘999’. This was corrected and now the allowed values are ‘0 to 999.’

61. Previously, an error occurred when the user selected Reports > Configure Reports in SMS for the first time after installation. This was corrected.

62. Previously in Transaction Manager, when a user login was successful, the username was cleared. This required the user to key in the username again when they logged off. This was corrected and now the username remains until a new username is used.

63. Previously, the DCR header, trailer and message could not be deleted using SMS Configuration Manager. This was corrected.

System1. Previously, the Pump Test MOP caused GemPro to lockup. This was

corrected.

2. Previously, after an auto upgrade, the soft keys were not properly restored and the fast credit parameters in Sale Configuration were reset.

3. Previously, notifications were not sent for NewPro logins. This was corrected.

4. Previously, the EPS sent the message “Online SSL Signon Unsuccessful” to the journal printer 57 times consecutively every few minutes. This was corrected and now the EPS sends the message once every 10-15 minutes when the network is offline.

5. Previously, the Batch Close Status was not recorded to the Sapphire Journal Printer when the network responded with exception codes. This was corrected.

6. This enhancement converts PLU numbers from 12-digits to14-digits if the attribute inputMethod is set to keyboard. If the inputMethod is not set or set to a value other than keyboard and a PLU number is not 14 digits, an error occurs.


35

7. Previously, the Gemcom “Create” function removed existing PLUs instead of adding to them. This was corrected.

8. New direct requests of the tank monitor have been added for inventory and delivery for dynamic tank monitoring.

9. Previously, the first character was missed in the NewPro journal printer if the journal message was from the Topaz.

10. Previously, when retrieving POP discount totals from NewPro, the customer count was not displayed. This was corrected.

11. Previously, if there was a router between the Sapphire and Digital Video Recorder (DVR), the DVR messages were lost. This was corrected.

12. Sapphire and Topaz user activity is now logged to meet PA-DSS requirements. See the Installation Options section in these release notes for information regarding the log server option.

13. Previously, if the encryption service was disabled on Newpro when the authorization was received from the network, the account number, expiration date, and cardholder's name was not encrypted, and the Topaz did not clear the corresponding fields from the transaction before it was stored in the database. This was corrected.

14. Previously, when Daylight Savings Time was in effect, Newpro may have incorrectly converted the local time from the Ruby or GemPro resulting in time stamps being reported one hour fast. This was corrected.

15. Sensitive data that may have been left inside temporary data files has now been removed to meet PA-DSS requirements.

16. Previously, NewPro only supported up to 50 fees while GemPro supported 99 fees. This was corrected and now NewPro supports 99 fees.

17. Previously, when Sapphire Site Controllers were rebooted, the system time was off by the amount of time the Sapphire was down. This was corrected.

18. Previously, when “Prompt for Exemption” was changed at SMS > Manager > Payment > Tax Rates, it was not sent to the Ruby terminal. This was corrected.

19. Previously, an error occurred if tax rate ‘3’ was set to collect only on tax ‘2’. This was corrected.

20. Previously, if the tax print indicator was set to a space (‘ ‘) in the System Setup > Manager > Tax Rate File, an error occurred and NewPro did not synchronize with GemPro. This was corrected.

21. Previously, if taxes were not setup sequentially (for example, only Tax 1 and Tax 4 were set up) and sales were completed on the POS using these taxes, an error occurred when the tax report was retrieved. This was corrected.

22. Previously, period close reports would not be available due to an invalid or incomplete tax, fee, and currency configuration. This was corrected.


36

23. Previously, when the Topaz registration failed, the user was not able to log into SMS. This was corrected.

Topaz

Clock In/Clock Out1. Previously, a cashier with a password using leading zeros could not Clock

In/Clock Out on Topaz. This was corrected.

2. Previously, the Topaz passwords required for performing Clock In/Clock Out functions were limited to six (6) digits. This was corrected and now eight (8) digits may be entered.

Network1. Previously, the Topaz displayed “ISO PART/ID” error for a Mannatec

transaction and the transaction was not completed. This was corrected.

2. Previously, Topaz “POP By Card Type” transactions were rejected by the network due to incorrect product data. This was corrected.

3. Previously, the CFN Secondary Network Cards were declined with an “Account Number Error” message when the magnetic stripe track data began with an “=” sign and it was processed on the Topaz. This was corrected.

4. Previously, Mannatec refund transactions on the Topaz were rejected by the network. This was corrected.

Reports1. Previously, the Payment-IN section in the Topaz Cashier Report was

missing the In-House account information. This was corrected.

2. Occasionally, the data was unavailable in the Topaz Cashier Tracking Report. This was corrected.

3. Previously, negative departments sold with positive fees on the Topaz had the fee amounts subtracted within the department report. This was corrected.

4. Previously, the Topaz “Print Car Wash PayPoint Period” displayed only 10 closed period reports instead of displaying all the close periods. This was corrected.

5. Previously, the “POP Discount Report” and the “POP Discount Def Report” was not printed in the Topaz Shift Report. This was corrected.

6. Previously, the Topaz Monthly and Yearly Reports were not printing all the data and gave an error “Error while getting report from sapphire”. This was corrected.


37

7. Previously, the Topaz Yearly and Monthly Reports were printed incorrectly due to an invalid entry in the grouplist.xml. This was corrected.

8. Previously, the report header was not printed on all Topaz flash reports. This was corrected.

9. Previously, when amounts greater than $1,000 were sold to a department, the Gross Sales and Refunds were combined together in the Topaz Department Report. This was corrected.

10. Previously, cashback amounts were reported incorrectly in the Topaz and SMS Cashier Reports. This was corrected.

11. Previously, the Topaz Summary Report reported the amount and volume of pump overruns as zero even though they occurred. This was corrected.

12. Previously, when using the Pump Test MOP in a fuel transaction on the Topaz, it was not accounted for in the FP/Hose Test Report. This was corrected.

13. Previously, the debit cashback amount was deducted twice from the Electronic Cashier Register (ECR) on the printed Topaz Cashier Report. This was corrected.

14. Previously, there was an invalid security control ID for the FP Hose Test Report in the Topaz flashMenu.xml. This was corrected.

15. Previously, the Topaz Flash Summary Report combined the check and cash MOP safe drops. This was corrected.

16. Previously, 8-digit bar codes beginning with the digit ‘5’ could not be scanned on the Topaz even though they existed in the database. This was corrected.

17. Previously, a line for the Credit MOP did not print on the Topaz Cashier Worksheet. This was corrected.

18. Previously, the MOP code and MOP description displayed differently on both the Topaz Cashier Report and SMS reports. This was corrected.

19. Previously, when there were more than ten report periods in the database, only the last ten periods displayed. This was corrected.

20. Previously, the Topaz Cashier Report added two additional zeroes to the prepaid activations count and amount. This was corrected.

21. Previously, the header information was missing when a tax report was printed from Topaz Flash Reports. This was corrected.

22. Previously, Topaz workstations failed to take into account safe drops, no sales, and other till transactions when reporting the number of transactions for a Cashier Report close. This was corrected.

23. Previously, the ticket numbers used for payroll transactions during a cashier period were not included in the Cashier Report. This was corrected.

24. Previously, refunds to the negative department did not appear correctly on Topaz Cashier Reports. This was corrected.


38

25. Previously, the Topaz printed “Cashier Tracking Data Unavailable” in the Cashier Tracking Report even though there was tracked data and the Sapphire and HPV-20 were communicating correctly. This was corrected.

26. Previously, there were formatting issues in the Topaz Batch Summary Report. These were corrected.

Sales1. Previously, when a fast credit with merchandise transaction was

performed on one Topaz, it could not be settled if the same type of transaction was performed on the same DCR from any other Topaz. This was corrected.

2. Previously, fuel prepays performed on the Topaz and tendered with FLEETCOR cards were rejected by the EPS. This was corrected.

3. Previously, the Topaz “CALL FOR AUTH” message only displayed for 75 seconds. This was corrected and now the message will not time out.

4. Previously, a manual fuel refund on Topaz displayed ‘NULL’ for fuel information on the display as well as the receipt. This was corrected.

5. Previously, the dismissal of the “Other MOP” prompt on the Topaz without any selection resulted in subsequent credit transactions not completing automatically. This was corrected.

6. Previously, when two gift cards were used in a split tender sale, the Topaz XL printed a previous fleet card network transaction on the receipt. This was corrected.

7. Previously, when a Fast Credit prepay was initiated with cash, but tendered with credit MOP and the Fast Credit prepay at DCR was canceled before fueling, the Topaz was not sending a $0.00 collect. This was corrected.

8. Previously, the autorefund for credit prepay underruns did not work for proprietary cards. This was corrected.

9. Previously, when Fast Credit with Merchandise transactions failed, no error was displayed on the Topaz if product codes were not assigned to merchandise. This was corrected.

10. Previously, debit partial approvals could not be voided on the Topaz and “Card not allowed” displayed. This was corrected.

11. Previously, when a fuel prepay was entered as cash and tendered as credit, the POS sent a sale completion and not a preauthorization to the network. This was corrected.

12. Previously, when a PLU with modifiers was scanned for a price check, the Topaz did not display the modifier menu and went straight to the price check overlay message. This was corrected.

13. Previously, when a cashier override was required for a secure cashier function and only a password was entered, the Topaz returned to the


39

transaction and “Reset: Internal Fault” displayed in the status bar. This was corrected and now “Invalid User ID” error displays.

14. Previously, percent discount was not allowed on a Topaz refund transaction. This was corrected.

15. Previously, when the cashier logged out without doing any transactions, the Topaz did not prompt for a beginning cash drawer amount when the same cashier logged back in. This was corrected.

16. Previously, the Incomm prepaid card receipt on the Topaz would only print if the MOP parameter to print the receipt was enabled. This was corrected.

17. Previously, when multiple Incomm prepaid cards were activated and one of the cards had a bad mag-stripe, the Topaz locked up. This was corrected.

18. Previously, the “Fuel Site Pause” menu label and status display messages on the Topaz were not user-friendly. This was corrected.

19. Previously, when the EBT Food Stamp MOP was used in a Topaz transaction, the food stamp total was incorrect. This was corrected.

20. Previously, the Topaz was not printing the cash and food ledger balances that were returned from the network on the receipt. This was corrected.

21. Previously, the Topaz allowed a price to be overridden with an amount less than that set in the “Min amount” parameter in Manager > Configuration > Sales Config. This was corrected.

22. Previously, Topaz error messages disappeared too quickly if the cashier used the “other department” key during a sales transaction. This was corrected.

23. Previously, with “Ignore MOP conflict” set to ‘N’ at Fuel Manager > Site Parameters > Fuel Site Parameters, a partially dispensed fast credit transaction with debit or a prepaid card cannot be completed on Topaz. The only option is to cash out the due sale. This was corrected.

24. Previously, a postpay fuel sale without fuel grade information could not be tendered on the Topaz if POP discount was enabled. This was corrected.

25. Previously, if a cashier closes out immediately after performing a fast credit preauthorization and before the transaction is fully dispensed at the pump, an additional open cashier entry gets created in the database when the fueling is eventually completed. Cashier reports do not balance. This was corrected.

26. Previously, the Topaz would approve a fast credit transaction if the preauthorization information was not stored in database. This was corrected and now it is stored in the database before approving.

27. Previously, when POP discount is enabled on the Topaz and a fuel discount is applied to the sale by using the “FUEL DISCOUNT” softkey on the touch screen, the POP discount code prompt appeared for the second time on the same ticket. This was corrected.


40

28. Previously, if [ERROR CORRECT] was pressed on the Topaz immediately after an invalid card swipe during a prepaid card activation item sale, the transaction balance was incorrectly reduced. This was corrected.

29. Previously, when Error Correct was used in a Mix 'n Match transaction on the Topaz, the deal's discount was not removed from the transaction. This was corrected.

30. Previously, linked mixes on the Topaz did not work under certain configurations. This was corrected.

31. Previously, department mixes on the Topaz did not report discounts correctly. This was corrected.

32. Previously, the Topaz was not accepting the lottery MOP code 17. This was corrected.

33. Previously, if the cashier pressed [SAFE DROP] and then walked away from Topaz allowing the inactivity timeout to occur, the Topaz locked up. This was corrected.

34. Previously, when a volume prepay with fast credit merchandise enabled was dispensed fully, the due sale could be different from the original preauthorization amount. This was corrected.

35. Previously, if the money order device displayed an error and a money order was sold on the Topaz, the Topaz displayed the printing of the money order even though no money order printed. This was corrected.

36. Previously, if a prepay transaction was paid with credit and the entire amount was over the partial authorization and the balance due is paid with cash, the Topaz auto refunded the entire balance to credit. This was corrected.

37. Previously, during a pay in transaction, the Topaz would prompt for an in-house account even though in-house accounts were not defined. This was corrected.

38. Previously, the Topaz sale screen would not clear for network transactions even though the “Reset display on timeout” parameter was set. This was corrected.

39. Occasionally, the Topaz fuel buttons did not reflect the changes in the pump status and due sales. This was corrected.

40. Previously, the Topaz in-house account number entry overlay disappeared when [CLEAR] was pressed. This was corrected and now an amount has to be entered.

41. Previously, the item count was incorrectly incremented on the Topaz for a prepay underrun or overrun settlement when there was a fuel deposit present. This was corrected.

42. Previously, the “Use Imprinter” prompt displayed indefinitely on the Topaz when the Manual Credit MOP was used with no items in the transaction. This was corrected.


41

43. Previously, when the first item on a ticket was error corrected, the Topaz did not reset the ticket totals (total without tax, discounts, and so forth). This resulted in the customer being charged an invalid amount. This was corrected.

44. Previously, the Topaz would exit “Ready” mode if the cashier keyed an invalid quantity for a transaction. This was corrected.

45. Previously, after entering 32 items into a Topaz transaction, ‘PLU’ cannot be touched and get a line item overlay. This was corrected.

46. Previously, a Topaz prepay fuel sale was not restricting the use of the Drive Off MOP. This was corrected.

47. Previously, when in Sales and a security prompt was displayed on the Topaz, the entered ID and password did not display correctly. This was corrected.

48. Previously, if a transaction received a Match discount using multiple PLUs on the Topaz, the item count was incorrect. This was corrected.

49. Previously, the “Show Fuel” key on the Topaz had to be pressed twice to display the fuel panel. This was corrected.

50. Previously, the FP Convert button on the Topaz touch-screen did not function. This was corrected.

51. Previously, the Topaz did not display an error message for a car wash quantity sale if the quantity sale was changed using the touch to modify feature of the receipt window. This was corrected.

52. Previously, the “Other Fuel Functions” did not work on the Topaz. This was corrected.

53. Previously, the Fuel Tax Exemption signature line receipt did not print on the Topaz. This was corrected.

54. Previously, when a fuel tax was added to the fuel department and a fuel tax exemption occurred within the same fuel transaction, the fuel tax addition in the fuel department was ignored causing incorrect totals on the Topaz. This was corrected.

55. Previously, when there was a stacked sale, First In and First Out was set to ‘Yes’, and the second sale was attempted to be tendered before the first sale, the POS displayed an erroneous message. This was corrected.

56. Previously, an incorrect Topaz overlay was used for a fuel prepay error message on a pump that has “Preset Prepay” disabled. This was corrected.

57. Previously, the trailer and footer were missing from a DCR reprint on the Topaz and the paper was not cut at the end. This was corrected.

58. Previously, when a prepay underrun transaction was tendered to credit MOP, the Topaz did not prompt for specific information such as a reference number needed to process the refund for the card type. This was corrected.


42

59. Previously, when autorefund was enabled on Topaz, coupons could not be redeemed in a credit prepay transaction. This was corrected.

60. Previously, when a price check was performed and [CANCEL] or [OK] was pressed, the overlay remained on the Topaz display. This was corrected.

61. Previously, the first character entered when logging in (user ID and password) on the Topaz XL did not display. This was corrected.

62. Previously, Topaz In-House MOP refund was completing before the account number was entered. This was corrected.

63. Previously, alpha characters were not allowed on Topaz for In-House account entry. This was corrected and now alphanumeric account numbers are allowed.

64. Previously, if the car wash Pay Point interface failed, the site was unable to perform a Close Daily on the Topaz. This was corrected.

65. Previously, when the safe drop information sent from the Topaz to the Seiko Journal Printer, it printed “0.00” for the amount and nothing for the reference number. This was corrected.

66. Previously, with “Auto refund enabled” in Manager > Configuration > Sales Configuration and a fuel prepay was performed, the “Number of postpay hours” parameter in Fuel Manager > Site Parameters > Fuel Site Parameters was changed to some other value. This was corrected and the value stays unchanged.

67. Previously, when a transaction had multiple prepaid activation and deactivation items, the Topaz occasionally locked up after the payment was tendered. This was corrected.

68. Previously, a scanned PIN-based prepaid card would not appear on the display if it was the first item on the ticket. Even though the totals were not displayed, they would update. This was corrected.

69. Previously, when a customer’s credit card number and expiration date were entered manually on Topaz for an inside transaction with full-service attendant tracking in effect, and the cashier entered an existing attendant number (such as “1” for “Jack”) from the list of up to 15 attendants displayed instead of entering ‘0’ (zero) for “OTHER”, the sale was not transmitted to the host network. This was corrected.

70. Previously, Topaz workstations rounded incorrectly while using the At-For Pricing method. This was corrected.

71. Previously, linked mixes on the Topaz completed before the criteria was met. This was corrected.

72. Previously, when using the error correct key on the Topaz to remove a voiding line, doesn't restore deals for the now unvoided line.

73. Previously, line items created with the repeat last item function on the Topaz were not recognized in deals. This was corrected.

74. Previously, single-mix deals with all items sold on one item line caused inaccurate discount amounts on the Topaz. This was corrected.


43

75. Previously, recalled sales on the Topaz did not include the tax on discounted amounts of deals. This was corrected.

76. Previously, the Topaz did not report deals correctly in the Department Report when using the quantity key. This was corrected.

77. Previously, when using the touch screen to modify a PLU, the Topaz failed to recognize certain deals. This was corrected.

78. Previously, the discount value on the customer receipt copy was different from the merchant receipt on the Topaz. The report totals were accurate. This was corrected.

79. Previously, the Topaz was not applying the taxes to Matches correctly if the [MODIFY] key was used. This was corrected.

System1. Previously, the Topaz was not journaling cashier activity such as logins,

logouts, and cashier closes. This was corrected.

2. Occasionally, a duplicate request ID to the EPS may be generated at a site with multiple Topaz workstations causing failed transactions. This was corrected.

3. Occasionally, “SSL Sign-on unsuccessful” displayed on the Topaz. This was corrected.

4. Previously, there were time delays and “unauth printer” messages using the Topaz printer. This was corrected.

5. Previously, when EasyID was enabled on Topaz workstations and the ID check dialog box was displayed, Topaz would display an error message that the expiration date was invalid when 2D driver’s licence barcodes were scanned. This was corrected.

6. Previously, the HPV-20 would occasionally appear to be locked up when a message box was open while the system was trying to log out a user. This was corrected.

7. Previously, after an error correct on Topaz, the pole display showed 0.00, which remained on the pole display even after logoff. This was corrected.

8. Previously, when the Topaz Backspace key was used to correct a manual keyboard entry, the entire entry was deleted. This was corrected and now the Backspace key erases one character at a time.

9. Previously, the Topaz keyboard arrow keys did not work when selecting a fuel product during a fuel prepay transaction using credit or debit. This was corrected.

10. Previously, when the Ruby-compatible menu was selected on the Topaz, the inactive item buttons were black instead of gray. This was corrected.

11. Previously, when an invalid selection was selected from a Ruby-compatible menu on the Topaz, the menu disappeared without an error message or audio event. This was corrected.


44

12. Previously, the Topaz installer would hang on the 12” Topaz. This was corrected.

13. Previously, the Topaz volume adjustment was not set correctly within the range. This was corrected.

14. Previously, the Topaz printer stopped printing after an error condition. This was corrected.

15. Previously, the Topaz printer stopped printing after reloading the correct paper roll. This was corrected.

16. Previously, when very large print jobs were printed from the Topaz, the output had format issues due to the printer service. This was corrected.

17. Occasionally, a previous card read on the Topaz would be used for the current customer. This was corrected.

18. Previously, on the Topaz, when the [EXIT] key was pressed at the swipe card prompt, it did not return the MX870 to its IDLE state. This was corrected.

19. Previously, a cash drawer connected to a Topaz would open on a credit transaction. This was corrected.

20. Previously, touching the word “touch” in “Press enter or touch screen” had no effect. This was corrected.

21. Previously, when the PINpad port was re-assigned on the Topaz, the assignment disappeared from the screen. This was corrected.

22. Previously, the Topaz alarm line messages were not removed properly. This was corrected.

23. Previously, no alarm message displayed if a coin dispenser lost communication with the Topaz. This was corrected.

24. Previously, the incorrect change was given from a coin dispenser if communication was lost with the Topaz. This was corrected.

25. Occasionally, when the Topaz terminal played an audio event, it continued to play and appeared to be locked up. This was corrected.

26. Previously, the Topaz had to be rebooted several times in order to enable the audio. This was corrected.

27. Previously, if an employee used the clock-in function while another cashier was logged into the Topaz, a separate cashier session was opened for the employee but the clock-in receipt displayed the current cashier ID. This was corrected and now the Topaz will not open a separate cashier session for the clock-in and the clock-in receipt now displays the correct employee ID.

28. Previously, the Topaz volume adjustment level was not stored correctly. This was corrected.

29. Previously, the same overlay message was used for both password entry and error message display. This was corrected and now both instances use separate message overlays.


45

30. The following issues during the Topaz installation and startup have been corrected.

– An error message now displays if the touchscreen controller fails.

– Application and database scripts are only executed if invoked by user 'topaz'.

– The installation now continues if an option code is not entered for a set time limit.

31. Previously, a PINpad communication error occurred on the Topaz when POP discount was set up for debit card type. This was corrected.

32. Previously, the Topaz XL locked up at the logo screen with a white background upon reboot after installation and/or upgrade. This was corrected.


46

Installation Options

NOTE: This software no longer supports the ability to use a Ruby and Topaz on the same Sapphire.

Sapphire Installation Options

Option Code Description

logserver This option code is used to assign the IP address of a customer provided server that will receive system log messages from the Sapphire and Topaz.

wuice This option code is used when the Western Union ICE6000 Terminal is connected via IP.

wut7e This option code is used when the Western Union T7e Terminal is connected via serial port.

mgdelta This option code is used when the MoneyGram/TravelersExpress Delta Network Terminal is connected via IP.

Supported POS Terminals

Ruby SuperSystem, Sapphire, Topaz 110, and Topaz XL


47

Upgrade Summary

NOTE: See VASC Bulletin 0508-001 for checking the reliability of downloaded software releases using MD5 files.

Onsite Upgrades

Overview

All sites must use a full install.

NOTE: All upgrades must be completed in sequential order. For example:

■ GemPro, NewPro, Ruby

■ GemPro, NewPro, Topaz

Sapphire/Ruby/Topaz Site Installation

Overview

Sapphire installation uses files from CVXPAK_V6_00_15_Suite_Production_CD.exe, which, when extracted, contains GemPro for Gemstalling, folders for installing NewPro from a CD, and a folder containing the files to install Sapphire Management Suite. See Suite Installation CD Preparation.

GemPro

After extracting the files, use the GemPro Installation for Sapphire Sites procedure to install Sapphire GemPro.

NewPro

After preparing the CD, use the NewPro Installation for Sapphire Sites procedure, which uses a CD-ROM and HPV-20, to install NewPro.

Topaz Workstation Installation

Topaz workstations are upgraded from the same CD containing the NewPro installation: CVXPAK_V6_00_15_Suite_Production_CD.exe. Topaz installation follows Sapphire installation. See Topaz Workstation Installation.

Sapphire GemPro Board Upgrade to CPU-6The Sapphire Site Controller GemPro board software is to be upgraded from CPU-5 to CPU-6 if it has not already been upgraded. This software upgrade enhancing the operating system is accomplished at Gemstall time, and the


48

process also converts the CPU-5 Ruby Card to a CPU-6 Ruby Card. Only the software is upgraded. The hardware remains the same.

NOTE: The CPU-6 upgrade is not needed if the OS version is 2.7.3 or higher. The OS version is found on the Sapphire display. If the upgrade has been performed and then upgraded again, the program exits.

NOTE: Failing to perform this procedure correctly could damage your system. This software upgrade is for Sapphire/Ruby or Sapphire/Topaz sites only. It is NOT for Ruby-only sites. Documentation on the CPU-6 upgrade may be found on the VeriFone Premier Web Connection at Petro Downloads > Sapphire > Sapphire and SMS: Other Documentation > Installation Guide in the PDF file CPU-6 Installation for Sapphire Base 160.

Questions?If you have any questions while upgrading, the VeriFone Customer Support Center is available for assistance 24 hours a day, 7 days a week at 888-777-3536.

Saving Sales Data and Ruby Settings

Saving Data

Use these steps to begin any onsite upgrade:

1. Close the current report periods.

a. Run Close Cashier Totals and Print Cashier Report at the Ruby terminal. In a multiterminal system, run Close Cashier Totals and Print Cashier Report at each workstation also.

b. Run and print close period reports:

• In a 3-shift configuration, run Close Shift (Close Period 1), Close Daily (Close Period 2), Close Monthly (Close Period 3) and Close Yearly (Close Period 4). Print these reports.

• In a 12-shift configuration, run Close Shift (Close Period 1) and Close Daily (Close Period 2). Print these reports.

c. Run the Payroll Report using the “Close” option.

2. Make sure that the last batch was reconciled. To do this:

a. In Network Manager > Print Batch Report, select the appropriate batch.

b. Look at the Network Report (part of the Close Daily report printed above) for the last balanced batch.

c. Verify that the last balanced batch on the “In Balance” totals agrees with the last batch on the Network Report.


49

Saving Settings

List out all of the site’s configuration parameters and data from the Ruby terminal. To print out your Ruby terminal settings, access each of the following functions and [List] their contents. Keep the printouts for use at the end of the upgrade.

– Manager menu: All functions

– Fuel Manager menu:: All functions

– Reports menu:: Configuration

– Maintenance menu:: All functions

– Network Mgr menu:: All functions

– Car Wash Mgr menu: (if applicable): All functions

Ruby Manager Backup of Data and Settings

Using Ruby Manager, perform a complete system backup.

Onsite Upgrade Procedure For Ruby-Only to Ruby/SapphireAfter completing the steps of Saving Sales Data and Ruby Settings by using Ruby Manager to back up all sales data and Ruby configuration settings, continue here to upgrade the Ruby terminal. This procedure uses files extracted to C:\GEMSTALL\CVXPAK\V6_00_15\Gempro, which are then Gemstalled using Relsapp.vfg.

1. Connect the PC COM port through a null modem adapter and an RS-232 cable to the Ruby terminal’s COM 1 port.

2. Place the Ruby terminal into SYSMGR mode by pressing and holding (with a ballpoint pen point or paperclip) the forwardmost button on the card holder on the right side of the terminal.

3. Once the terminal is in SYSMGR mode, run Gemstall.

a. Open the Relsapp.vfg file for the version being installed.

NOTE: Do not save over this file.

b. Run the Edit function to set the terminal specific requirements such as the correct printer, keyboard, and terminal type for the terminal you are upgrading.

c. Run the Install function.

NOTE: Gemstall version 2.52 or higher, compatible with USB ports and all Windows versions through Windows XP, should be used at a Baud rate of 57600 if the laptop supports it. The latest Gemstall version is available on the VeriFone Premier Web Portal at Petro Downloads > PC Based Applications > Gemstall.

4. Reboot the Ruby terminal.

NOTE: If an update of your operating system is required, the Ruby terminal prompts for confirmation and automatically updates the


50

system. The system then reboots the Ruby terminal as necessary. When the update has been completed successfully, the system reboots, and the updated version displays.

NOTE: If an update of your operating system is required, the Ruby terminal prompts for confirmation and automatically updates the system. The system then reboots the Ruby terminal as necessary. When the update has been completed successfully, the system reboots, and the updated version displays.

5. If there are other workstation Ruby terminals on the site, repeat steps 1 through 4 for every other workstation.

Suite Installation CD Preparation

Overview

Sapphire GemPro, NewPro, and SMS for this release are all contained in the self-extracting zip file CVXPAK_V6_00_15_Suite_Production_CD.exe. This file may be downloaded or distributed on a PC. In either case, double-click on this file and choose “Unzip”. The files will be placed in C:\CVXPAK V6.00.15 Suite Production CD.

GemPro

The GemPro component is CVXPAK_V6_00_15_GemPro_Production_Software.exe. Double-click on it and it will extract to C:\GEMSTALL\CVXPAK\V6_00_15\GemPro where it is Gemstalled using Relsapp.vfg. See GemPro Installation for Sapphire Sites.

NewPro

The NewPro folders and files must be burned to the root of a CD-ROM disk for installation.

NOTE: See VASC Bulletin 1210_002 for CD file structure changes.

NOTE: It may be convenient to place the SMS folder on this CD. The GemPro file does not need to be placed on the CD, although it may be. Whether or not it is placed on the CD, remember to Gemstall from files on your PC’s hard drive and not from the CD.

See NewPro Installation for Sapphire Sites.

Topaz

Topaz software is included with the NewPro software and is installed after Sapphire NewPro.

See Topaz Installation for Sapphire/Topaz Sites.

SMS

Sapphire Management Suite files must also be burned to a CD for installation. They may be placed on the CD used to install NewPro or on a CD of their own.


51

See SMS Installation for Sapphire Sites.

GemPro Installation for Sapphire Sites After completing the steps of Saving Sales Data and Ruby Settings by using Ruby Manager to back up all sales data and Ruby configuration settings or exporting SMS configuration data at SMS > Configuration Manager > Tools > Export Configuration Data, continue here to upgrade Sapphire GemPro software for Sapphire sites. Note that this procedure uses files extracted into C:\GEMSTALL\CVXPAK\V6_00_15\GemPro which are then Gemstalled using Relsapp.vfg.

NOTE: These are abbreviated instructions. For full details, see The Sapphire Installation Guide available for download from the new VeriFone Premier Web Connection at Petro Downloads > Sapphire > Sapphire and SMS: Other Documentation > Installation Guide.

1. Remove the Ruby Card from the Sapphire Site Controller.

2. Connect the RS-232 cable from your PC to COM 2 of the COM Port Bank

3. Place the GemPro side of the Sapphire Site Controller in SysMgr mode by pressing [+] and [S] on the front panel keypad at the same time for 2 seconds. Release the keys when you hear a short beep.

4. Using the keypad on the front panel of the Sapphire Site Controller, press [1] twice to establish the [Yes] key and [2] twice to establish the [No] key.

5. Use the [2] key to answer “No” until the “Select SYSMGR Port” option appears.

6. Press ‘1’ for [Yes] for

– “Select SYSMGR Port”

– “SYSMGR on COM PORT 2”

– To select the Baud rate of 57600 for Gemstall

NOTE: If your PC will not support the high Baud rate, choose 19200.

Other questions should be answered with ‘2’ for [No].

7. On your PC, start Gemstall. Move to the C:\GEMSTALL directory and then continue to the sub directories for the application, version, and GemPro. Select Relsapp.vfg.

NOTE: Gemstall version 2.52 or higher, compatible with USB ports and all Windows versions through Windows XP, should be used at a Baud rate of 57600. The latest Gemstall version is available on the VeriFone Premier Web Portal at Petro Downloads > PC Based Applications > Gemstall.

8. Open the Relsapp.vfg file for the version being installed.

a. Run the Edit function.

b. At the “Sapphire or Ruby” prompt, choose “Sapphire (controller)”.


52

c. Continue with the Edit function to set the terminal specific requirements such as the correct printer, keyboard, and terminal type for the terminal you are upgrading.

d. Run the Install function.

NOTE: Be sure to select the Relsapp.vfg option and Gemstall the Sapphire as a controller of a multiterminal configuration.

9. The Sapphire begins a reboot. To speed up the process, press the [Pause] key on your PC to pause the program before the Sapphire beeps to show the reboot is complete.

10. Once again, repeat the selection of [1] twice to establish the [Yes] key and [2] twice to establish the [No] key.

11. Use the [2] key to answer “No” until the “Select SYSMGR Port” option appears.

12. Press ‘1’ for [Yes] for

– “Select SYSMGR Port”

– “SYSMGR on COM PORT 2”

– To select the Baud rate of 57600 for Gemstall

NOTE: If your PC will not support the high Baud rate, choose 19200.

Other questions should be answered with ‘2’ for [No].

13. Gemstall installs the GemPro software.

14. From the up to four Ruby workstations that can work with the Sapphire Site Controller, choose the Ruby terminal that will have the [SYSTEM SETUP] mode that may be used to configure the system. Remove the Ruby card from this workstation.

15. Connect the PC COM port through a null modem adapter and an RS-232 cable to this Ruby workstation’s COM 1 port.

16. Place this first Ruby workstation into SYSMGR mode by pressing and holding (with a ballpoint pen point or paperclip) the forwardmost button on the card holder on the right side of the terminal.

17. Once the Ruby is in SYSMGR mode, run Gemstall.

a. Open the Relsapp.vfg file for the version being installed.

b. Run the Edit function and select “Ruby (workstation)” at the “Sapphire or Ruby” prompt.

c. Designate the first Ruby as “Terminal No. 1”. The Sapphire uses the [SYSTEM SETUP] mode on the No. 1 workstation terminal to provide manager-level configuration of the Ruby system to site requirements.

d. Continue the Edit function to set the terminal specific requirements such as the correct printer, keyboard, and terminal type for the terminal you are upgrading.

e. Run the Install function.


53

18. In turn, Gemstall any other Ruby workstations with Relsapp.vfg, designating them as “Terminal No. 2”, “Terminal No. 3”, and “Terminal No. 4” as needed.

19. When Gemstall is complete, replace the Ruby Card in the Sapphire Site Controller and reboot by pressing + and R at the same time.

20. Allow the Sapphire to boot up, then replace the Ruby cards in the workstations and power up the workstations.

21. Using Ruby Manager, restore all sales data and Ruby settings except for settings in Fuel Manager. The Fuel Manager settings must be manually restored using the printouts that you made earlier in Saving Sales And Settings Data. (Note that you may want to save the printouts for future reference.)

22. Make the change to NACS 3-digit product codes:

Product Code Conversion

Note that, as part of the changes made in the CVXPAK application, it now supports the NACS 3-Digit product codes. When restoring the site’s departments and PLU's, each item must change its product code to match the new product code from the NACS product code listing. In order to accomplish this, there are a variety of ways to convert the products. Additionally, there a multiple ways in which PLU's and Departments can be setup.

Product Code Setup

To set up product codes, do one of the following:

■ Assign each PLU and each department a specific product code. Then when a PLU is sold it will use the product code assigned to that PLU. And when a department is sold it will use the product code assigned to that department.

■ Assign each PLU a product code of zero. If this option is chosen, then each PLU must be assigned a department and that department must have the corresponding NACS product code. Then, when a PLU is sold, it will use the product code assigned to the department that the PLU is associated with.

NOTE: Do NOT assign a product code of zero to a department.

Converting Product Codes

You can use one of the following methods to convert product codes:

■ The product codes can be converted manually once the PLU and Departments are pushed over to the POS by utilizing the POS and selecting each individual PLU and department.

■ The product codes can be converted in the Ruby Manager application. This is a manual process, but the user interface in Ruby Manager allows this to be done quicker then selecting each item on the POS.


54

■ The product codes can be converted by the customer using their back office product. This process will vary depending on the capabilities of the back office software program.

■ The product codes could be provided by the sites price book provider. Since these product codes are the NACS standard, this data is no longer unique for the POS or the application and, as part of the standard price book that the store receives, they may have the ability to send the items, PLUs, and Departments already assigned with the NACS product codes.

Obviously, it is very important that this conversion be correct during the install, so it will be very important that you work closely with the site, manager, or the responsible party for the customer.

NewPro Installation for Sapphire SitesAfter completing the steps of Saving Sales Data and Ruby Settings by using Ruby Manager to back up all sales data and Ruby configuration settings or exporting SMS configuration data at SMS > Configuration Manager > Tools > Export Configuration Data, continue here to install Sapphire NewPro software for Sapphire sites. The Sapphire NewPro version to use is 6.00.15. The installation CD is made from folders and files extracted from CVXPAK_V6_00_15_Suite_Production_CD.exe as previously described.

1. Place the installation CD in the HPV-20/V950 PC drive.

2. Power-cycle the HPV-20/V950 PC to transfer the NewPro and Topaz files.

3. Connect your laptop/PC to the SERVICE CONSOLE of the Sapphire Site Controller with an RS-232 cable.

4. Run HyperTerminal to install the NewPro files.

NOTE: If a firmware caution message appears, see the “Upgrading Sapphire Firmware” section below.

NOTE: For full details, see The Sapphire Installation Guide available for download from the new VeriFone Premier Web Connection at Petro Downloads > Sapphire > Sapphire and SMS: Other Documentation > Installation Guide.

Upgrading Sapphire FirmwareIf your application requires you to upgrade the Sapphire Firmware from DK 1.3.0 to DK 1.4.0, you will see the following caution soon after starting Sapphire software installation:

CAUTION: This process replaces the firmware in the Sapphire NewPro.This will erase all customer data. Answer no to cancel this process.

Follow the prompts to complete the firmware upgrade.


55

CAUTION: This process replaces the firmware in the Sapphire NewPro.This will erase all customer data. Answer no to cancel this process.

Proceed with firmware change?

<yes or no> yReprogramming BIOS and Diagnostic KernelDO NOT INTERRUPT THE PROCESS, OR THE SAPPHIRE MAY BECOME UNUSABLE.ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ>>º Autoflash Program, Version 1.3 ºº Copyright 2000-2003 by VeriFone INC. All rights reserved.ºÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ

Preparing to write: System BIOS Version 2.0.3

WARNING -- PRESSING RESET OR TURNING OFF THE POWER DURING THE UPDATE PROCESS WILL RESULT IN INVALID FLASH CONTENTS

Flash Memory Map

FILE NAME SIZE FLASHED TObios 0x40000 BIOS device

Processing file : biosFlash Programming Succeeded!

ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ>>º Autoflash Program, Version 1.3 ºº Copyright 2000-2003 by VeriFone INC. All rights reserved.ºÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ

** Diagnostic Kernel will be flashed with file dk

** File dk is larger than the DK flashpart!

** Remaining 0x6C000 bytes of file dk will be flashed to the beginning of the BIOS flash part.

WARNING -- PRESSING RESET OR TURNING OFF THE POWER DURING THE UPDATE PROCESS WILL RESULT IN INVALID FLASH CONTENTS


56

Flash Memory Map

FILE NAME SIZE FLASHED TOdk 0xFC0000 DK devicedk 0x6c0000 BIOS device

Processing file : dkProcessing file : dk (BIOS device)

Flash Programming Succeeded!

BIOS and Diagnostic Kernel versions were successfully updated.

Please return the DIAG switch to the down position to restart in the new Diagnostic Kernel and start the application installation process.

Please note that you will need to run loadinstallkdi again from the new Diagnostic Kernel.

NOTE: These statements repeat until you put the Diag switch down, after which the system reboots automatically.

Please return the DIAG switch to the down position to restart in the new Diagnostic Kernel and start the application installation process.

Please note that you will need to run loadinstallkdi again from the new Diagnostic Kernel.Rebooting to Linux Installer **** LynxOS is down ****

The DK and operating system have been upgraded. Log in again as user ‘install’ and follow the prompts.

Topaz Installation for Sapphire/Topaz SitesAfter installing Sapphire NewPro software, you will be prompted “Do you have a Topaz?” Key ‘y’, and you will be told to switch the RS-232 cable connected to the installer’s laptop to the CONSOLE port on the right side of the first of any Topaz workstations to be loaded.

NOTE: During Topaz installation, when the choice of “1. Complete Installation” and “2. Custom Installation” appears, you must choose “1. Complete Installation.” Do NOT choose option “2” unless instructed to do so by the VeriFone Help Desk. A “Custom Installation” may not complete properly.


57

NOTE: The first workstation loaded must be given the number of Topaz terminals on site. Thus if there are four Topaz workstations to be loaded with the upgraded software, the first to be upgraded would be given the designation of Terminal 4. The second upgraded would be given the designation of Terminal 3. The third, Terminal 2. And finally the fourth, Terminal 1. This is to insure that the terminals receive correct IP addresses.

Proceed with the Topaz installation using HyperTerminal.

NOTE: Topaz hardware and software installation instructions may be found on the VeriFone Premier Web Connection at Petro Downloads > Topaz > Topaz: Other Documentation.

SMS Installation for Sapphire SitesNOTE: If the previous version is not needed, remove the older version of SMS

before installing the current version.

1. Insert a CD containing the folder SMS v1.10.03 for CVXPAK 6.00.15 in the CD drive of the PC that is going to run SMS.

2. Open the SMS folder and double-click on setup.exe.

V910 InstallationSee the documentation section at VeriFone Premier Portal > Connect > Petro Downloads > EPS: V910 for installation instructions.

NOTE: You must be certified in order to access this section.


58

Minimum Requirements

Displays

4x40 Display v3.03

Customer Display v2.01

LED Display v1.00

Gembus Modem

Ruby 24MHz v1.08

Gemix Operating System

Ruby 24MHz v2.5.9

Gemstall

Gemstall v2.52

Gemstone Ruby II

Workstation 24MHz

Non-DCR Controller 24MHz

DCR Controller 24MHz

Gemstone Ruby II Memory

Workstation 8MB

Controller 8MB

Keyboards

MSR/13x5 v2.02

MSR/15x8 v3.01

Other

RS-232 to RS-422 Converter DCR controller

Network

Network Version 06.00.63.15a


59

Sapphire-01 and Sapphire-02 Compact Flash

Support for 1 - 4 Topaz Terminals

128 MB Compact Flash


512 MB Compact Flash

Sapphire-03 Compact Flash


512 MB Compact Flash (Minimum)


60

Fuel Hardware Peripherals Supported

Dispensers Supported VeriFone advises using the “Recommended Version” shown here. Unlisted versions may not work reliably with the Ruby SuperSystem®, Sapphire, or Topaz.

Dispenser/Interface

Supported:Yes/No

RecommendedVersion

Notation

VeriFone

SFC Application Yes v2.03.04

SFS (Suite) Yes v1.00.12

Bennett

DOSPIB No

515 Yes v515T01.08

Horizon 1 Yes v6.27 Supports Standard POP Discount &

Generic Loyalty with Bennett 515 interface box, firmware v.507

Horizon 2 Yes v2.15 Supports Standard POP Discount &

Generic Loyalty with Bennett 515 interface box, firmware v.507

Dresser/Wayne

CPU Yes v49.37 v49.32 and v49.34 are not supported.

PIB Yes v39000 Loyalty not supported

Fusion Yes v2.0.1.24

HyperPIB Yes v54000 Supports Standard POP Discount & Generic Loyalty

Arbitration Board Yes


61

Gilbarco

PAM 1000 Yes v32.1.60 Supports Standard POP Discount & Generic Loyalty

PAM 5000 Yes 410-27-1.05 Supports Standard POP Discount & Generic Loyalty

SMART Connect No

Schlumberger

SAM Yes vC4501.04.30 Supports Alternate POP on Dual-PPU CardScan 4000s

Tokheim

DHC Yes v6.17 Supports Standard POP Discount & Generic Loyalty

VXDHC Yes v4200.03.09 Supports Standard POP Discount & Generic Loyalty


62

Dispenser Card Readers — Supported Options VeriFone advises using the “Recommended Version” shown here. Unlisted versions may not work reliably with the Ruby SuperSystem®, Sapphire, or Topaz.

Bennett

Bennett: DCA

Option Supported:Yes/No

RecommendedVersion

Part Description/Notation

Non-debit Yes N/A

Cash Acceptors No

Debit No

Graphics No

Debit

Non-debit Yes N/A

SDES (DUKPT) No

TDES No

M/S No

Bennett: DCT (VeriFone Everest Card Reader)


RecommendedVersion


Cash Acceptors No

Graphics No

Debit

Non-debit Yes 1.02.02

SDES (DUKPT) Yes 1.02.02

TDES No

M/S Yes 1.02.02


63

Dresser/Wayne

Legacy CAT


RecommendedVersion


Cash Acceptors Yes 64.00

DSM Yes v1.19

Graphics Yes 64.00

Scanner Yes 64.00

Secure CAT No

Debit

Non-debit(not enhanced)

Yes 58.00

SDES (DUKPT) Yes 64.00

TDES No

M/S Yes 64.00

Dual CAT


RecommendedVersion



DSM Yes v1.19

Graphics Yes 103.00

Scanner Yes 103.00

Secure CAT No

BCB Yes 5.1

Debit

Non-Debit Yes 103.00


TDES No

M/S Yes 103.00


64

Dresser/Wayne (continued)

Vista3V


Recommended MinimumVersion



DSM Yes v1.19

Graphics Yes 103.00

Scanner Yes 103.00

Secure CAT No

BCB Yes 5.1

iGEM Yes 36.00

Debit



TDES No

M/S Yes 103.00


65

Dresser/Wayne (continued)

Ovation




Cash Acceptors No

DSM Yes v1.19

Graphics Yes 206.00

Scanner Yes 206.00

Secure CAT No

iGEM Yes 36.00

Debit



TDES No

M/S Yes 206.00

IX




Cash Acceptors No

DSM No

Graphics No

Scanner No

Secure CAT No

iGEM No

Debit

Non-Debit No

SDES (DUKPT) No

TDES No

M/S No


66

Gilbarco

FlexPay Secure Card Reader


RecommendedVersion


Graphics No

Cash Acceptors No

GSM No

Scanner No

Contactless (RFID) No

Smart Pad No

Debit

Non-Debit No

SDES (DUKPT) No

TDES No

M/S No

Z80 Logic Board


RecommendedVersion


Cash Acceptors No

GSM No

Graphics No

Scanner No


Smart Pad No

Debit


SDES (DUKPT) No

TDES No

M/S No


67

Gilbarco (continued)

NOTE: Encrypting PIN Pad (EPP) without Advanced GSM is not supported unless the Ruby Card feature is present.

NOTE: Please contact your Gilbarco servicer for the correct setup of the EPP and the mapping of the keypad.

Encrypting PIN Pad (EPP) with Advanced GSM


RecommendedVersion


Cash Acceptors No

Advanced GSM Yes

See CRIND versions below.

Graphics Yes

Scanner Yes

Contactless (RFID) Yes

Smart Pad No

Debit

SDES (DUKPT) Yes See CRIND versions below.

TDES Yes

M/S No

CRINDs

Advantage Yes 62.6.10

Encore 300 Yes 62.6.10

Encore 500 Yes 3.1.50

Eclipse Yes 3.1.50


68

Gilbarco (Continued)

Advantage CRIND (Z180 Logic Board)


RecommendedVersion


Cash Acceptors Yes 60.8.90

GSM Yes

Graphics: Monochrome

Yes 60.8.90

Graphics: InfoScreen

Yes 60.8.90 InfoScreen graphics are supported only in

single-line mode.

Scanner Yes 60.8.90

Contactless (RFID) Yes 60.8.90

Smart Pad No

Debit

Non-debit Yes 60.8.90 Note that v60.7.30 is NOT supported for

any mode.


TDES No

M/S Yes 60.8.90


69


Encore 300


RecommendedVersion


Cash Acceptors Yes 60.8.90

GSM Yes

Graphics: Monochrome

Yes 60.8.90

Graphics: InfoScreen

Yes 60.8.90 InfoScreen graphics are supported only in

single-line mode.

Scanner Yes 60.8.90

Contactless (RFID) Yes 60.8.90

Smart Pad No

Debit

Non-debit Yes 60.8.90 Note that v60.7.30 is NOT supported for

any mode.


TDES No

M/S Yes 60.8.90


70


Options for the Gilbarco Encore 500 and Eclipse models are supported as shown only with required component versions as shown in the Component Table below. The component version must at least meet the versions shown in the Component Table. In addition, the dispensers must be upgraded to the Gilbarco power supply shown.

Encore 500/Eclipse



Cash Acceptors Yes

GSM Yes

Graphics: Monochrome Yes


Smart Pad No

Debit

Non-debit Yes

SDES (DUKPT) Yes

TDES No

M/S No

Encore/Eclipse Component Version Number/Part Number

CRIND Bios v2.1.95

CRIND MIP v2.0.00

Pump v1.6.95

Pump MIP v10.0.07

Pump Door Node v01.0.37

Printer Neuron v1.01

Printer HOST v1.04

Gilbarco Power Supply P/N M02274A001


71

These are the current recommended versions for Gilbarco models. Other Gilbarco dispenser model versions are currently supported.

Gilbarco Dispensers

Dispenser Description Version

Encore 500 Pump Control Node 1.8.30

MPD Legacy 70.9.82

MPD Modular Advantage 70.9.82

Selectable Blender Modular Advantage 75.6.10


72

Schlumberger

4000


RecommendedVersion

Notation

Cash Acceptors No

SSM Yes

Graphics No

Scanner No


Debit


SDES (DUKPT) Yes 0130.04.15 Debit Module Software v401.01.06

TDES No

M/S Yes 0130.04.15

Centurion


RecommendedVersion

Notation

Cash Acceptors No

SSM Yes

Graphics No

Scanner No


Debit


SDES (DUKPT) Yes 1000.05.04 Debit Module Software v401.01.06

TDES No

M/S Yes 1000.05.04


73

Secure PumpPAY Model OP 4100

Secure PumpPAY Model MX 760

Secure PumpPAY Model OP 4100


RecommendedVersion


Graphics Yes 1.00.15

Debit

Non-Debit Yes 1.00.15


TDES Yes 1.00.15

PCI Yes 1.00.15

Secure PumpPAY Model MX 760


RecommendedVersion


Graphics Yes 2.00.07

Debit

Non-Debit Yes 2.00.07


TDES Yes 2.00.07

PCI Yes 2.00.07


74

Tokheim

Premier B


RecommendedVersion


Cash Acceptors Yes N/A

TED Yes v300 or v400

Scanner No

Debit

Non-debit(4-line display)

Yes JP02.18.00

TDES No

Debit TDS Plus(4-line display) SDES (DUKPT)

Yes MT0301.00

Debit TDS Plus(4-line display) M/S

Yes MT0301.00

Debit TED(4-line display)SDES (DUKPT)

Yes MTQD02.00

Debit TED(4-line display) M/S

Yes MTQD02.00

Insight GraphicsNon-debit

Yes MTPQ06.03

Insight GraphicsSDES (DUKPT)

Yes MTPQ06.03


75

Tokheim (continued)

Premier C


RecommendedVersion


Cash Acceptors Yes N/A

TED Yes v300 or v400

Scanner No

Debit

Non-debit(4-line display)

Yes JP02.18.00

TDES No

Debit TED(4-line display) SDES (DUKPT)

Yes MTQD02.00

Debit TED(4-line display) M/S

Yes MTQD02.00

Insight GraphicsNon-debit

Yes MTPQ06.03

Insight GraphicsSDES (DUKPT)

Yes MTPQ06.03


76

Ruby/Sapphire/Topaz Options Supported

Backup Power Supply (UPS)

ONEAC 200, with RJ-11 port protection, is recommended.

VFI P/N P040-07-040

Car Wash

Ryko Code-A-Wash III Version 15554-009, Rev. E

A Ruby Card is needed to enable this feature.

Ryko Code-A-Wash IV 19574-006 Rev. N


Unitec POS4000 Firmware version 6.67


Car Wash PayPoint - Topaz Only

Unitec Enterlink Super Interface

Version 2. Firmware version 2.13


Cash Drawer

Ruby terminal VFI P/N P040-08-024

VFI P/N P040-08-019

VFI P/N P050-01-200Note: Must have adapter:

VFI P/N 22839-01 Rev 3 or Rev C. Do NOT use adapters marked with Rev 1 or Rev A. These adapters can be damaged if plugged into a powered-up Ruby. In addition, the adapter MUST ONLY be plugged into one of the Ruby CASH DWR ports.


77

Coin Dispenser

Transact2 VFI P/N P040-08-023

Displays

32 Icon Display (32 fueling pts) VFI P/N P040-08-017

Customer Display VFI P/N P040-08-300

EASY IDTM

A Ruby Card is needed to enable this feature. Easy ID is supported for ALL states as long as the Mag Stripe/2D codes use the AAMVA standard format. Please contact your local Department of Motor Vehicles for details about your state.

Electronic Fuel Price Signs

Supported with tested interface:• DakTronics: DM-100 PSC

(0A-1196-0133)• FutureMedia Displays

Inc.: PriceVision LED Model FMD9-GSX.

Supported:• Everbrite• Skyline • NOVYC Electronics Inc.• PWM

Note: Contact manufacturer for details.

Available for Sapphire sites with SMS (Sapphire Management Suite). The Price Sign Controller (PSC) and an RS-232 connector is supplied by the sign manufacturer. A Ruby Card is needed to enable this feature.

Expanded PLUs

Expanded PLUs A Ruby Card is needed to enable this feature.

Fast Food

Fast Food A Ruby Card is needed to enable this feature.

Laser Scanners (Ruby Ready)

Use the following URL to access a list of laser scanners that have been approved by VeriFone.http://www.verifone.com/industry-solutions/petroleum-convenience/integrated-partner-solutions/scanners.aspx


78

Money Order

Note: Money Order devices can connect to serial ports on GemPro and NewPro.

Travelers Express: Delta Network Terminal 780T Version 3.5

Option Code: mgdelta

P/N 11-0021-001

Printer model: 1600

VFI cable: VFI P/N 55296-03Note: The money order printer should

not be connected to a MUX.

Note: Money Order can be connected to both NewPro and GemPro serial ports.


Western Union Money Order Dispenser System:Version 3.5

Option Code: wut7e

P/N FDX-400(Version 7534 and above)

Adaptor: DB-9M to RJ-45 (VFI P/N 13641-01)Requires an RS-232 cable (P/N 13836-XX)

Note: Money Order can be connected to both NewPro and GemPro serial ports.

Interface: FIP11 Interface Module (P/N 010064-02)

Note: The FIP11 Interface module cannot communicate with the Ruby terminal via a MUX.



79

Western Union Money Order Dispenser System:ICE6000 Terminal (Ethernet)

Option Code: wuice

Requires an Ethernet cable.


Note: If at a Sapphire site, Gemstall GemPro Money Order as On_NewPro and Gemstall Ruby workstations as MO_NotOnThisRuby. Do not Gemstall Ruby terminals with the On_NewPro option.

PINpads

MX 870/MX 860/MX 850/MX 830 Multimedia

Note: The MX 830 PINpad must support IP connection.

See the Sales Representative for part numbers.

Note: For debit, PINpads must be injected with the appropriate key for the application.

Port Multiplexor

Black Box COS-II Used when additional RS-232 ports are needed.

Note: See VASC Bulletin 0207-002


80

Printers (Point of Sale)

Ruby terminals VeriFone P540 Ruby SuperSystem Dual Printer Combination with thermal receipt printer and impact journal printerVFI P/N V050-02-001Paper Width Receipt Printer:80 mm (3.15”)Paper Width Journal Printer:76 mm (2.99”)

Note: Printers replace multi-station dot matrix printers. Printers connect to Ruby terminals only. Printers sold as a pair only.

Epson TM-U930 Multi-station dot matrix printing both receipts and journalMinimum: v1.2 ESC/POSVFI P/N P040-02-004Paper Width: 70 mm (2.75”)

Epson TM-U950 Multi-station dot matrix printing both receipts and journalMinimum: v1.02 ESC/POSVFI P/N P040-02-006Paper Width: 70 mm (2.75”)


81

Sapphire/Ruby POS terminals and Sapphire/Topaz POS terminals

Seiko DPU-E427 Thermal journal only printerVFI P/N P040-02-009Paper Width: 58 mm +0/-1 mm (2.28”-2.24”)Seiko P/N (Paper): TP-E23C-1

Note: This printer must be used if a printed journal is wanted on site with Sapphire. To print receipts at the Ruby terminals in a Sapphire system, the EPSON TM-T88III Thermal receipt only printer is recommended, but Sapphire sites may use either of the Epson Multi-station dot matrix printers with Ruby terminals to print receipts only.

VeriFone Thermal receipt only printer (May be used to replace EPSON TM-T88)VFI P/N P040-02-020Paper Width: 79.5 mm ±.5 mm (3.15 ±.02”)EPSON P/N (Paper) NTP080-80

EPSON TM-T88III Thermal receipt only printerVFI P/N P040-02-008Paper Width: 79.5 mm ±.5 mm (3.15 ±.02”)EPSON P/N (Paper) NTP080-80

Note: For installation information and DIP switch settings, refer to the “VASC Field Service Bulletin No. 0406.001”.

Secondary Network

Mannatec®, FUELMAN®, or CFN®

Interface: Secondary Network Protocol v. 2.0


Note: A site may accept only one brand of secondary network Fleet card.


82

Tank Level Sensor

EBW: Auto/Stik Firmware version AMOCO4

Requires an RS-232 cable (P/N 13836-XX)

Requires an adapter DB-9M, standard (black) (VFI P/N 13641-01)

Emco: EECO System 1500 Firmware version 023E

Requires an RS-232 cable (VFI P/N 13836-XX)

Requires an adapter DB-9F, null modem (red) (VFI P/N 13638)

Emco: EECO System 2000 Firmware version 004L



Emco: EECO System 3000 Firmware version 005I



Veeder Root: TLS 250 Requires an RS-232 cable (VFI P/N 13836-XX)

Requires an adapter DB-25M, null modem (red) (VFI P/N 13581-01)

Veeder Root: TLS 350 Requires an RS-232 cable (VFI P/N 13836-XX)

Requires an adapter DB-25M, null modem (red) (VFI P/N 13581-01)


83

Important Information

Initial Release Series For CVXPAK and V910 Software

Overview

These Release Notes, Ruby/Sapphire, and Sapphire/Topaz are for CVXPAK 6.00.15 in the release series of CVXPAK using the VeriFone EPS (Electronic Payment Server) as the network connection. The hardware for the EPS is the VeriFone V910. For details on the CVXPAK concept and details on converting sites to CVXPAK follow.

The Ruby/Sapphire/Topaz EPS Interface

Overview

CVXPAK is the Ruby/Sapphire and Sapphire/Topaz application that utilizes the VeriFone generic EPS (Electronic Payment Server) instead of a direct Ruby-to-network connection.

The EPS handles all primary network card processing for any POS device on the site. The VeriFone EPS is the V910 server.

CVXPAK has the advanced capability of updated Ruby/Sapphire/Topaz software including:

■ Support for the browser-capable Sapphire Site Controller

■ Support for the POP Discount feature

■ Support for cash acceptors and graphics at DCRs

The most obvious difference on site is that the Ruby and Topaz magstripe reader is disabled, and credit and debit card swiping is performed on a VeriFone MX800 Series PINpad connected to the V910 EPS through a router or switch.

Card Usage: Primary Network

Credit and debit cards are swiped by the customer outside at the DCR as usual, or inside at the VeriFone MX800 Series PINpad. While the mag-stripe readers on Ruby terminals are disabled, the Ruby or Topaz keyboards are used for manual entry of card information.


84

Card Usage: Secondary Network Proprietary Cards

Mannatec, FUELMAN, or CFN secondary network Proprietary Cards are also swiped outside at the DCR as usual, and inside at the MX 800 Series PINpad. As before, a VeriFone Vx570 terminal serves as the interface with the secondary network.

Configuration: EPS V910

The EPS card table functions are configured by the host network.

Configuration: Ruby

With the EPS, each POS device must have a POP (Point Of Purchase) ID. Each of the up-to-four Ruby terminals possible in a Ruby/Sapphire system is identified by their POP ID. By default, this POP ID starts at ‘1’ for a Ruby and counts up until the maximum of POP IDs is reached. These POP IDs may be configured at System Setup > Network Mgr > POS Configuration > EPS Comm Settings.

Configuration: Topaz

The Topaz Network Manager functions are set in the network applet and the network connectivity is handled by the EPS. With the EPS, each POS device must have a POP (Point Of Purchase) ID. Each of the Topaz terminals possible in a Sapphire/Topaz system is identified by their POP ID. By default, this POP ID starts at ‘01’ for a Topaz and counts up until the maximum of POP IDs is reached. These POP IDs may be configured at SMS > Network Mgr > Network Config. (Applet).

V910 ConfigurationAs part of the installation, the system will already be configured to communicate with the V910. See the IP Configuration Tool Guide for setting up the IP addresses.

V910 Network ConfigurationThe Merchant ID, Terminal ID, and Host IP Address and Port are required to be entered by the VeriFone Authorized Service Contractor (VASC) at the following areas:

■ Ruby > System Setup > Network Manager >EPS Network Functions > EPS Configuration

■ Topaz > CSR Func > Network Menu > EPS Network Functions > EPS Configuration

Additional parameters are also set up as part of the configuration download that is sent to the V910. These parameters cannot be setup using SMS


85

NACS Three-Digit Product CodesNACS (National Association of Convenience Stores) three-digit product codes are supported. For fuel transactions, product codes may be set up for both self service and full service for each of the up to nine named types and grades of fuel.

Backdoor PasswordNOTE: This password does not allow access to full account numbers.

Several functions and parameters require the entry of a backdoor password. These functions and parameters should only be used with the assistance of the VeriFone Technical Support Center, which is available 24 hours a day, 7 days a week at 888-777-3536.

Gemcom VersionThis application requires Gemcom 1.08.08 or higher, available on the new VeriFone Premier Web connection (go to Petro Downloads > Sapphire > Sapphire Utilities). Gemcom 1.08.08 or higher is recommended for non-Sapphire sites as well.

Gilbarco Sites Must Set PAM JumperGilbarco sites must enable the PAM (Pump Access Module) for buffer price mode by making the CPU board jumper JP7=A.

POP Discount Enhancements and Limitations

Alternate POP Lowest Price Level Configuration

When using the Alternate Configuration for POP Discount, only sites with Tokheim dispensers may use either the value ‘1’ or the value ‘2’ for the parameter “POP Lowest Price Lvl (1=CA 2=CR)” in Fuel Manager > Site Parameters > Fuel Site Parameters. Dresser/Wayne and Gilbarco sites must enter the value ‘1’ when configuring this parameter.

Bennett DCTs Support Standard POP Configuration

Bennett DCTs with Horizon 1 (firmware v6.27) or Horizon 2 (firmware v2.15) dispensers now support POP Discount with Standard Configuration only. To support POP Discount, the dispensers must be equipped with a Bennett 515 interface box (firmware v5.07).

Dresser/Wayne HyperPIB 54000 Sites May Use Standard POP

Dresser/Wayne sites equipped with HyperPIB 54000 or higher may use the Standard Configuration for POP Discount. Sites without HyperPIB 54000 or higher must use the Alternate Configuration for POP Discount. Note that if the Standard Configuration is used, and if dual cash/credit pricing is enabled, the POP Discount will be given on both cash and credit sales.


86

Gilbarco Sites Must Set PAM Jumper

As noted above, Gilbarco sites must enable the PAM (Pump Access Module) for buffer price mode by making the CPU board jumper JP7=A. This applies to POP as well as other sites.

Gilbarco With PAM May Use Standard Configuration

Gilbarco sites with PAM version 32.1.60 or higher may now use the Standard Configuration for POP Discount. The Alternate Configuration remains available for all sites including Gilbarco.

POP Fueling Limit

POP Discounts awarded for purchasing specified PLUs or departments, such as car washes, may now be limited by cutting off fueling in a POP-eligible transaction at a pre-configured dollar amount. Only the fuel purchase, and not any other merchandise or service, such as a car wash, counts towards the dollar fueling limit.

Standard Configuration: 10 Prices Per Fuel Grade

POP Discount sites using the Standard Configuration may now set up to 10 price definitions for each grade of fuel offered for a POP Discount. Previously, only two price definitions could be set up for each grade of fuel.

Product Codes

Product Code Conversion

Note that, as part of the changes made in the CVXPAK application, it now supports the NACS 3-Digit product codes. When restoring the site’s departments and PLUs, each item must change its product code to match the new product code from the NACS product code listing. In order to accomplish this, there are a variety of ways to convert the products. Additionally, there a multiple ways in which PLUs and Departments can be setup.

Product Code Setup

To set up product codes, do one of the following:

■ Assign each PLU and each department a specific product code. Then when a PLU is sold, it will use the product code assigned to that PLU. And when a department is sold it will use the product code assigned to that department.

■ Assign each PLU a product code of zero. If this option is chosen, then each PLU must be assigned a department and that department must have the corresponding NACS product code. Then, when a PLU is sold, it will use the product code assigned to the department that the PLU is associated with.

NOTE: Do NOT assign a product code of zero to a department.


87

Converting Product Codes

You can use one of the following methods to convert product codes:

■ The product codes can be converted manually once the PLU and Departments are pushed over to the POS by utilizing the POS and selecting each individual PLU and department.

■ The product codes can be converted in the Ruby Manager application. This is a manual process, but the user interface in Ruby Manager allows this to be done quicker then selecting each item on the POS.

■ The product codes can be converted by the customer using their back office product. This process will vary depending on the capabilities of the back office software program.

■ The product codes could be provided by the sites price book provider. Since these product codes are the NACS standard, this data is no longer unique for the POS or the application and, as part of the standard price book that the store receives, they may have the ability to send the items, PLUs, and Departments already assigned with the NACS product codes.

Obviously, it is very important that this conversion be correct during the install, so it will be very important that you work closely with the site, manager, or the party responsible for the customer.

Proprietary Cards Using Secondary Network: Mannatec®, FUELMAN®, or CFN®

Upgraded Interface

The Ruby application’s secondary network Proprietary card interface has been upgraded to Protocol version 2.0 from version 1.0. Sites using secondary network Proprietary Fleet cards with Proprietary Card Protocol version 1.0 must get their ACU (Authorization Control Unit) upgraded by the secondary network Proprietary card provider to version 2.0 for the Ruby terminal to interface properly with the secondary network and the VeriFone Vx570 terminal. Note that a Ruby card is required, and that a site may elect to accept only one secondary network Proprietary card: either Mannatec, FUELMAN, or CFN.

NOTE: When the Proprietary card interface with ACU version 2.0 is connected through a MUX (port MUtipleXer), the MUX must be reconfigured to allow both numeric and non-numeric values, both of which are necessary for interfacing with version 2.0. Switch number 7 of switch banks SWA and SWB must both be set to “ON” in the configuration. See “VASC Field Service Bulletin No. 0206-003” for details on reconfiguring the MUX.

Ruby, Sapphire, and Topaz In Release NotesRelease Note categories — such as New Features, Enhancements, and Resolutions — are separated into such sections as “Ruby/Sapphire/Topaz”; “Sapphire”; and “Topaz”. For instance, a New Feature designated “Ruby/


88

Sapphire/Topaz” would apply to Ruby sites, Sapphire sites, and Sapphire sites with Topaz and/or Ruby workstations; while a New Feature designated “Topaz” would apply only to sites with Topaz workstations.

Ruby/Sapphire/Topaz Sites

Overview

Sapphire Sites

Sapphire software has two parts:

■ “GemPro” refers to the part of the Sapphire software package that runs the Ruby terminals and Ruby-side of the Sapphire Site Controller

■ “NewPro” refers to the part of the Sapphire software package that runs the Sapphire side of the Mini-server

Topaz Sites

Topaz software is included with the NewPro software and is installed after Sapphire NewPro.

Version Numbers

The Sapphire GemPro version, the Sapphire NewPro version, and the Topaz version use the version number: EPSPAk 3.00.16. The suite version is CVXPAK 6.00.15. The SMS version is 1.10.03.

Software Suite

The Sapphire, Topaz, and SMS software is distributed as a suite. Use only the software distributed in the Sapphire/Topaz/SMS suite. Do NOT make any substitutions. The application will not run correctly or at all if other software is substituted.

Sapphire LOGIN Switch In “UP” PositionThe LOGIN switch on the front of the Sapphire Site Controller must be placed in the “UP” position and left that way at all times. The only exceptions are when upgrading or when a VeriFone representatives asks that the switch be put in the “DOWN” position for diagnostic purposes.

V950TM PC Replacing Dell PC

Overview

HPV-20 sites may now be equipped with the VeriFone V950 PC, which is a replacement for the Dell PC. The operation of the V950 PC and the Dell PC is similar, with the V950 having an advanced operating system (XPE). All Sapphire sites require an HPV-20 which can be the Dell PC or the VeriFone V950 PC. The


89

HPV-20 is required for the Sapphire's installation and supports Auto Upgrade and Auto File Repair. In addition, the V950 system allows the VeriFone Technical Support Center to remotely conduct diagnostics while the POS is operating.

TerminologySystem — The system and software enabled by either the V950 PC or the Dell PC is still referred to as “HPV-20”.

PC Name — Since either PC may be used to run HPV-20, the term “V950/Dell PC” is used to refer to the PC running the HPV-20 system.

VASC Field Service Bulletins and Release NotesCheck for VASC Field Service Bulletins issued after the publication date listed on the cover of these Release Notes for updated information. Peripheral devices supported, especially fuel hardware peripherals, may change after the release of software.

If there is a conflict between what is stated in these Release Notes and what is stated in a VASC Field Service Bulletin with a later publication date, the information in the Bulletin should be considered correct. Installation of non-supported peripherals may void the VeriFone warranty.

DocumentationBrief guides to various features, which used to appear in the Release Notes, may now be downloaded from the new VeriFone Premier Web connection at Petro Downloads > Features Reference:

■ POP Discount Features Reference (Base 153): Includes a description of the POP Discount feature and detailed instructions on configuring the POP Discount feature. Check items in this Important Information section and recent ASC Field Service Bulletins for complete fuel hardware restrictions.

■ HPV-20 Release Notes Features Reference: Includes instructions on installing and using HPV-20. Steps for using HPV-20 for upgrades are also included.

■ Sapphire Release Notes Features Reference: Includes a description of Sapphire’s features, cabling instructions, minimum requirements, and instructions for using Sapphire to upgrade applications.

Sapphire and SMS: Other Documentation

Comprehensive guides along with various utilities can be found on the new VeriFone Premier Web connection (at Petro Downloads > Sapphire > Sapphire and SMS: Other Documentation). Among the publications are:

■ Sapphire Installation Guide: A guide to installing the Sapphire system.

■ Sapphire Software Installation Guide: A guide to installing the Sapphire software.


90

Topaz Archive

Among other documents in the Topaz archive on the new VeriFone Premier Web connection at Petro Downloads > Topaz > Topaz: Other Documentation is the Topaz Installation Guide: A guide to installing Topaz workstations.

Weights and MeasuresSupport for cash and credit pricing at the dispenser requires explicit cash and credit selections on the dispenser. This is in compliance with the Weights and Measures Guidelines for Selectable Unit Price Capability, section G-S.5.1.

Notice: This Ruby software supports a POP Discount feature, which allows a point-of-purchase discount on fuel based on the purchase meeting certain pre-defined transaction criteria. It is possible that the Weights and Measures department in your state may consider this POP Discount feature, when used in a post-pay scenario, to be in violation of state regulations. YOUR IMPLEMENTATION OF THE POP DISCOUNT FEATURE IS DONE AT YOUR OWN RISK. VERIFONE EXPRESSLY DISCLAIMS ANY LIABILITY FOR CLAIMS, FINES OR DAMAGES RESULTING FROM IMPLEMENTATION OF THE POP DISCOUNT FEATURE IN A LOCALE WHERE IT IS DEEMED A VIOLATION OF LOCAL OR STATE REGULATIONS. YOU SHOULD CONSULT YOUR LOCAL WEIGHTS AND MEASURES ENFORCEMENT GROUP BEFORE IMPLEMENTING THE POP DISCOUNT FEATURE.

© 2012 VeriFone, Inc. All rights reserved.

No part of this publication covered by the copyrights hereon may be reproduced or copied in any form or by any means - graphic, electronic, or mechanical, including photocopying, taping, or information storage and retrieval systems - without written permission of the publisher.The content of this document is subject to change without notice. The information contained herein does not represent a commitment on the part of VeriFone. All features and specifications are subject to change without notice.VeriFone, the VeriFone logo, and Ruby SuperSystem are registered trademarks of VeriFone, Inc. Sapphire, Topaz, HPV-20, Ruby Manager, Everest, EASY ID, Electronic Journal On-site, and Ruby Card are trademarks of VeriFone, Inc. in the U.S. and/or other countries. All other trademarks or brand names are the properties of their respective holders.

isd software release notes - maintenance page

Documents