1.0.6

Updates

SAPBOA-58 - A change has been implemented in preparation for the future support of encrypted SSL connections to CAST Storage Service/PostgreSQL.

Internal ID	Ticket ID	Description	Impact?
SAPBOA-51	20286	Crash during an analysis with the error [Error in Analysis:The program ExternalLinkCommandLine has not ended correctly]	A bug in the analyzer (the ID for BO Condition objects was not being correctly populated) was causing the ID of the most recent object analyzed to be used when a BO Condition object was encountered. This caused the analysis to crash in error. This bug has now been fixed.

SAPBOA-34 - A change has been implemented to introduce a connectivity layer compatible with PostgreSQL 10 and 11.

Internal ID	Call ID	Description	Impact?
SAPBOA-45	16340	Missing links between BO Objects and Oracle Objects	Direct links between BO Universes and database tables are no longer displayed Instead, links now go from BO Universes via the BO object (BO Dimension, BO Detail, BO Measure) to the database table Transactions will be impacted Currently no bookmark is available for the links between the BO objects and the database table (will be fixed in future release)
SAPBOA-40	16069	BO Wrong description - AFP stands for Automated, not Automatic	-
SAPBOA-39	16078	Missing flow from BO Universe to the Oracle database	BO Universes are no longer classed as Transaction entry points in CAST Transaction Configuration Center Instead, BO Classes without sub-classes are now Transaction entry points in CAST Transaction Configuration Center Transactions will be impacted

Internal ID	Call ID	Description	Impact?
SAPBOA-32	14424	BO Class objects should not be set up as entry points in TCC	In previous releases of the analyzer, SAP BusinessObjects classes were configured as the entry point for transactions through to the database objects. However, this was incorrect since there is no "flow" from a class through to the database. This bug has now been fixed and SAP BusinessObjects universes are now set as the entry point for transactions through to the database. Therefore, after an upgrade to this release of the extension and the generation of a post upgrade consistency snapshot on unchanged source code, results may be impacted: Function Point values may change.