Version Information

OpenEdge Release

Version Information

11.7.4, 11.7.5, 11.7.6, 12.1, 12.2

Release 11.7 #61703@2020-09-22

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.

OpenEdge 12.1 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.1. We hereby declare OpenEdge 12.1 fully supported for the SmartComponent Library as of the release of September 21st 2019.

OpenEdge 11.7.6 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 11.7.6. We hereby declare OpenEdge 11.7.6 fully supported for the SmartComponent Library as of the release of June 9th 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!

Announcing the SmartFramework ERD Designer

We are announcing the availability of the SmartFramework ERD Designer

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: 

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: 

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 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-3137 Resolved issue in ErrorHelper:AddJsonErrorDetails()


We have resolved an issue in the ErrorHelper:AddJsonErrorDetails() which caused in some cases to fail to add the first message to the array.

SCL-3144 Workaround for AllowDrop property error message from UltraDockManager when starting the Business Entity Designer


We have implemented a workaround caused by the Infragistics Controls (OpenEdge UltraControls) shipped with OpenEdge 12.3 CQC.
When starting the Business Entity Designer in OpenEdge 12.3, the following error message is shown:
UltraDockManager - DragDrop disabled
The 'AllowDrop' property is set to true but the ApartmentState of the current thread does not support drag drop. To disable drag drop functionality set the 'AllowDrop' property to false. To enable drag drop functionality you must set the ApartmentState of the thread to STAThread. This can also be accomplished by putting the [STAThread] attribute on your 'Main' method.

We have implemented a workaround that might be required for Forms using the UltraDockManager in customer's screens too. In the Form's constructor, after the call to the InitializeComponent method, please call the SuspendSTAThreadWarning () method of the BaseForm like shown here.

    CONSTRUCTOR PUBLIC BusinessEntityDesignerForm ():

        DEFINE VARIABLE oStatusManager AS IStatusManager NO-UNDO .
        DEFINE VARIABLE oTool AS ToolBase NO-UNDO .



        /* Mike Fechner, Consultingwerk Ltd. 15.09.2020
           SCL-3144: Suspends STAThread warnings for an UltraDockManager instance
                     Workaround for an Issue with the Infragistics UltraDockManager of OpenEdge 12.3 CQC
                     19.2.20192.381 */
        &IF DEFINED (UltraDockManagerSTAThreadWarningWorkaround) NE 0 &THEN
        THIS-OBJECT:SuspendSTAThreadWarning(ultraDockManager1) .

The preprocessor variable UltraDockManagerSTAThreadWarningWorkaround is defined in products.i.

SCL-3145 Setup.xml not able to find \DataFields\ePossibleAssignments.GroupGuid.smartrepo


The SmartDB upgrade and migration utility had an issue locating the .smartrepo files of the standard repository objects. The issue was only seen when the utility was executed from source code and was caused by an issue in the TTY variant of the FileHelper:GetFiles() method.
The issue is fixed now.

SCL-3146 JSON Generic Service did cause empty WHERE phrase for empty filter when sort was used


We have resolved an issue that has caused an invalid query string generated by the JSDO generic service when the browser issued a request with a SortBy criteria but no selection.
This issue is resolved now.

SCL-3147 GenericDataImporter failed to load SmartGroups with multiple parent groups


When the multiple user group inheritance was enabled, the GenericDataImporter might have failed to load SmartGroup records from XML files.
This issue is resolved now.

SCL-3148 Fixed issue with resolving class names for RESTful resources when r-code is located in a PL file


We have fixed an issue that might have prevented RESTful resources from being registered when the AppServer starts. I should now be fully possible to keep Business Entities providing RESTful resources in a procedure library file. Note, that the .annotations files still must reside outside of the procedure library, as OpenEdge does not support reading JSON files from inside a procedure library.

SCL-3149 SessionInfoWebHandler replaced slash with backslash in PROPATH on Linux


The SessionInfoWebHandle was using the backslash instead of the forward slash when displaying the PROPATH on Linux. While this did not cause any other issue it was confusing.


SCL-3108 Implement DatasetAssert methods for questions


We have implemented new methods in the DatasetAssert class that provide assertions for Questions similar to those that had already been existing for messages.

SCL-3122 ProparseDotNetVariable:Value of new ProparseApi should be of type Object


We have changed the type of the Value property of the IVariable (ProparseDotNetVariable implementation) from CHARACTER to Progress.Lang.Object and implemented the RunHandle type. Depending on the type returned by Proparse the property now returns either a CharacterHolder or a RunHandle instance.

SCL-3132 Improved parsing of calculated field expressions in the SDO Importer Plugin


We have improved the parsing of calculated field expressions in the SDO importer plugin, especially improving error messages and handling of "" caused by string literals in the calculated field expression.

New Feature

SCL-3125 Created a tool to build a list of class members


The class Consultingwerk.Studio.Refactor.ClassMember.ClassMemberParser has been implemented and provides the method ParseClass. This method returns a temp-table with the class members for the given ABL class.

SCL-3134 New API in DatabaseHelper: Tell if selected DB is Enterprise or Workgroup


We have implemented a new method in the DatabaseHelper based on option 2 described in the knowledge base article at

SCL-3138 SmartViewer Migration of ADM2 SmartDataFields


The SmartFrame migration utility now supports migration of custom ADM2 SmartDataFields into .NET custom control instances.

SCL-3139 Added support for generating Image controls from ABL IMAGE Widgets


The legacy GUI frame migration utility now supports generating Image controls from ABL Image widgets.


SCL-3143 Added OpenEdge 12.3 to ProVersion Enum, Business Entity Designer config and CLI tools


We have prepared the ProVersion Enum, the Business Entity Designer config and the various CLI tools for the release of OpenEdge 12.3