Platform Server - 11.10.1

Published on 2020-12-14 21:37:31
PlatformServer-11.10.1 (Build 23852).exe
211.21 MB
Installation Checklist EN
Installation Checklist JP

  • Compatible with Development Environment 11, versions or later.
  • Can be managed by LifeTime 11, Release Sep.2019 or later
Additional Resources For further information on any issues, use the Support Portal.

NOTICE: OutSystems does not give support to any undesirable behavior you may experience due to the use or manipulation of undocumented components of the OutSystems platform, such as, internal JavaScript, RuntimePlatform library, database system meta-model, components in installation directories, etc.
Release Notes

New in Platform Server 11.10.1

  • Multilingual for Mobile and Reactive now maintains the selected locale between applications. (RAR-338)

Bug Fixing

  • Fixed an issue with the message after an upgrade is rolled back. The message that notifies the user that the upgrade failed now correctly shows. (RAR-423)
  • Fixed navigation after a pending refresh. Now the screen redirects to the destination screen if there's a pending refresh when the user refreshes the page. Previously the app showed the origin screen after the refresh. (RAR-422)
  • Fixed PWAs crashing in OutSystems on iOS when accessing Local Storage. The crash was introduced by a bug in WebKit ( (RAR-374)
  • Fixed "No Default Screen" error screen when no default screen is selected. Now the app uses the first screen of the module and there's no error. (RAR-356)
  • Fixed a bug introduced in version, that caused already imported SOAP Web Services to fail to publish, if they had defined SOAP headers as either input or output for methods, even if they weren't being used. (RPD-5225)
  • Fix for connections left open in the database when modules start (RPM-504)
  • Fixed incorrect redirect to Users module after login using SAML Authentication for end-users. (RPM-395)
  • Validation and Upgrade messages can now be properly translated in Reactive and Mobile applications. (RTAF-3427)
  • The page title is now correctly translated in the runtime of Reactive Web Apps and Mobile Apps. (RTAF-3505)
  • Fixed a rare issue where publishing an extension would impact the database tables used by another module. (RPST-1039)
  • Using .Net Framework 4.7.2 Oracle DB Provider. (RSAT-2481)
  • Fixed potential deadlock in OutSystems services when generating error logs while persisting logs in the database. (RRCT-3222)
  • Added a new NameId format option in SAML configuration of the Users module (<Ignore field>). This new option allows you not to send the NameId format field. (RIDT-355)
  • Fixed an issue that allowed code injection on the description of exposed SOAP Web Services. CVSSv3.1 score 4.8 (Medium). (RBIT-37)

Known Issues

  • In farm environments, if there is a symbolic link to the Platform Server folder, it’s possible for the Configuration Tool to be executed from different locations. e.g “F:\Program Files\OutSystems\Platform Server” is the platform installation folder and “C:\Program Files\OutSystems\” is a symbolic link. Every time Configuration Tool is run from a different location, it will corrupt some platform settings and it will cause DLLs to be wrongly deleted from the front-end.
    More details here.