OpenEdge Release | Version Information |
---|---|
11.3.3, 11.3.4, 11.4, 11.6.2, 11.6.3, 11.7, 11.7.1, 11.7.2, 11.7.3.007 | Release 11.3 #48227@2018-09-10 |
The previously reported issues with the Progress Developer Studio Visual Designer (Visual Designer related OpenEdge 11.7.3 product alert!!!) has been resolved by Progress Software with Hotfix 007 of OpenEdge 11.7.3. We hereby announce full compatibility of the SmartComponent Library with OpenEdge 11.7.3.007.
Besides the issue with the Visual Designer however, we habe not been aware of any incompatibilities with OpenEdge 11.7.3.
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!
We are announcing the availability of the SmartFramework ERD Designer
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.
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.
During our tests on OpenEdge 11.7.2 we have experienced two issues:
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
from Progress Software for in OpenEdge 11.7.2.001 we further recommend all customers to apply this hotfix as well.
We have updated proparse with further enhancements in this release (see https://github.com/consultingwerk/proparse/releases/tag/4.0.1.1176). 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 methods for refactoring purposes. The most recent code in the Consultingwerk.Studio package relies on those methods. It's therefore mandatory to update proparse to this version.
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.
This is an overview of the web handlers supported by this release
defaultHandler=OpenEdge.Web.CompatibilityHandler handler39=Consultingwerk.Web2.WebHandler.SmartFieldSecurityCheckWebHandler: /RestrictedFields/{TableName} |
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
http://esd.consultingwerkcloud.com/
https://github.com/consultingwerk/SmartComponentLibrary
We have resolved an issue where the invocation of the FetchDataByKeyTable method using a DatasetModel caused the error
Unable to convert SET-PARAMETER value to datatype passed. (10059) CallStack from ABL error object: --> FillByKeyTable Consultingwerk.OERA.TableModel at line 2412 |
Aded the following new method to the ArrayHelper:
/** * Purpose: Displays a message with the items of the given character array * Notes: * @param pcPrefix The prefix to add to each item (e.g. array name) * @param phArray The Handle Array */ METHOD PUBLIC STATIC VOID Message (pcPrefix AS CHARACTER, phArray AS HANDLE EXTENT): |
The Interface has already been a superset of the IFormWithUltraToolbarsManager. We've now finally added the inheritance between the two interfaces to reduce the number of CAST's which are required when working with the WinKit.
Implemented method to render ABL MENU-BAR as Office 2010 style Application menu
/** * Purpose: Builds a Ribbon ApplicationMenu structure with the structure * of an ABL menu-bar * Notes: * @param poForm The Form owning the UltraToolbarsManager that contains the Ribbon */ METHOD PUBLIC STATIC VOID BuildRibbonApplicationMenu2010 (poForm AS IFormWithUltraToolbarsManager): |
We have improved the error handling here, so that the error message now indicates the invalid entry in the .classpath file. This will simplify locating the configuration problem.
The Business Entity Designer does now support generating a SERIALIZE-NAME that only differs in the case form the field name. Previously a case-insensitive comparison was performed to decide of the SERIALIZE-NAME attribute of a temp-table field had to be written to the source code.
Implemented the following new method in the BufferHelper which returns an Enum value representing the type of a given buffer: Database, Temp-Table or Before-Table
/** * Purpose: Determines the type of a Buffer * Notes: Database, Temp-Table or Before-Table * @param phBuffer The buffer to determine the type of * @return The type of the Buffer as a BufferTypeEnum value */ METHOD PUBLIC STATIC BufferTypeEnum BufferType (phBuffer AS HANDLE): |
Added the following new methods to the JsonHelper class
/** * Purpose: Returns a delimited list with the values of the given * attributes of the JsonObject * Notes: * @param poJsonObject The reference to the JsonObject * @param pcAttributeNames The comma delimited list with the names of the JSON attributes * @return The delimited list with the values */ METHOD PUBLIC STATIC CHARACTER ListFromAttributeValues (poJsonObject AS JsonObject, pcAttributeNames AS CHARACTER): |
/** * Purpose: Returns a delimited list with the values of the given * attributes of the JsonObject * Notes: * @param poJsonObject The reference to the JsonObject * @param pcAttributeNames The comma delimited list with the names of the JSON attributes * @param pcDelimiter The list delimited * @return The delimited list with the values */ METHOD PUBLIC STATIC CHARACTER ListFromAttributeValues (poJsonObject AS JsonObject, pcAttributeNames AS CHARACTER, pcDelimiter AS CHARACTER): |
We have implemented the following new scaffolding templates ( https://documentation.consultingwerkcloud.com/display/SCL/Scaffolding+utility+for+common+helper+classes ):
scl-gen ParameterWithInterface SampleParameter Value1 Value2 scl-gen ParameterWithReadOnlyInterface SampleParameter Value1 Value2 scl-gen Interface SampleInterface Value1 Value2 scl-gen ReadOnlyInterface SampleInterface Value1 Value2 |
These templates can be used to generate Interface types and serializable parameter objects implementing those interfaces.
The RESTful services now utilize the SFV and SFS security realms. Fields which are not authorized using the SFV realm will be excluded from the responses of a RESTful entity. Fields which are not authorized using the SFS or SFV realms will cause an http 403 error when the user tries to update those fields using a POST, PUT or PATCH method.
The Consultingwerk.Util.LogManager class now supports setting the LOG-MANAGER:LOG-ENTRY-TYPES and the LogManager:CustomLogEntryTypes using presets provided by the IConfigurationProvider service (e.g. .applicationsettings file).
The .applicationsettings file can provide the logging presets using a nested JSON Structure:
"loggingPresets": { "query": { "LogEntryTypes": "QryInfo:4,4GLTrace:2", "CustomLogEntryTypes": "DataAccess" }, "sample": { "LogEntryTypes": "4GLMessages:2,4GLTrans:2", "CustomLogEntryTypes": "ABC,DEF,GHI" } } |
The logging presets can be activated using the LoggingPreset property:
Consultingwerk.Util.LogManager:LoggingPreset = "query". |
The LogManagerSettings user control also supports selection of the active logging preset in a combo-box.
To facilitate a common two label stack-layout in the NativeScript Grids, the JSON template for grids, both repository and annotations based, should have four new character properties:
* rowImageTemplate
* rowTemplate
* rowDetailTemplate
* rowBadgeTemplate
When the rowTemplate is not set by a developer, the NativeScript rending will derive a column layout based on the Grid columns.