Skip to main content
Skip table of contents

Release Notes MOXIS 4.49.0

Table of Contents

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


1. Enhancements

1.1. MOXIS

  • The buttons [Save draft], [Save template] and [Send order] were previously hidden when more than one decision level was inserted. To improve usability, these are now always visible.

  • From now on, if a customer logo is available, our poweredBy logo will be displayed. If there is no customer logo, the MOXIS logo will be displayed.

  • During the signature process, clear feedback will be provided to prevent signature processes from being cancelled unnecessarily in the future.

  • The knowledge base can now be accessed directly via an icon in MOXIS.

1.2. MOXIS Guest

  • A help button has been added so that you can access the knowledge database directly from MOXIS Guest.  

  • Previously, it was not possible to see images uploaded as attachments in MOXIS Guest. This led to confusion in handling, which is why images are now displayed after uploading. If non-displayable file types are uploaded correctly, users receive a message.  

  • To improve the user experience, uploading logos for emails in MOXIS Guest is now more flexible in terms of size.

  • The rejection reason for MOXIS Guest can now be controlled via the process configuration.

  • The PDF viewer from MOXIS Guest is now available for InstantSign.

  • From now on, MOXIS Guest also stores which graphics can be uploaded in which file formats for signature visualisation.

  • From now on, there is the option of storing additional information, such as an email address or telephone number, in MOXIS Guest for signature visualisation.

1.3. Usability

1.3.1. e-Mail Handling  

  • The user experience for external signatories has been improved. When entering email addresses, the name and email address are now automatically split.

  • From now on, email headers will be enriched with additional information, such as an order number.

1.3.2. Templates and Reports

  •  It is now possible to define different signature profiles for each tenant (client).

1.4. Content and content Upgrades 

  • The texts in the signature type menu have been adapted to improve usability.

  • The logo in the order protocol has been updated and several text adaptations have been made for easier comprehension.

  • The fonts in MOXIS and MOXIS Guest have been standardised.

  • The designation for the Swisscom seal in the signature folder has been changed to ZertES seal to avoid confusion among users in the future.

  • The button design and wording in the order creation page has been adapted. In addition, the decision level now opens automatically, even if no document has been uploaded.

  • In order to standardise content and make it easier for end users to understand, text adjustments have been made to the simple and qualified signatures and the release. 

2. Bugfixes

  •  FolderAPI is available again.

  • The display of the time format has been corrected in the protocol and is now adapted to the 24-hour format.

  • From now on, when the phone number and language are changed in the address book entry, the placeholder is retained in the order creation page.

  • The behaviour when editing external groups has been corrected. It now works the same way as for internal groups.

  • An error in the group iteration that affected post-processing has been corrected.

  • Template migration is now possible without errors.

  • The user interface for displaying address books on smaller screens in a responsive design has been corrected. From now on, address books can be viewed without any problems even on smaller screens.

  • An error with an empty default location in reason has been fixed.

  • An error that occurred when uploading documents with links has been fixed. From now on, managing documents with links is possible without any problems.

  • A space has been added between the customer logo and powerdBy MOXIS. From now on, the two will no longer overlap.

  • An error that occurred when displaying orphaned users has been fixed.

  • The null pointer in hooks without configuration has been fixed.

  • The error when calling findMOXISUserByID has been fixed.

  • It is now possible to display signature fields in PDF forms again without any problems.

  • The user page no longer gets stuck on the search query.

  • In Edge and Chrome, the upload window is now only displayed once.

  • The error when deleting a draft with a date field has been fixed. Deletion is possible again without problems.

  • It is now possible to add a second placeholder of the same size as the first.

  • From now on, changing a signature quality can be done with one click instead of two.

  • xIDENTITY in combination with Long Term Validation no longer causes errors.

  • Performance when placing placeholders on large documents has been improved.

  • The behaviour of drafts in PDFs with form fields when saving and loading has been corrected. They can now be edited smoothly.

  • From now on, when users click on the group icon, the address book opens and a group member can be selected. The [Save] button no longer displays a number in brackets. After saving, the person selected by the user is visible in the decision level as a signatory/approver for the group.

  • The image size on the login page has been corrected.

  • The selection field for the company seal is now displayed enlarged.

  • The distance between the customer logo and poweredBy MOXIS has been increased so that they no longer overlap.

  • Missing translations have been added.

  • The [Reserve] button has been renamed and standardised.

  • The icon for the process selection search is now available in a larger design.

  • Previously, the modal for representations with long process names was too wide. This behaviour has been corrected.  

  • An unwanted scrollbar in the process management has been removed.

  • Placeholders were cut off when names were long. This has been fixed.

3. Security- and Performanceupdates

  • Springboot was updated. 

  • Old Angular components were recreated in React.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.