Time Off Policies - Developers should go back to basics

  • 2
  • Idea
  • Updated 7 months ago
  • Under Consideration
Time Off module in Replicon is a great idea with a very poor development and thought process.

Let's go back to basics.

Should a user accrue time when he's on non-paid leave?
NO

Should a company policy overwrite a user Policy?
YES

Why on earth Replicon creates an Admin tab where the Admin (myself) can set policies, change policies etc and when it saves it doesn't apply to all users? but only to new user?

Well...here we go:
Every end of the year, during Christmas and NYE we allow our staff to overdraw up to 5 days. However, all year around we have a 0 overdraw policy. So far so good.

When I went to change the company policy to allow users to overdraw up to 5 days, hit save and updated the policy on a company level (a.k.a Parent level).

To my surprise, our staff still can't make use of the new policy, why? Because the policy will only apply to new users. Therefore I have to go and change user by user. 

At this time the customer support is doing it for me but what happens if my business has 5,000 employees? Clearly, this is a broken process, which seems quite common with Replicon.

 
Photo of Castro, Thiago

Castro, Thiago

  • 31 Posts
  • 4 Reply Likes
  • disappointed

Posted 9 months ago

  • 2
Photo of Drema Herron

Drema Herron

  • 49 Posts
  • 13 Reply Likes
Does using mass edit not help?
Photo of Castro, Thiago

Castro, Thiago

  • 31 Posts
  • 4 Reply Likes
I wish that was the case, but again, Replicon's Dev's should go back to basics. If I adjust via mass edit then it will override all previous balance etc...My feeling about Replicon is that they work on a "break fix scenario" instead of thinking what they want to produce and have it tested prior to releasing "new features"
Photo of Hildi

Hildi

  • 7 Posts
  • 5 Reply Likes
Couldn't agree more ..... it's beyond frustrating!
Photo of Aashnee Kamboj

Aashnee Kamboj, Community Moderator

  • 1657 Posts
  • 114 Reply Likes
Hi Thiago,

We understand your concern here. We will have this discussed internally with our product management team and will update the thread in case of any progress.
Photo of Charlene Eriksen

Charlene Eriksen, Product Manager

  • 410 Posts
  • 42 Reply Likes
Hi Thiago,

Currently within each time off type you can set a default policy. This policy is automatically applied for each new user who's given that time off type, but from then onwards each user has their own policies. This is a concept that's existed for quite some time in our time off system and I'm not sure of the origins of it.

While this approach does allow for a lot of flexibility if employees have negotiated different policies, I agree with you that being able to set and update the policies for a group of users at once would be helpful and it's something I've been thinking about for a while. At this moment, I don't think it's something we'll be looking at in Q1, but I'll update this if we do prioritize it in future. And once we get to that point it would be great to get your input on what we are designing.

Thanks,
Charlene
Photo of Hildi

Hildi

  • 7 Posts
  • 5 Reply Likes
Speaking of 'going back to basics' - the TimeOff Policy area worked FAR better previously. Here are some of my issues:

a)  The TIme Off Policy list isn't even appearing in alphabetical order
b)  The Time Off Policies showcase EVERY single change/update ever made, with the OLDEST appearing at the top of each category - and without the ability to collapse the changes within each category (what a time-waster - endless scrolling to get to what you need to change/add/refer to).

This is BASIC programming protocol - why weren't these basic considerations implemented? IT seems you are moving the program upgrade backward - and not forward with improvements. Why should the 'community' have to be pointing out basic process development 'misses' that should have been considered by your development team? 

We began this 'Gen3 upgrade' migration, supposedly a year ago. The 'launch' has taken far too long, and there are far too many issues that we're having to contend with (not the least of which are problems that are presenting, that didn't previously exist).