Project:
| View Revisions: Issue #25449 | [ Back to Issue ] | ||
| Summary | 0025449: int-3.0-api fails because I need to change 2 columns definition | ||
| Revision | 2014-01-31 12:27 by jecharri | ||
| Description | Due to this issue https://issues.openbravo.com/view.php?id=24685 [^] I have to make an api change. Below you will find the changeset and api change: -https://code.openbravo.com/erp/devel/try/rev/48befdcb4245 [^] -http://builds.openbravo.com/view/try/job/try-api/1728/console [^] -The changes are the followings: I have changed the definition of column processing to column processed and the definition of processed to processing. Apart from that, I have created a sqllofic field to be able to filter in the grid view by column "Processed" -The risk of this api change is medium because of the following reason: The problem was that button "Process/Unprocess" expense sheet was using column processing and it was wrong, because the button needs to change from processing to unprocess when processed has value 'Y' and the only way to do that is using processed column. Apart from that the risk is medium because both columns only allow to save values 'Y' or 'N' but there are modules that are already using and we should do little changes |
||
| Revision | 2014-01-09 10:47 by jecharri | ||
| Description | Due to this issue https://issues.openbravo.com/view.php?id=24685 [^] I have to make an api change. Below you will find the changeset and api change: -https://code.openbravo.com/erp/devel/try/rev/3301738fd11f [^] -http://builds.openbravo.com/view/try/job/try-api/1728/console [^] -The changes are the followings: I have changed the definition of column processing to column processed and the definition of processed to processing -The risk of this api change is low because of the following reason: The problem was that button "Process/Unprocess" expense sheet was using column processing and it was wrong, because the button needs to change from processing to unprocess when processed has value 'Y' and the only way to do that is using processed column. Apart from that the risk is medium because both columns only allow to save values 'Y' or 'N'. |
||
| Revision | 2014-01-09 10:40 by jecharri | ||
| Description | Due to this issue https://issues.openbravo.com/view.php?id=24685 [^] I have to make an api change. Below you will find the changeset and api change: -https://code.openbravo.com/erp/devel/try/rev/3301738fd11f [^] -http://builds.openbravo.com/view/try/job/try-api/1728/console [^] -The changes are the followings: I have changed the definition of column processing to column processed and the definition of processed to processing -The risk of this api change is low because of the following reason: The problem was that button "Process/Unprocess" expense sheet was using column processing and it was wrong, because the button needs to change from processing to unprocess when processed has value 'Y' and the only way to do that is using processed column. Apart from that the risk is low because both columns only allow to save values 'Y' or 'N'. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |