...
SCL-3559 The RestEntitiesWebHandler builds a FetchDataRequest using the QueryExpressionWithSort property when enabled in the Business Entity
Description:
If a Business Entity implements the Consultingwerk.OERA.ISupportsQueryExpressionWithSort interface, the Consultingwerk.OERA.RestResource.RestEntitiesWebHandler webhandler will construct fetch data requests using the QueryExpressionWithSort property rather than using the string-based Queries property.
If a Business Entity does not implement the Consultingwerk.OERA.ISupportsQueryExpressionWithSort interface, the default behaviour continues to be to build a query string and populate the fetch data request’s Queries property.
SCL-3791 Reduced code-duplication between DynamicControlGroup and DynamicForm rendering
Description:
To improve maintainability of our code base we have reduced code duplication between the rendering of DynamicControlGroup and DynamicForm repository objects.
SCL-4068 Implemented alternative SmartComponent Library Desktop
Description:
We have implemented an alternative SmartComponent Library Desktop as the carrousel of the initial SmartComponent Library desktop became less usable with a large number of tools added. The new desktop can be launched in the same way as the previous desktop - the startup procedure is called Consultingwerk/Studio/Desktop/start2.p
Note: This feature relies on an additional Telerik .NET Assembly:
<assembly name="Telerik.WinControls.Themes.VisualStudio2012Dark, Version=2021.2.615.40, Culture=neutral, PublicKeyToken=5bb2a467cbec794e"/>
SCL-4155 Custom tags can be added to RESTful annotations and business services
Description:
Tags can be added to RESTful annotations and business services, to group endpoints and/or services meaningfully in the Swagger documentation generated by the Consultingwerk.OERA.Swagger.SwaggerRestEntitiesWebHandler webhandler, typically used for the /SwaggerEntities endpoint.
Tags can be added as a comma-separated value to any RestAddress and RestMethod annotations, using a new tags attribute. These tags apply to the documentation generated for those endpoints. If no tags are specified, the default tags for the business service are used: the business service class name. If multiple tags are used, the endpoint(s) will appear in multiple groups.
The same tags can be used by multiple business service endpoints, allowing logical grouping of services in the Swagger documentation.
For example, adding the tags=”Customers” attribute as below will ensure that the GET, DELETE and POST endpoints, as well as the GET /Count endpoint, will be in a Customers group in the Swagger documentation.
| No Format |
|---|
@RestAddress (type="collection", address="/SCL4155/Customers", tables="eCustomer", id="CustNum",
tags="Customers",
fields="Name,City,Country",
canRead="true", canCreate="true", canDelete="true",
links="orders:/Customers/~{CustNum}/Orders,openOrders:/Orders?CustNum=~{CustNum}&&orderstatus=ordered,salesrep:/Salesreps/~{SalesRep}"). |
The default tags used for all the endpoints described in a service can be provided by means of a new annotation, @ApiDoc . This annotation supports a single attribute named tags, which work in the same way as those added to the RestAddress and RestMethod annotations.
| No Format |
|---|
@ApiDoc(tags="Customers"). |
In addition, details for these tags can be provided in a file. The location of this file is specified in the .restapplicationsettings file. Information in this file includes the tag name and a description of the tag, and optionally information about an external documentation URL.
For example,
| Code Block |
|---|
{
"pets": {
"description": "Everything about your Pets",
"url": "http://docs.my-api.com/pet-operations.htm",
"urlDescription": "Click here for pet info"
},
"store": {
"description": "Access to Petstore orders",
"url": "http://docs.my-api.com/store-orders.htm",
"urlDescription": "Click here for store info"
}
} |
If no tag detail is avaiable (eg no configuration provided, or the file cannot be found), the tag values are still used for grouping services. Details on configuring the file location are at https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/1989509121/Providing+Swagger+tag+descriptions .
Additional information can be found at https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8094254/Support+for+RESTful+invocation+of+Business+Task+and+Business+Entity+Methods and https://consultingwerk.atlassian.net/wiki/spaces/SCL/pages/8094560/RESTful+services .
SCL-4166 GenericDataImporter in GUI now provides option to disable RI checks
Description:
The GUI frontend for the GenericDataImporter (Import/Export SmartFramework metadata) now provides an option to disable the referential integrity checks of the SmartDataAccess classes during the import. The option is settable from a checkbox in the import wizards.
SCL-4167 TableAndFieldStaticClassGeneratorPlugin now checks to create target directory
Description:
The Business Entity Designer plugin now checks if it needs to create the target folder. Previously the plugin failed when the target folder was not available. The functionality is based on a new API in the FileHelper class: CreateDirectoryForFile
SCL-4174 Improved error message when fetching repository objects with orphaned SmartObjectInstance records
Description:
We have improved the error message raised when fetching repository objects fails due to orphaned object instances (instance records pointing to an invalid object master guid).
The error message now includes the name of the instance causing the issue.
SCL-4175 Export/Import Menu structure from GUI now work with an AppServer connection
Description:
The Export/Import Menu structure from GUI now work in a thin client session connected to an AppServer. The improvement is based on a new general purpose business task that supports invoking methods of custom objects on the AppServer remotely: Consultingwerk.OERA.DynamicInvokeBusinessTask
SCL-4177 Supporting BufferHelper:FindDatabaseBuffer for database buffers that are not source-buffer of a Data-Source
Description:
We’re now supporting the BufferHelper:FindDatabaseBuffer for database buffers that are not source-buffer of a Data-Source. Previously the method fetched the KEYS attribute of the buffer from the DATA-SOURCE object handle. Now we’re fetching the attribute directly from the BUFFER object handle.
SCL-4178 New GUID for the "Toolbar" SmartLinkType record in the repository
Description:
Due to a conflict with a customer’s application that had already added a SmartLinkType record named “Toolbar” we’ve had to update the GUID of the SmartLinkType reocrd that we have recently introduced. The SmartDB update and migration routine has been enhanced with a routine that updates the LinkTypeGuid from "e3fb1251-e65b-d5a0-ae14-1b265c7998ed" to "f52235a4-c120-2490-3814-9d291ca82acc" in the SmartLinkType, SmartSupportedLink and SmartLink database tables.
It is mandatory to execute the SmartDB update and migration routine against every SmartDB that previously had loaded the release from June 18th of newer.
Customers may observe that containers using the “Toolbar” link are indicated as modified and will be dumped by the data versioning scripts.
New Feature
SCL-3986 Implement support for rendering "enabledState" setting on Smart Fields in Angular Viewers
Description:
The rendering of Angular viewers now includes rendering of the three enabled states for components in the viewer: Add, Copy, Update
SCL-4070 Implemented support rendering for components of type "custom" in Angular Smart Viewer and Smart Frame
Description:
Rendering support for custom components has been added to Angular viewers and smart frames. The rendering is based on the placeholderId attribute.
SCL-4074 Added an Outline View to Repository Viewer Designer
Description:
To improve usability of the viewer designer for large repository based designs we have added an Outline View to the viewer designer. The outline view can be accessed from a Button in the contextual ribbon of the designer.
SCL-4176 SmartDataAdapter's ParentPositionChangedBase method now check for validity of SmartDataSource
Description:
The ParentPositionChangedBase method of the SmartDataAdapter class can be used to signal linked data adapters, that the current SmartDataAdapter instance points to a different record (e.g. after opening the client side query). However in case of a SmartDatasetAdapter that has no SmartDataSource, this meathod did lead to closing the current adapter’s query.
This issue is now resolved.