Release Notes 2023-06-05

Version Information

OpenEdge Release

Version Information

11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2, 12.6, 12.7 CQC

Release 11.7 #76354@2023-06-05

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

OpenEdge 12.7 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.7. We hereby declare OpenEdge 12.7 fully supported for the SmartComponent Library as of the release of  May 10th 2023.

OpenEdge 12.6 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.6. We hereby declare OpenEdge 12.6 fully supported for the SmartComponent Library as of the release of  October 4th 2022.

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: 

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 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 Please download the .NET Assemblies ZIP file from our ESD and replace the in your environment with the latest one. The new assembly reference is:

<assembly name=", Version=, Culture=neutral, PublicKeyToken=cda1b098b1034b24"/>

As proparse is used by our Business Entity Generator, this new version of the 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

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=, 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

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
handler41=Consultingwerk.Web2.WebHandler.ExecuteQueryWebHandler: /ExecuteQuery
handler42=Consultingwerk.Web2.WebHandler.TranslationProviderWebHandler: /GetTranslation

UTF-8 based deployments available

Starting August 14th 2016 we ship our source code also as UTF-8 encoded. The ZIP files ending with 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

Download Link

Overview of included tickets


SCL-4065 Data Dictionary Dump hack now optionally supports using concatenated PUK values for LOB file name


The Data Dictionary Dump hack primarily intended for Consultingwerk’s internal use now supports dumping LOB’s to files with names based on primary unique key values of the owning record - instead of the ROWID. The purpose of this improvement is to ensure persisting LOB file dump names in even more scenarios. The default behavior of Progress' dump routine is to use a new file name each time a developer dumps a table. This makes tracking of changes in LOB fields (especially in CLOB fields) practically impossible.

We still support using the ROWID of the record to build the LOB fieidl dump file names. This ensures the same LOB dump file name when dumped from the same instance of the database.

Now we support building the LOB field dump file name based on the unique key fields values of the record (e.g. GUID’s). When the unique key consists of multiple field names, we use the ! (exclamation mark) as a delimiter. We know that there will be cases where this may the causing collisions between records. Developers that use fields that may contain the exclamation mark or characters not supported in file names should not use the new variant.

The new behavior is enabled using a switch in products.i:

&IF 1=0 &THEN
/* Peter Judge / Consultingwerk Ltd.
   SCL-4065 : Support dumping LOB values to files using primary unique keys
&GLOBAL-DEFINE LOBExportFileNameUsingUniqueKey LOBExportFileNameUsingUniqueKey

SCL-4071 Added support for DECIMAL key field values in the Security Assignment


We now support the use custom security realm implementations with non character key fields. Previously te Authorization report was always assuming a CHARACTER key field value.

SCL-4092 Property DetailFormDataSources of SmartDataBrowser now supports mapping


The DetailFormDataSources property of the SmartDataBrowser now supports mapping of instance names. This lifts the requirement that shared object instances (typically SmartBusinessEntityAdapter) need to have the same name in the parent and detail form. The mapping is optionally specified in the form:

<detail instance1=parent_instance1>,<detail instance2=parent_instance2>

We also support a mix of mapped and unmapped instance names:

<detail instance1=parent_instance1>,<instance2>

SCL-4118 Updated CefSharp to v113.1.40


We have updated the CefSharp component included in the SmartComponent Library. See for details.

SCL-4121 Implemented ability to export/import objects from repository object master form


The Repository Object Master Form now allows the developer to export and import .smartrepo files directly form the tool. For this purpose we have added two menu items to the File menu of the Form’s Ribbon control.

SCL-4122 Supporting more Lookup Properties in ABL Legacy GUI Frame migration


We are now supporting additional properties of the SmartBusinessEntityLookup when migrating lookups into the SmartFramework repository:

* LookupKeyField
* LookupKeyValueColumn
* LookupKeyValueBinding
* FetchDataFromKeyValueOnNavigate
* FetchDataOnNavigate
* ForeignFields
* LookupDialogQueryString
* LookupQueryString
* Unbound

SCL-4123 Resolved Legacy GUI Migration not assigning images/combo-box in Rectangle to GroupBox


The Legacy GUI Frame migration tool did not properly migrate images or combo-box widgets inside a Rectangle widget into controls inside a GroupBox container. This has been resolved now.

SCL-4124 MapEnterToTab should no longer applies Tab, when modifier keys are used


The MapEnterToTab feature of the SmartWindowForm no longer reacts when the Enter key is pressed together with the modifier keys Alt, Control or Shift.

SCL-4125 TabOrder Message Filter now handles Tab out of Radio-Buttons


The TabOrder Manager (TabOrderMessageFilter .NET Class) has been enhanced so that if also handles Tab events from radio-buttons properly. ABL RADIO-SET widgets are realized as a frame containing multiple radio-button controls in the Windows API. This is now respected by the TabOrderMessageFilter.

SCL-4126 TabOrderManager now detects and skip disabled controls


The TabOrder Manager (TabOrderMessageFilter .NET Class) has been enhanced so that it now skips disabled or hidden controls/widgets when applying the tab order. The TabOrder manager now applies focus to the new enabled and visible control/widget that is registered in the TabOrder manager.

SCL-4127 New RestEntitiesWebHandler FilterString(poURI, phBuffer) method replaces FilterString(pcQueryString, phBuffer) method


A new protected FilterString(poURI, phBuffer) method has been added to the Consultingwerk.OERA.RestResource.RestEntitiesWebHandler class. This method takes the URI object that was used to make the request, and a buffer handle. It replaces the FilterString(pcQueryString, phBuffer) method since that method assumes that the & character is a name-value pair delimiter in the query string; this assumption fails when there are & characters in the query value.

The FilterString(pcQueryString, phBuffer) method has been removed from the Consultingwerk.OERA.RestResource.RestEntitiesWebHandler class.

SCL-4128 When copying a SmartUser, SmartUserGroup assignments will be copied as well


When copying a SmartUser we are not copying the user group assignment (SmartUserGroup records) as well.

SCL-4129 Data Source Query of SmartObjectInstance now outer-joins SmartObjectMaster


We have modified the Data Access class of the ObjectMasterBusinessEntity. The Data Source query for the eSmartObjectInstance table now uses the outer-join between the SmartObjectInstance and SmartObjectMaster tables. This allows to retrieve broken object instance records (when there is no object master) through the Business Entity as well.

Edit 16.07.2023:

This change will help developers detecting repository integrity issues early during development. Before this change containers with orphaned object instances records (referenced object master not valid, not existing) were silently rendered. Now the repository service will raised an error indicating that the instance master cannot be found. 

Developers should use the Repository Integrity Check utility to cleanup the invalid SmartObjectInstance records from the repository. 


SCL-4100 Adapt MetaBusinessEntityForm to Work in Desktop and Web application


We have adapted the MetaBusinessEntityForm repository layout to work equally in Web and Desktop rendering.