New in Release Sep.2018
- Added a new application and module type (Services) to promote a better application segmentation and governance. (ABE-1276)
- Added a new language element (Service Action) which is a loosely coupled action (REST underneath) with impact analysis and security by default. (ABE-1277)
- Optional parameters and attributes do not require refreshing consumers, making larger systems more loosely coupled and allowing independent teams to release more often without impacting each other. (ABE-1278)
- Public Screens are now loosely coupled, avoiding circular references in dependency analysis. (ABE-1279)
- It's now possible to deploy and run OutSystems applications using Windows Docker Container in an on-premise Docker container environment, or in a cloud environment like Amazon (in Elastic Container Service) or Azure (in Azure Container Service). (RSAT-505)
- The concept of Zones was revamped and it's now called Deployment Zones and have them associated to a hosting technology when application will be deployed. (RSAT-612)
- A set of tools is now available to collect information about the Docker container and application health in order to help the troubleshoot or gather relevant information to the analysis. Check these troubleshooting tools here. (RSAT-829)
- "Automatic" in the Deployment Mode section. For more info on how to configure the URLs that trigger the deployment actions, check How to automate Docker container deployment with Jenkins. (RSAT-395)
- When an application is associated to a Deployment Zone configured to use containers as hosting technology, OutSystems platform will generate a bundle with all the assets needed to allow build and run your application in a container. (RSAT-385)
- Fixed a container-related issue that left temporary files behind after aborting a solution that was published in the two steps mode. (RSCT-1379)
- OutSystems Management Consoles gives you the possibility to defined the hosting technology for your applications. That technology is now visible though their logos in Lifetime animations. (RSAT-769)
- Provided an hosting technology associated to Pivotal Cloud Foundry. When applications associated to a Deployment Zone with this kind of hosting technology are deployed, a bundle with all the assets are generated in order to deploy and run OutSystems applications in Pivotal Application Service (PAS). (RSAT-694)
- It is now possible to define the desired Deployment Zone for an application during the preparation of a staging operation in LifeTime. (RSAT-744)
- SOAP Web Service Methods now support default values in Input Parameters, Output Parameters and Structure Attributes of SOAP Web Services. The minOccurs/nillable WSDL attributes are now taken into consideration when determining mandatory Input Parameters and Structure Attributes. (RINT-1833)
- Added support for consuming SOAP web services with Enumerations. (RINT-1764)
- Introspect a WSDL that requires the basic authentication by passing the username and password into the URL (e.g. https://username:password@server/example.com?wsdl). Inspired by Darren Conroy's idea. (RINT-1656)
- It is now possible to define the authentication type and the corresponding credentials for an imported SOAP 1.2 web service. (RINT-1225)
- It is now possible to dynamically authenticate with different credentials per SOAP 1.2 web service method. (RINT-900)
- It is now possible to override the authentication credentials for a SOAP 1.2 web service in Service Center. (RINT-897)
- It's now possible to configure and see logs of consumed SOAP 1.2 web services in Service Center. (RINT-841)
- Added support for consuming SOAP web services with nillable attributes. (RINT-835)
- It is now possible to override the default service endpoint for a SOAP 1.2 web service in Service Center. (RINT-899)
- It's now possible to store logs in a separate database from the one storing the data used by business applications and the data that supports the platform runtime (thanks to Didier Miller for highlighting this need as an idea). (RRCT-1472)
- Applications are now self sufficient regarding logging their own information. From now on the logging mechanism do not rely on an external service (LogService). (RRCT-839)
- The logs of the query errors from Aggregates and Advanced SQL now contain more details. (RRCT-1918)
- Unattended Installation API was updated to take in consideration a possible split between platform database and logging database (RRCT-1783)
- We improved the 1-Click Publish performance of the published modules by making the deploy phase differential. The smaller the number of modified resources, the more noticeable the speed improvement is. (RSCT-1436)
- Application debug mode no longer depends on environment type (e.g. DEV, QA), making it possible to debug applications in all environments. Introduced new types of environments to allow for more flexible management of infrastructures. (RSCT-1148)
- Web Blocks now support Events and Event Handlers to propagate changes to their parent element. (RAFT-1371)
- You can now use ListDistinct, a new client and server action. The action removes duplicates from the list. Inspired by Carlos Henriques' idea. (RCOT-1108)
- Inputs now have aria-required and aria-invalid attributes in web runtime applications. (RAFT-1292)
- HTTPS is now maintained even when navigating to a Screen not explicitly marked as requiring HTTPS. (RRCT-1399)
- Binary Resources referenced by Web Applications now have a 'by-copy' semantic and are automatically copied to relevant consumer Modules. (RRCT-1155)
- New method registerDeviceClassGetter added to JS Public API allows to change the default behavior of adapting the css classes applied to the device resolution. By default, resolution higher than 1024px are considered tablets. (RAFT-1296)
- To achieve higher performance, you can now create stateless BAPI calls to the SAP servers. (RINT-1934)
- Changed the default User Provider for blank modules to match the provider of the Application Template in use. (RRCT-1858)
- Configuration Tool now automatically changes the pipeline mode to "Integrated" in IIS Application Pools that only contain OutSystems applications. (RSAT-295)
- OutSystems caching mechanism now uses RabbitMQ system to forward cache invalidation notifications to OutSystems applications. (RRCT-835)
- You can now use Configuration Tool, via UI or Unattended Installation API, to install and configure the Cache Invalidation Service (RabbitMQ). (RRCT-1728)
- To prevent runtime problems, the Session Database upgrade step is now mandatory during the Platform updates. (RSAT-974)
- Removed support for SMS feature. (RRCT-1639)
- Deprecated BeginReadUncommittedTransaction and BeginTransaction methods from RuntimePublic.Db API. (RSAT-791)
- Fixed a bug that caused the processing of error logs to fail with long Action names. (RPD-1769)
- Fixed the bug that caused "Could not login to 127.0.0.1" error while publishing the "Current Running Version" of a Solution in Service Center. This caused issues in some upgrades. (RPD-2415)
- Improved the Resources error message about paths that are too long. (ABE-1214)
- Fixed invalid login error when using Integrated Authentication for both database and web service consumption. (RPD-3417)
- Fixed an error related to the generation of the application icons when uploading an icon or creating a solution by uploading an OSP or OAP. (RPD-3444)
- Fixed splash screen hanging in iOS when Content Security Policies are enabled. (RPD-3428)
- Fixed an installation problem that was recreating the default Global Zone even after you had deleted it. (RSCT-1412)
- Fixed an issue that was keeping unnecessary files in the "repository" folder on the server, increasing the folder size. (RSCT-1227)
- Fixed problem that caused a module publish operation to fail due to a concurrent publish even when that module was not being published anywhere else. (RSCT-1267)
- Fixed a problem where publishing simultaneously modules with identical names in different personal environments would result in having future publication attempts of those modules blocked. (RSCT-1287)
- Fixed a bug that caused invalid generation of the CSP HTTP headers when using the default values from the Service Center settings. This prevented a small number of iOS apps from loading after the splash screen. (RRCT-1966)
In some situations, the new SOAP implementation in OutSystems 11 incorrectly serializes input parameters of Date, Time and DateTime data types for consumed Web Services, which might cause data corruption (namely losing time offsets for Time and DateTime data types) when sending values of these data types. This new implementation is used for all consumed SOAP Web Service elements created in version 11.
The previous behavior (in OutSystems 10) is the following:
— Values of Time data type are sent without date information and with timezone information (offset).
— Values of DateTime data type are sent with timezone information (offset).
— Values of Date data type are sent without time information.
In OutSystems 11 up to version 220.127.116.11 the incorrect behavior is the following:
— Values of Time data type are sent with (unnecessary) date information and without timezone information (offset).
— Values of DateTime data type are sent without timezone information (offset).
— Values of Date data type are sent with (unnecessary) time information.
The incorrect behavior has been fixed in version 18.104.22.168 to match the OutSystems 10 behavior.