0039344: A Javascript error is shown when check stock button is tap

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0039344

Retail Modules

Web POS

public

2018-09-24 14:10

2018-09-26 09:32

Reporter

javierRodriguez

Assigned To

ranjith_qualiantech_com

Priority

immediate

Severity

major

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

RR18Q3

Fixed in Version

RR18Q4

Merge Request Status

Review Assigned To

marvintm

OBNetwork customer

Support ticket

Regression level

Production - QA Approved

Regression date

2018-04-24

Regression introduced in release

RR18Q3

Regression introduced by commit

https://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/558cde6e982b [^]

Triggers an Emergency Pack

Summary

0039344: A Javascript error is shown when check stock button is tap

Description

When you have a product in the ticket, and you try to check stock with the corresponding button, a Javascript error appear.

Steps To Reproduce

-Go to livebuilds
-Login in ERP (18Q3 version)
-In Organization, set 2 warehouses with different priorities (1 and 2)
-Generate stock for the warehouse 2, for a product, and make sure that this product doesn't have stock in warehouse 1
-Login in WebPOS (18Q3)
-Go to BROWSER view and select this product
-Tap the product in your ticket
-Tap check stock button and see the js error

Proposed Solution

- StoreDetailedStock class should be modified, to take into account that a parameter "warehouse" may be specified. If it is not specified, the class should work as before, but if it is specified then the query should return the stock of the specified product in the specified warehouse.
- Then, in the request to this class that happens when the user taps on "Check stock", the main store warehouse should be specified as this parameter

With these two changes, the request should return no values in this case, and then stock should be considered "0" automatically, which is the desired result, and the js error will not happen anymore.

Additional Information