Release Notes
Release Notes
Breadcrumbs

MOXIS 4.50.0, March 21, 2024

Content

In this overview you will find all improvements, bug fixes and security updates that have been made for the 4.50.0 release. 

1. Improvements 

1.1. MOXIS

  • From now on, it is possible to transmit a PDF document via an API call. The API determines placed placeholders and their iterations, creates a listing for each iteration and returns a ValidationCode. If there are no placeholders on the document or if they are not recognized correctly, then an empty list is returned or a corresponding error code is returned.

  • From now on, users will be informed if there is an unassigned signature field on one of their pages.

  • License file export data can now be retrieved from Finance via API.

  • MOXIS 4.50 is now available in all previously available languages plus Spanish.

  • It is now possible to upload the company branding (customer logo, name and favicon) for the instance via the user interface.

  • The logo and the name of the Autenti Trustcenter have been adapted.

  • From now on, additional recipients will be documented in the order log.

  • From now on, PDFA validation can be performed and set via the user interface.

  • The global address book can now be imported, extended, edited or deleted via a web service.

1.2. MOXIS Guest

  • From now on, additional information for signature visualization in MOXIS Guest is available.

  • From now on, certain FAQs concerning signature visualization will only be displayed in MOXIS Guest in visualization mode.

  • Until now, it was unclear to external providers whether the sending was successful and whether transactions were completed. Therefore, an API response for iFrame has been set up for InstantSign.

  • MOXIS now supports another listener for completed MOXIS Guest orders.

  • The MOXIS Guest-MOXIS interface has been extended with isJobAvailable.

  • A "About MOXIS" tab with the version number has been added to the MOXIS Guest user interface. From now on, the version number is also visible in the log.

  • From now on, it is possible for signatories to access the documents again without access restrictions after signing or rejecting the order in MOXIS Guest.

  • From now on, it is easier for external signers to see whether other documents or attachments have been sent in MOXIS Guest.

  • In MOXIS Guest, additional information such as the e-mail address or the telephone number is now available for signature visualization in MOXIS Guest.

1.3. Usability

1.3.1. Document Management

  • From now on, attachments can be downloaded directly in the folder view.

  • From now on, the value Client is also transferred to the Protocol and Job Status.

1.3.2. Form and Signature Fields

  • From now on, formfileds are available in InstantSign.

1.3.3. Templates and Reports

  • It is now possible to specify the mapping from Role to Tenant in moxis.yml reversed.

  • From now on, reports can be downloaded in the MOXIS user interface and the period can be determined independently.

  • The CSRD Report Hook is now active in all MOXIS instances.

  • From now on, a CSRD report can be created in MOXIS.

  • From now on, smooth data collection for CSRD reports is possible.

  • Reporting has been simplified for active users.

1.3.4. E-mail handling

  • From now on, mail templates in MOXIS NEMO can be adapted independently by customers.

  • From now on, the InstaSign link will also be transferred to NEMO for internal emails.

  • NEMO has been integrated into MOXIS 4.

2. Bug fixes

  • After the Vaadin update, some components were damaged, but they were quickly fixed thanks to a profoundly worked out solution concept.

  • The exception when applying Long Term Validations has been fixed.

  • Spring Actuators are now integrated into MOXIS Services.

  • In the signature folders, there was no space between first and last names. This has now been added.

  • The info text for using the shift keys when positioning placeholders has been adjusted for better understanding.

  • The .zip files downloaded from the folder were empty. This error has been corrected and orders can now be downloaded safely again.

  • From now on, users with login names can be correctly invited to selected groups.

  • The [Mark for Signing] button has been transferred from the detailed view to the overview list and displayed there.

  • The date field in the detail view was incorrect and has been corrected.

  • Username can now be checked again in productive SignMe.

  • Changes in bounce management routing and Nemo login roles have been initiated.

  • If two InstantSign pages were open at the same time, an authentication error occurred. This has been adjusted.

  • With preconfigured groups, the recipients were not selectable. This misconduct has been rectified.

  • An error occurred during the migration from MEQA to MOGU. This has been corrected.

  • When using group placeholders in the PDF template, a placeholder was displayed in the UI, but it could not be placed. This misconduct has been corrected.

  • After successful Synaturtype validation, the info text is hidden.

  • A bug was discovered when disabling the toolbox for form fields, which has now been fixed.

  • The data in the CSRD reports are now correctly cited.

  • When inviting external signatories, there was no bounce message. This misconduct has been rectified.

  • Fixed the date picker in the Export License File field.

  • From now on, InstantSign works on the Signature Page.

  • Firefox now displays the customer favicon.

  • MOXIS Webservice no longer sets unwanted session cookies.

  • Deleting roles previously generated an error in the admin UI. This has been adjusted.

  • Previously, UserDetails were not initialized during user registration. This misconduct was eliminated.

  • showDuplicatedUsernameNotification protected in MOXIS Core for Cloud Project has been initiated.

  • The "Back to Document" redirect in MOGU now works smoothly and without an error page.

  • Previously, placeholders could not be picked up and moved during positioning under certain circumstances. This misconduct has now been corrected.

  • The placeholder segment is now also displayed correctly in Safari.

  • A special document with form fields triggered an error message. The behavior has been corrected and the document can now be edited regularly again.

  • Tables were only incompletely visible to logged in users. This has been corrected.

  • The POST subscribe to close the dialog has been restructured.

  • The ad name of the signature handler is now used in the user interface.

  • Special zeals in certain documents are now displayed correctly.

  • Problems occurred when displaying PDF/js with annotations. These have been fixed.

  • SimplifiedAdmin-Conditional on RetryUIView for Cloud instances has been removed.

  • The sending of biometric and Swisscom seal e-mails did not work. This misconduct has been corrected.

  • The text of the signature quality on the application page has been cut off. The issue has been fixed.

  • When calling up two of the same signers, InstaSign ran into an error page. This behavior has been corrected.

  • In some cases, it was not possible to pass through documents. However, the error has been fixed.

  • From now on, Base64 image data will be added to the log when sending e-mails

  • The deletion of the telephone number at Swisscom will now be carried out cleanly.

  • The "Sharer" field in the placeholder sidebar has been renamed to Signer.

  • Signature visualizations can now be performed in the usual quality again.

  • An irregular error occurred when creating users via the user interface in Keycloak. This has been adjusted.

  • Saving mail templates is possible again smoothly.

  • Fixed a bug in the assignment of new releases.

  • Periodic urgency emails to external signers with multiple parallel signers were not sent. This bug has been fixed.

  • Sending admin and process admin mails together with Keycloak provoked an error. This has been adjusted.

  • Templates without configured PDF recipients provoked a null pointer.

  • Internally signed documents did not arrive in MOXIS Guest. The misconduct has been rectified.

  • The preparation of the protocol was not possible under certain circumstances. The error has been fixed.

  • Fixed the incorrect migration of JobStatusHook.

  • The link to share in the login info box has been fixed.

  • The feedback during the password reset was incorrect. The misconduct has been rectified.

  • The About MOXIS page has been updated and updated.

  • The month display in the signature folder view has been corrected.

  • An error occurred while saving changes to the email branding. This has been adjusted.

  • The search by first name is now possible again.

  • During a duplicate session in MOXIS Guest, an error message occurred. This misconduct has been rectified.

  • When creating a user by the same user, an error occurred when using uppercase or lowercase letters. This incorrect behavior has been corrected.

3. Security and performance updates

  • To increase security, a restriction in the event of repeated incorrect password entry has been introduced.

  • In terms of reflected xss, there has been an improvement in the API.

  • To improve performance, caching has been extended to include more entities.

  • In the user query with multiple placeholders, an improvement in performance was achieved.

  • The possibility of a ConcurrentModificationException has been fixed in the SignatureParamterRegistry.

  • The session handling of MOXIS Guets has been improved with simultaneous access.

  • For security reasons, certain Vaadin components have been updated.

  • The performance of the signature folders has been improved.

  • The performance of the signature folders has been improved.

  • Certain database indexes have been set to commonly used tebells to improve performance.

  • The temporary file at startProcess is now deleted correctly.

  • Performance in connection with the order situation and MABS was improved.

  • The stability of the system has been increased.