Version Information

OpenEdge Release	Version Information
11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2., 12.5.2	Release 11.7 #73045@2022-11-21

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-3722 FIxed parsing of Annotations with periods in the name in Proparse

Description:

We have fixed the parsing of ABL Annotations in Proparse. When the annotation identifier was defined with one or multiple dots, this was parsed into multiple nodes. We’re now parsing this into a single ID node.

SCL-3840 QueryString:ParseQuery parses " AND " into " A ND " incorrectly during deployment of SmartMessageData

Description:

We have fixed the query definition in some of the deployment dataset definition in Consultingwerk/SmartFramework/Tools/deployment-datasets.json to resolve issues when building the executed DB query strings.

SCL-3844 Fixed error rendering custom toolbar button on a toolbar in a tab-folder

Description:

When a custom action is referenced in a repository toolbar instance in a tab folder page the following error was raised:

Invalid handle. Not initialized or points to a deleted object. (3135)

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

RenderRootTool Consultingwerk.Windows.Framework.Repository.Rendering.Toolbar.SmartToolbarControllerRenderer at line 681

This issue is now resolved.

SCL-3849 Fixed X-NODEREF or X-DOCUMENT NODE-VALUE got an error: String length too long during GenericDataImporter

Description:

We have now made the XmlHelper’s DecodeLineBreaks method tollerang to large string values in the XML document.

Improvement

SCL-3821 Enhancements to the BusinessEntityBusinessTask generator functionality in Business Entity Designer

Description:

The BusinessEntityBusinessTaskGeneratorPlugin of the Business Entity Desinger now supports the generation of a DatasetModel for the BusinessTask. The user is prompted now if the additional classes should be generated.

The plugin is providing the option to customize the names used for the Dataset Model classes.

The BusinessEntityDesigner itself provides three static properties that allow customization of the standard names used for Business Entities (used by the Consultingwerk.BusinessEntityDesigner.Plugins.CustomServices.CustomBusinessEntityNameHandler class):

    /**
     * Purpose: Allows to define the name suffix for the BusinessEntity classes
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixBusinessEntity AS CHARACTER NO-UNDO INITIAL "BusinessEntity":U
    GET.
    SET.

    /**
     * Purpose: Allows to define the name suffix for the DataAccess classes
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixDataAccess AS CHARACTER NO-UNDO INITIAL "DataAccess":U
    GET.
    SET.

    /**
     * Purpose: Allows to define the name suffix for the DataAccess classes
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixDatasetController AS CHARACTER NO-UNDO INITIAL "DatasetController":U
    GET.
    SET.

The BusinessTaskGenerator provides the following new static properties to customize the naming:

    /**
     * Purpose: Defines the Name Suffix for the Business Entity Business task class
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixBusinessTask AS CHARACTER NO-UNDO INITIAL "BusinessTask":U
    GET.
    SET.

    /**
     * Purpose: Defines the Name Suffix for the Dataset Model class
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixDatasetModel AS CHARACTER NO-UNDO INITIAL "DatasetModel":U
    GET.
    SET.

    /**
     * Purpose: Defines the Name Suffix for the Table Model class
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixTableModel AS CHARACTER NO-UNDO INITIAL "BusinessTaskTableModel":U
    GET.
    SET.

    /**
     * Purpose: Defines the Name Suffix for the Table Model class
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixTableModelFilter AS CHARACTER NO-UNDO INITIAL "BusinessTaskTableModelFilter":U
    GET.
    SET.

    /**
     * Purpose: Defines the Name Suffix for the Table Model class
     * Notes:
     */
    DEFINE PUBLIC STATIC PROPERTY SuffixTableModelSort AS CHARACTER NO-UNDO INITIAL "BusinessTaskTableModelSort":U
    GET.
    SET.

SCL-3842 Support verify-connection-allowed.p of setup.xml with different DB than SmartDB

Description:

The Setup/Install/Support/verify-connection-allowed.p procedure of the SmartDB Setup and migration utility now supports a custom name for the database.

SCL-3843 Simplify customization of the GUI for .NET Rendering Form

Description:

The DynamicForm base class required for Form rendering is always realizing a Ribbon component. This may not be desired in all cases.

Due to dependencies between the form client logic classes on the DynamicForm class itself it was not trivial to design a form without a Ribbon. We are now treating the DynamicForm itself as a pseudo abstract base class (the Visual Designer does not support real abstract base classes).

As new Form DynamicFormWithRibbon has been implemented that is used as the new default rendering form for all MetaForm masters and this now add the Ribbon.

Customers can now build custom forms inheriting from the DynamicForm class that do no longer need to use the Infragistics Ribbon.

SCL-3846 Added repository rendering support for SmartBusinessEntityAdapter CustomContext and SaveChangesParameter

Description:

The MetaDataSource now supports rendering of the CustomContext and SaveChangesParameter in GUI for .NET forms. Both attributes are CHARACTER values and in case of the SaveChangesParameter, this value is provided in a CharacterHolder instance as the SaveChangesParameter is an object reference.

SCL-3847 Added CustomContext attribute to MetaControlGroup

Description:

The rendering of the MetaControlGroup in the GUI for .NET Repository now supports the CustomContext attribute. This attribute can be queried from custom logic in the control group to distinguish different use cases for the component.

SCL-3848 Solve issues with too many restricted tokens in session context

Description:

A customer has defined a very large number of security tokens and users with a large number of restricted tokens were seeing errors from GetRestrictedTokens in the AuthorizatinClientService indicating that SUBSTITUTE with CHARACTER values exceeded the maximum size for CHARACTER variables:

Kein Stackplatz mehr für Bearbeitung von SUBSTITUTE. (2922)"

To resolve the issue, the Restricted Tokens are now returned as a LONGCHAR value and stored as a CLOB field in the context dataset.