Platform Server - 11.13.0

Published on 2021-08-23 14:29:25
File
PlatformServer-11.13.0 (Build 31107).exe
Size
222.30 MB
Assets
Installation Checklist EN
InstallationChecklist-EN-11.13.0.html
 MB
Installation Checklist JP
InstallationChecklist-JP-11.13.0.html
 MB
Information

Compatibility
  • Compatible with Development Environment 11, versions 11.0.109.0 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.13.0

  • We improved the experience of the "SEO-friendly URLs for Reactive Web Apps" technical preview. The platform now shows a compilation error when ISAPI Filter, one of the prerequisites, is missing from the installation. (RTAF-4270)
  • New features in emails for Mobile and Reactive Web Apps. Attach files to emails. In addition to the existing widgets, design content with Table, List, and If. The Image widget now supports adding binary content from the database. To use the new widgets, update Platform Server and keep "Emails for Mobile and Reactive" on. To add attachments, update Platform Server and turn on "Attachments in Mobile and Reactive emails". (RTAF-4602)
  • You can now use expressions to set titles of Screens. This lets you change the page title dynamically, and set unique values that show in the browser tabs, bookmarks, and results from the search engines. When using this feature, it is recomended that all developers in the same organization update Service Studio. (RTAF-4738)

Bug Fixing

More details

RPM-1038
Fixed an issue that was causing headers not to be applied correctly in applications.
Application Runtime System Components

Fix Details:
Headers added using the AddHeader action of HTTPRequestHandler weren't being applied to the applications. The symptoms may vary according to the type of header that was added. The issue can happen from Platform Server version 11.9.0 onwards and was fixed in this version to restore the proper behavior, adding the defined headers.

RPM-1040
Fixed an issue that could cause the log file downloaded from the Integration Detail screen in Service Center to be empty.
Application Lifecycle Service Center

Fix Details:
*Symptoms* When attempting to retrieve an HTTP Trace File that after the platform's log rotation occurred, the file will come empty. *How to reproduce* Attempt to download the HTTP trace for the previous week in the Integration logs of the Service Center.

RPM-1052
Fixed an issue with SEO Friendly Urls, that caused a 404 when the module alias had the same name as the module.
Application Runtime SEO Friendly URLs

Fix Details:
The issue occurs in modules that have the same name as the module alias. This created 2 entries in the database table every time you publish, overflowing, in the long run, the 10000 lines DB table limit. To prevent this issue, the DB table limit was increased above the 10000 lines, and there's an automatic cleanup on duplicated entries.

RPM-1245
Fixed an issue that caused the login action to take a long time in Traditional Web apps using SAML 2.0 authentication when the user has many active sessions.
Application Lifecycle Users

Fix Details:
When using SAML 2.0 authentication in Traditional Web apps, the action of logging in is taking a very long time. This happens for very active users with hundreds of active sessions, most typically, users used for testing or automation. The issue resides in the RegisterUserSession action that's not performant in this edge case. This action was improved so that's no longer subject to performance degradation.

RPM-341
Fixed an issue with SEO Friendly Urls, that caused a 404 when the module alias had the same name as the module.
Application Runtime SEO Friendly URLs

Fix Details:
This issue has the same cause as RPM-1052. Refer to it to understand the impacts and changes.

RPM-365
Fixed an issue that caused the join between the system tables Sent_Email and Email_Status not to retrieve any results.
Application Runtime Logging

Fix Details:
This issue caused a join between the system tables Sent_Email and Email_Status not to retrieve any results. This has no impact on the OutSystems capability to send emails, but if you're using the Emails API in your logic, your application can be affected. The fix restored the proper behavior and the results of that join are now correctly retrieved.

RPM-638
Fixed an issue in the Security exceptions of Mobile apps that caused incorrect exception handling.
Application Runtime Logic Execution

Fix Details:
The issue resided in the "Invalid Login" and "Not Registered" exceptions of Mobile apps that were not caught by their parent handler, Security exception. Instead, they were bubbling up to "All exceptions", ultimately causing the wrong exception message to appear to the end-user.

RPM-769
Fixed an issue that caused a consumer to always have outdated references when it has references to a Local Storage Entity.
Service Studio References

Fix Details:
This issue caused a consumer module to always have outdated references when all the following conditions apply: - it's consuming a Local Storage Entity - the identifier of that Local Storage Entity has a foreign key to a server Entity. In this situation, when there are changes in the Local Storage entity, the consumer would always show outdated references even though it was already refreshed.

RPM-905
Fixed the client-side exception mechanism so it properly manages handlers from the parent exception.
Application Runtime Logic Execution

Fix Details:
In Reactive Web or Mobile apps, user exceptions were not properly following the hierarchy of exceptions. The "parent node" exception, User Exception, should be able to handle any "children node" exception, for example, UserException1. Due to this issue, a UserException1 on client-side logic was not being handled by the User Exception parent node, and instead, it was bubbling up to AllExceptions, ultimately causing the wrong exception message to appear to the end-user.