2017 03 Software Update 03 For 4.6

Salesware Update: Version 4.6.
03 Release Notes (03/01/2017)
Details .....................................................................................................................................................................6
System recommendations ......................................................................................................................................6
Update instructions ................................................................................................................................................6
One-time setup .......................................................................................................................................................6
64 bit servers ..................................................................................................................................................................... 7
32 bit servers ..................................................................................................................................................................... 9
Steps to Update ................................................................................................................................................... 12
64 bit servers ................................................................................................................................................................... 13
32 bit servers ................................................................................................................................................................... 14
Updating services ................................................................................................................................................ 17
Updating the ww.dll ............................................................................................................................................ 17
eCommerce.......................................................................................................................................................... 18
Steps to update eCommerce pages ................................................................................................................................. 18
Step 1: Preparing for the Update ..................................................................................................................................... 18
Step 2: BIN update ................................................................................................................................................................................................ 19
Step 3: New files to be added ........................................................................................................................................................................... 19
Step 4: Remove ...................................................................................................................................................................................................... 20
Step 5: Replace Files ............................................................................................................................................................................................. 20
Step 6: Changes to Files....................................................................................................................................................................................... 21
Step 8: Restart the Site ........................................................................................................................................................................................ 24
Additional information ........................................................................................................................................ 25
What’s new in accesso Siriusware version 4.6.03 ................................................................................................ 25
Scope and audience......................................................................................................................................................... 25
Components in this release ............................................................................................................................................. 25
Enhancements ..................................................................................................................................................... 27
Changes to Access Control ................................................................................................................................... 27
Additional blocking reason added to Axess for voided passes ........................................................................................ 27
New GateKeeper .INI settings and functionality.............................................................................................................. 27
Fingerprint sensor now enabled....................................................................................................................................................................... 27
Setting prevents rescans from activating turnstile..................................................................................................................................... 28
Added functionality for operator data ........................................................................................................................................................... 28
New Axess printer functionalities.................................................................................................................................... 28
New port option on Axess Smart Printers ..................................................................................................................................................... 28
BatchPrint utility updated to support AxCoding ......................................................................................................................................... 28
Two new fields, AxessPOS and AxessProject have been added ....................................................................................... 29
Configuration .......................................................................................................................................................................................................... 29
New SETPARENTACCVAL and CHANGEACCVAL macros for access table.......................................................................... 30
Changes to Dynamic Pricing ................................................................................................................................. 31
New SOLDDATE() macro and Dynamic Pricing capabilities .............................................................................................. 31
New Dynamic Pricing Rules ................................................................................................................................................................................ 31
SOLDDATE() macro................................................................................................................................................................................................ 32
Changes to eCommerce ....................................................................................................................................... 32
New eCommerce Calendar module available .................................................................................................................. 32
Calendar module settings ................................................................................................................................................................................... 33
New setting to show unavailable modifiers .................................................................................................................... 35
Sales ........................................................................................................................................................................................................................... 35
SiriusSQL ................................................................................................................................................................................................................... 35
SysManager ............................................................................................................................................................................................................. 35
ww.dll ........................................................................................................................................................................................................................ 36
New notifications for Web Sales Host utility errors......................................................................................................... 36
Updated Instructions folder removed from eCommerce ................................................................................................. 37
Changes to Food Service ...................................................................................................................................... 37
Room charges now reversible in Table Service F&B module ........................................................................................... 37
Changes to TallyMan ........................................................................................................................................... 39
Ability to remove scanned barcode prefix ....................................................................................................................... 39
Changes to Memberships and Passes .................................................................................................................. 40
Improved auto-renewal formatting................................................................................................................................. 40
New BLACKOUT macro and pass blackout functionalities ............................................................................................... 40
New BLACKOUT macro added for individual blackout dates on passes .............................................................................................. 40
Added option to prevent blackout date pass printing .............................................................................................................................. 41
New .INI setting to prevent printing a pass with blackout ...................................................................................................................... 41
CHANGEPASSVAL and SETPARENTPASSVAL macros newly added functionality.............................................................. 42
Added capabilities on GLOBALSPECIAL and SELECTIVESPECIAL macros ........................................................................... 42
Added guest user-defined fields on BatchPrint utility ..................................................................................................... 42
Added functionalities on CityPASS items......................................................................................................................... 43
Additional CityPASS enhancements: ............................................................................................................................................................... 43
New reporting services for passes near expiration .......................................................................................................... 43
Changes to Reporting .......................................................................................................................................... 44
New fields on the View Item Detail Report ..................................................................................................................... 44
Changes to Reservations...................................................................................................................................... 44
New default abilities on the Reservation Header ............................................................................................................ 44
Event reservations can now be “bulk finalized” .............................................................................................................. 45
Added ability to exclude non-finalized reservations........................................................................................................ 45
Changes to Retail ................................................................................................................................................. 47
Closed purchase orders can be opened and edited ......................................................................................................... 47
Changes to Sales .................................................................................................................................................. 48
Added functionality on CHECKAGE macro ....................................................................................................................... 48
Check boxes added to allow select of multiple records ................................................................................................... 48
Ability to scan 2D barcodes added .................................................................................................................................. 49
New .INI setting CouponsUseItemTreeTable ................................................................................................................... 49
New .INI setting MatchBirthday ...................................................................................................................................... 49
New discount and special price item and invoice rules ................................................................................................... 49
Configuration .......................................................................................................................................................................................................... 50
SysManager ............................................................................................................................................................................................................. 51
New functionality for TRI CardDog Pinpad ...................................................................................................................... 52
Passport order numbers can now be looked up in Sales ................................................................................................. 52
New .INI setting and features added for tablet/mobile users ......................................................................................... 53
.INI setting................................................................................................................................................................................................................ 53
Portrait mode ......................................................................................................................................................................................................... 53
Additional features ............................................................................................................................................................................................... 54
New SkiData layout option................................................................................................................................................................................. 55
New SETGUESTFIELDONFINALIZE macro ......................................................................................................................... 56
New .INI setting added to prune credit card data............................................................................................................ 56
New prompt to alert operator to update password ........................................................................................................ 57
New rule to automatically apply discounts in Sales......................................................................................................... 57
Updated tipping functionality on the iWL250 Pinpad...................................................................................................... 58
Changes to Salesware .......................................................................................................................................... 58
Added new preferences for unique email addresses ....................................................................................................... 58
New search .INI settings, algorithm, More button and Wildcard search added .............................................................. 58
Enhancements ........................................................................................................................................................................................................ 59
Added security rights to create and edit guests .............................................................................................................. 60
Configuration .......................................................................................................................................................................................................... 60
Added Node ID to Item Tree ............................................................................................................................................ 61
New backgrounds and icons for ReportManager and SysManager ................................................................................. 63
Changes to Self Entry ........................................................................................................................................... 64
URLs now embedded on Self Entry start page buttons.................................................................................................... 64
Deposit Page removed from Self Entry ............................................................................................................................ 64
Changes to SiriusSQL ........................................................................................................................................... 64
Updated length of i_items.user_code1 ........................................................................................................................... 64
Changes to SysManager ....................................................................................................................................... 64
Ability to view eCommerce Calendar licensing ................................................................................................................ 64
Simplify Pinpad now displayed in licenses....................................................................................................................... 65
New TenderRetail options ............................................................................................................................................... 65
New TRI option....................................................................................................................................................................................................... 66
New TRI IngeDog integration on eCommerce.............................................................................................................................................. 67
Warning prompt added for Auto Scan changes ............................................................................................................... 67
Changes to Ticketing ............................................................................................................................................ 67
New promo code data ability for Sales screen action macros ......................................................................................... 67
Configuration .......................................................................................................................................................................................................... 67
New reporting ability and country option added ............................................................................................................ 69
Sales ........................................................................................................................................................................................................................... 70
Reports...................................................................................................................................................................................................................... 70
New .INI setting added to reconnect to SalesEZ module ................................................................................................. 71
Givex Gift Card support added for eCommerce sales and gratuity .................................................................................. 71
Configuration .......................................................................................................................................................................................................... 71
Improved performance of historical Max4Sale data ....................................................................................................... 73
Added Access Control preference for processing trickled scans ...................................................................................... 73
Configuration .......................................................................................................................................................................................................... 73
New import feature......................................................................................................................................................... 74
Changes to ww.dll................................................................................................................................................ 75
New available inventory function added......................................................................................................................... 75
Known issues ....................................................................................................................................................... 75
Fixes ..................................................................................................................................................................... 75
Copyright ............................................................................................................................................................. 90
Details
We have uploaded a new update for version 4.6.03 (Update 03 for version 4.6) for download from the accesso
SiriuswareSM 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.
To ensure the longest product lifecycle possible, accesso® recommends upgrading to a recently released
operating system such as Windows 7, 8, 8.1 or 10. If you have questions concerning replacement hardware
compatibility or wish to inquire about obtaining replacement computer hardware through accesso, our hardware
specialist is happy to assist you.
Update instructions
Important: The updating process has changed to streamline the update process for their accesso SiriuswareSM
product suite. Before beginning the updating process, please review the following steps:
One-time setup
Clients may now use the DACPAC for database updates with our batch file moving forward. The Microsoft files are
required for you to use this new process. You will only need to do this the first time that you use the DACPAC or
when Microsoft releases new DACPAC files. accesso Siriusware will post recent version details when updates are
published. The current Data-Tier Application Framework is 16.4, version 13.0.3450.1.
Important: Clients using a 64-bit server must install x86 and x64 versions.
64 bit servers
1. Visit https://www.microsoft.com/en-us/download/details.aspx?id=53876
2. Click on System Requirements
3. Download both the SQLSysCLRTypes.msi x64 and the SQLSysCLRTypes.msi x86 files by
clicking on each link.
Note: Both files download with the same name by default, so it is recommended to use Save As or to rename the
downloaded files to add the version to the file name
4. Click the Download button

5. Select the check boxes for both EN\x64\DacFramework.msi and EN\x86\DacFramework.msi.
6. After all files are downloaded to the SQL server, double click each SQLSysCLrTypes.msi file and
install individually.
7. To run the DacFramework.msi files, double click on each one.
32 bit servers
1. Visit https://www.microsoft.com/en-us/download/details.aspx?id=53876
2. Click on System Requirements
3. Download the SQLSysCLRTypes.msi x86 file by clicking on the link.
4. Click the Download button
5. Select the check box for EN\x86\DacFramework.msi.

6. After both files are downloaded to the SQL server, double click on the SQLSysClrTypes.msi file to
run it.
7. Double click on the DacFramework.msi to run it.
Steps to Update
1. Create a temporary folder on the desktop of the SQL server and name it 4603 Update.
2. Create two folders inside of the 4603 Update folder called: DACPAC and Updates.
Note: This folder temporarily holds the files that need to be updated until both the script and DACPAC run
successfully.
3. Download all required update files, which are located on Downloads > Updates > 4.6 Updates page of
the accesso Siriusware portal.
4. Check for update files in: 4.6.03 Salesware, 4.6.03 Optional Modules, 4.6.03 Reports, and 4.6.03
Utilities.
5. A new update file is required for each file in the Siriusware\Updates folder.
Important: The accesso Siriusware product suite must be on version 4.5.04 before running DACPAC. Clients using
version 4.5.04 or older must update the database with required script(s) before proceeding to the next step.
6. Download the DACPAC file from the portal, located on Downloads > Updates > 4.6 Updates > 4.6.03
Salesware page. Locate SiriusSQL_DACPAC_4.6.03_01007.zip and
SiriusSQL_Update_SetupFiles.zip files and save them in the 4603\DACPAC folder
previously created on the desktop.
7. Extract the contents of both zip files into the DACPAC folder and delete the .ZIP files.
8. Create a backup of the SiriusSQL database.
9. All applications on the accesso Siriusware product suite must be closed and services must be stopped.
These applications include:
• Accounting Export
• BookEZ
• ExportService
• MessengerService
• RentEZ
• ReportManager
• Sales
• SalesEZ
• SysManager
• TallyEZ
• Web Sales Host
Note: All IIS on ww.dll and eCommerce page servers must also be stopped.
64 bit servers
1. Users must run the update directly on the SQL server and be logged-in as an Administrator with SQL
access.
2. Double click on the SirisuSQL_Update.bat file to run it.
Important: Do not right click and run as an administrator – it will cause the process to fail.
3. The C:\Windows\system32\cmd.exe dialog now appears.
4. After the DACPAC finishes running, the following dialog will appear:
Note: If the DACPAC fails a message will appear, indicating that an error occurred and the log file must be checked
to identify the issue. Failure may be caused by:
• Not running a backup
• Applications and/or services running
If these scenarios caused the failure, the DACPAC can be run again. If any other errors are present:
1. Restore your backup
2. Open a case
3. Attach the SiriusSQL_Update.log file to the case
32 bit servers
Clients using a 32-bit operating system need to edit the SiriusSQL_update.bat file by performing the
following:
1. Right click on SiriusSQL_Update.bat and choose edit to open the file in the Notepad
application.
• Locate the file path by scrolling to the bottom of the file list. The file path is located after the
Running the database update <this may take a while>… line. Edit the file path by removing the
x86 after the Program Files section. The path should read as follows: C:\Program Files\Microsoft
SQL Server\...
• Click the Save button and close the file.
2. Users must run the update directly on the SQL server and be logged-in as an Administrator with SQL
access.
3. Double click on the SirisuSQL_Update.bat file to run it.
Important: Do not right click and run as an administrator – it will cause the process to fail.
4. The C:\Windows\system32\cmd.exe dialog now appears.

5. After the DACPAC finishes running, the following dialog will appear:
Note: If the DACPAC fails a message will appear, indicating that an error occurred and the log file must be checked
to identify the issue. Failure may be caused by:
• Not running a backup
• Applications and/or services running
If these scenarios caused the failure, the DACPAC can be run again. If any other errors are present:
• Restore your backup
• Open a case
• Attach the SiriusSQL_Update.log file to the case
6. Move the new 4.6.03 application update files to the SiriusFS\Updates or

Siriusware\Updates folder, which are located on the SQL Server by default.
7. Open SysManager and log-in.
8. The Security Update dialog box appears while the system performs a precautionary scan of the
database to verify that all credit card data is secure. Click the Start button.
9. After the mandatory update has run completely, click the Close button.
10. The final setting is located on SysManager > Utilities > Data Maintenance > MaxKeys on Server button.
Updating services
The following services do not update automatically:

1. The Middleware server has a folder on the desktop named Update Pools that contains short cuts that
need to be double clicked to pull the updates down.
2. The following services: ww.dll, Export Services, Accounting Export and Messenger Service have a shortcut
on each server desktop which are named:
• Update ww.dll
• Update ExportService
• Update Accounting Export
• Update MessengerService
Updating the ww.dll
1. If not already completed, download the update file located on Downloads > Updates > 4.6 Updates > 4.6
Updates > 4.6.03 Optional Modules.
2. Perform an IISRESET/stop in the Command Prompt.
3. Double click on the Update ww.dll shortcut located on the ww.dll machine.
4. Perform an IISRESET/start in the Command Prompt.
Note: If the shortcut file is not present or the ww.dll machine is not local, copy the c_ww_4603_01019.exe
file to your c:\Program Files (x86)\Siriusware\E-Commerce folder.
1. Open a Command Prompt.

2. Perform an IISRESET /stop in the Command Prompt.
3. Double click the c_ww_4603_01019.exe file to extract it.
4. Do an IISRESET /start in the Command Prompt.
eCommerce
Steps to update eCommerce pages
Please read the below instructions carefully!
Note: Follow these steps if accesso Siriusware has updated the client eCommerce pages:
1. Make a copy of the live eCommerce folder located on c:\inetpub\wwwroot\
2. Open the folder sent by accesso Siriusware and copy the updated files into the appropriate folders
3. Check Permissions on these folders and ensure the IIS_USRS user has modify permissions:
• Images
• XMLFiles
• SiteConfig.config
4. Perform an IISRESET
Step 1: Preparing for the Update
Note: Follow these steps if the client is updating eCommerce pages independently:
Important: The following applications must be updated to 4.6.03 prior to updating eCommerce: SiriusSQL,
SalesEZ, Sales Host, and ww.dll.
1. Stop the website by opening a command prompt and typing: IISRESET /STOP
2. Download the ECommerce_Pages_4603_01025.exe update file located on Downloads > Updates >
4.6 Updates > 4.6.03 Optional Modules.
Note: Do not download the Ecommerce_Pages _Config_4603_01025.exe file.

3. Create a desktop folder named E-commerce 4603.
4. Extract the Ecommerce_Pages_4603_01025.exe file into the E-Commerce 4603 folder
created in step 3. These files contain the latest pages and updates. As next steps, files will be copied
from this location to the main eCommerce directory.
5. Copy the live eCommerce folder located on c:\inetpub\wwwroot\. This serves as a backup in the
event of update failure.
6. Apply all the Step 2 through Step 5 changes as per the instructions listed below.
Step 2: BIN update
1. Delete all the files in the c:\inetpub\ecommerce\BIN folder

2. Copy all the files from the folder to the E-commerce 4603/BIN directory
3. Paste the files into the c:\inetpub\wwroot\ecommerce\BIN folder.
Note: The eCommerce folder may have an alternate name. In this scenario, identify the correct set of pages.
Step 3: New files to be added
\admin\help\add-on-module.htm
\admin\help\calendar-alt-url.htm
\admin\help\calendar-avail-threshold.htm
\admin\help\calendar-items-incell.htm
\admin\help\calendar-mode.htm
\admin\help\calendar-remaining-template.htm
\admin\help\calendar-savings-break.htm
\admin\help\calendar-savings-format.htm
\admin\help\calendar-show-capacity-alert.htm
\admin\help\calendar-show-price.htm
\admin\help\calendar-show-savings.htm
\admin\help\calendar-show-tooltip.htm
\admin\help\calendar-use-itemurl.htm
\admin\help\developer-settings-panel.htm
\admin\help\multi-add-view.htm
\admin\images\green-circle-plus.png
\admin\images\red-circle-remove.png
\app\admin\ - (and all children)
\app\calview\calendarItemDirective.js
\app\general\ - (and all children)
\app\templates\addressVerificationTemplate.html
\app\templates\checkboxesTemplate.html
\app\templates\creditcardTemplate.html
\app\templates\customTemplate.html
\app\templates\dropdownTemplate.html
\app\templates\emailTemplate.html
\app\templates\guestTemplate.html
\app\templates\heightTemplate.html
\app\templates\maskedInputTemplate.html
\app\templates\ModalTemplateIframe.html
\app\templates\passwordTemplate.html
\app\templates\phoneInputTemplate.html
\app\templates\textMemoTemplate.html
\app\templates\textRegexTemplate.html
\app\templates\weightTemplate.html
\app\templates\zipCodeTemplate.html
\App_Themes\themeName\bootstrap\ - (and all children)

\App_Themes\sirius_admin\bootstrap\ - (and all children)
\App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.eot
\App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.svg
\App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.ttf
\App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.woff
\images\Screenshot Calendar.PNG
\scripts\xml2jsonAdmin.min.js
\template\FinalizedTemplate-Moneris.html
\template\SavedTemplate-Moneris.html
License.aspx
Step 4: Remove
Remove the Calendar folder and all contents.
Step 5: Replace Files
If changes were made to any of these files, pages will need to be manually updated. It is recommended that users
pay close attention to commonly customized files. Users should leverage a utility, such as the BeyondCompare
utility, to make the changes to customized pages. Customized pages are noted below with a * symbol:
\admin\AdminControls\ConfigEditor.ascx
\admin\AdminControls\ItemEditor2.ascx
\admin\AdminControls\ItemTreeEditor2.ascx
\admin\AdminControls\AdminMaster.master
\admin\ItemListConfig.aspx
\admin\Utilities.aspx
\app\calview\calendarDayDirective.js
\app\calview\calendarViewDayPopover.html
\app\calview\calendarViewDayTemplate.html
\app\calview\calendarViewDirective.js
\app\calview\calendarViewTemplate.html
\app\calview\calviewController.js
\app\calview\calviewService.js
\app\itemTree\itemTreeService.js
\app\app.js
\App_Themes\themeName\calendarView.css
\App_Themes\sirius_admin\style.css
\App_Themes\sirius_admin\style_admin.css
\scripts\frameBuster.js
\scripts\memberbenefits-itemshow.js
\UserControls\AngularLinks.ascx
*\UserControls\Cart.ascx
\UserControls\Email.ascx
\UserControls\ItemListMulti.ascx
\UserControls\RSControl.ascx
CalendarView.aspx
* Checkout.aspx
* Checkout2.aspx
* Checkout3.aspx
* Conf2.aspx
* GuestEdit.aspx
* GuestSelected.aspx
Step 6: Changes to Files
XMLFiles\dynamicControls.xml
Add:
<guestEdit>
<Name>UCmid_name</Name>
<RowID>mid_name</RowID>
<dbField>g.mid_name</dbField>
<Columns>20</Columns>
<MaxLength>15</MaxLength>
<Required>0</Required>
<Required_purch>0</Required_purch>
<RequiredText>Required!</RequiredText>
</guestEdit>
After this:
<Name>UClast_name</Name> section
MasterPageThemeName.master (if this file is not already present)
Remove:
scripts/resize_fancybox.js
After the
scripts/jquery-1.12.3.min.js
Add:
<script src="scripts/jquery-migrate-1.3.0.min.js"></script>
MasterPageThemeNameMobile.master (if this file is not already present)
Add:
<script src="scripts/jquery-migrate-1.3.0.min.js"></script>
SiteConfig.config
Add these new keys below the last </SiteConfig> and above the </ArrayOfSiteConfig> tag
<SiteConfig>
<Key>GivexInsufficentFundsMsg</Key>
<Value>Sorry, you do not have sufficient funds on your Givex Gift Card
for this sale. Please try another form of payment.</Value>
<Category>Checkout Settings</Category>
<Description>Set GivexInsufficentFundsMsg to the text that should be
displayed when a user attempts to use a Gixex Gift Card, but has insufficient
funds.</Description>
</SiteConfig>
<SiteConfig>
<Key>GivexLabel</Key>
<Value>Pay with Givex Gift Card</Value>
<Description>Set GivexLabel to the desired label to appear on
Checkout.aspx to enable this payment type.</Description>
</SiteConfig>
<SiteConfig>
<Key>GivexPayment</Key>
<Value>1</Value>
<Description>Set GivexPayment to 1 to enable a checkbox on Checkout.aspx
that allows paying with a Givex Gift Cards. Note, this is available through
Elavon's Simplify solution.</Description>
</SiteConfig>
<SiteConfig>
<Key>GivexGiftTermID</Key>
<Value></Value>
<Description></Description>
</SiteConfig>
<SiteConfig>
<Key>UniqueEmailError</Key>
<Value>Sorry, this email is already in use. Please click <a
href="GuestLookup.aspx">here</a> to login or use a different email
address</Value>
<Category>Guest Related Settings</Category>
</SiteConfig>
Check to see if the client already has these keys
<SiteConfig>
<Key>MicroDonate</Key>
<Value>0</Value>
<Category>Donation Settings</Category>
<Description>Set MicroDonate to 1 to enable 'round-up' donation prompts
to the ecommerce customer at checkout</Description>
</SiteConfig>
<SiteConfig>
<Key>MicroDonateText</Key>
<Value>Would you like to make a $1.00 donation to our energy-offset
program?</Value>
<Description>MicroDonateText will be the text displayed to the ecommerce
customer when using the microdonate feature.</Description>
</SiteConfig>
<SiteConfig>
<Key>MicroDonationItemDCI</Key>
<Value>DDDDDDDDDDCCCCCCCCCCIIIIIIIIII</Value>
<Description>MicroDonationItemDCI is the padded nickname of the round-up
donation DCI</Description>
</SiteConfig>
Tix2.aspx
Change this:
<script src="scripts/jquery.min.js" type="text/javascript"></script>
To this:
<script src="scripts/jquery-1.12.3.min.js" type="text/javascript"></script>
Web.config
Change this:
<httpRuntime requestValidationMode="2.0" />
To this:
<httpRuntime requestValidationType="CustomRequestValidator"
requestValidationMode="2.0" />
Step 8: Restart the Site
1. Check Permissions on these folders and ensure the IIS_USRS user has modify permissions:
• Images
• XMLFiles
• Siteconfig.config
2. Open the command prompt and type IISRESET

3. Test the site to ensure it is functioning properly
Additional information
Updated: 03/01/2017
Applies To: SiriusSQL_DACPAC_4.6.03.01007.zip
What’s new in accesso Siriusware version 4.6.03
Scope and audience
The following summarizes the newest features in the latest update of accesso Siriusware Version 4.6. This is
intended for Salesware administrators and other personnel charged with reviewing the latest features available in
ongoing releases of Salesware from accesso.
Components in this release
The components that received the version 4.6.03 designation are listed in the following table.
Note: accesso uses official release version designations.
Component 4.6.03 Update Number

Accounting Export 4603_01001
BatchPrint 4603_01005
BookEZ 4603_01001
Club Management 4603_01027
eCommerce Pages 4603_01027
Export Service 4603_01001
Folio Charge 4603_01001
GateKeeper 4603_01001
Instructor Payroll 4603_01001
Invent Pricer 4603_01001
Messenger Service 4603_01001
Pool Service 4603_01002
Component 4.6.03 Update Number
RentEZ 4603_01006
RentPrint 4603_01001
ReportManager 4603_02001
ResPrint 4603_01001
RSWebApp 4603_01005
Runexe 4603_01001
Sales (PrintEZ included) 4603_01062
SalesEZ 4603_01006
Salesware Service 4603_01003
ScanMan 5590 4603_01001
ScanMan 9090 4603_01001
ScanMan 9190 4603_01001
ScanWatch 4603_01001
SeeBooks 4603_01001
SeeBooks Online 4603_01001
Self Entry 4603_01002
ServiceMonitor 4603_01001
SysManager 4603_02002
TallyEZ 4603_01001
TallyManPPC 5590 4603_01001
TechStationPC 4603_01001
TechStationPPC 5590 4603_01001
ww.dll 4603_01020
wwService 4603_01001
Enhancements
Changes to Access Control
Additional blocking reason added to Axess for voided passes
The Axess Data Synchronizer application now has the ability to send a blocking reason of 5 to Axess. This
enhancement is configured though a setting on the _ax_settings table known as BlockReasonStatus5.
When set to TRUE, any voids of passes are sent to the exchange block. The TRUE setting triggers the Axess gates
to remove the blocked pass from the media and encode it with the new reload. When BlockReasonStatus5
is set to FALSE, the block reason = 1 and the pass is not removed from the media.
Important: To enable this feature, the Gate Controller configuration on Axess must be changed. Please contact
Axess and test before enabling site-wide changes.
New GateKeeper .INI settings and functionality
Fingerprint sensor now enabled
Prior to this release, GateKeeper module fingerprint reader hardware settings were set to FALSE. This setting
prevented GateKeeper module from detecting fingerprint reader hardware. When the fingerprint sensor
hardware was not present, some clients may have experienced a long wait for GateKeeper module to launch.
This enhancement adds a new .INI setting to enable fingerprint sensor hardware. When set to TRUE,
GateKeeper module detects the fingerprint reader. When a fingerprint reader is not present, GateKeeper module
completes startup in less time.
Configuration
Users should update PREFERENCES in the GateKeeper.INI file. To configure the new .INI setting in the
GateKeeper.INI file:
[Preferences]
EnableFingerprintReader = TRUE
Note: The EnableFingerprintReader setting must be updated to TRUE to change the default value, which
is set to FALSE.
Setting prevents rescans from activating turnstile
When a ticket is scanned to activate (unlock) turnstiles, the turnstile activates for each single guest ticket rescan.
For example, if an operator scans the same guest ticket twice, the turnstile is activated two times.
This enhancement adds a new .INI setting to prevent GateKeeper module from activating the turnstile when
the ticket scan is detected as a rescan. The setting is configured on the Gatekeeper.INI file on the
Preferences section:
[Preferences]
DontAdmitForRescan=TRUE
Note: The default setting is FALSE.
Added functionality for operator data
Clients using GateKeeper may have found that operator data is validated from the GateKeeper.INI setting
Operator=XXXXXX. When this value is blank, the default settings caused the application to validate the
operator specified on the GateKeeper.INI setting. This enhancement sets the operator data validation to use
the operator logged in on the Sales application. In addition, users now have the option of writing the Sales
operator information to the scan history. This can be configured by setting Operator=<salespoint> in the
[Preferences] section of the Gatekeeper.INI.
New Axess printer functionalities
New port option on Axess Smart Printers
Clients utilizing the new Axess smart printer AX600 and the latest version of AxCoding can now add the network
port on the printer. To configure this option, users must enter the MAC address of the printer (including the “SN”
prefix) on the ports.INI Port= setting. When this setting is configured, AxCoding uses the MAC address
to locate the network printer after the Sales application initializes it.
BatchPrint utility updated to support AxCoding
Users now have the ability to connect to an Axess printer by using an IP MAC address. This new capability is
located on the Axess Printer option on the Setup tab. Users may enter a COM port number or enter the printer’s
MAC address in the following format: SN<MAC address>.
Two new fields, AxessPOS and AxessProject have been added
Prior to this release, some clients experienced issues with the wrong AxessPOS items being defined in the
ports.INI file. This issue may have also caused duplicate RF serial numbers. This enhancement:
• Adds two new fields to the sales_pt table called AxessPOS and AxessProject
• Adds two new fields on the salespoint configuration form to set the AxessPOS and AxessProject
numbers
• Adds a verification upon Save to ensure the AxessPOS is unique across all sales_pt records when it is
set to a value other than 0
• Capability to overwrite the local Ports.INI settings for [SmartPrinter] POS= and Project=
upon startup of Sales if the values on the corresponding sales_pt records are not 0
Configuration
Users should update [PREFERENCES] and configure the new .INI setting in the GateKeeper.INI file.
Users can override the local ports.INI Axess [SmartPrinter] settings for AxessPOS and
AxessProject values. Configuration for these values must be set on the SalesPoint Configuration dialog,
which is located on the Misc tab in SysManager > Activities > System Lists > Salespoints.
AxessPOS and AxessProject can be found on the Misc tab. These settings allow the configuration of
AxessPoint and AxessProject values in SysManager. When the fields in AxessPOS and AxessProject
are set to any value other than 0, the salespoint database record overwrites the settings in the local Ports.INI
file.
Note: The port setting for the Axess printer must be set locally in the Ports.INI file. Values cannot be negative.
To help prevent duplicate RF serial numbers, SysManager performs a check after saving changes to the salespoint
configuration. This check ensures that the value set for the AxessPOS does not already exist on a previously
created salespoint record in the database. If the AxessPOS value already exists in the database, the operator is:
• Alerted of the salespoint already containing the AxessPOS value.
• Asked to change the AxessPOS value on the salespoint currently being edited prior to saving.
Note: This check only occurs for non-zero values in the AxessPOS field. The AxessProject field is always the
same number so the check is not necessary.
New SETPARENTACCVAL and CHANGEACCVAL macros for access table
New functionality has been added that allows Sales screen action macros to insert or edit data on the Access
table. This functionality can be configured through the new macros, SETPARENTACCVAL and CHANGEACCVAL.
Users should implement the same logic as the SETPARENTPASSVAL and CHANGEPASSVAL macros.
Note: The SETPARENTPASSVAL macro is used on modifiers and CHANGEPASSVAL macro is used within the
validation template located on the item/pass relationship Discount macro field.
SETPARENTACCVAL and CHANGEACCVAL macros can be set on the item Sales Action tab for an item, located
on the Sales Screen action. The setting enables the macros to execute based on the Item is Sold field or the
Discount macro for assigned item field. Depending on when the macro initiates, these settings can be located on
the Create Access Record template or the Validation template.
Changes to Dynamic Pricing
New SOLDDATE() macro and Dynamic Pricing capabilities
To give users additional capabilities for pricing items, this enhancement adds Dynamic Pricing Conditions in Sales
and eCommerce modules. Users can manage yield and maximize revenue by establishing Dynamic Pricing Rules
based on:
• Quantity sold
• Quantity remaining
• Sold-on date
Online orders associated with new Dynamic Pricing features reflect accurate real-time inventory based on set
Dynamic Pricing quantities and remaining quantity available. Capacity controlled pricing is defined by user set
parameters for the quantity sold and/or quantity remaining for an item.
Note: When an item is configured for capacity controlled pricing:

• Sales and eCommerce modules verify available inventory at the specified price level when quantities are
changed on the line item.
• The operator cannot change the quantity of an item that is included in a recalled sales transaction.
• The quantity remaining for the specified price level for the item only displays in Sales.
New Dynamic Pricing Rules
Dynamic Pricing Rules were added to create flexibility for pricing programs that enact price changes based on:
• Limited numbers available (*REM)
• How many items have been sold (*SOLD)
• To offer specified prices for sales that occur on or before a specific date.
As per below, each rule is set to display a specific value for a given item:
• M4SREM() - Max4Sale items remaining
• M4SSOLD()- Max4Sale items sold
• P4SREM() - Points4Sale points remaining
• P4SSOLD() - Points4Sale points sold
Note: New Dynamic Pricing Rules can specify an exact number, range of numbers or =, >, < values.
SOLDDATE() macro
The SOLDDATE()macro was added to mimic the existing DATE condition. SOLDDATE()evaluates item pricing
based on the actual purchase date.
Changes to eCommerce
New eCommerce Calendar module available
To give clients extended capabilities on capacity based Dynamic Pricing Rules and items with limited capacities, a
new eCommerce Calendar module has been added. The Calendar module integrates with capacity based rules to
display remaining quantity by price level. Users may also configure the Calendar module without capacity based
rule integration.
Note: the eCommerce Calendar is a separately licensed module.
This enhancement allows integration with rules that enforce Max4Sale or Points4Sale and capacity based pricing.
Max4Sale and Points4Sale rules can be located on SysManager > Items button > New/Edit button > Restrictions
tab.
The Capacity Based Pricing dropdown allows users to select the With unlimited Max4Sale/Points4Sale option.
When this option is selected, SysManager creates a new Max4Sale or Points4Sale time entry with a numeric value
which can be set up to 999,999. When the value of 999,999 is set, Sales and eCommerce sell items without
limiting how many are sold. The Alert eCommerce when amount remaining in current level is =< field enables
eCommerce to show the quantity remaining for the specified price level when it is less than or equal to the set
value.
Note: Users must configure Max4Sale or Points4Sale settings to integrate these behaviors with the Calendar
module.
Calendar module settings
Users can view Calendar module settings on the Calendar View Options dialog located on eCommerce > Admin
Panel > Item List Configuration > Folder(s) (on which the calendar is enabled).
Users can configure the Calendar module view by selecting the preferred setting on the Calendar Mode
dropdown, which offers Event View or Variable Pricing View. An example of the Variable Pricing View setting is
as follows:
An example of the Event View setting is as follows:
Important: The Calendar module is only available for users on accesso Siriusware version 4.6.03 or above.
SiriusSQL, ww.dll, Sales, SalesEZ and eCommerce applications must be on version 4.6.03 or above.
New setting to show unavailable modifiers
A new SiteConfig setting has been added to show unavailable modifiers called
DisplayNonAvailableMods. This enhancement offers the following benefits and settings for users:
• When an unavailable module is selected or the select quantity exceeds its availability, the Add to Cart
button is disabled.
• When DisplayUnAvailableMods is set to 1, the pages continue to display modifiers that either are
sold out, are set to 0 availability or have the check box Prevent Sales when no limits are set checked.
• When DisplayUnAvailableMods is set to 0, the pages hide the modifiers that either are sold out,
are set to 0 availability or have the check box Prevent Sales when no limits are set checked.
Sales
Sales now communicates with the accesso Passport® product suite to enforce unique email address entry for
guests/contacts. This behavior adds the ability to check for unique guest emails being entered and to alleviate
duplicate guest records. In addition, the Sales application respects this preference when creating a new
guest/contact or editing an existing guest/contact.
SiriusSQL
The SiriusSQL database has added a new a default setting for unique email addresses. This feature adds a new
row on the Settings table which enforces unique email addresses for guests/contacts. This new setting is
called General.EnableUniqueGuestEmailAddresses and its default is set to FALSE.
SysManager
SysManager now communicates with the accesso Passport product suite to enforce unique email address entry
for guests and contacts. This enhancement includes a new Force Unique Guest Email Addresses check box that
can be located on SysManager > Preferences > Guests > Guest Preferences dialog > Misc tab.
In addition, when entering a new email address on the Guest Edit dialog, the Force Unique Guest Addresses
setting on the Guest Preferences dialog is respected.
Note: This check box is enabled only if there are currently no duplicate email addresses present on guest and
contact records. It is recommended that clients with this issue contact accesso Siriusware Technical Support prior
to activating this new preference.
ww.dll
The ww.dll installer now checks for email uniqueness in newguest and modifyguest when the preference for
checking for uniqueness is enabled on the client eCommerce site.
New notifications for Web Sales Host utility errors
When a client experiences a large number of errors on the server, operators may delay reporting these issues
while they are focusing on the immediate needs of the business. Many clients would like to be proactive in
reviewing server errors so they can prevent significant issues in the future.
This enhancement enables a notification email and creates notification records when an error is generated on the
Web Sales Host utility. The notification records capture data for initial and reprocess errors that result in adding
the following new activity types:
• 1350: Web Sales Host Error - Initial Error
• 1351: Web Sales Host Error - Reprocess Error
Note: The notification email is only sent if email notification is set for the operator.
Updated Instructions folder removed from eCommerce
To streamline installation for users, the UpdateInstructions folder has been removed from eCommerce
module installation files on builds 4.5.03, 4.5.04 and 4.6.01. Installation information is now published separately.
Changes to Food Service
Room charges now reversible in Table Service F&B module
This enhancement adds the ability to reverse room charges in the Folio Charge module using the Reverse
Payment button in the Sales application. When a room charge is used as a form of payment in F&B Sales, the
transaction amount is reversed after the operator recalls the transaction and clicks the Reverse Payment button
located on the bottom row of icons on the Sales screen.
The operator is then directed to the Reverse Payments dialog, which displays reversible payments for the
transaction.
The operator selects the payment(s) to be reversed and when all selections are completed, the operator clicks on
the Reverse button. After the transaction is selected and successfully reversed, the Reverse Payment Result
dialog displays the reversed transaction details.
The operator must click the OK button to return the main Sales screen.
Changes to TallyMan
Ability to remove scanned barcode prefix
Users can now remove select prefix characters from the barcode scan on the TallyMan module. This enhancement
adds a new option in the Misc tab on the Configuration dialog to allow the user to specify the number of prefix
characters to strip from a scan.
Changes to Memberships and Passes
Improved auto-renewal formatting
In some scenarios, operators may have been confused by Pass auto-renewal details located on the Pass
Information dialog in Sales. Passholders with a DebitWare number were displayed on the Pass Information
dialog in a manner that may have caused some operators to associate the DebitWare number with the card to be
used for the renewal. To alleviate confusion for operators, this enhancement adds the current renewal start date
to the Pass Information dialog. In addition, the auto-renew information for the pass information has been moved
closer to the top of the dialog box.
New BLACKOUT macro and pass blackout functionalities
New BLACKOUT macro added for individual blackout dates on passes
When season pass holders leave their passes behind, the operator can issue a one-day temporary ticket for use in
place of the forgotten season pass. Previously, operators needed to manually blackout the season pass to match
the date of the one-day temporary ticket to prevent pass holders from using both their day ticket and pass for
access. The new BLACKOUT()macro streamlines the season pass blackout process for front line operators.
When this macro is present, individual blackout dates are set on the pass number that match the valid dates for
the temporary ticket.
Configuration
Users should create a coordinating blackout item such as a “Forgot-My-Pass” item. Configure the validation
template of the “Forgot-My-Pass” item with the new BLACKOUT() macro within the Discount Macro box
located on the Items description> Action tab> Template button> Item/Pass Relationships tab.
Note: The BLACKOUT() macro can be set with either Optional or Forced validation.
In addition, the user may enter in a specified reason in the parenthesis of the macro (e.g., FORGOT, MISPLACED)
that populates the Blackout Reason field of the pass record.
Sales
In order to use the new BLACKOUT() macro functionality:
1. The operator sells a “Forgot-My-Pass” item.
2. The operator enters the season pass number and the item is validated using either forced or optional
validation.
3. The operator finalizes the sale and prints or encodes the day ticket.
This new automation action initiates a back-end process which allows the season pass to:
• Validate the line item
• Set the individual blackout date range that is equal dates specified on the validated item
• Notes the blackout reason in the macro
Note: The BLACKOUT() macro functionality only occurs after the Finalize action. To avoid discrepancy that may
occur if the sales transaction is cleared, functionality does not occur the moment the pass is validated or upon the
Save action.
Added option to prevent blackout date pass printing
In previous versions, voided passes could not be printed but passes with active individual blackout date ranges
were allowed to be printed. This new setting prevents passes with active individual blackout date ranges from
being able to be printed. This can be set on the new check box, Do not print passes with active Individual
Blackouts, located on the Print Options tab on the BatchPrint utility. When the check box is checked and the
printing date falls within the individual blackout date range for the pass, the pass does not print.
New .INI setting to prevent printing a pass with blackout
A new .INI setting has been created to prevent printing a pass. This is functionality is useful when the pass has
an individual blackout date range set that includes the date on which the operator attempts to print the pass. This
enhancement can be configured on the following Sales32c.INI setting:
[Preferences]
DoNotPrintPassWithIndividualBlackout=TRUE
Note: The default setting is FALSE.
CHANGEPASSVAL and SETPARENTPASSVAL macros newly added functionality
To accommodate expanded features for memberships renewed on accesso Passport product suite and onsite
sales, two enhancements have been added:
• The = sign has been added to the CHANGEPASSVAL macro, which allows users to overwrite the original
value by accessing it inside of the validation template.
• The SETPARENTPASSVAL macro now allows modification on pass validated items.
When the CHANGEPASSVAL macro is used for renewals, if the + sign is not present the macro assumes that the
user wants to add to the existing number. The SETPARENTPASSVAL macro sets the value to the specified
number.
Added capabilities on GLOBALSPECIAL and SELECTIVESPECIAL macros
The Sales application macros, GLOBALSPECIAL and SELECTIVESPECIAL, now allow users to display a list of
items eligible for the macro-applied special and to select items to be discounted. These macros are set on: Create
Pass > Action Specifics > Global Settings tab on the Sales Screen action to execute when this item is validated
dialog:
SELECTIVESPECIAL("SPEC_NAME ",,,PROMPT)
GLOBALSPECIAL("SPEC_NAME ",,,PROMPT)
Note: This prompt is configurable per special. The special is padded to ten characters and the PROMPT parameter
is added on the fourth position in the macro.
Added guest user-defined fields on BatchPrint utility
To match the functionality of the column names made available in pass printing via Sales, the BatchPrint
application now offers guest "text_1" through "text_8" user-defined columns for layouts as "tmp_ptxt1"
through "tmp_ptxt8".
Added functionalities on CityPASS items
Select clients using CityPASS items would benefit from real-time validation and record usage at respective
salespoints. These capabilities are ideal for clients who prefer to trade a CityPASS voucher for the attraction’s
admission ticket prior to allowing guest entry into the venue. To support these client needs, this enhancement
offers a new grid and edit form for third party validation in SysManager located on Preferences > 3rd Party
Validation.
Additional CityPASS enhancements:
• CheckPass, ValidatePass, CheckAndValidatePass and TricklePass now supports

CityPASS item and 3rd Party Validation functionality
• A new Siriusware.CityPASS.dll feature has also been added to be used from the SalesEZ
application for 3rd Party Validation
• Sales performs CityPASS validations which recognize if the barcode is valid or has been used
• If a duplicate entry is made and the Check item is selected on the Remote Validation tab in SysManager,
the message, "Scan already used in sale" displays.
Note: When the operator clicks the OK button or closes the dialog by clicking the X button, the duplicate scan is
removed from the Validation dialog.
Note: These enhancements support CityPASS only.
New reporting services for passes near expiration
Clients that have guests utilizing Payment Plans and/or Auto-Renewals need options to monitor and maintain
updated credit card information. These clients would benefit from the ability to proactively contact customers
prior to the automated Payment Plan or Auto-Renewal date to request updated credit card information.
The Sales application now writes the expiration dates of stored credit card numbers on the Guest and Guest
Pass tables. This functionality adds reporting capabilities that can be used to segment guests with credit card
information on file near expiration. This new reporting feature helps prevent lapse in processing Payment Plans
and Auto-Renewals. For additional security, these reporting services access expiration dates without
compromising encryption.
Changes to Reporting
New fields on the View Item Detail Report
To give clients the ability to view item messages and account information on the Sales application, new fields have
been added on the View Item Detail Report. To test these new reporting fields, users should perform the
following steps:
1. Update the _rs_ViewItemDetail sproc in SSMS.
2. Upload ViewItemDetail RDL to SSRS.
Note: A new hidden parameter has been added for the report called ShowAccount, which can be viewed when
managing the report in SSRS and locating the Parameters section. The user can now select True or False for this
parameter to show or hide the account information on the View Item Detail Report.
1. Configure the Sales application to run the View Item Detail Report via the following .INI setting:
[ReportingServices]
ReportServer=http://[ServerNameHere]/ReportServer
ItemDetailsReports=ViewItemDetail
2. After selling items on the Sales application, right click the item and select the View Detail option to
allow the report to run.
3. Test Max4Sale, Items Sold on Account and Line item messages on listed items to verify in the report.
Changes to Reservations
New default abilities on the Reservation Header
This enhancement adds the ability to set defaults for the dropdown box options on the Reservation Header.
Below is a list of what can be set in the Sales32c.INI file:
[ReservationDefaults]
Accommodation=CHALET CONDOS
PickUpLocation=FED-EX
BaseLodge=Lodge 33
WrapUpCode=NO FLIGHTS
UserDef1=YES
UserDef2=8:30 AM
UserDef3=Test
MarketingCode=EMPLOYEE
SourceCode=MEMBER
Note: Set values must be valid within the dropdown selection and are case sensitive.
Event reservations can now be “bulk finalized”
Some clients process large amounts of reservations for events each day. To validate daily revenue, event
reservations need to be finalized each day. To give users the ability to bulk finalize events, this enhancement adds
the following new functionalities:
• A DCI dropdown and Item Start Date filter to the recall options for both Sales and Reservations
• A new button called Partial Finalize added in the matching Reservation Review List dialog
The DCI dropdown creates the ability to retrieve a list of reservations that contain a specific event item for a
specified date. Partial finalize retrieves a list of unique saved items and start dates based on the reservations
selected in the Reservation Review list.
In addition, item descriptions are now shown on the Item dropdown in the recall by DCI section on the Recall Sale
dialog. This allows for easier recognition and selection of items by users.
Added ability to exclude non-finalized reservations
Some clients use the Review dialog to view reservations. By default, the Review button displays non-finalized
reservations and sales that match search criteria. To give users more Review List functionality when the specific
item and/or date used in the search has been finalized, this enhancement allows users to omit these reservations
from the Review list.
In addition, a DCI and Item Start Date feature has been added to the Recall Sale dialog, which allows users to
batch finalize reservations for specific items. This section also includes the Exclude reservations where selected
DCI has already been finalized check box, which excludes orders that contain non-finalized items from displaying
on the Review dialog.
Note: The Exclude reservations where selected DCI has already been finalized check box is not checked by
default.
Changes to Retail
Closed purchase orders can be opened and edited
Users can now open and edit a closed purchase order. This functionality is available in the SysManager application
directly from the Re-Open button, which can be located via SysManager > Activities > Inventory Activities >
Purchase Orders > Find button. Users can now open a closed purchase order by selecting it and then clicking the
Re-Open button.
Alternately, users can select a closed purchase or order, click the Edit button and click the Re-Open button on the
Purchase Order Edit dialog.
Changes to Sales
Added functionality on CHECKAGE macro
To improve functionality of the CHECKAGE macro, an additional option has been added. The CHECKAGE macro
now accepts a parameter to specify that only the birth year should be entered rather than the entire birthdate.
For example, the following collects a year and verifies that the entry is an age between 21 and 99 years old (based
on age birthday of January 1st of the year entered):
CHECKAGE(21,99,TRUE)
An additional check occurs if an invalid age is entered with the CHECKAGE macro. After the operator attempts to
add the information again, a prompt displays and requests reentry for the birthdate/birth year.
Check boxes added to allow select of multiple records
In previous versions, users looking up a list of access records in Sales had the options to select a single record to
refund or exchange or to select all records to refund or exchange. To give users more flexibility to select multiple
records, this enhancement allows operators to select one item or multiple items for refund and exchanges in
Sales.
Ability to scan 2D barcodes added
Operators now have the ability to scan a 2D barcode, which is typically the type of barcode used on a driver's
license. 2D barcode scans may be used for performing a guest lookup in Sales or for creating a new guest when an
existing guest record is not located. To perform a lookup, the cursor must be positioned in the First Name or Last
Name field located on the Guest dialog.
New .INI setting CouponsUseItemTreeTable
To enable functionality for the Coupon button to use ItemTree table restrictions, a new .INI setting has been
added, CouponsUseItemTreeTable. The default value is FALSE, which prompts the behavior to use the
Items table restrictions. When the value is set to TRUE, coupons using the %%C1CODE will use the ITEMTREE
to check for restrictions.
New .INI setting MatchBirthday
A new .INI setting called MatchBirthday has been added to the [Preferences] section of
Sales32c.INI. When MatchBirthday is set to FALSE, the Sales application searches for guests with a first
and last name that match the swiped license after a driver's license barcode is scanned. The MatchBirthday
setting does not match the birth date on the driver’s license.
Note: The default for MatchBirthday is set to TRUE.
New discount and special price item and invoice rules[JR1]
Sales can now apply discounts based on the items that are added to the sale. These new rules are applied at the
invoice (sale) level and allow for free, discounted or specially priced items. This functionality is enabled either by
applying invoice rules via MainButton=RUL or the rules apply as an order finalizes. Applying invoice rules
triggers a new type of dynamic pricing rule called Sale Discount Rules.
Note: To enable this functionality, the salespoint must be included within the appropriate dynamic rule group
with dynamic pricing rules assigned.
Configuration
Users can create several combinations of Sale (Cart) Discount Rules and can configure these settings based on
specific items to be discounted and the functionality of the Dynamic Pricing Rule. Some examples of
configurations for new discount, special price item and cart rules may include:
10% OFF any personalized product/specific range

Automatically apply a 10% special to any personalized item included in item group 4 that isn’t already discounted
by another special (TRUE parameter).
IF(SELECTSET(DCISET(4), >0, ALL, TRUE), APPLYSETSPECIAL(10OFF,10))
Any 2 items for $10

Apply the 2 for 10 special to items included in Item Group 5 that do not already have a special attached (TRUE
parameter). Do this for every two qualifying items in the sale (2 items would be discounted, 3 items would have 2
of the 3 items discounted, 4 items would all be discounted, 5 items would have 4 of the 5 items discounted, etc.)
IF(SELECTSET(DCISET(5), 2, , TRUE), APPLYSETSPECIAL2(2FOR10,10))

IGNOREANDREPROCESSSET()
10% off when purchase in a specific range totals $20 or more

Customers receive 10% off all books associated with Item Group 6 and souvenirs located in category SOUVENIRS
with a purchase $20 or more of these regularly priced items.
IF(SELECTSET(DCISET(6;,SOUVENIRS) , >0, ALL, TRUE) AND

ITEMTOTAL(>19.99),APPLYSETSPECIAL(10OFF,10))
There is an additional configuration option that makes this discount rule easier to read. This option can be
configured by specifying the Department nickname.
IF(SELECTSET(DCISET(6;RETAIL,SOUVENIRS) , >0, ALL, TRUE) AND

ITEMTOTAL(>19.99),APPLYSETSPECIAL(10OFF,10))
Spend over $100 and get $10 off of sale

This rule uses the sale total (including items with discounts) that are over $100 and automatically adds an item for
-$10 (to discount the overall sale by $10).
IF(SELECTSET(DCISET(ANY),>1, ALL) AND ITEMTOTAL(>99.99, TRUE),
SELECTITEM(RETAIL,DISCOUNTS,10OVER100,PRICE(-10)))
Spend over $100 and get an additional 10% off regularly priced items
This rule uses the sale total (including items with discounts) that are over $100 and automatically applies a 10%
discount to any item not already discounted by a special.
IF(SELECTSET(DCISET(ANY),>=1, ALL) AND ITEMTOTAL(>99.99, TRUE),

SELECTSET(DCISET(ANY),>=1, ALL, TRUE) APPLYSETSPECIAL(10OFF,10))
Note: To enable these settings, DCIs and specials must be configured to match the samples above.
SysManager
SysManager a has a new menu item called Sales Discount Rules Groups, which allows users to create and apply
discounts based on the items added to the sale:
• A new security role has been created called, SysManager - List - Sale Discount Rule Groups. When this
role is assigned, it allows an operator to create and edit Sale Discount Rule Groups.
• A new type of Dynamic Pricing Rule (Sale Discount Rule) has been created, which can be set and assigned
to Dynamic Rule groups. This new functionality of sale/cart rule feature allows specific pricing rules to be
assigned to certain salespoints and is located in SysManager > Activities > Item/Sales Lists > Sale Discount
Rule Assignments dialog.
In addition, required data tables and columns have been in added to the SiriusSQL database in support of this new
functionality.
New functionality for TRI CardDog Pinpad
The TRI CardDog Pinpad is now supported and may be configured through a new setting used to define the
location of CardDog Pinpad in Sales32c.INI:
[carddog]
address = 192.168.0.30:4405
An additional new setting has been created to define CardDog TenderPortal in Sales32c_system.INI:
[Server]
CardDogAddress = 192.168.0.2:4405
CardDogTimeout =60
CardDogTerminalID = 0033333333330003
In addition, support has been added to bypass the TRI Pinpad when not required for a transaction. For example,
recurring payments, batch close and purchases with a stored token may bypass the Pinpad and go directly to the
server for processing. To enable this capability, the address and port must be configured to
Sales32c_system.INI as follows:
[Server]
cardDogDirect = qa.carddog.com:46010
Passport order numbers can now be looked up in Sales
This enhancement gives clients using the accesso Passport product suite integration the ability to easily lookup
orders in the Sales application by using the order number from the accesso Passport product suite. When a user
completes a Sales transaction, the accesso Passport product suite order number is now stored in the SiriusSQL
table, resrvatn.user_resno. To recall the order on the Sales application, users may scan a barcode that is
formatted to %RCXXXXXX where XXXXX is the number in resrvatn.user_resno.
New .INI setting and features added for tablet/mobile users
To optimize the Sales application for tablet/mobile users, a new .INI setting, portrait mode capability and other
additional features have been added.
.INI setting
A new .INI setting is now available to enable tablet mode. This setting can be configured on:
[Preferences]
Tablet=FALSE
Note: The defaults for this .INI setting is TRUE.
Portrait mode
Portrait mode orientation has been added to the Sales application. Users have the ability to specify the number of
action buttons that are using an .INI setting through the following configuration:
[Interface]
NumMainButtons=4
Note: The maximum number of action buttons allowed to be set is 12.
In addition, users now have the ability to set up the main action button as a directory of action buttons. This can
be set up in the MainButtonX .INI setting as follows:
[Interface]
MainButton1=<text>sub action</text><id>DIR1</id><action>CLS</action>
<action>FIN</action><action>APP</action>
The tags used in this configuration specify the following:
• <text> contains the text to display.

• <id> is the name of the button, it looks for id.bmp to display
• <action> is the list of main action buttons that the setting contains
When the Sales application detects that the window size is in portrait mode, it reorients the screen view
automatically. On portrait orientation, the invoice screen is on top and the item selection buttons are found at the
bottom. By default, the screen allocates both sections at fifty percent. The default may be changed by configuring
the following .INI setting:
[Interface]
PortraitModeTopScreenPct=60
The above setting allocates the invoice portion of the screen to the specified percentage of 60 percent.
Note: When the tablet is in portrait mode, the Sales screen maximizes automatically.
Additional features
To optimize the Sales application for tablet/mobile users, the following capabilities have also been added:
• The Sales summary can now be viewed by clicking the Sale Total option, located on the top left of the item
list.
• Users have the ability to scroll by placing their finger on the items list and swiping it in the preferred
direction.
• When all M&M buttons (status buttons) are green, they are hidden automatically.
New SkiData printer integration
To further printing hardware options, this enhancement integrates SkiData printers with Sales applications. This
functionality allows users to configure and view a SkiData printer on the available printer list. Users can enable
SkiData printer functionality by:
• SmartPrinter section PrinterType in ports.INI to the printer type

• SmartPrinter section Port in ports.INI to the port that the printer is connected to
• SkiData section Server to the SkiData server address in Sales32c.INI
• SkiData section User to the username in Sales32c.INI
• SkiData section Pass to the password for the user in Sales32c.INI
Example:
ports.INI
[SmartPrinter]
PrinterType=CoderUnlimited
Port=USB
Example:
sales32c.INI
[SkiData]
Server=https://sandbox.skidata.com/dta
Client=655229004
User=user
Pass=123456
The following printer hardware is supported through this enhancement:
• CoderSimulatorGui
• KDDuo
• KeyDetector
• SD705
• SD805
• KDGate
• KeyDetectorGate
• MRGate
• MobileReaderGate
• Cox70
• Cox70TX
• Cox70TDM
• CoderLight
• CoderBasic
• CoderUnlimited
New SkiData layout option
To streamline ticket and voucher printing setup for SkiData, a new option has been added on the Item
Edit/Printing tab. The SkiData Layout option can be located on the Ticket and Voucher Printing Setup dialog.
New SETGUESTFIELDONFINALIZE macro
This enhancement adds a new macro, SETGUESTFIELDONFINALIZE which gives users the ability to set guest
column fields upon finalize. The macro takes the following parameters:
• Column name
• The second column is the value to set. This can also work with the GETDATE() macro to set the column
to the current date.time.
• The override flag - 1 is always write, 0 is write only if the column is not already set.
SETGUESTFIELDONFINALIZE("date_1",GETDATE(),0) - sets the date_1 to the current date/time

provided it wasn't already set before.
SETGUESTFIELDONFINALIZE("memo_1",test,1) - always sets the memo_1 field to test.
In addition, the Sales screen actions macro commands now result in transaction date being written to the
date_1 field in the database.
• SETGUESTFIELDONFINALIZE("date_1",GETDATE(),0) - this macro injects the date stamp only

if date_1 is blank
• SETGUESTFIELDONFINALIZE("date_1",GETDATE(),1) - this macro injects the date stamp and
overwrites any previous entry in the date_1 field.
New .INI setting added to prune credit card data
A new .INI setting, PruneDaysOffLineCC has been added to give users more flexibility with managing
settings for online and offline credit card data. Data records related to offline credit card transactions are stored
and later deleted based on the number of days specified on the PruneDaysOffLineCC.INI setting. This
setting can be configured on:
[Preferences] PruneDaysOffLineCC = 90
The minimum setting for offline data is thirty days and the maximum is 180 days. Records related to online credit
card transactions are deleted according to the Prune credit card data out of local Sales data every ‘X’ days and
Prune daily at ‘X’ credit card transaction data on Server which is older than ‘X’ days settings which can be
configured in SysManager > Preferences > Miscellaneous > PA-DSS tab
Note: The default settings are forty-five days for online data and ninety days for offline data.
New prompt to alert operator to update password
A new prompt has been added to provide lead time for operators to update their passwords. Sales now alerts
operators within fourteen days of when the password is due to expire by displaying a prompt one time per day.
Operators can use the prompt to access the Change Password option until their password credentials have been
updated.
When operators log-in to Sales for the first time in a given day, it determines if their password needs to be reset
within fourteen days. If the reset is needed within fourteen days, a prompt appears with a message that their
password expires within “X” days and to provide yes or no option to reset. When an operator selects:
• Yes - The operator is logged-in to Sales and directed to the Change Password option on the Action menu.
• No – Sales continues to launch.
New rule to automatically apply discounts in Sales
Some operators regularly process transactions with specials attached to items added to the Sales. To alleviate the
need for operators to manually apply specials, this enhancement adds rules to automatically apply discounts. In
addition, discounts can now be applied based on the contents of the Sales transaction.
Updated tipping functionality on the iWL250 Pinpad
Previously, operators were only able to add a tip through the Finalize dialog. This tipping enhancement supports
the firmware setting which enables tipping on the iWL250 Pinpad. Operators using the CardDog application can
now tip directly on the iWL250 Pinpad. This functionality is configured on the following setting in
Sales32c.INI:
TIPS=FALSE
Note: If Tips=TRUE is in the .INI, tipping works only by entering the tip on the salespoint.
Changes to Salesware
Added new preferences for unique email addresses
To improve the new database installation process and preferences for established accesso Siriusware clients, this
enhancement helps alleviate duplicate email addresses. New preferences have been added on Sales, SysManager
and ww.dll applications. eCommerce and SelfEntry pages also respect new preferences for creating a new
guest/contact or editing an existing guest/contact. In addition, these enhancement preferences are set as the
default for clients that create new databases for implementation.
New search .INI settings, algorithm, More button and Wildcard search added
Some clients performing searches in Sales applications may have experienced one or more of the following:
• Search stops when items are found and does not continue to search other fields.
• Search results may be inconsistent between SysManager and the Inventory Lookup in Sales.
• Though the search settings are the same, the order of the searches performed in Inventory Lookup are
fundamentally different than searches performed in Sales.
• When there is an .INI setting set to “X” number of searches, results are constrained to the first “X”
number of items.
• The inability to view all items that match search criteria.
Enhancements
.INI setting
This enhancement has added two .INI settings and created a search algorithm to improve retail inventory
search functionality. The new .INI settings have been added specifically on the Inventory Lookup search dialog
boxes.
• InventoryTrackingLookupOrder defaulted to the same values as TrackingLookupOrder

• InventoryMatrixLookupOrder defaulted to the same values as MatrixLookupOrder
Search algorithm
A new search algorithm modifies the following functionalities:
• Description is not treated as a different field. When a search does not return results, Sales does not
perform a separate description search.
• A vendor specific code or multi-code are no longer needed.
• Inventory[Tracking/Matrix]LookupOrder is used to determine searchable fields.
• Interrupted searches can resume from a given location.
More button
The More button has been added on the Matching Items dialog:
The More button can be used when the search results exceed the parameters specified in the
MaxInventoryMatches .INI setting. When a user clicks the More button, Sales continues the search when
there are more records to be displayed.
Wildcard search
The Inventory Lookup dialog in Sales now offers a Wildcard search check box.
When a Wildcard search is indicated by the user, results are retuned for all searched fields.
Added security rights to create and edit guests
Administrators can now set operator profiles to allow the ability to create new guest profiles and/or edit existing
guest profiles. SysManager and Sales applications allow users to assign security role settings as follows:
• SysManager - Create New Guest

• SysManager - Edit Existing Guest
• Sales - Create New Guest
• Sales - Edit Existing Guest
Configuration
Users can modify the default Global Settings in SysManager. Configure changes on the security role settings
located on Preferences description > Security button > Global Defaults button. Sales assigned settings can be
viewed by selecting the Categories dropdown > GUEST option. The user can modify the following assigned
settings:
• Sales - Allow Create New Guest

• Sales - Allow Edit of Existing Guest
SysManager assigned settings can be viewed by selecting the Categories dropdown > SECURITY option. The user
can modify the following assigned settings:
• SysManager - Menu/Activity – Guests – Security - Create

• SysManager - Menu/Activity – Guests – Security - Edit
Note: New role settings are enabled by default in the Global Settings security role. When users want to assign
settings to specific security roles, users must edit the Global Settings and disable settings before they take effect
for the other assigned roles.
Added Node ID to Item Tree
Clients using the accesso Passport product suite may need to routinely obtain the Node ID for Item Tree folder
configuration. In previous versions, when a new folder was added or changed, the Node ID was viewable only
after the user ran SQL script. This process could be time consuming because all users at the client site may not
have access to run SQL script.
To make it easier for clients to using accesso Passport product suite integration, this enhancement displays the
Node ID on the Item Tree dialog box in SysManager. The Node ID is indicated by Node #, which is a read-only field
that appears in the top right of the Restrictions section of the pane.
After the user selects a folder or item, the Node ID appears.

New backgrounds and icons for ReportManager and SysManager
To update branding for the most recent software release, ReportManager and SysManager now have an updated
background/log-in/splash screen and a new icon for each application.
Changes to Self Entry
URLs now embedded on Self Entry start page buttons
This new option adds a new default for both the StartPageAlt.aspx and StartPageAlt2.aspx Self-
Entry pages by having URLs embedded in each button. This new feature also gives the ability to change the URLs
associated with the buttons as needed.
Deposit Page removed from Self Entry
Some clients use the Deposit Page to add a credit card to a guest profile or to attach the credit card number to all
guests associated with the guest that checks in. The Deposit Page does not validate, collect a deposit or charge
the associated credit card; its functionality has been removed from Self Entry pages. Clients previously using the
Deposit Page to store credit card information must now collect credit card details at the point-of-sale.
Changes to SiriusSQL
Updated length of i_items.user_code1
To increase the length of varchar(15), i_items.user_code1 has been updated. Varchar(15) has
increased by five characters and is now varchar(20).
Changes to SysManager
Ability to view eCommerce Calendar licensing
Users now have the ability to view if they have licensing permissions for the eCommerce Calendar. This
information is located on SysManager > Preferences > Sales Point Licenses, which now displays the eCommerce
Calendar view. If the license exists within the eCommerce Calendar module, the check box is checked.
Note: Users must have the Calendar module license installed to have access to the Calendar module. The check
box is unchecked and details are in read-only mode for users who do not have access to the eCommerce Calendar
view.
Simplify Pinpad now displayed in licenses
To allow clients the ability to use mobile payment solutions via Elavon’s Pay@Table solution for wireless capable
processing, a new and secure Pinpad Sales Host system communication has been developed. The new Pinpad
Sales Host license is now active and can be located in SysManager > Preferences > Sales Point Licenses.
New TenderRetail options
This enhancement supports clients using TenderRetail by offering integration with their new release, MCM
Windows. Users can configure these settings in SysManager > Activities > Financial Lists > Payment Types > New
> Process Via dropdown > TR MCM Windows.
New TRI option
Users may now use TRI IngeDog to process payments. Users may activate this new integration, which is located in
SysManager > Activities > Financial Lists > Payment Types > New/Edit button.
After the Payment Type dialog appears, configure this setting on General tab > Process Via dropdown > TRI
option. Users should enter and verify any additional fields for needed for this setting and finalize by clicking on
the Save button.
New TRI IngeDog integration on eCommerce
This enhancement has also integrated TRI credit card processing on the eCommerce application. The new settings
can be located on the [server] section of the in_system.INI as follows:
[Server]
cardDogdirect= qa.carddog.com:46010
carddogtimeout = 20
carddogterminalid = 0033333333330003
Warning prompt added for Auto Scan changes
In some cases, when users change the Auto Scan dropdown on the Account dialog, vouchers may link to the
incorrect invoice. Vouchers that are linked to the incorrect invoice can create accounting variances. This
enhancement displays a warning prompt to users when an invoice is changed on the Auto Scan dropdown located
on the Invoices tab on the Account dialog. The prompt asks the user to verify and save the changes.
Note: The warning prompt only displays if the user changes the Auto Scan value and if the value was previously
set to a value other than 0.
Changes to Ticketing
New promo code data ability for Sales screen action macros
Promo code data can now be injected into client databases via Sales screen action macros for reporting purposes.
This ability includes source codes and marketing codes. To implement this functionality, macros must be set up
with the promo codes in specific positions based on the type of special.
Configuration
For SPECIAL and ITEMSPECIAL promo codes, use fourth position in the command for source code and fifth
position for marketing code. For SELECTIVESPECIAL and GLOBALSPECIAL, the source code is in field two
and the marketing code is in field three. If an invalid source or marketing code is passed, the Special is not set and
the promo code data does not write to the database. In addition, the "Source code required to apply this special"
and/or “Marketing code required to apply this special” check boxes need to be populated appropriately on the
General tab located in SysManager > Activities > Financial Lists > Specials dialog.
The examples below illustrate how to draft macros that tell the promo codes to write to the data:
<ISWEB>SPECIAL("MACROSPEC",0,0,0,LOCAL)SELECTLAST()FORCEFINALIZE()</ISWEB>
<ISWEB>SPECIAL("MACROSPEC",0,0,MEMBER)SELECTLAST()FORCEFINALIZE()</ISWEB>
<ISWEB>SPECIAL("MACROSPEC",0,0,MEMBER,LOCAL)SELECTLAST()FORCEFINALIZE()</ISWE
B>
<ISWEB>ITEMSPECIAL("MACROSPEC",0,0,0,LOCAL)SELECTLAST()FORCEFINALIZE()</ISWEB
>
<ISWEB>ITEMSPECIAL("MACROSPEC",0,0,MEMBER)SELECTLAST()FORCEFINALIZE()</ISWEB>
<ISWEB>ITEMSPECIAL("MACROSPEC",0,0,MEMBER,LOCAL)SELECTLAST()FORCEFINALIZE()</
ISWEB>
<ISWEB>GLOBALSPECIAL("MACROSPEC",0,LOCAL)SELECTLAST()FORCEFINALIZE()</ISWEB>
<ISWEB>GLOBALSPECIAL("MACROSPEC",MEMBER)SELECTLAST()FORCEFINALIZE()</ISWEB>
<ISWEB>GLOBALSPECIAL("MACROSPEC",MEMBER,LOCAL)SELECTLAST()FORCEFINALIZE()</IS
WEB>
<ISWEB>SELECTIVESPECIAL("MACROSPEC",0,LOCAL)SELECTLAST()FORCEFINALIZE()</ISWE
B>
<ISWEB>SELECTIVESPECIAL("MACROSPEC",MEMBER)SELECTLAST()FORCEFINALIZE()</ISWEB
>
<ISWEB>SELECTIVESPECIAL("MACROSPEC",MEMBER,LOCAL)SELECTLAST()FORCEFINALIZE()<
/ISWEB>
In these examples, MACROSPEC is the special name, MEMBER is the source code and LOCAL is the marketing
code. In the case of eCommerce sales and the use of <ISWEB> tags, FORCEFINALIZE is set to ensure that the
promo code(s) writes to the data. The feature adheres to existing logic related to the application of Specials.
When using SELECTIVESPECIAL commands, the associated special must be added as a Special for This Item
on the Specials tab of the Activities > DCIs > Item dialog.
Note: An item must be finalized before the code(s) are written. When using classic Sales screen action macros, the
<ISWEB> tags and FORCEFINALIZE command must be removed.
New reporting ability and country option added
When a customer does not have a ZIP code or postal code, some clients would like the option to collect country
information as part of a Sales transaction. This enhancement allows clients to configure Sales to easily capture
country information from guests and associate that data with specific reservation information in the same
manner that ZIPcodes are gathered. In addition, reporting can now be performed to compile demographic
information to better understand statistical data in relation to guest origins.
Sales
When an operator is prompted to enter a ZIP Code, they can now enter a: ZIP code, postal code or country name.
In addition, operators entering a country name are prompted to enter an autofill selection based on spelling.
Reports
A new SQL Server Reporting Services Report has been added called, Zip Collection Performance. The report details
guest responses to the Sales operator and inquiries about country of origin. This new capability offers a new level
of customer relationship management and data collection beyond capturing ZIP or postal code data.
New .INI setting added to reconnect to SalesEZ module
In previous versions, when an operator was disconnected by an inactivity timeout after a successful log-in, SalesEZ
did not attempt to reconnect automatically. This enhancement offers a new .INI setting to allow operators to
reconnect to the SalesEZ module after a disconnect or an inactivity timeout. This .INI setting is configured:
[Preferences]
CheckEzConnectionOnLogin=TRUE
When set to TRUE and the connection is disconnected, the SalesEZ module tries to reconnect on a successful log-
in. The SalesEZ module checks and respects the ReconnectThreshold and ReconnectInterval settings.
If the SalesEZ module detects an error while trying to communicate with the server, an error message dialog
appears. The error message presents the operator with an option to continue working offline or to try to
reconnect with the server.
Givex Gift Card support added for eCommerce sales and gratuity
Givex gift cards can now be used to:

• Purchase cards through eCommerce
• Use Givex gift cards as a form of payment through eCommerce
• Fusebox can process Givex gift cards as Pre-authorization / Capture as needed for gratuity in F&B
Note: The terminal identifier for gift cards may be different than the terminal ID for credit cards. Therefore, the
gift card terminal must be specified.
Configuration
Gift Card Terminal Procedure

The gift card terminal can be set one of two ways:
1. Modify settings in the ww_system.INI:
[Server]
GiftTerminalID = Givex
2. Passed in along with the settlement string:
<settlement>
<GiftTermID> RETAILIG </GiftTermID>
</settlement>
eCommerce Checkout
For access to the Givex gift card support in the eCommerce checkout pages, users should implement the following
new configuration settings:
<SiteConfig>
<Key>GivexInsufficentFundsMsg</Key>
<Value>Sorry, you do not have sufficient funds on your Givex Gift
Card for this sale. Please try another form of payment.</Value>
<Description>Set GivexInsufficentFundsMsg to the text that should be
displayed when a user attempts to use a Gixex Gift Card, but has
insufficient funds.</Description>
</SiteConfig>
<SiteConfig>
<Key>GivexLabel</Key>
<Value>Pay with Givex Gift Card</Value>
<Description>Set GivexLabel to the desired label to appear on
Checkout.aspx to enable this payment type.</Description>
</SiteConfig>
<SiteConfig>
<Key>GivexPayment</Key>
<Value>1</Value>
<Description>Set GivexPayment to 1 to enable a checkbox on
Checkout.aspx that allows paying with a Givex Gift Cards. Note, this is
available through Elavon's Simplify solution.</Description>
</SiteConfig>
<SiteConfig>
<Key>GivexGiftTermID</Key>
<Value>RETAILIG</Value>
<Description></Description>
</SiteConfig>
Gratuity
To enable functionality to process a pre-authorization or to capture for gratuity, add the following to the
Sales32c.INI:
[Preferences]
GiftCardTips = TRUE
Improved performance of historical Max4Sale data
Some clients may experience performance issues in Sales applications when historical Max4Sale data records
are not deleted. This enhancement reflects changes with the Max4Saleopt index which vastly improves
processing times for specific database calls. Clients selling quantity restricted items and yielding large numbers of
Max4Sale records now experience improved performance on Sales and eCommerce modules.
Added Access Control preference for processing trickled scans
Some client scenarios create the need to scan tickets in trickled (offline) mode. By default, the Sales application
validates records for all invalid trickled scans. This enhancement gives users the ability to set Access Control
preferences to record trickled scans as invalid records.
Configuration
Users can modify trickled scans default settings by updating Access Control Preferences settings in SysManager.
Configure changes by locating the check box on the Preferences description > Access Control button, which opens
the Access Control Preferences dialog and presents the Do not process validations on invalid trickled (offline)
scans check box. The check box must be checked to bypass validation on records for trickled scans.
Note: The Do not process validations on invalid trickled (offline) scans check box is unchecked by default.
New import feature
SysManager offers a new Import Access Numbers utility, which allows users to generate new Access Records from
ticket numbers in either a .CSV (text) file or as a user specified range. Users can access this utility configured in
SysManager > Utilities > Data Maintenance > Import Access Numbers button.
Ticket numbers are populated on new Access Records either on the swipe_no column or one of the addit_no
columns. The Import Access Numbers utility validates that ticket numbers in the specified column have not been
previously added to existing Access Records and are unique within the specified import file.
Changes to ww.dll
New available inventory function added
To improve retail tracking for items, this enhancement shows available inventory to users that have enabled
tracking items. The functions <getitemexpanded> and <getitemtree> display tracking results.
Note: To enable this functionality, users must verify that the tag <tracking> is included in the function call.
Known issues
For a complete listing of Known Issues, please visit our KI page. Issues are sorted by general software version
number.
Fixes
US# Release Notes Application Version

Resolved issue which caused the Export Service
application to time out and mark the access records to
indicate that the revenue move was completed
successfully when these records were not updated.
The Export Service application now has a web
interface which identifies how the functionality is
being executed. This capability can be set on:
[Preferences] Accounting
21897
MiniHttpServerPort=8082 Export 4603_01001
When a browser is opened to localhost:8082,

options are displayed to:
• Export Job Activity - For last day / 7 days / 30 days
• Export Job Status - Shows when each job was last
run
• Revenue Recognition Activity - For last day / 7
days / 30 days
• View/Reprocess Revenue Recognition
The Reprocessing of Revenue Recognition allows

querying the database to see activity in the past for
different statuses and selecting items to reprocess
through ww.dll. The results are recorded in a
special log file and export jobs now have a
configurable timeout, which can be set as follows:
[Preferences]
ExportJobTimeoutSeconds=300
Note: The timeout default is five minutes and it also

applies to the query that is used to retrieve the
records that require revenue recognition.
The web interface now allows for dates to be entered

for researching revenue recognition. The number of
records that are returned is set at a default of 5000
and can be modified. In addition, users have the
option to enter a pass number and get details only for
that specific pass. The date for recognizing
transactions defaults to the current day, but users may
also specify an alternate date. The log file is
generated while reprocessing is occurring to serve as a
running record of what has been processed.
The following issues have been resolved:

• Problem with large guest numbers causing
mug_shots to not be sent
• Bug with a guest number that did not exist in the
_ax_transactions table, which prevented
photo updates (and reloads) until the record was Axess
25412
cleared DataSynchronizer 4603_01002
A setting has been added for MaxPictureBytes

with a default of 50000. If the picture that is
retrieved is over this threshold, the default picture is
sent.
Clients using a French target system on Windows 10

no longer experience the issue that prevented the
23189 Common File
modifydacl.exe function from using correct 4603_01001
group permissions.
Retail tracking items now show how many items are

remaining and prevents sales from being performed
when the available inventory is less than the quantity
6490 selected. eCommerce 4603_01027
Note: ww.dll 4602_01013 or later is required.

A bug preventing the display of the programmed long
9978 description on the item show pages has been eCommerce 4603_01027
resolved.
Fixed duplicate error that would appear intermittently
15115 when user attempted to add new guest. The new eCommerce 4603_01027
guest now saves and page does not display errors.
The Middle Name field on the Guest Edit dialog now
18109 eCommerce
retains and displays the field value without any errors. 4603_01027
Fixed an issue that prevented operators to set a guest

20386 when using the Family Pass Package caused by eCommerce 4603_01027
transposing of the previous guest number.
Resolved an issue with items added on Sales
applications using the SELECTITEM macro. After the
20999 eCommerce
user clicks the Remove button, the primary item and 4603_01027
SELECTITEM are removed from the cart.

An issue that prevented real-time inventory quantities
21883 from being displayed on eCommerce pages is eCommerce 4603_01027
resolved.
Promo codes now calculate discounts correctly when
22120 eCommerce
applying a special to a sales item. 4603_01027
Items that are on a pricing schedule and configured via

22209 LeadTime now display the correct price on eCommerce 4603_01027
ItemList.aspx and Itemshow.aspx.
Resolved the issue that prevented a phone number
22376 added to the Phone2 field from displaying on eCommerce 4603_01027
GuestSelected.aspx and GuestEdit.aspx.
An issue that caused guest credit card information to
be removed from the guest profile when changes
22764 eCommerce
were made on the GuestEdit.aspx page has been 4603_01027
resolved.
An issue has been resolved that prevented the ability
22985 to set a guest on items with modifiers attached when eCommerce 4603_01027
using mobile themes.
Points4Sale items now display accurately and the
23030 Quantity dropdown now shows on the ItemShow eCommerce 4603_01027
page.
eCommerce pages now display a clear indicator as to
23088 eCommerce
when a promo code is applied. 4603_01027
23205 Promo codes now apply the correct discounts. eCommerce 4603_01027
The error that occurred when charging to account on
23333 eCommerce
CheckoutSteps has been resolved. 4603_01027
When editing purchaser information upon checkout,

required fields specified in
23562 PurchaserForceEditFields now display eCommerce 4603_01027
consistently. Redundant purchaser requirements from
Checkout and Checkout2 have been removed.
CartShow.aspx does not crash when the Guest
23588 eCommerce
Lookup and Member Login pages are used. 4603_01027
When PopUpGuest=1, the Guest dialog only pops

23636 up on the desktop and remain disabled on eCommerce 4603_01027
mobile/tablet devices.
Pages accurately display multiple liability forms
(including pending forms) for new or existing guests.
23644 eCommerce
Each guest is prompted to accept liability based on 4603_01027
liability expiration.
Inconsistent API calls are no longer produced
23775 intermittently when MultiAddITGroups and eCommerce 4603_01026
Max4Sale are enabled.
Itemshow.aspx no longer crashes when an item is
23803 eCommerce
selected on Itemlist.aspx. 4603_01027
Fixed logic problems that prevented modifiers from

24205 eCommerce
inheriting guest information during checkout. 4603_01027
Capacity based Points4Sales pricing now calculates

24209 correctly on the eCommerce MultiAddITGroup eCommerce 4603_01027
view.
Fixed the display of the long description for package
24220 eCommerce
items. 4603_01027
Resolved an issue that caused the second level

24229 eCommerce
modifier to display first level modifier price. 4603_01027
An issue has been resolved to allow acceptance of

24333 liability forms for minors and added customization eCommerce 4603_01027
options.
Web Pages now include <taxa> and <taxb> tags at
24506 eCommerce
item level. 4603_01027
Correct dates now display when users are switching

24642 back and forth between calendarview.aspx and eCommerce 4603_01027
itemshow.aspx.
Credit card numbers are now able to be saved and
update on checkout.aspx after operator checks
24828 eCommerce
the existing Credit Card On File check box and then 4603_01027
deselects the check box.

A bug that prevented items from displaying on the
24936 ItemList.aspx when using Max4Sale and eCommerce 4603_01027
ListView has been resolved.
Fixed an issue with parsing macro arguments that
25791 prevented specials from working with do_on_web eCommerce 4603_01027
macros.
The Export Service application now correctly processes

21835 Export Service
values that contain comma and carriage return. 4603_01001
The issue that caused both the originally scanned and

21957 exchanged tickets to incorrectly move remaining Export Service 4603_01001
balances after ticket expiration has been resolved.
The MoveRevenue revenue recognition rule now
23308 Export Service
correctly moves revenue. 4603_01001
PrintEZ now starts without displaying the error

Message, “Unable to create instance of PrintEZ -
Unable to load PrintEZ. Unspecified error” in the Sales
application. The PrintEZ application error, “Expression
is not valid outside of WITH/ENDWITH. Error# 1940
20791 Method:write_log Line: 2484” has also been resolved. PrintEZ 4603_01062
Note: If the error occurred while attempting to print,

delete the Printing.dbf file from
C:\ProgramData\Siriusware\Sales\Data\
and restart the Sales application.
Unknown Error 199, “ExecuteScalerSQL returned more

than one row” no longer occurs when the rental item
18482 RentEZ
is an *UNLIMITED* type and level that is exchanged 4603_01006
for a different type of rental equipment.

Fixed issue with the Rentals TechStationPC item
19040 generating an unresponsive window when RentEZ 4603_01006
communicating with the RentEZ application.
The Rentals TechStationPC item now limits the
19054 RentEZ
instance name textbox to six characters. 4603_01006
Fixed crashes that occurred when the Rentals

19661 TechStationPPC item received data from the RentEZ RentEZ 4603_01006
application.
Fixed an issue that occurred when an operator

Reporting
25477 refunded within a reservation, which prevented
Services 4603_02001
revenue from adding up correctly.
A Pass Info Error no longer occurs when voiding a line

item from a recalled saved sale or reservation when
17973 Sales
using Standard Validation or Benefits and Redemption 4603_01062
Validation.
Fixed issue with tax amount being recorded incorrectly
18865 on the Web Sales Host utility for items with a quantity Sales 4603_01062
of two or more.
The DCI dropdown on both the Recall Sale and Item
18956 Availability dialog now lists all the departments from Sales 4603_01062
the Item Tree on the salespoint.
When splitting payments with credit cards, the
19285 Simplify Pinpad now correctly displays the amount Sales 4603_01062
being charged to card instead of the sale total.
When the Sales application is configured with Sticky
List functionality, entering oversell credentials no
20104 Sales
longer results in a return to the top node of the Item 4603_01062
Tree.
The ability to select all reservations on the Recall
Reservations dialog now exists, which allows
20129 Sales
operators to bulk finalize with greater ease and fewer 4603_01062
clicks.
Fixed issue with the recall reservation functionality
that occurred when using a DCI filter. The date now
20180 Sales
displays correctly when the date format for the 4603_01062
salespoint is set to Canadian format.

Discount Point4Sale tracking now accurately
calculates remaining inventory and allows clients to
20225 Sales
manage their yield by limiting the sale of items via 4603_01062
discount point tracking.

Fixed an issue that caused an, “Out of Memory” error
20304 Sales
to display for operators using inter-linked modifiers. 4603_01062
The issue that occurred when reloading or selling a gift

card using Simplify Pinpads and caused the Sales
20429 Sales
application to pause between gift card swipe and 4603_01062
credit card swipe on the Pinpad has been resolved.

The issue that prevented the operator from clearing
the Pinpad Transaction Timeout dialog has been
resolved. The Sales application now continues to listen
20499 to Simplify Pinpads with IP connection until end of Sales 4603_01062
transaction is found or timeout occurs. The default
time out for this functionality is 120 seconds, but may
be changed on the following .INI setting:
[Simplify]
timeout = 120
Sales no longer crashes when and auto-renew item is
20664 Sales
paid prior to the scheduled payment date. 4603_01062
The issue that occurred when attempting to recall a

sale that contained items outside of the local Item
20719 Sales
Tree and caused the Reservation Header to incorrectly 4603_01062
link with a different reservation has been resolved.

Partial credit card payments are no longer allowed
when finalizing a reservation and the operator is now
20822 Sales
alerted if the final payment on a reservation is not 4603_01062
approved for the full amount.

The Web Sales Host utility now processes Family Pass
20877 Sales
Program items without any errors of last name. 4603_01062
Fixed an issue that occurred in the Web Sales Host

utility that caused an, “Encountered Improper
Argument” error when processing a Sales transaction
20903 Sales
that used 1Risk liability forms with a pass quantity 4603_01062
greater than one. The multiple quantity functionality

now works correctly.
Fixed an issue that caused the Web Sales Host utility
20987 Sales
to hang when processing regular items with modifiers. 4603_01062
The Web Sales Host utility now correctly processes

20997 regular items with modifiers that does not require Sales 4603_01062
guest to be attached.
Sales now works properly with large databases and
21009 Sales
returns guest number data accurately. 4603_01062
The Sales32c.INI Preferences setting,

ForcePhotoCheckWithPhotoAxessLayout
21171 Sales
now prevents encoding of the RFID card and no longer 4603_01062
prevents pass finalization.

The guest item user defined fields 1 and 2 are no
21335 longer cleared after users click the Get From Self Entry Sales 4603_01062
button.
After the Web Sales Host utility declines a credit card
21829 via Fusebox code 0600, a transaction inquiry is now Sales 4603_01062
performed to verify if the transaction was successful.
When expired passes are exchanged, Sales applies
21882 credit for the original item purchase price rather than Sales 4603_01062
the current item price.
A bug that prevented a Membership Renewal item
from correctly updating the expiration date for a
21953 Sales
renewal product has been resolved. Sales now 4603_01062
performs the renewal for the validated pass.

The pass renewal item now accurately extends the
21965 expiration date after the renewal item is saved, and Sales 4603_01062
then finalized.
Operators using Sales version 4.5.04 and up now have
the ability to select a range of recalled reservations
22069 Sales
using the Select All check box in the Recall > Review > 4603_01062
Recall Reservation dialog.

Direct pricing for items that are saved and recalled
22146 Sales
now retain the last changed price. 4603_01062
In a pass renewal, cstrt_date now runs properly

when a renewal is performed after the pass has
22166 Sales
expired. The date writes as the current day rather 4603_01062
than the day after the pass expired.

Partial credit card authorizations on a saved sale no
22215 Sales
longer reverse automatically. 4603_01062
The ZIP code column now populates with CANCEL

22224 when the operator cancels out of the Zip Code Sales 4603_01062
Collection dialog.
The issue that prevented the payment plan from
canceling automatically after the operator processed a
22229 Sales
refund for a pass on a payment plan has been 4603_01062
resolved.
Items configured with the Prevent sales when no
22641 limits are set functionality are no longer shown as Sales 4603_01062
available on the Modifiers dialog.
Voice authorization failure that occurred when using
Simplify has now been resolved. Offline Simplify
22940 Sales
transactions that require voice authorization are now 4603_01062
forwarded correctly.
The issue that caused the Pinpad to freeze has been
22381 Sales
resolved. 4603_01062
New tokens can now be created and stored using

23235 Sales
CardDog and Simplify items. 4603_01062
The issue that prevented ticket auto-selling from

23267 Sales
working in Sales has been resolved. 4603_01062
Resolved the issue that caused the Web Sales Host

23570 utility to crash when attempting to cancel a Sales 4603_01062
reservation.
Issues that caused reprocessed payment plan failure
23843 Sales
and partial payment reversal have been resolved. 4603_01062
When using the PaymentExpress item, the card

23909 number now displays as a token rather than credit Sales 4603_01062
card number with middle digits crossed out.
The correct FuseboxChainCode, location and
23931 terminal ID are now used when sending a transaction Sales 4603_01062
inquiry on Web Sales Host utility transactions.
When using Simplify Pinpads, tip records are now
23939 Sales
recorded to the correct credit card type. 4603_01062
Partial credit card payments are no longer allowed

23944 when finalizing a reservation and is automatically Sales 4603_01062
reversed.
When using Simplify Pinpads with an IP connection,
instead of closing the dialog box, the Close Dialog
24181 Sales
button on the Pinpad status dialog now sends a, 4603_01062
“cancel” message.
When users attempt to reprint Axess Passes, the
24196 Sales
printing record now populates correctly. 4603_01062
Removed batch close functionality from Simplify

24221 Sales
Pinpad solution. 4603_01062
The printing table is now populated with proper

24422 information when an operator performs a guest Sales 4603_01062
lookup.
When tablet enhancements are added, this no longer
24434 Sales
breaks screen layout. 4603_01062
To determine the status of the transaction, Fusebox,
ProtoBase and Simplify transaction types now perform
24466 Sales
a transaction inquiry if a message of, “DUPLICATE” is 4603_01062
received during the initial credit card transaction.

Credit card processing is not forced offline when there
24528 is no response from the Pinpad and Sales 4603_01062
ForceCCOfflineOnTimeout is set to TRUE.
When Sticky List is enabled, an items folder with over
thirty Max4Sale items (located on the second page
24545 of the folder) now display on the same page. When an Sales 4603_01062
item is selected from the second page of the folder,
the second page continues to display.
RFserial numbers are now issued only when the media
24632 is encoded as the original design worked and required Sales 4603_01062
by Axess.
Reserved Seating pages now update values accurately
24637 Sales
and account for different date formatting. 4603_01062
Purchases made on stored tokens now show the

correct credit card type in the cc_trans table. The
correct credit card type displays on the speed dial
24761 Sales
buttons that are located on the Finalize dialog and on 4603_01062
the Purchase Correction dialog after a stored token

has been used for purchase.
An issue that caused Sales to check for an incorrect
24762 item_type value when selling Reserved Seating Sales 4603_01062
items has been resolved.
When using Simplify Pinpads, when an operator
24838 presses the <enter> key, this action no longer force Sales 4603_01062
closes the Pinpad Status dialog.
Sales now attaches a guest profile to globally validated
24938 Sales
items. 4603_01062
Resolved an issue that prevented the Start Contract

process when any item in the sale requires a liability. A
24946 Sales
new .INI setting was added, 4603_01062
RequireLiabilityOnContract.
Note: The default value is TRUE. When set to FALSE,
users have the ability to start rental contracts before
the liability is accepted.
When recalling a reservation that uses AutoRecall
25021 Sales
settings, the reservation Notes prompt now appears. 4603_01062
RFSerial numbers now match the POS number of the

25037 encoding salespoint and reverts functionality to issue Sales 4603_01062
RFSerial numbers at the time of encoding.
Resolved the error that caused prompt, “mug_shot
does not accept null values errors in Sales”. Sales now
25081 handles guests who do not have a mug_shot by Sales 4603_01062
adding the mugshot from an alternate salespoint and
then validating the original salespoint.
The Item Select dialog on the Classic Kiosk now
25163 Sales
displays correctly. 4603_01062
The Web Sales Host utility no longer sends a

25251 transaction inquiry when gift card transactions using Sales 4603_01062
Fusebox return an error of, “0060”.
The issue that occurred with the price of an item when
RecalculatePriceOnRecall was set TRUE, the
25320 Sales
operator recalled a sale with an item with a special 4603_01062
attached and added a modifier has been resolved.

Givex transactions that return an error of, “Post-Auth
25376 references invalid Pre-Auth” are now retried three Sales 4603_01062
times.
When a guest record is deduped in SysManager and
the record is updated in Sales before refreshing or
finalizing, the records are now merged correctly. If
the guest does not have a mugshot in the local sales
25415 data, the mugshot is removed from the server to Sales 4603_01062
prevent errors.
Note: When a user performs a dedupe in SysManager,
it is recommended that the user clicks Update or
Finalize buttons to refresh guest record data.
When a user adds an item to an existing reservation
25460 finalizes the record, a refund does not occur on the Sales 4603_01062
customer credit card.
Fixed an issue that occurred when a pass with on-the-
fly discounting and an item using validation were
25565 processed in the same sale, which prompted Sales to Sales 4603_01062
continually attempt to validate until the application
crashed.
A bug caused Sales to crash when trying to run
salesclib.exe has been fixed by adding a new
26410 diagnostic tool. This tool allows users to verify that Sales 4603_01062
Sales can connect and is located on Sales > Tools >
Diagnostics > ConnectSalesCsLib.
SeeBooks application:
• No longer displays the note icon if no scheduler
note exists
20394 SeeBooks
• Can edit the start and end times of the schedule 4603_01001
and the content of the right click menu
• Long press functionality now works again on
mobile devices
The Keep me logged in check box on the

Login.aspx page now functions as designed and
19994 SeeBooks Online
improves the interface when looking up schedules via 4603_01001
a mobile device.
Added timeout setting to resolve issue with

22071 ExternalLiability.aspx timeout that Self Entry 4603_01002
occurred after one minute.
When a defined benefit has the number of

redemptions defined as one of the Autosale Max Qty
levels, the calculated quantity now respects the
Customize this Quantity option on the Pass Template
18968 SiriusSQL
setup. When this option is checked, the quantity is 4.6.03.01007
derived directly from the guest pass record. If this

option not checked, the quantity is derived from the
pass template.
To resolve errors that occurred when purging guest
credit cards on file, two new sp_log log activity type
calls have been added:
20878 SiriusSQL 4.6.03.01007
• 2175: Pruned all Guest Credit Card numbers on file
• 2176: Pruned all Auto Payment Card numbers on
file
The error that occurred with
24636 SiriusSp_rsGetBestAvailableSeats due to SiriusSQL 4.6.03.01007
collation issues has been resolved.
Items and template settings for all non-hidden item
blackout showing ending date values for end of day
25242 SiriusSQL
(11:59:59 PM) are no longer incorrectly set to the 4.6.03.01007
beginning of the day (12:00:00 AM).
The issue tied to deleting seat blocks has been

resolved and new alert messaging has been added.
24837 SysManager
Seat block management functionality has been 4603_02002
improved on the Reserved Seating module.

Resolved issue that prevented purging for
automatically renewed payment cards on file by
17174 adding the Prune All Auto Payment Cards On File SysManager 4603_02002
button located in SysManager > Preferences >
Miscellaneous Preferences dialog > PA-DSS tab.
The SysManager launch error, “Database version is
20794 newer than expected” has been resolved and now SysManager 4603_02002
accurately displays the updated database version.
Fixed the issue with DeDupe Data which caused an
23681 SysManager
error to appear and SysManager to crash. 4603_02002
An issue related to the Reserved Seating pages not

24638 displaying properly when setting up productions and SysManager 4603_02002
shows has been resolved.
Reserved Seating is now refined in terms of speed and
overall functionality, which includes:
• New rows on Changes in Venue Configuration
24839 SysManager
form into rsTemplateSeats when new blocks 4603_02002
are created
• Default values for CenterMost and Sequencing
columns when adding a new block
A bug that disrupted item and access template end
24962 SysManager
dates has been resolved. 4603_02002
When the liability form_no is greater than seven

25321 characters, it is now displayed properly in SysManager 4603_02002
SysManager.
When using the full option with AVS/CVV checking,

20566 the user no longer sees the error message, “Unable to ww.dll 4603_01020
Find Payment Type”.
The ww.dll module no longer requires supporting
.dll files to be in the same directory as the
23313 executable file. ww.dll 4603_01020
Note: New installers are required.

24008 Points4Sale now works with avail_detail. ww.dll 4603_01020
The correct price is calculated for an item with
24219 multiple liability forms when the quantity is greater ww.dll 4603_01020
than one.
Credit cards that are declined under Fusebox or
24444 ww.dll
ProtoBase now display error messages correctly. 4603_01020
When performing a transaction inquiry, the correct

24476 ww.dll
reference number is sent to Elavon. 4603_01020
The authorization code created with Givex pre-

25285 authorization are longer included in the post- ww.dll 4603_01020
authorization transaction.
The issues that caused sale_text to fail in the Web
25882 Sales Host utility and @SaleText to appear in data ww.dll 4603_01020
have been resolved.
Copyright
Copyright 2017 accesso Technology Group, plc. All rights reserved.
NOTICE: All information contained herein is the property of accesso Technology Group, plc. No part of this
publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any
means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of
accesso Technology Group, plc. 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 accesso Technology Group, plc. accesso Technology Group, plc. 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.

2017 03 Software Update 03 For 4.6

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

2017 03 Software Update 03 For 4.6

Diunggah oleh

Hak Cipta:

Format Tersedia

Salesware Update: Version 4.6.

03 Release Notes (03/01/2017)

4. Click the Download button

5. Select the check box for EN\x86\DacFramework.msi.

4. The C:\Windows\system32\cmd.exe dialog now appears.

6. Move the new 4.6.03 application update files to the SiriusFS\Updates or

The following services do not update automatically:

Updating the ww.dll

1. Open a Command Prompt.

Steps to update eCommerce pages

Please read the below instructions carefully!

Step 1: Preparing for the Update

Note: Do not download the Ecommerce_Pages _Config_4603_01025.exe file.

Step 2: BIN update

1. Delete all the files in the c:\inetpub\ecommerce\BIN folder

Step 3: New files to be added

\App_Themes\themeName\bootstrap\ - (and all children)

Remove the Calendar folder and all contents.

Step 5: Replace Files

Step 6: Changes to Files

MasterPageThemeName.master (if this file is not already present)

MasterPageThemeNameMobile.master (if this file is not already present)

Step 8: Restart the Site

2. Open the command prompt and type IISRESET

What’s new in accesso Siriusware version 4.6.03

Scope and audience

Components in this release

Note: accesso uses official release version designations.

Component 4.6.03 Update Number

Changes to Access Control

Additional blocking reason added to Axess for voided passes

New GateKeeper .INI settings and functionality

Fingerprint sensor now enabled

Note: The default setting is FALSE.

Added functionality for operator data

New Axess printer functionalities

New port option on Axess Smart Printers

BatchPrint utility updated to support AxCoding

New SETPARENTACCVAL and CHANGEACCVAL macros for access table

New SOLDDATE() macro and Dynamic Pricing capabilities

Note: When an item is configured for capacity controlled pricing:

New Dynamic Pricing Rules

New eCommerce Calendar module available

Note: the eCommerce Calendar is a separately licensed module.

Calendar module settings

New notifications for Web Sales Host utility errors

Updated Instructions folder removed from eCommerce

Changes to Food Service

Room charges now reversible in Table Service F&B module

Ability to remove scanned barcode prefix

Improved auto-renewal formatting

New BLACKOUT macro and pass blackout functionalities

New BLACKOUT macro added for individual blackout dates on passes

Added option to prevent blackout date pass printing

New .INI setting to prevent printing a pass with blackout

CHANGEPASSVAL and SETPARENTPASSVAL macros newly added functionality

Added capabilities on GLOBALSPECIAL and SELECTIVESPECIAL macros

Added guest user-defined fields on BatchPrint utility

Additional CityPASS enhancements:

• CheckPass, ValidatePass, CheckAndValidatePass and TricklePass now supports

Note: These enhancements support CityPASS only.

New reporting services for passes near expiration

New fields on the View Item Detail Report