Hi,

I tested with first formula (which is not as bad IMO, as attribution will differ from max 1 day, so that doe snot seem so strange).
I had 3 resources as employee, start at same date, 2 (admin & Project manager) with contract type leading to extra day from sdeniority, 1 (analyst A) with anoter contract.
Result seem correct :

Note that update of days does not seem to be calculated on connection, but on Leave Period Update, when you click on "initialize with contractual values".
This seems valid for "acquisition period that ended" (in my case, all day are obtaines and can be taken).

Difficulties with this module is that is reacts dynamically on year progression.
Also terms are not always clear : in Leave Period display, start and end dates are not for aquisition of days, but for using the days.

Hi,
[...]
Difficulties with this module is that is reacts dynamically on year progression.

I see what you mean, when the date will reach the 'birthday' start date of employee during the year of acquisition, he would obtain an extra day off instead of having it calcultated only at start of acquisition period... hum.. yeah so first formula should be more correct, but with a small pb regarding the exact number of days according to leap years.. gonna check again..
(or maybe add an extra option check box 'calculated on start of acquisition perio only' for specific rules 😉 and in that case second formula is correct :p )

My second issue (the fact that the formula is not applicated on other employes) is more problematic, even with "initialise with contractual value, seniority day is not incremented '... (still V8.4.6)

floor (DATEDIFF(CURDATE(),${Employee.startDate}) / ( 365 * 5 ) )
floor((YEAR(NOW()) - YEAR(${Employee.startDate}) - IF( DAYOFYEAR(NOW()) < DAYOFYEAR(${Employee.startDate}) , 1, 0)) / 5)

In fact both formulas are wrong, as extra day off for seniority is generally calculated only at the end of the vesting period

I come back on that.. If projeqtor calculate Special right ONLY at the end of vesting period, the 2nd formula is accurate...

for exemple : acquisition period from 1st june - 31th may with a employe start on october 2015

at 31th of may 2020 (end of vesting period) floor((YEAR(NOW()) - YEAR(${Employee.startDate}) = 2020-2015 = 5

so 5/5 should lead to 1 seniority day

but as his start day is AFTER 31th may, he should not have that because he des'nt have full 5Y presence at vestling end period date ..

that why "-IF( DAYOFYEAR(NOW()) < DAYOFYEAR(${Employee.startDate}) , 1, 0)" will remove 1 year , with DAYOFYEAR(NOW())= end of vesting date (31th may)
so that floor (4/5) = 0 and not one ...

just have to know exactly WHEN those special rights are calculated

and I still don't manage to make seniority calculation works properly for other employes... BTW as our vacancy can be anticipated (i.e. taken before end of vesting period), I've got a delay before use of 1 month. Pressing initialise with contractual values, with a period from 1st of june to 31may, leads to a initialise value of 2 days initialised (1st-june to 31thjune) without any calculation from previous period for seniority.

I come back on that.. If projeqtor calculate Special right ONLY at the end of vesting period, the 2nd formula is accurate...

I did'nt mean Projeqtor calculates only at the end of the period, I meant HR rules often define that extra day is acquires at the end of the period.
That's why I guess calculating only with years is wrong.

just have to know exactly WHEN those special rights are calculated

I would also like to know this.
This module is an external contribution, and we don"t master it as well as the rest of the application that is developped internally. :whistle:

ok. So Wait and see for further info.. atm, I just integrate special right day with other holiday directly to make the job ! Thx

Back From Holiday !
I Hope all projeqtor team is going fine ! 🙂

I came back to this thread with some other funny facts.

With my acquisition formulae calculated "each month" (so mostly 2 days/month), regardless of special rights acquisition, the HR module doesn't take into account previous day number from previous acquisition period and simply erase it and calculate again from the start of aquisition period the total number of day... ^^ so it complelty messed up everything 🙂

I re-enter it manually, but I lost "already taken day" from this current acquisition period (I guess when you enter a number a day manually, the "taken day" is set to 0 without checking all day already taken in the current acquisition period).

Another really annoying thing is acquired right manually update where "quantity" and "remaining day" are not accessible correctly. I could'nt access (grey) quantity day, I had to set back my remaining first day, but as soon as I change this, "quantity" went grey and couldn't be corrected.. I had to save the remaining day update and only then, quantity went white again and accessible for correction. So it makes a lot of save to be able to correct this.

Hoping it will help you to find what's wrong with that module or claim more explanations.

I guess my next automatic "september update calculation" will completly mess up everything again ^^ 😛 , hoping you will find what's wrong before that 😉

Regards

Hi, Projeqtor Team !
Just a quick post to know if you have some news regarding the HR module problem before the "waited problem" of 1st September and new calculation that will erase previous numbers of day ?

Keep it up, have a nice day

As 'expected', messed-up calculation from HR module that erase previous days taking into account only it's monthly calculation from start...

It's really started to be an annoying problem as it can't be used properly...

Got a proposal Enhancement :

Should it be possible to have a specific customizable "Day entry" from previous period so that Current period calculation will follow its law.
The "Total days" could be calculated using previous period day+ Current period calculation + special right calculation which give a "total number of day"

At the end of a period, the current period day remaining should be put onto previous period day and calculation from current period could be run (+ specific right)

Until previous period days goes to 0, Vacation Days should be taken off from this entry.

As the matter of fact, and as the HR module is running right now, we can see that if monthly calculation is used, it's really messing up all days off calculation, but I guess that (in France at least), we really earn mostly 2 days / month added directly into our vacation days count.

Sure it will be mostly 25 days / year over a 1Y period, but not earn at 1 time at the end of period but really earn and taken into account each month.

Thanks for reading

As the matter of fact, and as the HR module is running right now, we can see that if monthly calculation is used, it's really messing up all days off calculation, but I guess that (in France at least), we really earn mostly 2 days / month added directly into our vacation days count.

Sure it will be mostly 25 days / year over a 1Y period, but not earn at 1 time at the end of period but really earn and taken into account each month.

Yes this it it. It was designed on a monthly earning basis (based on french rules).
The system should adapt to other countries and add the timeframe : monthly (existing), yearly at start of period, yearly at end of period
Ticket #4902 recorded

Hi,
As HR module still buggy using a month earn, I redefine a year earn base. However, special leave rights still buggy and I don't know why they are only applied to my profile. We are 4 ppl with the same kind of contract and only mine is well initialised with those special rights.. Any clue to solve out this problem ?