Release Notes 2021-02-04

Version Information 

OpenEdge Release

Version Information

11.7.7, 11.7.8, 12.2, 12.3

Release 11.7 #64596@2021-02-04

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: 

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: 

  • [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-136 Resolved: QueryString - ParseQuery: A Query with brackets is parsed in the wrong way so that it is broken and can not be executed after being build (BuildQueryString)


We have resolved issues in the QueryString class used by the DataAccess class to parse the consumers query string and merge it with the Source Default Query. These issues caused problems when parsing queries with nested pairs of parentheses under certain conditions resulting in invalid query strings passed to the QUERY-PREPARE method.

SCL-3261 Order of call graph nodes now matches first appearance in source


The call graph tree view now uses the order of calls appearing in the source code to order the nodes in the tree view.

SCL-3267 Resolved error in SmartBusinessEntityAdapter:RefetchCurrentRow method


We have resolved an issue in the RefreshCurentRow method of the SmartBusinessEntityAdpater. The issue was causing a runtime error due to a typo in the source code of the method.

SCL-3278 Reoslve issue in QueryString class, causing parsing issues with query strings with an unquoted ? value


When adding QueryExpression's to a ListQueryExpression and the secondoperand has an unknown value the GetExpression method of the ListExpression returns an expression where the unknown value is not quoted.
The ParseQuery method in the QueryString class was not able to handle this resulting in the following error:

** Array subscript 0 is out of range. (26)

SCL-3291 Root Node Consultingwerk.Framework.SessionInfo data is not complete


We have resolved issues with the drilling down in the Angular version of the Session Info configuration tree view.


SCL-3091 Extended Callgraph with support for ADM1 RUN dispatch ("...").


We have extended the call graph utility with support for recognizing ADM1 style RUN dispatch ("") calls.

SCL-3239 The call graph tree view now supports Database-Triggers as calls


Database schema triggers are not reported as calls from the database statements causing triggers to execute.

SCL-3250 Call graph tree view now suppresses procedure file nodes in when hiding uncalled routines


When uncalled routines are hidden in the call graph tree the notes representing the procedure or class files of the called routine are not required and actually confusing - as this appears like an actual bit of code executed during the call into an internal procedure/method.
We are now hiding those nodes. Instead (also used when not hiding the uncalled path) we'll be adding another column to the tree representing the relative procedure name or class name (including package) containing the called routine.

SCL-3255 Now selecting complete node text when navigating to a proparse node in the linked ABL Editor


We're now selecting the full text of a node when navigating from the Proparse Tree to the Node in the Proparse treeview form. This will improve ability to spot the cursor location. Previously only the I - bar cursor was positioned before the keyword.

SCL-3263 Call graph tree now optionally treats blocks as routines


Blocks (FOR EACH, REPEAT, DO) are now optionally considered routines as well.
When refactoring larger routines, it is expected that the qualification (UI, DB, DB-Transaction) may be distinct for some blocks in the routine.

SCL-3265 SmartException now returns MessageBoxStyle and template to REST client


We have added properties for the MessageBoxStyle and MessageTemplate to the SmartException class. Those properties are also returned to REST clients when exceptions are serialized to JSON.

SCL-3266 The ServiceInterfaceMethodNotAuthorizedException now provides similar properties as the SmartException to return the message box style etc.


We have added the same properties to the ServiceInterfaceMethodNotAuthorizedException that are available in the SmartException class. This allows frontend to handle presentation of issues accordingly.

SCL-3272 Added SecondOperatorAs ... methods for all primitive DataTypes in QueryExpression


.We have added further methods like SecondOperatorAsCharacter to the QueryExpression class. Previously those methods have only been available to return Character or Integer values. Now this is supported for all ABL primitive data types.

SCL-3274 Added method to retrieve ABL error message description to ErrorHelper


We have added a new method to the ErorrHelper class that retrieves an ABL runtime error description as described in

SCL-3280 Added method to remove query expressions of a field from an IQueryExpression


We have added the method RemoveBufferFieldFromQueryExpression to the QueryExpression class. This method removes all query expressions where the first operand represents the given buffer field. The method works on QueryExpression instances and (nested) ListQueryExpression instances.

SCL-3290 FileHelper:ShortFileNameWithoutExtension now returns filename also for filename without extension


We have modified the behavior of the FileHelper:ShortFileNameWithoutExtension method to return the filename itself for filenames without an extension at all.

SCL-3295 Added DB indexes by the SmartLanguage field


To support queries used by referential integrity, we have added a non-unique, non-default Index with the SmartLanguage field to those database tables:
- SmartAttachment
- SmartMessage
- SmartTranslation
- SmartUser

New Feature

SCL-3260 Added support for VAR statement to Proparse


The ABL now supports variable definitions based on a new VAR statement. We've added support for this new statement to Proparse.

SCL-3268 Added support for class based event handlers to RUN ASYNCHRONOUS statement to Proparse


The ABL now supports class based event handlers for the RUN ASYNCHRONOUS statement. We've added support for this to Proparse.

SCL-3269 Added support for methods as call-backs for the Socket Widget Handle


The ABL now supports methods as callbacks for the socket widget handle. We've added support for the new syntax to Proparse.

SCL-3270 Added support for Compounts Assignment Operators to proparse


The ABL now supports the new compounts assignment operator (e.g. +=). We have added support for these new operators to Proparse.

SCL-3282 Implemented procedure which copies translations to specific language


We have added a procedure in the Consultingwerk\SmartFramework\Tools folder. The procedure copyUnknownTranslations.p supports coying translations from the unspecifed language to a given language. This may simplify creating translation records for a new language.

SCL-3283 Added static WriteLog method to the QueryExpression method


We have added static WriteLog methods to the QueryExpression class. Those methods support a structured logging output of a QueryExpression or (nested) ListQueryExpression using the LogManager or a provided ILogginStream reference. Those methods will simplify debugging of query manipulation routines.

SCL-3288 Resolve memory leaks caused by references to session:current-request-info


Referenceto session:current-request-info creates a new instance of the object, and when you do not assign it to a variable or reference it via a chained reference, e.g. when testing if valid-object(session:current-request-info)... an object is created that is not destroyed. The creation is not logged either, so it is extremely difficult to detect it.
Progress logged OCTA-33438 for this but there is a workaround.
We have implemented workarounds for the issue in our code.