RetailSTAR Version 10.1 is a release of the latest update to the RetailSTAR product.

Transcription

1 RetailSTAR Version 10.1 Release Notes 2/12/2016 Contents Introduction... 1 Before Installation... 1 i.star ecommerce Sites... 2 Security... 2 Please Note... 2 New Features... 4 Enhancements... 4 Issues Modified... 6 Introduction RetailSTAR Version 10.1 is a release of the latest update to the RetailSTAR product. RetailSTAR Version 10.1 is compatible with the Windows Vista, Windows Vista Business, Windows Vista Enterprise, Windows 7 Pro, Windows 8.1 Professional 64 bit, Windows 2008 Server R2, Windows bit, and Windows Server 2012 operating systems. RetailSTAR Version 10.1 upgrade requires the user to be on Version or higher prior to upgrade. Before Installation Please familiarize yourself with the contents of these Release Notes for details regarding this release. This upgrade will attempt to perform a backup to the database. All users must log out of RetailSTAR and the SQL engine must be stopped from running. Note: If running RetailSTAR 10.1 with a multi-core processor, you may notice performance issues if the "Gupta Sqlbase Server1" service is not set to interact with the desktop. If this is the case, you must manually set the database engine service on your RetailSTAR server to interact with the desktop and restart this service. This setting will revert after an upgrade or service pack installation. To enable SQLBase to interact with the desktop: For Windows Vista Click on the Start button, then click on Control Panel. Double-click on Administrative Tools and then double-click on Services. Right-click on Gupta SQLBase Server in the list, and select Properties from the pop-up menu. Click on the Log On tab and make sure the Local System account radio button is selected. Make sure the database engine is shut down, and then create a hard drive backup of the data. This is usually a process that should occur on a nightly basis; however, open files like the database (pos.dbs file) are not backed up if the engine is running. This will ensure that a restore can be conducted if something fails during the upgrade. NOTE: Failure to have a current backup on an unsuccessful upgrade may cause a loss of all your data! -1-

2 During the upgrade: You will be prompted to halt the upgrade if you have an i.star store and you have not coordinated the upgrade with the i.star team. You will be given the option to start the Getting Started Wizard when rebooting the system after the initial upgrade. Accounting Users - Prior to upgrading: Prior to upgrading, users need to run Daily Process (select to Process Receivers) and Post to GL to import unprocessed receivers and post unposted receivers created in the old version. This is because key tables and fields have been replaced or modified in the new Purchasing and Receiving system. i.star ecommerce Sites If you are an i.star customer, your i.star server (hosted at the CAM facility) must be upgraded concurrent with upgrading your store systems. Please contact the i.star Support Department to coordinate this effort. Security New features are automatically available only when logged in as the system account. All other users must have the rights granted to them in Maintenance> Employee/Security before the options will display in the RetailSTAR menu. Security is enhanced by the folder install/upgrade paths now utilizing the Documents and Settings/All Users/Application Data area. This makes it unnecessary to give users access to write to the root C:\ drive as reports, etc. will be written to that area instead. (13302) Please Note RetailSTAR Version 10.1 requires a minimum of Version to upgrade. During an upgrade to Version 10.1, a window will display listing the new options available that will require password access and you will be able to decide which to employees you want to grant access to the options. On a fresh installation of RetailSTAR Version 10.1, a Star folder will install under the Local User as well as All Users under Application Data for future use. C:\RetailSTAR holds all of the program files, the document folder, pictures, Gupta, etc. C:\StarData holds backups, communication files, temporary files, and the training database. RetailSTAR will no longer install under Program Files. CODESOFT does not work with RetailSTAR Version Microsoft Office 2000 to 2007 is supported for use of the Mail Merge feature in Frequent Buyer Redemption. If you are running Windows Vista, an Internet connection must be running to install the help (.hlp) files properly (and silently) during the RetailSTAR install

3 Also included on the CD is a.msu file which can be used if it did not install properly from the RetailSTAR install or if you need to install the update at a later date. Its location on the CD is: <CD Volume>:\Utilities\Help for Vista. If the database is located in a subdirectory of the STAR folder, it gets moved to <same volume>:\stardata now regardless of the operating system. Example: RetailSTAR is located in D:\RetailSTAR Database is located in D:\RetailSTAR\POS Training Database is located in: D:\RetailSTAR\Training\POS If you have a training database that you want to preserve, copy it into a folder outside of STARData to prevent it from being overwritten during the upgrade process; then, upgrade the training database separately before moving it back in. (14262) If you post void a receipt that was tendered with a credit card using X-Charge, a message will now display stating that the credit card is invalid. This is because the credit card number is no longer stored due to the new credit card security. The receipt is voided, but you still must void the charge through X-Charge. If you have made any modifications to the standard ( canned ) reports in ReportSTAR, you must make a backup copy before upgrading to avoid losing your modifications. (14656) Version 5.1.x of the PDT software (STAR_PPCSetup.exe) is required if using a PDT other than the PDT3100 with RetailSTAR Version You must contact Support to install this for you. On a Windows 2008 R2 server, the.net Framework 3.5 must be installed before installing RetailSTAR. This is a known and documented problem with Windows 2008 R2. Even installing MS Visual Studio 2008 requires installation of the.net Framework 3.5 via Server Manager before it can be installed. See this link: If you have upgraded your FDW and FDL databases to , the following must take place before you can report on Corporate Sales in ReportSTAR. All FDL locations and the FDW must be upgraded to In order to upgrade the FDW database to include the new fields, the user must go to FDW Setup and use "F6-Sync DB". All previous FDL sales records will be deleted upon upgrade to Sales must be exported by the FDL at all locations and imported to the FDW. Old format FDL sales data files will be ignored by the new FDW. The following additional fields can be reported on in LOD for Corporate Sales Reports as of : Class, Class Name, Color, Color Name, Department, Department Name, Description, Fabric, Fabric Name, Item Key. SalesAssocID, SalesAssocName, Size, SizeCde, Style, SubClass, SubClass Name, Subsize, Vendor, Vendor Name. These fields that may still be reported on as in prior versions: DayofWk, Franchise ID, Franchise Name, Zip Code, YYYYMMDDD (Receipt Date). Additional Notes Just like in the normal Receipt Report, the total for the Number of Receipts (Rcpt) is only valid if the LOD is Franchise Id (Store No in Receipt Report). If the LOD is Item Key (UPC in Receipt Report), some receipts are counted multiple times because they contain multiple different items and the Total in the report is meaningless

4 If the Code/ID LOD fields (size code, fabric, department, style, etc.) included in the LOD do not exist at the FDW, they will be reported and identified as -UNK-. If the ID fields do exist at the FDW, but have a different name/description at the FDW, the name fields will identify them by the name at the FDW. Example: FDL and FDW may both have an employee 1-1. The corporate sales report will report for SalesAssocName based on the name of employee 1-1 at the FDW location. New Features 1) Rentals Rentals module allows the user to create rental plans with rental items along with fee tracking. Rental plans can be sold and returned in POS. 2) Menu Refresh The RetailSTAR menu has been redesigned including new icons. 3) CAM Utility Service Allows the functionality for Experian address/ validation service and allows functionality for Appriss ID parsing for Nplex. 4) Tax Templates Tax Templates module allows you to modify the rules of what tax ID gets applied to sales in POS. Enhancements 1) Pharmacy (Rx) a) Signature Maintenance/Reporting i) Added ability to search for and return a customer. (27351/ ) b) Chemical Tracking ID Selection i) Added ability to select an ID to attach to a chemical sale. c) Rx Controlled Substance ID Selection i) Added ability to select an ID to attach to an Rx Controlled Substance sale. d) Rx Scanning i) Added ability to use Rx manual entry when using a listening service. (27872) e) Rx Server i) Added prompting for controlled substances. (27369/ ) - 4 -

5 f) Reports 2) POS a) Discounts b) POS Errors i) RX Signature reports have been modified to filter and include/exclude sales which required ID for controlled substance. i) User can now set percent, dollar, or fixed type of discounts for Bulk Buy. (27536/ ) i) Increased performance in Print Register Balance query. (27993) c) POS Group Maintenance i) POS groups more efficient in how they use space. (27603/ ) d) POS Reports e) Returns f) Receipts 3) Pricing i) Added current and custom filters. (27995/ ) i) Added threshold amount when returning to a gift card. (27585/ ) i) Added new header options for Posted, Unposted, and Unposted with Balance. (26672/ ) a) Promotions 4) Purchasing i) New promotion types: Award and Match Group. a) PO Maintenance 5) Reports i) Added ability to create PO from file. a) Credit Card Query i) Updated module and report. b) Tax Summary i) Updated module and report

6 Issues Modified 1) AR 2.0 a) Statements i) Error message when saving Balance Forward statement. (27548/ ) b) Troubleshooting 2) EDI i) Improved performance on initializing. (27883) ii) Invoices clearing after paid in next statement. (27916/ ) iii) PO number showing up in statements. (27917/ ) iv) Transaction date for finance charges correct. (27729/ ) v) Can change account defaults. (27950/ ) a) Import/Export i) No duplication of PO when ordered for multiple stores. (27309/ ) 3) External Accounting a) Import/Export 4) Maintenance i) Export in balance with QB. (27937/ ) a) Case Templates b) Customer i) POS displays all quantities in case template when loading by style. (27975/ ) i) Customer search filters for customer if subsequent searches done. (27433/ ) ii) Icon and hint text are correct when launched from Customer Maintenance. (27945/ ) c) Frequent Buyer i) Correct frequent buyer points value for customer after frequent buyer voucher payment. (27836/ ) ii) Frequent buyer points do not get removed on post voids. (27909/ ) iii) Duplicate receipts in hold and save. (27976/ ) d) Time Clock i) Issue for one employee if two different employees clocked in at same exact time. (27903/ ) e) Transaction Fees i) Can void transaction fee on a hold receipt. (27754/ ) - 6 -

7 5) Office STAR a) Office Errors 6) POS i) Receipt reprint now shows same data as original. (27906/ ) a) POS Designer i) When creating invoice templates with different Bill To and Ship To names, the Ship To name is available as a field. (27440/ ) ii) Gift policy printed twice. (27904/ ) b) POS Errors c) Receipts d) Returns e) Tenders 7) Pricing i) Price Check Mode only allowed one digit to be typed in the field and scanning a barcode only brought up one digit. (27839/ ) ii) Cash drawer popped twice for gift receipt. (27912/ ) iii) Product search column customization issue. (27805/ ) iv) Receipt updates now check if length is more than 30+. (28028) i) Last name displaying when adding customer through POS. (26913/ ) ii) Multi-line function working for receipt policy. (27984/ ) i) Return receipt and return line work properly with kit items. (27921/ / ) i) Can void hold receipts containing pre-auth tenders using X-Charge Global account. (27854/ ) ii) Split tender preauth populated total instead of balance. (27868/ ) a) Contract Pricing 8) Purchasing i) Adding style to contract shows cost/retail. (27951) ii) Product description displays on contract screen. (27958) iii) Contract number displays on menu form. (27955) a) PO Maintenance i) PO report set to sort by anything other than by line, and with By Store as shipping group, still sorted by line. (27490/ ) ii) Line note spacing issue in reports. (27787/ ) iii) Product description missing in report. (27694/ ) iv) PO special order working for special orders created at another store. (26247/ ) b) Special Orders i) Store, OH, OO, and Cmtd fields can be edited/resized in Order/View Product screen. (27890/ ) - 7 -

8 9) Reports a) Best/Worst Sellers i) Numeric overflow due to case quantity. (27923/ ) b) Profitability i) An open PLU with a retail price of at least.01 in Product Maintenance shows as profitable on the report. (27985) c) Register Summary i) Report is correct when estimate/quote used at POS. (27950/ ) d) Report STAR i) OH value shows bucket OH value across all periods. (27580/ ) ii) $DISC was reporting negative values. (26866) - 8 -