0028788: The OBPOS_PreCustomerSave should include the customer attributes as an argument

Description

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())

Steps To Reproduce

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.

Proposed Solution

Add a sixth parameter to the hook on the last position (to avoid api changes) including all parameters taken from the edit/create window

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

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

Issue History
Date Modified	Username	Field	Change
2015-01-27 18:14	aaroncalero	New Issue
2015-01-27 18:14	aaroncalero	Assigned To	=> marvintm
2015-01-27 18:14	aaroncalero	Triggers an Emergency Pack	=> No
2019-05-29 09:26	aaroncalero	Note Added: 0112220
2019-05-29 09:26	aaroncalero	Status	new => closed
2019-05-29 09:26	aaroncalero	Resolution	open => no change required