OpenEdge Release | Version Information |
---|---|
11.3.3, 11.3.4, 11.4, 11.6.2, 11.6.3, 11.7, 11.7.1, 11.7.2 | Release 11.3 #46656@2018-05-28 |
OpenEdge 11.7 Service Pack 2
We are announcing full compatibility with the Service Pack 2 for OpenEdge 11.7 (OpenEdge 11.7.2).
See further remarks below.
Deletion of SmartDataAdapters and BindingSources
In SCL-2019 we have changed the clean-up behavior of the SmartDataBrowser control when a Form is closed. After this change, the SmartDataBrowser will delete it's linked SmartDataSource (e.g. SmartBusinessEntityAdpater) instance and DataSource (binding source). In rare cases, where those instances may still be required after the form containing the browser have been closed, developers can set the following new property of the SmartDataBrowser to FALSE:
|
Your action may be required!
Changes to the SmartDB and SmartDB upgrade and migration utility
Announcing the SmartFramework ERD Designer
We are announcing the availability of the SmartFramework ERD Designer
Following the release of the OpenEdge 11.7 Release we have completed our testing of the SmartComponent Library on this release of Progress and are proud to announce formal support for the SmartComponent Library on OpenEdge 11.7 with the 2017-04-24 release of the SmartComponent Library. Generally we recommend customers on OpenEdge 11 to upgrade to OpenEdge 11.7 quickly. Starting the 2017-07-14 release we are supporting OpenEdge 11.7 Service Pack 1 (11.7.1).
Starting the 2015-10-09 release the Business Entity Designer will feature a start page with links to most recent release note articles on this site.
With SCL-751 we have adopted native Enums for OpenEdge 11.6. To activate this feature customers must add a definition to products.i. SCL-751 provides details for this.
With SCL-1113 we have modified the templates for SmartWindowForms and SmartTabFolderPages generated from the Business Entity Designer. We have removed the initialization of the viewer controls SmartTableIOState property (value was set to "NoDataSource" within the InitializeComponent method). Customers using their own set of templates should adopt the same fix to their templates.
During our tests on OpenEdge 11.7.2 we have experienced two issues:
We consider it mandatory for customers using OpenEdge 11.7.2 to use at least the release #44166@2017-11-27 of the SmartComponent Library.
Due to an fix for
from Progress Software for in OpenEdge 11.7.2.001 we further recommend all customers to apply this hotfix as well.
We have updated proparse with further enhancements in this release (see https://github.com/consultingwerk/proparse/releases/tag/4.0.1.1176). Please download the .NET Assemblies ZIP file from our ESD and replace the proparse.net.dll in your environment with the latest one. The new assembly reference is:
|
As proparse is used by our Business Entity Generator, this new version of the proparse.net Assembly is also relevant for customers not doing GUI for .NET development and require support for parsing new ABL language constructs.
This version of proparse provides additional methods for refactoring purposes. The most recent code in the Consultingwerk.Studio package relies on those methods. It's therefore mandatory to update proparse to this version.
We've updated the SmartHybridRealm class used for http authentication to leverage the IAuthenticationService. It is therefor required that for AppServers requiring http Authentication (e.g. REST or Web) the correct IAuthenticationService implementation is registered (using service.xml files).
Customers relying on the previous behavior should ensure that the Consultingwerk.SmartFramework.Authentication.AuthenticationService is regsitered as the IAuthenticationService. This implementation will authenticate users against the password stored in the SmartUser database table.
When users with no Login Company set should be able to login using the SmartHybridRealm, it's required to set the Login Company Tennant Domain (similar to the field in the Login Company Maintenance) in the .restapplicationsettings / .applicationsettings, e.g.:
"DefaultAuthenticationDomain": "consultingwerk" |
This is required as the Hydrid Realm Interface from Progress does not provide the domain name to the authentication method.
This is an overview of the web handlers supported by this release
|
Starting August 14th 2016 we ship our source code also as UTF-8 encoded. The ZIP files ending with _utf8.zip contain the source code encoded with that code page. The source code in the remaining archives is still encoded in ISO8859-1. Also on Github there is a new branch containing the OpenEdge 11 based source code in UTF-8.
Related article (Progress K-Base): How to get Progress Developer Studio to save in UTF-8 encoding
http://esd.consultingwerkcloud.com/
https://github.com/consultingwerk/SmartComponentLibrary
We have fixed an issue where the Business Entity Designer was not using the split array settings (leading zeros, split character) when refreshing a temp-table from the database tables.
We are now shipping PCT Version 209 (https://github.com/Riverside-Software/pct/releases/tag/v209) with the SmartDB upgrade and migration utility.
We are now encoding the curly brace in the query string received by the ResourceWebHandler (JSDO Generic Service). Previously GET requests with a filter QueryString value of
filter: {"ablFilter":"Name BEGINS 'lift{'","tableRef":"eCustomer","viewTables":"eSalesrep","orderBy":"","skip":0,"top":10} |
caused a runtime error when preparing the Data Access query.
Prior to this enhancement, the /web/Catalogs/{PackageName} web handler returned an empty response when not Business Services have been found (invalid .classpath configuration, no r-codes present or invalid rackage requested). We're not returning an http 404 error with the following content:
{ "title": "An application error has occurred (Consultingwerk.OERA.JsdoGenericService.WebHandler.NoBusinessServiceFoundInPackageException)", "error": "Consultingwerk.OERA.JsdoGenericService.WebHandler.NoBusinessServiceFoundInPackageException", "message": "No Business Services found in package Consultingwerk.SmartComponentsDemo2.OERA.Sports2000.*", "messageNum": 0, "callStack": "HandleGet Consultingwerk.OERA.JsdoGenericService.WebHandler.CatalogsWebHandler at line 728 (c:\\work_stream\\SmartComponentLibrary\\Develop\\ABL\\Consultingwerk\\OERA\\JsdoGenericService\\WebHandler\\CatalogsWebHandler.r)\nHandleRequest OpenEdge.Web.WebHandler at line 61 (OpenEdge/Web/WebHandler.r)\nHandleRequest OpenEdge.Web.InternalWebRouter at line 113 (OpenEdge/Web/InternalWebRouter.r)", "properties": { "PackageName": "Consultingwerk.SmartComponentsDemo2.OERA.Sports2000.*", "OriginalStackTrace": null, "SessionInfo": { } } } } |
This should simplify trouble shooting.
We have added the capability of generating SmartFramework repository DataSources, Grids, Viewers and Windows to the SmartRepositorySupportPlugin (http://help.consultingwerkcloud.com/smartcomponent_library/release/Consultingwerk.Windows.Framework.Repository.Plugins.SmartRepositorySupportPlugin.html). The functionality is available as four wizards provided by the plugin.
See Support for RESTful invocation of Business Task and Business Entity Methods (https://documentation.consultingwerkcloud.com/display/SCL/Support+for+RESTful+invocation+of+Business+Task+and+Business+Entity+Methods)
See issue SCL-2148.
We have implemented a container designer control for MetaForm derived repository objects. This designer provides a read-only view of the responsive container layout.