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, 11.7.4 | Release 11.3 #50786@2019-02-25 |
We are please to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 11.7.4. We hereby declare OpenEdge 11.7.4 fully supported for the SmartComponent Library as of the release of November 5th 2018.
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 have not been aware of any incompatibilities with OpenEdge 11.7.3.
.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.
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.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.
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.
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 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 |
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
The REST Entities Web Handler now supports exposing individual array elements for GET requests to Collections.
http://localhost:8820/web/Entities/SCL2528/Salesreps ?fields=SalesRep,RepName,MonthQuota[4] ( http://localhost:8820/web/Entities/SCL2528/Salesreps ?fields=SalesRep,RepName,MonthQuota%5B4%5D) will now return just the MonthQuota[4] field.
Individual array elements can also be specified in the @RestAddress annotation for collections. When receiving the individual resource or during update array fields are still represented as JsonArray's only.
We are raising now a more meaningful error message when attempting to render a web menu structure that contains an incompatible menu function.
To simplify the distinction between implementation details and site configuration data for security realms, we have added group boxes to the maintenance form.
We have implemented client side input restrictions (validation) to the security assignment maintenance screen. This restriction blanks out the user name when entering a group name and vice versa as only one of the fields may be populated.
We have implemented a Business Entity Designer plugin that supports creating lookup controls in the Repository for a selected Table of the current Business Entity Design.
We have implemented a rendering engine compatible to the Meta-Repository-Types. This rendering engine support rendering the same repository data to GUI for .NET, Angular and NativeScript.
The SmartDataBrowser now supports a Hotkey for Refresh. The the Hotkey can either be set as an ABL Shortcut (e.g. F5 or CTRL-R) to the
Consultingwerk.SmartComponents.Implementation.SmartDataBrowserSettings:RefreshHotKeyString |
property or an System.Windows.Forms.Shortcut value to the
Consultingwerk.SmartComponents.Implementation.SmartDataBrowserSettings:RefreshHotKeyString |
property. The property can also be set using the JSON Startup file of the GUI session using a static property setting:
"staticProperties": { ... "Consultingwerk.SmartComponents.Implementation.SmartDataBrowserSettings:RefreshHotKeyString": "F5", ... } |
When the user hit's the property, the SmartDataBrowser will let the linked Data Adapter to either reopen it's query or fetch updated data from the backend.
Implemented a new utility that supports updating or deleting multiple object master records. The product module can be updated for a set of objects using a button in the Ribbon.
!screenshot-1.png|thumbnail!
We have implemented a new RESTful endpoint which supports web rendering of the security item lookup for a security realm.
http://localhost:8820/web/Entities/SmartFramework/GetSecurityRealmItemLookup ?Value=99c76236-bd65-aeb8-e013-4ffcf411e4c1
Where Value is the GUID of the Security Realm.
Sample response:
{ "SerializedType": "Consultingwerk.Framework.RepositoryServices.SmartBusinessEntityLookupDescriptor", "LookupBrowserFields": "SecurityTokenCode,SecurityTokenDescription", "LookupDialogFilterFields": "SecurityTokenCode,SecurityTokenDescription", "LookupDialogFilterOperators": "BEGINS,BEGINS", "LookupDialogQuerySort": "BY eSmartSecurityToken.SecurityTokenCode", "LookupDialogQueryString": "FOR EACH eSmartSecurityToken", "LookupDialogTitle": "Select Security Token", "LookupEntityName": "Consultingwerk.SmartFramework.Authorization.SecurityTokenBusinessEntity", "LookupEntityTable": "eSmartSecurityToken", "LookupKeyField": "SecurityTokenCode", "LookupKeyValueColumn": "SecurityTokenGuid", "LookupQueryString": "FOR EACH eSmartSecurityToken WHERE eSmartSecurityToken.SecurityTokenCode BEGINS \"&1\"" } |
Implemented a RESTful endpoint for the security assignment verification (similar to the GUI form).
Sample URL:
http://localhost:8820/web/Entities/SmartFramework/IsRestrictedCheck ?RealmGuid=9f2d813a-d8c2-2bbb-dc13-7aabd0d7e66f&SecurityItemGuid=cd229641-1db6-81b3-e211-66569ba03908&UserGuid=ffcc4f24-af98-8187-e211-4714049f854c
That is the Message Translation Realm, Security Item Dutch and user mikefe (in Consultingwerk)
Returns:
{ "IsRestricted": true, "Reason": "User", "Runtime": 0, "Groups": [ { "GroupName": "Consultingwerk Admin", "ParentGroupName": "Admin", "LoginCompanyName": "Consultingwerk Ltd." }, { "GroupName": "User" }, { "GroupName": "Admin" } ] } |
To simplify usage of the ClassHelper:GetClassNamesInClassPath in environments support business entities, we have implemented a business entity as a wrapper to ClassHelper:GetClassNamesInClassPath
This feature is implemented using a Named Query on the new Consultingwerk.Util.ClassHelper.ClassHelperBusinessEntity business entity.
Query name: ClassNamesInClassPath
Parameter BaseClassName (Character): Consultingwerk.SmartFramework.Authorization.ISecurityRealmService
Parameter IncludeAbstractClasses (Logical): false
When invoking this via the JSDO generic service, you should also set the StopAfter to zero (turn off stop-after) using an additional query string parameter: &stopAfter=0