Project:
| View Revisions: Issue #27614 | [ Back to Issue ] | ||
| Summary | 0027614: API Break on Reconciliation Project (try-api 673) | ||
| Revision | 2014-09-24 11:06 by Sandrahuguet | ||
| Description | Look at: * API Break due to following columns have been marked as mandatory and not null in Fin_Finacc_Transaction table: - statementdate - dateacct - trxtype * Also due to a new constraint in Fin_Finacc_Transaction table: Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) * The size of table AD_COLUMN Column ENTITY_ALIAS has changed from 60 to 2000 * Not Allowed insertions in AD_PROCESS_PARA table. ID: 993E5D1AE89649648DFE15C27360CD52 is a false positive. Action param now is created in application dictionary previously is hardcoded. Risk api-changes: * statementdate: There should not be any transaction without Transaction Date. Before this project is was not possible to add transactions with this field empty from the application. * dateacct: The Accounting Date field it was possible to leave empty, but it should not be a common case, because this would mean a transaction not used in accounting, and this is an error and should be fixed. If statementdate or dateacct a buildvalidation fails and to solve this it is very helpful to visit http://wiki.openbravo.com/wiki/Update_Transaction_Refactor [^] * trxtype: The Transaction Type field it should not be a problem because there is a modulescript that inserts a value there in case is needed. * (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0): there should not be any record with both amounts Zero, the application does not allow it. But we found that retail allowed to insert transactions with both amounts Zero. To fix this transactions we provide a new modulescript. * Size of entity_alias in ad_column, it should not be a problem because the size is bigger. |
||
| Revision | 2014-09-24 10:08 by Sandrahuguet | ||
| Description | Look at: * API Break due to following columns have been marked as mandatory and not null in Fin_Finacc_Transaction table: - statementdate - dateacct - trxtype * Also due to a new constraint in Fin_Finacc_Transaction table: Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) * The size of table AD_COLUMN Column ENTITY_ALIAS has changed from 60 to 2000 Risk api-changes: * statementdate: There should not be any transaction without Transaction Date. Before this project is was not possible to add transactions with this field empty from the application. * dateacct: The Accounting Date field it was possible to leave empty, but it should not be a common case, because this would mean a transaction not used in accounting, and this is an error and should be fixed. If statementdate or dateacct a buildvalidation fails and to solve this it is very helpful to visit http://wiki.openbravo.com/wiki/Update_Transaction_Refactor [^] * trxtype: The Transaction Type field it should not be a problem because there is a modulescript that inserts a value there in case is needed. * (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0): there should not be any record with both amounts Zero, the application does not allow it. But we found that retail allowed to insert transactions with both amounts Zero. To fix this transactions we provide a new modulescript. * Size of entity_alias in ad_column, it should not be a problem because the size is bigger. |
||
| Revision | 2014-09-24 10:07 by Sandrahuguet | ||
| Description | Look at: *API Break due to following columns have been marked as mandatory and not null in Fin_Finacc_Transaction table: - statementdate - dateacct - trxtype *Also due to a new constraint in Fin_Finacc_Transaction table: Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) *The size of table AD_COLUMN Column ENTITY_ALIAS has changed from 60 to 2000 Risk api-changes: *statementdate: There should not be any transaction without Transaction Date. Before this project is was not possible to add transactions with this field empty from the application. *dateacct: The Accounting Date field it was possible to leave empty, but it should not be a common case, because this would mean a transaction not used in accounting, and this is an error and should be fixed. If statementdate or dateacct a buildvalidation fails and to solve this it is very helpful to visit http://wiki.openbravo.com/wiki/Update_Transaction_Refactor [^] *trxtype: The Transaction Type field it should not be a problem because there is a modulescript that inserts a value there in case is needed. *(PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0): there should not be any record with both amounts Zero, the application does not allow it. But we found that retail allowed to insert transactions with both amounts Zero. To fix this transactions we provide a new modulescript. *Size of entity_alias in ad_column, it should not be a problem because the size is bigger. |
||
| Revision | 2014-09-24 10:06 by Sandrahuguet | ||
| Description | Look at: *API Break due to following columns have been marked as mandatory and not null in Fin_Finacc_Transaction table: - statementdate - dateacct - trxtype *Also due to a new constraint in Fin_Finacc_Transaction table: Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) *The size of table AD_COLUMN Column ENTITY_ALIAS has changed from 60 to 2000 Risk api-changes: *statementdate: There should not be any transaction without Transaction Date. Before this project is was not possible to add transactions with this field empty from the application. *dateacct: The Accounting Date field it was possible to leave empty, but it should not be a common case, because this would mean a transaction not used in accounting, and this is an error and should be fixed. If statementdate or dateacct a buildvalidation fails and to solve this it is very helpful to visit http://wiki.openbravo.com/wiki/Update_Transaction_Refactor [^] *trxtype: The Transaction Type field it should not be a problem because there is a modulescript that inserts a value there in case is needed. *(PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0): there should not be any record with both amounts Zero, the application does not allow it. But we found that retail allowed to insert transactions with both amounts Zero. To fix this transactions we provide a new modulescript. *Size of entity_alias in ad_column, it should not be a problem because the size is bigger. |
||
| Revision | 2014-09-24 10:01 by Sandrahuguet | ||
| Steps To Reproduce | Look at: http://ci.openbravo.com/view/try/job/try-api/673/consoleFull [^] [checkAPI] 29166 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 29170 ERROR - Errors in API model validation [checkAPI] 29173 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 29178 ERROR - Check Constraint addition: table: FIN_FINACC_TRANSACTION - Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) [checkAPI] 29181 ERROR - Column change from not required to required: column: FIN_FINACC_TRANSACTION.DATEACCT [checkAPI] 29185 ERROR - Column change from not required to required: column: FIN_FINACC_TRANSACTION.TRXTYPE [checkAPI] 29189 ERROR - Column change from not required to required: column: FIN_FINACC_TRANSACTION.STATEMENTDATE [checkAPI] 29192 ERROR - [checkAPI] [checkAPI] 29195 WARN - [checkAPI] [checkAPI] 29199 WARN - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 29202 WARN - Warnings in API model validation [checkAPI] 29205 WARN - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 29208 WARN - Column size changed from 60 to 2000: column: AD_COLUMN.ENTITY_ALIAS [checkAPI] 29213 WARN - [checkAPI] [checkAPI] 29218 ERROR - [checkAPI] [checkAPI] 29222 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 29225 ERROR - Errors in API data validation [checkAPI] 29228 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 29232 ERROR - Changed column value AD_COLUMN.ISMANDATORY -ID:7DC34559B416B45BE040007F0100784A from [N] to [Y] [checkAPI] 29237 ERROR - Changed column value AD_COLUMN.ISMANDATORY -ID:828EE0AE801C5FA1E040007F010067C7 from [N] to [Y] [checkAPI] 29242 ERROR - Changed column value AD_COLUMN.ISMANDATORY -ID:828EE0AE801D5FA1E040007F010067C7 from [N] to [Y] [checkAPI] 29247 ERROR - Not Allowed insertions in AD_PROCESS_PARA table. ID: 993E5D1AE89649648DFE15C27360CD52 [checkAPI] 29252 ERROR - |
||
| Revision | 2014-09-24 10:01 by Sandrahuguet | ||
| Description | Look at: *API Break due to following columns have been marked as mandatory and not null in Fin_Finacc_Transaction table: - statementdate - dateacct - trxtype *Also due to a new constraint in Fin_Finacc_Transaction table: Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) *The size of table AD_COLUMN Column ENTITY_ALIAS has changed from 60 to 2000 Risk api-changes: *statementdate: There should not be any transaction without Transaction Date. Before this project is was not possible to add transactions with this field empty from the application. *dateacct: The Accounting Date field it was possible to leave empty, but it should not be a common case, because this would mean a transaction not used in accounting, and this is an error and should be fixed. If statementdate or dateacct a buildvalidation fails and to solve this it is very helpful to visit http://wiki.openbravo.com/wiki/Update_Transaction_Refactor [^] *trxtype: The Transaction Type field it should not be a problem because there is a modulescript that inserts a value there in case is needed. *(PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0): there should not be any record with both amounts Zero, the application does not allow it. But we found that retail allowed to insert transactions with both amounts Zero. To fix this transactions we provide a new modulescript. *Size of entity_alias in ad_column, it should not be a problem because the size is bigger. |
||
| Revision | 2014-09-24 09:38 by Sandrahuguet | ||
| Steps To Reproduce | Look at: http://ci.openbravo.com/view/try/job/try-api/648/consoleFull [^] [checkAPI] 31310 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 31313 ERROR - Errors in API data validation [checkAPI] 31316 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 31319 ERROR - Changed column value AD_COLUMN.ISMANDATORY -ID:7DC34559B416B45BE040007F0100784A from [N] to [Y] [checkAPI] 31322 ERROR - Changed column value AD_COLUMN.ISMANDATORY -ID:828EE0AE801C5FA1E040007F010067C7 from [N] to [Y] [checkAPI] 31326 ERROR - Changed column value AD_COLUMN.ISMANDATORY -ID:828EE0AE801D5FA1E040007F010067C7 from [N] to [Y] [checkAPI] 31281 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 31284 ERROR - Errors in API model validation [checkAPI] 31286 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++ [checkAPI] 31288 ERROR - Check Constraint addition: table: FIN_FINACC_TRANSACTION - Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) |
||
| Revision | 2014-09-24 09:38 by Sandrahuguet | ||
| Description | Look at: API Break due to following columns have been marked as mandatory and not null in Fin_Finacc_Transaction table: - statementdate - dateacct - trxtype Also due to a new constraint in Fin_Finacc_Transaction table: Constraint: FIN_TRANS_AMOUNTS_CHK defined as: (PAYMENTAMT <> 0) OR (DEPOSITAMT <> 0) |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |