Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Serial

Dev IDIssue TrackerDescription
116584 N.A.

16584 POS Bill printing  or reprinting action generating error in formula

Module:

POS – Normal POS POS – POS as Collection Centre POS – POS as Delivery Slip

Reported Version:

1.107.0

Scenario:

  1. Create a POS Bill
  2. Attempt to print the POS Bill, error is thrown
  3. Attempt to reprint the POS Bill, error is thrown
219214N.A.

19214 In Plutus integrated POS environment, name of the bank, which had the EDC installed, was reflecting wrongly in the report

Module:

POS – Normal POS
POS – POS as Collection Centre
POS – POS as Delivery Slip

Reported Version:

1.110.0

Scenario:

  1. Create a POS Bill with MOP credit card
  2. Check in report the bank name is coming wrong
319253N.A.

19253 Software was not opening due to space being taken up by huge size of unnecessary SMTP Service logs

Module:

GINESYS Launchpad – Mail Notification - Logs

Reported Version:

1.107.0

Scenario:

In case of Occurrence job processing, GINESYS SMTP Service was generating a log even if there was no occurrence events found in the table.

419337N.A.

19337 Sales invoice report through mail was reflecting wrong item quantity and site information

Module:

GINESYS Launchpad – Mail Notification 

Reported Version:

1.108.0

Scenario:

Whenever the sales invoice report was sent through mail, it was reflecting wrong item quantity and site information (multiple sites were reflected for each entry).

519508N.A.

19508 In sales return email report, short/excess quantity was not showing correctly

Module:

GINESYS Launchpad – Mail Notification 

Reported Version:

1.108.0

Scenario:

Whenever the sales invoice report was sent through mail, it was reflecting wrong short/excess quantity.

619489N.A.

19489 GINESYS POS was not working after scanning any barcode (Invalid or Null) which has no records in database 

Module:

POS – Back Office – Store control – Barcode Printing 

Reported Version:

1.107.0

Scenario:

  1. Go to POS Back Office > Store control > Barcode Printing
  2. Enter any invalid barcode
  3. The screen turns white
719490N.A.

19490 Error was being displayed while voiding the POS bill

Module:

POS – Normal POS
POS – POS as Collection Centre
POS – POS as Delivery Slip

Reported Version:

 1.107.0

Scenario:

  1. Create a POS bill.
  2. Tag a customer with mobile number.
  3. Void the bill.
  4. The following error was shown – “Failed to convert parameter value from a Decimal to a Int32”
817890N.A.

17890 Points were not getting earned while billing with the same card

Module:

POS – Normal POS
POS – POS as Collection Centre
POS – POS as Delivery Slip

Reported Version:

1.108.0

Scenario:

  1. Create a Manual LP card where attach point benefit and don't specify opening point.
  2. Assign the card to a customer and allocate to a store.
  3. Create a POS bill with that customer (as well as the card).
  4. Sync the bill to HO.
  5. Sync from Retail to Web.
  6. Check the loyalty points of the customer from store. Points earned by the customer on that card are not displayed.
918289N.A.

18289 In Sample Testing tool, when promo allocation group is selected, a promo with a higher priority is getting activated irrespective of applicable activation date

Module:

GINESYS Web – Retail Management – Promotion – Sample Testing

Reported Version:

1.108.0 

Scenario:

If there were two promotions having same set of assortments with different activation date, higher priority promotion was getting resolved irrespective of its activation date.

For ex: Promo Group A was having two promotions:
P1 & P2 with same assortment set.
P1 starts from 16-06-2016 ends on 30-06-2016 with priority 2
P2 starts from 10-06-2016 ends on 14-06-2016 with priority 1

Promo Allocation Group is selected with Sale Start date as 11-06-2016
Promo resolution date is 13-06-2016
P1 was getting resolved instead of P2.

 

...