Salesware Update: Version 4.4.02 Release Notes (3/5/2015)

Details ..................................................................................................................................................................... 3

System recommendations ...................................................................................................................................... 3

Installation instructions .......................................................................................................................................... 4

Additional information ........................................................................................................................................... 4

What’s new in Salesware version 4.4.02................................................................................................................. 5

Scope and audience ............................................................................................................................................. 5

Components in this release.................................................................................................................................. 5

Enhancements ........................................................................................................................................................ 7

Changes to Charge Cards ........................................................................................................................................ 7

Added Aloha Stored Value Cards ......................................................................................................................... 7

Configuration ................................................................................................................................................... 7

Restrictions ...................................................................................................................................................... 9

New settings for preauthorization ..................................................................................................................... 10

Changes to Kiosk ................................................................................................................................................... 10

HTML Kiosk Interface ......................................................................................................................................... 10

Installation and configuration ........................................................................................................................ 11

Use ................................................................................................................................................................ 14

Kiosk settings reference ................................................................................................................................. 18

Troubleshooting ............................................................................................................................................ 21

Changes to Reporting ............................................................................................................................................ 22

E-Commerce Transaction Detail Report ............................................................................................................. 22

Changes to Ticketing ............................................................................................................................................. 22

Bosch security recorder integration ................................................................................................................... 22

Introduction ................................................................................................................................................... 22

Configuration ................................................................................................................................................. 23

Examples of use ............................................................................................................................................. 23

Additional functionality for Block Holds ............................................................................................................. 25

Block Holds can now be released by date ...................................................................................................... 25

Editing Block hold categories and subcategories ............................................................................................ 27

1

Cascading access records through multiple layers of modifiers .......................................................................... 28

Sort sale history by date/time ............................................................................................................................ 29

Additional functionality for Member Benefits .................................................................................................... 29

Automatic drawer pop on Closeout ................................................................................................................... 29

Automated Revenue Recognition on expired and un-used tickets/passes .......................................................... 29

Configuration ................................................................................................................................................. 30

Reporting ....................................................................................................................................................... 34

Receipts can now be emailed from Sales ........................................................................................................... 35

Configuration ................................................................................................................................................. 35

Use ................................................................................................................................................................ 41

Payment plan refund warning ............................................................................................................................ 43

Changes to ww.dll ................................................................................................................................................. 43

Enhancements to the MOVEREVENUE function ................................................................................................. 43

Troubleshooting ............................................................................................................................................ 45

Global Specials applied to linked items in E-Commerce ..................................................................................... 45

Salesware platform changes ................................................................................................................................. 45

RFID scanning improvements............................................................................................................................. 45

.INI change......................................................................................................................................................... 46

Adjusted parameters ......................................................................................................................................... 46

Changes to automatic update checks ................................................................................................................. 46

Updates to the default Siteconfig.config ............................................................................................................ 46

Known issues ........................................................................................................................................................ 46

Fixes ...................................................................................................................................................................... 47

Copyright .............................................................................................................................................................. 53

2

Details

We have uploaded 4.4.02 (Update 02 for version 4.4) for download from the Siriusware® Inc. Information Portal.

System recommendations

You must meet the minimum system requirements as stated in the Salesware System Architecture and Specifications document. You can refer to the tables and figures in this document to ensure your site meets these specifications.

Siriusware’s policy is not to maintain operating systems not supported by Microsoft. As such, this past April, Microsoft no longer supports or provides security patches for the Windows XP operating system. PCI compliance requires that you ensure all payment system components are protected from known security vulnerabilities. If you are running Siriusware applications on Windows XP computers, it becomes extremely difficult for you to ensure your system is protected against emerging security threats and remain compliant with PCI.

Important notes:

• Use of a supported operating system is outlined in PCI DSS Requirement 6.1, which requires that the merchant (you) ensure that all system components and software are protected from known vulnerabilities by regularly applying vendor-supplied security patches. As Microsoft does not provide these for Windows XP, it is difficult for you to meet this requirement if you use Windows XP for your Siriusware system. Your simplest course of action is to stop using the Windows XP operating system for Siriusware applications. For more information, consult a PCI Qualified Security Assessor or see the PCI Security Council web site and search for article #1130.

• Additionally, use of a computer operating system that is not regularly updated with security patches could put your site at risk.

• It is also Siriusware's policy to only support Windows operating systems that are currently supported by Microsoft. Siriusware Inc. no longer supports Windows XP. This means that future versions of the Siriusware product may not operate on Windows XP. Also, if incompatibility issues are found that are operating system related, Siriusware Inc. may not be able to resolve them.

• To ensure the longest product lifecycle possible, Siriusware Inc. recommends upgrading to a recently released operating system such as Windows 7 or Windows 8.

If you have questions concerning replacement hardware compatibility or wish to inquire about obtaining replacement computer hardware through Siriusware Inc., our Hardware Specialist is happy to assist you.

3

Installation instructions

The success of your update depends on adequate planning and resources. Please review the complete Updating Salesware Modules document for information on the general updating process. You can find specific information about each version and reviews the Update Notice for each release on the Siriusware Information Portal in Downloads > X.XX Salesware.

We also ask that clients review the version specific Updating Instructions document prior to updating to the most recent software release.

Updating instructions:

1. Review appropriate updating instruction documents. 2. You must download the SiriusSQL_4400_0137_03_To_4400_0137_11.sql script to update

your database. 3. Siriusware Inc. does not support replication so please disable it before updating.

Warning: As of version 4.3, if you are replicating your SiriusSQL database, you must exclude the Max4SaleCounts and Pts4SaleCounts tables from being replicated. These tables are temporary count buckets that are maintained on the fly and do not need to be replicated. More importantly, some triggers need to truncate these tables under certain circumstances and replication of these tables prevents this, causing run-time errors in SysManager.

Additional information

Updated: 01/07/2015

Applies To: SiriusSQL_4400_0137_03_To_4400_0137_11.sql and version 4.2.02 or higher

Important: Please only download these updates if you are already running Siriusware Salesware version 4.3.05 or higher. You must download the SiriusSQL_4400_0137_03_To_4400_0137_11.sql script to update your database.

If you are on a database version that is different from those that posted on the Siriusware Information Portal, please contact Siriusware Technical Support.

Warning: If you are currently on version 4.4.01 of Salesware, Do Not download the 4402 CommonUpdate files. Downloading and installing these files causes complications with the update.

4

What’s new in Salesware version 4.4.02

Scope and audience

The following summarizes the newest features in the latest update of Salesware Version 4.4.02. This is intended for Salesware administrators and other personnel charged with reviewing the latest features available in ongoing releases of Salesware from Siriusware Inc.

Components in this release

The components that received the version 4.4.02 designation are listed in the following table.

Note: Siriusware Inc. uses official release version designations. They are listed in the following table.

Component 4.4.02

Accounting Export 4402_0009

BookEZ 4402_0101_02

BatchPrint 4402_044_02

Club Management 4402_0436_04

ClubManagementReportSite 4402_0015_02 CommonUpdate 4402

ConfigManager 4402_0012

E-Commerce Pages 4402_0436_04 Export Service 4402_0012

Folio Charge 4402_0022_02

GateKeeper 4402_0047_02

Helper 4402_0010 Instructor Payroll 4402_0071_02

InventPricer 4402_0021_02 Messenger Service 4402_0027

Photo 4402_0012 Pool Service 4402_0012_02

RentEZ 4402_0149_06

5

Component 4.4.02

RentPrint 4402_0029_04

ResPrint 4402_0044_02

ReportManager 4402_0338_02

RSWebApp 4402_0020_02

Runexe 4402_0039_02

Sales (PrintEZ is included in Sales) 4402_1619_62

SalesEZ 4402_0322_13 Salesware Service 4402_0080_02

ScanMan 5590 4402_0033

ScanMan 9090 4402_0033

ScanMan 9190 4402_0033

ScanWatch 4402_0042_02

SeeBooks 4402_0031_02

SeeBooks Online 4402_0018_02 Self Entry Pages 4402_0076

Service Monitor 4402_0007_02

SiriusSQL 4400_0137_11 SysManager 4402_0528_15

TallyEZ 4402_0041_02 TallyManPPC 5590 4402_0051

TallyManPPC 9090 4402_0051

TallyManPPC 9190 4402_0051

TechStationPC 4402_0039

TechStationPPC 5590 4402_0014

TechStationPPC 9090 4402_0014

TechStationPPC 9190 4402_0014

Ticker 4402_0011 ww.dll 4402_0357_14

wwService 4402_0010

6

Enhancements

Changes to Charge Cards

Added Aloha Stored Value Cards

Siriusware Inc. now provides the capability to use Aloha Stored Value Cards for redemption purposes. Specific enhancements to enable this form of payment include:

• Compatibility with Radiant Systems Aloha Stored Value program • Ability to use the cards at a salespoint via Sales or SimpleCharge applications • Enable a new Payment Type (Aloha Stored Value Cards) • Ability to enter a PIN for a Stored Value Card

Configuration

To install you must first configure your Sales32c.INI file enable Aloha Stored Value Cards:

[aloha] enable = TRUE Url = https://storedvalue.alohaenterprise.com/StoredValue/public/soap/StoredValuePublicWS company = companyname storeid = 1 user = admin pass =password

• Url: Location of the Aloha Stored Value web service • company: The company ID assigned by Aloha • storeid: store id number • user: Aloha Stored Value web service username • pass: Aloha Stored Value web service password (encrypted after initial launch of Sales)

SysManager

A new Aloha Stored Value option has been added to the Activities > Payment Types > Process Via dropdown on the Payment Type edit form.

7

Also a new Require PIN check box has been added. This is only available only when the new Aloha Stored Value option is selected.

8

Restrictions

Based on the interface capabilities with Aloha, Salesware does not process cards in these manners:

• There is no balance inquiry, cash-out, loads, issuing of cards, etc. • This enhancement only adds functionality to process payments. • This enhancement is only supported in Sales (or SimpleCharge application). This is not available in E-

Commerce module. • This enhancement does not include any sort of end-of-day procedures for a batch settlement.

Important:

Aloha Stored Value cards may not be activated or redeemed for cash at a Siriusware salespoint. Offline purchases by Stored Value Cards are not allowed. If the total of the Sale is greater than the value of the stored value card, the operator is asked to obtain another form of payment to cover the difference. Aloha transaction info may be found in the log file AlohaLog.txt located in the Sales data directory.

9

New settings for preauthorization

A new setting has been added for locations which use the full purchase amount of a sale for pre-authorization for AVS / CVV matching. Editing either ProtobaseCvvFail or ProtobaseAvsFail setting in the [server] section of sales32c_system.INI and adding FULL to the card's definition enables this functionality.

[Server] ProtobaseCvvFail= DISC:N,I,,FULL;VISA:N,S,I,FULL;MACH:N,I,FULL;AMEX:N,U,FULL ProtobaseAvsFail= DISC:9,A,N,FULL;VISA:9,A,N,FULL;MACH:9,A,N,FULL;AMEX:9,A,N,FULL

Changes to Kiosk

HTML Kiosk Interface

The new kiosk interface emulates classic kiosk functionality as an HTML web page. Due to being web-based, this kiosk allows for some customization when creating kiosk screens. In addition to classic kiosk features, the new HTML kiosk provides the following capabilities:

General • New Interface with larger buttons, intuitive design and enhanced screen resolution • Automatically updates with item tree changes

Item that can be sold • Any regular items • Max4Sale and Points4Sale items • Items with optional or required modifiers

Selling and configuration • Max4Sale and Points4Sale availability can be displayed • Optional and required modifiers are presented during the sale process • Blank and New Row Item Tree functions are available for configuration • Configure the number of rows and columns of item items that are displayed

Will Call capability • Ability to designate kiosk as purchase only, will call only or both • Recall a saved or finalized reservation by scanning a barcode with the reservation number or via credit

card • Recall an E-Commerce sale with a web sales ID number • Reprint E-Commerce tickets • Auto sell an item based on scanning a barcode or pass

10

Discounts • Pass/Member discounts • Coupon codes • Specials • All discounts can be applied at the Insert Card Finalize Screen

Payment options • In House Cards • Fusebox • CreditCheq / Tender Retail payment through the K800 pin pad terminal

Installation and configuration

Requirements

Hardware • Computer must meet the minimum hardware requirements found in the Salesware System Architecture

and Specification document • Computer must be at minimum, Windows 7 SP1 with Internet Explorer 10 or greater • Touchscreen monitor must have the capability of displaying at 1280 x 1024 resolution or greater • A physical keyboard available for installation purposes

Software • You must have at least one Kiosk License in your license file. • You need an HTML Kiosk Skin Pack from Siriusware Inc.

Installation steps

Create a Kiosk salespoint and operator 1. Create a new salespoint by going to SysManager > System Lists > Salespoints 2. Click on New > select Kiosk > click on Continue

11

3. Enter a Salespoint Nickname and Description. 4. Configure the following tabs:

• Printing: Select the appropriate Receipt layout and select Email Only if you would like to send a receipt by email at the kiosk

• SP Type: As needed for your organization • Credit Cards: Enter the appropriate information for your credit card setup • Item Tree: Select the Kiosk Item Tree to be used and click on Done

5. Create an operator by going to SysManager > System Lists > Operators 6. Click on New and enter an Operator Login (e.g., “KIOSK”) and a full name 7. In Security Roles, select a role that has salespoint access and functions 8. In Security/Login create an initial password 9. Click Save 10. Log out of SysManager and log back in with the user and password created for the Kiosk

Install the Kiosk salespoint 1. Install Common Files application, and then run the Sales Installer

• Custom Setup: You may choose to install Kiosk Training by selecting the red X and selecting This feature will be installed on local hard drive

• Salespoint Mode: Select the Kiosk option • Interface Scaling: Leave as default (Kiosk uses onscreen keyboards automatically as needed) • IP Addresses: Configure IP addresses as needed • Initial Configuration Information: Leave settings as default

12

• Credit Card Processing: Select the appropriate processor

Configure the salespoint 1. Paste the HTML Kiosk Skin Pack provided by Siriusware Inc. into: C:\Program

Files\Siriusware\Sales.

Note: Ensure that the folder that you are copying is NOT kiosk_html as this folder gets overwritten when Sales version updates occur.

2. Start Sales and select Yes to update local tables. 3. Once Sales has started and you have reached the log-in screen, select Cancel to close Sales. 4. Open the Sales32.INI file by going to Start > Siriusware > Settings > Sales32c.ini. 5. Ensure the following settings are in the [Kiosk] Section:

32 Bit Computers

[Kiosk] Mode=file:///C:\Program Files\Siriusware\Sales\kiosk_html_Client_Name\ClassicKiosk.html

64 Bit Computers

[Kiosk] Mode=file:///C:\Program Files(x86)\Siriusware\Sales\kiosk_html_Client_Name\ClassicKiosk.html

Note: The filename bolded above is the folder name of your skin pack.

6. Set up a password to exit the kiosk interface by adding the following [Kiosk] Setting. If you do not have a physical keyboard at the kiosk the setting could be blank.

[Kiosk] Pass=Sirius

7. Set up auto log-in for the Kiosk so Sales logs in and starts up automatically without requiring a username and password. Use the Kiosk user and password as the set up in the Create a Kiosk Salespoint and Operator section.

[AutoLogin] Login=kiosk Pass=kiosk123

13

8. Start up Sales, it should automatically log-in and your specific client skin pack is now displayed. 9. Attach a physical keyboard to the computer and Press F8. 10. On the Tools dialog, click on Sales Pt Setup > printing, and then configure your ticket and receipt printers

as needed.

Note: While the Kiosk is running, you can enter the Tools menu by hitting F8 on a keyboard at any time.

Use

Adding Items to be sold at the Kiosk

Items for sale at the kiosk are added in a similar fashion as is performed for a normal salespoint. Typically a Kiosk Item Tree group is created and items are dragged over from the DCI list.

The following Item Tree functions work in Kiosk:

• New row • Folders • Blank Item to create a space • Day of week, time and date restrictions

Note: Button / Text color and pictures do not display on the user interface at the Kiosk.

Working with Max4Sale and Points4Sale items

Max4Sale and Points4Sale capability are typically used for controlling capacity on timed items. The Kiosk has many functions to enable an easy and intuitive display of what is available and when.

Helpful settings: Timed items can be set up to only display during a specific time frame. For example, if it is 2:00 PM now, only those items that can be sold for 2:00 PM and later are displayed. The [Preferences] setting EnforceTimeOfDayRestrictionOnTodayOnly=TRUE enables this functionality. It is recommended that this setting be placed in the defaults in the Global INI. The time window to show on the screen is set in the Item > Restrictions tab in the Times entry.

To display the number of items that remain and change the, “Available” or “Sold Out” text you must use the following HTMLKioskSettings:

14

HtmlKioskSettingX=showNumberRemaining:true HtmlKioskSettingX=availableText:Open HtmlKioskSettingX=notAvailableText:Sold Out HtmlKioskSettingX=hideNonAvailableItems:true

For more information and detailed descriptions of Kiosk settings please see the Salesware. INI Settings Reference document.

Will Call in Kiosk

Will Call options include:

• Ability to designate a kiosk as a point for purchase only, will call only or both

A kiosk can be set to any combination of modes to suit business needs. For example, you can have one kiosk as a Purchase Only and another kiosk as a Will Call Only kiosk.

The following [Kiosk] settings are used for this purpose: • HtmlKioskSettingX=showPickupButton:true • HtmlKioskSettingX=showpurchasebutton:true

Assuming showPickupButton is set to true, the following options are available:

• Recall a saved or finalized reservation using reservation # Saved and finalized reservations can be recalled from the kiosk using the reservation number created by Sales. If reservations are saved, the Kiosk prompts the user to finalize the sale and if any payment is due, they are required to pay before the reservation is finalized and tickets are printed.

The following [Kiosk] setting enables the Reservation Number button to be shown after you select Will Call from the Welcome screen.

HtmlKioskSettingX=showNumberButton:true

• Recall a saved or finalized reservation using a credit card Saved and Finalized reservations can be recalled from the Kiosk using the credit card associated with the reservation. This is typically used to pick up E-Commerce tickets that either need to be printed or reprinted again.

The following [Kiosk] setting enables the Credit Card button to be displayed after you select Will Call from the Welcome screen.

15

HtmlKioskSettingX=showSwipeCreditCardButton:true

• Reprint E-Commerce tickets at the kiosk after a lookup is performed using reservation number, web sale ID or credit card lookup. After a reservation is recalled using the aforementioned methods, the Kiosk prompts to reprint tickets on the ticket printer. In order for this to work, you must ensure that a Ticket layout is selected on the Printing tab of the item and the same ticket printer is selected on the Salespoint Setup. For example, if selling Print At Home Tickets items online, ensure the item has a layout selected (Items > Printing > Ticket 1) and the ticket printer is selected for Ticket 1 (Kiosk Tools > Sales Pt Setup > Printing).

• Auto sell an item based on scanning a barcode or pass. The barcode can be encrypted or unencrypted. An item can be configured to auto sell when scanned and after scanning, the Kiosk auto sells the item and immediately prints it. The barcode would need to start with %AA for a ticket or %AP for a pass.

Note: Auto sell tickets can ONLY be scanned at the Welcome screen, Purchase screen and the general Will Call screen. Auto sell tickets cannot be scanned after selecting Number lookup, Credit Card Lookup or Reservation Scan Lookup.

Discounts in Kiosk

A variety of discount options are available at the kiosk including:

• Pass/Member discounts can be applied by entering the pass number or scanning the card: At the, final, Insert Card screen, you can add a Pass Discount button to enter or scan a pass number to receive discounts. The kiosk utilizes the specials associated in the Global Settings of the pass item and applies the appropriate special only to those items in the sale that receive a discount. The default value of this setting is false. After selecting this button, the Kiosk adds %EP to any items scanned. The following [Kiosk] Setting enables the Pass Discount button to be shown:

HtmlKioskSettingX=showPassDiscountButton:true

• Coupon codes can be applied by entering the source code or marketing code On the final, Insert Card screen, you can add a Coupon Code button to enter a coupon code. You set up the special, link the special to the item, and then link the appropriate marketing or source code to the special. The default value for this setting is false.The following [Kiosk] setting enables the Coupon Code button to be displayed:

HtmlKioskSettingX=showCouponCodeButton:true

16

There are three coupon code lookup options available at the kiosk:

• Marketing code - set with mktgcode • Source code - set with srcecode • Special name – the default setting, if this is not pre-established, the special’s nickname is used.

HtmlKioskSettingX=couponButton:srcecode

• Specials can be applied by scanning a barcode Specials can also be applied by scanning a barcode that containing a marketing code, source code or special name for a particular discount. Please see the Salesware User and Ticketing Guide for Beginning Users documentation for proper setup. The default value for this setting is false. The following [Kiosk] setting enable the Coupon Scan button to be shown:

HtmlKioskSettingX=showCouponScanButton:true

Payments in Kiosk

The following payment types are accepted at the Kiosk and show the standard, Please Swipe Card screen at the end of the sale process.

• Credit Card – Fusebox • In House Cards / Debitware

Note: Multiple Debitware cards can be used in a single transaction at the kiosk. However, the Debitware card used must not have enough remaining on the card to pay for the entire sale. In this scenario, the kiosk asks for an additional form of payment to cover the remainder of the sale. A maximum of four payments can be used.

• Chip and Pin / EMV –Tender Retail cards are accepted and once enabled automatically show the Debit or Credit screen. Set the below setting to TRUE to activate.

[Preferences] Creditcheq=TRUE

Note: The K800 is the only pinpad that works with the Kiosk.

17

Kiosk settings reference

HTML Kiosk specific settings

Important:

• All of the following HTML Kiosk settings are case sensitive and must be entered exactly as shown • All true or false must be lowercase • HTML Kiosk Settings are numbered, however the setting and setting number do not need to match

For example, HTMLKioskSetting1 could be saleTimeoutWarning or it could be showPickupButton.

• HTML Kiosk settings must be in consecutive numbered order without missing numbers

Example: If you use 10 HTML Kiosk settings, you must have settings 1-10 in order without missing numbers in between 1 and 10. Missing a number in sequence, causes the kiosk to not function properly.

;Time Out Settings HtmlKioskSetting1=saleTimeoutWarning:120000 htmlKioskSetting2=FinalizeTimeOut:120000 HtmlKioskSetting3=thankYouScreenDisplayTime:45000 htmlKioskSetting4=commandTimeOut:10000 HtmlKioskSetting5=pinpadTimeout:10000

;Welcome Screen Settings HtmlKioskSetting6=showPickupButton:true HtmlKioskSetting7=showpurchasebutton:true

;Will Call Settings HtmlKioskSetting8=showScanBarcodeButton:true HtmlKioskSetting9=showSwipeCreditCardButton:true HtmlKioskSetting10=showNumberButton:true

Note: For the following settings, replace X with the next consecutive number.

Timeout settings

HtmlKioskSettingX=saleTimeoutWarning:120000 • Controls the amount of time the Kiosk waits, without user interaction, before it times out and reverts back

to the Welcome screen. This setting affects all screens except the Finalize and Thank You screens. Timeout settings are in milliseconds.

HtmlKioskSettingX=FinalizeTimeOut:120000

18

• Controls the amount of time the Kiosk waits, without user interaction, on the Finalize (Please Swipe Card) screen before it times out and reverts back to the Welcome screen.

HtmlKioskSettingX=thankYouScreenDisplayTime:45000 • Controls the amount of time the Kiosk waits, without user interaction, on the Thank You screen before it

times out and reverts back to the Welcome screen.

HtmlKioskSettingX=commandTimeout:10000 • Amount of time until the HTML page times out communication with Sales. 10000 should work for most

instances, unless the computer is slow or a large item tree has Max4Sale or Points4Sale values calculated.

HtmlKioskSettingX=pinpadTimeout:10000 • Controls the amount of time the Kiosk waits, without user interaction, on the Pinpad screen before it

times out and reverts back to the Welcome screen.

Welcome Screen settings

HtmlKioskSettingX=showPickupButton:true • Enables the Pick Up Tickets button on the Welcome Screen.

HtmlKioskSettingX=showpurchasebutton:true • Enables the Purchase Tickets button on the Welcome Screen.

Will Call settings

HtmlKioskSettingX=showScanBarcodeButton:true • Enables the Scan Barcode button used for scanning a reservation number barcode to recall a reservation.

The barcode expression would be %+resrvatn.reserv_no or %+resrvatn.user_resno.

HtmlKioskSettingX=showSwipeCreditCardButton:true • Enables the Lookup by Credit Card button used to lookup a reservation (including E-Commerce module)

using the credit number.

HtmlKioskSettingX=showNumberButton:true • Enables the lookup of an E-Commerce sale by using the Web Sales ID.

Discount settings

HtmlKioskSettingX=showPassDiscountButton:true

19

• Enables the Pass Discount button at the Finalize screen. This allows the user type in or scan a pass/ membership number to receive the discount linked on their pass.

HtmlKioskSettingX=showCouponCodeButton:true • Enables the Coupon Code button at the Finalize screen. This allows the user type in a coupon code.

HtmlKioskSettingX=showCouponScanButton:true • Enables the Coupon Scan button at the Finalize screen. This allows the user scan a barcode to enable a

special.

HtmlKioskSettingX=couponButton:srcecode • Sets the Coupon Code button to look at the Source Code or Marketing Code list. If not entered, the default

is the Special’s nickname. Possible options are srcecode or mktgcode.

Availability settings

HtmlKioskSettingX=showNumberRemaining:true • For Max4Sale or Points4Sale items, setting to true shows the actual number remaining to the user on the

item button.

HtmlKioskSettingX=availableText:Open • Overrides the default, “Available” text shown under the item button when an item is available.

Note: Does not override when showNumberRemaining is set to true.

HtmlKioskSettingX=notAvailableText:Sold Out • Overrides the default “Not Available” text shown under the item button when an item is no longer

available.

HtmlKioskSettingX=hideNonAvailableItems:true • If set to true, Kiosk hides all non-available items. This is helpful when selling items like movie times

where you only want the user to see available movie times.

General settings

HtmlKioskSettingX=kioskbuttonscols:3 • Number of item columns to show on the Kiosk item selection screen. The Maximum number possible is 3.

HtmlKioskSettingX=kioskbuttonsrows:3

20

• Number of item rows to show on the Kiosk item selection screen. The Maximum number possible is 3.

HtmlKioskSettingX=numItems:3 Limits the number of items shown on the Kiosk screen to create a cleaner appearance. This is typically used with the [Preferences] setting EnforceTimeOfDayRestrictionOnTodayOnly=TRUE as this would enable the Kiosk screen to only show the items available up to a certain number as defined by this setting.

Troubleshooting

HTMLKioskSettings do not seem to be working The HTMLKioskSettings have a very particular order in the Sales32c.INI file. If you notice that a setting is not working as it should, ensure the following:

• HTMLKioskSettings are all under the [Kiosk] section • HTMLKioskSettings all have a number, for example HTMLKioskSetting5= • HTMLKioskSettings are all in numerical order, and there are no skipped or duplicated numbers, for

example:

HTMLKioskSetting1= HTMLKioskSetting2= HTMLKioskSetting3=

• All HTMLKioskSettings are case sensitive • HTMLKioskSettings settings that are true or false must be lower case • The correct format for HTMLKioskSettings is the following, any other format does not work. Note the

placement of = and:

HtmlKioskSetting15=showNumberRemaining:true

Credit card swipe does not work properly This is usually due to the improper mag reader formatting. The correct format is as follows:

• One single line with no carriage return • The data from the swipe must start with a % and end with a ?

To ensure the swipe data is coming through correctly, open Notepad on the computer and swipe a credit card. If the output does not look correct, then a mag configuration utility needs to be downloaded. Look at the vendor and model number of the mag swipe unit and download the configuration utility to make the appropriate changes.

21

Changes to Reporting

E-Commerce Transaction Detail Report

The E-Commerce Transaction Detail Report is used to display the following information about sales made through E-Commerce: wwSale ID, sale number, guest information for guests in the sale (either the purchasing guest name, address, email address, and guest number or the item guest name, address, email address, and guest number are displayed), the item description, quantity, and amount paid, pass type (A = access item, P = pass item), pass number, purchase date, the original salespoint, and whether or not the sale has been finalized. The report can be filtered by entering a date range, by department, category, and item, by purchaser or item guest number, by wwSaleID, by pass number, and by sale finalized/saved status. The report can show purchaser or item guest information, different guest address types, all items, modifiers only or no modifiers.

Changes to Ticketing

Bosch security recorder integration

Introduction

Siriusware Inc. is now able to integrate and send sales data to a Bosch 750 Security DVR system. Sales can now act as a Bosch Text Data Application sending data to a Bosch Recording Device in real-time with actions such as:

• Adding an item to a sale • Applying a special • Changing a quantity • Direct Pricing of an item • Finalizing a sale • Clearing a sale • Voiding a line item

In addition to the record-of-sale type messages, any successful security override events are sent to the camera system as well.

Note: If the connection between Sales and the Bosch Security Recorder is lost, messages are not sent to the camera system during the time the two systems are disconnected. There is no store-and-forward type of mechanism available in this integration.

22

Configuration

In order to enable Sales to communicate data with the Bosch security recording device, you must add the following setting in the Sales32c.INI section:

[BoschCamera] Enable=TRUE

Additional preferences have been added to allow the installer to tell the salespoint which port the recorder is listening on, as well as what port the salespoint itself is listening for the recorder's configuration pings.

[BoschCamera] SalespointPort=4201 RecorderPort=4200

These settings, SalespointPort and RecorderPort, default to 4201 and 4200.

Examples of use

In all associated activities, the location of the salespoint and the operator name appear within the first line of text sent to the recorder. Depending on the type of activity performed at the salespoint, this determines the remainder of information that is sent out.

1. Activity Type - An item is added to the sale: When an item is added to the sale the location, operator, item and date appear on the first line. The second line of text displays quantity, price and tax of the item.

Example: RET01 JWILLI Chips 02/05/2015 Qty: 1 Price: 0.75 Tax: 0.05

2. Activity Type - A special is applied to and item: The first line of test displays location, operator and special name. The second line of text displays the rate of discount whether a flat rate or percentage.

23

Example: RET01 JWILLI EMPRETAIL Flat 0.00 Percent 25.00

3. Activity Type - A quantity is changed: If a quantity is changed, the first line of text displays location, operator and quantity change. The new quantity number, item and date display on the second line of text.

Example: RET01 JWILLI Quantity Change New Qty: 2 on Altoids 02/05/2015

4. Activity Type - Direct Price is set: When a direct price is set on an item, the location, operator and direct price appear on the first line. The second line of text displays set price, item and the date the price was set.

Example: RET01 SUZY Direct Price

Price: 10.99 on Calendar 02/05/2015

5. Activity Type – A sale is finalized: When a sale is finalized, the location, operator, final, sale number, payment type and total appear on the first line. The second line of text displays subtotal, discounts, tax and total.

Example: RET01 JWILLI Final 5015001 CASH 6.29 Sub 5.90 Dsc 0.00 Tax 0.39 Total 6.29

Note: A spacer line // may appear after a finalized transaction in the case of multiple payments. For instance, a gift card is used and the balance of the card is 0.00. This is only a partial payment of the total transaction. A spacer line // appears, and then the next form of payment is listed.

6. Activity Type - A security override is successful: If a security override occurs, the location, operator and the operator name (the operator who selected the override action but did not have security to perform that action) appear on the first line. The second line of text displays the override activity and the operator name who performed the actual override.

Example: RET01 SUZY Security Override by SUZY

24

Special: ‘Comp’ security override by ‘JWILLI’

7. Activity Type: A Sale is cleared. When a sale is cleared, the location, operator and sale cleared appear on the first line. The second line of text displays the cleared subtotal, fee, tax and total.

Example: RET01 SUZY Sale ClearedSubtotal: 4.00 Fee: 0.00 Tax: 0.26 Total:4.26

8. Activity Type: A line item is voided by pressing the line item quantity button, and then pressing Void. The first line of test displays location, operator and item voided. The second line of text displays the quantity of voided items and the department, category and item.

Example: RET01 SUZY Item VoidedVoid item: 1 of ‘Retail Supplies Batteries’

Additional functionality for Block Holds

Block Holds can now be released by date

Previously, Block Hold functionality only allowed the release of a Block Hold X minutes before it expired on the “day of”. However, many clients need to release the Block Holds days in at advance of the specific time of the event. In order to enhance this capability, we added the following functionality to the Block Holds feature:

• Add control for the # of days in advance to release the Block Hold in addition to the time of day to release.

Example: A Block Hold of 20 for Feb 26, 2015 should be released on Feb 20 at 8:00 AM. The Block Hold Expiration for this Feb 26 Date/Time Max4Sale record would be 6 days at 08:00.

25

• Revised the Stored Procedure to look at not only the time of day, but the number of days prior, in order to determine if the Block Hold should be released.

• Sales is sending in both the current date/time and the item valid date so that the stored procedure can compare and release as appropriate.

Configuration

SysManager The Category and Sub-Category Max4Sale limits have been combined into one form. In addition, one can now designate that Sub-Category block holds be released at a certain number of days prior to the limit date at a designated time. To make these additions possible, the following fields are now a part of the Category Max4Sale creation dialog (individual and create daily ranges).

Note: These fields are only present when Sub Categories have been configured for the Category:

• Enable Block Hold check box - checking this activates the fields described below, when unchecked the fields below are deactivated

• Sub Category description field • Block Hold Expires - field with a Days counter field and a time entry field • Max # for Block Hold - numeric entry field • Rem. – Displays number of remaining available items under the block hold • Allow Item Sale after Expire check box

26

Use

Sales & E-Commerce Sub Category block holds can now be released a set number of days prior to the limit date at a designated time in Sales and E-Commerce modules.

Reporting The Max4Sale Subcategory Detail Report has been updated to include the expiration date and time for block holds expiring on prior days.

Editing Block hold categories and subcategories

The Max4Sale button on the Category edit dialog now opens an enlarged Max4Sale grid displaying the following columns:

• Start Time & End Time - the beginning and ending date/time for the configured Max4Sale limit • # Days - the number of days that the Max4Sale limit exists • Max - the Max4Sale limit • Sub Category - if applicable, the Sub Category description

27

• Block Hold Expires - if applicable, the number of days prior to and the time when the block hold expires• Allow Item Sale after Expire - if applicable, indicates whether or not a Sub Category item can be sold after

the block hold expires

Logic has been adjusted so that when editing an existing Max4Sale limit the Enable Block Hold check box for a Sub-Category remains unchecked if it was saved that way originally.

Cascading access records through multiple layers of modifiers

Previously, a sales line item modifier could only access one level of modifier to take on the access record of its parent. For example, many clients have multiple timed events. For ease of selling, the main item is Adult, Child and Senior. The first layer of modifiers are the various venues/activities/exhibits/movies, then these have their own modifiers for selecting the time. The second layer of modifiers contain the revenue and Max4Sale. In the past this could only be achieved through multiple barcodes on a ticket or by printing multiple tickets.

Now, by default, a Sales line item modifier takes on the access record of the top-most access record in its chain. To disable this functionality and revert to the previous behavior, set SetMasterpassToParentPass=TRUE in the Sales32c.INI, [Preferences] section.

28

Sort sale history by date/time

Guest history on the Guest History dialog is now sorted descending by Date/ Time. Previously, the sale history for a guest (Sales > Guest Lookup > History) was sorted by Sale Number.

Additional functionality for Member Benefits

You can now save a reservations and recall at another point in time and modify the benefit item. The quantity of items on a saved sale / reservation that have redeemed benefits may now be changed on sale recall as well.

Automatic drawer pop on Closeout

Salespoints configured with two cash drawers each assigned to different operators now pop the operator's drawer who just closed out.

Automated Revenue Recognition on expired and un-used tickets/passes

At times visitors purchase tickets and do not actually visit the site by the expiration of the item or they do not attend at all. Previously un-used and expired tickets did not move to recognized revenue and therefore could not be properly accounted, despite actual revenue being actualized. In order to automate the process of recognizing revenue in these circumstances and enhancement was created to push this revenue and actualize these amounts.

29

Configuration

SysManager

The following changes have been made to SysManager in support of the Automated Revenue Recognition on Expired and Unused Tickets/Passes enhancement:

1. Profit Center edit dialog: added Deferred Revenue check box. Used for reporting purposes on Revenue Recognition Report on expired access and pass records.

2. Dynamic Pricing Rules Edit dialog: added option Rules to process on an expired access/pass records text field to use when processing Revenue Recognition on expired access and guest pass records.

Note: This option applies only on Revenue Recognition Rule types.

30

Note: In order to use the new automated revenue recognition on expired tickets, the Revenue Rule also needs to be populated for validation scans, even if the client does not intend to use that section of the Dynamic Pricing Rule Edit form.

3. Data Maintenance: added new option to Reprocess Failed Revenue Recognition On Expired Access or Guest Passes. This option is used to mark access or guest passes for reprocessing by Export Service application that failed Revenue Recognition. This is used once a problem is corrected or to “retire” expired or unused records so they are not reprocessed and no longer appear on the list.

31

Export Service

The Export Service application has been enhanced to allow it to recognize revenue for access tickets/guest passes that have expired. The following must be performed in order for this enhancement to work properly:

1. The ww.dll must be installed on the same computer as Export Service application 2. The following section and settings must be added to the ExportService.INI file

[ExpiredRevenueMove]MinDays=0MaxDays=60Operator=EXPORTSalespoint=EXP01UseExpirationDateForTransaction=TRUENumRecordsToProcessAtATime=100DefaultMoveExpiredRevenueRule=MOVEREVENUE(DEFERRED,RECOGNIZED,100,0,,,)

32

• MinDays/MaxDays - the range, in days, to search for expired tickets. The default value for MinDays is 0 and MaxDays is 30. These can take floating point values, i.e., the user can set this to a floating point value such as 0.1 which equates to 2.4 hours.

• Operator - the operator to use to populate the tables when recognizing revenue on expired tickets/passes. The value set here is only used if the MOVEREVENUE Rule for expired records does not already contain an operator. A valid operator needs to be defined in either the MOVEREVENUE Rule or in the ExportService.INI file or the revenue moving transaction fails.

• Salespoint - the salespoint that is used to populate the tables when recognizing revenue on expired tickets/passes. The value set here is only used if the MOVEREVENUE Rule for expired records does not already contain a salespoint. A valid salespoint needs to be defined in either the MOVEREVENUE Rule or in the ExportService.INI file or the revenue moving transaction fails. If no salespoint is defined in either place, the computer name, truncated to six characters, is used instead which causes the transaction to fail because the computer name is not a valid salespoint.

• UseExpirationDateForTranstion - uses the expiration date of the ticket or pass as the date for recognizing the expired revenue if it is set to TRUE. If set to FALSE, then the current date/time is used. This setting defaults to FALSE.

• NumRecordsToProcessAtATime - used to limit the number of records that are processed at a time. Initially, Export Service application checks the server for records to process at approximately ten second intervals and attempts to process the number of records designated with this setting. If records are found to process, Export Service processes the records and continue checking and processing records at approximately one second intervals until all records are processed. After processing is complete, Export Service returns to checking the server at approximately ten second intervals. This setting defaults to 1000. This setting can also be used to disable this feature by setting the value to 0.

• DefaultMoveExpiredRevenueRule - the Revenue Moving Rule to use on expired tickets/passes if the ticket/pass item does not have a rule defined for recognizing revenue on expired records.

Additional tasks performed by Export Service application • Export Service writes a 1322 entry into the sp_log table when it fails during any part of the revenue

recognition transaction on an expired ticket/pass. • Export Service also writes a 124 activity type into the gst_actv or acc_actv table when it fails trying

to process revenue on an expired ticket/pass. • Export Service write a 125 activity type into the gst_actv or acc_actv table if it successfully

processes an expired ticket/pass but the ticket/pass does not have any remaining revenue to be moved.

ww.dll

The ww.dll has been enhanced to support Automated Revenue Recognition on expired and unused tickets/passes as follows:

1. Two new parameters have been added to the recognizerevenue function,

33

• macrotouse - allows the caller to define the macro to use to recognize revenue. If this is not entered, it use the rules column in the dp_rules table (original behavior).

• info_type - allows the user to specify the info_type number when it inserts a new entry into the tr_info table. If this is not specified, then a 31 is used (original behavior).

Example: <func>recognizerevenue</func> <table>access</table> <passno>2926007000</passno> <macrotouse>MOVEREVENUE(*DEFERRED*, EXPIRERECOGNIZE, 100, 0, TICKETS,MOVEREVENU,EXPADJTIX, EXPRT1, MIKEG)</macrotouse> <info_type>32</info_type> <operator>EXPORT</operator> <salespoint>EXPRT1</salespoint>

2. The recognizerevenue function now fails if any of the parameters are not valid, i.e., move from profit center, move to profit center, salespoint name, operator name, and DCI.

Reporting

Three new reports have been created for Revenue Recognition activity, Revenue Recognition Summary, Revenue Recognition Detail, and Revenue Recognition Profit Center Split.

Revenue Recognition Summary Report This report summarizes information related to Revenue Recognition products, including revenue earned and deferred in the original sale, revenue recognized via scanning, expiration and returned revenue activity and the total uses and calculated deferred revenue remaining. Report can be filtered by Date Sold, Processed or Expired, by the selling and/or processing salespoint, by the Pass DCI and by Pass #.

Revenue Recognition Detail Report This report offers detail down to the Profit Center split for all transactions related to Revenue Recognition items, whether the original sale, revenue moved via scanning, revenue moved via expiration or any possible return or exchange. Filterable by date pass was sold, date the revenue activity took place, by ticket/pass DCI, by selling salespoint/group, by revenue activity salespoint/group and/or by pass# directly.

Revenue Recognition Profit Center Split Report This summarizes Profit Center splits by DCI or by Ticket/Pass # for Revenue Recognition items, whether from the original sale, revenue moved via scanning, revenue moved via expiration or any possible return or exchange. Filterable by date ticket/pass was sold, date the revenue activity took place, by ticket/pass DCI, by selling

34

Receipts can now be emailed from Sales

This enhancement enables the ability to email receipts in Sales. Additionally, you can now print historical receipts (not just for the day, but for any historical transaction).

Important: Currently, we are only able to add support of emailed receipts for Text Receipt layouts. Email support of Graphic layouts is not currently available.

Configuration

SysManager

In order to enable email receipts from Sales you must enable the following in SysManager:

1. Go to Preferences > Miscellaneous > Miscellaneous Preferences > Salespoint Layouts tab. 2. Click on the new E-Mail tab for editing default values for receipt emails.

35

Note: In order to display a proper “From” address, please enter a title prior to the actual return email address. In the example above this is, Siriusware Resort. When the email is generated and sent to guests it displays only the address of your SMTP server.

36

Example layout In order to make the receipt contents use a fixed width font, you must sandwich the layout between <pre></pre> tags. In addition to fixed widths, you can also adjust the look and style of the Email layout using HTML. The following layout incorporates a Text Receipt layout with HTML to enhance the look of the email.

<p style="color:DarkBlue; font-family:Calibri">Dear Valued Customer,<br/><br/>Per your request, we have provided a detailed receipt for purchases made on <|DSTR2(sale_hdr->Date_time)|>.<br/><br/>If you have any questions or concerns, please call us at (###) ###-#### or email our <a href="mailto:customerservice@yourbusiness.com">customer service department</a>.<br/><br/>Visit our <a href="http://www.yourbusiness.com">website</a> to learn about current programs and events, and to plan your next trip. <br/><br/>We appreciate your business and look forward to seeing you again in the near future!<br/><br/>The staff at Your Company.<br/><br/></p><pre><|CENTER('COMPANY NAME',40)|><|CENTER('COMPANY ADDRESS',40)|><|CENTER('COMPANY CITY STATE POST OR ZIP CODE',40)|><|CENTER('COMPANY PHONE NUMBER',40)|><|CENTER('COMPANY WEB ADDRESS',40)|><|NEWLINE()|>

37

<|CENTER('SALES RECEIPT',40)|> <|CENTER('Sold at: '+alltrim(sale_hdr->salespoint)+' by: '+alltrim(sale_hdr->operator),40)|> <|CENTER('Sale Number: '+IIF(sale_hdr->sale_no=sale_hdr->mastersale,ALLTRIM(STR(sale_hdr->mastersale,16,0)),ALLTRIM(STR(sale_hdr->sale_no))),40)|> <|CENTER(DSTR2(sale_hdr->Date_time),40)|> <|NEWLINE()|> <|'Qty Item Price '|> <|' Special Discount'|> <|'----------------------------------------'|> <|Details(IIF(Item="**TRANS**",' Account Transaction '+STR(extension,8,2),IIF(MODIFIER(),' '+Items->descrip+' '+STR(extension-tax_amount-tax_amt2+disc_amt,8,2),STR(quantity,3,0)+' '+Items->descrip+' '+STR(extension-tax_amount-tax_amt2+disc_amt,8,2))+NEWLINE())+IIF(disc_amt=0,ALLTRIM(' '),' '+specials->descrip+' '+STR(-1*disc_amt,8,2)+NEWLINE())+IIF(guest_no=0,ALLTRIM(' '),IIF(MODIFIER(),alltrim(' '),' '+alltrim(guests->first_name)+' '+alltrim(guests->last_name)))+NEWLINE())|> <|JUSTRIGHT('---------------------------',40)|> <|JUSTRIGHT(' Sub Total:'+STR(Utility->sale_sub+Utility->Sale_disc+Utility->SAle_tax,10,2),40)|> <|JUSTRIGHT(' Discounts:'+STR(Utility->sale_disc,10,2),40)|> <|JUSTRIGHT(' Tax:'+STR(Utility->sale_tax,10,2),40)|> <|JUSTRIGHT(' Total:'+STR(Utility->sale_ext,10,2),40)|> <|JUSTRIGHT('---------------------------',40)|> <|JUSTRIGHT(' PAYMENTS:'+STR(Utility->amt_paid,10,2),40)|> <|JUSTRIGHT(' BALANCE DUE:'+STR(Utility->bal_due,10,2),40)|> <|JUSTRIGHT('---------------------------',40)|> <|JUSTRIGHT(iif(Utility->sale_ext>0.00,'Payment Types and Amounts:',''),40)|> <|JUSTRIGHT(iif(Utility->sale_ext>0.00,FOP(),''),40)|> <|JUSTRIGHT(iif(sale_hdr->pmt_amt1>0.0000,alltrim(str(sale_hdr->pmt_amt1,8,2))+' ','')+iif(sale_hdr->pmt_amt2>0.0000,alltrim(str(sale_hdr->pmt_amt2,8,2))+' ','')+iif(sale_hdr->pmt_amt3>0.0000,alltrim(str(sale_hdr->pmt_amt3,8,2))+' ','')+iif(sale_hdr->pmt_amt4>0.0000,alltrim(str(sale_hdr->pmt_amt4,8,2)),''),40)|> <|JUSTRIGHT('CHANGE DUE: '+iif(Utility->change>0.0000,'-','')+alltrim(STR(Utility->change,8,2)),40)|> <|NEWLINE()|> <|iterate_over(cc_trans, sale_no, sale_hdr->sale_no, IIF(cc_trans->status=3,ALLTRIM(' '),'Card Number: XXXXXXXXXXXX' + cc_trans->card_id + NEWLINE() + 'Card Type: ' + cc_trans->card_type + NEWLINE() + 'Amount: $' + ALLTRIM(STR(cc_trans->total,16,2)) + NEWLINE() + 'Approval: ' + ALLTRIM(cc_trans->approval) + NEWLINE()), NEWLINE())|> <|NEWLINE()|> </pre> <p style="color:#000099; font-family:Calibri"> Thank You ~ Gracias ~ Merci </p>

38

3. In Activities > System Lists > Salespoints > Salespoint Configuration > Printing tab, the option to sending receipts via printer only, email only or both has been added.

39

Sales

If you have selected the option to print or email you may want to prompt your operator to ask customers their preference of a printed or emailed receipt after every transaction. In order to enable this prompt you must go to Sales > Tools > Sales Pt Setup > Miscellaneous > Miscellaneous Setup dialog. On the dialog, you can check the Print Receipt button to enable the operator to be prompted to select a printed or emailed receipt after every finalized transaction.

40

Use

In Sales you can choose to email receipts in several ways:

• When you finalize a sale • When you Reprint a receipt • When you recall a sale

41

Finalizing the sale If you have enabled the Print Receipt check box within the Miscellaneous Setup in SalesPt Setup, upon finalizing the sale you are prompted with a Receipt Delivery Option dialog box.

1. Selecting the Print button prints a receipt or selected the Email button displays the email Address entry dialog.

2. The operator enters the guest email address and the receipt is sent out via Messenger Service application.

Note: If a guest has been associated on an initial sale and their email is listed within the guest record, the Address dialog auto populates with that email address.

42

Reprint a receipt

If you do not wish to be prompted by the Receipt Delivery Option dialog after every transaction, ensure that the Print Receipt check box within the Miscellaneous Setup in SalesPt Setup is not checked. In order to email a receipt, you finalize the transaction and see the receipt on screen. At this point, you select the Reprint button. The Receipt Deliver Option dialog box appears.

To recall a sale and reprint a receipt 1. Select the Recall button and search by either Guest or Sale information.

2. Highlight the appropriate sale on the Sale Research dialog and click the Receipt button.

3. You receive the Receipt Delivery Option dialog.

Note: Emailing of receipts now only applies to receipts, not remote receipts, invoices or anything else that happens to be printed.

Payment plan refund warning

When refunding a Payment Plan on an item which has available Debitware, the operator is warned that the item has available funds which should be cashed out. The operator may then cancel out of the refund or continue.

Changes to ww.dll

Enhancements to the MOVEREVENUE function

The ability to omit the DCI section has been added to the MOVEREVENUE Rule. If omitted, the DCI of the pass item validated is used. This change to the MOVEREVENUE Rule allows for fewer arguments (if DCI is omitted) and

43

enables a more generic rule for similar tickets. For example, all adult, child and senior admission tickets could use a simplified rule such as MOVEREVENUE(Deferred, Admissions, 100,0) while still allowing lots of details regarding why revenue moved from one Profit Center to another on the Profit Center Split Report.

Note: If you want to omit the DCI, you need to omit the entire DCI, not just one portion (i.e., omit the category but not the department).

Examples: • Dept=TRANSPORT, CAT=PUNCHCARDS, Item=10USE • Scanner Salespoint = SCAN01 • Scanner Operator=DOUG • Amount distributed to Deferred when the Punch Card was purchased = $250

Current Functionality

MOVEREVENUE(Deferred, Passenger Cards, 10, 0, TRANSPORT, REVENUE, PUNCHUSE, DOCK, PURSER)

This results in a transact record that removes $25 from Deferred, adds $25 to Passenger Cards, uses TRANSPORT REVENUE PUNCHUSE as the DCI, writes DOCK for the salespoint, and writes PURSER for the operator.

New Functionality

MOVEREVENUE(Deferred, Passenger Cards, 10, 0)

This results in a transact record that removes $25 from Deferred, adds $25 to Passenger Cards, uses TRANSPORT PUNCHCARDS 10USE as the DCI, writes SCAN01 for the salespoint, and writes DOUG for the operator.

MOVEREVENUE(Deferred, Passenger Cards, 10, 0,,,,DOCK,PURSER)

This would results in a transact record that removes $25 from Deferred, adds $25 to Passenger Cards, uses TRANSPORT PUNCHCARDS 10USE as the DCI, writes DOCK for the salespoint, and writes PURSER for the operator.

44

Troubleshooting

If any error or incorrect information is in the rule, gst_actv for pass item and acc_actv for access item generates a reason of failure.

Global Specials applied to linked items in E-Commerce

The ww.dll now correctly handles Global Specials that have the check box Only apply global special to linked items checked on the Restrictions tab of the Special edit form. This means that specials configured in this manner now work in E-Commerce module the same way they work in Sales.

Salesware platform changes

RFID scanning improvements

Configuration

Sales can now read RFID UHF cards with the ThingMagic reader. Sales now installs the two required dll's. MercuryAPI.dll and ThingMagicReaderWrapper.dll, in C:\Program Files\Siriusware\Sales on 32 bit or C:\Program Files (x86)\Siriusware\Sales on 64 bit computers. The following Sales32c.INI settings are required for proper setup:

[Preferences] AxessInquiry=TRUE [SerialReader] ComPort=4 Type=3

Note: The Com port may be other than 4. When the reader is plugged in it determines which com port is being used and that value should be entered for the Com Port setting. If the ThingMagic Reader Assistant is running when Sales starts, an, “unable to initialize comport.” message occurs. Shut down the utility and restart Sales.

Use

To use the reader, go into Ticket Inquiry and with the card at the reader, choose Read RF Card. The encrypted pass number appears on the entry dialog. Select OK and the Pass Information dialog for the pass is brought up.

45

.INI change

If Table Service is selected in the Global .INI, > Group dropdown on the Initial Configuration dialog, the value TableService is now written to the Group setting in Sales32c.INI.

Adjusted parameters

Adjusted the way parameters are passed from VFP into SQL Server by using explicit cast.

Changes to automatic update checks

Version update scripts now have an additional pre-flight check to ensure there are no open connections to the database from running applications such as SysManager, Pool Service, ww.dll, SSMS, Open Query, Windows, etc. If there are any other open connections, the update script halts and the user is notified to inspect the Results pane for a list of those open connections which must be closed before upgrading.

Updates to the default Siteconfig.config

The key "BenefitHeaderLinkText" has been added to the default SiteConfig.config file.

Known issues

For a complete listing of Known Issues, please visit our KI page. Issues are sorted by general software version number.

46

Fixes

US# Release Notes Application Version

10793 BookEZ no longer displays errors when attempting to refund a Private Booking item that requires additional bookings per line item quantity.

BookEZ 4402_0101_02

11160 CommonUpdate 4.4.02 no longer throws errors at startup. CommonUpdate 4402

8978 A bug was fixed that reorders validation items at checkout.

Additionally, you can no longer overspend member benefits when validated outside of the cart order.

E-Commerce 4402_0436_04

9961 The Member Benefits control on the GuestSelected.aspx page now shows or hides the list of benefits used when the Member Benefits history (click to view) link is selected.

E-Commerce 4402_0436_04

10127 The E-Commerce pages no longer crash with the error message, “Column 'AutoAdd' does not belong to table Mods” when finalizing a sale containing a WTP Reload item with a modifier.

E-Commerce 4402_0436_04

10271 The sale of a Create New Guest Record item configured with no age restrictions (i.e., Min Age and Max Age set to 0.000) is once again allowed in the pages for a guest with no birth date in their guest record.

E-Commerce 4402_0436_04

9937 Export Service application now terminates lines with carriage return/line feed when creating CSV and TXT files.

Export Service 4402_0012

10895 Messenger Service application now uses SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED to provide a successful connection to the database.

Messenger Service

4402_0027

10945 Added ORDER BY expression to the select statement in the TimeCard Report.

PayManager 4402_0071_02

10838 Added ability to set default shop for the Last N Forms to All Shops based on the saved value in the Stations table

RentEZ 4402_0149_06

47

US# Release Notes Application Version

10839 You can once again disable the timer for checking and truncating the RentPrint_log file. Use of this setting, when set to FALSE, prevents automated truncation of the RentPrint_log file, so periodic manual “cleaning” is required if set to FALSE.

The setting can be found in RentPrint_System.INI:

[Preferences] AutomaticLogTruncationEnabled=TRUE

TRUE is the default. Set it to FALSE to prevent the check from happening.

RentPrint 4402_0029_04

10737 Printing the Cardware Transactions By Operator/Salespoint Report from preview mode now masks the card numbers, even if the operator has security rights to view unmasked numbers.

ReportManager 4402_0338_02

1883 Scanning a voucher in the HTML & Classic Kiosk interface properly auto sells a ticket and places the charge on account.

Sales 4402_1619_62

1954 Web Sales Host no longer returns an error when processing sales containing a combination of Reserved Seating tickets, some of which, require validation and others that do not.

Sales 4402_1619_62

2569 A new setting, BypassTransactionOnItemtreeSave, was added to the [Preferences] section of SysManager.INI. The default setting, if not present, is No. If set to Yes, SysManager does not wrap item tree saving in an explicit SQL transaction. This option is normally not needed but it may prevent potential deadlocks under certain high volume scenarios.

Sales 4402_1619_62

2613 It is now apparent when an operator is using Correct Closeout. The Sales invoice turns orange when in Correct Closeout mode. After a sale is finalized in Correct Closeout the operator is prompted to Stay in Closeout Correction or

Sales 4402_1619_62

48

US# Release Notes Application Version

Exit Closeout Correction. Selecting, Stay in Closeout Correction enables the operator to remain in Closeout Correction mode and can add more items to the closeout. Selecting, Exit Closeout Correction forces the Closeout Correction to end and the invoice area returns to default white indicating the operator is no longer in Correct Closeout mode.

3056 An item with the SINGLEGUEST macro that has a minimum quantity greater than one, no longer shows an error message that the guest's first name is missing when saving guest info.

Sales 4402_1619_62

8954 Adjusted checks for available docents in the GetResourceEventSortedSchedule method. Back to back docents display on available docents list when pre/post events = 0 or > 0.

Sales 4402_1619_62

8883 An error, regarding missing required fields, no longer displays on sale finalization when a Debitware item with Bonus Cash has been removed from a sale.

Sales 4402_1619_62

9156 Member benefits added as modifiers are now correctly redeemed.

Sales 4402_1619_62

9626 Phone number is correctly selected in the Reservation Header if the selected guest has an associated phone number.

Sales 4402_1619_62

9762 Sales no longer crashes when refunding two pass items for two different guests, and then selling two new pass items to the same guests in the same sale.

Sales 4402_1619_62

9897 A Tip added at finalize is now correctly recorded when a line item tip has already been added to the sale.

Sales 4402_1619_62

9945 When using PCEFTPOS The pinpad no longer asks the user to select their account twice when performing a transaction.

Sales 4402_1619_62

10047 If a user tries to use the Reservation Header along with Payment Plan, it now displays an “Unable to pay for payment plan with Reservation Header present.” message.

Note: Payment Plan is not designed to be used with the Reservation Header.

Sales 4402_1619_62

49

US# Release Notes Application Version

10442 Taxes are correctly calculated when refunding multiple passes on a single line item.

Sales 4402_1619_62

10502 A pass refunded through the Ticket Inquiry is now refunded at the purchase price, rather than the default price of the item's start date.

Sales 4402_1619_62

10577 Age restrictions which use a fraction of a year are now correctly enforced.

Sales 4402_1619_62

10628 In-House Cards payments are correctly handled in the data when paying for a sale with an In-House Cards card and a credit card, where the credit card payment is declined and the remaining sale balance is paid for with cash or another credit card.

Sales 4402_1619_62

10669 Sales no longer allows overselling of a Max4Sale item when using the >> button to increase line item quantity.

Sales 4402_1619_62

10670 SysManager no longer crashes when creating Max4Sale limits.

Sales 4402_1619_62

10678 Sales operators no longer are prompted to add a revenue moving item (from a ticket scan) as a modifier to the refund of a ticket that has a Revenue Recognition Rule assigned to it.

Sales 4402_1619_62

10683 Extra modifier items are no longer displayed in the HTML kiosk. Also, an issue was fixed in which the prompt modifier option was not working. The modifier selection page was changed to display a Select button if there is only one modifier required. Values for min and max modifier quantities are now respected.

Sales 4402_1619_62

10684 Fixed an issue with recalling sales in the HTML kiosk in which credit cards acquired too many records. A new .INI setting was added to limit the number of days to search for credit card records. The setting is:

[Kiosk] NumDaysToSearchForCreditCard=365

This setting defaults to 365 days.

Sales 4402_1619_62

50

US# Release Notes Application Version

The SQLPassThrough searches by card_id and the date set by the NumDaysToSearchForCreditCard= .INI setting. In the code, it also searches for a match on the reservation Arrival date. However, if there is only one record with the card_id the Arrival date check is not performed.

10723 Modifiers are not doubled if refunding a reservation which contains an item with modifiers.

Sales 4402_1619_62

10758 It is now possible to control time restriction for just today. The new .INI setting, if set to TRUE, Sales observes the Available for Sale time restrictions for today only. For days in the future the time values are ignored.

The new setting is as follows:

[Preferences] EnforceTimeOfDayRestrictionOnTodayOnly=FALSE

This setting defaults to TRUE.

Sales 4402_1619_62

10788 Sales no longer crashes when adding a guest to an item in a sale where that same guest had been linked to a voided item in the same sale.

Sales 4402_1619_62

10825 Incorrect tr_save.pts4qty values are no longer written to the data when re-saving or finalizing a saved sale which has a Points4Sale item with one or more modifiers and replacing one or more modifiers in the sale.

Sales 4402_1619_62

10826 The HTML Kiosk now observes the presence of "blank" items and checked New Row check boxes in the Item Tree.

Sales 4402_1619_62

10847 Pressing the Enter key no longer closes the secondary display and after the secondary display starts, the focus returns to the main sales screen.

Sales 4402_1619_62

10856 Current graphics for the HTML kiosk work correctly at resolution of 1280 x 1024.

Sales 4402_1619_62

10870 The Inactivity dialog is now working for the pickup ticket window in the HTML kiosk.

Sales 4402_1619_62

10871 Increasing the quantity of a Debitware item on a saved sale no longer causes Sales to crash.

Sales 4402_1619_62

51

US# Release Notes Application Version

10896 Resources from a recalled reservation retain their correct, initial start and end times.

Sales 4402_1619_62

10904 Fixed bugs in printing signatures. Sales 4402_1619_62

10943 Fixed an issue with Sales not being able to modify tip amount after reversing the payment for a faux finalized sale.

Sales 4402_1619_62

10946 Max4Sale and Points4Sale items now display if the operator has the security setting to see oversold items upon log-in.

Sales 4402_1619_62

10947 It is now possible to change the time of a resource item after a docent has been assigned. The docent has to first be removed, and then reassigned after the time is changed.

Sales 4402_1619_62

10952 Debitware functionality may now be included on a Payment Plan item. The load amount of Debitware is due immediately and cannot be put on a Payment Plan. Functionality has been added to allow items and modifiers with a zero dollar price to be included in Payment Plan transactions as well.

Sales 4402_1619_62

10953 Changed wording when a docent/ instructor is not available for requested time. Now it uses the text Not Available. The message appears as, “This Docent is not available during this Tour.”

Sales 4402_1619_62

11141 Sales no longer finalizes a sale when ForceCCOfflineOnTimeout=TRUE and the operator cancels out of the Manual Override dialog box when the credit card authorization fails.

Also a new setting was added which creates a verbosity 6 Sales log entry in the Sales32c_debug_crash_log.txt file when there is a credit card decline.

[Preferences] CaptureCCVerbosityLogWhenCCFail=TRUE

Sales 4402_1619_62

11181 A memory leak was fixed that occurred during the use of the fingerprint reader.

Sales 4402_1619_62

52

US# Release Notes Application Version

11186 The guest_no field is now populated in sh_print table if the sale has an associated guest.

Sales 4402_1619_62

11206 Web Sales Host once again correctly reprocesses, prints and sends out the confirmation emails for printing errors when selling pdf-based Print At Home Tickets items.

Sales 4402_1619_62

10016 A validation check was added for Block Hold Expire Release time when a Block Hold is activated.

SysManager 4402_0528_15

10023 Ensured that blank item cannot be moved between available items and associated items in SubCategory Edit form. Behavior was adjusted when moving items between available items and associated items in SubCategory Edit form.

SysManager 4402_0528_15

11406 Data Maintenance > Copy To Training has been revised to prevent potential copy errors on the pass template table.

SysManager 4402_0528_15

10722 The Enter key now functions as expected. Expected behavior is entering inventory in Scan Item and selecting the Enter key and the inventory is processed. In addition, scanning inventory with a barcode reader programed with a carriage return suffix, processes the inventory item again.

TechStationPC 4402_0039

11132 A comment or remark in a Recognize Revenue Rule no longer causes a rule to return an error and not work.

ww.dll 4402_0357_14

11167 The ww.dll now correctly handles multiple profit center splits when recognizing revenue.

ww.dll 4402_0357_14

Copyright

Copyright 2015 Siriusware®, Incorporated. All rights reserved.

NOTICE: All information contained herein is the property of Siriusware, Incorporated. No part of this publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means,

53

electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Siriusware, Incorporated. The software, which includes information contained in any databases, described in this document is furnished under a license agreement and may be used or copied only in accordance with the terms of that agreement.

This publication and the information herein is furnished AS IS, is subject to change without notice and should not be construed as a commitment by Siriusware, Incorporated. Siriusware, Incorporated assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with respect to this publication and expressly disclaims any and all warranties of merchantability, fitness for particular purposes and non-infringement of third party rights.

54