Release Notes 2019-09-21

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.4, 12.0, 12.1

Release 11.3 #54495@2019-09-21

OpenEdge 12.1 support!

We are please to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.1. We hereby declare OpenEdge 12.1 fully supported for the SmartComponent Library as of the release of September 21st 2019.

OpenEdge 12.0 support!

We are please to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.0. We hereby declare OpenEdge 12.0 fully supported for the SmartComponent Library as of the release of May 1st 2019.

OpenEdge 11.7.4 support!

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.

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 

Besides the issue with the Visual Designer however, we have not been aware of any incompatibilities with OpenEdge 11.7.3. 

.NET Framework Version 4.7

.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.

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: 

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 we further recommend all customers to apply this hotfix as well. 

New Versions of Proparse .NET Assemblies (30 December 2018)

We have updated proparse with further enhancements in this release (see Please download the .NET Assemblies ZIP file from our ESD and replace the in your environment with the latest one. The new assembly reference is:

<assembly name=", Version=, Culture=neutral, PublicKeyToken=cda1b098b1034b24"/>

As proparse is used by our Business Entity Generator, this new version of the 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

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

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

Overview of included tickets


SCL-2607 Fixed issue with FindRowWhere on server with match close to the end of the query result list


We've fixed an issue in the DataAccess FindRowWhere method that when the match was close to the end of the queries result list might have caused an invalid query string with the INDEXED-REPOSITION keyword appearing twice in the fetch query string.

SCL-2754 Resolved errors during regeneration of large Business Entity


During the regeneration of larger business entities, the error
DITEM is not large enough to hold string. (4043).
might have been raised by the AVM. We've resolved those issues by changing the way how we modify existing source code.

SCL-2760 Business Entity Designer and Generator now validate that all temp-table indexes have at least a single field


The Business Entity Designer and Generate have been enhanced to validate that all indexes have at least a single field. Indexes without fields might habe caused compile errors in the temp-table definitions and have caused duplicate signature definitions in the DatasetModel and Query constructors.

SCL-2763 Fixed an issue retrieving Object Instances using JSDO Generic Service


We have resolved an issue with the generation of the query string that might have been raised when retrieving repository data from the ObjectMasterBusinessEntity using the JSDO generic service:

Unable to prepare query: eSmartObjectInstance.ObjectMasterGuid EQ "ad7c5f60-68e4-d28e-5314-77e12cce2962" , FIRST b_SmartObjectMaster OF SmartObjectInstance
Client-Query: eSmartObjectInstance.ObjectMasterGuid EQ "ad7c5f60-68e4-d28e-5314-77e12cce2962"
Default-Query: FOR EACH SmartObjectInstance, FIRST b_SmartObjectMaster OF SmartObjectInstance

SCL-2769 Fixed issues with using Date values in the InputPromptHelper:ComplexInput


We've resolved issue in the ComplexInputDateControl class that might have caused the error message

** Invalid date input. (85)

when typing an incomplete date. This has been resolved now.

SCL-2772 Fixed an issue with SmartBusinessEntityAdapter adding wrong sort phrase


We have resolved an issue where the SmartBusinessEntityAdapter was adding the default sort phrase to the wrong buffer. When the QueryString property of the SmartBusinessEntityAdapter was set with queries for multiple buffers CHR(1) delimited and the QuerySort property was empty. The SmartBusinessEntityAdapter uses the temp-table's primary index sort criteria instead of the QuerySort property. However, this was added to the end of the QueryString property instead of adding it to the first entry (query string of the EntityTable). This has been fixed.


SCL-2615 Added details about context to UnsupportedReturnTypeException exception


When the generation of a Swagger documentation for a Business Entity fails due to issues with the method's return-type, we're now adding details about the name of the method causing this issue to the Exception.

SCL-2723 Improved performance of ContextDatasetStore by using JSON instead of XML


We have implemented the class Consultingwerk.Framework.Server.JsonContextDatasetStore as an alternative IContextDatasetStore implementation. This class uses JSON to store the context dataset between HTTP requests to the PASOE. We've identified a 10% performance improvement for short HTTP requests by this change.
The XML based ContextDatasetStore is still provided for backwards compatibility.

SCL-2752 SmartHttpClient now inherits from HttpClientDecorator


The Smart HttpClient as a decorator of the HttpClient now leverage the abstract base class HttpClient Decorator. This should allow inheriting potential future enhancements made by Progress Software and is also the foundation for allowing the HttpClient Builder to use this class the default decorator of the HttpClient .

SCL-2756 protop Launcher (SmartComponent Library desktop) now reads DLC from dblist.cfg


To allow connections to DB's of various OpenEdge releases, we now retrieve the value for the DLC variable when launching protop from the Studio Desktop from the protop configuration.

SCL-2758 Improved error message when retrieving repository data for a container with an invalid instance


We now provide further details for issues with inconsistent repository data found during retrieving a container from the SmartFramework repository.

SCL-2759 Extend Factory/Builder of OpenEdge HttpClient to return SmartHttpClient by default


We have implemented the class Smart[ HttpClient Service| HttpClient Service] which should be loaded as a service via a service.xml file when the session starts (it's important that it's loaded that way so the initialize method gets called). After that class has been loaded, it registers the Smart HttpClient as a decorator to the HttpClient class so that there's no longer the need to manually load the Smart HttpClient decorator, the HttpClient Builder will take care of that. So when executing

oResponse = ClientBuilder:Build():Client:Execute(RequestBuilder:Get("":U):Request) .

the request will automatically be using the Smart[ http Client| http Client] and provide the error handling by throwing ABL errors instead of just returning an http status code.

SCL-2767 Performance improvements in the StringHelper:FirstOccurenceOf method


We have improved the performance of the StringHelper:FirstOccurenceOf method by 10 - 20%. This method is used a few times within the QueryParser implementation.

SCL-2768 Simplify handling of query flags in Data Access classes


When retrieving data through a Business Entity and Data Access class the consuming application typically provides selection criteria through a query string or mechanisms like named queries. These query conditions are typically concatenated to the source default query implemented in the data access. The source default query hereby defines the maximum set of records from the source tables the client application can retrieve. The client application can only select (filter) within this set of data. The source default query provides a means of implementing row level security in the Data Access class.
There are rare cases where it is however desired to consider the source default query as a default and allow the client application to influence the source default query through the query string. In the following we refer to the specific selection criteria which will allow customization of the source default query as query flags.
With the API’s introduced here we support two use cases for query flags:
- Removing a selection criteria from the source default query, e.g. a filter by a row status (e.g. Deleted = false, OrderStatus = Ordered)
- Providing additional options (valid values) for a field which is present in the source default query (e.g. OrderStatus = Ordered should become OrderStatus = Ordered or OrderStatus = Shipped or OrderStatus = Partially Shipped). In this case values provided by the client need to be OR’ed with the value(s) for this field specified in the source default query.
Implementation of the use-cases has been possible before the implementation of this ticket. The new API’s in introduced in this feature are however providing a simplification.
Foundation of those API’s is the QueryParser which splits the selection criteria passed by the client in the IFetchDataRequest instance into a list of QueryExpression object. The QueryParser is frequently used in the DataAccess:FetchData method in the context of query optimization (e.g. switching the buffer sequence in the DATA-SOURCE query). As the result of the QueryParser may now also be used for the handling of query flags, we have added the QueryExpression property to the IFetchDataRequest interface (the property has previously already been added to the FetchDataRequest implementation, so that this now only resolves the need for frequent CAST’ing of poFetchDataRequest to the implementing type). The parsing of the query string provided by the client application can now be achieved by calling the PROTECTED method ParseTopBufferRequestQuery() in the Consultingwerk.OERA.DataAccess class.

    METHOD PUBLIC OVERRIDE VOID FetchData (poFetchDataRequest AS IFetchDataRequest):

        DEFINE VARIABLE oParser AS QueryParser NO-UNDO .

        oParser = NEW QueryParser () .

        poFetchDataRequest:QueryExpression = THIS-OBJECT:ParseTopBufferRequestQuery (poFetchDataRequest) .

        SUPER:FetchData(poFetchDataRequest) .


For the first use case listed above (ability to remove a default selection criteria from the source default query, code similar to the following block of code may be implemented in the SourceDefaultQuery method of the Data Access class. In this example, the default source default query is

FOR EACH Order WHERE Order.OrderStatus = ‘Ordered’ INDEXED-REPOSITION

The client can pass in the following pseudo selection criteria in the client query string

eOrder.OnlyOrdered = FALSE 

which will cause the following sample implementation of the SourceDefaultQuery method to return just


as the default selection criteria. Nether in the database table nor in any temp-table a column named OnlyOrdered exists.


        /* Handle OnlyOrdered = FALSE */
        DEFINE VARIABLE oOnlyOrdered AS QueryExpression NO-UNDO .

        CASE pcTable:
            WHEN "eOrder":U THEN DO:
                IF VALID-OBJECT (THIS-OBJECT:FetchDataRequest:QueryExpression) THEN
                    oOnlyOrdered = QueryExpression:GetExpressionForField ("eOrder.OnlyOrdered",
                                                                          THIS-OBJECT:FetchDataRequest:QueryExpression) .

                IF VALID-OBJECT (oOnlyOrdered) AND oOnlyOrdered:SecondOperandAsLogical() = FALSE THEN
                    RETURN "FOR EACH Order INDEXED-REPOSITION":U .
                    RETURN "FOR EACH Order WHERE Order.OrderStatus = 'Ordered' INDEXED-REPOSITION":U.

        END CASE .


The implementation of the method uses the result of the QueryParser stored in the QueryExpression property of the current IFetchDataRequest instance. The static QueryExpression:GetExpressionForField (singular) method has been previously existing, the SecondOperandAsLogical() instance method of the QueryExpression class has been asses now to avoid CAST’ing the SecondOperand property of the QueryExpression instance to an ILogicalHolder or ICharacterHolder to retrieve the value of the OnlyOrdered selection in the query string.
For the second use case described above (providing additional valid values for a field already contained in the source default query), code similar to the following sample implementation of the SourceDefaultQuery method in the DataAccess class can be used. In this example, the default source default query is


and the client may provide additional valid salesrep’s in the query string, e.g. by providing

eOrder.SalesRep = ‘BBB’ or eOrder.SalesRep = ‘DOS’

in the FetchDataRequest:Queries property. The resulting source default query in this example must OR the values provided by the client query with the value in the default source default query, e.g.

RETURN "FOR EACH Order WHERE (Order.SalesRep = 'HXM' or Order.SalesRep = ‘BBB’ or Order.SalesRep = ‘DOS’ INDEXED-REPOSITION":U.

        DEFINE VARIABLE oSalesRep AS ListQueryExpression NO-UNDO .

        CASE pcTable:
            WHEN "eOrder":U THEN DO:
                IF VALID-OBJECT (THIS-OBJECT:FetchDataRequest:QueryExpression) THEN
                    oSalesrep = QueryExpression:GetExpressionsForField ("eOrder.Salesrep",
                                                                        THIS-OBJECT:FetchDataRequest:QueryExpression) .

                IF VALID-OBJECT (oSalesrep) AND NOT oSalesRep:IsEmpty THEN
                    RETURN SUBSTITUTE ("FOR EACH Order WHERE (Order.SalesRep = 'HXM' or &1) INDEXED-REPOSITION":U,
                                       oSalesrep:GetExpression()) .

                    RETURN "FOR EACH Order WHERE Order.SalesRep = 'HXM' INDEXED-REPOSITION":U.

        END CASE .


The implementation of the method uses the result of the QueryParser stored in the QueryExpression property of the current IFetchDataRequest instance. The new static QueryExpression:GetExpressionsForField (plural) method has been implemented to filter the list of query expressions for a single field. This method also supports providing the required field mapping of the eOrder.Salesrep field in the temp-table to the database field Order.SalesRep required in the source default query. The GetExpresison() method of the oSalesrep instance (ListQueryExpression class) returns the selection criteria provided by the client with the OR operator.
In order to prevent the query processing of the DataAccess class (implemented in the QueryString class) from handling the SalesRep field again when merging the source default query with the FetchDataRequest:Queries, the SourceColumn method can be extended like this to return no mapping for those fields anymore:



        /* When the query expression contains Salesrep, this will be handled
           in SourceDefaultQuery, so ignore the field in the client query */
        IF THIS-OBJECT:IsQueryFlagPresent (pcColumn, "eOrder.SalesRep") THEN
            RETURN ? .

        CASE pcTable:
            WHEN "eOrder":U THEN
                cMap = BUFFER eOrder:DATA-SOURCE-COMPLETE-MAP .

        END CASE .

        ASSIGN iPos = LOOKUP(pcColumn, cMap) .

        IF iPos MODULO 2 = 1 THEN
            RETURN ENTRY(LOOKUP(pcColumn,cMap) + 1,cMap).
            RETURN "":U .


The PROTECTED IsQueryFlagPresent() method of the DataAccess class is checking the current column name against the comma delimited list of columns interpreted as query flags (just eOrder.SalesRep in this example) and checks if that column is contained in the QueryExpression stored in the current FetchDataRequest instance. By returning ? from SourceColumn, this method indicates that the field should not mapped anymore when processing the queries.

SCL-2770 Added new Repository Attribute to control the web designer for a container type


We've added the new Attribute WebDesignerComponent to the MetaForm, MetaViewer and MetaGrid repository types. This Attribute controls the designer component to use when editing a component to that type in the Angular based repository designer..

SCL-2776 ClassHelperBusinessEntity now provides option to retrieve classes without the use of the .NET Framework


We've added a new logical argument NoDotNet to the ClassNamesInClassPath named query of the ClassHelperBusinessEntity. This argument allows to controls that the business entity does not use the .NET framework to retrieve the list of matching classes from the backend. This allows to workaround issues with using the .NET framework on PASOE in certain situations.
A sample request payload when using the method from a REST client may look like this:

{ "NamedQuery": 
  { "name": "ClassNamesInClassPath", 
    "parameters": [
      { "name": "BaseClassName", 
        "type": "character", 
        "value": "Consultingwerk.SmartFramework.Authorization.ISecurityRealmService"}, 
      { "name": "IncludeAbstractClasses", 
        "type": "logical", 
        "value": false},
      { "name": "NoDotNet", 
        "type": "logical", 
        "value": true}]

SCL-2777 UserBusinessEntity now populates ManagerUserName and ManagerUserFullName for new records


We've enhanced the UserBusinessEntity of the SmartFramework so that it populates the ManagerUserName and ManagerUserFullName for new user records.

SCL-2778 MetaViewer rendering (GUI and Web) now supports VIEW-AS COMBO-BOX with list-items or list-item-pairs


When rendering DataField instances in a MetaViewer the ValueListItems and ValueListItemPairs properties are now fully supported for fields using VIEW-AS COMBO-BOX.

SCL-2779 Updated JSON Rendering for MetaBusinessEntityLookup components


We have updated and completed the JSON rendering of the MetaBusinessEntityLookup to support the latest changes and enhancement of the Angular lookup component.

New Feature

SCL-2713 Added Support for Dataset Input for RESTful method invokation


Formerly the implementation of RESTful method invokation (Business Entity or Task) did only support providing an input object, not input datasets. The dataset-parameters are only used as output.
This feature has now been enhanced, so that we now also support multiple ProDatasets for input. Similar to the response we should be optionally supporting the specification of datasets used for input using the request argument of the RestMethod annotation, e.g.:

    @RestMethod (address="/GetCustomerAndInvoices", requestMethod="post",

In this sample, the JSON request body of a POST, PUT, PATCH, ... request is expected to be structured like this

  "dsCustomer": {"eCustomer": [ .... ] }
  "parameter": .... 

The dsCustomer will be deserialized into the appropriate dataset. The "parameter" will be deserialized into the parameter object of the method.
If the "request" is not defined as part of the annotation, the request is processed like before, interpreting the whole request payload as the parameter object.

SCL-2749 Implemented REST endpoint to store Object Master Attributes


We have implemented a REST endpoint to store object master attributes in the SmartFramework repository.
This has been implemented as a PUT request to this endpoint with the ObjectMasterGuid value in the URL http://localhost:8820/web/Entities/SmartFramework/Repository/StoreObjectMasterDesignAttributes/857872d2-4eb4-b38f-3614-2191e8c7bf07
All properties that are modified from the Object Type defaults are expected to have the IsInherited property set to FALSE.

SCL-2765 Implemented REST endpoints to fetch and update attributes of SmartObjectInstances


We have implemented the following endpoints to retrieve and store instance attribute values based on the ObjectInstanceGuid value:
GET: http://localhost:8820/web/Entities/SmartFramework/Repository/GetObjectInstanceDesignAttributes/ad238208-b49f-68b9-1c14-1fb28817ba8b
PUT: http://localhost:8820/web/Entities/SmartFramework/Repository/StoreObjectInstanceDesignAttributes/ad238208-b49f-68b9-1c14-1fb28817ba8b


SCL-2751 scl-pasoe-... scripts now support retrieving DLC for OpenEdge 12.1


We've updated the scl-pasoe-... scripts to be able to determine the DLC value for OpenEdge 12.1 from the Windows registry.

SCL-2775 New API in DatasetHelper to detach the DATA-SOURCE's from all ProDataset buffers


We've implemented the new API DatasetHelper:DetachDataSources (phDataset). This API detaches all DATA-SOURCE's from the Buffers of the given ProDataset.