On this page:
|Summary: CAST AIP 8.3.1 introduces a number of features and changes as listed below. To view the impacts of these changes on analysis results, see: Changes in results post upgrade.|
Technology support changes
Although the CAST AIP upgrade guide prioritises the use of CAST Server Manager to complete all upgrade processes through the new "Upgrade Combined Installation" option, the functionality introduced through this option is still in its infancy and the CAST AIP 8.3.1 release does not contain all required configuration files.
Therefore, to upgrade to CAST AIP 8.3.1, please continue to use the "legacy" method described in Step by step upgrade process - workaround method as follows:
However, if you wish to experiment with the new "Upgrade Combined Installation" option in CAST Server Manager, please contact Laurent Windels for more information before starting.
Remove one or multiple older snapshots
If you remove an older snapshot (i.e. not the most recent) then the next snapshot will be updated:
Update Capture Date
If you update the capture date, three snapshots will be updated:
For these three snapshots, CAST AIP will:
If the snapshot you updated was previously the latest, source code and object properties will be removed from the CAST Dashboard Service schema (as they no longer match with the new latest snapshot). Data in the CAST Analysis Service will remain as before. Therefore data in the two schemas will no longer correspond.
Example of impact of changing the capture date:
If three snapshots exist as follows:
An object <OBJECT_LAST> was added in snapshot S3, and so it is marked as ADDED in the snapshot S3 because it was not there in the previous snapshot S2. If the functional date is now changed as follows (capture date changed on S3):
then the snapshots are reordered as follows:
<OBJECT_LAST> will still be marked as ADDED in the snapshot S3 which is no longer the latest snapshot because its functional date has been updated. S2 is now the latest snapshot and it is compared to the previous snapshot which is now S3. Because object <OBJECT_LAST> wasn't present in the S2 snapshot, then it will be shown as 'DELETED' in S2 when compared to S3, even though <OBJECT_LAST> is part of the most recent analysis and version of the source code that exists in the CAST Analysis Service schema.
|Consolidate an older snapshot|
If you reconsolidate an older (i.e. not the most recent), then the next snapshot will be updated:
|Snapshot generation with a capture date that is before an existing snapshot|
If you generate a snapshot, with a capture date that is before an existing snapshot, the existing snapshot will be updated:
Health Dashboard / Engineering
Dashboard / Rest API
User authentication / data authorization
An error in the example given in the roles.xml file (delivered with CAST Application Analytics Health Dashboard / Engineering Dashboards Dashboard and the Rest API) for configuring roles for LDAP groups has been corrected. In addition, the documentation has been updated as a result. The following pages have therefore been updated:
- CAST-AAD HD - Configuring user authenticationCAST
- HD - AAD - Configuring data authorization
- CASTED - AED - Configuring user authenticationCAST
- ED - AED - Configuring data authorization
Configurable Technical Size indicators
It is now possible to customize the list of Technical Size indicators (Number of Critical Violations, Number of Code Lines, Number of Files etc.) that are displayed for the drill down page available at Application level for the Technical Size tile (click to enlarge):
See CASTHD - AAD - Tile management for more information.
Tile management for more information.
Can't access link
The "Can't access" link that was previously available by default on the login screen (this link enables a user who is not able to log in - for example because they have forgotten their login credentials or if they have not yet been granted access - to send an email to the dashboard administrator requesting access) has now been removed by default. If you want to re-enable this option, please set the "requestAccess" option to true in the cmp.json file. See HD - Dashboard wide configuration options in json for more information.
Reset language option
The top user menu now has an additional drop down menu item called "Reset language". This allows a user to change the language of the text items in the dashboard, providing an administrator has configured the language:
Violation details section
A new section has been added to the Source Code display called Violation details to display Violation Name along with the values of the Violation Details (i.e the "Associated Values"). See CAST Application Engineering Dashboard - CAST AED.
Change in behaviour of Risk Introduced tile
A new Education tab has been added alongside the existing Action Plan and Exclusion tabs. This tab is designed to list Quality Rules for which particularly bad practice has been seen through violation investigations. Quality Rules can be added to the list to promote best practices or for monitoring purposes.
|Note that this feature while present in CAST AIP 8.3.1 is not fully functional and should not be used. It will be available for use in CAST AIP 8.3.2.|
Can't access link
The "Can't access" link that was previously available by default on the login screen (this link enables a user who is not able to log in - for example because they have forgotten their login credentials or if they have not yet been granted access - to send an email to the dashboard administrator requesting access) has now been removed by default. If you want to re-enable this option, please set the "requestAccess" option to true in the ced.json file. See ED - Dashboard wide configuration options in json for more information.
CAST Management Studio
It is no longer possible to configure the weight and criticality of an Architecture Model's associated Quality Rule in the CAST Management Studio (previously this was possible in the Architecture Model editor or in the Architecture Models tab of the Application editor. Weight and Criticality are now configured directy in CAST Architecture Checker. See GUI: configuring model properties below.
In an upgrade scenario:
Items updated here will then be visible in the CAST Application Engineering Dashboard (click to enlarge):
CAST Transaction Configuration Center
Transaction Graph Adjustment feature now taken into account for Transaction Risk Index (TRI) computation
The Transaction Graph Adjustment feature introduced in CAST AIP 8.3.0 is now taken into account during the computation of Transaction Risk Index (TRI) and during Function Point computation. In CAST AIP 8.3.0, it was only taken into account during Function Point computation.