Release Note MOXIS 4.52.0

Contents

This overview shows all the improvements, bug fixes and security updates that were made for release 4.52.0.

1. Improvements

1.1. MOXIS

• MOXIS now offers an interface for generating a registration link and for querying the limit for XignUp.

• From now on, MOXIS supports signature fields that have multiple annotation widgets when signing and releasing.

• Another timestamp service has been integrated into MOXIS to provide documents with a qualified timestamp.

• From now on, a reference ID can be shown or hidden on the order creation page and filled in if required. This allows internal reference numbers for orders to be entered and/or corrected via the UI. They can also be used in the protocol and via the API (enterprise feature).

• MOXIS now offers the option of always trusting an SSL certificate in the jobstatusHook.

• A jobStatusHook with OAuth2 can now obtain tokens from Microsoft and Keycloak.

• Annotations in decision levels, which are added when creating an order, now appear in the order log.

• When an administrator connects MOXIS to XignUp, a XignUp tile is visible on the dashboard for clients. This allows a client to create an email template with a XignUp registration link with a single click.

• The MOXIS administration area now offers a separate menu entry ‘Connect XignUp’. This makes it possible to establish a connection to XignUp.

• If multiple visualisations are available, these are now displayed in the protocol.

• MOXIS now recognises PDFs with a defective pre-signature and offers a selection in which you can decide whether you still want to sign.

• It is now possible to use signature comments in the visualisation by configuring the signature profile.

• Chinese characters are now displayed correctly in the signature visualisation.

• The parameter ID of a process, which can be used to list all orders of a process via the API command ‘lookupJobState’, can now be seen in the process configuration user interface. (Enterprise Feature)

• When uploading a locked PDF document for signing via the interface, an improved response is now returned.

• As a user, you will receive feedback when creating a request if no process is configured for it.

• If a document is signed with an invalid pre-signature, an entry will now be made in the log.

• MOXIS now locks form fields that have already been assigned to a specific signer.

• In the new MOXIS user interface, the company branding is visible to MOXIS users.

• From now on, there will be a guided dialogue for approvals in the new MOXIS user interface.

• Users will now receive feedback in the new MOXIS user interface regarding the approval that has or has not been granted.

• From now on, documents can be viewed and downloaded in the new MOXIS user interface.

• The user view for users who are not maintained via an identity management system, so-called database users, has been improved.

• From now on, a reference ID can also be optionally provided from the OfficeAPI.

• A separate signature handler is now available for protocol signing. This can be set up via the user interface.

• When signing with Swisscom, an additional note about the change to the mobile phone was added to the signing window.

• The user interface in MOXIS has been improved based on the reference ID.

• Changes have been made to improve logging with the Swisscom handler.

• If the username contains characters that are invalid in an email address (e.g. semicolon), emails cannot be sent. With the character processing correction, emails with invalid characters can now be sent.

• Address books can now be deleted via the user interface.

• The locking of form fields after a signature can now be configured depending on the MOXIS instance.

• MOXIS is now also available in Romanian.

1.2. MOXIS Guest (for external signers)

• Timestamp signatures have been integrated into MOXIS Guest (for external signers).

• If ‘Text’ is selected for visualisation in the signature window in MOXIS Guest (for external signers), the cursor is automatically placed with focus on the text field.

• The authentication TAN can now also be transmitted via a voice call.

• The display of secondary visualisations for documents with multiple visualisations of a PDF signature is now possible without any problems.

• MOXIS Guest (for external signatories) now offers help with activating the location service.

• The query of the client branding for MOXIS Guest (for external signatories) has been optimised in MOXIS.

• Navigation through the signature window during the location data capture step has been made easier for users.

• MOXIS Guest (for external signatories) now has a new corporate design.

• From now on, the client will receive a notification if the email address of an external signatory is missing.

• In MOXIS Guest (for external signatories), configured success/not success pages are now retained when forwarded after processing (sign/reject).

• The FAQs in MOXIS Guest are now displayed correctly.

• The password entry in MOXIS Guest (for external signatories) has been updated to include missing translations.

• MOXIS Guest is now also available in Romanian.

1.3. Usability

1.3.1. E-mail handling

• The e-mail editor has been extended for certain templates to include the ‘user name’ variable. This ensures that the variable can also be used for the salutation in mail templates.

1.3.2. Templates and reports

• If a client uses a MOXIS template with embedded placeholders for signed documents, a correct message will now be displayed. The template is applied accordingly without embedding.

• From now on, MOXIS administrators will receive information when generating a CSRD report about when data will be available for evaluation.

• Templates can now also be used if the person who is or was supposed to sign has lost the corresponding rights or is no longer stored as a recipient in MOXIS. All existing template data is used and can be added to as required.

• Templates can now be applied to multiple documents at the same time.

• It is now possible to use templates with embedded placeholders with signed documents via the order creation page.

• Umlauts in CSV reports are now displayed correctly.

• Drafts can now be updated when used in the user interface.

1.3.3. Signature process

• If biometric data is collected in a signature process from now on, the signature in the protocol will be marked as an ‘advanced signature’.

• Text adjustments have been made to the advanced signature in the user interface to increase user-friendliness.

• To increase user-friendliness, the character set for entering the SMS-TAN has been restricted, as some letters sound very similar. Thus, D, T, B, P and F have been removed to avoid input discrepancies.

• In the job log, the advanced signature is now identified as ‘personal advanced signature’.

• To improve the user experience, a text adjustment was made in MOXIS for the signing process with Swisscom. This concerns signatures where the second factor on a mobile phone is used.

1.4. XignUp

• The error handling for XignUp connections has been improved.

• The XignUp invitation email, which is automatically generated from MOXIS, has been extended to include links to the XignUp manual.

1.4. Content and content upgrades

2. Bug fixes

• An error in statistics related to releases has been fixed.

• Chinese characters caused an error when rendering the job log in the detail view. This error has been corrected.

• A bug has been fixed: It was not possible to carry out an advanced signature based on ZertES because the signature profile was not recognised.

• An error has been fixed: Orders with a series function generated errors during the signature process in MOXIS Guest.

• A bug has been fixed: The signing process with InstantSign was not carried out correctly. The job continued to be displayed in the MOXIS instance with the status ‘open’, although it had already been completed on the InstantSign side. This error has been corrected.

• From now on, placeholders for multiple visualisations with long names will be displayed correctly.

• The description of the pre-signature was displayed incompletely on the order creation page. This bug has been fixed.

• A bug has been fixed: orders in viewer folders and counters for the number of orders were not displayed immediately in 4.52. This has been fixed and both are displayed again to users.

• When subsequently changing the visualisation type to ‘No visualisation’, incorrect information was stored in the protocol. From now on, the data will be transferred correctly.

• Reports with large transaction volumes were cancelled. This error has been corrected.

• The interface's response has been improved when the processID is missing.

• The error message of the interface when users are missing has been improved.

• From now on, language-specific special characters can be used for process names.

• OAuth 2 is now available as an authentication method for MOXIS web services.

• Old signme data was transferred incorrectly. This error has been corrected.

• A bug has been fixed: Signing with the A-Trust timestamp now works smoothly again.

• The filter button ‘Marked orders’ did not display the orders filtered by ‘marked’. This bug has been fixed.

• If several documents were downloaded simultaneously via the API, an error message appeared. This affected getDocuments and has been corrected.

• From now on, scrolling is possible when evaluating ‘registered users’.

• A bug has been fixed: Filling in form fields with currency symbols triggered an error in some documents. This behaviour has been corrected and filling in fields works smoothly again.

• When special characters from other languages were displayed, errors occurred. From now on, they will be displayed correctly.

• The page for groups in the address book is now the same size as the other tabs.

• A bug has been fixed: an error message was occasionally displayed when MOXIS Guest was accessed. This bug has been fixed and MOXIS Guest (for external signers) can now be used again without problems.

• The response via the API for a user who cannot be found has been improved.

• A bug has been fixed: the API lookupjobState now only returns orders for which the web service user is authorised.

• After updating to the latest MOXIS version, logs of older orders could not be rendered when changing languages. This bug has been fixed.

• The selection of signature regulations for the Swisscom signature type was incorrect and has been corrected.

• When querying the signature regulation for the signature type Swisscom, an error occurred. This has been rectified and the query can be carried out smoothly again.

• When creating an order with a preconfigured group and number of signatories, the number of signatories jumps to the number of selected signatories instead of remaining at the predefined number. This error has been corrected.

• A bug has been fixed: When MOXIS Guest was accessed for the first time (for external signatories), an error occurred. This has been rectified.

• A bug has been fixed: After an update to the latest MOXIS version, logs of old orders could no longer be rendered. This malfunction has been rectified.

• If a document contained form fields that were outside the area visible on the screen, MOXIS jumped to the position, but it was not possible to scroll. The error has been rectified and form fields can now be correctly accessed using the keyboard tab.

• To improve the user experience, the accompanying text for ‘SMS-TAN or password mandatory’ has been changed.

• The email notifications of the email editor for releasing persons were faulty. These have now been corrected and are applicable.

• If a person in a decision-making level signed for themselves and a second time as a representative of another person, the request log could not be rendered. From now on, the request log will be displayed correctly.

• When getReport was applied to a draft in the interface, it provoked a server error. This malfunction has been corrected.

• The behaviour for customers with a licence model in the Keycloak AdminView has been improved.