Version Information

OpenEdge Release	Version Information
11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2, 12.6, 12.7 CQC	Release 11.7 #75712@2023-05-01

Security Bulletin - log4j CVE-2021-44228

Further details: log4j CVE-2021-44228

OpenEdge 12.7 support!

We have finished our testing based on the OpenEdge 12.7 CQC (customer quality certification) release and are expecting to be able to announce formal support for OpenEdge 12.7 shortly after the commercial release from Progress Software.

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:

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

Download Link

http://esd.consultingwerkcloud.com/

https://github.com/consultingwerk/SmartComponentLibrary

Overview of included tickets

Bug

SCL-3399 Fetching data BY-REFERENCE with &SUFFIX specified

Description:

When programs use a dataset include that specifies the &SUFFIX argument, and call the FetchData method with the BY-REFERENCE modifier, then the DataAccess objects used must provide a value for the DataAccess class' DefinedBufferNames property. This property must contain the defined (canonical) temp-table names for the dataset, in the order that they appear in the dataset.

SCL-4046 Parsing annotations with comma-delimited values with the XrefClassAnnotationParser

Description:

The Consultingwerk.Studio.XrefClassAnnotationParser now parses annotation attribute values that contain comma-delimited values into the correct attribute name-value pairs.

SCL-4052 Fixed error when opening object master that was deleted and recreated from LRU

Description:

We have resolved the error that was raised when opening an object master that was deleted and recreated with the same name from the LRU in the Object Master Designer form. The error raised was:

An Consultingwerk.SmartFramework.Repository.InvalidObjectMasterException has occurred:

Invalid object master "dc30d795-9418-a8b0-aa14-fe81b8e48edb"

SCL-4054 Proparse failed on &IF DEFINED (Test-{&Test})

Description:

We have resolved an issue in Proparse that was raised when the preprocessor variable name reference in an &IF DEFINED expression was build from an preprocessor variable itself like in the code shown here.

&SCOPED-DEFINE Test 42

&SCOPED-DEFINE Test-42

&IF DEFINED (Test-{&Test}) NE 0 &THEN
MESSAGE "yeah"
    VIEW-AS ALERT-BOX.
&ENDIF

The error thrown was similar to this:

org.prorefactor.refactor.RefactorException: Error parsing test-parse.p

Original Exception: java.lang.IllegalArgumentException: C:\Work_STREAM\SmartComponentLibrary\Develop127\ABL\Demo\SDO\test-parse.p:13 Bad DEFINED function in &IF preprocessor condition

The issue is resolved now.

Improvement

SCL-4049 Added Session Info Form to Legacy Browser Migration Tool

Description:

We have added the Session Info Form to the Legacy Browser Migration Tool.

SCL-4050 Legacy Frame Migration now detects LABEL on Rectangle

Description:

The Legacy Frame Migration tool now detects ABL LABEL widgets (leterals) that are placed within the top line of a RECTANGLE widgets. The text contained in those LABEL widgets is used as the Title of the GroupBox that is used to replace the RECTANGLE widget.

SCL-4051 ISmartRepositoryService now provides an API to CreatePage

Description:

The ISmartRepositoryService interface now provides an API to create a new page on a container.

SCL-4053 Ability to render multiple toolbars into a single Ribbon

Description:

The rendering of Ribbon Style Toolbars in the Desktop rendering engine now supports to render multiple MetaToolbar instances into the same Ribbon component on the MetaForm master.

SCL-4056 Kendo UI Builder View Button of Legacy GUI Frame Widget Migration was missing small icon

Description:

We have added a Small Button Image to the Form to improve rendering on the Ribbon Quick Access Toolbar.

SCL-4057 Support for unbound fields in MetaViewerGenerator

Description:

The MetaViewerGenerator used when migrating static ABL GUI layouts (.w files) into the repository now supports setting the “Unbound” attribute for fields not bound to a database field.

SCL-4058 Implemented ability to inject existing SmartDataAdapter instances into a rendered Form

Description:

We have implemented injecting existing SmartBusinessEntityAdapter instances (MetaDataSource) when rendering dynamic forms. The SmartFormFactory now contains additional variants of the Form factory methods with an additional parameter like this:

    /**
     * Purpose: Creates a Form instance with the given parameters
     * Notes:
     * @param pcClassName The name of the Form to launch (static class name or repository object name)
     * @param plUseCharacterParameterValue Logical value indicating if the routine should use the character parameter to the Form
     * @param pcCharacterParameterValue The optional character parameter value to the form
     * @param pcFormAction The FormAction for this form instance
     * @param poComponents The Dictionary of existing components (SmartDataAdapters)
     * @return The reference to the new form instance
     */
    METHOD PUBLIC STATIC Progress.Windows.Form CreateInstance (pcClassName AS CHARACTER,
                                                               plUseCharacterParameterValue AS LOGICAL,
                                                               pcCharacterParameterValue AS CHARACTER,
                                                               pcFormAction AS CHARACTER,
                                                               poComponents AS "System.Collections.Generic.Dictionary<System.String, System.ComponentModel.IComponent>"):

That additional parameter poComponents supports passing in existing components. Based on the key in the dictionary (Instance Name) the Form rendering service will not create and initialize new instances of the component. Instead the references of the components passed in the Dictionary of Components will be used when constructing the new form.

This provides an alternative variant of pass through links and especially supports sharing multiple SmartBusinessEntityAdapter instances between a parent and a child form.

SCL-4062 SmartBusinessEntityLookup now supports fetching values for description fields when navigating data

Description:

Based on two new Attributes the SmartLookup (including SmartBusinessEntityLookup) supports fetching of description and key field values when navigating data.

The FetchDataOnNavigate property will allow to fetch data based on the Lookup’s Text attribute (typically data-bound) when navigating data (e.g. in a SmartDataBrowser also linked to the same data source).

The FetchDataFromKeyValueOnNavigate property will allow to fetch data based on the Lookup’s LookupKeyValue attribute (typically data-bound) when navigating data (e.g. in a SmartDataBrowser also linked to the same data source). This includes fetching the value for the Text property of the Lookup.

/**
 * Purpose: Controls if the lookup fetches data when the (viewer's) data-source
            is navigating data
 * Notes:
 */
DEFINE PUBLIC PROPERTY FetchDataOnNavigate AS LOGICAL NO-UNDO INITIAL FALSE
GET.
SET.

/**
 * Purpose: Controls if the lookup fetches data when the (viewer's) data-source is
            navigating data and the LookupKeyValue property changes
 * Notes:
 */
DEFINE PUBLIC PROPERTY FetchDataFromKeyValueOnNavigate AS LOGICAL NO-UNDO INITIAL FALSE
GET.
SET.

When those properties are not set to TRUE, our Lookups will behave as always, expecting that during navigating all data is provided by the Viewer’s DataSource.

Only one of those properties should be set to TRUE.

SCL-4063 Implemented clipboard copy from Session Info Form

Description:

The SessionInfoForm (used in the error message form) now supports to copy the key and value column from the list views to the clipboard.

SCL-4064 Data Source Query Editor in Business Entity Designer now supports "pop out"

Description:

The Data Source Query Editor (SourceDefaultQuery) in the Table properties viewer of the Business Entity Designer now supports to be popped our into a resizable editor. This will simplify the typing of longer query strings.

SCL-4069 Implemented general support for useBeforeImage for invokable methods in the JSDO Catalog

Description:

We now support setting the useBeforeImage attribute for invokable methods in the JSDO catalog.

For Business Entity methods, the UseBeforeImage atttribute can by added to the @InvokeMethod annotation with a value of true or false. The default value is false.

For Business Tasks, the BusinessTaskMethodData class and Interface contain this option as an additional logical property.

New Feature

SCL-3950 Object Master Designer now supports creating a new object master based on an instance

Description:

The Object Master Designer now provides a wizard to create a new object master based on an existing instance (for instance in a Form or Viewer). This supports developers in creating reusable components by prototyping them on an initial container. The wizard allows to optionally replace the existing instance with a new master. When using this tool on a SmartViewer the wizard allows to optionally skip the X and Y attributes when assigning instance attribute values to the new object master.

Story

SCL-4055 The TelemetryService sets key values for procedures to a dotted-notation value

Description:

The key value used when a procedure is sepcified for a request’s ServiceName or ServiceInterface (if the SetServiceRequest method is not called), now uses a dotted notation similar to class-based services. Any path separators in the procedure name are replaced with “.”.

The name is shortened using the same approach used for classes (ie the Consultingwerk.Util.ClassHelper’s ShortPackageName method).

SCL-4059 Implemented Web Rendering support for SaveMode property

Description:

The rendering of viewers to the web (Angular) now supports the “SaveMode” property of the SmartViewer controlling if fields should always be enabled (SaveMode = TRUE) or require the user to press an Update button first.

SCL-4060 Implemented Desktop rendering support for SaveMode property

Description:

The rendering of viewers and grids to the Desktop now supports the “SaveMode” property of the SmartViewer and SmartUpdatableDataBrowser controlling if fields should always be enabled (SaveMode = TRUE) or require the user to press an Update button first.

Task

SCL-4047 The Rollbase adapter has been removed from the SmartComponent Library

Description:

The Rollbase adapter has been removed from the SmartComponent Library. This includes removal from the Business Entity Designer.

The following files have been removed from the SmartComponent Library:

* Consultingwerk/BusinessEntityDesigner/Plugins/RollbaseImporter/SelectObjectNameDialog.cls
* Consultingwerk/BusinessEntityDesigner/Plugins/RollbaseImporter/SelectObjectNameDialog.resx
* Consultingwerk/BusinessEntityDesigner/Plugins/RollbaseImporterPlugin.cls
* Consultingwerk/RollbaseAdapter/Data/SelectQueryResponseParser.cls
* Consultingwerk/RollbaseAdapter/IRollbaseAdapter.cls
* Consultingwerk/RollbaseAdapter/IRollbaseCredentials.cls
* Consultingwerk/RollbaseAdapter/Login/LoginResponseParser.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDef.i
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDefs.i
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDefsTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDefsTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDefsTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDefTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDefTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataFieldDefTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataObjectDef.i
* Consultingwerk/RollbaseAdapter/MetaData/DataObjectDefTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataObjectDefTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/DataObjectDefTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/MetaData/dsObjectDef.i
* Consultingwerk/RollbaseAdapter/MetaData/dsObjectDef.xsd
* Consultingwerk/RollbaseAdapter/MetaData/dsObjectDefNames.i
* Consultingwerk/RollbaseAdapter/MetaData/dsObjectDefNames.xsd
* Consultingwerk/RollbaseAdapter/MetaData/eObjectDefName.i
* Consultingwerk/RollbaseAdapter/MetaData/ListItem.i
* Consultingwerk/RollbaseAdapter/MetaData/ListItems.i
* Consultingwerk/RollbaseAdapter/MetaData/ListItemsTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/ListItemsTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/ListItemsTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/MetaData/ListItemTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/ListItemTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/ListItemTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefBusinessEntity.bedgm
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefBusinessEntity.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefBusinessEntity.png
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefDataAccess.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefDatasetController.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefDatasetModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefDatasetModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNamesBusinessEntity.bedgm
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNamesBusinessEntity.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNamesDataAccess.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNamesDatasetController.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNamesDatasetModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNamesDatasetModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNamesResponseParser.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNameTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNameTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/ObjectDefNameTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDef.i
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDefs.i
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDefsTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDefsTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDefsTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDefTableModel.cls
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDefTableModel_Generated.cls
* Consultingwerk/RollbaseAdapter/MetaData/RelationshipDefTableModelFilter.cls
* Consultingwerk/RollbaseAdapter/PermissionEnum.cls
* Consultingwerk/RollbaseAdapter/RollbaseAdapter.cls
* Consultingwerk/RollbaseAdapter/RollbaseCredentials.cls
* Consultingwerk/RollbaseAdapter/RollbaseException.cls
* Consultingwerk/RollbaseAdapter/RollbaseLoginException.cls
* Consultingwerk/Windows/Framework/Rollbase/DataObjectDefViewerControl.cls
* Consultingwerk/Windows/Framework/Rollbase/DataObjectDefViewerControl.resx
* Consultingwerk/Windows/Framework/Rollbase/ObjectDefinitionForm.cls
* Consultingwerk/Windows/Framework/Rollbase/ObjectDefinitionForm.resx

SCL-4048 Support for the BPM Adapter has been removed from the SmartComponent Library

Description:

Support for the BPM Adapter has been removed from the SmartComponent Library.

This includes the removal of the OpenEdge-BPM preprocessor from various products.i includes.

The following files were removed as part of this

* BPMAdapterSettings.xml
* BPMWorkStepDescriptionTemplates.xml

Customers that want to keep their copy of the BPM Adapter are fine to do so.

Customers that have not been using the BPM Adapter need to remove the following line from their product.i file:

&GLOBAL-DEFINE OpenEdgeBPM