Release Notes 2024-07-24
Version Information
OpenEdge Release | Version Information |
---|---|
11.7.17, 12.2, 12.7, 12.8, 12.8.3 | Release 11.7 #81212@2024-07-24 |
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.7 support!
We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.7. We hereby declare OpenEdge 12.7 fully supported for the SmartComponent Library as of the release of May 10th 2023.
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:
|
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 |
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-4457 UltraTreeColumnResizeHelper now resizing columns properly when double-clicking between two cells
Description:
We have resolved an issue in the Consultingwerk.Windows.Util.UltraTreeColumnResizeHelper class that was causing the component to only resize the columns in the current ColumnSet when resizing by double-clicking between two cells. Double-clicking between two cells behaves now like resizing columns by dragging the cell border.
SCL-4544 Fixed issue issue opening visual MetaGrid designer
Description:
We have fixed a minor regression causing an invalid handle error while opening the visual designer for MetaGrid object masters.
Improvement
SCL-3923 Implemented control if buttons are rendered in Desktop or Web
Description:
Toolbar/Ribbon Buttons defined in the ToolbarButtons instance property have been rendered on the web also when those buttons have not been defined in the JSON files with the button definitions. This behavior has changed. Buttons are not only rendered on Desktop or web when they are defined in the respective JSON files. This gives a developer now full control about which buttons are rendered to web and desktop.
SCL-4470 Implemented repository-defined server-side event handler to GUI for .NET
Description:
We have now implemented server-side event handler that are registered in the repository. Server side event handler are specified using the prefix “server:” followed by the backend handler class name, another colon and the method name.
Methods are expected to receive the dataset as an input-output parameter along with an instance of the Consultingwerk.CommonUi.EventHandlerParameter class.
The return value of the server-side event handler method is an instance of the Consultingwerk.CommonUi.UiControl class.
For lookups’s we’re supporting this on:
* AfterPerformLookup (after lookup performed a search because the user typed a value in the field)
* Leave
* LookupComplete (after the lookup dialog has returned a value)
* LookupKeyValueChanged
* Validating (Cancelable)
* ValueChanged
For Buttons:
* Click
For Combo, Field, Editor, Radioset:
* Leave
* Validating (Cancelable)
* ValueChanged
SCL-4510 Added support for combo-box list-items and list-item-pairs to UiControl
Description:
We have extended the UiControl return object of server-side event handler with support for setting list-items and list-item-pairs of combo-boxes.
SCL-4521 Integrated Angular WebApp into Repository Designer Tooling
Description:
The Repository Designer now supports launching the Angular Web Application in an integrated CefSharp web browser.
The feature requires a few settings in the .applicationsetting file:
* RepositoryDesigner.Plugins.0 : Consultingwerk.Windows.Framework.Repository.Object.GenerateLogicObjectPlugin
* RepositoryDesigner.Plugins.1 : Consultingwerk.Windows.Framework.Repository.AngularPreview.AngularPreviewSmartObjectMasterFormPlugin
* RepositoryDesigner.AngularPreview.WebAppUrl : Url of the Angular Web Application
SCL-4527 Security Assignment Verification now shows restricted/unrestricted for each user group
Description:
The Security Assignment Verification has been enhanced. The list of user groups now displays also if the requested security item is restricted or unrestricted for every user group of the user.
SCL-4532 Added "Add Page" items to pages combo in Repository Designer
Description:
We have added and “add page” item to the combo-box of pages in the repository designer object instances viewer. When this item is selected, the developer can add a new page to the form without switching to the Pages tab page.
SCL-4542 Added server-side event handler for viewer Initializing event
Description:
We have introduced a new Initializing event to the viewer that allows to call into a server-side event handler.
SCL-4545 Resolved unqualified references to Flags Enum
Description:
We have resolved unqualified references to the Flags Enum by added the Progress.Reflect package in the source code to prevent issues with compiling a customers application when the application database is connected.
SCL-4546 Package Browser dialog now allows to navigate to child-nodes when filtering
Description:
When filtering the package browser dialog, previously only allowed to navigated to the matching nodes and parent nodes. However if may also be desired or useful to navigate to child nodes.
SCL-4548 Server side event handler in Viewer when Data source current changed
Description:
When the SmartDataSource has a new record
* navigation to different record
* Add or Copy
* No record available
we are now able to call into a server side event handler. As part of the event args we provide the record status
* Available
* NotAvailable
* Add
* Copy
with the event args.
SCL-4549 Added Form name and Viewer name to event args of server-side event handler
Description:
We have added the names of the form and the viewer to the Event Args of a server-side event handler, allowing to react on the origin of an event in a server-side event handler.
New Feature
SCL-4234 FieldRenderer now processes the format phrase for all Data-Types
Description:
The field renderer now processes the Format phrase for all field data types. For CHARACTER fields the format phrase is translated into the MaxLength attribute of the UltraTextEditor.
SCL-4309 Updated CEF to latest for HighDPI support
Description:
We have updated the CefSharp libraries to version 126. This version does among other issues resolve HighDPI compatibility issues.
Task
SCL-4550 Providing formName in Smart Form JSON Layouts
Description:
As part of rendering Forms for the Angular UI, we’re now providing the Form name as part of the JSON layout.