Skip to content

Kronos Workforce Central 7 is STILL 78% Java Free!

May 30, 2014

Kronos Workforce Central 7 - No Desktop JavaMan, it’s been a long week for a short week. It got to the point where I wondered if my post on Workforce Central 7 being Java free for about 78% of users was induced by some hallucinogenic dropped in my coffee, but although my post contributed to an internal kerfuffleit’s still true. I got my information directly from Kronos Engineering (see, the slide’s right there!), but I’m in marketing, so it was natural for some people to think I was just making stuff up. So, the challenges and questions began. I hope these concerns, and the responses by Kronos Engineering help bring some clarity to what can be a little um, cloudy, like when you add half and half to your coffee…

To reiterate, with our new Workforce Central 7 Navigator interface, it is possible to deliver a Java-free desktop experience for all employee functions except for Workforce Activities (small % of customers).

Here are some specific issues Kronos Engineering responded to:

  • Cannot view classic timecard – Classic timecard is our legacy timecard application, which was and remains written in Java. For a Java-free desktop environment, customers should use the new Navigator employee timecard.
  • No genies – genies are a function used almost exclusively by managers, and do require desktop Java.
  • No alerts – This is not accurate. The new alerts framework is delivered with Navigator in Workforce Central 7.
  • Must have Flash – True, but Flash does not require Java.
  • If you have manager access, you must have Java – True. Most manager functions continue to require desktop Java.
  • Still need Java loaded on the desktop – Per the comments above, Java on the desktop is not needed for employee functionality when the Navigator interface is used.
  • May limit some functionality – There are a number of typical front line manager or HR functions that very few customers intermittently allow employees to access. Again, for the large majority of organizations and employee users these do not pose a problem, but for transparency sake, we wanted to make you aware of them since they are typically manager functions, and are NOT desktop Java free in Workforce Central 7:
    • Timecard View Audit Trail
    • Timecard perform Historical Edits
    • Mark exceptions as reviewed
    • Approve Overtime
    • Edit long term leave cases
    • Pay Rule Analysis
    • Manage Accrual Transitions
    • Reset Accrual Balances
    • Update Accrual Balances
    • Move Accrual Balances
    • View Accrual Profile Assignments

These are the questions and answers regarding Workforce Central 7 and desktop Java that I’m aware of. If I learn more, you’ll be the first to know. Now I need that coffee…

8 Comments leave one →
  1. June 2, 2014 10:20 am

    “Cannot view classic timecard – Classic timecard is our legacy timecard application, which was and remains written in Java. For a Java-free desktop environment, customers should use the new Navigator employee timecard.

    If you have manager access, you must have Java – True. Most manager functions continue to require desktop Java.”

    So classic manager view and classic time card are both java dependent. That amounts to 90% of activity for most of your clients which is where the real issue comes in. We’re excited for HTML 5 but will avoid 7.x for now as Java continues to kill our support team.

  2. June 2, 2014 12:08 pm

    Hey JJ, thanks for your comment. Yes, manager functions still (mostly) require Java, but the Navigator time card (no Java required) is where the 78% number comes from. Eliminating the need for Java for many of your end-users could offer your support staff some relief.

  3. Mitri Dahdaly permalink
    June 5, 2014 6:08 pm

    Or you could opt to replace Kronos with a more modern system that is already 100% web based

  4. June 6, 2014 10:11 am

    Hi Mitri. Thanks for your comment. Workforce Central is 100% web-based, and has been for years. We’re working to get the Java out for all desktop users. We’re very focused on meeting the evolving needs of our customers in terms of functionality, user experience, and support.

  5. Adam Bennett permalink
    February 28, 2015 9:57 pm

    Why must the navigator be limited to one in and one out column per line? if you clock out for lunch you have twice as many lines as in classic. Classic has a four column format which is so much easier to work with. So, the Java remains necessary.


  1. Five Things You Should At Least Pretend to Know About Kronos today | Working Smarter Cafe
  2. There Once Was a Man From Nantucket… | Working Smarter Cafe
  3. Why you messin’ with my Java? | Working Smarter Cafe

Leave a Reply

%d bloggers like this: