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

Release 11.3 #51276@2019-03-25

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 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 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: 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 (30 December 2018)

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:

<assembly name="proparse.net, Version=4.0.1.1177, 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 debug information when errors are thrown from proparse.net.dll.

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

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


Bug

SCL-2447 Fixed an issue when deleting group-boxes in the Repository Viewer Designer

Description:

We've fixed an issue that occurred when deleting group-boxes in the Repository Viewer-Designer.

SCL-2545 Fixed error when loading AuthorizationClient while starting AppServer client

Description:

We have fixed an issue when starting the AuthorizationClient service on an AppServer client
An Consultingwerk.Framework.Exceptions.ServiceLoaderException has occurred:
Error while loading service: Consultingwerk.SmartFramework.Authorization.AuthorizationClient
Unable to use dedicated business entity when not using the Service Interface.

SCL-2560 Fixed "Invalid Handle (3135)" error when moving a menu structure in the Menu Maintenance

Description:

We've fixed an issue in the Menu Maintenance that could occur when moving a menu item and the form was configured not to expand all menu structures when loading the menu.

SCL-2565 Removed dependency to Business Entity Designer from between List & Label support routines

Description:

The List & Label support routines have been referencing the BusinessEntityGenerator's GetUserId method. We've resolved this dependency by moving that method to the SessionHelper class instead. The Business Entity Generator now also references to method from the SessionHelper.

SCL-2568 Corrected setting of BindingSource property UseFullFieldNames in RenderedBrowseControl

Description:

Since SCL-2374 we support the re-initialization of the RenderedBrowseControl by calling into the InitializeGrid method when the ABL browse widget has changed (eg. different columns etc.).
We've now corrected the setting of the UseFullFieldNames property, was we need to support setting this both to TRUE and to FALSE now.

Improvement

SCL-2566 Implemented a Builder for IBufferDataSource instances

Description:

We've implemented a static builder to simplify creation of IBufferDataSource instances using the IFactory service. The builder can be used like this:

DEFINE VARIABLE oDataSource AS IBufferDataSource NO-UNDO .

oDataSource = BufferDataSourceBuilder:ForTable("Customer")
                                     :AddTable("SalesRep")
                                     :BufferDataSource .


or

oDataSource = BufferDataSourceBuilder:ForBuffer(NEW BufferSpec("Customer", "b_Customer"))
                                     :AddBuffer(NEW BufferSpec("Salesrep", "b_Salesrep"))
                                     :BufferDataSource .


Internally the static builder leverages the IFactory service (when loaded) and requests instances of the IBufferDataSource type. When the IFactory service is not available, the builder will create a new instance of the BufferDataSource class straight away.

SCL-2570 Setting the AddingRecord property into SmartViewerControl to TRUE prior to rasing the FieldsEnabled event

Description:

When adding or copying records using a SmartViewerControl and SmartUpdatableBrowser the AddingRecord property was only set to TRUE after raising the FieldsEnabled event. This made it impossible to distinguish between Add and Update in this event.
We've changed the order to facilitate distinguishing between Add and Update when handling the FieldsEnabled event.

SCL-2571 New options on Dataset Model SaveChanges method

Description:

The DatasetModel's SaveChanges method now supports an additional parameter based on the Consultingwerk.OERA.Enum.OnValidationErrorEnum enumeration. This parameter allows to specify how the DatasetModel behaves in case of validation error.
By default the DatasetModel:SaveChanges() method will throw validation errors taking direct influence on the code flow.
Now developers can invoke the method with the continue option:

DatasetModel:SaveChanges(OnValidationErrorEnum:Continue). 


This option won't throw an error and developers can investigate the error status of every record using the BufferError and BufferErrorString properties of the TableModel class.

SCL-2572 Business Entity Adapter now enforce buffer's default sort when SortString is empty

Description:

In order to enforce a reasonable batching behavior, the SmartBusinessEntityAdapter now uses the sort string matching the EntityTable's primary index as the SortString when no sort string was specified before (using the SortString property or the Business Entity Descriptor).

SCL-2573 Implemented support for FORMAT of numeric fields in Windows Rendering

Description:

GUI for .NET forms rendered based on repository data will now use the FORMAT property (ABL format string) to set the Infragistics InputMask property. The functionality is based on the FormatHelper class.

SCL-2574 Improvement the Business Entity Designer Folder/Package Browser

Description:

When searching for a folder/package in the Business Entity Designer's folder browser dialog, the tree view will now select the first match. Previously the root node remained selected.

SCL-2575 Implemented details about the status of temp-table records in the BufferHelper:ShowBuffer() method

Description:

The BufferHelper:ShowBuffer method will now display informations about the ROW-STATE, ERROR, REJECTED and ERROR-STRING attributes of a ProDataset temp-table record.

SCL-2576 Added LRU to Repository Object Maintenance Form

Description:

We have implemented an LRU (last recently used) list of repository objects to the Ribbon File menu of the Repository Object Maintenance Form.

New Feature

SCL-2499 SmartRequestAuthorizationProvider now supports distinction between Create, Modify and Delete

Description:

The SmartRequestAuthorizationProvider implementation now supports optional distinction between Create, Modify and Delete. Previously it was only possible to restrict or grant access to any form of updates through a Business Entity. Now it's optionally possible to distinguish between the type of update.
We have added three additional security tokens for that purpose:
- ServiceInterface.Create
- ServiceInterface.Modify
- ServiceInterface.Delete
Those can be assigned to a security object (Business Entity) in addition to the existing ServiceInterface.SaveChanges.
When the config setting (.applicationsettings or .restapplicationsettings) UseDetailedRequestAuthorizationOnUpdate is set to TRUE the SmartRequestAuthorizationProvider will check for new security tokens as well as to the ServiceInterface.SaveChanges.
Note: The SmartRequestAuthorizationProvider's initialization has been moved to the initialize() method (following the CCS standards). The service must either be loaded through the ServiceLoader (from a services.xml file), or the initialize() method must be called manually (e.g. when loading an instance of the service manually in unit tests etc.).

SCL-2567 Implement support for questions during updates in a Business Entity

Description:

We've implemented support for handling questions (Yes-No, Yes-No-Cancel, OK-Cancel) when doing updates using the GUI for. NET frontend and Business Entities. The support requires a standard CHARACTER field with the name SmartUiAction in the concerned temp-table definition. The functionality is based on the IMessageInteractionService .
The feature allows to return questions from the Business Entity to the user and resume (redo) the validation of an update once the user has answered those questions. The frontend will display questions received from the backend during a save operation.
In order to use this feature in the Business Entity ValidateDate method, you need to create an instance of the ISmartUiAction type. This instance needs to be initialized for a given temp-table record using the InitializeFromBuffer method. This will deserialize a list of potentially already answered questions received from the user interface.
To ask a question, the ValidateData method calls in to the AskQuestion method of the ISmartUiAction instance. This method is invoked with the various details of the question (including the set of buttons) and two identifiers for the question:
- pcMessageId is an unique identifier for a question's location in the source code. This can be a GUID value (using the genuuid script on the proenv shell) or any other unqiue identifier (like the class name and a source code line number). This value is only relevant to distinguish multiple questions issued during a single backend call.
- pcMessageContext is an unqiue identifier for a record to which a question instance belongs. This is primarily relevant when asking the same question in multiple iterations of a loop in ValidateData; typically when multiple records are validated at once.
The AskQuestion method either returns the answer provided by the user as an MessageReply enum value (including the possibility for the Unanswered status).
Based on the response given by the user (or the unanswered status) the code may react.
If based on a certain answer, the backend would like to indicate that the current update operation should be cancelled (user needs to change values in the UI), a specialized buffer ERROR-STRING can be set using then DatasetHelper's SetControlCancel method.

    METHOD OVERRIDE PROTECTED VOID ValidateData ():

        DEFINE VARIABLE oUiAction AS ISmartUiAction   NO-UNDO .

        oUiAction = CAST ({Consultingwerk/get-mandatory-service.i IFactory}:CreateInstance (Progress.Lang.Class:GetClass ("Consultingwerk.OERA.ISmartUiAction":U)),
                          ISmartUiAction) .

        FOR EACH eOrder ON ERROR UNDO, THROW:
            Consultingwerk.OERA.Validate:IsNotUnknown (BUFFER eOrder:HANDLE,
                                                       "OrderDate":U,
                                                       "Order date may not be empty":U) .

            oUiAction:InitializeFromBuffer (BUFFER eOrder:HANDLE) .

            BufferHelper:FindBeforeBuffer(BUFFER eOrder:HANDLE) .

            IF eOrder.ShipDate <> ? AND eOrderBefore.ShipDate <> ? AND
               eOrder.Instructions <> eOrderBefore.Instructions THEN DO:

                IF oUiAction:AskQuestion ("6aa8941028d40f55:-40a29757:169851f1d2d:-8000":U,
                                          STRING (eOrder.OrderNum),
                                          "Update Instructions for shipped order?"{&TRAN},
                                          "Update Order"{&TRAN},
                                          "Updating instructions for shipped order might not be followed by the carrier."{&TRAN},
                                          MessageButtons:YesNo,
                                          MessageReplyEnum:ReplyNo) = MessageReplyEnum:ReplyNo THEN

                    DatasetHelper:SetControlCancel (BUFFER eOrder:HANDLE) .
            END.

            oUiAction:FinalizeBuffer() .
        END.

        FOR EACH eOrderBefore WHERE ROW-STATE (eOrderBefore) = ROW-DELETED:

            oUiAction:InitializeFromBuffer (BUFFER eOrderBefore:HANDLE) .

            IF eOrderBefore.ShipDate <> ? THEN DO:
                IF oUiAction:AskQuestion ("3a1d3043bcd6e4f3:-3281de7e:169851ed704:-8000":U,
                                          STRING (eOrderBefore.OrderNum),
                                          "Delete shipped order?"{&TRAN},
                                          "Delete Order"{&TRAN},
                                          "Deleting a shipped order might not have an impact on the carrier."{&TRAN},
                                          MessageButtons:YesNo,
                                          MessageReplyEnum:ReplyNo) = MessageReplyEnum:ReplyNo THEN

                    DatasetHelper:SetControlCancel (BUFFER eOrderBefore:HANDLE) .
            END.

            oUiAction:FinalizeBuffer() .
        END.
    END METHOD . 


SCL-2569 New ListHelper API: EnsureUniqueEntries

Description:

We're implemented a new API in the ListHelper. The EnsureUniqueEntries method returns a delimited list based only on unique entries from the input list. Duplicates are eliminated.



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