What's New in Version October 2016

Friday, September 30, 2016 by Karin Huber

Active and Passive Travel Time in Context of Working Time Limits

In September, we primarily worked on an extension to time cockpit's working time violation check functions. You find a general introduction into that feature in the article Working Time Violations and Maximum Working Time. In the past, it was already possible to use a global setting to specify whether travel time is counted as working time. This setting will be replaced with a new, more powerful functionality that allows you to distinguish active and passive travel time when evaluating working time violations.

This month, we will roll out the new functions to a few beta customers. We plan to make it available to all time cockpit customers in four week with time cockpit's November release.

Read more ...

This month's time cockpit client is made available to beta customers testing the extensions mentioned above. Contact us if you want to be part of the beta program Otherwise, you will get the new features with next month's release.

Change Password in HTML5 Client

In the HTML5 client of time cockpit we are using Identity Server for authorization. Until now, we used the default view for the login page that is provided by Identity Server. This month, we customized the login experience so that we can fully control the appearance of the login page. This allowed us to add the Reset Password link you know from the time cockpit website and from the Silverlight client

The reset password page allows you to enter your username. Then it will send you an email with a link to a page, where you can enter a new password. This link will only be valid for two hours. If the link expires, you will have to request a new link on the reset password page again.

The new password is used for the full client, the Silverlight client, the HTML5 client and the time cockpit website. After changing the password in the HTML5 client, the full client will ask you to enter the new password when it tries to sync data with the server the next time.

comments powered by Disqus