Version Information

OpenEdge Release	Version Information
11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2, 12.6, 12.7 CQC	Release 11.7 #76192@2023-05-28

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

OpenEdge 12.7 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.7. We hereby declare OpenEdge 12.7 fully supported for the SmartComponent Library as of the release of May 10th 2023.

OpenEdge 12.6 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.6. We hereby declare OpenEdge 12.6 fully supported for the SmartComponent Library as of the release of October 4th 2022.

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-3640 Resolved issues with Business Entity Designer's move/rename tool

Description:

We have resolved issues with the Business Entity Designer’s move/rename tool in multi-project environments where the include files/database models and Business Entity/Data Access classes are typically generated into different project structures.

SCL-4081 Attempt to exceed maximum size of a CHARACTER variable. (9324) when generating Business Entities

Description:

The TempTableMetaInformationPlugin of the Business Entity Generator might have caused the following error:

Attempt to exceed maximum size of a CHARACTER variable. (9324)

This issue is resolved now.

SCL-4082 Cleaned up Demo products & product modules from Deployment

Description:

We have now removed product and product module records from the deployment of SmartFramework data with our product releases by inserting selection criteria in the Consultingwerk/SmartFramework/Tools/Export/export-smartdb.json file.

All products deployed by us are now starting with “SmartFramework” and all product modules with “Consultingwerk”.

Customers are o.k. to remove all other products and product modules previously deployed by us from their SmartDB.

SCL-4102 When only exposing RestMethods but no RestAddresses the Swagger page was showing a 500 error

Description:

We have resolved an issue in the generator for the Swagger page for RESTful Business Entities causing that an error

“Service Addresses Not found.”

was raised and returned with an HTTP 500 status code to the browser when the backend was only exposing RESTful methods of either Business Entities or Business Tasks but no RESTful addresses (CRUD interface).

This issue is resolved now.

SCL-4106 Resolved rendering issue when a DynamicControlGroup was contained in a dynamic viewer

Description:

When rendering a MetaViewer containing a MetaControlGroup, the following error did occur:

BUFFER-FIELD hidden was not found in buffer MetaControlGroup. (7351)

Lead attributes in a chained-attribute expression (a:b:c) must be type HANDLE or a user-defined type and valid (not UNKNOWN). (10068)

The issue is resolved now.

SCL-4107 Import File Status: Fixed "Mark as resolved"

Description:

We have resolved an issue with the “Mark as Resolved” button of the Import File Status form. The button didn’t work as expected, when clicking the button the following message was shown:

Could not locate method 'MarkAsResolved' with matching signature in class 'Consultingwerk.Windows.Framework.Repository.MergeUtil.SmartImportFileStatusFormLogic'. (14457)

SCL-4108 Fixed issues with Group-By in Object Instance Property Grid

Description:

We have resolved issues in the Object Instance Property Grid of the Repository Object Master Designer. Those issues caused wrong attributes being shown when GroupBy is used and selecting a different object instance.

SCL-4116 Business Entity Generator now respects field name mapping when generating AssignSkipDictionary

Description:

Previously the Business Entity Generator was always generating the temp-table field names into the AssignSkipList setting of the Data Access class. This has been modified now, the tool now generates the mapped database field name into the AssignSkipList.

Improvement

SCL-2815 DATA-SOURCE queries used for FetchData operations set FORWARD-ONLY = TRUE

Description:

The FORWARD-ONLY attribute of the DATA-SOURCE queries is set to TRUE by default, when the FetchData request is the initial request. It is not set for FetchData requests for any subsequent batches, or for Count operations, or when a FindRowWhere operation is used.

A new protected property in the Consultingwerk.OERA.DataAccess class called UseForwardOnlyQueries controls this behaviour: the default value is TRUE. Implementing DataAccess classes can override this value, if needed.

If UseForwardOnlyQueries is FALSE, then FORWARD-ONLY is never set.

If the UseForwardOnlyQueries is TRUE, then FORWARD-ONLY is set to TRUE for the parent table in the FetchData query, subject to the criteria above. Child tables always have FORWARD-ONLY set to TRUE, since they are never repositioned or batched.

SCL-4066 ABL Legacy Frame and Browse migration now longer launch Business Entity Designer based on Win32 API

Description:

We have introduced a new Class Consultingwerk.BusinessEntityDesigner.BusinessEntityDesigner. This class supports launching the Business Entity Designer directly using a new prowin.exe/prowin32.exe - instead of launching the .bedgm file using the Win32 API and relying on a correct configuration of the Business Entity Designer Launcher.

SCL-4076 The ClassHelper:FileNameToClass method can optionally throw an error on failure

Description:

A new FIleNameToClass method has been added to the Consultingwerk.Util.ClassHelper class that allows a caller to specify whether or not an exception should be thrown when the file name cannot be resolved to an instance of _Progress.Lang.Class_.

The existing FileNameToClass method ~~without the second parameter~~ keeps its existing behaviour, which is to NOT thrown an exception.

The method signure is below.

    /**
     * Purpose: Returns the Progress.Lang.Class reference for a type referenced
     *          by either the .cls or .r file name
     * Notes:
     * @param pcFileName The file name
     * @param plThrowExceptionIfNotType If TRUE, an exception is thrown of the filename does not represent an OOABL type
     * @return The Progress.Lang.Class reference of the matching type
     */
    METHOD PUBLIC STATIC Progress.Lang.Class FileNameToClass (pcFileName AS CHARACTER,
                                                              plThrowExceptionIfNotType AS LOGICAL):

SCL-4093 Repository attribute DetailForm of MetaGrid now provides lookup

Description:

When setting the properties of a MetaGrid master or instance in the Repository Object Master Designer, we now provide a lookup dialog for repository object instances.

SCL-4098 Added Constructor to FilteredDsQueryString that supports ListQueryExpressionWithSort

Description:

We have added additional constructors to the FilteredDsQueryString class that now also support customizing the query string processing in the DataAccess class based on ListQueryExpressionWithSort.

SCL-4099 Added proxy properties to retrieve link targets to Logic Class base classes

Description:

We have added proxy properties to the SmartDataBrowserLogic, SmartViewerLogic and SmartControlGroupLogic classes. Those properties simpolify accesss to the same named properties of the Owner instnaces:

* SmartDataSource
* SmartTableIOSource
* SmartGroupAssignSource

SCL-4110 Implemented more verbose logging in RestResourceService

Description:

We have implemented more verbose logging in the RestResourceService when locating RESTful methods and addresses from .annotation files. The logging is enabled using the RestResourceService:3 or RestResourceService:4 log entry types.

SCL-4113 Repository Object Master Designer now supports updating of object master from an instance

Description:

The Create Master from Instance tool of the Repository Object Master Designer now supports updating the master of an object instance with the attributes of the instance.

SCL-4114 The ExcelWorksheetImporter now supports for Work sheet Index

Description:

The WorksheetIndex argument passed to the export/import routines have always been ignored so far. Developers had to pass the name of a worksheet in any case.

This has been resolved now, when developers don’t provide the worksheet name anymore, the worksheet index argument is now used correctly.

SCL-4119 FrameParser improvements for parsing PRIVATE-DATA

Description:

We have made the parsing of an ABL source code (AppBuilder) for PRIVATE-DATA definitions of ABL widgets more robust, resolving a few cases where the PRIVATE data might have been ignored when migrating an ABL frame using the ABL Legacy GUI Frame migration.

SCL-4120 AblPrimitiveDictionary now exposes Keys as List to support iterating

Description:

The ABL Primitive Dictionary classes now expose the keys as an iterable List. The following method has been added for that purpose:

    /**
     * Purpose: Returns the Keys as a CharacterList
     * Notes:
     * @return The CharacterList with the keys
     */
    METHOD PUBLIC CharacterList GetKeysAsList():

Task

SCL-4097 Import File Status GUI now provides filter button in Ribbon for pending merge only

Description:

The Import File Status form now provides a state button in the Ribbon for filtering on the Pending Merge Only field.