Problem after updating to 5.3.3

[HenrikH]

Hi,

After updating from v.5.0.8 to v.5.3.3 I have some problems.

1. Recurring Schedule
I suddenly have some users in recurring schedule with first and last name OPEN.

2. Break Policy
An auto-deduct break policy gets added to every punch. But it should only be activated after 10 hours working. I tried to delete the 10 hour break policy from Group policys, but it still gets added to the punch made by the user.

Best regards

Henrik Hegelund

[shanec]

In regards to your questions:

1. If you're seeing OPEN shifts go to ATTENDANCE -> RECURRING SCHEDULES to remove them.

2. Check the Schedule Policy. Break Policies can be assigned through there, separately from the Policy Group.

[HenrikH]

Hi

Thanks for speedy answer.

The break policy was working fine under 5.0.8. Now, in v.5.3.3 it gets added to all punches, for users in the Schedule Policy. But it should only be active after 10 hours of working. I have attached the Schedule Policy. As shown you can see that there's a break policy added to this.
The break policy is an auto-deduct and isn't active before 10 hours work, detected by time window. But it still gets added - even if 10 hours work hasn't been reached.

[shanec]

If you manually add punches to a date several days in the future for a total of one hour is the Break Policy deducted?
Have you tried recalculating the employee's timesheet to see if that makes a difference?

[HenrikH]

I tried to recalculate timesheets and it doesn't solve the problem. The error seems to only exist in the current pay period. If I make a manually punch in the next pay period, the hour's gets calculated correctly.

[shanec]

At this stage your issue requires further investigation. In order to do that we need you to email a dump of your database to support@timetrex.com.

[HenrikH]

Hi Again

Sorry for late replay. Been away from the office.

I have tried to mail the dump to you. But it's 155 MB and you mail system doesn't allow mails this large.

Br,

Henrik

[shanec]

Please use Dropbox or Google Drive and then email us the link.

[shaunw]

This issue will be corrected in the next version of TimeTrex (v7.0.1).