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.

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.

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.

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

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!

Open

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.

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:

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.

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:

Customers need to update this Assembly in order to compile the latest releases of the SmartComponent Library.

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.:

This is required as the Hydrid Realm Interface from Progress does not provide the domain name to the authentication method. 

This is an overview of the web handlers supported by this release

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

• Support for RESTful invocation of Business Task and Business Entity Methods

• Invalid Proparse code-page setting corrupts temp-table field labels during "Refresh from Include"

• Generic Factory Service

• Using Invokable Business Entity Methods with Dataset Model Classes

• Using the Business Entity method FetchDataByKeyTable

• PASOE management scripts

• Business Entity Designer Launcher

• Searching data using ROWID's within the SmartBusinessEntityAdapter

• Business Entity Count Method

• SmartFramework ERD Designer

• Changes to the SmartDB and SmartDB upgrade and migration utility

• How to implement dynamic initial values

• How do I control the amount of details provided for error messages caused by our web handler

• Using custom log entry types

• Strong-typed Query Support

• Swagger REST API Documentation for RESTful Services

• Swagger REST API Documention for JSDO Generic Service

• Scaffolding utility for common helper classes

• RESTful services

• JSON Configuration File Format

• Common Component Specification (CCS)

http://esd.consultingwerkcloud.com/

https://github.com/consultingwerk/SmartComponentLibrary

The GetIdentityProvider method determines the provider by looking at the Client Principles identityprovider property \(allows us to determine the identify of which provider Keycloak has used for authentication\).

For authentication directly with Entra, the identityprovider attribute is now populated using the “iss” claim.

The MetaGrid has been updated to support two new attributes as properties "ReportTitleTemplate" and "ReportFooterTemplate" that shall be rendered as properties at the root level of the grid "componentOptions".

When trying to access the following within OpenAPI \(Swagger\) https://sfrbo.consultingwerkcloud.com:8821/web/Entities/SmartFramework/Authorization/GetIdentityProvider, an Invalid Rest Address exception is thrown. With recent changes for the return type 'XML', the correct content-type was missing. This fix has ensured that the correct content-type is provided.

An issue has been resolved when using the "Lookup Link Source/Target" and filtering on one of the Column's.

A new feature protected by a security token has been added that allows the opening of the current form in the repository designer.

The facility within RESTful / Swagger now provides the ability to return a content type of XML. The @RestMethod annotation now supports an additional argument "contentType" which now allows us now to have a method either return application/json, text/plain or text/xml etc.. If the content-type is not specified, then application/json is assumed.

A new method GetIdentityProvider has been created to provide ID Provider details based on the “idprovider” property. The following endpoint "/web/Entities/SmartFramework/Authorization/GetIdentityProvider" returns a JSON Object with the following proerty values:
"idprovider", "description" and "icon".

A new feature has been added to the MCP Server tool that can return a a list of product modules. So that the LLM can validate/propose product modules, returning a JSON Object providing the following layout:

• Product Module Code

• Product Code

• Product Module Description

• DataFolder

For further details, see SmartFramework MCP ServerPreview {: data-inline-card='' }

An issue has been resolved on the Frame Migration MCP Server Tool when SmartViewerBuilders retrieves the the dataset on an AppServer.