Project:
| View Revisions: Issue #47799 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0047799: Tab --> Add Function different problems with the new record created | ||
| Revision | 2021-10-01 18:05 by vmromanos | ||
| Description | Discovered in the Modify Payment Plan feature. There is an Add Function defined into the tab (OB.APRM.addNew). There is a Validation Function defined into one of the fields (Outstanding --> OB.APRM.validateModifyPaymentPlanAmounts) The implementation uses: returnObject = isc.addProperties({}, allRows[0]); to clone an existing record from the grid to use it as a template. Some properties are modified and then it is returned by the function. The record is added to the grid after executing the function, however the following problems have been detected: 1) The validation function associated to the field is not executed after returning the record. This behavior is not consistent if we compare with the Remove Function which is executed (see 0047798) 2) The fields associated to a foreign key (Payment Method in my case) are not properly populated in the new record. Not sure if this is related to the function used to clone the record or anything else. In any case, it should be provided an API to be able to clone a record ready to be added to the grid. 3) If I manually edit the field associated to the validation function just after creating the new record, the validation function's item.grid.data.allRows doesn't have yet the newly created record. However, in the moment I press over the same field in another record, the validation function is called again, but this time the item.grid.data.allRows does have the record. This behavior makes it very difficult to implement a consistent validation function. 4) The item.grid.data.allRows doesn't have updated information. |
||
| Revision | 2021-10-01 17:52 by vmromanos | ||
| Description | Discovered in the Modify Payment Plan feature. There is an Add Function defined into the tab (OB.APRM.addNew). There is a Validation Function defined into one of the fields (Outstanding --> OB.APRM.validateModifyPaymentPlanAmounts) The implementation uses: returnObject = isc.addProperties({}, allRows[0]); to clone an existing record from the grid to use it as a template. Some properties are modified and then it is returned by the function. The record is added to the grid after executing the function, however the following problems have been detected: 1) The validation function associated to the field is not executed after returning the record. This behavior is not consistent if we compare with the Remove Function which is executed (see 0047798) 2) The fields associated to a foreign key (Payment Method in my case) are not properly populated in the new record. Not sure if this is related to the function used to clone the record or anything else. In any case, it should be provided an API to be able to clone a record ready to be added to the grid. 3) If I manually edit the field associated to the validation function just after creating the new record, the validation function's item.grid.data.allRows doesn't have yet the newly created record. However, in the moment I press over the same field in another record, the validation function is called again, but this time the item.grid.data.allRows does have the record. This behavior makes it very difficult to implement a consistent validation function. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |