Loading color scheme

Boston v7.0 - Release Notes

Boston Professional v7.0 Release Notes

Boston Professional v7.0 is a patch release to Boston Professional v6.6
Release Date: 29th May 2023

A summary of the main commits follows:

- Implemented Model Settings in ReferenceFieldTable/Value tables;
- Refining the management of data for Neo4j databases;
- Implemented Model Settings in ReferenceFieldTable/Value tables;
- Implementing ability to view and add Edges on Edge Types for Neo4j/Graph databases;
- Refined how FactInstances are loaded for FactTypeInstance on Pages when XML stored Models load;
- Implementing BinarySerialiser for Model serialisation;
- Implemented Binary Serialisation/Deserialisation of Models;
- Implemented RecordsetProxy to move Boston to SQLite;
- Implementing GenericRecordset and SQLiteRecordset classes to move to Boston running over an SQLite database;
- Introduced Data Lineage to Boston;
- Glossary view improvements;
- Fixed DBName property for RDSTable. Was returning empty string in some circumstances;
- Created Code Generator template for Data Vault for SQLite. Can be used as a reference for other database types;
- Added Properties Table display for Entity Types and Objectified Fact Types on the frmDiagramORM form. i.e. can now see the table/attributes for an Entity Type and Objectified Fact Type from within the ORM diagram view;
- Bug Fix: Tidied up DBName for columns in FactEngine SQL queries;
- Improved and refined Derived Fact Types, for database table Columns;
- Improvements to removing Attributes/Properties from Entities/Node Types. More checking is done to see that the removal of the Attribute/Property will not effect related model elements;
- Navigation improvements from within the Model Dictionary;
- Improvements to Verbalisations and navigation between Model Dictionary, Diagram Spy and Verbalisation Toolbox;
- Introduced Column/Property mismatch error. CMML - Difference between RDS Columns on Table and actual database Columns/Properties;
- Made it easier to navigate around the Property Graph schema view. Able to jump to Model Dictionary for Node Type, for example;
- Adding Relational.AI Database Connection Manager;
- Added error checking to the FEKL Uploader to check that Fact Type Names are not longer than 100 characters;
- Navigation improvements on Attributes and Properties to the various toolboxes in Boston;
- Added error checker, tErrorChecker140CMMLModelError.vb
- Added CMML (Common MetaModel Language) errors to error list;
- Column Name creation on import of NORMA file now more in line with Column Names (for Entities) as in NORMA;
- Fixed Duplex Service bug when creating a Fact Type using the Virtual Analyst. Had circular broadcast;
- Fixed bug where loaded NORMA models, in Client/Server configuration, were not being saved to a model.
- Added a new Model Fix Type. ObjectifiedFactTypesWithNoCorrespondingRDSTable;
- Can now create PGS and ORM Pages from an ERD Page;
- Can now create Entities on an ERD Page from the Toolbox;
- FactEngine: Improvements to FEQL for Cypher;
- Improvements to ERD drawing on the frmDiagramERD form;
- FactEngine: Improvements to the FactEngine parser. Introduction of math functions. Introduction of COUNT(DISTINCT...) type clauses;
- FactEngine: Updates to generation of SQL and Cypher;
- FactEngine - Improved parser and implemented Math Functions;
- Improvements to FEQL. Implementing math functions on/over domains/columns/properties;
- Fact Type Readings - Fixed bug where the Fact Type Reading was not showing for Fact Types on Page;
- ORMQL Recordset is now an enumerator;
- Better error messaging in tableORMReferenceFieldValue, GetReferenceFieldValueTuples;
- Update to Wildcard Operators for databases in publicDatabase, getLikeWildcardOperator;
- RDSColumn: NodeModifierFunction added to Equals;
- FactEngine: FEQL: Improvement to getAndSetFBMFactType in QueryEdge;
- FactEngine: FEQL: Implemented Math Function in QueryEdge;
- FactEngine: FEQL: Changes to QueryGraph in tune with introduction of the new CountClause (allowing COUNT(DISTINCT...) type queries;
- FactEngine: FEQL: QueryNode now inherits from tQueryFormulaToken;
- FactEngine: FEQL: Math functions in QueryNode now moved to Formula in QueryEdge;
- FactEngine: FEQL parsing. Introduced QueryFormulaToken. QueryNodes can be formula under certain circumnstances;
- New FEQL parser classes introduced to Boston;
- Small change in tSQLite.vb database manager;
- Can now set the data for Foreign Key Relationships through the GUI using the Table Data Toolbox;
- Added new error type - 131 - Population contains NULL value error;
- Improvements to FactEngine for SQL;
- FEQL Parser now includes SUM and AVG modifier functions;
- Fact Type Readings for ManyToOneBinaryFactTypes from/to the same Object Type, now have the first Fact Type Reading for the Fact Type with the first Role that with the Internal Uniqueness Constraint;
- FactEngine: Implemented MONTH an YEAR modifier functions;
- Transitioning 'String...' data types in FEKL to 'Text...' data types. 'String...' syntax is still valid for now. E.g. 'StringFixedLength' when used is converted to the TextFixedLength data type;
- FactEngine: Implemented Time, Date, ToLower, ToUpper node modifier functions in FEQL, FactEngine Query Language, parser. Mostly complete for SQL generator;
- FactEngine: Standardised code structure for FactEngine for Services;
- FactEngine: Improvements to Cypher query generation for FactEngine;
- FactEngine: Introduced DATE node modifier to FEQL;
- FactEngine: Introduced TODAY function to FEQL/FEKL;
- FactEngine: Bug fixes FEQL to Cypher;
- Added GPT3 Nl-2-FEQL processing to FactEngine;
- Improvements to the FactEngine parser and FactEngine Cypher generation;
- Fixed bug in reverse engineering a SQLite database. Single column primary key column names were being truncated to their associated Entity Type Reference Mode;
- Multi column filtering on the Table Data Toolbox now available;
- Minor bug fixes;

Known Issues:
--------------------
- FactEngine doesn't cater for unary fact types in all cases at this stage

--------------------------------------------------------------------------------------------------------------------------
     End of Document
--------------------------------------------------------------------------------------------------------------------------