Project:
| View Revisions: Issue #41320 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0041320: API Change: Remove Old Payment Monitor used in Openbravo 2.50 | ||
| Revision | 2019-07-08 21:29 by AtulOpenbravo | ||
| Description | Delete Old Payment Monitor used in Openbravo 2.50 consists of below candidates removal. - Remove AD_PROCESS for PaymentMonitor & InvoicePaymentMonitor - Remove AD_MODEL_OBJECT, AD_MODEL_OBJECT_MAPPING for InvoicePaymentMonitor - Remove java class for PaymentMonitor, PaymentMonitorProcess, InvoicePaymentMonitor, InvoicePaymentMonitor.html, InvoicePaymentMonitor.xml - Remove UPDATEPAYMENTMONITOR column from table C_INVOICE, AD_FIELD used in Purchase and Sales Invoice Header Tab, its AD_COLUMN & AD_ELEMENT record, deletes PROPERTY_UPDATEPAYMENTMONITOR property, isUpdatePaymentMonitor() & setUpdatePaymentMonitor() method of Invoice class. The risk of this change is very low as Update Payment Monitor button in Sales / Purchase Invoice header is not used because of display logic based on a preference PaymentMonitor having value '' and Processed='Y' but it is set with value as Yes. so the condition is never met. Hence the class PaymentMonitor and classes InvoicePaymentMonitor, PaymentMonitorProcess using PaymentMonitor method is not used anymore so the fields in Sales/Purchase Invoice header tab is safe to remove. Column UPDATEPAYMENTMONITOR from C_Invoice could be safely removed by managing removal of its values in Sample Data (Core, AWO, Retail). |
||
| Revision | 2019-07-08 20:52 by AtulOpenbravo | ||
| Description | Remove Old Payment Monitor used in Openbravo 2.50 | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |