Release Notes 2025-10-16

Release Notes 2025-10-16

Version Information

OpenEdge Release

Version Information

OpenEdge Release

Version Information

11.7.21, 12.2.18, 12.8.7, 12.8.8, 12.8.9

Release 11.7 #87823@2025-10-16

Retirement of OpenEdge 11.7

OpenEdge 11.7 has been retired by Progress Software on April 1st 2025. In consequence we urge all customers still using OpenEdge 11 to upgrade to OpenEdge 12.2 or 12.8 as soon as possible.

We are intending to drop the official support of the SmartComponent Library for OpenEdge 11.7 during the second half of the year 2025. We will then no longer ensure that new features of the framework will be usable with OpenEdge 11.7

Customers that are concerned by this intention, should reach out to us as soon as possible, so that we can discuss about a solution.

OpenEdge 12.8 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.8. We hereby declare OpenEdge 12.8 fully supported for the SmartComponent Library as of the release of  January 15th 2024.

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.

PASOE / OEMANAGER VS Code Extension

Our first VS Code extension is available in the VS Code marketplace: https://marketplace.visualstudio.com/items?itemName=ConsultingwerkApplicationModernizationSolutionsLtd.oemanager

The extension supports developers with PASOE related routine tasks during development:

  • checking agent or session status

  • trimming the PASOE agents

  • restarting a new agent vai the ping request

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: https://www.consultingwerk.com/support/forum 

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.

New Versions of Proparse .NET Assemblies (30 December 2018)

We have updated proparse with further enhancements in this release (see https://github.com/consultingwerk/proparse/releases/tag/4.0.1.1177). Please download the .NET Assemblies ZIP file from our ESD and replace the proparse.net.dll in your environment with the latest one. The new assembly reference is:

<assembly name="proparse.net, Version=4.0.1.1177, Culture=neutral, PublicKeyToken=cda1b098b1034b24"/>

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

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

defaultHandler=OpenEdge.Web.CompatibilityHandler 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 _utf8.zip 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

http://esd.consultingwerkcloud.com/

https://github.com/consultingwerk/SmartComponentLibrary

Overview of included tickets

SCL-5006 : Implemented JSON rendering support for Smart Grid column aggregates

We have implemented JSON rendering of the Aggregate feature of the Angular Kendo UI grid. The columns can now set the Aggregate to be max, min, sum, count or average. On a per column level you can specify the aggregateTextTemplate and the groupAggregateTextTemplate.

Grouping is enabled in the repository using the AllowGroupBy property of the grid.

SCL-5005 : Enabeld QueryParser to parse query string with INTEGER(), INT64 or DECIMAL() function

The QueryParser class now supports parsing of query strings where the INTEGER, INT64 or DECIMAL functions are used on the left hand side of the equals operator.

SCL-5004 : Resolve dependency from ObjectMasterDesignBusinessTask to Consultingwerk.Windows.Framework package

We have moved the IViewerDesignerPaletteProvider.cls and ViewerDesignerPaletteProvider.cls classes to the Consultingwerk/SmartFramework/Repository/Object package - as those classes are required serverside and should not cause a dependency on the Windows folder.

SCL-5001 : Added new API QueryStringFieldNames to the QueryHelper

We have added a new API QueryStringFieldNames to the QueryHelper class. This API returns the list of field names that are used in a Query String.

SCL-4997 : Simplified import of repository objects in case of GUID conflicts

When using the Object Master Designer or the Compare Repository data screens to import repository data, we’re now checking if the imported data has a new GUID before attempting to import the repository data. The developer is then prompted if he wants to update the Object Master GUID value in his SmartDB to match the imported value prior to attempting to import.

This will simplify handling of GUID conflicts during repository imports.

SCL-4990 : Implemented API to return MCP responses that instruct our Chatbot to open a form

We have implemented the SclngResponse and OpenFormAction classes to return response from MCP calls, that out chat bot will interpret and allow the user to open records in an Angular Form.

SCL-4986 : Implemented Angular rendering of combo-boxes for filter fields

We have implemented rendering of combo-boxes in Angular filter components in the same way as lookups can be rendered.

SCL-4985 : Implemented new variant of the BufferHelper:NumRecords method that takes a TableModel as argument

We have added a new variant of the BufferHelper:NumRecords method that accepts a TableModel instance as the input parameter.

SCL-4983 : Implemented support for long error messages caused by ProDataset validation

When a large number of validation messages was returned by a Business Entity to the GUI for .NET Frontend, the error handling/error message form might have errored due to the dependency on CHARACTER values.

This has been resolved now, so that users or developers will see the actual error messages instead of

REPLACE/CONCAT may not result in data > 32000 bytes. (11678)

SCL-4982 : Introduced DefaultActionBehavior attribute in GridWebRendering

We have introduced a new attribute DefaultActionBehavior to the rendering of Angular grids.

SCL-4979 : Fixed issue with ForeignField handling during CountDataSources

We have resolved an issue in the implementation of counting records on tab folder pages that occurred when the foreign field names in the source business entity and the target business entity did not match.

SCL-4978 : Implemented authentication for MCP calls

The SmartFramework MCP servers now support authentication for the AppServer calls made from them. Authentication is based on an AuthKey (--authKey) startup parameter.

The AuthKey itself is a base64 encoded encrypted value consisting of username, domain name and password. The encryption and decryption is based on the Consultingwerk.SmartFrameworkMcpServer.Authentication.McpServerCredentialService service and uses the internal database identifier of the SmartDB as the encryption key. So the auth key is only valid for a single SmartDB instance (or copies or those).

Developers can generate a new Auth Key using theConsultingwerk/SmartFrameworkMcpServer/Authentication/gen-smartframeworkmcp-auth-key.p procedure.

SCL-4974 : Implemented JSON rendering support for DetailFormMode Smart Grid attribute

We have implemented Angular rendering support for the new DetailFormMode attribute. This attribute is now populated with popup or childform based on the DetailFormModal attribute in the repository.

SCL-4973 : Implemented MCP Server tool to convert ABL Legacy GUI Frames to the Repository

We have implemented an MCP tool that can convert ABL Legacy GUI Frame widgets into the Repository. There are two tools - one that retrieves the names of frames in an ABL routine and another one that migrates a frame into a viewer based on:

  • The name of the ABL procedure (.p or .w file)

  • The name of the FRAME widget to migrate

  • The name for the object master to create

  • The product module for the new object master

  • The name of the Data-Source to use as the Design Time Data-Source

SCL-4922 : Implemented MCP server tool that generates a Business Entity

The SmartFramework MCP server now provides functionality to generate a Business Entity based on the following arguments:

  • Business Entity Name

  • Package Name

  • Database Table Name

  • Additional Fields

SCL-4847 : Angular rendering support for SmartFilter with support for value lists and lookups

This feature introduces backend rendering support for value lists and lookups in the SmartFilter Angular components based on the FilterFieldsAlternativeControlTypes and FilterFieldAlternativeControlNames properties.

SCL-3703 : Replaced ServiceInterface:FetchData calls in SmartFramework with direct access to the Business Entity

We have implemented the remaining batch of changes in which we are now using direct access to Business Entities instead of going via the ServiceInterface class within the SmartFramework. This is in line with our current coding standards and will slightly improve performance.