Release Notes 2018-08-25

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 #48039@2018-08-25

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-2216 Resolved: 11.7.3 Visual Designer disabling properties of ABL user controls


Progress Software has released hotfix 7 for OpenEdge 11.7.3 ( This hotfix resolves critical regression issues with the Progress Developer Studio for OpenEdge (PDSOE) Visual Designer.

We have now successfully tested the functionality of the SmartComponent Library on OpenEdge 11.7.3 and are able to announce full support of the SmartComponent Library on OpenEdge It is strongly recommended for all customers on OpenEdge 11.7.3 to apply hotfix 7 before using the SmartComponent Library.

SCL-2322 Improved error handling in SmartHybridRealm when DefaultAuthenticationDomain is invalid


WE have improved the error handling in the SmartHybridRealm class when the DefaultAuthenticationDomain setting in .restapplicationsettings did contain an invalid value (non existing domain).

Previously an error

[18/08/14@07:26:04.782+0200] P-007340 T-019380 1 AS-7 SmartHybri     ### ValidatePassword UID=42
[18/08/14@07:26:04.979+0200] P-007340 T-019380 1 AS-7 -- No record is available in buffer eSmartLoginCompany.

was raised.

SCL-2326 When there is a compile-error in the Data Access class, the Business Entity no longer raises an A:B.C reference error


When the Data Access class could not be started due to a compile error, the Business Entity did raise a meaningless invalid A:B:C reference runtime error.

We are now raising a more meaningful application error instead.

SCL-2327 Read permission denied error by DB (14323) when starting Business Entity Designer


When the DICTDB has auditing enabled and the user had no authorization for the audit trail, the Business Entity Designer caused an runtime errorwhen the tool was started.

Read permission denied by DB (14323)

Call Stack:
FetchTable Consultingwerk.BusinessEntityDesigner.Services.DatabaseSchemaDataAccess at line 621  (..\SmartComponentLibrary\Consultingwerk\BusinessEntityDesigner\Services\DatabaseSchemaDataAccess.r)
FetchMetaschemaTables Consultingwerk.BusinessEntityDesigner.Services.DatabaseSchemaDataAccess at line 472  (..\SmartComponentLibrary\Consultingwerk\BusinessEntityDesigner\Services\DatabaseSchemaDataAccess.r)
FetchData Consultingwerk.BusinessEntityDesigner.Services.DatabaseSchemaDataAccess at line 360  (..\SmartComponentLibrary\Consultingwerk\BusinessEntityDesigner\Services\DatabaseSchemaDataAccess.r)
FetchData Consultingwerk.OERA.BusinessEntity at line 895  (..\SmartComponentLibrary\Consultingwerk\OERA\BusinessEntity.r)
FetchData Consultingwerk.OERA.BusinessEntity at line 969  (..\SmartComponentLibrary\Consultingwerk\OERA\BusinessEntity.r)
FetchData Consultingwerk.OERA.ServiceInterface at line 839  (..\SmartComponentLibrary\Consultingwerk\OERA\ServiceInterface.r) 

SCL-2328 Business Entity Designer canvas was not large enough for table with many fields


The height of the Design Canvas of the Business Entity Designer was limited to 5000 pixel and did truncate large tables on the design canvas.

We are now dynamically setting the maximum height of the design canvas based on the available tables and their position.

SCL-2329 scl-pasoe scripts only work from same drive where SCL is installed


The script now supports running from a different drive as where SCL is installed.

SCL-2335 Implemented a wrapper procedure for SmartModifiedBusinessEntity:DeleteAll()


We have implemented the procedure Consultingwerk/SmartFramework/Tools/Import/reset-modified-status.p which can be executed using a PCTRun task in an ANT script.

This allows customers to reset the modified state (e.g. SmartFramework repository) from automation scripts.

SCL-2336 .NET Error When Using Export To Excel


The Consultingwerk.Windows.Util.UltraGridExcelExportController component was raising an 15580 runtime error after closing the Dialog that prompts to fetch more rows from the backend after upgrading to OpenEdge 11.7.

We have resolved this error now.

SCL-2337 SmartUserGroupDataAccess needs to add UserGroupGuid to AssignSkipList




SCL-2323 Validation generated by Business Entity Designer does now process the UNMODIFIED rows only


Previously the generated validation code in a Business Entity did process all records of the AFTER-TABLE. We have modified this now, so that only modified or created records are validated.

SCL-2325 Import failed if PageSequence fields are changed


The import of .smartrepo files failed if this did result in switching the page sequence of two existing SmartPage records. This issue was caused by the fact that the SmartPage records have two unqiue indexes.

This issue is resolved now.

SCL-2331 Implemented a setting in .restapplicationsettings to disable CLIENT-PRINCIPAL validation


When theclientPrincipalSeal setting in .restapplicationsettings is now set to null or completely missing, the RestServerSessionActivator will no longer attempt to modify the CLIENT-PRINCIPAL seal using the VALIDATE-SEAL method.

This allows to bypass the seal validation in case of configuration issues with database domains.

SCL-2332 Avoid unneccessarsy repositioning after update in a SmartDatasetChildAdapter a SmartBusinessEntityAdapter with AutoCommit = FALSE


When a SmartBusinessEntityAdapter has committed records modified by a linked SmartDatasetChildAdapter to the backend the SmartBusinessEntityAdapter did previously reopen it's query and reposition to it's current user. This was causing unnecessary screen refresh caused by two PositionChanged events and might have caused a rather long performance penalty.

We have resolved this by detecting if the SmartBusinessEntityAdapter has updates any changes as well that may require the query to be reopened to reflect the modified sort order after records have been updated.

We have implemented the new event SetQueryOpenAfterCommit in the SmartBusinessEntityAdapter class that allows to change this behavior, allowing to control if or if not the SmartBusinessEntityAdapter should reopen it's query after committing changes to the backend.

     * Purpose: Raised after committing changes to the backend to determine of the
     *          SmartBusinessEntityAdapter should be opening it's query (EntityTable)
     *          to refresh updates
     * Notes:
     * @param sender The object that raised the SetQueryOpenAfterCommit event
     * @param e The SetQueryOpenAfterCommitEventArgs with the data for the event
    DEFINE PUBLIC EVENT SetQueryOpenAfterCommit SIGNATURE VOID (sender AS Progress.Lang.Object,
                                                                e AS SetQueryOpenAfterCommitEventArgs).

New Feature

SCL-2318 New QueryHelper methods to simplify manipulating a QueryString's Sort phrase


We've implemented the following methods in the QueryHelper to simplify sort string manipulation:

     * Purpose: Returns the sort phrase of the given query string
     * Notes:
     * @param pcQueryString The original query string
     * @return The sort phrase of the query string

     * Purpose: Returns the list of SortField instances for the given query string
     * Notes:
     * @param pcQueryString The original query string
     * @return The list of SortField instances
    METHOD PUBLIC STATIC ListSortField QuerySortList (pcQueryString AS CHARACTER)

The ListSortField class returned by the QuerySortList has method

     * Purpose: Returns a sort phrase (query string)
     * Notes:
     * @return The sort phrase represented by the ListSortField

which returns the Sort String for a query.

SCL-2319 SessionInfoWeb Handler should include details about Client-Principal


The SessionInfoWebHandler now returns all properties of the session CLIENT-PRINCIPAL object handle including the remaining validity of the client-principal seal.

SCL-2320 SessionInfoForm now includes remaining validity of the session's CLIENT-PRINCIPAL seal.


The SessionInfoForm now includes remaining validity of the session's CLIENT-PRINCIPAL seal.

SCL-2321 Implemented new optional Parameter to SmartUnit which may specify the LOG-ENTRY-TYPES


Added a new (optional) parameter to the SmartUnit ANT Macro. Using the logEntryTypes parameter, it is now possible to specify the LOG-ENTRY-TYPES used when executing unit tests.

SCL-2330 RESTful methods now support JSON as the input parameter type


We have implemented support for RESTful method invocation for methods with JsonObject parameters.

It is now possible to define RESTful methods like this:

    @RestMethod (address="/TestSCL2330/~{CustNum}",
    @RestMethod (address="/TestSCL2330",
    @RestMethod (address="/TestSCL2330/~{CustNum}",
    METHOD PUBLIC JsonObject TestMethod (poParameter AS JsonObject):

SCL-2334 Support for RESTful methods with no input parameter at all


We have implemented support for RESTful method invocation for methods with no parameter at all.

It is now possible to define RESTful methods like this:

    @RestMethod (address="/TestSCL2334",
    METHOD PUBLIC JsonObject TestMethod ():

In order to support Business Task methods with no parameters, we have implemented a new method in the ServiceInterface class:

     * Purpose: Invokes a method in a Task class.
     * Notes:   When no MethodName is passed then "Invoke" will be executed as the
     *          default task method
     * @param pcTaskName The name of the task class
     * @param pcMethodName The name of the business entity method to invoke
     * @return The optional return value object of the Business Task Method
    METHOD PUBLIC STATIC Object InvokeTask (pcTaskName AS CHARACTER,
                                            pcMethodName AS CHARACTER):