Release Notes 2025-01-20
- 1 Version Information
- 2 Security Bulletin - log4j CVE-2021-44228
- 3 OpenEdge 12.8 support!
- 4 OpenEdge 12.2 support!
- 5 Introducing the SmartComponent Library developer forum
- 6 Release Notes
- 7 New Versions of Proparse .NET Assemblies (30 December 2018)
- 8 New Version of the Consultingwerk.SmartComponents Assemly (09 January 2019)
- 9 Hybrid Realm now using IAuthenticationService
- 10 Web Handler overview
- 11 UTF-8 based deployments available
- 12 New Feature Documentation
- 13 Download Link
- 14 Overview of included tickets
- 14.1 Bug
- 14.2 Improvement
- 14.2.1 SCL-3433 Implemented Business Entity Generator based on new Proparse API
- 14.2.2 SCL-4677 Improved regenerate prompts in Business Entity Designer
- 14.2.3 SCL-4696 Improved display of LRU entries in .NET Telemetry Data Viewer
- 14.2.4 SCL-4697 Windows Installer for Telemetry Viewer
- 14.2.5 SCL-4698 Command line converter for Telemetry NDJSON files -> Excel
- 14.2.6 SCL-4699 Added Time Filters to Telemetry Viewer
- 14.2.7 SCL-4701 Changed .Net target framework to 4.8 for Telemetry Toolkit
- 14.2.8 SCL-4706 Added GetBufferHandle method to BufferDataSource
- 14.2.9 SCL-4707 Menu Function Maintenance - Implemented a validation that FunctionName is mandatory
- 14.2.10 SCL-4708 User Maintenance- Implemented a validation that at least the user name is filled in
- 14.2.11 SCL-4709 Product Maintenance - Implemented validation, if Code field is empty.
- 14.2.12 SCL-4710 Security Realm Maintenance - Implemented validation if Realm code is empty
- 14.3 New Feature
- 14.4 Story
- 14.5 Task
Version Information
OpenEdge Release | Version Information |
---|---|
11.7.21, 12.2.13, 12.8.3, 12.8.4 | Release 11.7 #83673@2025-01-20 |
Security Bulletin - log4j CVE-2021-44228
Further details: log4j CVE-2021-44228
OpenEdge 12.8 support!
We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.8. We hereby declare OpenEdge 12.8 fully supported for the SmartComponent Library as of the release of January 15th 2024.
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.
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.
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"
Using Invokable Business Entity Methods with Dataset Model Classes
Searching data using ROWID's within the SmartBusinessEntityAdapter
Changes to the SmartDB and SmartDB upgrade and migration utility
How do I control the amount of details provided for error messages caused by our web handler
Download Link
http://esd.consultingwerkcloud.com/
https://github.com/consultingwerk/SmartComponentLibrary
Overview of included tickets
Bug
SCL-4695 Fixed Telemetry Reporting for Repository Requests from the Angular web app
Description:
We have fixed the repository reporting for requests to repository data from the Angular frontend. Those requests had been reported as requests into the FieldSecurityItemBusinessEntity. We are now reporting those as a requests into the Repository Service and are reporting the form name as the query of the request.
SCL-4700 Fixed error when using web version of SmartFramework Administration tool
Description:
Customer has reported issue with the Angular web version of the SmartFramework tools. This was caused by the BusinessEntityDescriptorClient service trying to use the Service Adapter to connect to backend. This is now resolved, the component does not need to make an AppServer call, was we’re already on the AppServer backend.
SCL-4703 Fixed unhandled exception in GUI designer
Description:
We have resolved an unhandled exception in the Repository GUI Designer. The exception might have occurred when clicking into the instances grid.
Improvement
SCL-3433 Implemented Business Entity Generator based on new Proparse API
Description:
We have implemented the Business Entity Generator based on the Proparse API service. This will allow us to abstract the Business Entity Generator from the Proparse implementation in the future.
SCL-4677 Improved regenerate prompts in Business Entity Designer
Description:
The Business Entity Designer now shows a single prompt to regenerate Business Entity or Data Access class. This new dialog provides check boxes for the two types of components.
The dialog can also be used by plugin developers as the Business Entity Generator raises an even to obtain the prompts (check boxes) to be included in that dialog.
SCL-4696 Improved display of LRU entries in .NET Telemetry Data Viewer
Description:
We have improved the display of the LRU entries in the .NET Telemetry Data Viewer. We’re now truncating the folder names from the left.
SCL-4697 Windows Installer for Telemetry Viewer
Description:
We do now provide a Windows Installer for the .NET Telemetry Viewer. The installer can be downloaded from the Consultingwerk ESD. Customers may need to request access to the product on the ESD through a support call.
SCL-4698 Command line converter for Telemetry NDJSON files -> Excel
Description:
We have implemented a command line converter the supports converting all telemetry data in a folder to
* Excel
* JSON
* JSON formatted
The utility supports the following command line switches:
TelemetryConverter.exe -format excel {-outputfile filename} [-inputfolder folder]
The tool is bundled with the .NET Telemetry Viewer. The converter is currently provided for Windows, in the future we may be porting this to Linux based on .NET Core.
SCL-4699 Added Time Filters to Telemetry Viewer
Description:
We have added a Ribbon Group to the .NET Telemetry Viewer that supports filtering the telemetry data shown by date range, supporting filtering by the last minute, 15 minutes, hour, day, week, month or year. The main purpose of this filter is to speed up loading time for large telemetry data sets.
SCL-4701 Changed .Net target framework to 4.8 for Telemetry Toolkit
Description:
To support Windows 2016 servers, we have changed the .NET framework version required by the Telemetry Toolkit Viewer to 4.8 (instead of 4.8.1).
SCL-4706 Added GetBufferHandle method to BufferDataSource
Description:
We have added a method GetBufferHandle to the BufferDataSource class. This method returns a buffer handle either based on the Buffer sequence or name.
SCL-4707 Menu Function Maintenance - Implemented a validation that FunctionName is mandatory
Description:
The menu business entity now performs validation that the function name of a menu function is not empty.
SCL-4708 User Maintenance- Implemented a validation that at least the user name is filled in
Description:
The user business entity now performs validation that the user name is not empty.
SCL-4709 Product Maintenance - Implemented validation, if Code field is empty.
Description:
The product business entity now performs validation that the product code field is not empty.
SCL-4710 Security Realm Maintenance - Implemented validation if Realm code is empty
Description:
We have implemented validation that at least the realm code is entered for a security realm record.
New Feature
SCL-4525 Implemented Security Assignment Integrity Check
Description:
Similar to the Repository Integrity Check we have implemented a feature that verifies the cross references from the SmartSecurityAssignment table
* user
* group
* security realm
* security item
Story
SCL-4704 MessageFormatter now uses INT64 for message numbers
Description:
As some customers are using Enums to reference messages, we have now modified the MessageFormatter API’s to use INT64 parameters instead of INTEGER.
Task
SCL-4702 Enable more codepages to be used as ProparseCodepage
Description:
We have extended the Consultingwerk.Codepages class to support more classes. The method IsKnownCodepage is now based on the ABL GET-CODEPAGES method to support all valid code pages supported by the OpenEdge runtime.
To support a wide set of Java code pages for Proparse, we have now added a new method IsKnownJavaCodepage that is based on the code pages referenced at https://docs.oracle.com/en/java/javase/17/intl/supported-encodings.html