Project:
View Revisions: Issue #35718 | [ Back to Issue ] | ||
Summary | 0035718: API Break on Purchase Order Report Modifications project (try-api 4815) | ||
Revision | 2017-05-25 13:15 by airaceburu | ||
Steps To Reproduce | Look at: https://ci.openbravo.com/job/try-api/4908/consoleText [^] org.openbravo.erpCommon.reference: 99.43% good, 0.56% missing |
||
Revision | 2017-05-25 13:15 by airaceburu | ||
Steps To Reproduce | Look at: https://ci.openbravo.com/job/try-api/4815/consoleText [^] [checkAPI] 10647 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 10651 ERROR - Errors in API data validation [checkAPI] 10654 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 10658 ERROR - Removed row from table AD_PROCESS - ID: 800171 [checkAPI] 10662 ERROR - Removed row from table AD_PROCESS_PARA - ID: 800054 [checkAPI] 10665 ERROR - Removed row from table AD_PROCESS_PARA - ID: 800055 [checkAPI] 10669 ERROR - Removed row from table AD_PROCESS_PARA - ID: 800056 [checkAPI] 10672 ERROR - Removed row from table AD_PROCESS_PARA - ID: 800058 [checkAPI] 10676 ERROR - Removed row from table AD_PROCESS_PARA - ID: 800059 [checkAPI] 10679 ERROR - Removed row from table AD_PROCESS_PARA - ID: 800060 [checkAPI] 10683 ERROR - Removed row from table AD_PROCESS_PARA - ID: 3AC22B0F80264CF09D52044F198C75BD |
||
Revision | 2017-05-25 13:15 by airaceburu | ||
Description | API Break due to the disabling of "Purchase Order Report" "Report and Process" due to a refactor moving it to a "Process Definition" There risk on this change is very low, is not very common to customize a report. Is more frequent to create a new jrxml. Although is very unlikely to be affected by this change, an affected developer could either extract the ad_process with its changes to a custom module, or build his changes in top of the new technology. |
||
Revision | 2017-05-25 13:15 by airaceburu | ||
Description | API Break due to the displacement of "Purchase Order Report" from a "Report and Process" to a "Process Definition" There risk on this change is very low, is not very common to customize a report. Is more frequent to create a new jrxml. Although is very unlikely to be affected by this change, an affected developer could either extract the ad_process with its changes to a custom module, or build his changes in top of the new technology. |
Copyright © 2000 - 2009 MantisBT Group |