Version Information

OpenEdge Release	Version Information
11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2., 12.6	Release 11.7 #75097@2023-03-19

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

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-3987 JPNode:ToStringSourceText now returns operator text in correct order

Description:

We have fixed issues with some fortran style operators being returned in wrong position by the JPNode’s ToStringSourceText() method. THis fixes issues with using Proparse to generate ABL source code based on a movified ParseUnit. Proparse has been updated to

<assembly name="proparse.net, Version=4.2.0.2, Culture=neutral, PublicKeyToken=cda1b098b1034b24"/>

The Proparse and IKVM assemblies shipped are now

<assembly name="IKVM.OpenJDK.Core, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>
<assembly name="IKVM.OpenJDK.Text, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>
<assembly name="IKVM.OpenJDK.Util, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>
<assembly name="IKVM.Runtime, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>

SCL-4007 Static Names Generator failed with sub-packages with "similar" names

Description:

We have resolve an issue in the static names generator tool that caused the tool to malfunction when a code base contains a package that is the abbreviated name for another package, e.g.

* Beckelmann.Auftrag
* Beckelmann.AuftragsKlasse

The issue has been fixed now. Static names will be generated properly in those cases.

For more information on the static names generator, refer to the Confluence documentation: https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8094104/Static+Names+Generator

SCL-4008 Parameter Comment Validator did not alert about some missing Constructor parameters

Description:

We have resolved an issue in our parameter comment validator that caused some missing parameter comments not to be reported by our unit testing. In consequence we have added missing parameter comments to our source code documentation.

SCL-4009 Fixed issues with Assert methods and LONGCHAR variables/properties

Description:

We have resolved issues in the Assert:Equals and Assert:NotEquals methods causing issues to compare LONGCHAR values to both the empty string and ?.

SCL-4012 SecurityRealmInfoBusinessTask in the SmartComponent Library was not referencing the interface (ISecurityService)

Description:

The SecurityRealmInfoBusinessTask did reference the SecurityService directly using it’s class name and not based on the ISecurityService interface. That made it implossible to register and use custom ISecurityService implementations in a customer project. The limitation has been lifted now. The SecurityRealmInfoBusinessTask is now referencing the registered ISecurityService implementation based on the Interface and not a Class type.

Improvement

SCL-3970 Improved exception handling in proparse

Description:

We have improved Exception handling in our port of Proparse. Exceptions will now only include the “Original Exception” in the message text when the inner exception is not null. We’ve also improved the way the original stack trace is returned. Proparse has been updated to

<assembly name="proparse.net, Version=4.2.0.2, Culture=neutral, PublicKeyToken=cda1b098b1034b24"/>

and we’ve also added the

<assembly name="IKVM.OpenJDK.Text, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>

assembly as a new dependency to the deployment. The Proparse and IKVM assemblies shipped are now

<assembly name="IKVM.OpenJDK.Core, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>
<assembly name="IKVM.OpenJDK.Text, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>
<assembly name="IKVM.OpenJDK.Util, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>
<assembly name="IKVM.Runtime, Version=7.2.4630.5, Culture=neutral, PublicKeyToken=13235d27fcbfff58"/>

SCL-3990 Added support for JPNode's setNextSibling and setPrevSibling to IProparseAPI

Description:

We have extended the IProparseAPI based API to provide the ability to set the NextSibling and PrevSibling properties of a JPNode using the setNextSibling() and setPrevSibling() methods. This provides a simple way to reorder nodes within a ParseUnit or skip nodes when regenerating source code from the AST.

Support is implemented both for Proparse.NET and the Proparse Web Service.

SCL-4005 Added column for original field name to Legacy GUI Frame Migration tool

Description:

We have added a new column called “OriginalFieldName” to the Legacy GUI Frame Migration Tool. This column can be used by custom migration routines to keep track of a database field name an ABL field level widget is bound to.

SCL-4010 Support for Custom Control Properties in AblFrameMigration

Description:

We have added support in the Consultingwerk.BusinessEntityDesigner.Generator.IControlGenerator Interface and it’s implementations to pass custom control specific property values form plugins to the Legacy GUI Frame migration tool. This allows to pass additional control configuration properties like details about the SmartBusinessEntityLookup to the control generators.

SCL-4011 Listed restriction of 10 buffer names or buffers specs being passed to the BufferDataSource constructor.

Description:

To support more complex queries the BufferDataSource constructor now supports 15 parameters instead of 10. To support usage based on the IFactory service, we have also extended the Consultingwerk/create-instance.i include file/macro to support up to 15 parameters being passed the Factory service.

SCL-4013 Ignoring Literal widgets when generating Business Entity from Frame

Description:

The ABL Legacy GUI Frame migration utility now ignores literal widgets when generating a Business Entity schema based on the (databound) widgets on an ABL frame widget. Literal widgets are not databound and cannot be used to represent application data and thus should not be used as the foundation of a Business Entity schema at all.

SCL-4014 ProparseHelper:GetBufferFieldName now returns unabbreviated field name

Description:

When the original ABL source code contained abbreviated field names the ProparseHelper’s GetBufferFieldName API returned the abbreviated field name. We have changed this implementation to return the full unabbreviated field name. This allows to map abbreviated references of fields in legacy code to the actual database or temp-table field name.

SCL-4015 Added support for VIEW-AS "fill-in" attribute when generating instances on a meta viewer

Description:

When generating a MetaViewer object in the SmartFramework based on an ABL frame layout the Legacy GUI Frame Migration tool now supports settings the VIEW-AS “FILL-IN” attribute in the repository. This allows to distinguish between rendering of logical fields as checkboxes or text widgets.

SCL-4016 AblFrameMigrationForm now provides PUBLIC access to ViewerSettings instance

Description:

We have added a PUBLIC method GetViewerSettings() to the AblFrameMigrationForm. This methods allows custom plugins to the tool to obtain details about the currently processed ABL source code file, selected frame and Business Entity configuration.

Story

SCL-3964 SmartScheduler runtime supports JSON configuration file

Description:

The SmartScheduler runtime supports using a JSON configuration file to specify parameters for the scheduler, using the Consultingwerk JSON Configuration File Format . Values specific to the Scheduler Runtime may be provided as static properties (eg {{Consultingwerk.SmartFramework.Scheduler.Runtime.SchedulerRuntime:Verbose}} ) in this config file, or they may be specified as a parameter to the PCTRun task. Values supplied to the Ant task will override those in the configuration file.

For more details see https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/294584321/Configuring+the+SmartScheduler+runtime .