Openbravo Issue Tracking System - Retail Modules
View Issue Details
0028788Retail ModulesWeb POSpublic2015-01-27 18:142019-05-29 09:26
aaroncalero 
marvintm 
normalminorhave not tried
closedno change required 
5
 
 
No
0028788: The OBPOS_PreCustomerSave should include the customer attributes as an argument
The OBPOS_PreCustomerSave should include the customer attributes as an argument.
Currently there is no easy or intuitive way to access the attributes of the customer. In order to access attributes, you have to navigate from the window to the attribute lines, and from there, to the specific attribute (e.g. in order to access the 'name' of the customer: me.$.customerAttributes.$.line_customerName.$.newAttribute.$.customerName.getValue())
Implement the OBPOS_PreCustomerSave hook. Verify that the available parameters are: the buttons header, the save button itself, the edit/new customer window, and a boolean and a string that always contain the same values.
Add a sixth parameter to the hook on the last position (to avoid api changes) including all parameters taken from the edit/create window
No tags attached.
Issue History
2015-01-27 18:14aaroncaleroNew Issue
2015-01-27 18:14aaroncaleroAssigned To => marvintm
2015-01-27 18:14aaroncaleroTriggers an Emergency Pack => No
2019-05-29 09:26aaroncaleroNote Added: 0112220
2019-05-29 09:26aaroncaleroStatusnew => closed
2019-05-29 09:26aaroncaleroResolutionopen => no change required

Notes
(0112220)
aaroncalero   
2019-05-29 09:26   
No longer required, there is now an OBPOS_BeforeCustomerSave hook which includes the data retrieved from the customer form