...
SCL-3429 Resolved issue with ServiceManager:IsInCallStack when not using the ServiceNameMappingService
Description:
We have resolved an issue in the Service Manager that customers might have faced when not using a ServiceNameMappingService implementation. The issue might have through an invalid object reference error at runtime when using DatasetModels with the UseInterface value of "UnmanagedWhenInCallStack".
Improvement
SCL-3426 Implemented meaningful error message when Proparse cannot write to prorefactor/temp
Description:
When Proparse was not able to write to files in the prorefactor or prorefactor/temp previously a Java null pointer exception has been raised.
We're now raising a more meaningful error message.
SCL-3427 Implemented support for new records in SmartBusinessEntityAdapter:HandleBufferQuestions
Description:
We have implemented support for deleted records when handling questions raised by the Backend Validation logic.
SCL-3428 Added support for BY-REFERENCE Datasets in BusinessEntity:FetchRelatedRecords
Description:
The BusinessEntity method FetchRelatedRecords can now also be used from an invokable method that has been called with a BY-REFERENCE dataset.
SCL-3430 Additional Deployment Datasets have been defined for the export utility
Description:
We have defined additional deployment datasets in the
Consultingwerk/SmartFramework/Tools/deployment-datasets.json
file. These dataset definitions serve the user interface to import and export SmartFramework metadata and as a starting point for automation routines developed by customers using the Generic Data Importer and Exporter.
New Feature
SCL-3425 Implement new DatasetHelper:DeleteOrphanedRecords API
Description:
We have added a new API in the DatasetHelper:
DatasetHelper:DeleteOrphanedRecords (phDataset) deletes records in all child tables.
DatasetHelper:DeleteOrphanedRecords (phBuffer) deletes records in that child table (should be called on a child table, not the parent table).
Orphaned records are child records where the parent record does not exist in the Dataset.
SCL-3431 Support for single record/group by dump and load of SmartFramework data
Description:
When dumping and loading SmartFramework data using a JSON configuration file we do now support to dump from a single Business Entity to multiple files based on grouping by unique record values. Grouping is supported for up to nine fields of the first dumped table.
Dumping to multiple files is controlled by a JSON object FileNamePattern which is used as an alternative to the FileName character property. So an entry in the JSON file like this:
| Code Block | ||
|---|---|---|
| ||
{
"Description": "Messages",
"BusinessEntity": "Consultingwerk.SmartFramework.System.MessageBusinessEntity",
"SkipFields": "",
"Tables": "*",
"QueryString": "FOR EACH eSmartMessage WHERE eSmartMessage.LanguageGuid = '' AND eSmartMessage.MessageGroup <> 'TEST' BY eSmartMessage.MessageNumber",
"FileName": "Test/data/smartmessages-full.xml"
}
|
dumps all Smart Messages into a single file. Two entries like this:
| Code Block | ||
|---|---|---|
| ||
{
"Description": "Messages",
"BusinessEntity": "Consultingwerk.SmartFramework.System.MessageBusinessEntity",
"SkipFields": "",
"Tables": "*",
"QueryString": "FOR EACH eSmartMessage WHERE eSmartMessage.LanguageGuid = '' AND eSmartMessage.MessageGroup <> 'TEST' BY eSmartMessage.MessageNumber",
"FileNamePattern": {
"ExportFileName": "Test/data/smartmessages/&1.xml",
"GroupByFieldNames": [
"MessageGroup"
],
"ImportFileNamePattern": "Test/data/smartmessages/*.xml"
}
},
{
"Description": "Messages",
"BusinessEntity": "Consultingwerk.SmartFramework.System.MessageBusinessEntity",
"SkipFields": "",
"Tables": "*",
"QueryString": "FOR EACH eSmartMessage WHERE eSmartMessage.LanguageGuid > '' AND eSmartMessage.MessageGroup <> 'TEST' BY eSmartMessage.MessageNumber",
"FileNamePattern": {
"ExportFileName": "Test/data/smartmessages/&1-&2.xml",
"GroupByFieldNames": [
"MessageGroup",
"LanguageGuid"
],
"ImportFileNamePattern": "Test/data/smartmessages/*.xml"
}
}
|
Will dump all messages with no specific language (LanguageGuid = "") into files named by the MessageGroup (GroupByFIeldNames array and FileNamePattern with &1) and all messages with a specific language into files by langage and by group (GroupByFieldNames with two values and FileNamePattern with &1 and &2).
File Names will be
OpenEdge.xml, VALMSG.xml, SFR.xml and SFR-DE.xml, SFR-FR.xml, SFR-NL.xml.
Info: The LanguageGuid will automatically be replaced by the language ISO code.
This example here dumps the SmartBusinessEntity configuration into individual files, one per SmartBusinessEntity Name and Package, SmartBusinessEntityTable is contained in the SmartBusinessEntity XML files:
| Code Block | ||
|---|---|---|
| ||
{
"Description": "SmartBusinessEntity Definitions",
"BusinessEntity": "Consultingwerk.SmartFramework.System.SmartBusinessEntityBusinessEntity",
"Tables": "*",
"QueryString": "FOR EACH eSmartBusinessEntity WHERE NOT eSmartBusinessEntity.BusinessEntityPackage BEGINS 'Consultingwerk.SmartComponentsDemo'",
"FileNamePattern": {
"ExportFileName": "Test/SCL3431/data/smartbusinessentity/&1.&2.xml",
"GroupByFieldNames": [
"BusinessEntityPackage",
"BusinessEntityName"
],
"ImportFileNamePattern": "Test/SCL3431/data/smartbusinessentity/*.xml"
},
"SkipFields": "TrackDeletions"
}
|
When loading data via JSON, the FileNamePattern object contains the ImportFileNamePattern. This pattern controls which XML files are loaded.
The new structure in the JSON file is supported both by the
- Consultingwerk/SmartFramework/Tools/Export/release-data-from-json.p
- Consultingwerk/SmartFramework/Tools/Import/import-data-from-json.p
procedures and the class files
- Consultingwerk.SmartFramework.Tools.Export.GenericDataExporter
- Consultingwerk.SmartFramework.Tools.Import.GenericDataImporter