We just finished the update of 10-12-2020. 

New features

Nmbrs® Engine 2021

The new Nmbrs® Engine for 2021 is live! This means that it's now possible to do a year transit. Read all about it in this article.

Access to documents for employees

As announced last week, it is now possible to specify, for each document, whether the employee is allowed to see it. This is now a separate setting, not linked to the Document type anymore. For all documents that currently have the type Employee Login File, we have set the type to 'Other' and visibility for the employee to 'Yes'. For all other document types, this is still set to 'No'. For future improvements on the documents, we'll keep a close eye on our Community.

API: webhooks management via API

Until now, the only way to create webhooks was to logon to your environment and set them up manually on Debtor Level => Webhook Settings. With more and more partners using webhooks, this meant a lot of work. As our goal is to make life easier with integrations, from now on it's possible for integration partners to configure webhooks via the API. All you need to do is to allow this in the user templates.

New calls:

• WebhookSettings_Get => retrieve list of all webhook settings configured for a specific debtor
• WebhookSettings_Insert => insert new webhook setting with events that must be active
• WebhookSettings_Delete => delete a webhook setting
• WebhookSettings_GetEvents => get list of all events that can be activated for a debtor

Improvements

API: EmployeeDocument_UploadDocument 

Due to the new functionality of making a document visible to the employee, we had to adept the correspondent API call. When uploading a document via the API, if you send GuidDocumentType 'Employee Login File' the document will be inserted with type 'Other' and 'Visible to employee' = Yes. We recommend using this new call.

API: EmployeeDocument_UploadDocumentFull

In line with the new functionality to provide access to documents, it is now possible to set the visibility of a document for an employee to 'Yes' or 'No' via the API. With this update the following two new optional fields were added to this call.

• DocumentFolder (int) => in future, it will be possible to define the folder of a document, therefore there is already a placeholder in the API to avoid breaking because of future changes. For now, this field will be ignored.
• VisibleToEmployee (boolean) => is by default false. If set to true, the employee to which the document belongs will be able to see the document with his Employee Login.

Initials required on 'First day at work' form

Upon request, we decided to make the initials a required field in the 'First day at work' form, since this requires little additional work for the employee and the initials are used a lot in the document generation.

Solved bugs

Time Registration: entry for more than one period

The time registration for unpaid Parental leave (1043), Sickness (1004) and Unpaid leave (1009) is now correct when adding an entry for more than one period.

Time Registration: adding Leave

When adding leave directly into the time registration, it looked like it was already approved for the employee in the Employee Leave dashlet, now it shows the status 'Pending'.

API: Reports_Accountant_Debtor_EmployeeWageComponentsPerPeriod_Background

This call was not returning the data correctly according to what is available in the webapp. This is fixed and the call is working as expected now.

Twinfield error

The Twinfield error 'The maximum message size quota for incoming messages (65536) has been exceeded' has been fixed.

Twinfield: when mapping no companies visible 

This issue is connected to the previous one, so it will be fixed with this update.

Overview name and address: missing prefix in column 'Name'

If the employee and employee's partner last names both contained prefixes, the overview Name and address was missing one of the prefixes in column 'Name'. This is fixed.