Release Notes 2022-08-07
Version Information
OpenEdge Release | Version Information |
---|---|
11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2., 12.5.2 | Release 11.7 #71153@2022-08-07 |
Security Bulletin - log4j CVE-2021-44228
Further details: log4j CVE-2021-44228
OpenEdge 12.3 support!
We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.3. We hereby declare OpenEdge 12.3 fully supported for the SmartComponent Library as of the release of November 24th 2020.
OpenEdge 12.2 support!
We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.2. We hereby declare OpenEdge 12.2 fully supported for the SmartComponent Library as of the release of April 09th 2020.
.NET Framework Version 4.7
.NET 4.7 is not supported with OpenEdge 11.x, see: Is .NET 4.7 certified and supported for OpenEdge?
Progress has reported severy issues with OpenEdge GUI for .NET and .NET 4.7: GUI .Net Application crashes after .Net upgrade to 4.7
When using the .NET Framework 4.7, please make sure, you upgrade to OpenEdge 11.6.4 or OpenEdge 11.7.2 or later. Also, it may be required to recompile the application on a PC running .NET Framework 4.7 when applications are also executed on a PC with .NET Framework 4.7.
Introducing the SmartComponent Library developer forum
Got questions about using the SmartComponent Library? Wish to discuss feature requests with other users of the SmartComponent Library? To facilitate networking in the growing number of SmartComponent Library users and developers, we've added a developer forum on our new home-page. The developer forum can be found at: https://www.consultingwerk.com/support/forum
A login is required to participate in the forum. Don't be shy - create your account today!
Release Notes
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.
OpenEdge 11.7.3 compatibility
During our tests on OpenEdge 11.7.3 we have experienced the following issues:
- [SCL-2216] - 11.7.3 Visual Designer disabling properties of ABL user controls
The issue has been resolved by Progress Software with hotfix 007 for OpenEdge 11.7.3.
OpenEdge 11.7.2 compatibility
During our tests on OpenEdge 11.7.2 we have experienced two issues:
- [SCL-2007] - Correct support for WebHandler in CcsServiceManager
- [SCL-2008] - Closing SmartWindowForm causes crash on OpenEdge 11.7.2
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
- [SCL-1924] - SmartViewerControl: copy mechanism cannot cope with clob datatype
from Progress Software for in OpenEdge 11.7.2.001 we further recommend all customers to apply this hotfix as well.
New Versions of Proparse .NET Assemblies (30 December 2018)
We have updated proparse with further enhancements in this release (see https://github.com/consultingwerk/proparse/releases/tag/4.0.1.1177). 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 debug information when errors are thrown from proparse.net.dll.
New Version of the Consultingwerk.SmartComponents Assemly (09 January 2019)
To support the new SmartFilterControl and the "Filter" link between the SmartFilterControl/SmartDynamciFilterControl and a SmartBusinessEntityAdapter or SmartDatasetChildAdapter we have updated the Consultingwerk.SmartComponents.dll. The new Assembly reference is:
<assembly name="Consultingwerk.SmartComponents, Version=2.2.0.49856, Culture=neutral, PublicKeyToken=10603cb31df311b3"/>
Customers need to update this Assembly in order to compile the latest releases of the SmartComponent Library.
Hybrid Realm now using IAuthenticationService
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 auhtenticate 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.
Web Handler overview
This is an overview of the web handlers supported by this release
defaultHandler=OpenEdge.Web.CompatibilityHandler handler1=Consultingwerk.OERA.JsdoGenericService.WebHandler.CatalogWebHandler: /Catalog/{EntityName} handler2=Consultingwerk.OERA.JsdoGenericService.WebHandler.CatalogsWebHandler: /Catalogs/{PackageName} handler3=Consultingwerk.OERA.JsdoGenericService.WebHandler.CountWebHandler: /Resource/{EntityName}/count handler4=Consultingwerk.OERA.JsdoGenericService.WebHandler.ResourceSubmitWebHandler: /Resource/{EntityName}/SubmitData handler5=Consultingwerk.OERA.JsdoGenericService.WebHandler.InvokeMethodWebHandler: /Resource/{EntityName}/{MethodName} handler6=Consultingwerk.OERA.JsdoGenericService.WebHandler.ResourceWebHandler: /Resource/{EntityName} handler7=Consultingwerk.OERA.JsdoGenericService.WebHandler.BusinessServicesWebHandler: /BusinessServices/{OutputFormat}/{PackageName} handler8=Consultingwerk.Web2.WebHandler.SmartMenuWebHandler: /SmartMenu/{MenuStructureId} handler9=Consultingwerk.Web2.WebHandler.SmartMenuStructureWebHandler: /SmartMenuStructure handler10=Consultingwerk.Web2.WebHandler.SmartRoutesWebHandler: /SmartRoutes handler11=Consultingwerk.Web2.Services.SmartViewsHandler.SmartGridWebHandler: /SmartViews/Grid/{EntityName}/{ViewName}/{DetailTemplate} handler12=Consultingwerk.Web2.Services.SmartViewsHandler.SmartGridWebHandler: /SmartViews/Grid/{EntityName}/{ViewName} handler13=Consultingwerk.Web2.Services.SmartViewsHandler.SmartGridWebHandler: /SmartViews/Grid/{CustomViewName} handler14=Consultingwerk.Web2.Services.SmartViewsHandler.SmartViewerWebHandler: /SmartViewer/Viewer/{EntityName}/{ViewName} handler15=Consultingwerk.Web2.Services.SmartViewsHandler.SmartViewerWebHandler: /SmartViewer/Viewer/{ObjectName} handler16=Consultingwerk.Web2.Services.SmartViewsHandler.SmartFormWebHandler: /SmartForm/{FormTemplate}/{EntityName}/{ViewName} handler17=Consultingwerk.Web2.Services.SmartViewsHandler.SmartFormWebHandler: /SmartForm/{FormTemplate}/{ObjectName} handler18=Consultingwerk.Web2.WebHandler.SmartMessageWebHandler: /SmartMessage/{MessageGroup}/{MessageNumber} handler19=Consultingwerk.Web2.WebHandler.GetImageWebHandler: /Image/{FileName} handler20=Consultingwerk.Web2.WebHandler.SmartValueListWebHandler: /ValueList/{ValueList} handler21=Consultingwerk.Web2.WebHandler.SmartAttachmentsWebHandler: /Attachments/{Table}/{KeyValues} handler22=Consultingwerk.Web2.WebHandler.SmartAttachmentWebHandler: /Attachment/{Guid} handler23=Consultingwerk.Web2.WebHandler.SessionContextWebHandler: /SessionContext handler24=Consultingwerk.Web2.WebHandler.ContextPropertiesWebHandler: /ContextProperties/{PropertyName} handler25=Consultingwerk.Web2.WebHandler.ContextPropertiesWebHandler: /ContextProperties handler26=Consultingwerk.Web2.WebHandler.SessionInfoWebHandler: /SessionInfo handler27=Consultingwerk.Web2.WebHandler.FileSearchWebHandler: /FileSearch/{FileName} handler28=Consultingwerk.Web2.WebHandler.ExecuteAblWebHandler: /ExecuteAbl handler29=Consultingwerk.Web2.WebHandler.SmartLanguagesWebHandler: /Languages handler30=Consultingwerk.OERA.RestResource.RestEntitiesWebHandler: /Entities handler31=Consultingwerk.OERA.Swagger.SwaggerWebHandler: /Swagger/{EntityName} handler32=Consultingwerk.OERA.Swagger.SwaggerRestEntitiesWebHandler: /SwaggerEntities/{OutputType} handler33=Consultingwerk.Web2.WebHandler.SmartTokenSecurityCheckWebHandler: /TokenSecurityCheck/{ObjectName} handler34=Consultingwerk.Web2.WebHandler.SmartTokenSecurityCheckWebHandler: /TokenSecurityCheck handler35=Consultingwerk.Web2.WebHandler.SmartEntityTableMappingHandler: /EntityTableMapping/{EntityName}/{TableName}/{UiTypeCodes} handler36=Consultingwerk.Web2.WebHandler.SmartTreeRootNodeWebHandler: /SmartViews/TreeRootNode/{rootnodeid} handler37=Consultingwerk.Web2.WebHandler.SmartTreeChildNodesWebHandler: /SmartViews/TreeChildNodes/{parentnodeid} handler38=Consultingwerk.Web2.WebHandler.SmartSecurityCheckWebHandler: /IsRestricted/{SecurityRealmCode}/{SecurityItemGuid} handler39=Consultingwerk.Web2.WebHandler.SmartFieldSecurityCheckWebHandler: /RestrictedFields/{TableName} handler40=Consultingwerk.Web2.WebHandler.GetImageNamesHandler: /ImageNames |
UTF-8 based deployments available
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
New Feature Documentation
- Support for RESTful invocation of Business Task and Business Entity Methods
- Invalid Proparse code-page setting corrupts temp-table field labels during "Refresh from Include"
- Generic Factory Service
- Using Invokable Business Entity Methods with Dataset Model Classes
- Using the Business Entity method FetchDataByKeyTable
- PASOE management scripts
- Business Entity Designer Launcher
- Searching data using ROWID's within the SmartBusinessEntityAdapter
- Business Entity Count Method
- SmartFramework ERD Designer
- Changes to the SmartDB and SmartDB upgrade and migration utility
- How to implement dynamic initial values
- How do I control the amount of details provided for error messages caused by our web handler
- Using custom log entry types
- Strong-typed Query Support
- Swagger REST API Documentation for RESTful Services
- Swagger REST API Documention for JSDO Generic Service
- Scaffolding utility for common helper classes
- RESTful services
- JSON Configuration File Format
- Common Component Specification (CCS)
Download Link
http://esd.consultingwerkcloud.com/
https://github.com/consultingwerk/SmartComponentLibrary
Overview of included tickets
Bug
SCL-3725 RestAddress and RestMethod class now registers serializable properties
Description:
Previously the RestAddress and RestMethods have not been registering their properties with the JsonSerializable base class. This has now been implemented in preparation for https://consultingwerk.atlassian.net/browse/SCL-3711
SCL-3727 JsonSerializable's DeserializeProperty() method now ensures validity of enumerable objects
Description:
We have extended the deserialization of list properties in the JsonSerializable class to ensure that there’s always a valid list instance. Before this change the deserialization was relying on the constructor of the serializable object to create a new list instance.
Now we’re dynamically NEW’ing the list instance unless the list property of the holding serializable object is defined based on an interface type of abstract class.
When the constructor of a serializable object already NEW’s the list instance (previous requirement), the DeserializeProperty method does not create a new list intance.
SCL-3728 DatasetModel's Filter with "In" condition failed to execute
Description:
We have fixed an issue in the DataAccess classes query parsing that was causing the “In” Filter condition of the DatasetModel’s filter to fail.
The error message that was caused was:
** Unable to understand after -- ", USA,DE )>0". (247) PREPARE syntax is: {FOR | PRESELECT} EACH OF.. WHERE ... etc". (7324)
Improvement
SCL-3711 Improve RestResourceService startup time through a persistent cache
Description:
The startup of the RestResourceService https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8094254/Support+for+RESTful+invocation+of+Business+Task+and+Business+Entity+Methods significantly slows down the startup of every PASOE session. In our setup we have observed startup times for the service of 4 to 5 seconds. This is caused by the need to call into every Business Entity and Business Task to obtain the exposed REST endpoints during startup.
By the implementation of a cache this delay could almost completely be avoided.
The persistent cache is implemented in the form of a JSON file. The name of the JSON file is referenced by the property RestResourcesCacheFile in the .applicationsettings / .restapplicationsettings file. Relative path names are referenced relatively to the AppServer working directory.
Reading and writing of the cache are implemented by two services that have been added to the Consultingwerk/OERA/RestResource/services.xml
<ttServiceLoaderRow> <Order>10</Order> <ServiceTypeName>Consultingwerk.OERA.RestResource.IRestResourcesReader</ServiceTypeName> <ServiceClassName>Consultingwerk.OERA.RestResource.RestResourcesJsonReader</ServiceClassName> </ttServiceLoaderRow> <ttServiceLoaderRow> <Order>20</Order> <ServiceTypeName>Consultingwerk.OERA.RestResource.IRestResourcesWriter</ServiceTypeName> <ServiceClassName>Consultingwerk.OERA.RestResource.RestResourcesJsonWriter</ServiceClassName> </ttServiceLoaderRow>
When the cache file is specified the REST endpoints (addresses and methods) are only obtained from the cache file and not from the business services themselves andmore.
When the cache file is specified and the IRestResourceWriter service is loaded, the AppServer will dump the cache file after the initialization of the RestResourceService. Developers that add REST endpoints simply have to delete the existing cache file before restarting the PASOE agents or sessions to update the cache file.
The procedure Consultingwerk/OERA/RestResource/generate-rest-resources-json.p can be invoked by PCT from a build pipeline to programmatically generate the cache of REST endpoints. The procedure expects to parameters to be passed via PCTRun:
* RestResourcesOutputFile the name of the cache file to generate
* StartupConfigFile the name of the JSON configuration file of the AppServer session, required to initialize the RestResourceService and it’s dependencies
SCL-3717 Added support for "Unbound" attribute to GUI for .NET Rendering classes
Description:
We have added a new Attribute Unbound to the MetaDataField class in the SmartFramework Repository. Based on this attribute, fields in a MetaViewer will not add data binding to fields from the binding source.
SCL-3718 Added InitializingChanged event to SmartViewerControl
Description:
To support custom behavior based on the Initializing state of the SmartViewerControl instance we’ve added an InitializingChanged event that is raised whenever the Initializing property changes it’s value.
SCL-3721 JSON rendering support for SmartForm form title
Description:
We have implemented Angular JSON rendering support for the TITLE property of a Form. Previously the Angular Frontend was using the menu item’s title as the title for rendered forms.
This feature is the foundation of https://consultingwerk.atlassian.net/browse/SCLNG-526
SCL-3723 Fixed typo in WinKit Designer Service Popup
Description:
We have fixed a type in the text of the “Winkit Designer” service popup message that was shown when an application with the enabled WinKit designer has been started.
SCL-3731 Providing Consultingwerk.UltraControls Assembly for 16.2.20162.2182
Description:
We have built an additional version of the Consultingwerk.UltraControls Assembly with dependencies on the OpenEdge UltraControls (Infragistics) Version16.2.20162.2182
New Feature
SCL-3491 New utility to generate assemblies.xml
Description:
To simplify the generation of an assemblies.xml file for a SmartComponent Library based development workspace or deployment we have added a new tool to the SmartDB setup and migration routine https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8093744/SmartDB+Upgrade+and+Migration+Routine
The utility will generate an assemblies.xml based on a configuration file typically called assemblies-generator.json. For your convenience we are shipping a version of this file that should work for most customers in the assemblies.zip file available on the ESD:
[ { "fromFolder": { "folderName": "Assemblies", "includeProbingPath": true, "excludeSubfolders": [ "Infragistics" ], "excludeAssemblies": [ "Consultingwerk.RadControlSupport.*", "Consultingwerk.UltraControls.*", "CefSharp.BrowserSubprocess.Core", "CefSharp.Core.Runtime", "Microsoft.AnalysisServices.AdomdClient", "Newtonsoft.Json", "RadControlSpy", "TelerikProviderForGoogleAnalytics", "Telerik.WinControls.Themes.*", "VisualStyleBuilder.Design" ] } }, { "infragistics": { "from": "${DLC}/bin/infragistics/winforms", "include": [ "Infragistics4.Documents.Core.*", "Infragistics4.Documents.Excel.*", "Infragistics4.Documents.IO.*", "Infragistics4.Documents.Reports.*", "Infragistics4.Documents.TextDocument.CSharp.*", "Infragistics4.Documents.TextDocument.TSql.*", "Infragistics4.Documents.TextDocument.*", "Infragistics4.Documents.TextDocument.VisualBasic.*", "Infragistics4.Documents.Word.*", "Infragistics4.Math.*", "Infragistics4.Shared.*", "Infragistics4.Undo.*", "Infragistics4.Win.AppStylistSupport.*", "Infragistics4.Win.Misc.*", "Infragistics4.Win.Portable.Core.*", "Infragistics4.Win.SupportDialogs.*", "Infragistics4.Win.UltraWinCalcManager.*", "Infragistics4.Win.UltraWinCalcManager.*.FormulaBuilder", "Infragistics4.Win.UltraWinChart.*", "Infragistics4.Win.UltraWinDataSource.*", "Infragistics4.Win.UltraWinDock.*", "Infragistics4.Win.UltraWinEditors.*", "Infragistics4.Win.UltraWinExplorerBar.*", "Infragistics4.Win.UltraWinFormattedText.WordWriter.*", "Infragistics4.Win.UltraWinGanttView.*", "Infragistics4.Win.UltraWinGauge.*", "Infragistics4.Win.UltraWinGrid.DocumentExport.*", "Infragistics4.Win.UltraWinGrid.ExcelExport.*", "Infragistics4.Win.UltraWinGrid.*", "Infragistics4.Win.UltraWinGrid.WordWriter.*", "Infragistics4.Win.UltraWinInkProvider.Ink17.*", "Infragistics4.Win.UltraWinListBar.*", "Infragistics4.Win.UltraWinListView.*", "Infragistics4.Win.UltraWinLiveTileView.*", "Infragistics4.Win.UltraWinMaskedEdit.*", "Infragistics4.Win.UltraWinOfficeNavBar.*", "Infragistics4.Win.UltraWinPivotGrid.*", "Infragistics4.Win.UltraWinPrintPreviewDialog.*", "Infragistics4.Win.UltraWinRadialMenu.*", "Infragistics4.Win.UltraWinSchedule.*", "Infragistics4.Win.UltraWinSpellChecker.*", "Infragistics4.Win.UltraWinSpreadsheet.ChartAdapter.*", "Infragistics4.Win.UltraWinSpreadsheet.*", "Infragistics4.Win.UltraWinStatusBar.*", "Infragistics4.Win.UltraWinTabbedMdi.*", "Infragistics4.Win.UltraWinTabControl.*", "Infragistics4.Win.UltraWinToolbars.*", "Infragistics4.Win.UltraWinTree.*", "Infragistics4.Win.*" ] } }, { "radControlSupport": { "versionFrom": "Assemblies/Telerik", "assemblyFrom": "Assemblies/Consultingwerk" } }, { "ultraControlsSupport": { "versionFrom": "${DLC}/bin/infragistics/winforms", "assemblyFrom": "Assemblies/Consultingwerk" } }, { "includeAssemblies": { "list": [ "Accessibility, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "Microsoft.Office.Interop.Excel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c", "Microsoft.VisualBasic, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089", "System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089", "System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089", "System.Deployment, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.Runtime.Serialization.Formatters.Soap, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.Security, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089", "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" ] } } ]
The configuration file contains multiple sections:
fromFolder
This section defines that all assemblies from the given folder will be added to the assemblies.xml file. The folderName is relative to the installroot argument passed to the utility. When the includeProbindPath attribute is set to TRUE also the folders referenced in the probing privatePath section of the assemblies.config file are included. The folders and assemblies referenced by the excludeSubfiolders and excludeAssemblies attributes are excluded.
infragistics
Adds Infragistics Control to assemblies XML. The source folder is specified by the from attribute and typically points to a given OpenEdge installation referenced by the DLC variable.
radControlSupport
Adds the Consultingwerk.RadControlSupport assembly to the assemblies.xml file. The version added to the assemblies.xml file will be matching the Telerik RadControl assemblies found in the folder referenced by the versionFrom attribute.
ultraControlsSupport
Adds the Consultingwerk.UltraControls assembly to the assemblies.xml file. The version added to the assemblies.xml file will be matching the Infragistics assemblies found in the folder referenced by the versionFrom attribute (typically from the OpenEdge installation).
includeAssemblies
This attribute references a list of assemblies that should be added to assemblies.xml - typically from the global assemblies cache (GAC).
The utility is launched from the setup.xml in the Setup folder of the SmartComponent Library installation like this:
ant createAssemblies -f setup.xml -Ddlc=%dlc% -Dinstallroot=.. -DconfigFile=Assemblies\assemblies-generator.json -DoutputFile=Assemblies\assemblies.xml
The arguments -DconfigFile and -DoutputFile are relatively to the installroot (not the Setup folder).