Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Update Release Cycles 2004 - 2005
#1

RPRO 8 Older URC's/Update Release Notes/Bug Fixes (2004-2005)

  • Technician: Donna Knight
    Date:
    February 21, 2008

RPRO 8 Older URC's/Update Release Notes/Bug Fixes (2004-2005) 1

June 15, 2004. 1

October 27, 2004. 11

March 1, 2005. 17

March 23, 2005. 26

Update Release Cycle Retail Pro BTF-Series8.4/8.5/Tools. 26

March 23, 2005. 35

March 24, 2005. 37

Update Release Cycle: Retail Pro BTF-Series7.63/8.4/Tools/Plug-ins. 38

April 29, 2005. 42

Updated Release Cycle Retail Pro BTF-Series8.52/Tools/Plug-Ins. 43

May 2, 2005. 60

Update Release Cycle: Retail Pro BTF-Series8.52/Tools/Plug-Ins. 60

Update Release Cycles (oldest to newest)

June 15, 2004

Rpro v8.51 Core

Updated executables Contained in the June Rpro v8.51 Core update:

Core Files:

Rpro8.exe, RproDB.exe, Trans.exe, RProcIn.exe, Batch.exe

Tools:

~Bridge.exe, Auto.exe, DVS.exe, Reconstruct.exe, RproPI.exe


Issue ID:

14063

WebTAC ID:

25272, 25281, 25285

Area:

Rpro Update

Severity:

Critical

Title:

RPRO update gives Retail Pro version mismatch on 8.51 install

Description:

Running RPRO update on a 8.51 install and I got the error msg: "Retail Pro version mismatch. Please run RPRO to ensure that all files match the installed version. You may then re-run update" . This happens on ether on fresh installation or on upgraded install.

Resolution:

A change was made to Rprodb.exe to enable Rproupdate.exe to read the correct Rpro version number.


Issue ID:

13266

WebTAC ID:

19931

Area:

Vouchers

Severity:

Moderate

Title:

Would like functionality in ASN Voucher Batch Receive to allow scanning multiple packages at one time, without having to choose Select after scanning each package.

Description:

Would like functionality in ASN Voucher Batch Receive to allow scanning multiple packages at one time, without having to choose Select after scanning each package (like in 7 Series).

In 7 Series, users could scan several packages at once (if the package didn't exist it would warn them with a warning beep and a message) then they could update these ASN vouchers in one swoop by pressing end. In 8 series they have to select the package row then go to the assumptive find, then scan the package (if the item doesn't exit there is no warning it just remains on the last item selected) and then click on the select button after each item. The client is receiving hundreds of packages a day and this is really inefficient process as compared to the way they had been able to do this in 7 series.

Resolution:

In 7-series, it is possible to scan multiple ASN packages, and receive them in a batch receive. In 8-series, it was necessary to add the package numbers one at a time to the batch receive grid, which was much more time consuming for the customer. Functionality has been added to the batch receive area so that multiple ASN package numbers can be scanned in and received in a batch.


Issue ID:

13980

WebTAC ID:

4845

Area:

RproDB / ECM

Severity:

Critical

Title:

ECM > System needs a better way to tell you that RPRODB needs to run

Description:

After a polling cycle I HAPPENED to notice that there was a message that a critical preference was updated and RPRODB needs to be run. The system should either do that automatically or give a more visual warning. People do not generally look at the log every day and who knows what that critical preference could affect. When entering RPRO you should get a warning that RPRODB needs to be run because a preference has been updated by EMS/ECM

Resolution:

After data processed in from ECM changes key preferences, Rpro8 will now notify a user with the following message: "Updated key preferences have been received by ECM. Please launch RproDB to process them." This occurs upon logging in to Rpro8.


Issue ID:

14028

WebTAC ID:

In-House

Area:

Polling

Severity:

Serious

Title:

SecAdmin Updates are not processed in immediately

Description:

When SecAdmin Updates are processed in to an RPro Remote 2 behaviors occur.

If RPro is open the system immediately prompts for the user to relog in to RPro for SecAdmin updates to take affect. This behavior was supposed to be removed for bug 13651. The user should no longer be prompted to relog back in.

If RPro is closed when SecAdmin changes are processed in the system allows the user to log in. Two minutes after they are logged in the user is prompted to log in to accept the SecAdmin changes. Even if RProDB is run prior to login the changes are not accepted until 2 minutes after RPro is opened.

To replicate :

1>Create a main and a remote installation and initialize the remote

2>At the main in SECADMIN make a change to security such as adding a user and a group

3>Go into Polling> Stations> initialize> and select security for the remote (send groups and users)

4>At the remote process in through trans

5>Go into point of sale and wait.

You will be prompted to apply new security settings in a variable amount of time of up to 2 minutes.

This is a problem for large clients as there may be users at Point of sale making sales after these files are processed in. When the prompt comes up and the user (often a cashier) has to answer the prompt they may answer incorrectly or be confused by the prompt.

Security should be applied as soon as process in finishes and control is returned to trans. Security settings are being controlled and sent down from the main to remotes by larger clients and it is a certainty in most cases that the security settings should be applied user intervention or dialog.

Resolution:

Employee and Group Security changes that are polled to the remote sites were not being processed in immediately to SecAdmin by RProDB. Now when polling, since logins have changed the system will still request that you log off if you are signed in to RPro. However, once RProDB has initially run the system will check for updates immediately and then poll ever 2 minutes for changes. Previously it was just waiting two minutes prior to checking for changes. If RProDB is run while logged off the system all changes are then entered into the system and new users are able to log in to the system.


Issue ID:

14035

WebTAC ID:

Area:

Receipts

Severity:

Critical

Title:

QTY Pricing causes the price level to change on items in an Invoice even when the qty req is set to 0 in prices.

Description:

In V8.51 set your System Preferences>Point of Sales>Prices to Use Qty Pricing. In Inventory setup an item with different prices in 2 price levels. Make sure the Qty Pricing is set to 0 Qty Req for all levels for this item. Now add this item to an Invoice. Highlight the item and use F5 to change the price level of the item. Now add the item to the Receipt again. The price of the first instance of the item will change back to the original price level. This only happens with Use Qty Pricing selected. If this is not selected the first Instance will retain the changed price level.

Resolution:

If a price level is manually assigned (F5 or selecting the drop down list in the price level column), then that item is excluded from determining the quantity discount on another same item on the document.


Issue ID:

13943

WebTAC ID:

24252

Area:

Polling

Severity:

Moderate

Title:

Polling > Stations columns are not sortable.

Description:

Create several stations in Polling > Stations. Try to sort on any of the columns. It does not work as it has in 7 series. In 7 series all columns were sortable.

Resolution:

It was not possible to sort any columns when looking at the Stations list view in polling. This was a feature in 7-series, but was removed from 8-series. The standard Retail Pro sort buttons have now been enabled for all columns in the list view.


Issue ID:

13972

WebTAC ID:

24470

Area:

Credit Pro

Severity:

Serious

Title:

Credit Pro > Batch > Error occurs when you attempt to run batch in 7.63 "you are not licensed for this EFT type."

Description:

When you attempt to run Batch.exe (in a 7.63 installation only) when configured and licensed for Credit Pro you get the following error message: "You are not licensed for this EFT type. Select the type you are licensed for in Workstation Preferences.".

To reproduce:

Using a 7.63 install set your EFT type in Workstation Preferences to use Credit Pro.

With the latest Credit Pro updates, including the latest Windows Batch.exe, run the Batch tool.

When you run batch.exe you will get the error message: "You are not licensed for this EFT type. Select the type you are licensed for in Workstation Preferences.".

Resolution:

Batch.exe was assuming that 7 series users were using PPM. Now it checks the 7 series setting that specifies the EFT type (which is different from the 8 series setting). We now allow the user to set the server workstation number if the EFT type is Credit Pro.

Rpro v8.40 Core

Updated executables Contained in the June Rpro v8.51 Core update:

Core Files:

Rpro8.exe, Trans.exe, RProcIn.exe, Batch.exe

Tools:

~Bridge.exe, Auto.exe, DVS.exe, Reconstruct.exe, RproPI.exe


Issue ID:

13266

WebTAC ID:

19931

Area:

Vouchers

Severity:

Moderate

Title:

Would like functionality in ASN Voucher Batch Receive to allow scanning multiple packages at one time, without having to choose Select after scanning each package.

Description:

Would like functionality in ASN Voucher Batch Receive to allow scanning multiple packages at one time, without having to choose Select after scanning each package (like in 7 Series).

In 7 Series, users could scan several packages at once (if the package didn't exist it would warn them with a warning beep and a message) then they could update these ASN vouchers in one swoop by pressing end. In 8 series they have to select the package row then go to the assumptive find, then scan the package (if the item doesn't exit there is no warning it just remains on the last item selected) and then click on the select button after each item. The client is receiving hundreds of packages a day and this is really inefficient process as compared to the way they had been able to do this in 7 series.

Resolution:

In 7-series, it is possible to scan multiple ASN packages, and receive them in a batch receive. In 8-series, it was necessary to add the package numbers one at a time to the batch receive grid, which was much more time consuming for the customer. Functionality has been added to the batch receive area so that multiple ASN package numbers can be scanned in and received in a batch.


Issue ID:

13980

WebTAC ID:

4845

Area:

RproDB / ECM

Severity:

Critical

Title:

ECM > System needs a better way to tell you that RPRODB needs to run

Description:

After a polling cycle I HAPPENED to notice that there was a message that a critical preference was updated and RPRODB needs to be run. The system should either do that automatically or give a more visual warning. People do not generally look at the log every day and who knows what that critical preference could affect. When entering RPRO you should get a warning that RPRODB needs to be run because a preference has been updated by EMS/ECM

Resolution:

After data processed in from ECM changes key preferences, Rpro8 will now notify a user with the following message: "Updated key preferences have been received by ECM. Please launch RproDB to process them." This occurs upon logging in to Rpro8.


Issue ID:

13943

WebTAC ID:

24252

Area:

Polling

Severity:

Moderate

Title:

Polling > Stations columns are not sortable.

Description:

Create several stations in Polling > Stations. Try to sort on any of the columns. It does not work as it has in 7 series. In 7 series all columns were sortable.

Resolution:

It was not possible to sort any columns when looking at the Stations list view in polling. This was a feature in 7-series, but was removed from 8-series. The standard Retail Pro sort buttons have now been enabled for all columns in the list view.


Issue ID:

14007

WebTAC ID:

24496

Area:

Summary Reports

Severity:

Moderate

Title:

The latest 8.40 image does not contain the files needed to create Receiving Merchandise Summary Report.

Description:

Create a clean install of RPRO8.40. Go into Reports>new>summaries>receiving merchandise click new, nothing happens. Add the following files from a working install of 8.5 to the \WINRPT folder of the 8.4 install RL000001.SVM & DL000001.SVM. Repeat step 2. you will have a blank report now.

Resolution:

The RL000001.SVM and DL000001.SVM files were missing from the 8.40 installation which prevented new Receiving Merchandise Summary reports from being created. These files have been added so that the reports can run.

Rpro v7.63 Core

Updated executables Contained in the June Rpro v8.51 Core update:

Core Files:

Activity.exe, Advops.exe, PrefSys.exe, PrefWS.exe, RProcIn.exe

Tools:

~Bridge.exe, Batch.exe, DVS.exe, Reconstruct.exe, RproPI.exe


Issue ID:

14074

WebTAC ID:

25315, 25351

Area:

Adjustment Memos

Severity:

Critical

Title:

Need the ability to enter negative quantities in any document.

Description:

In a perfect example, one would order merchandise, receive it and then sell it. Once in a while, when an item is damaged or stolen, it would be marked out of stock to correct the inventory level.

In a not so perfect example, especially in a world where retailers are dealing with vendors in several countries, the merchandise is ordered and sometimes physically received in stores and sold prior making the logical receiving of the merchandise through RPRO. The RPRO receiving may be delayed for several reasons but mainly because all the paperwork (Invoices from foreign vendors, duty information, freight, etc ) will be available to the retailers much later on.

The idea is that the receiving will eventually take place but not systematically before transactions are actually rang up against the physically received goods. Therefore this situation created the following problems among others:

1) Store 1 has a red dress A in hand, but did not receive it in RPRO yet. The red dress A needs to be marked out of stock (because a) it can be damaged, b) it is sold at wholesale to a department store, c) it is part of a staff clothing allowance, etc"¦).

2) Store 1 did physically received merchandise and puts it on the floor as soon as possible. RPRO merchandise receiving will happen as soon as the paperwork is available. In the meantime, a physical inventory is conducted. The pieces counted show items not yet received in RPRO as greater than zero quantity counted. Staff knows they have a pending receiving session and we want to make sure that the physical inventory memos generated by the physical inventory process are taking into account the fact that we do have pending merchandise receipts.

Up to version 7.61, you could create adjustment memos in which you had the ability to enter a negative quantity.

As an example, in situation number one the accounting would generate a negative adjustment memo showing a quantity of -1 for the Red Dress A in store 1. The accounting would be able to use the reason Marked out of stock (in situation 1a) or Wholesale (in situation 1b) or Allowance (in situation 1c) for the adjustment memo and book a journal entry accordingly. Eventually, when the RPRO receiving voucher would be created for store 1, the inventory for that store would be adjusted correctly. Doing this chain of events would insure that no one within the company would have to wait until the process of someone else is done prior performing his/her duties.

In the second example, based on the pending merchandise receiving to be performed, auditors would make the necessary quantity adjustment memos (these would include negative quantities) to make sure that when receiving is done, it would not over-inflate inventory quantities.

In version 7.62 and above, this is not allowed any longer and it creates a pretty big frustration, to say the least, among our clients, especially the ones with many stores who therefore have a constant flow of merchandise deliveries, Marked out of stock items, clothing allowances, etc"¦ The way the system is designed as of today does not fit their needs. If they do understand that in a perfect world, the normal cycle of things would be that you cannot mark out of stock something that you did not receive, the reality is that for efficiency purpose and logging reasons, they need to make adjustments with negative quantities as they see fit.

Resolution:

A new preference has been added in System Preferences to Allow Negative Quantities on PO's, TO's and Adjustments. The preference is under General Documents and is called "Allow Negative Quantities on Other Documents". Setting this preference will allow you to enter negative quantities.


Issue ID:

13434

WebTAC ID:

3291, 18510

Area:

Purchase Orders

Severity:

Moderate

Title:

EDI Sent Date on POs in status bar obscured by store#

Description:

After an EDI PO has been transmitted, the PO is updated with an EDI Sent Date. This date is displayed on the status bar on the top of the screen. Currently, this date is obscured by the Store#. This is preventing the client from accurately discerning the EDI sent date.

Resolution:

The EDI status and date are now correctly displayed in the upper right of the screen. The store number is no longer displayed if the PO is marked as a EDI PO.


Issue ID:

13437

WebTAC ID:

3297

Area:

Vouchers

Severity:

Serious

Title:

ASN Vouchers should use the station code of your store when they are made into regular vouchers.

Description:

When you import ASN vouchers using the RNET tool you can only enter the store. There is no interface to allow you to import the station code. Retail Pro automatically enters the station code as 0 instead of A. So at remotes when you make the ASN into a regular voucher it has station 0 on the voucher. This is a problem if you need to regenerate vouchers from the remote to the Main. Only vouchers from that store/station will be regenerated so all the vouchers with station 0 are skipped and not regenerated.

Resolution:

ASN's that are received at a remote are now updated with the Remote's station ID instead of the station ID of where the ASN was created.


Issue ID:

13659

WebTAC ID:

22345

Area:

Journal Report

Severity:

Serious

Title:

Vouchers read differently by reports in 7.63 based on the voucher filing preference

Description:

Create an install of 7.63 with the latest reports and core updates. Set the system preferences>polling>"file vouchers based on" to ARRIVAL. Set the system date on your workstation to 02/01 and go into RPRO on 02/01 (Rpro date). Open RPRO go into purchasing and create a voucher. Exit completely out of retail pro and change the system date back to today. Re enter RPRO on today 02/04 (Rpro date) and copy the voucher that was made to a new voucher and update. Run the Reports>Journals>receiving journal for today. You will receive "nothing to print" even though the voucher was updated today.

If you change the preference in system preferences from file vouchers based on ARRIVAL to based on POSTED, The report runs correctly. This does not occur within 8 series using the same steps so it appears to be related to the way that 7.63 is saving the copied voucher.

Resolution:

When copying a former voucher the Arrival date is being updated correctly instead of being copied from the previous voucher.


Issue ID:

13430

WebTAC ID:

3241

Area:

Receipts

Severity:

Moderate

Title:

Cashiers have the ability to stealing by ringing up an invoice and after taking the money from the customer, putting the invoice on hold.

Description:

Client has discovered that their cashiers are stealing by ringing up an invoice and after taking the money from the customer, putting the invoice on hold. They have discovered numerous workstations with invoices on hold and have caught people in the act.

Resolution:

A new password activity has been added to system preferences that allow you to set a password level for putting an invoice on hold. The new setting is under System Preferences > Security > Password Activities > POINT OF SALE - Allow placing document On Hold. This setting allows you to restrict who can put an invoice on hold.


Issue ID:

14010

WebTAC ID:

Area:

Receipts

Severity:

Serious

Title:

Tender allows "Gift card" to be authorized two times without taking the tender for the gift card two times resulting in an error settling.

Description:

Create a receipt and tender $10.00 by credit card dial out and authorize. In the change window put 10.00 for GIFT2 tender. Choose AUTH. Let it dial out and authorize. After authorization hit enter while the focus is still on the gift card. NOTE that rather than warning the user that the transaction has already been authorized the user is presented with the authorization prompt again. Fill in the card number and the date hit enter. The user is presented with a "AUTH" number field for a forced auth code.

When you accept this you have doubled the amount of the gift card value but you have not paid for the card. There are 3 records in the batch for this transaction. 1 forced auth for the GIFT one regular AUTH and a credit card AUTH. This is very confusing to the user. Gift cards should only be allowed to dial out and authorize one time per transaction.

Resolution:

Tender was allowing Gift Cards to be authorized twice without charging the gift card. We now prevent the second and subsequent authorization attempts in this situation.

Multi-Version Tools

Auto Utilities

Issue ID:

14045

WebTAC ID:

25095

Area:

Auto Utilities

Severity:

Serious

Title:

Auto Min / Max is producing an Invalid Floating Point Operation

Description:

Rpro defined # of Stores = 6

Create formula #1 (Test1) Min Formula only (leave the Max Formula as the system default):

Sold From = 0

Sold Less Than = 9999999

Condition = Lesser Of

DOS = 1

Qty = 0

% Increase = 0

Ann Sales = unchecked

Store selection = Stores 5 & 6

Now run calculate for the formula. You will receive an Invalid Floating Point Operation.

Resolution:

A floating Point Operation Error was occurring when users used the following settings:

- RPRO was configured for multiple stores

- The DOS value in the Min formula was set to 1, and the Max formula was left at zero

- The formula used was only created and calculated for a portion of the stores that existed

With these settings, the original formula would try to divide by zero, producing the error. The formula was changed so that this would not occur.


Issue ID:

13984

Issue ID:

In House

Area:

Auto Utilities

Severity:

Serious

Title:

Auto min max will not assign new min or max values to items if the items have been received on a voucher.

Description:

With the latest updates, auto min/max will not assign min/max values to items if the items have been received on a voucher. To duplicate, clear any existing min/max values and calculate min/max with a quantity only formula. Other formulas probably fail too, but have not been tested.

Resolution:

In the case where last date received was the same as the last date in the analyzed date range, the number of days was 0 instead of 1. This has been fixed so that it calculates it as 1.

Issue ID:

13786

Issue ID:

23274, 23952, 24091, 22964, 24160, 24161

Area:

Bridge

Area:

Moderate

Title:

laceName w: st="on">RunninglaceName> laceType w: st="on">BridgelaceType> using the command line parameter fails to update the file.

Description:

Create a customer file with a couple or more customers. Use the default customer export bridge map to export the customer file. Rename the current customer file and go into RProDB and recreate a blank client.dat file. Now open a command line prompt or using the scheduler run bridge to import the client file (~bridge.exe default_custimp). The bridge tool may flash like it worked but if you go into the customer file in Retail Pro you will not see any customers.

Resolution:

The bridge file requires filters to be associated with the bridge maps in order to be able to import data. Previous defaults of the bridge maps did not include any filter, and the command line parameter did not require them. Changes have been made so that no maps are required to transfer the data for Departments, Vendors or Customers. For all other areas command line parameter has been updated to require that the filters are assigned to the bridge maps to run.


Issue ID:

13851

WebTAC ID:

23615

Area:

Bridge

Severity:

Change Request

Title:

Request the "marked" field be made available in the bridge filter

Description:

The client has flagged the customer in DVS using the "marked" field and would like to be able to filter on the marked for 1 and 2 fields when they run bridge to export their customers.

Resolution:

A new bridge filter has been added to the default customer export map. You can now filter on the two marked fields and export only those customers.


Issue ID:

13857

WebTAC ID:

24092

Area:

Bridge

Severity:

Serious

Title:

Bridge field INvoice: Sub Tndr type does not import the tender type.

Description:

Create some receipts in V8.50 using all different types of tender. Export the receipts using the default invoice export map. You will notice that the field Invoice: Sub Tndr type is the second field in the subtotal record. This is exported as P for every record regardless of tender type. If you import the file into a blank data file and sync this EMS the tender type is blank on all the records. This is causing a serious problem with the importation of history data as the tender type is blank on all receipts.

Resolution:

The tender type is now imported/exported correctly from the default Bridge Invoice Map.


Issue ID:

13921

WebTAC ID:

In House

Area:

Bridge

Severity:

Moderate

Title:

Bridge tool has fields that do not export data

Description:

Please remove the fields that are no longer valid. A few things of note. I think but I'm not sure INVOICE: ITEM KIT ITEM ID - may be PkgItmNum and The other two may be the same field. I received 0,1,2,3,5 as options - 1 is dikKit, 3 is dikPackage, 5 is dikPackageItem.

Resolution:

In bridge the "Invoice: Item Break Pkg Flag" and "Invoice: Item Kit Item Id" fields have been removed from the invoice item record, as well as the default invoice import and output map. They were removed because there was no record in the Sales data file to read from or write to for these fields.


Issue ID:

13959

WebTAC ID:

In House

Area:

Bridge

Severity:

Change Request

Title:

Bridge > Merge files in Bridge and Maps directories

Description:

Most of the bridge files found in the Bridge and Maps directories are the same. These were originally split out to accommodate 7-Series and 8-Series installations. Today it is not necessary to split these files.

Resolution:

The map directory has been removed and is no longer needed for bridge.

DVS

Issue ID:

13872

WebTAC ID:

23727, 24589

Area:

DVS

Severity:

Moderate

Title:

Recalc SRO is not recalculating PO's at INFO stations.

Description:

Create a PO for an item at a main. Record the On Order amount in Merchandise > Inventory > Inventory Qtys at the remote INFO station. Poll the PO to the INFO from the Main. Run Recalc SRO. Check On Order amount in Merchandise>Inventory>Inventory Qtys at the INFO station. This field should have been updated with the new PO info.

Resolution:

On an INFO station, On Order Quantities for items on a PO polled down from a Main station were not updated after running Recalc SRO from DVS. The problem was caused by the fact that, at an INFO station, the file POINF.DAT was not validated by DVS. This issue is fixed now, and running Recalc SRO now correctly updates On Order Quantities for inventory items.


Issue ID:

14011

WebTAC ID:

24776, 25195

Area:

DVS

Severity:

Serious

Title:

Re link SOs not working at Remote Locations

Description:

Drop in the latest DVS tool into a remote. Run Tools>DVS>Recalc> notice that the Relink SOs is not highlighted. This feature should be available at the remote location. That way each remote can repair the file locally then send ALL SOs through polling to the main. The main cannot send ALL SOs in polling. The only way to do it at a main is to use the Split SO tool and then send the SO file to the remote through a move list.

Resolution:

In DVS.exe, the 'ReLink SO' button is grayed out and disabled at a Remote station or a Backroom station. This feature needed to be enabled at the Remote so that SO can be repaired locally. The button is now enabled at both Remote stations and Backroom stations, and functions correctly.

EFT – Credit Pro (v8.40 & v7.63 Only)

Issue ID:

13972

WebTAC ID:

24470

Area:

Credit Pro

Severity:

Serious

Title:

Credit Pro > Batch > Error occurs when you attempt to run batch in 7.63 "you are not licensed for this EFT type."

Description:

When you attempt to run Batch.exe (in a 7.63 installation only) when configured and licensed for Credit Pro you get the following error message: "You are not licensed for this EFT type. Select the type you are licensed for in Workstation Preferences.".

To reproduce:

Using a 7.63 install set your EFT type in Workstation Preferences to use Credit Pro. With the latest Credit Pro updates, including the latest Windows Batch.exe, run the Batch tool. When you run batch.exe you will get the error message: "You are not licensed for this EFT type. Select the type you are licensed for in Workstation Preferences."

Resolution:

Batch.exe was assuming that 7 series users were using PPM. Now it checks the 7 series setting that specifies the EFT type (which is different from the 8 series setting). We now allow the user to set the server workstation number if the EFT type is Credit Pro.

Reconstruct

Issue ID:

14013

WebTAC ID:

24785

Area:

PI Tool

Severity:

Serious

Title:

Cannot store more than 9 archived PIs for the same store.

Description:

A client does cycle counts and accumulates a large number of archived PIs that they wish to refer to as they have been able to do in the past when using the DOS PI tool

Resolution:

Created a setting in RproPI system prefs called # backups. It defaults to 12 and accepts any value between 1 and 35. Note that if you set it to a value lower than the number of backups you currently have, then the extra backups will not be deleted. If you set it to a value outside 1 and 35, you will get a warning message.

Reports

Issue ID:

14050

WebTAC ID:

25194, 25330, 25387, 25456

Area:

Reports - General

Severity:

Serious

Title:

Cost information is not displayed after applying the May 2004 updates when logged on as a user other than SecAdmin.

Description:

Non-SecAdmin users cannot view cost info with the new reports update without the sec file. It is necessary to revert to a prior version of Reports.

Resolution:

The security setting that removes the right to view cost on reports was not working. A new reports security file is being used to fix the problem.

Rpro PI

Issue ID:

14013

WebTAC ID:

24785

Area:

PI Tool

Severity:

Serious

Title:

Cannot store more than 9 archived PIs for the same store.

Description:

A client does cycle counts and accumulates a large number of archived PIs that they wish to refer to as they have been able to do in the past when using the DOS PI tool

Resolution:

Created a setting in RproPI system prefs called # backups. It defaults to 12 and accepts any value between 1 and 35. Note that if you set it to a value lower than the number of backups you currently have, then the extra backups will not be deleted. If you set it to a value outside 1 and 35, you will get a warning message.

Rpro Update

Issue ID:

14063

WebTAC ID:

25272, 25281, 25285

Area:

Rpro Update

Severity:

Critical

Title:

RPRO update gives Retail Pro version mismatch on 8.51 install

Description:

Running RPRO update on a 8.51 install and I got the error msg: "Retail Pro version mismatch. Please run RPRO to ensure that all files match the installed version. You may then re-run update" . This happens on ether on fresh installation or on upgraded install.

Resolution:

A change was made to Rprodb.exe to enable Rproupdate.exe to read the correct Rpro version number.

October 27, 2004

Retail Pro BTF-Series8.4/8.5 Update Release Cycle

RPro v8.51 Core

Updated executables Contained in the October RPro v8.51 Core update:

Core Files:

Rpro8.exe, Rpro_Api.bpl, RDA2.dll, ms_ie_d5.bpl, RPRO_API.bpl, vcl50.bpl, vclie50.bpl, SRO.exe, Custexport.exe, cprocin.exe, mprocin.exe, rprocin.exe, Rpro8.sec,

TS23_Pulse.pdf, Pulse.hlp, V8_3_DeptVend.pdf, V8_9_Customers.pdf, Rpro8.cnt, Rpro8.hlp

Tools:

SRO.exe

Issue ID:

13219

WebTAC ID:

19563

Area:

General System

Severity:

3 - Moderate

Title:

Random order of values for AUX fields displayed in Filter view

Description:

The values displayed for the AUX fields in a Filter design are not displayed in either the order entered or in alphabetical order. They appear to have no pattern, which makes it difficult to find the item you which to use as the criteria.

For example, added the following values to AUX1 - c,a,b,d. In Inventory > Filtered View, the AUX1 field shows the following order - a,b,d,c. I then added a value of "e" to the list. They're now ordered as - a,d,b,c,e.

When creating an item in Inventory, the order is shown as alphabetical. When returning to Preferences, the order is alphabetical. Filter View should display them as alphabetical as well.

Resolution:

In Inventory filter view, AUX fields' values are sorted in alphabetical order.

Issue ID:

13569

WebTAC ID:

Area:

Receipts

Severity:

2 - Serious

Title:

Customer Defined Price Levels defaults to Active price level if no value is set, and it should default to the price level on the document.

Description:

If you are using Customer defined price levels and priced based stores then if you list a customer on the receipt it will change your price level to whatever the active price level is in inventory instead of using the level defined for the price based stores.

If you are using price based stores, and customer defined price levels, then if the customer does not have a level defined it should default to the price based store level, and not the active price level.

Resolution:

If System Preferences are set up to use price based stores and customer defined price levels, then if the customer does not have a level defined , the price on a receipt defaults to the Active price level as set in inventory, not to the price based store level. With this fix, the receipt price now defaults to the price-based store level instead.

Issue ID:

13688

WebTAC ID:

Area:

Tools - Other

Severity:

2 - Serious

Title:

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

Description:

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

Resolution:

SRO.exe now takes "Marked For" PO into consideration when calculating for Cmp On Order Qty and Store On Order Qty.

Issue ID:

13741

WebTAC ID:

Area:

Tools - Pulse

Severity:

4 - Low

Title:

Documentation specifies the wrong location for "Location of the pulse data base"

Description:

"Path to the RPRO folder containing the pulse database" should be the Retail\RPro folder. not the

Retail\Rpro\pulse\data folder as specified in the documentation on page 12 section 5.1 step 3

Resolution:

The following files have been updated in the Pulse documentation:

TS23_Pulse.doc

TS23_Pulse.pdf

The following files have been updated in Retail Pro help:

Pulse.hlp

Issue ID:

13807

WebTAC ID:

Area:

Vendors

Severity:

4 - Low

Title:

Vendor notes field is limited to 243 characters.

Description:

Documentation for the vendor notes field says this fields cap is 310. I was only able to enter 243 characters in 8.5 and 8.4.

Resolution:

The documentation has been updated.

Corrected the Vendor Note field and Customer Note field descriptions to state that the field holds 243 characters. The following E-Manual contents have been updated:

V8_3_DeptVend.doc

V8_3_DeptVend.pdf

V8_9_Customers.doc

V8_9_Customers.pdf

The following Help Files have been updated:

RPRO8.cnt

RPRO8.hlp

Issue ID:

14156

WebTAC ID:

25738

Area:

Customers

Severity:

5 - Change Request

Title:

Request Customer Export Tool have functionality to export inactvie customers.

Description:

Request Customer Export Tool have functionality to export inactive customers.

Resolution:

There is now an option in the Customer Export dialog "Export inactive customers".When selected, inactive customers will be included with the Customer Export.

Issue ID:

14198

WebTAC ID:

Area:

Security Manager

Severity:

5 - Change Request

Title:

Request to be able to restrict users making Out Slips to the available quantity.

Description:

Currently if you are set to Check Availability for Out Slips you can make an Out Slip and place an item on it with a quantity greater then the Available qty. You receive a message but you can still select to transfer more then you have. Can we add a setting in SecAdmin to restrict OutSlips to the quantity on hand only?

Resolution:

An option was added to enforce Checking Availability, Outslips cannot be created if the quantity listed was over the On Hand Quantity.

Issue ID:

14242

WebTAC ID:

26577, 26665

Area:

Receipts

Severity:

3 - Moderate

Title:

Quantity based pricing is not updating the price when price level 1 is first applied to the receipt

Description:

Quantity based pricing is not updating the price when price level 1 is first applied to the receipt

Resolution:

The customer price level was being applied to items first and then to the document. This caused quantity discounts to be recalculated based on the old price level. Now the document global price level is changed first, and then and only then to all items.

Issue ID:

14372

WebTAC ID:

Area:

Sales Orders

Severity:

2 - Serious

Title:

Deleting an SO with items with serial numbers, these serial numbers do not get available again. After poling they are still marked as "SO - reserved"

Description:

When we delete a SO with items with serial numbers, these serial numbers do not get available again. After poling they are still marked as "SO - reserved"

I make at a POS station a SO - layaway with full serial items on. I put the serial numbers on every serial number item.

If I look at the inventory and the serial number table the serial numbers has a status as: SO - reserved

Some days later I delete the whole SO or I delete some of the SO lines

No matter if I delete the whole SO or some the individual lines the serial numbers are not released in the serial number table, but have still the status as SO reserved.

Resolution:

Previously, polling was causing the flag for serial number items referenced on deleted SOs to be Reserved. This prevented other documents from using this serial number item. Polling has been changed to correctly set the Reserved flag for items that are returned to Available.

Issue ID:

14373

WebTAC ID:

Area:

Receipts

Severity:

2 - Serious

Title:

When we make a Return Receipt with items with full serial number tracking, we can't use the serial numbers which are on the original Sales Receipt (referring a SO), because they "are in use"

Description:

When we make a Return Receipt with items with full serial number tracking, we can't use the serial numbers which are on the original Sales Receipt (referring a SO), because they "are in use" and it means that we can't bring the serial numbers back to inventory again. Thí­s problem is related to the problem described in 3. Because the serial numbers never are really removed with the Sales Receipt, it's not possible to bring the serial numbers back with the Return Receipt.

Resolution:

Previously, processing in files to the remote, the Serial numbered items that were sold from a SO were incorrectly flagged as reserved. This prevented other documents from using this serial number item. Polling has been changed to correctly set the Reserved flag for items that are returned to Available.

Issue ID:

14392

WebTAC ID:

Area:

Customers

Severity:

3 - Moderate

Title:

RecP$ reverts to invnP$ when answering NO to use customer price level.

Description:

RecP$ reverts to invnP$ when answering NO to use customer price level

Resolution:

If a manual discount is applied to a receipt, it is removed on a receipt for a customer if that customer has a Price Level defined and the Price Level is not applied to the receipt. The price on the receipt reverts to the non-discounted price. With this fix, the discount is not removed anymore, it remains on the receipt as it should.

Issue ID:

14429

WebTAC ID:

Area:

Tools - Doc Designer

Severity:

1 - Critical

Title:

In the attached Doc Design, scales are part of the Grid Band. There is no way to disable totalling each scale.

Description:

This is an issue reported by Michelson's Shoes, and is related to Bug #14353 and WebTac #26422. The customer needs to use Style view and grids. When sorting by Scale, each Scale is totalled and they find this confusing. There is no way to disable this totaling by Scale in the Doc Design.

Resolution:

In a document using Grid Bands, if the grids are sorted by Scale, each Scale is totalled There is no way to disable totalling the Scale. Now the scales are not totalled.

Issue ID:

14473

WebTAC ID:

27219, 28419

Area:

Purchase Orders

Severity:

1 - Critical

Title:

Erroneous PO Dup Error

Description:

Create a main with 5 lines of inventory

Create and initialize 2 remotes

Turn on Proposed POs at each remote

Create a proposed PO at each remote that contain the same items at each one.

Poll the proposed POs to the main

then try to mark them and accept them; You get a PO DUP error. on one of the POs. RPRO thinks they are the same PO. You cannot resolve this issue without going into the body of the PO and modifying the items.

Resolution:

The PO DUP error message no longer occurs, and the PO's can be accepted.

Issue ID:

14488

WebTAC ID:

Area:

Security Manager

Severity:

1 - Critical

Title:

Do not allow transfers over the On Hand qty amount does not work if you use Choose Edit items.

Description:

There is a new security setting to Do not allow overide of availability checking on Slips. This works will if the items are entered in the new SLip form view. If you instead select Choose Edit Items you can enter any number in the doc qty field and you can select the qty entered. The security needs to encompass this manner of entering item qty as well.

Resolution:

An option was added to enforce Checking Availability when adding items from the Choose/Edit items window.

Rpro v8.40 Core

Updated executables Contained in the August Rpro v8.40 Core update:

Core Files:

Rpro8.exe, Rpro_Api.bpl, RDA2.dll, ms_ie_d5.bpl, RPRO_API.bpl, vcl50.bpl, vclie50.bpl, SRO.exe, Rpro8.sec

Tools:

SRO.exe

Issue ID:

13688

WebTAC ID:

Area:

Tools - Other

Severity:

2 - Serious

Title:

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

Description:

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

Resolution:

SRO.exe now takes "Marked For" PO into consideration when calculating for Cmp On Order Qty and Store On Order Qty.

Issue ID:

14198

WebTAC ID:

Area:

Security Manager

Severity:

5 - Change Request

Title:

Request to be able to restrict users making Out Slips to the available quantity.

Description:

Currently if you are set to Check Availability for Out Slips you can make an Out Slip and place an item on it with a quantity greater then the Available qty. You receive a message but you can still select to transfer more then you have. Can we add a setting in SecAdmin to restrict OutSlips to the quantity on hand only?

Resolution:

An option was added to enforce Checking Availability, Outslips cannot be created if the quantity listed was over the On Hand Quantity.

Issue ID:

14488

WebTAC ID:

Area:

Security Manager

Severity:

1 - Critical

Title:

Do not allow transfers over the On Hand qty amount does not work if you use Choose Edit items.

Description:

There is a new security setting to Do not allow overide of availability checking on Slips. This works will if the items are entered in the new SLip form view. If you instead select Choose Edit Items you can enter any number in the doc qty field and you can select the qty entered. The security needs to encompass this manner of entering item qty as well.

Resolution:

An option was added to enforce Checking Availability when adding items from the Choose/Edit items window.

Multi-Version Tools

SRO

Issue ID:

13688

WebTAC ID:

Area:

Tools - Other

Severity:

2 - Serious

Title:

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

Description:

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

Resolution:

SRO.exe now takes "Marked For" PO into consideration when calculating for Cmp On Order Qty and Store On Order Qty.

March 1, 2005

Update Release Cycle Retail Pro BTF-Series8.4/8.5/Tools

RPro v8.51 Core

Updated executables Contained in theFebruary RPro v8.51 Core update:

Core Files: Rpro8.exe, ms_ie_d5.bpl, vclie50.bpl, vcl50.bpl, RPRO_API.bpl, rda2.dll, RPro8.sec, RProDB.exe, RproDB.sec, SecAdmin.exe, PPMSERVR.exe, RtiShift4Gift.dll, RtiShift4Debit.dll, RtiShift4Credit.dll, RtiShift4Check.dll, RtiGift.dll, RtiDebit.dll, RtiCredit.dll, RtiCheck.dll, ReceiptRTISchema.xml, CustHistoryRTISchema.xml

Tools:SLCC.exe


Issue ID:

14883

WebTAC ID:

Area:

Vouchers

Severity:

3 - Moderate

Title:

Copying a voucher from a closed period to an open period does not clear the Audit flag

Description:

When copying a voucher from a closed period to an open period, the Audit flag is not cleared. This process is needed in order to work around a current design limitation of Stock Audit. Once copied, the document should be editable.

Resolution:

Issue: Copying a voucher from a closed period to an open period does not clear the Audit flag

Solution: The Audit flag is cleared on all documents (receipts, vouchers, memos and slips) when they are copied.


Issue ID:

14840

WebTAC ID:

31016

Area:

EFT - General

Severity:

1 - Critical

Title:

EFT settings return to DEFAULT value of NONE when connection is lost

Description:

Reported Problem:

Create an installation of RPRO with a mapped drive to an EFT folder where PPM or CPRO is running.

Setup workstation prefs to use the correct Credit option under EFT

Make a transaction to confirm the modem is dialing etc.

Disconnect the mapped drive

Exit out of RPRO

Run the instance of RPRO again and go into another EFT transaction

NOTE the prompt for EFT card type comes up. Go into workstation preferences EFT>Credit. Note it is now set to NONE.

Resolution:

Whenever a user goes to the tender screen, access to the eft folder is checked. If the folder cannot be accessed for any reason, or if there is a problem loading the eft files when first going into the tender screen, an error message is displayed and the eft tender buttons are disabled. The same logic was also put into SO's. The cashier can complete the transaction using a different type of tender.


Issue ID:

14833

WebTAC ID:

Area:

Security Manager

Severity:

2 - Serious

Title:

Communicating De-activated employees to RPro 8 causes Access Violations

Description:

An access violation can be generated when an employee that is a member of an RPro 8 Group is deactivated in V. 9 and communicated back to V. 8

Create an employee in RPro 9 and communicate the employee to RPro 8.

Once in RPro 8 add this employee to a group.

Process back to V. 9 and de-activate the employee.

Communicate the change back to V. 8

After Processing in the changes go to SecAdmin > Groups in V. 8 and Open a group (different from the group that you assigned the now de-activated employee to) and add another employee to the group and save. An Access Violation is shown at this point.

Resolution:

Initial Problem: An access violation is created when deactivating employees in RPro 9 and communicating the change back to RPro 8.

Solution: SecAdmin library was modified to detect when ECM has deleted employees and read data from RtiSec.dat on the fly.


Issue ID:

14803

WebTAC ID:

30257

Area:

EFT - Shift4

Severity:

2 - Serious

Title:

Shift4 credit card transactions duplicating under certain conditions

Description:

Reported Problem:

Based on analysis of trace files from customer combined with the audit trail sent to Shift4 from the client Shift4 has determined that Retail Pro is ignoring responses from Shift4 after an auth has been sent. This in turn causes them to time out and as such is a root cause of a duplicated transaction.

Additional information:

When the user tries to authorize again after the timeout, RPro doesn't always use the same transaction number. We should use the same transaction number again, so we don't defeat Shift4's duplicate checking code.

Resolution:

Programming has changed the way transaction numbers are assigned.

There's a file in the eft folder called shift4sn.dat which holds the serial numbers that are used to as transaction numbers. There used to just be one serial number that was shared by all workstations, but now each workstation has it's own serial number. Each serial number is in the range 1 to 999999. The transaction number consists of a 2 digit workstation number followed by the serial number for that workstation. Only if the transaction is approved is the serial number incremented. On the receipt tender screen, the transaction number is displayed in the reference number field (as before).


Issue ID:

14794

WebTAC ID:

Area:

Stock Audit

Severity:

1 - Critical

Title:

Stock Audit not creating open balances when choose to start from RPro backup all qtys zero

Description:

Stock Audit is not creating opening balances if you choose to start from a Retail Pro backup, all quantities are zero.

1) Make a backup of Retail Pro

2) Start SLCC and choose to create opening balance from a backup

3) Point the directory to the Retail\Rpro directoy for the backup

4) once step (3) is done start a new period

5) check the openeing balnce it will equal zero.

Resolution:

Issue:

When using a data back up to create an initial open period within stock audit the inventory cost and quantities were zero.

Solution:

Stock Audit has been fixed so that when and opening period is created from a snapshot of inventory the opening cost and company quantity is updated.


Issue ID:

14780

WebTAC ID:

30736

Area:

EFT - PPM

Severity:

3 - Moderate

Title:

PPMserver Times out dialog during upload of large batch

Description:

Reported Problem:

The time out put in place for the credit card dialog is timing out before PPMserver is done uploading the batch. This is causing the dialog to give the error "time out" while PPMserver is still posting the batch. See attached log.

Steps to replicate.

Select upload

You will see Connected

then see Settling batch ###

after about a minute you get Timed out

click OK

Queued at the server message is displayed for about a minute until the cancel button can be hit, Brings you back to the the Upload screen

If you try to settle again you get no batches to settle

System Impact:

The user will be confused by this.

Resolution:

The PPMServer will now stay open until the batch is finished processing. No timeout errors should be reported.


Issue ID:

14768

WebTAC ID:

30735

Area:

EFT - PPM

Severity:

2 - Serious

Title:

Duplicate checking in PPM creates a possible problem with void transactions

Description:

Reported Problem:

1> Create a transaction with a credit card and authorize it.

2> Now before updating the transaction void the authorizations by deleting the authorized amount in the tender window.

3> Now rerun the same amount using the same card and exp date etc.

Note you get the "duplicate authorization" prompt.

The options are to use the existing authorization or create a new authorization. If you choose to use the existing authorization the system does not go out and get a good authorization. It simply keeps the voided one that is in the batch.

This is bad for the client as it is confusing to the cashiers at POS. What happens is the cashier not knowing can select to use the previous auth and create a situation where the receipt can still be updated. One of three things should happen:

A> if the user chooses to use the existing authorization IE keep the void, then the tender should not be applied as a positive

or

B> the duplicate checking should not offer to use the existing transaction when it is a voided transaction.

or

C> as the duplicate issue has been corrected through disabling the cancel button and managing the way PPMserver behaves when using predial , rem out the routine for duplicate checking all together

Resolution:

Voided authorization information is now not stored. This prevents the situation in the issue description from occurring.


Issue ID:

14694

WebTAC ID:

29840, 30820

Area:

Sales Orders

Severity:

1 - Critical

Title:

SO deposit created when not tendered.

Description:

Reported Problem:

With A Deposit amount required on an SO a user can back out of an SO deposit and cause a receipt to be made. Steps to Reproduce.

1.) System Preferences > Require a 10 % deposit on SO's.

2.) Make a SO then Save, The user will be propted to leave a deposit.

3.) In the Deposit Screen do not tender and just select Back from the side menu.

4.) Back in the SO Screen Select Save again and the user will once again be brought to the Deposit screen and a new deposit will have been started.

5.) Once again in the Deposit Screen do not tender and just select Back from the side menu.

6.) Again back in the SO Screen Select Save again and the user will once again be brought to the Deposit screen and another new deposit will have been started.

7.) Do not tender and select the second deposit row with your mouse.

8.) Select the RPRO buttion in the upper corner. This will back you out to the Retail pro home screen, with out a deposit being made.

9.) Now check former SO's there will have been a SO made. And in former receipts there will be a deposit receipt for the so tendered using store credit.

Resolution:

The deposit on an SO isn't removed when the back button is pressed while in the deposit screen. This would result in a customer receiving unearned store credit in certain situations. Now the deposit is removed if the back button is selected prior to tendering the deposit.


Issue ID:

14844

WebTAC ID:

31051

Area:

EFT

Severity:

2 - Serious

Title:

POSres takes more than a minute to determine there is no connection to NETAPI

Description:

Reported Problem:

Due to the limitation in windows that results in NetAPI reporting a valid connection to POSres RPRO takes more than a minute to go into offline eft mode when the router side network connection is lost. Please add a configurable timeout value to an ini file. The time out should not be used if there is no value in INI file variable. IE if the value for time out is not set POSres should determine connectivity normally otherwise if the the timeout value is present then use that value to determine that the connection has been lost.

Resolution:

Added a section and a key to rtishift4.ini which is located in the eft folder:

[System]

OnlineCheckTimeoutSeconds=15

Part of the fix for this bug was put into 8.51 and 8.40 even though they don't support POS Resiliency. If netapi is shut down in the middle of running a transaction, RPro would wait indefinitely for a response from netapi. Now, the user will get an unexpected disconnect error message soon after netapi is shut down.


RPro v8.40 Core

Updated executables Contained in theFebruary RPro v8.40 Core update:

Core Files: Rpro8.exe, vclie50.bpl, vcl50.bpl, RPRO_API.bpl, rda2.dll, RPro8.sec, SecAdmin.exe, PPMSERVR.exe, RtiShift4Debit.dll, RtiShift4Credit.dll, RtiShift4Check.dll, RtiDebit.dll, RtiCredit.dll, RtiCheck.dll

Tools: SLCC.exe


Issue ID:

14833

WebTAC ID:

Area:

Security Manager

Severity:

2 - Serious

Title:

Communicating De-activated employees to RPro 8 causes Access Violations

Description:

An access violation can be generated when an employee that is a member of an RPro 8 Group is deactivated in V. 9 and communicated back to V. 8

Create an employee in RPro 9 and communicate the employee to RPro 8.

Once in RPro 8 add this employee to a group.

Process back to V. 9 and de-activate the employee.

Communicate the change back to V. 8

After Processing in the changes go to SecAdmin > Groups in V. 8 and Open a group (different from the group that you assigned the now de-activated employee to) and add another employee to the group and save. An Access Violation is shown at this point.

Found Internally by Alexey

Resolution:

Initial Problem: An access violation is created when deactivating employees in RPro 9 and communicating the change back to RPro 8.

Solution: SecAdmin library was modified to detect when ECM has deleted employees and read data from RtiSec.dat on the fly.


Issue ID:

14803

WebTAC ID:

30257

Area:

EFT - Shift4

Severity:

2 - Serious

Title:

Shift4 credit card transactions duplicating under certain conditions

Description:

Reported Problem:

Based on analysis of trace files from customer combined with the audit trail sent to Shift4 from the client Shift4 has determined that Retail Pro is ignoring responses from Shift4 after an auth has been sent. This in turn causes them to time out and as such is a root cause of a duplicated transaction.

Additional information:

When the user tries to authorize again after the timeout, RPro doesn't always use the same transaction number. We should use the same transaction number again, so we don't defeat Shift4's duplicate checking code.

Resolution:

Programming has changed the way transaction numbers are assigned.

There's a file in the eft folder called shift4sn.dat which holds the serial numbers that are used to as transaction numbers. There used to just be one serial number that was shared by all workstations, but now each workstation has it's own serial number. Each serial number is in the range 1 to 999999. The transaction number consists of a 2 digit workstation number followed by the serial number for that workstation. Only if the transaction is approved is the serial number incremented. On the receipt tender screen, the transaction number is displayed in the reference number field (as before).


Issue ID:

14780

WebTAC ID:

30736

Area:

EFT - PPM

Severity:

3 - Moderate

Title:

PPMserver Times out dialog during upload of large batch

Description:

Reported Problem:

The time out put in place for the credit card dialog is timing out before PPMserver is done uploading the batch. This is causing the dialog to give the error "time out" while PPMserver is still posting the batch. See attached log.

Steps to replicate.

Select upload

You will see Connected

then see Settling batch ###

after about a minute you get Timed out

click OK

Queued at the server message is displayed for about a minute until the cancel button can be hit, Brings you back to the the Upload screen

If you try to settle again you get no batches to settle

Upon reviewing the log the batch is settled correctly but the

See attached log.

System Impact:

The user will be confused by this.

Resolution:

The PPMServer will now stay open until the batch is finished processing. No timeout errors should be reported.


Issue ID:

14768

WebTAC ID:

30735

Area:

EFT - PPM

Severity:

2 - Serious

Title:

Duplicate checking in PPM creates a possible problem with void transactions

Description:

Reported Problem:

1> Create a transaction with a credit card and authorize it.

2> Now before updating the transaction void the authorizations by deleting the authorized amount in the tender window.

3> Now rerun the same amount using the same card and exp date etc.

Note you get the "duplicate authorization" prompt.

The options are to use the existing authorization or create a new authorization. If you choose to use the existing authorization the system does not go out and get a good authorization. It simply keeps the voided one that is in the batch.

This is bad for the client as it is confusing to the cashiers at POS. What happens is the cashier not knowing can select to use the previous auth and create a situation where the receipt can still be updated. One of three things should happen

A> if the user chooses to use the existing authorization IE keep the void, then the tender should not be applied as a positive

or

B> the duplicate checking should not offer to use the existing transaction when it is a voided transaction.

or

C> as the duplicate issue has been corrected through disabling the cancel button and managing the way PPMserver behaves when using predial , rem out the routine for duplicate checking all together

Resolution:

Voided authorization information is now not stored. This prevents the situation in the issue description from occurring.


Issue ID:

14844

WebTAC ID:

31051

Area:

EFT

Severity:

2 - Serious

Title:

POSres takes more than a minute to determine there is no connection to NETAPI

Description:

Reported Problem:

Due to the limitation in windows that results in NetAPI reporting a valid connection to POSres RPRO takes more than a minute to go into offline eft mode when the router side network connection is lost. Please add a configurable timeout value to an ini file. The time out should not be used if there is no value in INI file variable. IE if the value for time out is not set POSres should determine connectivity normally otherwise if the the timeout value is present then use that value to determine that the connection has been lost.

Resolution:

Added a section and a key to rtishift4.ini which is located in the eft folder:

[System]

OnlineCheckTimeoutSeconds=15

Part of the fix for this bug was put into 8.51 and 8.40 even though they don't support POS Resiliency. If netapi is shut down in the middle of running a transaction, RPro would wait indefinitely for a response from netapi. Now, the user will get an unexpected disconnect error message soon after netapi is shut down.


Multi-Version Tools:

Customer Loyalty Plug-In

Files: CLoyalty.bpl


Issue ID:

14628

WebTAC ID:

29475, 29804, 30582

Area:

Customer Loyalty

Severity:

1 - Critical

Title:

Cloyalty not affecting customer's loyalty value on returns.

Description:

Reported Problem:

First Set up Cloyalty with the below settings. Any returns with these settings will not subtract value back from the UDF field of a customer who has made a purchase. I have found this to be true when reversing a sale for a customer or using a negative value on an item. Also when making a Return type receipt Value is actually added to a customers Loyalty value rather then subtracting.

- I want to use currency to accumulate value.

-Calculate based on a percentage of sales amount.

-Accumulate values for all items.

-Apply redemption value to all items.

-UDF3

-Use 10% as the awarded value.

-Use a Global discount to redeem merchandise.

Resolution:

Loyalty dialog from tender screen will be automatically invoked when making Return receipt.


Issue ID:

14595

WebTAC ID:

29301, 28856, 29804

Area:

Customer Loyalty

Severity:

2 - Serious

Title:

Customer Loyalty accumulating points when item is purchased with points.

Description:

Reported Problem:

When customer purchases an item using their loyalty points they are given loyalty point back for that purchase. Steps to reproduce.

1.) Set up Loyalty with these options

a) I want to use points to accumulate value.

b) Accumulate points as a percentage of the sales amount.

c) I want to use a different number of points for different items.

d) Where do you wants to store accumulated loyalty value? UDF8

e) Enter the percentage of sales amount used for point accumulation. 100

f) Which inventory Aux field? Aux8

G) Discount type? Customer

2.) Create an item with P$= 10$ and AUX8=10 (Points)

3.) Configure RPRO to use SALES TAX

4.) Assign a tax rate of 10.0%

5.) Create a new customer

5.) Start a Receipt with the customer.

6.) Add the item you created.

7.) Tender the receipt. The customer will receive 10 points for the purchase

Up to here every thing is fine

8.) Start another new receipt for the same customer that already has the 10 points in his account

9.) Add the same item you have created but this time the customer will reedem his points to get this item.

10.) Select "Redeem" to redeem the item.

10.) The CLoyalty screen will show you that the customer has 10 points in his account and for the new purchase he will earn 10 points and for the redeeming he will use 10 points11.) Update the receipt.

12.) Now go back to check the customer record to make sure he already have used all his points and UDF8 should be "0" but instead you will see "10".

Resolution:

Loyalty points are now correctly calculated when customer purchases an item using their loyalty points. Loyalty points will not be given for the purchase using redeem points


Vendor Coupons Plug-In

Files: VendorCoupon.bpl


Issue ID:

14230

WebTAC ID:

Area:

Vendor Coupon

Severity:

2 - Serious

Title:

OTS: Vendor Coupons

Description:

Coupons that are buy N items, get 1 free does not work.

(Note, we had incorrect information about the possible ValueCodes for vendor coupons when developing this customization, support for buy N, get 1 free needs to be added.)

Resolution:

Functionality for "Buy N get 1 free" coupon has been fixed. To use a coupon that results in a free item, set the Value Code to have a value of -1 and the Qty to the number of items required to buy INCLUDING the free item.


Stock Audit

Files: SLCC.exe


Issue ID:

14794

WebTAC ID:

Area:

Stock Audit

Severity:

1 - Critical

Title:

Stock Audit not creating open balances when choose to start from RPro backup all qtys zero

Description:

Stock Audit is not creating opening balances if you choose to start from a Retail Pro backup, all quantities are zero.

1) Make a backup of Retail Pro

2) Start SLCC and choose to create opening balance from a backup

3) Point the directory to the Retail\Rpro directoy for the backup

4) once step (3) is done start a new period

5) check the opening balnce it will equal zero.

Resolution:

Issue:

When using a data back up to create an initial open period within stock audit the inventory cost and quantities were zero.

Solution:

Stock Audit has been fixed so that when and opening period is created from a snapshot of inventory the opening cost and company quantity is updated.


Shift4 UTG

Files: Update available from Shift4 using WebChat.exe


Issue ID:

14511

WebTAC ID:

Area:

EFT - Shift4

Severity:

2 - Serious

Title:

UTGstub not communicating Time out or cancel to the Ingenico PinPad.

Description:

Reported Problem:

Create an installation of RPRO that is setup to use Shift4 for Debit.

Run NETAPI and UTG on the file server

Setup to use the Ingenico Encrypt 2100 pinpad on a second RPRO workstation using the UTGstub.

Create a receipt that has an item that costing 3.00

Go into tender select debit

Choose Authorize

Do not swipe the card. (To simulate the customer not being able to find the card)

Wait until the TX engine times out in RPRO. (Time out waiting for response.)

Hit Cancel

Now tender the receipt by cash instead

**Notice that the pinpad has not reset. It is still indicating that it is waiting for the user to swipe the card.**

Now create a new transaction for 5.00 and tender it by Debit

hit authorize

swipe the card enter the pin hit enter on the PinPAD

**The pinpad indicates that the transaction was approved.**

In RPRO you receive "9501 failed to send packet to device"

Typically then in this circumstance the user would choose "cancel" ask the customer to swipe the card again and reenter their pin.

Go to the $$ on the net website and you will see.

0004000054 00000 Thu 10/14/2004 DB 3566xxxxxxxx0006 $3.00 S 001

0004000054 00000 Thu 10/14/2004 DB 3566xxxxxxxx0006 $5.00 S 001

The bug here is the pinpad not resetting when either the time out occurs or when the cancel button is selected.

System Impact:

Huge, there is no way to reverse the transaction in RPRO to credit the card back other than creating a new receipt and that is only if the user catches this while the customer is standing there.

Resolution:

A new UTGstub needs to be downloaded from Shift4 using the WebChat.exe

The problem was that there were several small timeouts in the utg when working with pinpads. For example, a timeout for swiping the card, then another timeout for entering the PIN, etc. Now, there's one overall timeout.

March 23, 2005

Update Release Cycle Retail Pro BTF-Series8.4/8.5/Tools

RPro v8.51 Core

Updated executables Contained in theFebruary RPro v8.51 Core update:

Core Files: Rpro8.exe, ms_ie_d5.bpl, vclie50.bpl, vcl50.bpl, RPRO_API.bpl, rda2.dll, RPro8.sec, RProDB.exe, RproDB.sec, SecAdmin.exe, PPMSERVR.exe, RtiShift4Gift.dll, RtiShift4Debit.dll, RtiShift4Credit.dll, RtiShift4Check.dll, RtiGift.dll, RtiDebit.dll, RtiCredit.dll, RtiCheck.dll, ReceiptRTISchema.xml, CustHistoryRTISchema.xml

Tools:SLCC.exe


Issue ID:

14883

WebTAC ID:

Area:

Vouchers

Severity:

3 - Moderate

Title:

Copying a voucher from a closed period to an open period does not clear the Audit flag

Description:

When copying a voucher from a closed period to an open period, the Audit flag is not cleared. This process is needed in order to work around a current design limitation of Stock Audit. Once copied, the document should be editable.

Resolution:

Issue: Copying a voucher from a closed period to an open period does not clear the Audit flag

Solution: The Audit flag is cleared on all documents (receipts, vouchers, memos and slips) when they are copied.


Issue ID:

14840

WebTAC ID:

31016

Area:

EFT - General

Severity:

1 - Critical

Title:

EFT settings return to DEFAULT value of NONE when connection is lost

Description:

Reported Problem:

Create an installation of RPRO with a mapped drive to an EFT folder where PPM or CPRO is running.

Setup workstation prefs to use the correct Credit option under EFT

Make a transaction to confirm the modem is dialing etc.

Disconnect the mapped drive

Exit out of RPRO

Run the instance of RPRO again and go into another EFT transaction

NOTE the prompt for EFT card type comes up. Go into workstation preferences EFT>Credit. Note it is now set to NONE.

Resolution:

Whenever a user goes to the tender screen, access to the eft folder is checked. If the folder cannot be accessed for any reason, or if there is a problem loading the eft files when first going into the tender screen, an error message is displayed and the eft tender buttons are disabled. The same logic was also put into SO's. The cashier can complete the transaction using a different type of tender.


Issue ID:

14833

WebTAC ID:

Area:

Security Manager

Severity:

2 - Serious

Title:

Communicating De-activated employees to RPro 8 causes Access Violations

Description:

An access violation can be generated when an employee that is a member of an RPro 8 Group is deactivated in V. 9 and communicated back to V. 8

Create an employee in RPro 9 and communicate the employee to RPro 8.

Once in RPro 8 add this employee to a group.

Process back to V. 9 and de-activate the employee.

Communicate the change back to V. 8

After Processing in the changes go to SecAdmin > Groups in V. 8 and Open a group (different from the group that you assigned the now de-activated employee to) and add another employee to the group and save. An Access Violation is shown at this point.

Resolution:

Initial Problem: An access violation is created when deactivating employees in RPro 9 and communicating the change back to RPro 8.

Solution: SecAdmin library was modified to detect when ECM has deleted employees and read data from RtiSec.dat on the fly.


Issue ID:

14803

WebTAC ID:

30257

Area:

EFT - Shift4

Severity:

2 - Serious

Title:

Shift4 credit card transactions duplicating under certain conditions

Description:

Reported Problem:

Based on analysis of trace files from customer combined with the audit trail sent to Shift4 from the client Shift4 has determined that Retail Pro is ignoring responses from Shift4 after an auth has been sent. This in turn causes them to time out and as such is a root cause of a duplicated transaction.

Additional information:

When the user tries to authorize again after the timeout, RPro doesn't always use the same transaction number. We should use the same transaction number again, so we don't defeat Shift4's duplicate checking code.

Resolution:

Programming has changed the way transaction numbers are assigned.

There's a file in the eft folder called shift4sn.dat which holds the serial numbers that are used to as transaction numbers. There used to just be one serial number that was shared by all workstations, but now each workstation has it's own serial number. Each serial number is in the range 1 to 999999. The transaction number consists of a 2 digit workstation number followed by the serial number for that workstation. Only if the transaction is approved is the serial number incremented. On the receipt tender screen, the transaction number is displayed in the reference number field (as before).


Issue ID:

14794

WebTAC ID:

Area:

Stock Audit

Severity:

1 - Critical

Title:

Stock Audit not creating open balances when choose to start from RPro backup all qtys zero

Description:

Stock Audit is not creating opening balances if you choose to start from a Retail Pro backup, all quantities are zero.

1) Make a backup of Retail Pro

2) Start SLCC and choose to create opening balance from a backup

3) Point the directory to the Retail\Rpro directoy for the backup

4) once step (3) is done start a new period

5) check the openeing balnce it will equal zero.

Resolution:

Issue:

When using a data back up to create an initial open period within stock audit the inventory cost and quantities were zero.

Solution:

Stock Audit has been fixed so that when and opening period is created from a snapshot of inventory the opening cost and company quantity is updated.


Issue ID:

14780

WebTAC ID:

30736

Area:

EFT - PPM

Severity:

3 - Moderate

Title:

PPMserver Times out dialog during upload of large batch

Description:

Reported Problem:

The time out put in place for the credit card dialog is timing out before PPMserver is done uploading the batch. This is causing the dialog to give the error "time out" while PPMserver is still posting the batch. See attached log.

Steps to replicate.

Select upload

You will see Connected

then see Settling batch ###

after about a minute you get Timed out

click OK

Queued at the server message is displayed for about a minute until the cancel button can be hit, Brings you back to the the Upload screen

If you try to settle again you get no batches to settle

System Impact:

The user will be confused by this.

Resolution:

The PPMServer will now stay open until the batch is finished processing. No timeout errors should be reported.


Issue ID:

14768

WebTAC ID:

30735

Area:

EFT - PPM

Severity:

2 - Serious

Title:

Duplicate checking in PPM creates a possible problem with void transactions

Description:

Reported Problem:

1> Create a transaction with a credit card and authorize it.

2> Now before updating the transaction void the authorizations by deleting the authorized amount in the tender window.

3> Now rerun the same amount using the same card and exp date etc.

Note you get the "duplicate authorization" prompt.

The options are to use the existing authorization or create a new authorization. If you choose to use the existing authorization the system does not go out and get a good authorization. It simply keeps the voided one that is in the batch.

This is bad for the client as it is confusing to the cashiers at POS. What happens is the cashier not knowing can select to use the previous auth and create a situation where the receipt can still be updated. One of three things should happen:

A> if the user chooses to use the existing authorization IE keep the void, then the tender should not be applied as a positive

or

B> the duplicate checking should not offer to use the existing transaction when it is a voided transaction.

or

C> as the duplicate issue has been corrected through disabling the cancel button and managing the way PPMserver behaves when using predial , rem out the routine for duplicate checking all together

Resolution:

Voided authorization information is now not stored. This prevents the situation in the issue description from occurring.


Issue ID:

14694

WebTAC ID:

29840, 30820

Area:

Sales Orders

Severity:

1 - Critical

Title:

SO deposit created when not tendered.

Description:

Reported Problem:

With A Deposit amount required on an SO a user can back out of an SO deposit and cause a receipt to be made. Steps to Reproduce.

1.) System Preferences > Require a 10 % deposit on SO's.

2.) Make a SO then Save, The user will be propted to leave a deposit.

3.) In the Deposit Screen do not tender and just select Back from the side menu.

4.) Back in the SO Screen Select Save again and the user will once again be brought to the Deposit screen and a new deposit will have been started.

5.) Once again in the Deposit Screen do not tender and just select Back from the side menu.

6.) Again back in the SO Screen Select Save again and the user will once again be brought to the Deposit screen and another new deposit will have been started.

7.) Do not tender and select the second deposit row with your mouse.

8.) Select the RPRO buttion in the upper corner. This will back you out to the Retail pro home screen, with out a deposit being made.

9.) Now check former SO's there will have been a SO made. And in former receipts there will be a deposit receipt for the so tendered using store credit.

Resolution:

The deposit on an SO isn't removed when the back button is pressed while in the deposit screen. This would result in a customer receiving unearned store credit in certain situations. Now the deposit is removed if the back button is selected prior to tendering the deposit.


Issue ID:

14844

WebTAC ID:

31051

Area:

EFT

Severity:

2 - Serious

Title:

POSres takes more than a minute to determine there is no connection to NETAPI

Description:

Reported Problem:

Due to the limitation in windows that results in NetAPI reporting a valid connection to POSres RPRO takes more than a minute to go into offline eft mode when the router side network connection is lost. Please add a configurable timeout value to an ini file. The time out should not be used if there is no value in INI file variable. IE if the value for time out is not set POSres should determine connectivity normally otherwise if the the timeout value is present then use that value to determine that the connection has been lost.

Resolution:

Added a section and a key to rtishift4.ini which is located in the eft folder:

[System]

OnlineCheckTimeoutSeconds=15

Part of the fix for this bug was put into 8.51 and 8.40 even though they don't support POS Resiliency. If netapi is shut down in the middle of running a transaction, RPro would wait indefinitely for a response from netapi. Now, the user will get an unexpected disconnect error message soon after netapi is shut down.


RPro v8.40 Core

Updated executables Contained in theFebruary RPro v8.40 Core update:

Core Files: Rpro8.exe, vclie50.bpl, vcl50.bpl, RPRO_API.bpl, rda2.dll, RPro8.sec, SecAdmin.exe, PPMSERVR.exe, RtiShift4Debit.dll, RtiShift4Credit.dll, RtiShift4Check.dll, RtiDebit.dll, RtiCredit.dll, RtiCheck.dll

Tools: SLCC.exe


Issue ID:

14833

WebTAC ID:

Area:

Security Manager

Severity:

2 - Serious

Title:

Communicating De-activated employees to RPro 8 causes Access Violations

Description:

An access violation can be generated when an employee that is a member of an RPro 8 Group is deactivated in V. 9 and communicated back to V. 8

Create an employee in RPro 9 and communicate the employee to RPro 8.

Once in RPro 8 add this employee to a group.

Process back to V. 9 and de-activate the employee.

Communicate the change back to V. 8

After Processing in the changes go to SecAdmin > Groups in V. 8 and Open a group (different from the group that you assigned the now de-activated employee to) and add another employee to the group and save. An Access Violation is shown at this point.

Found Internally by Alexey

Resolution:

Initial Problem: An access violation is created when deactivating employees in RPro 9 and communicating the change back to RPro 8.

Solution: SecAdmin library was modified to detect when ECM has deleted employees and read data from RtiSec.dat on the fly.


Issue ID:

14803

WebTAC ID:

30257

Area:

EFT - Shift4

Severity:

2 - Serious

Title:

Shift4 credit card transactions duplicating under certain conditions

Description:

Reported Problem:

Based on analysis of trace files from customer combined with the audit trail sent to Shift4 from the client Shift4 has determined that Retail Pro is ignoring responses from Shift4 after an auth has been sent. This in turn causes them to time out and as such is a root cause of a duplicated transaction.

Additional information:

When the user tries to authorize again after the timeout, RPro doesn't always use the same transaction number. We should use the same transaction number again, so we don't defeat Shift4's duplicate checking code.

Resolution:

Programming has changed the way transaction numbers are assigned.

There's a file in the eft folder called shift4sn.dat which holds the serial numbers that are used to as transaction numbers. There used to just be one serial number that was shared by all workstations, but now each workstation has it's own serial number. Each serial number is in the range 1 to 999999. The transaction number consists of a 2 digit workstation number followed by the serial number for that workstation. Only if the transaction is approved is the serial number incremented. On the receipt tender screen, the transaction number is displayed in the reference number field (as before).


Issue ID:

14780

WebTAC ID:

30736

Area:

EFT - PPM

Severity:

3 - Moderate

Title:

PPMserver Times out dialog during upload of large batch

Description:

Reported Problem:

The time out put in place for the credit card dialog is timing out before PPMserver is done uploading the batch. This is causing the dialog to give the error "time out" while PPMserver is still posting the batch. See attached log.

Steps to replicate.

Select upload

You will see Connected

then see Settling batch ###

after about a minute you get Timed out

click OK

Queued at the server message is displayed for about a minute until the cancel button can be hit, Brings you back to the the Upload screen

If you try to settle again you get no batches to settle

Upon reviewing the log the batch is settled correctly but the

See attached log.

System Impact:

The user will be confused by this.

Resolution:

The PPMServer will now stay open until the batch is finished processing. No timeout errors should be reported.


Issue ID:

14768

WebTAC ID:

30735

Area:

EFT - PPM

Severity:

2 - Serious

Title:

Duplicate checking in PPM creates a possible problem with void transactions

Description:

Reported Problem:

1> Create a transaction with a credit card and authorize it.

2> Now before updating the transaction void the authorizations by deleting the authorized amount in the tender window.

3> Now rerun the same amount using the same card and exp date etc.

Note you get the "duplicate authorization" prompt.

The options are to use the existing authorization or create a new authorization. If you choose to use the existing authorization the system does not go out and get a good authorization. It simply keeps the voided one that is in the batch.

This is bad for the client as it is confusing to the cashiers at POS. What happens is the cashier not knowing can select to use the previous auth and create a situation where the receipt can still be updated. One of three things should happen

A> if the user chooses to use the existing authorization IE keep the void, then the tender should not be applied as a positive

or

B> the duplicate checking should not offer to use the existing transaction when it is a voided transaction.

or

C> as the duplicate issue has been corrected through disabling the cancel button and managing the way PPMserver behaves when using predial , rem out the routine for duplicate checking all together

Resolution:

Voided authorization information is now not stored. This prevents the situation in the issue description from occurring.


Issue ID:

14844

WebTAC ID:

31051

Area:

EFT

Severity:

2 - Serious

Title:

POSres takes more than a minute to determine there is no connection to NETAPI

Description:

Reported Problem:

Due to the limitation in windows that results in NetAPI reporting a valid connection to POSres RPRO takes more than a minute to go into offline eft mode when the router side network connection is lost. Please add a configurable timeout value to an ini file. The time out should not be used if there is no value in INI file variable. IE if the value for time out is not set POSres should determine connectivity normally otherwise if the the timeout value is present then use that value to determine that the connection has been lost.

Resolution:

Added a section and a key to rtishift4.ini which is located in the eft folder:

[System]

OnlineCheckTimeoutSeconds=15

Part of the fix for this bug was put into 8.51 and 8.40 even though they don't support POS Resiliency. If netapi is shut down in the middle of running a transaction, RPro would wait indefinitely for a response from netapi. Now, the user will get an unexpected disconnect error message soon after netapi is shut down.


Multi-Version Tools:

Customer Loyalty Plug-In

Files: CLoyalty.bpl


Issue ID:

14628

WebTAC ID:

29475, 29804, 30582

Area:

Customer Loyalty

Severity:

1 - Critical

Title:

Cloyalty not affecting customer's loyalty value on returns.

Description:

Reported Problem:

First Set up Cloyalty with the below settings. Any returns with these settings will not subtract value back from the UDF field of a customer who has made a purchase. I have found this to be true when reversing a sale for a customer or using a negative value on an item. Also when making a Return type receipt Value is actually added to a customers Loyalty value rather then subtracting.

- I want to use currency to accumulate value.

-Calculate based on a percentage of sales amount.

-Accumulate values for all items.

-Apply redemption value to all items.

-UDF3

-Use 10% as the awarded value.

-Use a Global discount to redeem merchandise.

Resolution:

Loyalty dialog from tender screen will be automatically invoked when making Return receipt.


Issue ID:

14595

WebTAC ID:

29301, 28856, 29804

Area:

Customer Loyalty

Severity:

2 - Serious

Title:

Customer Loyalty accumulating points when item is purchased with points.

Description:

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)