Older release notes are listed on this article. You can read the latest release notes here.
12/12/2020 release (2.6.0)
New
-
Person import via API integration
Allows future changes to be imported into the service in advance and the import interval to be set to a minimum of one hour
Guidance [ref 10592]
-
Rulesets gain 'Deleted events' data
Can be used to retrieve deleted events and use them to generate various reports
Guidance [ref 11217,11297]
-
Work rises have a new setting
Possibility to set a new earning threshold, in which case earnings will only start after a certain time
Guidance [ref 11154]
Improvements
-
Support for Personec F export types 2 & 3 in integration
It is now possible to export all types in Personec F integration
Guidance [ref 10498]
-
Monitoring of annual working time
It is possible to set the annual working time monitoring with the levelling period settings
Guidance [ref 11027]
-
Project Hours by Person report improvement
Added grouping option "By Event". In addition, internal and public notes on the event and project will be included in the report.
Guidance [ref 11107]
-
Rulesets gain 'Information on the accumulation of annual leave'
Can retrieve information on the accumulation of annual leave for all event types
Guidance [ref 10752]
04/11/2020 release (2.5.1)
Improvements
-
Travel invoice
It is now more visual and easier to use. For example, we added travel method icons and route indications. Also domestic trips do not require time entries, which saves time and extra clicking.
Guidance [ref 10929]
24/10/2020 release (2.5.0)
New
-
Rulesets gain ‘Person Group’ data
This is so that, for example, a customer can query their event data and include the hierarchy of Person group information including names, codes, etc.
Guidance [ref 10466]
Improvements
-
Naming standardisation and improvements for Worktime
In UI, for example, the terms that appear in calendar and reports correspond to each other. We have changed the following terms, among others:
- Work hours -> Worked time incl. absences
- Basic time -> Regular time
[ref 10935]
-
Microsoft Login security & stability
We have improved Microsoft Login, so that our customers can log in to our service on all browsers and devices.
Guidance [ref 10755]
12/09/2020 release (2.4.0)
New
-
Digia Enterprise salary integration
We now support exporting salary data to this salary system. The information is transferred in Digia Enterprise format and can be used by all customers.
Guidance [ref 10075]
Improvements
-
Project report ”Hours per person”
Report has been added an Event type column to the report to allow better filtering and pivoting of the information. For example, you can now easily determine how many project hours were related to meetings, travel, etc.
Travel invoices and other supplements now appear in this report.
Several data selections on the report have been clarified to make it easier to understand its capabilities.
Guidance [ref 10041]
-
Worktime rounding
When compensated time is rounded there is now a clear distinction between work hours that were registered and time which is paid.
This corrects issues in reports such as the Overtime and Hours by salary type report, which were earlier unable to show the correct amount of worked hours.
It also improves the accuracy of data gathered by rulesets for exports and integrations. They can now be extended to consider whether compensation exists because of rounding or not. A good example of where this might be useful is when creating a ruleset for invoices, which should be based on actually worked hours, vs a ruleset for salary integrations, which should include rounded times.
The change also addresses situations where work rises were being incorrectly earned due to rounding. A good example of this are evening and night compensations as these should be awarded for the actual time worked, not rounded time used for salary calculations. There is a new Work rise setting to enable this method of calculation, which can be found in the Work rise settings section.
Guidance [ref 8841]
-
Integration rulesets are extended to include project data
We have added the ability to fetch project data as part of rulesets. With this you can create a variety of reports from recorded events.
Guidance [ref 10465]
16/07/2020 release (2.3.0)
New
-
It is possible to add internal and public notes to each project added to an event
Guidance [ref 9011]
-
SSO identity provider encryption certificates can be installed from UI
Guidance [ref 8088]
-
Microsoft Azure AD SSO can be configured from UI
Guidance [ref 10414]
Improvements
-
Travel invoices enhancements
Travel invoice report can be exported into excel.
Following travel invoices' fields are exposed in integration rule sets. Linked Guide heading 'Poimitaan matkalaskun matkan tietoja'
- Trip start and end address
- Trip reason
Guidance [ref 10178]
-
Enhanced options for public holiday and work week length on obligated days
Guidance [ref 10472]
-
Worktime roles can be imported and exported
Guidance [ref 10425]
20/05/2020 release (2.2.0)
New
-
Titania integration
Guidance [ref 9824, 9372]
-
Persons additional fields can now have default values
Guidance [ref 10189]
Improvements
-
Outdated API domain ramp-down
The new domain for events, projects and worktime calculations API is https://time.nepton.com. Old domain https://tyoaika.tyoteho.fi is obsolete and should no longer be used. Please switch to using new domain as soon as possible.
Guidance [ref 10211]
-
Service API now supports deleting events by using the UpdateActivities method
Guidance [ref 10211]
29/04/2020 release (2.1.0)
New
-
InTime integration
Guidance [ref 8824]
-
'Actual worktime' report (old report Work hours daily view)
Guidance [ref 9537]
Improvements
15/04/2020 release (2.0.0)
New
-
Travel invoice capabilities
Use supplements to define travel invoice rows, travel expenses or daily allowances - Guidance
Support for multiple routes per travel invoice.
Automatically calculated allowances, including foreign allowances, based on the routes
Guidance [ref 8831]
-
Platform status page launched
Here [ref 9283]
-
It is possible to use an external system's identifier to recognize projects in the API
In addition to the project code, projects can be recognized by identifiers used by a third party system. This permits user friendly codes and unique system identifiers to be different.
Guidance [ref 9426]
Improvements
-
Employees person information page
Usability and browser compatibility improved.
[ref 8834]
-
Wall terminal branding
[ref 9908]
-
Behaviour of primary and secondary supervisor data in person integrations
If this requires actions, you have been contacted.
Guidance [ref 5765]
-
Stability and performance issues solved
The previous version included many complicated changes, some of which did not go according to plan. We sincerely apologise for these issues! Stability and performance have now been restored, and we have made process changes to ensure this kind of situation will not reoccur.
[ref 8834, 9217]