Version Information

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

OpenEdge 12.7 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.7. We hereby declare OpenEdge 12.7 fully supported for the SmartComponent Library as of the release of  May 10th 2023.

OpenEdge 12.6 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.6. We hereby declare OpenEdge 12.6 fully supported for the SmartComponent Library as of the release of  October 4th 2022.

OpenEdge 12.2 support!

We are pleased to announce that we are not aware of any issues using the SmartComponent Library on OpenEdge 12.2. We hereby declare OpenEdge 12.2 fully supported for the SmartComponent Library as of the release of April 09th 2020.

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

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:

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
handler41=Consultingwerk.Web2.WebHandler.ExecuteQueryWebHandler: /ExecuteQuery
handler42=Consultingwerk.Web2.WebHandler.TranslationProviderWebHandler: /GetTranslation

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

• Support for RESTful invocation of Business Task and Business Entity Methods
• Invalid Proparse code-page setting corrupts temp-table field labels during "Refresh from Include"
• Generic Factory Service
• Using Invokable Business Entity Methods with Dataset Model Classes
• Using the Business Entity method FetchDataByKeyTable
• PASOE management scripts
• Business Entity Designer Launcher
• Searching data using ROWID's within the SmartBusinessEntityAdapter
• Business Entity Count Method
• 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 helper classes
• RESTful services
• JSON Configuration File Format
• Common Component Specification (CCS)

Download Link

http://esd.consultingwerkcloud.com/

https://github.com/consultingwerk/SmartComponentLibrary

Overview of included tickets

Bug

SCL-4101 Method parameter classes that have properties that are defined with arrays are correctly shown in the Swagger documentation

Description:

Rest and invokable method parameter classes that have properties that are defined with arrays, are shown correctly in the Swagger documentation.

The JSON that is generated for the Swagger documentation has the following format for properties that have indeterminate extents

"<property-name>": {
  "type": "array",
  "items": {
    "x-ablType": "<property-abl-datatype>",
    "type": "<JSON-datatype>"
  }
}

Properties that have fixed extents have the minItems and maxItems values set to the EXTENT value in the property definition.

"<property-name>": {
  "type": "array",
  "minItems": <array-size>,
  "maxItems": <array-size>,  
  "items": {
    "x-ablType": "<property-abl-datatype>",
    "type": "<JSON-datatype>"
  }
}

The Swagger UI deployed to PASOE may need to be updated in order for this information to be correctly displayed. See https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/1980137473/Keeping+Swagger+UI+up-to-date for more details on updating Swagger UI.

SCL-4148 Form title in Angular rendering now exposed as "formTitle"

Description:

Previously the form title has been assigned to a property “title” in the repository rendered JSON layout. This has now been changed to a property named “formTitle” to match the implementation of our Angular frontend library.

Improvement

SCL-3558 New QueryStyle property in IDatasetModel to control certain fetch data behaviour

Description:

A new property on the Consultingwerk.OERA.IDatasetModel interface and related classes (like Consultingwerk.OERA.DatasetModelPerformer) named QueryStyle controls how query expressions are added to the Consultingwerk.OERA.IFetchDataRequest implementations used to retrieve data. This property is used in the DatasetModel’s RetrieveData methods that have a parameter defined as Consultingwerk.IQueryExpression . RetrieveData methods that do not have such a parameter are not affected by this change.

For more detaiil on the behaviour of this property, see https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/1980792834/DatasetModel+QueryStyle+property .

SCL-3960 Providing ability to login to a GUI application using OAuth2 (eg Azure, Office 365)

Description:

We have implemented a new feature that allows to replace the login dialog of an OpenEdge GUI application with a browser interface authenticating with OAuth2 identify servers (OIDC) like Office 365.

The solution includes the following components:

* a login window based on CefSharp that drives the OIDC authentication flow
* a BeforeBrowser callback handler that retrieves the JWT token from the forward URL
* an Authentication Service that validates the JWT token
* two variants for validating the JWT token and retrieving the user name of the JWT
Token Exchange Service based on an PASOE ABL application
JwtTokenValidator service based on components of the .NET framework

More details can be found in the documentation: https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/1980792847/Configuring+the+Token+Exchange+Service

Or this YouTube presentation of the feature: https://www.youtube.com/watch?v=7iSFqqjk_Rk

SCL-4095 Introduced a Toolbar Link

Description:

We have implemented a new LinkType in the SmartComponent Library and the GUI for .NET repository rendering. The toolbar link can be set between a toolbar instance and a grid or viewer. The toolbar link causes that the action of a button is executed in the Viewer or Grid or their respective logic class rather than in the Form or the Form Logic class.

SCL-4105 Support SmartTable references to SmartDB tables with DatabaseName other than SmartDB

Description:

To complete the support for custom names for the SmartDB, we have now improved all code that references SmartDB tables from the SmartTable database table with the ability to mpa the database name to the database name configured in the Consultingwerk/products.i file.

SCL-4130 Added Reload button to the Repository Integrity Report form

Description:

We have added a reload button to the repository integrity report form. This button allows to rescan the repository without the need to close and reopen the form.

SCL-4132 Introduced SmartMessageFormHelper

Description:

.To simplify the use of localizable messages from the SmartDB SmartMessage table, we have introduced the SmartMessageFormHelper class. This class provides static API’s that combines retrieving messages from the IMessageProvider service with displaying it using the MessageFormHelper class.

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character):                                                  

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @param pcMessageParam3 The third parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character,
                                                   pcMessageParam3 as character):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @param pcMessageParam3 The third parameter for the message
 * @param pcMessageParam4 The fourth parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character,
                                                   pcMessageParam3 as character,
                                                   pcMessageParam4 as character):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @param pcMessageParam3 The third parameter for the message
 * @param pcMessageParam4 The fourth parameter for the message
 * @param pcMessageParam5 The fifth parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character,
                                                   pcMessageParam3 as character,
                                                   pcMessageParam4 as character,
                                                   pcMessageParam5 as character):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @param pcMessageParam3 The third parameter for the message
 * @param pcMessageParam4 The fourth parameter for the message
 * @param pcMessageParam5 The fifth parameter for the message
 * @param pcMessageParam6 The sixth parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character,
                                                   pcMessageParam3 as character,
                                                   pcMessageParam4 as character,
                                                   pcMessageParam5 as character,
                                                   pcMessageParam6 as character):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @param pcMessageParam3 The third parameter for the message
 * @param pcMessageParam4 The fourth parameter for the message
 * @param pcMessageParam5 The fifth parameter for the message
 * @param pcMessageParam6 The sixth parameter for the message
 * @param pcMessageParam7 The seventh parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character,
                                                   pcMessageParam3 as character,
                                                   pcMessageParam4 as character,
                                                   pcMessageParam5 as character,
                                                   pcMessageParam6 as character,
                                                   pcMessageParam7 as character):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @param pcMessageParam3 The third parameter for the message
 * @param pcMessageParam4 The fourth parameter for the message
 * @param pcMessageParam5 The fifth parameter for the message
 * @param pcMessageParam6 The sixth parameter for the message
 * @param pcMessageParam7 The seventh parameter for the message
 * @param pcMessageParam8 The eighth parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character,
                                                   pcMessageParam3 as character,
                                                   pcMessageParam4 as character,
                                                   pcMessageParam5 as character,
                                                   pcMessageParam6 as character,
                                                   pcMessageParam7 as character,
                                                   pcMessageParam8 as character):

/**
 * Purpose: Display Message based on a Message structure
 * Notes:
 * @param pcMessageGroup The message group to return
 * @param piMessageNumber The message number to return
 * @param pcMessageParam1 The first parameter for the message
 * @param pcMessageParam2 The second parameter for the message
 * @param pcMessageParam3 The third parameter for the message
 * @param pcMessageParam4 The fourth parameter for the message
 * @param pcMessageParam5 The fifth parameter for the message
 * @param pcMessageParam6 The sixth parameter for the message
 * @param pcMessageParam7 The seventh parameter for the message
 * @param pcMessageParam8 The eighth parameter for the message
 * @param pcMessageParam9 The ninth parameter for the message
 * @return The DialogResultEnum value
 */
method public static DialogResultEnum ShowMessage (pcMessageGroup as character,
                                                   piMessageNumber as integer,
                                                   pcMessageParam1 as character,
                                                   pcMessageParam2 as character,
                                                   pcMessageParam3 as character,
                                                   pcMessageParam4 as character,
                                                   pcMessageParam5 as character,
                                                   pcMessageParam6 as character,
                                                   pcMessageParam7 as character,
                                                   pcMessageParam8 as character,
                                                   pcMessageParam9 as character):

SCL-4133 ActionType is now capable of NEW'ing TableModel instances through the Factory

Description:

The ActionType (component of Business Entity validation) is now capable of creating the TableModel instance using the IFactory Service. The TableModel instance is newed using the Factory service when the TableModelType is an Interface and not an actual class.

SCL-4134 ProparseHelper:ParseFile now uses FileHelper:FindFile()

Description:

The ParseFile method of the ProparseHelper is now resolving the file name to parse using the FileHelper:FindFile() API which performs a PROPATH search for the file.

SCL-4143 AppServerStartupManager now traps STOP conditions

Description:

The AppServerStartupManager now catches as logs STOP conditions raised during startup of the AppServer session.

SCL-4145 Angular DataField rendering now supports ViewAs TOGGLE-BOX

Description:

The rendering of DataFields for the Angular UI (JSON layout) now supports the ViewAs “TOGGLE-BOX” phrase in the repository. Fields with that attribute value will be rendered with the “checkbox” style.

Sub-task

SCL-4131 .NET method to validate JWT token

Description:

We have implemented the Consultingwerk.Windows.JwtAuth.JwtValidator class that supports validating a JWT token’s signature using API’s of the .NET framework.