Version Information

OpenEdge Release	Version Information
11.7.4, 11.7.5, 11.7.6, 12.1, 12.2	Release 11.7 #59498@2020-06-09

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.

OpenEdge 12.1 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.1. We hereby declare OpenEdge 12.1 fully supported for the SmartComponent Library as of the release of September 21st 2019.

OpenEdge 11.7.6 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 11.7.6. We hereby declare OpenEdge 11.7.6 fully supported for the SmartComponent Library as of the release of June 9th 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!

Announcing the SmartFramework ERD Designer

We are announcing the availability of the SmartFramework ERD Designer

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-3050 Fix ** FIND FIRST/LAST failed for table ttTranslationCache. (565)

Description:

Some customers have seen this error returned to the client when a Business Entity was using the Translation Provider.
We are now clearing the error status in the Translation Provider before returning to the caller after failed attempts to locate records in the Translation Provider internal cache temp-tables.

SCL-3060 Fixed issue with the "New Business Entity Wizard" in Legacy Browse Migration Form

Description:

We have fixed an issue where the "New Business Entity Wizard" in the Legacy Browse Migration Form did not respect field mapping (e.g. replacing hyphens in field names) when creating fields for the primary unique key.

SCL-3065 Implemented Backend support for unbound fields in Angular UI

Description:

We have implemented rendering support for the "Unbound" attribute of fields in Angular viewers. The Unbound attribute is optional and can be set for components that should not be data-bound to fields from the JSDO Data Source.

Improvement

SCL-2984 Implemented Auto-Layout Feature for Business Entity Designer

Description:

We have implemented an Auto-Layout function for the Business Entity Designer. The function can be invoked from a Button in the Business Entity Designer Ribbon.
The following Assembly references have changed to support this feature:

<assembly name="Consultingwerk.Support, Version=4.2.0.59263, Culture=neutral, PublicKeyToken=10603cb31df311b3"/>
<assembly name="Crainiate.Diagramming, Version=5.0.1.59263, Culture=neutral, PublicKeyToken=10603cb31df311b3"/>
<assembly name="Crainiate.Diagramming.Forms, Version=5.0.1.59263, Culture=neutral, PublicKeyToken=10603cb31df311b3"/>

SCL-3047 Removed access to Property MonitorDropDownBehavior of ultraToolbarsManager

Description:

We have removed access to the MonitorDropDownBehavior property of Infragistics UltraToolbarsManager. This property is not used by our code, however the Progress Developer Studio visual designer seems to be adding this to some forms with a default value.
The property is not available in the UltraControls version Progress ships with OpenEdge 11.7.2 so that was is causing issues for some customers.

SCL-3048 Improved error handling during calling to GET-DB-CLIENT

Description:

To improve debugging of issues with an incorrect (or not connected) authenticationDb setting in the .applicationsettings or .restapplicationsettings file we have now implemented a GetDbClient method in the DatabaseHelper. Like the SetDbClient method it provides clear error messages about which database name caused the GetDbClient to fail.

SCL-3049 Fixed issue with invalid repository type in attribute definition

Description:

Customers might have seen this error message in the Repository Viewer or Grid Designer:

The parameter value "" for pcDataType in Consultingwerk.Util.DataTypeHelper is invalid.

Call Stack: 
ToSystemType Consultingwerk.Util.DataTypeHelper at line 1549
DisplayProperties Consultingwerk.Windows.Framework.Repository.Object.SmartPropertyGridControl at line 129
...

We have improved the error message to include details about the property causing this issue. We have also corrected the definition of a single property in the repository causing this issue.

SCL-3051 SmartDynamicFilterControl:OnLoad now catches errors before thrown to .NET

Description:

Customers have reported .NET Exceptions when loading the SmartFilter control.
!2020-05-28_15h52_14.png|thumbnail!
To improve debugging we are now handling errors raised during the control initialization before they are thrown to the .NET side.

SCL-3052 Improved error messages when toolbar definition files (JSON) are not available

Description:

We have improved the error messages raised when the toolbar definition files (JSON) are not available, e.g. as a result to references to our demo file in the default .applicationsettings or .restapplicationsettings files.
Previously a message from the JSON Object Model Parser was shown. Now we raise a clear error message including the invalid file name.

SCL-3053 Responsive rendering of Angular viewers failed when there is only a single component directly parented in the viewer

Description:

We have resolved an issue in the rendering of responsive viewers for the Angular UI.
The issue occurred when there was only a single component (e.g. GroupBox) directly contained in the viewer. The result was an empty viewer JSON markup.

SCL-3056 Implemented support for translations to authorization error messages

Description:

We have now implemented support for translations on the error messages raised by the Service Interface when the Request Authorization Provider indicates that the user is not authorized for the current request.
The error message can now be localized using the SFR 210 error message.

SCL-3057 Legacy GUI Migration now suggests short .w file name when creating repository objects

Description:

Legacy GUI Migration now suggests the short name of the .w file as the name for the repository object when creating a viewer or browser in the Repository.

SCL-3058 Angular viewer rendering: Random label was repeated for field with no Label

Description:

We have resolved an issue in rendering Angular Viewers. Like in this example components with no label, like the one button on this screenshot have had the label or a (more or less) random other field inherited.
This issue is resolved now.
!screenshot-1.png|thumbnail!

SCL-3059 Added support for custom style attributes for Angular group-box rendering

Description:

We have now implemented support for rendering custom style attributes for GroupBox components in Angular Viewers.

SCL-3063 Studio Desktop now remembers most recently launched tool

Description:

The SmartComponent Library Studio Desktop now remembers the most recently launched tool and repositions to this tool when starting.

Task

SCL-3064 Implemented a helper class to simplify formbased authentication from the ABL http client

Description:

We have implemented a new helper class that supports performing a form based login when using the ABL http client to perform (REST) requests to a PASOE instance secured by the form based login model.
The Consultingwerk.Framework. http .FormBasedLoginHelper class provides methods that perform the login an return the JSESSIONID Cookie instance required for actual calls to the PASOE backend.