0035118: Wiki explains that default behavior for discount key of the keyboard is Discretionary discounts but old discounts is active

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #35118		[ All Revisions ] [ Back to Issue ]
Summary	0035118: Wiki explains that default behavior for discount key of the keyboard is Discretionary discounts but old discounts is active

Revision	2017-02-01 10:12 by guilleaer
Steps To Reproduce	Create a clean instance of retail (including sample data) You will see that the preference which enables this behavior is the preference "OBPOS_retail.discountkeyboard" but it is not part of the source data (check in ad_preference xml file [src-db/database/sourcedata/AD_PREFERENCE.xml]) there is nothing there related to this preference. There is one entry in the retail sample data which set this preference to True, but it should be removed since it is not part of a default installation. delete from ad_preference where property = 'OBPOS_retail.discountkeyboard' (one line should be removed) Having this configuration, open web POS. You will see that the behavior of the button is the "basic" discount which is not the expected. however, if you execute this query [ INSERT INTO AD_PREFERENCE (AD_PREFERENCE_ID,AD_CLIENT_ID,AD_ORG_ID,ISACTIVE,CREATED,CREATEDBY,UPDATED,UPDATEDBY, AD_WINDOW_ID,AD_USER_ID,ATTRIBUTE,VALUE,PROPERTY,ISPROPERTYLIST,VISIBLEAT_CLIENT_ID, VISIBLEAT_ORG_ID,VISIBLEAT_ROLE_ID,SELECTED,AD_MODULE_ID) VALUES (get_uuid(),'0','0','Y',now(),'100',now(),'100', null,null,null,'Y','OBPOS_retail.discountkeyboard','Y',null,null, null,'N',null) ] the expected behavior will happen. Apart from that, there is a modulescript (very old) which creates this preference with value 'N' for instances which are not new. This module script is not doing nothing right now, because the behavior of Web POS is the same when this preference exists with 'N' value and when it does not exist.

Revision	2017-02-01 10:11 by guilleaer
Steps To Reproduce	Create a clean instance of retail (including sample data) You will see that the preference which enables this behavior is the preference "OBPOS_retail.discountkeyboard" but it is not part of the source data (check in ad_preference xml file [src-db/database/sourcedata/AD_PREFERENCE.xml]) there is nothing there related to this preference. There is one entry in the retail sample data which set this preference to True, but it should be removed since it is not part of a default installation. delete from ad_preference where property = 'OBPOS_retail.discountkeyboard' (one line should be removed) Having this configuration, open web POS. You will see that the behavior of the button is the "basic" discount which is not the expected. however, if you execute this query [ INSERT INTO AD_PREFERENCE (AD_PREFERENCE_ID,AD_CLIENT_ID,AD_ORG_ID,ISACTIVE,CREATED,CREATEDBY,UPDATED,UPDATEDBY,AD_WINDOW_ID,AD_USER_ID,ATTRIBUTE,VALUE,PROPERTY,ISPROPERTYLIST,VISIBLEAT_CLIENT_ID,VISIBLEAT_ORG_ID,VISIBLEAT_ROLE_ID,SELECTED,AD_MODULE_ID) VALUES (get_uuid(),'0','0','Y',now(),'100',now(),'100',null,null,null,'Y','OBPOS_retail.discountkeyboard','Y',null,null,null,'N',null) ] the expected behavior will happen. Apart from that, there is a modulescript (very old) which creates this preference with value 'N' for instances which are not new. This module script is not doing nothing right now, because the behavior of Web POS is the same when this preference exists with 'N' value and when it does not exist.

Revision	2017-02-01 10:03 by guilleaer
Steps To Reproduce	Create a clean instance of retail (including sample data) You will see that the preference which enables this behavior is the preference "OBPOS_retail.discountkeyboard" but it is not part of the source data (check in ad_preference xml file [src-db/database/sourcedata/AD_PREFERENCE.xml]) There is one preference in the retail sample data which set this preference to True, but it should be removed since it is not part of a default installation. delete from ad_preference where property = 'OBPOS_retail.discountkeyboard' (one line should be removed) Having this configuration, open web POS. You will see that the behavior of the button is the "basic" discount which is not the expected. Apart from that, there is a modulescript (very old) which creates this preference with value 'N' for instances which are not new. This module script is not doing nothing right now, because the behavior of Web POS is the same when this preference exists and when it does not.

Revision	2017-02-01 10:00 by guilleaer
Steps To Reproduce	Create a clean instance of retail (including sample data) You will see that the preference which enables this behavior is the preference "OBPOS_retail.discountkeyboard" but it is not part of the source data (check in ad_preference xml file [src-db/database/sourcedata/AD_PREFERENCE.xml]) There is one preference in the retail sample data which set this preference to True, but it should be removed since it is not part of a default installation. delete from ad_preference where property = 'OBPOS_retail.discountkeyboard' (one file should be removed) Having this configuration, open web POS. You will see that the behavior of the button is the "basic" discount which is not the expected. Apart from that, there is a modulescript (very old) which creates this preference with value 'N' for instances which are not new. This module script is not doing nothing right now, because the behavior of Web POS is the same when this preference exists and when it does not.