Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

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
Steps To Reproduce As System Admin.
Go to Window, Tabs and Fields. Search for Sales Invoice window.
Select Payment Plan tab.
Search for the Modify Payment Plan field which is hidden.
Set Displayed = Y

Change role to F&B group admin
Go to Payment Term window.
Create a header for * org
 - Overdue Payment Days Rule : 100
Create the following lines:
 - Percentage due: 25, Overdue Payment Days Rule: 10
 - Percentage due: 35, Overdue Payment Days Rule: 15
 - Percentage due: 20, Overdue Payment Days Rule: 90

Go to Sales Invoice window and create a new record for Norte organization. Select the above payment term in the header and use "Transferencia" payment method.
Enter any line with some amount.
Complete the invoice.

Go to Payment Plan tab and select any record.
Press Modify Payment Plan button.
A grid is opened with several lines.
Set a break point over the OB.APRM.validateModifyPaymentPlanAmounts function
Delete any of the lines.
Create a new line. Verify that:
 - The validation function is not executed [point (1) above]
 - The Payment method is not "Transferencia" but "Al Contado" (the first item in alphabetic order). It should be set to Transferencia as I'm cloning from a record with Transferencia payment method [point (2) above]
Now edit the Outstanding amount and set something lower. Press in an empty space of the grid. The validation function is run, but the item.grid.data.allRows has 3 records when it should have 4 [point (3) above]
Now select the Outstanding amount of any other record. The validation function is run, but the item.grid.data.allRows has now 4 records. This is OK, but is not consistent with previous scenario [point (3) above].
Cancel the popup.
Press again Modify Payment Plan button.
Delete any of the lines.
Create a new line and change the outstanding amount to a lower value.
Now enter a new line. The validation function's item.grid.data.allRows has the original outstanding amount and not the new lower amount. This means you can't trust in the information that you receive in the function. [point (4) above]
Revision 2021-10-01 17:52 by vmromanos
Steps To Reproduce As System Admin.
Go to Window, Tabs and Fields. Search for Sales Invoice window.
Select Payment Plan tab.
Search for the Modify Payment Plan field which is hidden.
Set Displayed = Y

Change role to F&B group admin
Go to Payment Term window.
Create a header for * org
 - Overdue Payment Days Rule : 100
Create the following lines:
 - Percentage due: 25, Overdue Payment Days Rule: 10
 - Percentage due: 35, Overdue Payment Days Rule: 15
 - Percentage due: 20, Overdue Payment Days Rule: 90

Go to Sales Invoice window and create a new record for Norte organization. Select the above payment term in the header and use "Transferencia" payment method.
Enter any line with some amount.
Complete the invoice.

Go to Payment Plan tab and select any record.
Press Modify Payment Plan button.
A grid is opened with several lines.
Set a break point over the OB.APRM.validateModifyPaymentPlanAmounts function
Delete any of the lines.
Create a new line. Verify that:
 - The validation function is not executed [point (1) above]
 - The Payment method is not "Transferencia" but "Al Contado" (the first item in alphabetic order). It should be set to Transferencia as I'm cloning from a record with Transferencia payment method [point (2) above]
Now edit the Outstanding amount and set something lower. Press in an empty space of the grid. The validation function is run, but the item.grid.data.allRows has 3 records when it should have 4 [point (3) above]
Now select the Outstanding amount of any other record. The validation function is run, but the item.grid.data.allRows has now 4 records. This is OK, but is not consistent with previous scenario [point (3) above]


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker