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
We had a case where two employee configurations were incorrect, and Vanga attempted to pay payroll. The system crashed with a generic error message (a NOT NULL error). After locating the issue with the employee in the database logs, we fixed that employee, but the users reported that the system still crashed.
In reality, we had fixed one employee, but were missing the second one. Had the users realized this, they might have been able to continue working by fixing the second employee.
Proposal
I propose we need better error messages for payroll crashes. We currently have everything in a database transaction, which is good, but we still need to keep some sort of log that to say "system crashed when processing employee jniles". That would provide some guidance to the user that something is wrong with employee jniles configuration. If we had this error message (instead of a NOT NULL error), there is a chance the payroll issues at Vanga would have worked themselves out yesterday without as much manual intervention from the team.
The text was updated successfully, but these errors were encountered:
- Prevent entry into the database of items whose values are not defined
- Display of the name of the employee for whom the Payroll data configuration was incorrect
closesIMA-WorldHealth#7455
- Prevent entry into the database of items whose values are not defined
- Display of the name of the employee for whom the Payroll data configuration was incorrect
closesIMA-WorldHealth#7455
lomamech
added a commit
to lomamech/bhima-2.X
that referenced
this issue
Mar 1, 2024
- Prevent entry into the database of items whose values are not defined
- Display of the name of the employee for whom the Payroll data configuration was incorrect
closesIMA-WorldHealth#7455
lomamech
added a commit
to lomamech/bhima-2.X
that referenced
this issue
Mar 4, 2024
- Prevent entry into the database of items whose values are not defined
- Display of the name of the employee for whom the Payroll data configuration was incorrect
closesIMA-WorldHealth#7455
lomamech
added a commit
to lomamech/bhima-2.X
that referenced
this issue
Mar 4, 2024
- Prevent entry into the database of items whose values are not defined
- Display of the name of the employee for whom the Payroll data configuration was incorrect
closesIMA-WorldHealth#7455
Scenario
We had a case where two employee configurations were incorrect, and Vanga attempted to pay payroll. The system crashed with a generic error message (a NOT NULL error). After locating the issue with the employee in the database logs, we fixed that employee, but the users reported that the system still crashed.
In reality, we had fixed one employee, but were missing the second one. Had the users realized this, they might have been able to continue working by fixing the second employee.
Proposal
I propose we need better error messages for payroll crashes. We currently have everything in a database transaction, which is good, but we still need to keep some sort of log that to say "system crashed when processing employee
jniles
". That would provide some guidance to the user that something is wrong with employeejniles
configuration. If we had this error message (instead of aNOT NULL
error), there is a chance the payroll issues at Vanga would have worked themselves out yesterday without as much manual intervention from the team.The text was updated successfully, but these errors were encountered: