Version Information

OpenEdge Release	Version Information
11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2.7, 12.4.1, 12.5	Release 11.7 #70719@2022-06-09

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

OpenEdge 12.3 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.3. We hereby declare OpenEdge 12.3 fully supported for the SmartComponent Library as of the release of November 24th 2020.

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.

.NET Framework Version 4.7

.NET 4.7 is not supported with OpenEdge 11.x, see: Is .NET 4.7 certified and supported for OpenEdge?

Progress has reported severy issues with OpenEdge GUI for .NET and .NET 4.7: GUI .Net Application crashes after .Net upgrade to 4.7

When using the .NET Framework 4.7, please make sure, you upgrade to OpenEdge 11.6.4 or OpenEdge 11.7.2 or later. Also, it may be required to recompile the application on a PC running .NET Framework 4.7 when applications are also executed on a PC with .NET Framework 4.7.

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.

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 11.7.2.001 we further recommend all customers to apply this hotfix as well.

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-3691 Fixed issue in JSDO Generic Service with un-nested data-relations

Description:

Recent changes to JSDO Generic Service has caused exposure of all data-relations as nested - even when they have not been defined as nested.

This issue has been resolved.

SCL-3692 Implemented Service Adapter method for async Business Task method with no output

Description:

We have implemented further methods of the InvokeTaskAsync method of the ServiceAdapter. These additional methods can be used when the caller is not expecting no output from the called Business Task.

By not waiting for an output from the Business Task method the client does not need to set up the read response handler.

SCL-3699 TableModel:BufferCopy() now verifies if enum property values are valid before invoking properties of the reference

Description:

The TableModel’s BufferCopy() method was erroring when a Enum type properties value aws not valid.

This issue has been resolved now.

Improvement

SCL-3670 Improved logging in SmartRequestManager:CancelRequest

Description:

We have now improved logging in the SmartRequestManager:CancelRequest method.

Based on the SmartRequestManager custom log entry type we’re now providing detailed information about why CancelRequest has failed.

SCL-3684 SmartViewerControl:RecurseInitializeControlEventHandler to prevent handling of components in nested viewers etc.

Description:

The SmartViewerControls’s RecurseInitializeControlEventHandler method is subscribing various events of components contained in the SmartViewer and deciding which components should be enabled during various update states. This method also handles components that are contained in UserControls (including nested SmartViewers) contained on the SmartViewer. This may cause undesired side-effects when too many components and their containers are disabled outside of an update state.

Developers can now implement the Consultingwerk.SmartComponents.Base.IAlwaysEnabledContainerControl interface for those user controls where the RecurseInitializeControlEventHandler method should not recurse into.

SCL-3685 QueryHelper:WhereClauseBuffer is now PUBLIC

Description:

The method used to be PRIVATE but customers have requested access to it for custom QueryHelper implementations.

SCL-3686 Support filtering of Business Services for Swagger for RESTful entities

Description:

We have implemented support for filtering the services included in a Swagger File. A Service implementing the new Consultingwerk.OERA.Swagger.ISwaggerEntitiesFilter interface can be registered and supports filtering of every business service included in a Swagger file.

SCL-3687 Swagger for RESTful entities now only provides the filter q for entities that support the QuickSearch

Description:

We have introduced a new Interface Consultingwerk.OERA.ISupportsQuickSearch that can be implemented by Business Entities implementing the QuickSearch Named Query. Business Entities implementing this Interface will provide the q filter string parameter in the Swaggerfile for RESTful entities.

SCL-3688 Implemented ability to customize Swagger HTML template

Description:

A new Interface Consultingwerk.OERA.Swagger.ISwaggerTemplateLocator has been implemented. Services implementing this Interface can be used to control the location of the templates for the Swagger HTML or JSON files.

SCL-3689 Swagger for RESTful entities now hides serialize-hidden fields

Description:

The Swagger pages will no longer include fields marked as SERIALIZE-HIDDEN in the Dataset definition.

SCL-3690 Added BeforeDeactivated event to ServiceInterface

Description:

We have added a new BeforeDeactivated event to the ServiceInterface.

This event can be used by services on the Backend to invoke code at the end of every AppServer request - but before the context is stored or disposed.

SCL-3694 Improved filtering on ? in JSDO Generic Service

Description:

We have improved the handling of the unquoted ? in query strings issued by JSDO based clients. The unquoted ? is not treated as the unknown value as expected.

SCL-3696 Providing Consultingwerk.UltraControls assembly for OpenEdge 12.1

Description:

We are now providing a copy of the Consultingwerk.UltraControls assembly that was built against the OpenEdge UltraControls shipped with OpenEdge 12.1.

SCL-3697 Styling of Repository Form Background

Description:

The TableLayout Panels used by the ResponsiveContainerRenderer when rendering a MetaForm on Windows now support custom background colors. The background color is determined from the current background color of the Infragistics UltraPanel component. The color can further be customized by using a StyleSet name. The name of the StyleSet used to determine the background color is controlled using the static property

Consultingwerk.Windows.Framework.Repository.Rendering.Form.ResponsiveContainerRenderer:TableLayoutPanelBackgroundStyleSet

The value of the property can be set using the staticProperties section in a JSON session startup file.

SCL-3698 Improved handling of long error messages (e.g. long stack trace) in the ErrorHelper

Description:

We have improved handling of long error messages or stack-traces in the ErrorHelper. Previously those errors might have caused CHARACTER values with more than 32k being concatenated. This has been improved now.

New Feature

SCL-3253 Implemented CefSharp based (Chromium) web browser Form in GUI for .NET

Description:

We have now included a CefSharp ( https://github.com/cefsharp/CefSharp ) based Web Browser Control for OpenEdge GUI for .NET. This feature has three components:

We have included a build of CefSharp version 101 for both 32 and 64 bit. Treh core Chromium implementation is implemented as native Windows code (C++) and is therefore not agnostic to the bittness of the CPU. Using the private probing path in the assemblies.config file developers can control if the 32 or 64 bit variants of the Windows DLLs and .NET Assemblies is used.

Note: Consultingwerk cannot provide support for the actual CefSharp implementation. Customers using CefSharp are required to keep the included CefSharp up to date themselves. Consultingwerk can support customers in setting up build environments for CefSharp using Microsoft Visual Studio.

We have further implemented a new Assembly Consultingwerk.CefSharpSupport. This assembly solves integration challenges between CefSharp and ABL based applications.

Note: When upgrading the CefSharp implementation, this Assembly needs to be rebuilt as well. The source code for this assembly is provided on our ESD website.

We are providing now a new Service Consultingwerk.Windows.CefBrowser.ICefBrowserService with a default implementation of Consultingwerk.Windows.CefBrowser.CefBrowserService. This service provides a method to open an URL in a browser window either as a standalone window or an MDI Child of the application’s MDI container.

SCL-3543 Implemented rendering support for multiple tab-folders (Windows and Angular)

Description:

We have implemented support for rendering nested tab pages in a MetaForm container. Rendering is supported both on Angular and Windows in the same way.

The tab pages in the MetaForm repository data now optionally support the TabGroup setting. A tab folder instance also provides TabGroup as an attribute. When set a tab folder only renders the pages of the matching TabGroup. This allows the definition of pages for multiple different tab groups in a single MetaForm.