Version 4.50.3 | Platform Release Notes

This is the planned release schedule and content for Version 4.50.3

Timing

What's New?

Movius Platform Enhancements:

1. Language Support - Portuguese: If language support is enabled for the customer, Customer Admins can now select Portuguese when creating a new user account. This setting determines the language used in automated messages sent from the Movius platform to the users.

   • Note: With this addition, the platform now supports automated messaging in: English, French, Spanish, Italian, German, Flemish (Dutch), and Portuguese. This update does not imply that the MultiLine app itself supports these languages. 

   • 

     MMP view while creating an account

2. Enhanced Read-Only Admin Capabilities: Read-Only Admins can now view user account details. Previously, these admins were unable to access user account information. With this update, they will have the same visibility as Admins with edit permissions — but will remain restricted from making any changes.

   • This enhancement provides organizations with greater flexibility in granting user accounts visibility while maintaining the integrity and security of account management.

3. SSO Integration: SAML Assertion Support for Admin Access at Sub-Org Level: We have enhanced MMP to support Single Sign-On (SSO) via SAML assertions with dynamic administrator provisioning. 
   • Highlights:
   • Customer Administrators can now log in to the MMP Portal using SAML assertions containing Email and Role@Sub-org from their organization's IDP.
   • Dynamic admin creation: Admin accounts are created automatically upon login, based on the SAML-provided Role and Sub-org — no pre-provisioning required.
   • Validation rules:
   • The Role in the SAML assertion must match an existing role at the specified Sub-org in MMP.
   • The Sub-org must exist under the correct top-level organization.
   • The combination of Org and Role must be unique for each admin session.
   • This implementation ensures secure, role-specific access at the sub-organization level while simplifying administrator onboarding.

4. Teams MultiLine Messaging – Account-Level Toggle Management: Admins can now view and manage the Teams MultiLine Messaging enablement toggle button for individual accounts within the Movius Management Portal (MMP).

   • For accounts created via Provisioning APIs or Bulk Provisioning, the toggle will be enabled by default if Teams Messaging is activated at the organization level (see image below).

   • 

   • There is no change to manual account creation — admins must continue to manually enable the toggle during setup for each new account. See image below:

   • 

5. WhatsApp API Solution – Improved Error Handling: Enhanced the user experience by providing clearer, more detailed information for any errors returned by the WhatsApp Business API when a MultiLine user leaves a conversation, adding or removing participants in a group chat, or resuming a paused conversation. Users will see these notifications in both the MS Teams MultiLine Messaging app and the MultiLine mobile apps.  

Platform Enhancements for native WhatsApp and iMessage capture

• Additional changes have been made to the platform to support the launch of a new product to capture messages from native WhatsApp and iMessage apps. These foundational updates ensure seamless integration and support for the new messaging compliance solution.

Bug Fixes:

CS-233599	Resolved an issue where Number Utilization Alert emails sent to Admins did not always display the Movius server geo name in the subject line. See SG1 shown in the subject line (correct example) in the image below:
CS-234067	Fixed an issue where roles in the SAML response could not be parsed if the role value did not match the expected case. Role parsing is now case-insensitive, improving reliability and ensuring successful login even if the role casing differs between the IDP and the MMP system.
CS-234349	We addressed an issue in the Message Report API that could cause missing or duplicate message records when using an offset in the request. This occurred if multiple messages had the same timestamp near the offset point, which could result in skipped records or the same record appearing in multiple responses.

Version History