Version Information

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:

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-3152 Changes on Layout Position did not trigger the update state in the Object Master Maintenance

Description:

When changing the Layout position of an object instance in a Form using the drop down dialog, the update state of the object instance viewer was not enabled.
This annoyance is now resolved.

SCL-3153 Updated (c) date in Trial Copy message

Description:

We have updated the (c) date in the trial copy message written to the AppServer logfile after the AppServer has been started.

SCL-3156 Fixed an issue with the Swagger JSON generation for Dynamic Business Entities

Description:

We have resolved an issue with generating the JSON SwaggerFile when the backend was exposing dynamic Business Entities as RESTful endpoints.
The feature is now working as expected.

SCL-3158 Links tab - Target/Source Page fields did not update after the Instance Page field has been changed in Object Master Maintenance

Description:

When an object instance has been moved from one page to another, the page information related to this instance has not been updated in the grid on the links tab.
This annoyance has been fixed now.

Improvement

SCL-3124 Completed support for EXTENT fields in JsonSerializable

Description:

We have completed the support for EXTENT fields in JsonSerializable types. Previously only CHARACTER and INTEGER EXTENT fields have been supported. Now support has been added for all ABL data types.

SCL-3154 Added images per Component Type to the repository master container designer preview

Description:

The Repository Container designer/preview now displays an image representing the type of the component on the preview.

SCL-3157 RESTful Entities: Added support for dynamic query string parameters in links

Description:

RESTful Entities now also support rendering query strings for variable links based on field values from the current record, e.g.:

@RestAddress (type="record", address="/Customers/~{CustNum}", tables="eCustomer,eSalesrep", id="CustNum",
              fields="eCustomer.*,eSalesrep.RepName,eSalesrep.Region", canRead="true", canUpdate="true", canDelete="true",
              childAddresses="eSalesrep:/Salesreps/~{SalesRep}",
              links="orders:/Customers/~{CustNum}/Orders,openOrders:/Orders?custnum=~{CustNum}&&orderstatus=open,salesrep:/Salesreps/~{SalesRep}").

SCL-3160 GUI Rendering Support for MetaCombo's DropDownStyle property

Description:

We have now implemented GUI rendering for the DropDownStyle property of the MetaComboBox and MetaBusinessEntityComboBox repository classes.

SCL-3168 Repository Object Maintenance now supports Drag & Drop of Object Master and Instance Name

Description:

The Repository Object Maintenance form now supports text drag and drop from the object master name and object instance name field in the viewers used in the form.
Drag and drop is enabled when the viewer is not in update mode. Drag and drop works from the form to text editors supporting text drag and drop such as the Progress Developer Studio editor. The feature is useful when implementing client side logic (ABL or JavaScript) that needs to reference object master or instance names.

New Feature

SCL-3070 Scenario Runner is now capable of assigning values to Static properties

Description:

Scenario based unit tests now support assigning values to static properties. This allows to set configuration variables with values specific to a test scenario. When executing these scenario tests, the current values of the static properties are backed up and restored after the test execution.
Example JSON configuration for static properties within a .scenario file:

 "StaticProperties":  {
        "Consultingwerk.OeraTests.SCL3070.TestClass:TestIntegerProperty": 42,
        "Consultingwerk.OeraTests.SCL3070.TestClass:TestLogicalProperty": false,
        "Consultingwerk.OeraTests.SCL3070.TestClass:TestCharacterProperty": "Hello World"
    }

SCL-3136 Progress Dynamics related tooling now moved to separate package/project

Description:

The tooling and supporting API's in the SmartComponent Library providing specific functionality for the Progress Dynamics framework has been moved to a separare package.
Customers interested in using the SmartComponent Library for migrating from Progress Dynamics or using the SmartComponent Library in combination with Progress Dynamics should contact us to receive access to this optional package.

SCL-3150 Implemented JSON Rendering support for Smart Combo Editor allowFilter

Description:

We have implemented JSON Rendering support for the SmartComponent Libraries Angular implementation of the SmartComboEditor components allowFilter attribute.
In the SmartFramework repository we're using the DropDownStyle property known from GUI for .NET to control this behavior.

Task

SCL-3151 Implemented JSON Rendering Support for Smart Grid resizable Setting

Description:

Based on the AllowColSizing property in the Repository we're not rendering the resibable attribute of the SmartComponent Library grid component for Angular.

SCL-3167 Added LRU button to OpenObjectMaster Dialog

Description:

We have added a button with the LRU items of the Object Master Form to the Open Object Master Dialog. This simplifies opening previously edited object masters when starting the maintenance form and the open object master dialog is shown by default.