Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0034552Retail ModulesWeb POSpublic2016-11-17 10:352016-12-12 09:27
Reporterjorgewederago 
Assigned Toranjith_qualiantech_com 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR17Q1 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0034552: When building a payment provider you cannot assign bodyButtons to it.
DescriptionWhen building a payment provider you cannot assign bodyButtons to it. However, if you add them to the bodyContent they are created properly but below the component an empty bodyButtons component will appear and you cannot assing values to it
These popups usually are able to handle that kind of component.
Steps To ReproduceCreate a new paymentProvider and add bodyButtons to it
Proposed SolutionTo create bodyButtons in the same way as bodyContent is created, dynamically.

Another solution could be to hide the inherited bodyButtons component.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-11-17 10:35jorgewederagoNew Issue
2016-11-17 10:35jorgewederagoAssigned To => Retail
2016-11-17 10:35jorgewederagoResolution time => 1481151600
2016-11-17 10:35jorgewederagoTriggers an Emergency Pack => No
2016-12-01 15:22ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2016-12-01 15:22ranjith_qualiantech_comStatusnew => scheduled
2016-12-09 09:06hgbotCheckin
2016-12-09 09:06hgbotNote Added: 0092230
2016-12-09 09:07hgbotCheckin
2016-12-09 09:07hgbotNote Added: 0092231
2016-12-09 09:07hgbotStatusscheduled => resolved
2016-12-09 09:07hgbotResolutionopen => fixed
2016-12-09 09:07hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/5f34bab5db4f2b91a4f9a6399f14e9235debc62e [^]
2016-12-12 09:27marvintmReview Assigned To => marvintm
2016-12-12 09:27marvintmStatusresolved => closed
2016-12-12 09:27marvintmFixed in Version => RR17Q1

Notes
(0092230)
hgbot   
2016-12-09 09:06   
Repository: erp/pmods/org.openbravo.mobile.core
Changeset: 7d025e6ba437a8319ad1f154271e045d0c9c1df3
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Fri Dec 09 13:35:19 2016 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/rev/7d025e6ba437a8319ad1f154271e045d0c9c1df3 [^]

Related to issue 34552 : Validating bodyButton in ModalAction

* In ModalAction initComponents, bodyButtons should be created if it defined in subclass

---
M web/org.openbravo.mobile.core/source/component/ob-commonbuttons.js
---
(0092231)
hgbot   
2016-12-09 09:07   
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 5f34bab5db4f2b91a4f9a6399f14e9235debc62e
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Fri Dec 09 13:36:00 2016 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/5f34bab5db4f2b91a4f9a6399f14e9235debc62e [^]

Fixed issue 34552 : Removing bodyButtons from modalpayment

* For ModalPayments, buttons are rendered inside bodyContent itself. So bodyButtons is not needed

---
M web/org.openbravo.retail.posterminal/js/components/modalpayment.js
---