I observe many incorrect symptoms and error messages in the HR module.
1. The Leave rights earned list for one of the Leaves types is not presented (the spinning wheel continues to spin).
2. You cannot delete the Leaves period (I modified the Leaves workflow allowing to change the status from submitted to recorded), so I can't delete the dependent Leaves type or Employment contract type as well).
3. Several screen forms are faulty (only one section visible, incorrect arrangement of fields).
4. On the profile of one of the Employees i see thousands of Leaves rights earned records.
I describe only a few of the dozen or so symptoms. HR module seem to be unstable at all.
Today's log attached.
Can you suggest a solution?
Zygmunt
Hi,
Sure HR modules required some improvments.
Your remarks are recorded on ticket #4758.
We spent some hours diagnosing ...
I want to share my thoughts.
1. The "employeeleaveearned" table was filled with records (last id over 340000). As the statuses "is an employee" were deleted in turn for all employees (about 30), the records disappeared. All employees reset - only one record left - for Resource as Leaves Manager.
2. Then we plan to turn on "is an employee" sequentially for Resource. This will result in the appearance of records in the "employeeleaveearned" array, according to the "Employment contract type" and "Leaves types" settings.
We will carefully add more employees watching the increase in records in "employeeleaveearned".
Hints would be very helpful:
a) how to reduce the ID from the current value of 346225 to real (justified by the amount of real data). I'm guessing that the parameter (something like "LastID") is stored in at least one of the arrays.
b) what mechanism (stored procedure?) implements adding records in "employeeleaveearned"?
Hi,
a) how to reduce the ID from the current value of 346225 to real (justified by the amount of real data). I'm guessing that the parameter (something like "LastID") is stored in at least one of the arrays.
This is managed by the DB.
MySql :
ALTER TABLE employeeleaveearned AUTO_INCREMENT = 1;
PostgreSql
ALTER SEQUENCE employeeleaveearned_id_seq START WITH 1;
b) what mechanism (stored procedure?) implements adding records in "employeeleaveearned"?
There is no stored procedure.
All is done through PHP.
Have a look at object "Resource", method save(), when isEmployee is checked, some specific function may be called.
Thanks - the solution for resetting the counter is effective.
I'm sharing my investigation of 'zeroing' leaves quantity' issue.
I am a User with the Leaves system administrator role. I set the status "is an employee" for subsequent employees (individually):
1. Set "is an employee" - save
2. Checking the "Leaves rights earned" list - result on the enclosed screen HR_01. The result is in line with the "EMployment contract type" settings - screen HR_01a.
3. Logout
4. Logging in - verification of the "Leaves rights earned" list - result on the enclosed screen HR_02.
5. Manual modification of the "quantity" value in "Leaves rights earned" - screen HR_03.
6. Logout
7. Logging in - verification of the "Leaves rights earned" list - "quantity" value is as expected.
8. Next employee - goto step 1
Previous attempts - setting the status "is an employee" for a larger number of employees, in several portions without logging off the Administrator, resulted in a haotic list of "Leaves rights earned", with incomprehensible "quantity" values - zero or non-zero.
I hope that my observations will be helpful in locating the algorithm defect.
Referenced screenshots not attached ?
Sorry - my fault - I'm attaching..
Remarks attached as note to the ticket.
Thanks.