Page tree
Skip to end of metadata
Go to start of metadata

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, 11.7.3.007

Release 11.3 #48289@2018-09-17

OpenEdge 11.7.3 support!

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. 

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 (08 April 2018)

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:

<assembly name="proparse.net, Version=4.0.1.1176, 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.

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}

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

Download Link

http://esd.consultingwerkcloud.com/

https://github.com/consultingwerk/SmartComponentLibrary

Overview of included tickets


Improvement

SCL-2360 Support for Enum properties of parameter objects passed by the RestEntitiesWebHandler to the invoked methods

Description:

Implemented support for assigning Enum properties of parameter instances passed to methods of Business Entities and Business Tasks. Before this change only properties of primitive types have been supported. Now it is supported to map character values to Enum type properties (Progress.Lang.Enum or Consultingwerk.Enum) in the parameter object.

SCL-2367 Defined RESTful URL's for Authorization related Business Entities

Description:

Added annotations for the following RESTful URL's of the Authorization related Business Entities.

/web/Entities/SmartFramework/Users
/web/Entities/SmartFramework/Groups
/web/Entities/SmartFramework/LoginCompanies
/web/Entities/SmartFramework/SecurityRealms
/web/Entities/SmartFramework/SecurityAssignments
/web/Entities/SmartFramework/SecurityTokens
/web/Entities/SmartFramework/FieldSecurityItems

See https://documentation.consultingwerkcloud.com/display/SCL/RESTful+services for a documentation of our RESTful end points for Business Entities.

SCL-2368 Implemented Method in SecurityAssignmentBusinessEntity to return distinct SecurityItemGuids for a security realm

Description:

We have implemented a new method in the SecurityAssignmentBusinessEntity. This method returns the list of distinct assigned security items for a security realm. This list contains every security item in a Dataset one, which is assigned to any user.

    @InvokeMethod (parameterClassName="Consultingwerk.CharacterHolder", datasetInput="false", datasetOutput="true") .
    @RestMethod (address="/SmartFramework/SecurityAssignments/GetDistinctSecurityItems/~{Value}", requestMethod="get", parameterClassName="Consultingwerk.CharacterHolder", response="dsSecurityItemKeys").
    METHOD PUBLIC VOID GetDistinctSecurityItems (INPUT-OUTPUT DATASET dsSecurityItemKeys,
                                                 poSecurityRealm AS CharacterHolder):



This method allows developers to implement custom authorization assignment maintenance functions. The method is also accessible as a RESTful endpoint, e.g.

/web/Entities/SmartFramework/SecurityAssignments/GetDistinctSecurityItems/SST

for the distinct security item id's assigned in the Smart Security Token Realm (SST).

SCL-2370 Implemented new XmlHelper method to locate a child node recursively by it's name

Description:

Added new method which locales the first child now with the given name recursively:

    /**
     * Purpose: Recursively locates a Node with the given name
     * Notes:   The caller is responsible for cleaning of the returned x-noderef
     * @param phParentNode The x-noderef of the parent node
     * @param pcNodeName The name of the element
     * @return The x-noderef representing the located node or ?
     */
    METHOD PUBLIC STATIC HANDLE ChildNodeByName (phParentNode AS HANDLE,
                                                 pcNodeName AS CHARACTER):



SCL-2371 Implemented an XmlHelper method that returns a node by a path

Description:

Implemented the new method GetChildNodeByPath

    /**
     * Purpose: Returns the child node by a path
     * Notes:   Performs an XPath-Like selection of an XML Node. Nodes are referenced
     *          by the name or attributes or position in a set, e.g.:
     *          /lm:eCafModel/lm:serviceCollection/lm:details
     *          /lm:eCafModel/lm:serviceCollection/lm:details/lm:adapterDetails/lm:properties[2]
     *          /lm:eCafModel/lm:serviceCollection/lm:services/lm:details/lm:adapterDetails/lm:properties[2]
     *          /lm:eCafModel/lm:serviceCollection/lm:services/lm:details/lm:adapterDetails/lm:properties/[2]
     *          /lm:eCafModel/lm:serviceCollection/lm:services[@displayName="api" and @id="api"][1]
     * @param phNode The x-noderef or x-document
     * @param pcPath The node path
     * @return The X-NODEREF referencing the selected node
     */
    METHOD PUBLIC STATIC HANDLE GetChildNodeByPath (phNode AS HANDLE, pcPath AS CHARACTER):



The method supports node paths in a simplified XPath syntax like these samples:

/lm:eCafModel/lm:serviceCollection/lm:details



Follows the node path returning the first nodes with the given name either from the document root or the provided parent node

/lm:eCafModel/lm:serviceCollection/lm:services/lm:details/lm:adapterDetails/lm:properties[2]
/lm:eCafModel/lm:serviceCollection/lm:services/lm:details/lm:adapterDetails/lm:properties/[2]



Returns the 2nd child node of the lm:properties node. The use of a slash between the _lm:properties and the index 2 is optional.

/lm:eCafModel/lm:serviceCollection/lm:services[@displayName="api" and @id="api"][1]



Returns the 1st child node of the lm:services node. Seeks for the lm:services node with the attribute values displayName "api" and id "api". Multiple attributes can be searched. Currently and is the only supported boolean operator.