Page tree
Skip to end of metadata
Go to start of metadata

1.4.0

New features

FeatureDescription
Transactions and Function Points tables are now sorted by most important information

In Transactions section, Transactions table is sorted to show invalid transactions first. Data entities table is sorted by object type. The rule tables are sorted on the number of captured objects to show rules that captured objects first.
In Function Points section, Transactional Functions table and Data Functions table are sorted on the FP column to show 0 FP elements first.

Export Transactions and Function Points tables contentThe user can now export the content of tables in CSV files.
User can see the objects captured by a specific type of ruleIt is now possible to show in one click the list of objects captured by all the rules belonging to the same category of rules (ex: entry points).
Free Definition Rule Editor

Preview of the rule editor.

  • User can click the "view" icon to enter the Free Definition editor.
  • User can click the "Edit" switch to activate the edition mode.

User can:

  • add/edit/remove selection criteria
  • add/edit/remove property blocks on name, full name, path, and type
  • add/edit/remove member-of/excluded-from blocks
  • save or discard his work

User can edit the rule attributes from the list of rules, by clicking the Edit action.

Limitation of the preview: it is not possible to create and update generic sets.

User can upload Architecture Checker models into analysis nodes

User can upload models but can also remove them from the system. Models are visible from application configuration page and are shared between all applications hosted on the same analysis node.

Only models that are not attached can be removed from an analysis node.

User can attach an Architecture Checker model to an application

User selects a model from the list of models that have been uploaded and attaches it to the application. He can also detach a model from the application.

Attached models will be used to compute snapshots for the applications.

Extension

management by application
  • Automatic detection of extension to be used based on DMT discover
  • Definition of list of Extensions by domain
  • Display list of included extension & versions by application version
  • Add new available extension
Application Summary filtering options

Filter application by status (ongoing/failed/pending analysis).

Display of Reports after Analysis based on Report Extension

It is possible to display reports that have been implemented by Extension.

DMT Report

DMT Report displays directly in AIP Console.

DMT authentication update

New mechanism used when downloading DMT on local machine to avoid using user/password.

Cancel ongoing Analysis

If analysis is running, new action available to stop it.

Configuration improvement

New explorer to support management of files for configuration on Analysis node. Useful for JEE and C/C++ analysis configuration.

AIP License update

Update CAST AIP License in admin area

Log Improvement

Logs can be investigated once the step is done, no need to wait for the end of the analysis (job).

Domain Improvement

Admin user can create a domain without having to create an application.

Known issues

IssueDescriptionWorkaround
DMT (CAST Delivery Manager Tool) fails to launch.

When attempting to download and launch the DMT, the following error occurs:

Edit the Java JRE settings to ensure that cached files are not saved locally:

Click to enlarge:

WEBI-2718

Performance issue observed in loading and also when navigating from one application to another application in Transaction and FP pages.-
WEBI-2791Front-end notification system does not show "Compute Function Points" job name in notifications.-
-"Extension Discovery Service" is not available by Extension or public internet access. It can be used internally to CAST only or can be deployed based on a github project.-
WEBI-3339Analysis always fails if an Application contains some UA type Analysis Units, such as Shell, TIBCO etc.
  1. Deliver the first version, select the corresponding UA Extensions, import the version and run the analysis. Here, the Analysis will fail (because of missing languages) but the UA extensions will be installed.
  2. Create a second version, import it and run the analysis/snapshot. This time it will work.

Currently, the AIP Console doesn’t support an Application which is created from CMS, so the feature to import an existing Application into the AIP Console does not currently work.

-

Limitations

LimitationDescriptionWorkaround
CMS-API cannot be configured as a Windows serviceWhen running CMS-API as a service (using Install-CMSAPI-Service.bat), any application declaration will fail Run the API using the runCMSAPI.bat script. It requires leaving a user session opened at all times on the installation server
Only one application can be declared or deleted at the same timeParrallel actions not yet supported for Application declaration.None.
Navigation to AED for an application which has no snapshotNavigation to AED for an application which has no snapshot will fail, since this application is not yet known by AED.None.
It is not possible to modify a Universal analysis unitDeleting an Universal analysis unit or modifying it (adding/removing languages) is not possibleUsing legacy CMS.
Application template limitations
  • Using application template disables the default extension installation by AIP 8.3.0
  • Putting an extension in the template does not automatically selects its dependencies, so application creation fails
  • Put the the list of default extensions in the template file (forced_install.xml file)
  • Put all dependencies in the template file

Requirements

See Deployment requirements.

How to report issues and feedback

Please report and issue or feedback to the product manager, Damien Charlemagne (d.charlemagne@castsoftware.com).

  • No labels