Release Notes 2017-12-11
Version Information
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 | Release 11.3 #44319@2017-12-11 |
OpenEdge 11.7 Service Pack 2
We are announcing full compatibility with the Service Pack 2 for OpenEdge 11.7 (OpenEdge 11.7.2).
See further remarks below.
Deletion of SmartDataAdapters and BindingSources
In SCL-2019 we have changed the clean-up behavior of the SmartDataBrowser control when a Form is closed. After this change, the SmartDataBrowser will delete it's linked SmartDataSource (e.g. SmartBusinessEntityAdpater) instance and DataSource (binding source). In rare cases, where those instances may still be required after the form containing the browser have been closed, developers can set the following new property of the SmartDataBrowser to FALSE:
/** * Purpose: Controls if the SmartDataBrowser deletes it's SmartDataSource and DataSource * when the Form is closed * Notes: */ DEFINE PUBLIC PROPERTY DeleteDataSourceOnFormClosed AS LOGICAL NO-UNDO INITIAL TRUE GET. SET.
Your action may be required!
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.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 (05 November 2017)
We have updated proparse with further enhancements in this release (completed support for multi-tenancy related functions and SERIALIZABLE/NON-SERIALIZABLE keywords on class members). 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:
<assembly name="proparse.net, Version=4.0.1.1173, Culture=neutral, PublicKeyToken=cda1b098b1034b24"/>
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.
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} handler12=Consultingwerk.Web2.Services.SmartViewsHandler.SmartGridWebHandler: /SmartViews/Grid/{CustomViewName} handler13=Consultingwerk.Web2.Services.SmartViewsHandler.SmartViewerWebHandler: /SmartViewer/Viewer/{EntityName}/{ViewName} handler14=Consultingwerk.Web2.Services.SmartViewsHandler.SmartViewerWebHandler: /SmartViewer/Viewer/{ObjectName} handler15=Consultingwerk.Web2.WebHandler.SmartMessageWebHandler: /SmartMessage/{MessageGroup}/{MessageNumber} handler16=Consultingwerk.Web2.WebHandler.GetImageWebHandler: /Image/{FileName} handler17=Consultingwerk.Web2.WebHandler.SmartValueListWebHandler: /ValueList/{ValueList} handler18=Consultingwerk.Web2.WebHandler.SmartAttachmentsWebHandler: /Attachments/{Table}/{KeyValues} handler19=Consultingwerk.Web2.WebHandler.SmartAttachmentWebHandler: /Attachment/{Guid} handler20=Consultingwerk.Web2.WebHandler.SessionContextWebHandler: /SessionContext handler21=Consultingwerk.Web2.WebHandler.ContextPropertiesWebHandler: /ContextProperties/{PropertyName} handler22=Consultingwerk.Web2.WebHandler.ContextPropertiesWebHandler: /ContextProperties handler23=Consultingwerk.Web2.WebHandler.SessionInfoWebHandler: /SessionInfo handler24=Consultingwerk.Web2.WebHandler.FileSearchWebHandler: /FileSearch/{FileName} handler25=Consultingwerk.Web2.WebHandler.ExecuteAblWebHandler: /ExecuteAbl handler26=Consultingwerk.Web2.WebHandler.SmartLanguagesWebHandler: /Languages handler27=Consultingwerk.OERA.RestResource.RestEntitiesWebHandler: /Entities handler28=Consultingwerk.OERA.Swagger.SwaggerWebHandler: /Swagger/{EntityName} handler29=Consultingwerk.OERA.Swagger.SwaggerRestEntitiesWebHandler: /SwaggerEntities/{OutputType} handler30=Consultingwerk.Web2.WebHandler.SmartTokenSecurityCheckWebHandler: /TokenSecurityCheck/{ObjectName} handler31=Consultingwerk.Web2.WebHandler.SmartTokenSecurityCheckWebHandler: /TokenSecurityCheck handler32=Consultingwerk.Web2.WebHandler.SmartEntityTableMappingHandler: /EntityTableMapping/{EntityName}/{TableName}/{UiTypeCodes} handler33=Consultingwerk.Web2.WebHandler.SmartTreeRootNodeWebHandler: /SmartViews/TreeRootNode/{rootnodeid} handler34=Consultingwerk.Web2.WebHandler.SmartTreeChildNodesWebHandler: /SmartViews/TreeChildNodes/{parentnodeid} handler35=Consultingwerk.Web2.WebHandler.SmartSecurityCheckWebHandler: /IsRestricted/{SecurityRealmCode}/{SecurityItemGuid}
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
- 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 utility classes
- RESTful services
- JSON Configuration File Format
- Common Component Specification (CCS)
- BY-REFERENCE Access to Business Entity FetchData
- Implementing Service Interface Authorization for Business Entity Methods
- SmartComponents NG2 reference
- Legacy GUI FRAME Migration
- Proparse TreeView
- How to use appsrvtt.d with PASOE
- Executing SonarLint CLI from within PDSOE
- Inspecting User Table and Index Statistics
- How to use appsrvtt.d with PASOE
- JsonSerializable classes
- Updating .annotation files through an ANT Eclipse Builder
Download Link
http://esd.consultingwerkcloud.com/
https://github.com/consultingwerk/SmartComponentLibrary
Bug
- [SCL-1991] - Error when fetching repository object
- [SCL-2021] - Incorrect validation message in Security Realm Business Entity
- [SCL-2025] - Viewers in the Business Entity tester do not subscribe to ParentFormDestroyed event
- [SCL-2026] - Investigate possible performance improvements around the BindingSourceHelper:IsBindingChangingValue () method
New Feature
- [SCL-1976] - Need a way in the DatasetModel classes to enforce the use of the ServiceAdapter even when there are DB's connected
- [SCL-1982] - import-data.p should working with a json-file as parameter
Improvement
- [SCL-1831] - Extend Retrieve Data Test-Scenario