Release Notes 2025-05-31

Release Notes 2025-05-31

Version Information

OpenEdge Release

Version Information

OpenEdge Release

Version Information

11.7.21, 12.2.13, 12.8.4, 12.8.5, 12.8.6

Release 11.7 #85852@2025-05-31

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

 

Bug

SCL-4438 Fixed nested table exposed in Swagger schema

Description:

In certain situations nested tables of a ProDataset have been exposed unexpectedly in the JSON schema embedded in a Swagger page generated for a PASOE RESTful backend.

This issue is resolved now.

SCL-4812 Fixed RestEntitiesWebHandler:BuildCollectionResponse issue when ID fields are empty

Description:

We have resolved an issue in the RestEntitiesWebHandler causing empty JSON object to be returned from a request when there have been no ID fields defined.

SCL-4824 Removed redundant code in the JsonHelper

Description:

We have removed a redundant condition form the JsonHelper:AddObjectPropertiesToJson method

SCL-4828 PROPATH lookup missing when reading images for user/group hierarchy diagrams

Description:

We’re now using the PROPATH to lookup the image paths used the user/group hierarchy diagrams.

SCL-4836 JsonHelper's AddWidgetPropertiesToJsonArray method no longer ignores the pcExceptPropertyNames parameter

Description:

We have fixed the functionality of the pcExceptPropertyNames parameter of the JsonHelper:AddWidgetPropertiesToJsonArray method.

SCL-4842 Certificate importer failed for www.infragistics.com

Description:

The SslCertificateImporter (scl-cert-import.cmd) did fail to import the Infragistics SSL certificate due to an issue with how we were determining the root certificate.

Previously we looped backwards through the whole set, but in general terms we need the issuer of the second/intermediary certificate.

Improvement

SCL-4324 All Services now use SessionManager:SessionId instead of the SessionId of the current request

Description:

The framework code now consistently refers to the SessionManager:SessionId property to determine the current session-id for an AppServer request. The SessionManager:SessionId property is determined using the Consultingwerk.Framework.Session.IClientPrincipalParser service so that customers can customize how the session id, user name and domain name values as extracted from the current client-principal instance.

This is useful for customers not using a Hybrid Realm implementation for authentication - as those implementations may be providing different properties or properties in the client-principal.

SCL-4808 Implemented IDE Integration with Windsurf

Description:

We have implemented the IDE Integration with Windsurf ( https://windsurf.com/editor ) in the same way we support VS Code or Progress Developer Studio. Developers can configure the Business Entity Designer to open generated code in Windsurf now and tools like the Proparse TreeView Form allow to open the current file in Windsurf too.

Windsurf is based on VS Code and offers extended AI features. Windsurf was formerly known as Codeium.

SCL-4810 Implemented Extension for the ProparseTreeView that prompts to explain selected code in Chat GPT

Description:

A new extension to the Proparse TreeView Form allows to ask Chat GPT to explain the selected source code.

SCL-4811 Improved error message when trying to render a viewer as a form (Angular)

Description:

We have improved the error message shown when trying to run an unsupported repository object using the Dynamic Launcher in Angular.

SCL-4813 New Objects generated by the "New Object Master From Template" wizard no longer flagged as template

Description:

When creating forms using the “New Object Master From Template” wizard, the generated objects are no longer flagged as being templates themselves.

SCL-4814 SmartUiAction/MessageInteractionService/ListQuestion should allow to omit the MessageId parameter

Description:

The MessageID parameter of the SmartUiAction/MessageInteractionSerivce/ListQuesting can be used to provide a unique identifier for the source code location that “raised” a question or input prompt. This is required to match a question and the later received answer.

Developers are now able to omit this parameter - in which case we use a hash code of the current stack trace as an alternative unique identifier for the location in the source code.

SCL-4815 New Holder class and Interface for BufferHandle

Description:

We have implemented a new Interface and Holder class for API’s that require a BufferHandle argument. This is also the foundation for the change in https://consultingwerk.atlassian.net/browse/SCL-4816

SCL-4816 Implemented Add DatasetHelper:AddErrorMessage methods based on IBufferHandle

Description:

We have added variants of the DatasetHelper:AddErrorMessage API’s that access the buffer handle based on the IBufferHandle parameter.

SCL-4817 REST Entities Handler now split field info from error messages

Description:

The REST Entities web handler now splits the field info from the error message when returning error strings to the HTTP client. Previously the field info was appended CHR(4) delimited to the error message.

SCL-4822 Re-introduced sicatch.i in OERA/support/proSIinvokeTaskAsync.p

Description:

We have implemented the sicatch.i include in the proSIinvokeTaskAsync.p procedure. This ensures that runtime errors are thrown to the client also for asynchronous AppServer calls.

SCL-4823 Introduced constant class with names and codes of the Consultingwerk supported security realms

Description:

We have implemented a new class returning constants about the Consultingwerk provided security realms. The constants are defined for the GUID, Code and Description of the security realms and can be accessed using the Consultingwerk.SmartFramework.Authorization.SmartSecurityRealms class.

SCL-4825 Implemented Toolbar Security in Web

Description:

We have implemented the Toolbar Security for Angular web applications.

SCL-4826 Implemented support for Security-Disabled Columns in Angular Grid Rendering

Description:

We have implemented support for security-disabled columns in the Angular Grid rendering.

SCL-4827 Fixed tab order in user maintenance viewer (GUI for .NET)

Description:

We have fixed the tab-order of the fields in the user maintenance viewer.

SCL-4833 Casing of code refactored from update editing statements now matches case of Business Entity Designer

Description:

The Update source code refactored from UPDATE EDITING statements now matches the source code casing used by the Business Entity Designer/Generator when generating Business Entities.

SCL-4835 Removed extra space characters returned by some QueryHelper API's

Description:

Some methods of the QueryHelper did return additional space characters in Query Strings returned. Those additional space characters did not impact the functionality or usability of the returned Query Strings.

The change was made primarily for cosmetical reasons.

SCL-4838 Fix TypeIconProvider for MetaTabFolder

Description:

The TypeIconProvider class used by the Reposiory Designer to determine the image used for an object instance did use an invalid base class name to test against tab folders. This did result in a generic component image being used for tab folders instead of a specific tab folder image.

SCL-4839 Disableed Toolbar Authorization Provider in Consultingwerk Studio

Description:

We have disabled the Toolbar Authorization Provider Service in the Consultingwerk Studio applications so that the tools functionality is not impacted by application security configurations.

SCL-4840 Table/field name Content Assist now supports filtering on numbers, hyphens and underscores

Description:

The table/field name content assist used in the Business Entity designer source default query editor or the business entity tester now also supports filtering as you type on numbers, hyphens and underscores.

SCL-4841 Implemented rendering support for CountDataSources property in Smart Tab Folder

Description:

We are now rendering the CountDataSources property to the tab folder in the Angular JSON markup. This is to support the count records on tab pages feature in the Angular UI as well.

SCL-4846 Reimplement the method we're using to detect the ABL appname in SmartRequestManager

Description:

The SmartRequestManager needs to know the name of the current PASOE ABL application, as this is required for the OE Manager requests to terminate a request. Previously we’ve been using the ClientContextId of the current request as a foundation. But as this is not successful in all authentication methods of the PASOE spring framework implementation, we have switched this to be based on the -zAppName startup parameter passed by the SessionManager to the agent process.

SCL-4849 ABL FrameParser now supports SKIP phrases and colon aligned positioning

Description:

When calculating row and column based positioning of ABL legacy frames, the FrameParser now considers colon aligned positioning and SKIP phrases. The result is a more precise adoption of the frame layout.

SCL-4850 Implemented ABL Frame migration preprocessor that detects lookups in UPDATE-EDITING Phrases

Description:

We have implemented another ABL Frame migration preprocessor that detects lookups in UPDATE-EDITING style layouts, typically TTY. A lookup is assumed, when a description field with no label is detected next to a key field.

New Feature

SCL-4728 Implemented new Java WebApp to collect runtime data from PASOE JMX/OEMANAGER

Description:

We have implemented a new PASOE/Tomcat web app that can collect runtime data about the PASOE agents/agent sessions.

For details refer to https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/2811854849/PASOE+Agent+Telemetry

SCL-4755 Interface generator now issues a warning instead of failure if class inherits from .NET class

Description:

The Interface generator tool (scl-gen-interface) now only shows a warning, if based types of the class for which the interface should be generated can not be found. This resolves an error situation when using the tool with ABL classes that inherit from a .NET type.

Task

SCL-4834 create-instance.i and BufferDataSource constructors now support up to 30 arguments

Description:

We have increased the number of arguments (Buffer definitions) that can be passed to the BufferDataSource constructors from 15 to 30. The create-instance.i Include File now also supports up to 30 parameters passed to any constructor of classes instantiated by the Factory service.

SCL-4843 Added more precise checks to the ClassHelper ValidateClassName API

Description:

The method ValidateClassName of the ClassHelper API has been enhanced to be more precise when testing an ABL string for compatibility with ABL class names:

* first character needs to be a letter
* empty strings no longer allowed
* allow #, $ and % in class names

SCL-4845 Added @RestMethod annotation to CountRecordsBusinessTask:CountRecords

Description:

The CountRecords method of the CountRecordsBusinessTask is now accessible using a RESTful endpoint. This is to support providing the record count on tab pages feature also in the Angular web UI.