0036966: When entering the attribute value, the user shouldn't need to follow internal Openbravo format

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0036966

Retail Modules

Web POS

public

2017-09-27 17:57

2018-06-26 11:42

Reporter

marvintm

Assigned To

guilleaer

Priority

normal

Severity

major

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

Fixed in Version

RR18Q1

Merge Request Status

Review Assigned To

marvintm

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0036966: When entering the attribute value, the user shouldn't need to follow internal Openbravo format

Description

When support for attributes is enabled, the Web POS prompts the user to add the attribute values whenever a product which has associated attribute set is added to the ticket.

However, as of now the value needs to follow internal Openbravo rules (such as starting with # if it's serial number, or L if it's lot), and this is confusing for the user.

In some cases the codes will be generated and the products labelled directly by the company using Openbravo, but in many cases, the codes may be scanned directly from the original goods, and therefore it's quite a hassle for the user to have to correct these codes.

Ideally, the user should only have to scan the value as it is, and Openbravo should handle the conversion to its internal format automatically.

Steps To Reproduce

Use Support for Attributes functionality, and verify that the serial number cannot be entered as it is, and # is required for the Web POS to recognize it properly.

Proposed Solution

Additional Information

Tags

No tags attached.

Relationships

depends on	backport	0037062	RR17Q3.1	closed	guilleaer	When entering the attribute value, the user shouldn't need to follow internal Openbravo format
depends on	backport	0037063	RR17Q4	closed	marvintm	When entering the attribute value, the user shouldn't need to follow internal Openbravo format
related to	defect	0037065		new	Retail	Test to verify attributes functionality are pending
related to	defect	0037256	RR18Q1	closed	guilleaer	Text input where attribute values are entered in Web POS should remove spaces
related to	design defect	0037240	RR18Q1	closed	gorka_gil	Layaways and attributes. Allow to work without attributes until layaway is completely paid
blocks	defect	0037308		closed	guilleaer	[Support For Attributes]: Attribute set instance without stock selected when there is stock with other instance and same value

Attached Files

Issue History

Date Modified

Username

Field

Change

2017-09-27 17:57

marvintm

New Issue

2017-09-27 17:57

marvintm

Assigned To

=> Retail

2017-09-27 17:57

marvintm

Triggers an Emergency Pack

=> No

2017-09-27 17:57

marvintm

Summary

Attributes specification shouldn't require the user to follow Openbravo specific format => When entering the attribute value, the user shouldn't need to follow Openbravo specific format

2017-09-27 17:58

marvintm

Summary

When entering the attribute value, the user shouldn't need to follow Openbravo specific format => When entering the attribute value, the user shouldn't need to follow internal Openbravo format

2017-09-27 17:58

marvintm

Description Updated

bug_revision_view_page.php?rev_id=16007#r16007

2017-09-27 18:22

marvintm

Description Updated

bug_revision_view_page.php?rev_id=16008#r16008

2017-10-10 13:27

guilleaer

File Added: stockvalidation.diff

2017-10-10 13:27