Version Information

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? 

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:

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

• 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-3330 FIxed issue resolving class names for Rest Resources when r-code is located in a PL file

Description:

We have fixed another issue that was causing problems parsing annotations for Business Entities and Business Tasks located in a PL file.

SCL-3333 Fixed issue where the Swagger file for RESTful Entities was showing the actual method name instead of URL

Description:

We have resolved an issue with the URL of invokable methods in the Swagger file. This was under certain conditions shown based on the actual method name and not the URL defined for the method. Result was that Swagger failed issuing the call to those methods correctly. This issue is resolved now.

SCL-3337 SmartDynamicFilter failed to render optional filter fields when two fields had the same label

Description:

We have resolved an issue with the SmartDynamicFilter control. The control was failing to render optional fields, when two or more field had the same label defined.
The issue is now resolved.

Improvement

SCL-3281 Improved FrameParser for Widgets without explicit positions

Description:

WE have improved the FrameParser class for ABL FRAME definitions without explicit positions given for widgets/fields.

SCL-3315 Added optional parameter for compare mode to BufferHelper:CompareBuffer method

Description:

WE have not implemented the ability to control if the BufferHelper:CompareBuffer method uses the field's STRING-VALUE or BUFFER-VALUE. The comparison using the STRING-VALUE remains the default, as this was the previous behavior.

/**
 * Purpose: Compare to records field by field and returns
 *          the list of different fields, performs case-sensitive comparison of
 *          character and clob fields. Provides the option of comparing the
 *          BUFFER-VALUE instead of STRING-VALUE
 * Notes:   Only processes fields that are on both buffers
 * @param phBuffer1 The handle of the first buffer
 * @param phBuffer2 The handle of the second buffer
 * @param poCompareMode The compare mode of the method, StringValue or BufferValue. CLOB fields will always be compared using the BUFFER-VALUE
 * @return Comma delimited list of field names with differences
 */
METHOD PUBLIC STATIC CHARACTER BufferCompare (phBuffer1 AS HANDLE,
                                              phBuffer2 AS HANDLE,
                                              poCompareMode AS BufferCompareModeEnum):

SCL-3334 Implemented Support for FetchDataRequest's CustomContext in SmartComboEditor

Description:

We have implemented support for the FetchDataRequests's CustomContext property in the SmartComboEditor control. The Control now has a new Property that allows to set the CustomContext of the FetchDataRequest.

SCL-3335 Implemented support for the Responsive Orientation on Smart Split View

Description:

We have added to new attributes to the Split View component in the repository:
- ResponsiveOrientation-Horizontal
- ResponsiveOrientation-Vertical
Based on t-shirt sizes these attributes allow to control the responsive behavior of the split view component when rendered to the Angular UI.

SCL-3336 Fixed grouping behavior in the Repository property grid

Description:

When grouping for Property or Event in the repository properties grids, the group-by column has not been re-resolved when switching to a different component. This might have caused incorrect grouping shown in the grid.
This issue is resolved now.

SCL-3338 Added property to SmartHttpClient to allow suppressing of error handling

Description:

We have added a new property SuppressErrorHandling to the Smart[ HTTP Client| HTTP Client] that allows to control if error handling should be suppressed. When se to TRUE the Smart[ HTTP Client| HTTP Client] will return the response of an HTTP request to the caller also when it's status code is >= 400. When it's set to FALSE the Smart[ HTTP Client| HTTP Client] continues to throw errors to the caller.

SCL-3339 Message dialog for validate data-source query now has a green checkmark when Query is validated successfully

Description:

To improve the appearance the message dialog shown when a DATA-SOURCE query in the Business Entity Designer is validated successfully is shown with a green checkmark instead of the standard info icon.

SCL-3340 Enforce early initialization of DynamicBusinessEntityRepository

Description:

When services have been loaded in an incorrect order, the DynamicBusinessEntityRepository might have had to return the dynamic business entities before it has been initialized by the ServiceLoader.
This issue has been fixed. The method GetRestAddresses is now capable of forcing initialization of the service when needed.

Task

SCL-3305 Made methods PerformIntegrityCheck and DeleteOrphanRecord of SmartRepositoryIntegrityCheckTask JSDO callable

Description:

We have made the methods PerformIntegrityCheck and DeleteOrphanRecord of the SmartRepositoryIntegrityCheckTask invokable through the JSDO service interface. This is a preparation for implementing feature SFRBO-170.