Release Notes 2022-10-24
Version Information
OpenEdge Release | Version Information |
|---|---|
| 11.7.9, 11.7.10, 11.7.11, 11.7.12, 12.2., 12.5.2 | Release 11.7 #72518@2022-10-24 |
Security Bulletin - log4j CVE-2021-44228
Further details: log4j CVE-2021-44228
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 |
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-3804 Business Entity Designer's Create Repository Form did not honor "Add Filter" option
Description:
The Create Repository Form wizard of the Business Entity Designer now honors the “Add Filter” option. When this option is unchecked, no MetaFilter component will be added to the generated form master anymore.
SCL-3814 FileHelper:RelativeFileName was failing on Linux
Description:
We have fixed an issue with FileHelper:RelativeFileName returning invalid file names on Linux. In particular the first letter was missing from the returned pathname.
SCL-3823 Fixed typos in Smart Scheduler code
Description:
We have resolved various typos in the SmartComponent Library code base including the SmartScheduler Code. Typos have been on the word “available” in comments and messages shown to the user.
SCL-3829 Fixed issues with CommentFormatter when Template does not contain PDSOE like file header
Description:
We have resolved issues in the CommentFormatter used by the Business Entity Designer. CommentFormatter might have been failing with an error message like
ENTRY 57 is not in List /***************
when the Business Entity template was not containing a PDSOE like file header comment block.
Improvement
SCL-3795 Providing a user name and password for SmartDB when running the update and migration utility
Description:
A username and password can be provided for the SmartDB when running the upgrade and migration utility. These can be provided via properties or iteractively.
The username and password can be provided by setting the {{smartdbuser.name}} and {{smartdbuser.password}} properties.
The script will prompt for the username and/or password if a {{smartdbuser.prompt}} property is set with a value of {{true}} , or if only one of the username or password is provided. The prompt option is for cases where customers do not want to store passwords in scripts or property files.
For more details on these properties, and how to run the upgrade utility, see https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8093744/SmartDB+Upgrade+and+Migration+Routine#SmartDBUpgradeandMigrationRoutine-RunningtheSmartDBUpgradeandMigrationutiltiy .
SCL-3797 Support for SmartDB upgrade and migration utility on Linux / TTY environments
Description:
The SmartDB Update and Migration utility may be run on Linux hosts. The major differences between running on Windows are pathing and environment variables (eg {{$DLC}} vs {{%DLC%}} ), and also that only the none and minimal values for the compile property are supported.
The instructions at https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8093744/SmartDB+Upgrade+and+Migration+Routine#SmartDBUpgradeandMigrationRoutine-RunningtheSmartDBUpgradeandMigrationutiltiy should still be followed.
SCL-3802 Enabled multiple selection when reorder instances in Object Master Maintenance
Description:
We are now supporting multi-selection in the Reorder instances dialog of the Object Master Designer.
SCL-3808 Added Disabled flag to SmartUser
Description:
We have added a Disabled flag to the SmartUser record. When this flag is set, the user can no longer login to the system.
SCL-3809 Added Comments field to the SmartGroup table
Description:
We have added a Comments field to the SmartGroup table. This field can be used to document the purpose of a defined user group.
SCL-3810 User Group assignment: Allow hiding child groups of already selected parent groups in available groups
Description:
When assigning parent groups (when multiple parent groups have been enabled in products.i) we now allow to filter out the parent and grand-parent groups of already assigned user groups.
So when a user group is child of group A which is child of group B, by default group B is shown in the list of the potential parent groups. The user can filter those out by clicking the toggle button “Hide parent groups of assigned parent groups” in the ribbon.
SCL-3812 When copying a SmartGroup, the parent group assignment will now be copied as well
Description:
We’ve extended the Group Business Entity to copy assigned parent groups to the new user group as well.
SCL-3813 Providing more context with RI error messages
Description:
We have implemented a new service: IRelationChildRecordDescriptionProvider
This service can be used to provide customized error messages when a parent record cannot be deleted due to the OnChildRestrict rule of a SmartRelation. When the service returns ? the default message is used - otherwise the message provided by the service is returned to the user.
We have implemented this service for the delete of a user group blocked by an user in the group.
SCL-3815 Support for DynamicControlGroup rendering outside of Dynamic Forms
Description:
We have added the static method RenderControlGroup to the Consultingwerk.Windows.Framework.Repository.Rendering.DynamicControlGroupRenderingService. This method allows to render a DynamicControlGroup (MetaControlGroup) outside of the rendering process of a DynamicForm into any .NET Container Control.
SCL-3816 Support IconFileName and Title on MetaControlGroup
Description:
We have added support for the IconFileName and Title properties on the MetaControlGroup type in the SmartFramework repository.
The Title will be used to set the DynamicControlGroup instance’s Text property and IconFileName has been implemented as a property with no other current functionality than to hold the value.
SCL-3817 Investigate: Do we still need our own copy of the Ccs Folder?
Description:
Consultingwerk has been shipping the Ccs folder ( https://github.com/progress/CCS ) longer than Progress software.
The Ccs package contains interfaces, enums and classes defined by the CCS Specifications. Since OpenEdge Release 11.7.2, this code is also shipped by Progress Software, as both source and rcode, and so does not need to be built or included in as part of a deployment.
We have decided to keep including those files in our deployment to simplify developers to get insight into the types.
SCL-3818 Distinguish what caused the "You are not authorized to invoke SaveChanges." exception
Description:
The SmartRequestAuthorizationProvider implementation has been extended raise a different error message when the user is not authorized for a specific SaveChanges request into a Business Entity. Previously the “You are not authorized to invoke SaveChanges.” has been raised when the authorization failed due to the missing ServiceInterface.SaveChanges, ServiceInterface.Create, ServiceInterface.Delete or ServiceInterface.Modify security object tokens.
Now we’re raising specific error messages for Create, Delete and Modify to provide less confusing error messages to the user.
The new SmartMessages SFR-215, SFR-216 and SFR-217 have been introduced for this purpose.
SCL-3820 Improved DatasetModel method templates
Description:
The ModelClassGeneratorPlugin for the Business Entity Designer has always been defining the parameter object for proxy methods in the DatasetModel_Generated class as Consultingwerk.ISerializable when the method was not using the ProDatasetParameter.
We have made the following improvements:
* Using the exact parameter type for the proxy method definition
* Expand short class names to full class names to not rely on USING definitions
* Added a new template invoke2-with-returnvalue which can be used to call into the Business Entity method using the ServiceAdapter InvokeTask2 method and supports for a parameter object and a return object
SCL-3822 Implemented support for deleted records in IUserSynchrinzationService inplementation
Description:
The IUserSynchronizationService has initially been implemented without support for deletes of user or group records.
This has now been enhanced.
SCL-3827 Angular JSON Rendering now honoring the RetrieveDataOnLoad property
Description:
The Angular JSON rendering is now rendering a MetaDataSource instances RetrieveDataOnLoad property into the autoFetch property of the data-source in the JSON layout of a form.
SCL-3828 Provide Consultingwerk.UltraControls.19.2.20192.198.dll Assembly
Description:
We’re now providing the Consultingwerk.UltraControls assembly for the Infragistics Controls shipped in OpenEdge 12.2 FCS (19.2.20192.198).
New Feature
SCL-3642 Adopted PctDynRun in setup.xml
Description:
We have exchanged PctRun tasks with PctDynRun tasks in setup.xml. This will enable the usage of the https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8093744/SmartDB+Upgrade+and+Migration+Routine in production environments without an installed OpenEdge developer license.
SCL-3788 New ServiceAdapter InvokeTask2 methods to use native ABL serialization
Description:
In order to support the use of native ABL serialization of objects (ie classes defined with the SERIALIZABLE keyword in the CLASS statement) for invocation of business tasks, several new methods are added to the Consultingwerk.OERA.IServiceAdapter interface and consequently to the Consultingwerk.OERA.ServiceAdapter implementation.
These methods' signatures are very similar to the InvokeTask methods, differing only in that they accept parameter objects defined as Progress.Lang.Object . The methods validate that the input parameter objects are either defined as {{SERIALIZABLE}} or that they implement Consultingwerk.ISerializable . Parameter objects that are neither will cause a Consultingwerk.OERA.Exceptions.NoSerializableTypeException to be thrown.
The InvokeTask2 methods do not modify/update the input parameter objects and return one of the following values:
# If the business task has been defined with a return type of Progress.Lang.Object (or a descendant), then the return value of the business task will be returned. This is true even if the retun value is not a valid object.
# If the business task is not defined as returning an object, then the input parameter object is returned.
Using the InvokesTask2 methods is recommended, since native ABL serialization performs better than serialization written in ABL.
An example of a InvokeTask2 method is below. There are multiple overloads of the method with zero to 5 dataset handle parameters, and variants with and without a context dataset. These methods all behave identically, as described here.
/**
* Purpose: Invokes a method in a Task class.
* Notes: When no MethodName is passed then "Invoke" will be executed as the
* default task method
* @param pcPartition The name of the AppServer partition for this call or "" for the default partition
* @param pcTaskName The name of the task class
* @param pcMethodName The name of the business entity method to invoke
* @param phDataset1 INPUT-OUTPUT DATASET-HANDLE The handle of the first dataset to be passed to the task method
* @param phDataset2 INPUT-OUTPUT DATASET-HANDLE The handle of the second dataset to be passed to the task method
* @param phDataset3 INPUT-OUTPUT DATASET-HANDLE The handle of the third dataset to be passed to the task method
* @param phDataset4 INPUT-OUTPUT DATASET-HANDLE The handle of the fourth dataset to be passed to the task method
* @param phDataset5 INPUT-OUTPUT DATASET-HANDLE The handle of the fifth dataset to be passed to the task method
* @param poParameter The serializable parameter object to the method
* @param phContextDataset The handle of the context dataset for this call
* @return The return object of the method
*/
METHOD PUBLIC Progress.Lang.Object InvokeTask2 (pcPartition AS CHARACTER,
pcTaskName AS CHARACTER,
pcMethodName AS CHARACTER,
INPUT-OUTPUT DATASET-HANDLE phDataset1,
INPUT-OUTPUT DATASET-HANDLE phDataset2,
INPUT-OUTPUT DATASET-HANDLE phDataset3,
INPUT-OUTPUT DATASET-HANDLE phDataset4,
INPUT-OUTPUT DATASET-HANDLE phDataset5,
poParameter AS Progress.Lang.Object,
phContextDataset AS HANDLE) .
The Consultingwerk.OERA.ServiceInterface class also adds new InvokeTask2 methods. An overload accepting a {{LONGCHAR}} value for a parameter object is included since the new InvokeTask2 methods may be passed objects that only implement _Consultingwerk.ISerializable_,
/**
* Purpose: Invokes a method in a Task class.
* Notes: When no MethodName is passed then "Invoke" will be executed as the
* default task method
* @param pcTaskName The name of the task class
* @param pcMethodName The name of the method of the task to execute
* @param piNumDatasets The number of datasets that were passed in from the consumer
* @param phDataset1 INPUT-OUTPUT DATASET-HANDLE The first dataset-handle parameter to the task method
* @param phDataset2 INPUT-OUTPUT DATASET-HANDLE The second dataset-handle parameter to the task method
* @param phDataset3 INPUT-OUTPUT DATASET-HANDLE The third dataset-handle parameter to the task method
* @param phDataset4 INPUT-OUTPUT DATASET-HANDLE The fourth dataset-handle parameter to the task method
* @param phDataset5 INPUT-OUTPUT DATASET-HANDLE The fifth dataset-handle parameter to the task method
* @param poParameter The parameter object
* @return The optional return value object of the Business Task Method. If the task method does not return an
* object, then the parameter object is returned.
*/
METHOD PUBLIC STATIC Object InvokeTask2 (pcTaskName AS CHARACTER,
pcMethodName AS CHARACTER,
piNumDatasets AS INTEGER,
INPUT-OUTPUT DATASET-HANDLE phDataset1,
INPUT-OUTPUT DATASET-HANDLE phDataset2,
INPUT-OUTPUT DATASET-HANDLE phDataset3,
INPUT-OUTPUT DATASET-HANDLE phDataset4,
INPUT-OUTPUT DATASET-HANDLE phDataset5,
poParameter AS Progress.Lang.Object).
/**
* Purpose: Invokes a method in a Task class.
* Notes: When no MethodName is passed then "Invoke" will be executed as the
* default task method
* @param pcTaskName The name of the task class
* @param pcMethodName The name of the method of the task to execute
* @param piNumDatasets The number of datasets that were passed in from the consumer
* @param phDataset1 INPUT-OUTPUT DATASET-HANDLE The first dataset-handle parameter to the task method
* @param phDataset2 INPUT-OUTPUT DATASET-HANDLE The second dataset-handle parameter to the task method
* @param phDataset3 INPUT-OUTPUT DATASET-HANDLE The third dataset-handle parameter to the task method
* @param phDataset4 INPUT-OUTPUT DATASET-HANDLE The fourth dataset-handle parameter to the task method
* @param phDataset5 INPUT-OUTPUT DATASET-HANDLE The fifth dataset-handle parameter to the task method
* @param plcParameter The LONGCHAR representation of the serialized parameter object
* @return The optional return value object of the Business Task Method
*/
METHOD PUBLIC STATIC Object InvokeTask2 (pcTaskName AS CHARACTER,
pcMethodName AS CHARACTER,
piNumDatasets AS INTEGER,
INPUT-OUTPUT DATASET-HANDLE phDataset1,
INPUT-OUTPUT DATASET-HANDLE phDataset2,
INPUT-OUTPUT DATASET-HANDLE phDataset3,
INPUT-OUTPUT DATASET-HANDLE phDataset4,
INPUT-OUTPUT DATASET-HANDLE phDataset5,
plcParameter AS LONGCHAR).
SCL-3806 Implemented session wide event when SmartObjectMaster is added to the modified list
Description:
We have implemented the ISmartModifiedStatePublisherService and the SmartModifiedStateChanged event. This event can be used to perform custom actions (e.g. dumping of the .smartrepo file or SCM actions) whenever a object master is modified in the SmartFramework repository.
SCL-3830 Implemented ReloadService Functionality in ServiceContainer
Description:
We have added a new method ReloadService in the IServiceContainer interface and ServiceContainer implementation. This method can be used to replace the instance of a service with a new instance of the same type. The ServiceContainer will DYNAMIC-NEW the service based on the default constructor (no parameters) and deregister the existing service instance and register the new service instance.