Release notes Axxerion Release 24.2
Release date 16-03-2024
Changes
Key | Release note |
---|---|
Administrators: The object 'SystemUser' now has a new field 'uniqueReference'. This will automatically be populated with a unique reference and can thus be used as a unique identifier of a system user. | |
Axxerion script / SEPA payments: A new script function is available in Axxerion script, "GenerateHash256". This function takes a document as input and generates a SHA-256 hash for it. This can be used for integrity checks on SEPA payment files. | |
Contact keyword search: The keyword search for contacts now also includes searching in the following fields: -Contact.externalReference | |
Customization (Administrators): From now on, it is possible to filter enumeration items on a page field linked to an enumeration field. This can for instance be used to only show a sub-set of request statussen in the request filter page. An example script for the RequestStatusCode field: result = [] ; | |
Reservations: The maximum number of reservation instances generated from a recurring reservation has now been fixed to 1080 reservations (equal to the maximum in Outlook). Before, it used to be dependent on several different system settings. it is still possible to lower this number on the general client level via the reservation settings page, field 'Maximum scheduled occurrences'. | |
User management: A warning is added when all the user groups are removed from a user that is still active. A user that has no direct user groups linked to it, will not be able to use the system. The warning is added to inform user managers about this potential issue directly. | |
User management: To avoid customers from changing users that are used by Spacewell support or implementation consultants, a non-partner user can no longer change the user settings of a partner user (This is only related to fields on the Systemuser object, not the related contact). | |
User management: To avoid user managers who do not have administrator access themselves, from changing users that have administrator access (Potentially resulting in not having any administrators and needing support to restore this), non-admin users can no longer change the user settings of a user with administrator access (This is only related to fields on the Systemuser object, not the related contact). | |
User management: To avoid users from changing user licenses for users related to Support/Spacewell consultants and technical users related to API integrations, the user license on the SystemUser page is read-only if it has the value Administrator, and this list also does not contain the value Administrator. If any changes to the licenses are needed for these users, these will need to be requested via support (who can change these values). | |
VAT administration: In the VAT declaration the deductable / recoverable VAT is now available as an aggregated amount for a specific VAT percentage type. | |
VAT administration: When the "Non recoverable VAT percentage" is determined, previously only the percentage was set / saved, but it was not clear where it was based on. From now on the link to the VAT configuration record is saved so that it's always possible to determine what the percentage was based on. |
Bugs
Key | Release note |
---|---|
Cost center naming: In error messages cost centers were often incorrectly named or translated. This has been fixed. | |
reconciliations: | |
Reservations: When using the 'Setup' or 'Tidy up' time fields on a reservable object (which can be used to add additional time before or after a reservation on the object, to reserve time for setting it up or cleaning it), decimals (e.g. 1,5 hours) were not correctly supported and it was always rounded down when automatically blocking the period before or after the reservation. This has been fixed. | |
Reservations: Reservable objects (e.g. an area) showed the next reservation (reservable field 'next reservation'), this did not work anymore and has been fixed. When a new reservation is created for an object, this field is correctly updated again. | |
Security: When generating a shared key (AES) for a trust relation by using Axxerion script, the generated key was incorrectly formatted which prevented the user to make use of it. This has been fixed, the correct formatting is now applied. | |
SSO / SAML: Updated the SAML library to prevent a check on the SAML sessionIndex, which is an optional parameter and checking it could result in incorrect errors. | |
Unsupported characters: When updating data in text fields via a planning script (for instance via an API) that contains unsupported characters (For instance, certain smileys that are not supported in our current Unicode version), an error was thrown and the script was deactivated. This has been updated, such that the unsupported characters are skipped and the script continues without an error. |