You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EPL-1160: "Done" button not locking in 'Add Payments' and 'Add Details' processes when only a value is entered in 'Actual Payment' without losing focus
#320
Closed
brunoromerosmf opened this issue
Feb 27, 2024
· 1 comment
· Fixed by #408
An issue occurs in popups related to the 'add payment' process within the 'transactions' tab of the 'financial account' window, and in the 'add details' process of the 'payment in' window. When a value is entered in the 'actual payment' field and an attempt is made to save without losing focus from the field, incorrect behaviors are observed:
In the first scenario, a 'payment in' is created with a value of 0 and without lines, allowing the transaction to be processed.
In the second scenario, even though the 'done' button does not lock, when attempting to save, the system fails to save and displays an error. However, the appropriate behavior would be for the 'done' button to lock.
Steps to reproduce the error
For the first case 'add payment':
a. Navigate to the 'financial account' window.
b. Go to the 'transactions' tab.
c. Create a new transaction.
d. Click on the '+' button next to the 'payment' field.
e. Enter a value in the 'actual payment' field.
f. Attempt to save by clicking 'done' without shifting focus from the 'actual payment' field.
g. The transaction is as follows:
The payment in is a follows:
For the second case 'add details':
a. Create a new 'payment in' with no value in the corresponding window. (Remember to set a partner)
b. Click on the 'add details' button.
c. Repeat the steps of entering a value in 'actual payment' and attempting to save without shifting focus, as in the first case.
Expected behavior
The expected behavior in both scenarios is that the 'done' button should lock while the 'actual payment' field is in focus with a value entered. This should prevent the creation of erroneous transactions (with a value of 0 and without lines) and ensure that the user cannot process the transaction until the payment is fully completed and the focus is shifted from the 'actual payment' field.
Affected Version
Etendo core 23.3.2
The text was updated successfully, but these errors were encountered:
Error's description
An issue occurs in popups related to the 'add payment' process within the 'transactions' tab of the 'financial account' window, and in the 'add details' process of the 'payment in' window. When a value is entered in the 'actual payment' field and an attempt is made to save without losing focus from the field, incorrect behaviors are observed:
Steps to reproduce the error
For the first case 'add payment':
a. Navigate to the 'financial account' window.
b. Go to the 'transactions' tab.
c. Create a new transaction.
d. Click on the '+' button next to the 'payment' field.
e. Enter a value in the 'actual payment' field.
f. Attempt to save by clicking 'done' without shifting focus from the 'actual payment' field.
g. The transaction is as follows:
The payment in is a follows:
For the second case 'add details':
a. Create a new 'payment in' with no value in the corresponding window. (Remember to set a partner)
b. Click on the 'add details' button.
c. Repeat the steps of entering a value in 'actual payment' and attempting to save without shifting focus, as in the first case.
Expected behavior
The expected behavior in both scenarios is that the 'done' button should lock while the 'actual payment' field is in focus with a value entered. This should prevent the creation of erroneous transactions (with a value of 0 and without lines) and ensure that the user cannot process the transaction until the payment is fully completed and the focus is shifted from the 'actual payment' field.
Affected Version
Etendo core 23.3.2
The text was updated successfully, but these errors were encountered: