/
Release Notes 2025-02-27

Release Notes 2025-02-27

Version Information

OpenEdge Release

Version Information

OpenEdge Release

Version Information

11.7.21, 12.2.13, 12.8.4, 12.8.5, 12.8.6

Release 11.7 #84321@2025-02-27

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.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-4019 FIxed IndexOutOfBoundsException error in Proparse toStringSourceText()

Description:

When using the toStringSourceText() method to regenerate the ABL source code from the proparse tree, nested preprocessor conditions might have caused the IndexOutOfBoundsException. This issue is resolved now.

SCL-4668 Fixed confusing error message when Web Lookup Rendering fails due to invalid LookupControls

Description:

Previously when rendering lookups with invalid LookupControl names in viewers to Angular JSON markup, the error message “Invalid poQuestions reference.” was raised. We have replaced this with the actual error message, indicating which control reference is invalid.

SCL-4714 SchedulerRuntime now setting Active Flag while running

Description:

The runtime of the scheduler now sets the SchedulerRuntime:Active flag while executing the scheduler. This allows business logic to detect it it’s running within the scheduler.

SCL-4722 ClassHelperBusinessEntity ClassNamesInPath named query returned empty list on subsequent runs

Description:

We have resolved an issue where the ClassNamesInPath named query of the ClassHelperBusinessEntity returned an empty list of class names on subsequence runs.

SCL-4726 Fixed issue: SchedulerJobStatus cannot update record because it is NO-LOCK

Description:

We have resolved an issue in the scheduler runtime that could cause teh SmartSchedulerJobStatus record not to be updated due to a NO-LOCK status.

Improvement

SCL-4502 JsonSerializable now supports to set a serialize-name for serializable properties and enum member names

Description:

* It is now possible to define a @SerializableProperty annotation with a serialize-name attribute for a property. This serialize-name is read during serialization and deserialization of JsonSerializable objects.
* It is now also possible to define serialize-names for enum members. The @EnumMapping annotation can be used on an enum class to define a memberName and mappedDataValue for individual enum members. These are picked up during serialization and deserialization of JsonSerializable objects as well.
* Both of these require .annotations-files generated via the ClassAnnotationParser.

SCL-4531 Telemetry Toolkit: Tracking of additional data

Description:

The Telemetry Toolkit now tracks additional data for every AppServer request:

* prepareQuery from the DataAccess class
* the httpStatus returned by a request to the SmartWebHandler derived web handlers
* the rest address by calls into @RestAddress or @RestMethod requests to the RestEntitiesWebHandler

SCL-4534 Simplified adding Splitter, TabFolder, DefaultToolbar etc. to a Form or ControlGroup layout

Description:

We have now simplified the adding of standard form level components (e.g. Splitter, TabFolder, DefaultToolbar, …) in the Object Master Designer. The designer now shows buttons that when clicked will add an instance of the matching type.

Developers can extend the list of default instances by referencing files similar to the form-default-components.json from the .applicationsettings file.

SCL-4535 SmartFilter support for value lists

Description:

The SmartFilter in GUI for .NET now supports rendering value lists for fields. The rendering is based on the following additional attributes:

* FilterFieldsAlternativeControlTypes: Currently supports rendering filter fields as combo or combo-box - but without providing any values to the UltraComboEditor (that is expected right now via Client Side Code)

New: Alternatively support
“lookup” for lookup text/value
“lookupkey” or “lookupkeyvalue” for lookup with keyvalue (e.g. GUID)
“valuelist” or “valuelistkey” for valuelist item key
“valuelistdescription” for valuelist description
* FilterFieldsAlternativeControlNames: comma delimited list of value list or lookup (repository)

Sample:

* FilterFieldsAlternativeControlTypes: Name=combo,Salesrep=lookup,country=lookup,City=ValueList
* FilterFieldsAlternativeControlNames: ,SalesrepLookup,CountryLookup,CityValueList

SCL-4552 The UiControl class now has UiActions to execute a RetrieveData call on a data-source

Description:

It is now possible to issue a RetrieveData call on a data-source from a server-side event handler via the UiControl class by adding an OpenQueryUiAction to the UiControls UiActions list.

SCL-4606 JsonHelper:GetJsonObjectByPath now supports proper JSON path

Description:

We have added methods to the JsonHelper to parse more standard JSON path expressions like

paths["/applications/{AppName}/webapps/{WebAppName}/transports/apsv/properties"].get.responses["200"]

When processing a Swagger document for instance, this will avoids to mask the / with ~~/

Goal was to implement retrieval of JSON Objects, Array, String, Decimal (number), Boolean Values following https://en.wikipedia.org/wiki/JSONPath and the sample above.

We have NOT implemented any handling of selection of multiple values like this

The expression $.store.book[*].price extracts the prices of books: 8.95 and 22.99 (since [*] selects all the nodes of an array).

The expression $..price extracts all the prices: 8.95, 22.99, and 399.

New method names:

JsonHelper:GetJsonObjectBy*Json*Path (poJsonObject, pcPath, ArrayBaseEnum)

JsonHelper:GetJsonArrayBy*Json*Path (poJsonObject, pcPath, ArrayBaseEnum)

JsonHelper:GetCharacterBy*Json*Path (poJsonObject, pcPath, ArrayBaseEnum)

JsonHelper:GetDecimalBy*Json*Path (poJsonObject, pcPath, ArrayBaseEnum)

JsonHelper:GetLogicalBy*Json*Path (poJsonObject, pcPath, ArrayBaseEnum)

SCL-4675 New Business Entity Designer Plugin to build ValueObjects for primary unique key values

Description:

The Consultingwerk.BusinessEntityDesigner.Plugins.KeyValueObjectPlugin now supports the generation of value objects based on the primary unqiue key of tables of business entities.

In the future we will support to use those values to fetch records from the database models and to distinguish various key field combinations with identical data-types due to the usage of meaningful strong types.

SCL-4718 Support for translation ABL formats with "<" behind the decimal point into Infragistics Input Masks

Description:

The FormatHelper now handles trailing ‘<' in decimal formats like trailing ‘9’. This leads to an InputMask that fills values with fewer digits to be filled with '0’ and thus preserves the position of the decimal seperator.

SCL-4723 Implemented support for rendering Lookup Bound fields in the Angular grid

Description:

We have implemented support for rendering bound field information for lookup bound fields in the Angular grid JSON markup.

SCL-4725 SmartWebHandler now exports Session Info details of Exceptions only once

Description:

The SmartWebErrorHandler now reports the SessionInfo structure of Consultingwerk Exceptions only once and now repeatedly in case of nested exceptions (InnerError pattern).

SCL-4727 Allowin developer to use data from SetServiceRequest for Key value in Telemetry data

Description:

The Key value of the telemetry data is generally determined using the service interface but if the service interface is one of a predefined list of service interfaces and the service request and service name are set using the SetServiceRequest method, then the key for the request is calculated from those values.

For the standalone Telemetry use-case, where SmartComponent Library service interfaces are not in use, we now allow developers to set the key value programmatically.

SCL-4734 DatasetModel:SaveChanges now raises an error, when tracking-changes = false

Description:

The DatasetModel:SaveChanges method now raises an error when TrackingChanges has not been set to TRUE before. Before that change, basically programming mistakes remained undiscovered.

SCL-4736 Telemetry service: pending request filename on Classic AppServer no longer contains /

Description:

We now ensure that the file name of the pending request JSON files generated by the Telemetry toolkit does not longer contain invalid characters such as “/” when used with the classic AppServer.

New Feature

SCL-4415 Implemented the ability to identify SmartSchedulerJobStatus records by an indexed identifier

Description:

We have added a new field SchedulerJobStatusId to the SmartSchedulerJobStatus table that allows developer to use a custom identifier to link scheduler entries to application data etc.. The API’s to schedule jobs now support this optional parameter.

SCL-4711 Telemetry Toolkit - improved "key" for simple procedure file

Description:

We have now improved how the “Key” attribute in the Telemetry output is calculated for simple procedure files executed from the client. Previously a call to orders.p was reported as “ord.p”. Now the full procedure name will be reported.

Task

SCL-4712 Implemented support for JSON rendering labels for Smart Grid edit buttons

Description:

We have now implemented JSON rendering support for the labels of the Edit buttons in an Angular grid.

SCL-4713 Implemented support for JSON rendering of Smart Filter operator labels

Description:

We are now rendering the Labels of the filter fields of the SmartFilter in the JSON layout for our Angular user interface.

 

 

    

Related content