Mango Release 15.0.1 (Feb 1, 2021)

This is a minor point release on MA 15.X platform that includes PDF viewer enhancement, SAML encryption support for SSO applications and bug fixes. This release went live, Feb 1st on US shared cloud.

  • PDF Viewer Enhancements

    • PDF documents now support a choice of viewers. These include
      • Mango PDF Viewer – This is the default viewer
      • Native Browser PDF Viewer – Use this viewer if you would like the PDF viewer controls to match your browser PDF viewer
      • Download Option Only. No PDF Viewer –  Turn of online viewer and make PDF available for download only
    • Domain admins can set the default for all PDFs in the domain from Modules > Files > Module Settings > Settings
    • File owners have the option to change the PDF viewer to use for their specific files to be different than the default set by domain admin
    • Mango PDF viewer now supports viewing of fillable PDF with form fields

 

  • SAML Encryption for Applications

    • MangoApps as Identity Provider now supports SAML responses to be encrypted and sent to the application
    • There are 3 options for admins to choose from
      • Sign the SAML response
      • Encrypt the SAML response
      • Sign & Encrypt the SAML response
    • MangoApps uses SHA256 bit encryption to encrypt the SAML response

 

  • Bug Fixes

    • Automation workflow reported bugs in MA 15.0 have been fixed in this release
    • Unable to edit post templates in languages other than english has been fixed
    • Search on quick links not working in certain cases has been fixed
    • Issue with calendar rendering has been fixed
    • Unable to save as draft after the post has been send for review has been fixed
    • Team name link was missing which disallowed going back to the team workspace from search results has been fixed
    • Users were able to upload profile photo via a path even when the setting to upload was turned off by the domain admin has now been fixed
    • Request for document approval feed displayed underlying html code has been fixed