Skip to main content

Release notes v13

Learn more about release 13 that is planned for release 2023-09-20

Written by Lukas Andersson

We are excited to announce the release of the latest version of our software product. This release comes with a host of new features and improvements that will enhance the users experience.

Feature improvements

We have made the following improvements to our software to make it more intuitive and user-friendly.

New profile design

As you know we have released a new profile design. Read more about that in our knowledge base here :

Fortnox timesheet export of project codes

We have now added functionality for the Fortnox integration to also contain project codes in the timesheet integration.

Project codes will be included in the timesheet export together with the reported hours if:

  • There is a project defined on a timesheet

  • There is a code connected to that project

PE Integration allowing for multiple PE companies

We have improved our integration towards PE Accounting so that it allows for customers to have multiple companies in PE Accounting and integrate that into one single Alexis HR Account.

When you create new users in Alexis and want to export them to PE Accounting you will now have the option to select what company in PE Accounting they should be connected to.

Configuration

You configure multiple Integration connections from Settings → Integrations → Integrate with PE Accounting

Export of new employees with multiple PE accounts

If you have multiple PE accounts and you have a new user in Alexis that you want to export to PE Accounting you need to decide the specific company that this user should be exported and “connected” to.

When doing an export from People → Export/Import → Alexis you are presented with a single select option to choose what company to export to.

Import of employees from multiple PE accounts

When importing from multiple PE Accounting accounts we will import from all of the companies that has an Integration connection. No choice is needed to choose from since the goal is to have all your employees within one instance of Alexis HR even if they are in multiple instances in PE Accounting.

Payroll report moved to Manage time

A small change to have all the payroll related items in the same place, we are looking over the menu even more moving forward so keep an eye out for that in the coming release notes.

Possibility to customize payroll report on organisation

This change will allow for customization of the payroll file to either include all employees (as before and this is chosen by default) or to only include employees that belongs to an organization.

No other changes are made to the output of the payroll report.

Organization is defined under People → selected Employee → Profile → Work

Leave type codes available through the API

With the added possibility for leave type codes we have now added them to the public API so that they can be retrieved and used for integrations to other HRIS systems if needed.

The leave type codes are added as a relation to the leave type and thus retrieved with adding

?relations=leaveTypeCode

So the request would be:

https://api.test-alexishr.com/v1/leave-type/{id}?relations=leaveTypeCode

And the response will then be in relation to the response of the leave-type

API documentation can be found here:

SCIM API improvements

We have made an improvement to the SCIM API and added 5 new fields in the response for GET scim/v2/Users/.

This will allow for customers using The provisioning API (SCIM) to be able to retrieve some needed data that is not part of the SCIM standard but needed for integrations to the AIM or another HRIS.

New fields:

  • office

  • team

  • employment type

  • hire date

  • end date

This will be exported in a new extension schemas.

"urn:ietf:params:scim:schemas:extension:alexis:2.0:User": { 
"office": "Brussels",
"team": [ "Peleton", "Jumbo Visma", "Alpecin–Deceuninck" ], "employmentType": "consultant",
"hireDate": "2023-01-01T00:00:00.000Z",
"endDate": null
},

Type added for Public API vs Provisioning API

We have added a new type definition for the Public API and the Provisioning API. This allows for creation of access tokens to be valid for both types or for either one.

Access tokens are created from Settings → Access tokens

Note:

  • Existing access tokens will have access to both to not break backwards compatibility.

  • An access token type can not be edited (edit only possible for Name & Description).

Bug Fixes

  • Resolved an issue with the employee profile where managers could not edit/delete notes for the employees reporting into them.

  • Resolved an issue where it was not possible to approve leaves in the Slack bot.

Did this answer your question?