Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #36966 Back to Issue ]
Summary 0036966: When entering the attribute value, the user shouldn't need to follow internal Openbravo format
Revision 2017-09-27 18:22 by marvintm
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.
Revision 2017-09-27 17:58 by marvintm
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 distributor, 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.
Revision 2017-09-27 17:58 by marvintm
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 to the user.

In some cases the codes will be generated and the products labelled directly by the distributor, 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.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker