Release Notes 2018-09-30

Version Information

OpenEdge Release

Version Information

11.3.3, 11.3.4, 11.4, 11.6.2, 11.6.3, 11.7, 11.7.1, 11.7.2,

Release 11.3 #48524@2018-09-30

OpenEdge 11.7.3 support!

The previously reported issues with the Progress Developer Studio Visual Designer (Visual Designer related OpenEdge 11.7.3 product alert!!!) has been resolved by Progress Software with Hotfix 007 of OpenEdge 11.7.3. We hereby announce full compatibility of the SmartComponent Library with OpenEdge 

Besides the issue with the Visual Designer however, we habe not been aware of any incompatibilities with OpenEdge 11.7.3. 

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 (08 April 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 methods for refactoring purposes. The most recent code in the Consultingwerk.Studio package relies on those methods. It's therefore mandatory to update proparse to this version.

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}

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-2316 Visual Designer Errors after upgrading to OpenEdge


One customer has reported issues with the Visual Designer after upgrading to OpenEdge We've been able to reproduce those errors in one virtualized environment (Amazon EC2), but not when working locally on our PC.

The issue seen were 15580 runtime errors (.NET is attempting to call a method in an ABL object that inherits from .NET. The object is either a form that has already been disposed or another object that has been explicitly deleted from the ABL.).

It's suspected that those issues were caused by the timing when the Visual Designer was reloading the design canvas.

Progress Software has confirmed a bug in OpenEdge which is expected to be fixed with OpenEdge 11.7.4

SCL-2388 Fixed an issue fetching data from the ObjectMasterBusinessEntity


We've resolved an issue caused by previous optimization in the ObjectMasterDataAccess class. Errors seen where

"eSmartObjectMaster objectname must be a quoted constant or an unabbreviated, unambiguous buffer/field reference for buffers known to query . (7328)"

"Unable to prepare query: FOR EACH SmartObjectMaster WHERE (eSmartObjectMaster.objectname Begins "main") , FIRST SmartObjectType WHERE SmartObjectType.ObjectTypeGuid = SmartObjectMaster.ObjectTypeGuid,FIRST SmartCustomizationResult WHERE SmartCustomizationResult.CustomizationResultGuid = SmartObjectMaster.CustomizationResultGuid OUTER-JOIN,FIRST SmartModule WHERE SmartModule.ModuleGuid = SmartObjectMaster.ModuleGuid,FIRST b_DataSource_SmartObjectMaster WHERE b_DataSource_SmartObjectMaster.ObjectMasterGuid = SmartObjectMaster.DesignTimeDataSourceGuid OUTER-JOIN BY SmartObjectMaster.ObjectName"

SCL-2391 Fixed System.ArgumentOutOfRangeException when dragging a field onto itself in the Reorder Fields Dialog


We've fixed an issue in the Business Entity Designer's "Reorder Fields" Dialog. We issue was seen when starting to reorder columns using Drag and Drop but dragging a column onto itself in the end.

SCL-2392 Fixed error when creating SecurityAssignment using REST POST method


The RestEntitiesWebHandler was only updating fields during an HTTP POST, PUT or PATCH request which have been part of the default view for the @RestAddress annotation. This was not correct. We have now resolved that so that all fields can be updated using the RestEntitiesWebHandler.

SCL-2393 Fixed issue that Field initial value is not correctly set when inserting a field from foreign table


We have resolved an issue in the Business Entity Designer, where adding an existing database field to an existing temp-table did not keep the InitialValueUnknown flag of the new field.


SCL-2374 WinKit RenderedBrowseControl: Split initialization of Query and Columns out of class Constructor


We have now added a new method to the RenderedBrowseControl which allows to re-initialize a RenderedBrowseControl instance with a new Query object handle. This allows to reuse a single RenderedBrowseControl instance when the original ABL code was assigning different queries object handles (as part of a users filtre selection) to the original browse widget.

        Purpose: Initializes the Grid based on the RenderedBrowseContext instance
        Notes:   Invoked from the Constructor. Allows to re-initialize the Grid when
                 either the Query or the Browse columns have changed
        @param poContext An instance of a Consultingwerk.WindowIntegrationKit.Controls.RenderedBrowseContext that contains the settings for this RenderedBrowseControl instance
    METHOD PUBLIC VOID InitializeGrid (poContext AS RenderedBrowseContext):

SCL-2389 Removed dependency from the LogManagerSettings Control to the ILoggingPresetProvider


Initially the LogManagerSettings Control was creating an instance of the LoggingPresetProvider when no ILoggingPresetProvider was yet registered in the ServiceContainer. As the LoggingPresetProvider implementation requires an IConfigurationProvider instance, this was a problem for customers no using an IConfigurationProvider.

We've resolved this dependency now.

Customers using the LoggingPresetProvider need to create an instance before instantiating the LogManagerSettings Control, e.g. through a services.xml file.

New Feature

SCL-2128 Implemented JSON Rendering for Custom Toolbar Buttons


The Rendering of JSON Form layouts for our Angular and NativeScript frontend does now support custom buttons in the Toolbar component.

Those custom buttons are defined in JSON files referenced in the .restapplicationsettings file like this:

    "Web2ToolbarButtonDefinitions": {
        "tableio": "Consultingwerk/Web2/Services/Rendering/default-buttons.json",
        "web2demo": "Consultingwerk/SmartComponentsDemo/Web2/web2demo-buttons.json"

In those JSON files buttons or combo-boxes are defined like this:

    "customer-orders": {
        "buttonType": "button",
        "buttonName": "customer-orders",
        "buttonLabel": "Orders",
        "buttonTooltip": "Show orders of the selected customer",
        "buttonImage": "Consultingwerk/SmartComponentsDemo/Web2/Images/package.png"
    "customer-credithold": {
        "buttonType": "button",
        "buttonName": "customer-credithold",
        "buttonLabel": "Credit hold",
        "buttonTooltip": "Puts the customer on credit hold",
        "buttonImage": "Consultingwerk/SmartComponentsDemo/Web2/Images/sign_stop.png"
    "country-combo": {
        "buttonType": "combo",
        "buttonName": "country-combo",
        "listItems": [
                "value": "AT",
                "text": "Austria"
                "value": "AU",
                "text": "Australia"
                "value": "BE",
                "text": "Belgium"
                "value": "CH",
                "text": "Switzerland"
                "value": "DE",
                "text": "Germany"
                "value": "DK",
                "text": "Denmark"
                "value": "ES",
                "text": "Spain"
                "value": "FI",
                "text": "Finland"
                "value": "FR",
                "text": "France"
                "value": "GB",
                "text": "Great Britan"
                "value": "IT",
                "text": "Italia"
                "value": "NL",
                "text": "The Netherlands"
                "value": "NO",
                "text": "Norway"
                "value": "SE",
                "text": "Sweden"
                "value": "USA",
                "text": "United States of America"

The MetaToolbar instance references those buttons in the ToolbarButtons property. The default buttons (TableIO) and a separator are defined in the file Consultingwerk/Web2/Services/Rendering/default-buttons.json

SCL-2141 Implemented a Repository Designer for Grid Controls


MetaGrid masters can now be designed using a Container Designer Component. This component will show up on the Design Tab in the Object Master Maintenance and allows simple Drag and Drop arranging of Columns originating from the Design Data Source.

SCL-2291 RestServerSessionActivator now returns an HTTP 401 status code when the client principal session is expired.


The configuration of an ABL web application in PASOE supports two different time out values for a login session:

a) OEClientPrincipalFilter.expires=60 in the file controlling the life time of the client-principal object.

This setting defines the absolute time span from the login until the client-principal provided by PASOE expires in seconds.

b) in web.xml

  <!-- ==================== Default Session Configuration ================= -->
  <!-- You can set the default session timeout (in minutes) for all newly   -->
  <!-- created sessions by modifying the value below.                       -->


which specifies a value in minutes after the last request.

While Tomcat (PASOE) handles the session-timeout value automatically, the OEClientPrincipalFilter.expires needs to be handled by the application. We're doing so now by raising the HTTP 401 status code when requests are made after the client-principal has expired.

SCL-2394 Implemented a service for sending Push notifications using Google Firebase


The push notification service implements sending of push notifications to mobile devices using Google's Firebase. The implementation requires the development and deployment of a service on Firebase. A sample implementation can be found here: [ http s://| http s://]

From the ABL side, the service requires configuration of the Firebase service endpoint and in this implementation an authentication token which will be send as the authentication header in the http request. This configuration is obtained from the IConfigurationProvider service (.applicationsettings / .restapplicationsettings file).

    "firebasePushService": {
        "orderstatus": {
            "endpoint": "",
            "authentication": "Bearer ckh0Qnl5NiVFYiRrbSNUX0MkRUMzUA=="

To send a JSON object as a push notification the following IPushNotificationService provides the Send() method with expects an IPushNotification argument. The JsonPushNotification class is a sample implementation for a JSON based push notification.


        DEFINE VARIABLE oPushService  AS IPushNotificationService NO-UNDO .
        DEFINE VARIABLE oNotification AS IPushNotification        NO-UNDO .
        DEFINE VARIABLE oJson         AS JsonObject               NO-UNDO .

        SUPER:SaveChanges () .

                           OR ROW-STATE (eOrder) = ROW-MODIFIED:

            BufferHelper:FindBeforeBuffer (BUFFER eOrder:HANDLE) .

            IF eOrder.OrderStatus <> eOrderBefore.OrderStatus THEN DO:
                oPushService = {Consultingwerk/get-service.i IPushNotificationService
                                                             "NEW FirebasePushNotificationService ()"} .

                oJson = NEW JsonObject () .
                oJson:Add ("shortText":U, SUBSTITUTE ("Order status of order &1 has changed.":U,
                                                   eOrder.Ordernum)) .
                oJson:Add ("longText":U, SUBSTITUTE ("Order status of order &1 has changed to &2":U,
                                                   eOrder.Ordernum, eOrder.OrderStatus)) .
                oJson:Add ("title":U, "Sports2000 Inc.":U) .

                JsonHelper:AddBufferFields (BUFFER eOrder:HANDLE,
                                            "OrderStatus,OrderNum,CustNum":U) .

                oNotification = NEW JsonPushNotification (oJson, "orderstatus":U) .

                oPushService:Send (oNotification).