Version Information

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

OpenEdge 12.3 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.3. We hereby declare OpenEdge 12.3 fully supported for the SmartComponent Library as of the release of  November 24th 2020.

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? 

...

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

...

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: 

...

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: 

...

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:

...

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:

...

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

...

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

• Support for RESTful invocation of Business Task and Business Entity Methods
• Invalid Proparse code-page setting corrupts temp-table field labels during "Refresh from Include"
• Generic Factory Service
• Using Invokable Business Entity Methods with Dataset Model Classes
• Using the Business Entity method FetchDataByKeyTable
• PASOE management scripts
• Business Entity Designer Launcher
• Searching data using ROWID's within the SmartBusinessEntityAdapter
• Business Entity Count Method
• SmartFramework ERD Designer
• Changes to the SmartDB and SmartDB upgrade and migration utility
• How to implement dynamic initial values
• How do I control the amount of details provided for error messages caused by our web handler
• Using custom log entry types
• Strong-typed Query Support
• Swagger REST API Documentation for RESTful Services
• Swagger REST API Documention for JSDO Generic Service
• Scaffolding utility for common helper classes
• RESTful services
• JSON Configuration File Format
• Common Component Specification (CCS)

Download Link

http://esd.consultingwerkcloud.com/

https://github.com/consultingwerk/SmartComponentLibrary

Overview of included tickets

Bug

SCL-3742 Exporting of smartrepo files from GUI thin client failed with Database smartdb not connected

Description:

We have fixed an issue that arose when trying to export smartrepo files in a thin-client configuration.

SCL-3743 Checking for VALID-OBJECT (poBindingSource) in field rendering routines

Description:

We’re have now extended the various field rendering services of the GUI for .NET rendering engine to check the validity of the BindingSource before Adding data-bindings. This resolves issues when using the fields on viewers not bound to a MetaDataSource instance.

SCL-3745 Fixed file access issue when saving Business Entity Design twice with only a short break

Description:

The SaveImagePlugin of the Business Entity Designer was causing a file access issue like this

“System.IO.IOException: The process cannot access the file 'C:\Work_Training\Training\Training\Order\OrderBusinessEntity.png' because it is being used by another process.”

when clicking the Save button of the Business Entity Designer twice with only a very short break in between. The issue was caused by not properly closing the .NET output stream used to write the image file and thus relying on the asynchronous operation of the garbage collector to clean up the file handle.

SCL-3746 Adding height to Group Box when rendering viewer for the web with absolute positioning

Description:

We’re now adding the height to group boxes rendered to the Angular UI when group boxes are placed on a viewer with absolute positioning.

SCL-3747 System.NullReferenceException: "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt." when clicking on Table header

Description:

We’ve resolved a NullReferenceException in the BusinessEntity Designer. The exception was raised when the tool is in the “Add Relation” mode and the user just clicked on a table header without moving the mouse pointer for a drag and drop operation.

SCL-3754 Resolved issue when generating a new Business Entity and adding a second table

Description:

When generating a new Business Entity from the ABL Frame legacy migration tool and adding a second table to the business entity in the same session an error was raised because the BusinessEntityDatasetController was loaded without a SmartBusinessEntityAdapter instance. This issue is now fixed.

Improvement

SCL-3675 Improve GET access to TableModel field properties (DatasetModel)

Description:

We have improved the performance of the GET access to the field properties of the TableModel implementations of the DatasetModel by moving some of the GET implementation into an include file ({Consultingwerk/OERA/GetFieldProperty.i) which is referenced in the property GETter. Previously the property GETter was calling into a method of the base class causing a slight runtime overhead.

To leverage the improvements developers will have to regenerate the Business Entity and the DatasetModel.

SCL-3748 Ensuring BufferedReader is always closed in ListingParser

Description:

We’re now ensuring that the BufferedReader instance is always closed in Proparse’s ListingParser. Previously the Reader might have remained opened when an error has been raised during parsing of the file.

SCL-3753 Added buttons to open file in PDSOE or VS Code to Legacy GUI Migration

Description:

We have added buttons to open the selected file in Progress Developer Studio or VS Code to the Legacy GUI MIgration tools (frame and browse).

SCL-3755 Setting MetaViewer size when converting static FRAME into repository viewer

Description:

We’re now setting the size (Height and Width) of the MetaViewer object master when converting an ABL FRAME into a repository viewer.

New Feature

SCL-3752 Implement "Add to existing Business Entity" to ABL GUI Frame migration

Description:

We have added the capability to add the temp-table matching an ABL frame to an existing business entity to the ABL GUI Frame migration utility.

Sub-task

SCL-3729 Modified GenericList.cls or GenericList.i to use a native list

Description:

Progress released support for generic lists in OpenEdge Release 12.5. This includes various interfaces, classes and iterators that use a new generic OOABL syntax (eg {{List<T>}} ). These are in the Progress.Collections namespace. These collections provide meaningful performance benefits to applications using Consultingwerk’s GenericList collection.

The Progress List<T> collection and related clases cannot be extended (or implemented) by ABL application code. To maintain support with existing lists, the Consultingwerk.Framework.Base.GenericList class and the Consultingwerk.Framework.Base.GenericList.i include replace the array-based internal structures with an instance of Progress.Collections.List<T>, where T is the type passed as an argument to the include. This may be called a wrapped approach. In the SmartCompoentLibrary the new Progress lists are called “native lists”.

The feature is enabled by adding the {{NativeLists}} preprocessor definition in Consultingwerk/products.i (see Consultingwerk/products.i.template) .

&IF 1=0 &THEN
/* Peter Judge, Consultingwerk Ltd. 28.08.2022
   SCL-3604: Support for native Lists from OpenEdge 12.5+ */
&ENDIF
&IF INTEGER(ENTRY(1, PROVERSION, '.')) GT 12 OR (INTEGER(ENTRY(1, PROVERSION, '.')) EQ 12 AND INTEGER(ENTRY(2, PROVERSION, '.')) GE 5) &THEN
&GLOBAL-DEFINE NativeLists NativeLists
&ELSE
&GLOBAL-DEFINE NoNativeLists NoNativeLists
&ENDIF

This feature is all-or-nothing: either all generic lists use the Progress List, or none do. Lists that do not use the Consultingwerk GenericList feature are not affected by this change.

Implementation requirements

Lists that would like to use this feature

* must include Consultingwerk/products.i before the {{CLASS}} block
* must be ABL serializable, using the {{SERIALIZABLE}} keyword in the {{CLASS}} definition
* must (continue to) inherit from Consultingwerk.Framework.Base.GenericList .

Enumerator

The existing Consultingwerk/foreachABL.i approach continues to work, without any changes to application code required.

A new include named Consultingwerk/foreachGeneric.i is provided that uses the Progress iterator (enumerator). It is recommended that, when using native lists, to use this new include to iterate over the items in the List.

The arguments for this include are identical to those used for the standard {{foreachABL.i}} include. In order to use this include, the class MUST include Consultingwerk/products.i before the {{CLASS}} block.

For example

/* Consultingwerk.OERA.RestResource.RestResourceService */
{Consultingwerk/foreachGeneric.i IRestMethod oMethod in poRestMethods}
    THIS-OBJECT:RegisterBusinessTaskRestMethod (oMethod) .
END.

Other changes

The Consultingwerk implementation of generic lists have moved from Consultingwerk.Framework.Base.GenericList.i into Consultingwerk/Framework/Base/GenericNativeList.i . The code in this include is protected by the same {{NativeLists}} preprocessor used to enable the native lists feature elsewhere.

Task

SCL-3744 Updated SmartComponent Library branding

Description:

We have updated the branding of the SmartComponent Library developer tools. This update includes the usage of the most recent product logos.

SCL-3750 Ignoring rectangles when generating Business Entity from Viewer Design

Description:

We’re now ignoring RECTANGLE widgets when generating a Business Entity from a frame layout in the Legacy ABL GUI Migration tool.

SCL-3751 Frame Migration tool generated second field for CustNum in Business Entity

Description:

The Legacy ABL GUI frame migration tool was generating an additional instance of the primary unique key field when generating temp-tables with a joined data-source. This has been resolved now.