Version Information

OpenEdge Release	Version Information
11.7.17, 12.2, 12.7, 12.8, 12.8.3	Release 11.7 #81697@2024-09-01

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

OpenEdge 12.8 support!

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.

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.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.

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.

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-4576 Fixed compile errors in SmartComponentLibrary_11.7_81446_upgrade_no_smartframework_utf8

Description:

We have resolved compile errors in the SmartComponent Library releases without the SmartFramework packages.

SCL-4588 Resolve data conflict with "Placeholder" attribute Build.One

Description:

With the introduction of the new template-engine we have caused a conflict in the name of the “placeholder” attribute used by the Build.One platform.

We have now renamed our attribute to “PlaceholderComponent”.

Improvement

SCL-4459 LookupWebRendering now provides LookupQueryString and LookupDialogQueryString

Description:

The Angular LookupWebRendering now supports distinct rendering for the LookupQueryString and the LookupDialogQueryString attributes.

SCL-4460 New Form that allows to search for object masters based on attribute values

Description:

We have implemented a new Form that supports searching for Repository Object masters or instances based on attribute values.

SCL-4565 CefSharp updated to 127

Description:

The address 3 critical CVE’s we have upgraded CefSharp to version 127, see https://chromereleases.googleblog.com/2024/07/stable-channel-update-for-desktop_30.html for details.

SCL-4574 Improved handling of messages with no MessageType

Description:

When messages with no defined MessageType are retrieved from the SmartMessageProvider we’re no longer raising an exception.

SCL-4575 Added "ControlGroup" to Repository Objects menu

Description:

We have added the MetaControlGroup type to the “Repository Objects” menu structure.

SCL-4577 Using SmartRepositoryService methods to retrieve Attribute Data Type

Description:

We have improved the performance when rendering repository based forms by using consistently using the SmartRepositoryService*s API to retrieve the data type of attributes.

SCL-4580 Ability to disable CefSharp debug.log

Description:

We now support the configuration of the logging severity and the location of the logfile used by CefSharp using the .applicationsettings file. See https://github.com/cefsharp/CefSharp/discussions/4121 for details.

    "WebBrowser":
    {
        "CachePath": "@{LocalApplicationData}\\CefCache",
        "LogSeverity": "error",
        "LogFile": "c:\\temp\\cefsharp-debug.log"
    }

SCL-4583 SmartRelationBusinessEntity now validates relation field pairs

Description:

The SmartRelationBusinessEntity now validates the relation field pairs when saving data.

SCL-4585 Introduced Interface for SmartLookup's PerformLookupIfActive method

Description:

We have introduced the new interface Consultingwerk.SmartComponents.Interfaces.ISupportsPerformLookupIfActive to improve the SmartViewers and SmartUpdatableBrowsers ability to finalize custom controls like the SmartLookup pending user actions while the viewer or grid is saving data.

SCL-4587 Improved initialization of the Class Annatation Parser Job

Description:

We have improved the runtime of the initialization of the Class Annotation Parser job. The job now completes in a fraction of the previous runtime.

New Feature

SCL-4488 TableModel FillByKeyTable now supports UseDedicatedBusinessEntity

Description:

The FillByKeyTable feature of the TableModel now honors the UseDedicatedBusinessEntity setting.

SCL-4582 Implemented Tab-Folder security in rendered Forms

Description:

Tab pages defined in repository based forms can be defined with a security token, when set, we have now implemented the check for that token while the form is loaded and will disable the tab page, when the user has no access.

SCL-4586 ComplexInputSmartBusinessEntityLookupControl now performs the Lookup when clicking the OK button of the InputPromptDialog

Description:

The ComplexInputPrompt dialog now calls into the PerformLookupIfActive method of ComplexInputSmartBusinessEntityLookupControl instances to ensure the lookup fetches data before returning the value object to the caller.

Story

SCL-4537 Google maps based component

Description:

We have implemented a user control based on the CefSharp web browser that embed google map into a GUI for .NET application. The Consultingwerk.Windows.CefBrowser.MapsControl.GoogleMapsControl supports data-binding using a SmartDataSource property.

The component supports binding to 2 fields providing latitude or longitude or multiple fields providing an address.

Sub-task

SCL-3521 Implemented support for GetInitialValues to SmartBusinessEntityAdapter / SmartDatasetChildAdapter

Description:

The SmartBusinessEntityAdapter and SmartDatasetChildAdapter now also support automatic calling into the Businses Entities GetInitialValues method when

a record is created. The feature is enabled by the GetInitialValues attribute of the BusinessEntityTable annotation.

@BusinessEntityTable (name="eOrderLine", MandatoryColumns="Ordernum,Linenum", ReadOnlyColumns="Ordernum", GetInitialValues="true") .

SCL-4158 Implemented support for GetInitialValues for Angular DataSource

Description:

We have implemented Angular rendering support the getInitialValues attribute of the Angular data-source component.

Task

SCL-4578 Including layout type in Smart Viewer and Smart Frame JSON rendering

Description:

We’re now including an attribute for a SmartViewers or SmartFrames layout to in the Angular markup when rendering repository based forms.