Release Notes MOXIS 4.53.0, May 15, 2025

Content

This overview lists all improvements, bug fixes and security updates that have been made for release 4.53.0.

1. Improvements

1.1. MOXIS

From now on, the exact signature time will be read from the signed document for display in the MOXIS user interface and in the log.
To increase the reliability of the time stamp, two time stamp servers can be stored.
Due to the introduction of the XiTrust MOXIS Teams Connector, a new job status hook has been added to the hooks in MOXIS Administration, which is linked to the Teams Connector.
After migration, it was ensured that ‘old’ user IDs would continue to be recognised in MOXIS during the placeholder scan.
From now on, the telephone number will also be displayed in the general overview of the address books.
From now on, the timestamp and time zone will be shown correctly in the log.
From now on, logs for non-final orders can be downloaded in various languages via the API.
Archived log data can now be downloaded via the API.
Another REST method has been introduced. Now a CSV file can be transferred via the audit trail, allowing a PDF to be generated.
Log data will now be stored as metadata. This ensures that it can be downloaded via the MOXIS user interface after the job has been deleted.
From now on, comments from the decision levels will also be shown in the log.
The MOXIS Document Creation Service is now also available in a version without Docker.
Text adjustments have been made in MOXIS. These relate to the term ‘mobile phone signature’, as it is outdated and has been removed from the product accordingly.
If a document with signature protection must be signed, MOXIS removes the protection. For reasons of traceability, this process is now documented in the log.
A translation error in the English audit log has been fixed. ‘User created’ has been replaced with ‘User changed’.
From now on, special times will be displayed correctly throughout the user interface.
The character length of the reference ID is now limited to 255 characters.

1.2. MOXIS Guest (for external signers)

For reasons of better traceability, the corresponding MOXIS ID and MOXIS job number will now be logged for jobs in MOXIS Guest.
There is now a new class for signature fields in the API. Thanks to this, the language, telephone number and signature name are transferred to MOXIS Guest.
A self-service identification procedure has been introduced in MOXIS Guest for external signers. If an external signatory does not have a digital identity, it can now be created quickly and easily in the browser based on Swisscom during the signing process.
External signers in MOXIS Guest can now upload attachments during the signing process. This reduces the amount of work involved, as attachments can be returned directly with the order if necessary and do not have to be sent separately by email.
Accessibility in MOXIS Guest for external signers has been further improved and expanded.
From now on, clicking on the signature visualisation in MOXIS Guest for external signers will open the signature modal. If there are several, you can navigate back and forth between the visualisations.
Chinese characters are now displayed correctly in the signature visualisation and user bubble in MOXIS Guest for external signers.
From now on, an additional advanced seal with qualified features can be used in MOXIS Guest for SES and FES.
Identifications and transactions carried out via self-service identification procedures based on Swisscom in MOXIS Guest for external signers will now be logged in the MOXIS Guest database for billing purposes.
The brand new ‘Upload attachments’ feature in MOXIS Guest for external signers can now be set up in the process configuration.
Text adjustments have been made in MOXIS Guest for external signers. These relate to the term ‘mobile phone signature’, as it is outdated and has been removed from the product accordingly.
“Open Sans” has been set as the default font in MOXIS Guest for external signers.
From now on, the zoom factor in MOXIS Guest will be retained for external signers when switching between documents.
In MOXIS Guest for external signers, documents are now listed in the order in which they were uploaded from MOXIS.

1.3. Usability

1.3.1. E-Mail Handling

From now on, a representative, provided the function is used, will also receive a completion email when a job is completed.
From now on, the MOXIS E-Mail Editor can also be used on installations without Keycloak.
From now on, additional exciting resolvers (placeholders for customising email templates) are available in the MOXIS mail editor. For more information, please refer to the XiTrust documentation.

1.3.2. Templates and reports

An additional variable, ‘Deletion period (date)’, has been introduced in the MOXIS E-mail Editor to expand the repertoire.
Missing translations for mail templates have been added to the MOXIS E-mail Editor.
The use of signature and rejection comments has been extended to other templates in MOXIS.
The MOXIS Mail Editor now has an additional template. This informs internal users involved in the process about the conclusion of a contract.
The text in email templates for job timeouts has been corrected.

1.3.3. The signature process

It has been ensured that PDFA1a and 1b compliance is maintained for signatures with Swisscom.
MOXIS has been added a new, advanced seal with qualified features. As a result, there is also a new signature handler that allows signatures with this seal.
The log entries for errors occurring during the signature process with Swisscom have been improved.
If a signature is carried out based on Swisscom, a message will appear during the process informing you to switch to MobileID.

2. Bugfixes

A bug has been fixed: Previously, rendering logs depended on opening the detail view. This bug has been fixed. Logs can now be rendered independently of opening the detail view.
A bug has been fixed: The variable was not stored correctly in an email template for administration. This error has been corrected.
A bug has been fixed: InstantSign now only locks form fields assigned to the signer after the signature process has been completed.
A bug has been fixed: In MOXIS Guest, you can now sign with A-Trust again using the latest iOS versions.
A bug has been fixed: An error occurred when saving drafts. This has been fixed.
A bug has been fixed: Additional signers who were invited did not receive notifications via the MOXIS email editor. This issue has been resolved.
A bug has been fixed: If the category was mandatory in a batch process, the process could not be started. This behaviour has been corrected.
A bug has been fixed: Previously, it was not possible to upload multiple documents in a batch process if the expiry date could not be changed. This has been fixed.
A bug has been fixed: When using templates that were supposed to be signed invisibly, the log might have shown ‘Visualisation applied’. This bug has been fixed and replaced with the correct message.
A bug has been fixed: After a job was released, it was not listed in the ‘Closed’ signature folder. This issue has been resolved.
A bug has been fixed: If the name and email address of a constituent were longer than 120 characters in combination, jobs could not be created. This has been fixed.
A bug has been fixed: If ‘Clean up unsigned documents’ was enabled in the process configuration, documents could not be uploaded for signing. This issue has been resolved.
A bug has been fixed: If the email address or telephone number was changed by the constituent during external signing, it was not transferred. This has been corrected.
A bug has been fixed: Special characters caused an error when entering the XignUp URL. This issue has been resolved.
A bug has been fixed: From now on, the form fields of the last signer will no longer be locked if several people have been invited to an iteration level and form fields have been assigned to them.
A bug has been fixed: After applying a draft, the job ended up in the ‘Completed’ folder in the ‘Received jobs’ folder. This issue has been fixed.
After it was determined that redundant emails were being sent when tenant mapping was not clear, this issue was fixed.
A text correction has been made in the process configuration in the settings for email notifications when a job is cancelled.
A bug has been fixed: Documents with rejection comments attached to the PDF are now displayed again in the detail view.
A bug has been fixed: If SMS TAN was set as optional and no telephone number was entered for the external signer, the signature was incorrectly indicated as ‘advanced signature’ in the log. This error has been corrected.
A bug has been fixed: From now on, the TAN window will revert to the language settings (locale) from the API call.
A bug has been fixed: Some scanned documents were displayed in black in MOXIS Guest for external signers. This issue has been resolved.
A bug has been fixed: After changing the signature text in MOXIS, the text was displayed very small in the visualisation. This has been fixed.
From now on, user data in MOXIS Guest can be verified again when signing with Swisscom.
The Clear button overlapped the text in MOXIS Guest. This has been corrected.
From now on, MOXIS Guest will correctly display the PDF preview for external signers when signing via the A-Trust app.
From now on, the note ‘verified by SMS and/or phone number’ will be added to the log created by the new Document Creation Service.
A bug has been fixed: Due to the introduction of the self-service identification process in the browser, it was no longer possible to sign via signme. The error has been fixed.
A bug has been fixed: Form fields were previously locked at the iteration level when an invitation was sent via a group. This issue has been resolved.
From now on, the times in the MOXIS E-Mail Editor will be displayed correctly in UTC+ for summer time/winter time.
A bug has been fixed: In the MOXIS E-mail Editor, the constituent was specified in the templates for notifying the representative instead of the person to be represented.
A bug has been fixed: When creating a user avatar, an exception occurred if the user was submitted without a first and last name.
A bug has been fixed: MOXIS Guest for external signers previously used the browser language as the default if no locale was available. The issue has been resolved.
A bug has been fixed: If no language was specified in the API for external signers, the default language was not transferred from MOXIS to MOXIS Guest. This issue has been resolved. The default language from MOXIS is now transferred to MOXIS Guest if no language has been specified for external signatories via the API.
A bug has been fixed: In MOXIS Guest for external signers, the signature page was restarted instead of ‘Process cancelled’ for the A-Trust-Seal signature handler and the time stamp service. This error has been corrected.
A bug has been fixed: From now on, signature visualisations will be displayed within the signature fields again and no longer above them.
A bug has been fixed: If RESTService was subsequently deactivated in a process, the WebserviceUser could still create jobs. This has been fixed.
A bug has been fixed: Previously, when a job with a locale was transferred via the API, an error occurred in MOXIS Guest for external signers after the signing process. This malfunction has been prevented and signing now works smoothly again.
From now on, signing with signme in MOXIS Guest will work smoothly again for external signers.
A bug has been fixed: From now on, some special characters in file names will no longer cause errors in MOXIS or MOXIS Guest for external signers when downloading files.
A bug has been fixed: When creating a draft, instant sign links were generated. This behaviour has been fixed.
A bug has been fixed: An incorrect role was passed to approvers in processInfoService. This behaviour has been corrected.
From now on, bounce management will work again with email delivery (even without using the MOXIS E-mail Editor).
The text for the terms of use was not displayed correctly after the last update when logging in for the first time. This has been corrected.
A bug has been fixed: A link to the document was incorrect. As a result, email templates in the MOXIS E-mail Editor have been corrected accordingly.
A bug has been fixed: All three visualisation types (text, drawing, image) are now available again if signature drawing has been set to optional in the biometric data.
A bug has been fixed: A resolver for substitution was triggered incorrectly. From now on, the correct information will appear in the visualisation again.
A bug has been fixed: In MOXIS Guest, signatures with biometrics caused an error for external signers due to Bouncycastle. This issue has been resolved.
An occasional cancellation during the signing process in MOXIS Guest for external signers has been fixed.
In MOXIS Guest, an error was mistakenly displayed when the user was also the constituent. This issue has been fixed.
Certain special characters are now displayed correctly in the MOXIS user interface for MOXIS instances with MS SQL.

3. Security Updates/Performance

General security and performance improvements have been made.