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 problem was that dbevent is a syntactic predicate \((rule)=>rule, a sort of look-ahead\) in the onstate rule. This meant the ProParser class had inputState.guessing > 0 and did not create the record or identifiers as it was just trying if this path works.

The resolution was to change (dbevent)=> dbevent to dbevent which now causes the parser to actually consider the path.

A new Interface IFetchDataByStaticQueryWithChildTablesRequest has been added to extend the FillChildTables when using static DataAccess queries.

Existing code that uses the ‘IFetchDataByStaticQueryRequest’ continues to work as it does now. For code does not use the ‘IFetchDataByStaticQueryRequest’ but now require the populaton of ‘child tables’, would need to regenerate the DataAccess and related classes.

All smarttable records are created with the databaseName=”FrameworkDB” attribute. The startup\_gui\_fatclient.json does not contain any alias Database Names \(the error pops up even when the alias “SmartDB” is defined there\).

The SmartObjectMasterForm internally invokes the class SmartLockService with a hard-coded “SmartDB” value for the database name.

As the products.i file contains the alias Database Name configuration, the resolution was to incorporate the ‘products.i’ file into the ‘SmartLockService’ class.

The SmartFramework MCP Server now provides the ability for migrating ABL Legacy GUI Browsers into the SmartFramework repository.

For details about the SmartFramework MCP server, follow SmartFramework MCP ServerPreview {: data-inline-card='' }

The OEMANAGER MCP Server supports basic interaction with an OpenEdge PASOE AppServer. The primary intent is to be able to trim the AppServer agent processes to ensure developers are testing the most recent code while developing.

For further details about the MCP Server for OEMANAGER, see https://github.com/consultingwerk/oemanager-mcp {: data-inline-card='' }.

We have enabled the HTTP protocol for the SmartFramework MCP server. For details about the SmartFramework MCP server, follow SmartFramework MCP ServerPreview {: data-inline-card='' }.

The CefSharp API version has now been upgraded to “v141.0.110”.

For further details, please visit https://github.com/cefsharp/CefSharp/releases/tag/v141.0.110 {: data-inline-card='' }. Anyone new to the CefSharp API should read the General Usage Guide.

The SmartFramework MCP Server now facilitates for the development of SmartComponent Library/SmartFramework tasks by providing tools to validate and create object masters from templates.

For details about the SmartFramework MCP server, follow SmartFramework MCP ServerPreview {: data-inline-card='' }

Two new API methods have been added to ProcedureLibraryHelper to extract Images and Files from an APL procedure library.

The first method “ReadImageFromApl” returns a “System.Drawing.Image”, whilst the second method “ReadFileFromApl” returns the contents as a “System.Byte\[\]”. In both instances, the parameters required are ‘the full path to the .apl archive’ and ‘the internal path of the file inside the archive \(e.g. "assets/img.png"\)’.

Created a new GetInputPromptValueObject method to simplify retrieving user-entered values from InputPrompts. This provides a cleaner API that eliminates the need for the verbose InputPrompts:FindInputPrompt\(...\):ValueObject pattern.

A new method 'ToInteger' has been added to the DataTypeHelper class that safely converts an INT64 to INTEGER value.
If the INT64 value exceeds "Consultingwerk.Const:MAX\_INTEGER" \(set at "2147483647"\) then a new exception "ValueTooLargeForIntegerException" is raised and thrown.