Compatibility matrix
| Component | Required release | Notes |
|---|
| Installer for embedded dashboards (when using standalone or Windows JAR installers) | 2.11.2-funcrel | You must use the installer provided with the current release of Console, otherwise there is no guarantee of compatibility. |
|---|
| CAST Imaging | ≥ 2.5.2-funcrel | - |
|---|
.
2.9.2-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 42905 | Fixes an issue where after migrating several applications from Console V1 to V2 and manually updating the Deployment folder path, some of the applications fail the Resync action. |
2.9.1-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 42099 | Fixes an issue that occurs when Console (Enterprise mode) has two or more nodes configured to use an Extend Local Server, and where a change has been made in a bundle which is then uploaded to Extend Local Server: one or more of the Nodes keep failing to connect to Extend Local Server because their Extend API key stored in the "aip_node" schema in the "settings" table is corrupt due to the presence of unusual characters. |
| 42586 | Fixes an issue where the standalone "Log Service" provided in Enterprise and Standalone modes was consuming excessive amounts of CPU resources, even when the associated Node was not running a Console job. |
| 42629 | Fixes an issue where attempting to run the Enterprise mode "Service Registry" installer in CLI mode on a Linux server results in the error "SEVERE: com.izforge.izpack.api.exception.IzPackException: Console implementation not found for panel: com.castsoftware.aip.service.registry.installer.panels.ServiceRegistryInstallPanel". |
2.9.0-funcrel
Note
All new features and improvements added in previous 2.9.0 beta releases are also included in this release. See the corresponding release notes for more information.
Other Updates
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 40116 | New applications created in this release and any future release will not be authorized to contain the & (ampersand) character in their name (previous releases accepted this character as valid). This is to ensure that applications can be correctly managed by CAST Dashboards where the use of the ampersand in application names causes issues. If you have existing applications which contain the ampersand character in the name and you are having issues with this application in the CAST Dashboards, you can rename the application and re-run an analysis/snapshot to ensure that the name change is transferred to the CAST Dashboards. See https://doc.castsoftware.com/display/ONBRD/Application+onboarding+with+Fast+Scan+-+onboard+your+application+source+code and https://doc.castsoftware.com/display/ONBRD/Application+onboarding+without+Fast+Scan+-+Add+a+new+Application and for more information about application naming conventions. |
| 33374 | Fixes an issue where, when attempting to create a Reference Finder rule with PHP as the "Source" technology, no PHP "Object Types" are available even though the application in question correctly contains this type of object. |
| 38536 | Fixes an issue where, when attempting to create a Reference Finder rule with PL1 as the "Source" technology, no PL1 "Object Types" are available even though the application in question correctly contains this type of object. |
| 37150 | Fixes an issue where Oracle Forms Reports Analysis Units were not visible in CAST Console for selection when defining a user defined module, or when choosing the "Per Analysis Unit" module strategy. |
| 41563 | Fixes an issue where when attempting to login in to CAST Console, the application home page takes an excessively long time to display. This issue was caused by CAST Console attempting to load assets from the URL "static.zdassets.com" - if access to this URL was not available, the application home page would only display after a timeout period. |
| 41716 | Fixes an issue where the error "Detect Framework Exclusions completed with non-zero error code : 2" is listed in the log viewer during the "Code Scanner/Content Discovery" step. |
| 41661 | Fixes an issue where the number of unanalyzed files in the Analysis Report is not updated on completion of a new analysis, specifically when all the unanalyzed files from the previous analysis are analyzed in the new analysis. |
| 41060 | An update has been made to the documentation regarding instructions for enabling secure access (https) to Console. See https://doc.castsoftware.com/display/AIPCONSOLE/Changing+Console+port+number+-+activating+HTTPS+-+for+Console+2.x. |
| 41881 | A fix has been implemented to ensure that the log file explains clearly why the error "C:\CAST\common-data\ApplicationDeclaration\<app_name>.mavenHttpPackage.xml (The specified file cannot be found). Return value: 1000" has occurred during the "Create package" step (this error typically occurs when a proxy is required by CAST Console and one is not defined and therefore the Maven repository cannot be accessed). In addition, if this error occurs, the job will now fail immediately. |
| 41629 | An update has been made to the documentation regarding instructions for enabling secure access (https) to Console. See https://doc.castsoftware.com/display/AIPCONSOLE/Changing+Console+port+number+-+activating+HTTPS+-+for+Console+2.x. |
| 41394 | Fixes an issue where custom exclusion patterns starting with "-" were ignored by CAST Console, therefore causing additional code to be analyzed which should have been excluded. |
| 41782 | Fixes an issue where, after an upgrade from Console V1 to V2 using the dedicated migration tool, the "Resync" action for an application (available in the Admin Center) failed. |
| 40856 | Fixes an issue present in legacy workflow without Fast Scan: erroneous additional exclusions are added by Console when adding a new version to an analyzed application where exclusions were only configured in the previous version. Note that if duplicate exclusions exist and the application is upgraded to Console 2.8.1-funcrel (or above), the duplicate exclusions will still exist. |
| 41720 | Fixes an issue where Analysis Results Indicator justification comments were lost when moving to a new page within Console. |
| 41816 | Fixes an issue where the Exclude Files mechanism was erroneously excluding files in any folder that contains the name of the exclude pattern, rather than confining the exclusion only to the specific folder configured in the exclude pattern. |
Known Issues
| Internal Id | Details |
|---|
| WEBI-15050 | When using CAST Console with AIP Core 8.3.52 and there are multiple "metrics calculation" job steps within an analysis, it is not possible to distinguish between each distinct step in the log panel because all steps are named "Running metrics calculation". |
| WEBI-15021 | When using CAST Console Enterprise mode in a Docker environment, and after running a new scan on an application that has been moved from legacy to fast scan mode, the warning popup about running a new scan post move to fast scan mode is re-displayed. Cancelling the popup will ensure it is no longer displayed. |
| WEBI-14985 | When a job is running and an alert has been generated and the "View details" option for the alert is clicked, the user is taken to the incorrect line number in the log where the alert was triggered. |
| WEBI-14895 | Logs displayed in the "Log panel" are limited to 3000 lines (for performance reasons) and therefore to view the entire log it is necessary to download it. |
| DASHBOARDS-5039 | When using CAST Console Enterprise mode in a Docker environment, no violations are ever displayed in the "embedded" Engineering Dashboard - the following error is recorded in the developer browser toolbar: "views.js:2288 Uncaught TypeError: Cannot read properties of undefined (reading 'exclusionManager')". |
2.9.0-beta6
Feature Improvements
| Summary | Details |
|---|
| UI - Job Progress Window - Log panel minor improvements | Some minor improvements has been added to the Log panel available in the Job Progress Window: 1) The font size for the left hand section has been reduced, 2) two icons are now used in the left hand section to denote steps and sub-steps, 3) the Alert panel section can now be hidden, 4) the log list and log panel can be re-sized as required, 5) a "Download" button has been added to download the log file, 6) a "Summary" tab has been added to match the layout provided in the standard log panel, 7) each tile for a specific step (such as "Configure", "Analyze", "Upload" etc.) now shows the the last three sub-steps that have been run. See https://doc.castsoftware.com/display/AIPCONSOLE/2.9+-+Onboarding+with+Fast+Scan+-+redesigned+job+progress+screen#id-2.9OnboardingwithFastScanredesignedjobprogressscreen-logLogpanel. |
| UI - Job Progress Window - Alerts for non-UTF-8 files | Alerts are now provided when your source code contains files that are encoded with a character set other than UTF-8 (which can cause problems during the analysis phase). See https://doc.castsoftware.com/display/AIPCONSOLE/2.9+-+Onboarding+with+Fast+Scan+-+redesigned+job+progress+screen#id-2.9OnboardingwithFastScanredesignedjobprogressscreen-NonUTF-8charactersetidentified. |
| Technical - Onboarding with Fast Scan - Automatic conversion to UTF-8 | Additional properties have been made available to control the automatic conversion to UTF-8 feature: pathsInReports, logRetainedFiles, logRejectedFiles, logConvertedFiles, fileExtensionsAdded, fileExtensionsRemoved, preservedEncodings. See https://doc.castsoftware.com/display/AIPCONSOLE/2.9+-+Automatic+UTF-8+conversion+feature. |
| UI - Overview panel (legacy and Fast Scan modes) - Analysis Reports accuracy | A change has been made to ensure that the "Fully Analyzed" and "Not Analyzed" statistics are more accurate: 1) .uax files resulting from CAST Database extractions will now be included in the "Fully Analyzed" count and 2) files which require preprocessing such as .uaxdirectory or PDS Dump files will be included in the "Not Analyzed" count. |
| UI - Job Progress Window - Analysis Alerts - View Issue | The "View Issue" button available for analysis alerts now functions and clicking it will take you to the specific line in the analysis log file where the alert occurred. See https://doc.castsoftware.com/display/AIPCONSOLE/2.9+-+Onboarding+with+Fast+Scan+-+redesigned+job+progress+screen#id-2.9OnboardingwithFastScanredesignedjobprogressscreen-ViewIssue. |
| UI - Job Progress Window - Alerts for unanalyzed files | When an analysis has been completed, CAST Console provides two alerts about files that have not been analyzed: 1) A global alert to cover all unanalyzed files for whatever reason and 2) a specific alert for files that were analyzed and Console is not able to provide a reason. If you receive these alerts, you should investigate why they have been triggered by examining the analysis log files. See https://doc.castsoftware.com/display/AIPCONSOLE/2.9+-+Onboarding+with+Fast+Scan+-+redesigned+job+progress+screen#id-2.9OnboardingwithFastScanredesignedjobprogressscreen-Unanalyzedfilesalerts. |
| UI - Overview panel (legacy and Fast Scan modes) - Analysis Reports - Unanalyzed files | When unanalyzed files are reported in the "Not Analyzed" column, this can be clicked and a dialog box will open listing the files (and their path) that have not been analyzed. Starting from AIP Core 8.3.52, this dialog box will now also provide a reason why the file has not been analyzed, where possible (sometimes there will be no reason and this is generally because the analyzer has skipped them). See https://doc.castsoftware.com/display/AIPCONSOLE/Application+-+Overview+with+Fast+Scan#ApplicationOverviewwithFastScan-AnalysisReports. |
Other Updates
| Internal Id | Details |
|---|
| WEBI-14857 | A minor update has been implemented to ensure that Console now provides the GUID of the current application in the "console_information.json" file. This file is used by the com.castsoftware.consoleinformation extension (https://doc.castsoftware.com/display/TECHNOS/Console+Information+for+Imaging+-+1.0) and the change was implemented to ensure that CAST Imaging is aware which application this refers to if the "name" of the application is changed in CAST Console. This change also ensures that when using CAST Imaging 2.18 (or above) and the renamed application is re-uploaded to CAST Imaging, the existing application in CAST Imaging will be overwritten, rather than creating a "new" application with the new name. |
2.9.0-beta5
Feature Improvements
Other Updates
2.9.0-beta4
New Features
Feature Improvements
Other Updates
2.9.0-beta3
New Features
Feature Improvements
| Summary | Details |
|---|
| UI - Admin Center - Extensions Strategy - Bulk Update | The Bulk Update options have been revamped in this release: instead of tick boxes, it is now possible to bulk enable/disable the Auto Update, Force Install and Blacklist options using buttons. See https://doc.castsoftware.com/display/AIPCONSOLE/Administration+Center+-+Extensions+Strategy. |
| UI - Admin Center - Extensions Strategy - Reset Settings | A new button has been added called "Reset Settings" - this will reset all custom extension strategy settings to the default settings provided by CAST. See https://doc.castsoftware.com/display/AIPCONSOLE/Administration+Center+-+Extensions+Strategy#AdministrationCenterExtensionsStrategy-Resetsettings. |
| UI - Onboarding with Fast Scan - Job step grouping | Changes have been made to the job step grouping in Fast Scan onboarding mode: 1) All job steps related to the legacy Delivery Manager Tool that were previously listed individually under the "Configure" phase have now been grouped together under a new step in the "Configure" phase called "Prepare analysis config" (this includes the following existing steps: Creating package from source, Attaching package to version, Delivering version, Accepting Version, Set as current version). 2) All jobs related to the installation and configuration of the application schemas that were previously listed individually under the "Install" phase have now been grouped together under a new step in the "Install" phase called "prepare environment" (this includes the following existing steps: Create application schemas, Set up Management database, Declare application in Management database). Logging is unaffected and logs for each existing individual step are still available. |
Other Updates
| Internal Id | Details |
|---|
| WEBI-12772 | When delivering and analyzing C++ source code, the .ppc file extension (used in C++ source code) was not correctly mapped in the analyzer config property file, which caused issues. This is now resolved. |
2.9.0-beta2
Feature Improvements
| Summary | Details |
|---|
| Technical - Application naming syntax | New applications created in this release and any future release will not be authorized to contain the & (ampersand) character in their name. This is to ensure that applications can be correctly managed by CAST Dashboards where the use of the ampersand in application names causes issues. If you have existing applications which contain the ampersand character in the name and you are having issues with this application in the CAST Dashboards, you can rename the application and re-run an analysis/snapshot to ensure that the name change is transferred to the CAST Dashboards. See https://doc.castsoftware.com/display/ONBRD/Application+onboarding+with+Fast+Scan+-+onboard+your+application+source+code and https://doc.castsoftware.com/display/ONBRD/Application+onboarding+without+Fast+Scan+-+Add+a+new+Application and for more information about application naming conventions. |
| UI - Architecture Studio - Model Properties for Documentation | When editing the properties of a model before publication, the mandatory fields under the "Documentation" tab are now pre-filled with "TBD" so that the model can be published even if the Documentation is not fully ready. See https://doc.castsoftware.com/display/AIPCONSOLE/AIP+Console+-+Architecture+Studio+-+Publishing+models#AIPConsoleArchitectureStudioPublishingmodels-Step1-Definethemodelproperties. |
| UI - Admin Center - Extensions Strategy | Two new columns have been added to the extension list in the "new" Extension Strategy interface: 1) "Type" to indicate the type of extension (Labs, Product, User Community) and 2) "Changed on" to indicate the last time a property was changed (Auto-install, Version, Force Install, Blacklist). See https://doc.castsoftware.com/display/AIPCONSOLE/Administration+Center+-+Extensions+Strategy. |
| UI - Imaging Settings - Warning for incorrect connection details | CAST Console now provides additional protection/warning for when the CAST Imaging settings (defined in CAST Console) are incorrect: for example the API was regenerated in CAST Imaging but was not updated in CAST Console. Now when this occurs, CAST Console will 1) display a System Alert to indicate the CAST Imaging settings are incorrect, 2) when using the Advanced option to run analysis jobs in Fast Scan mode, the Imaging steps will not be ticked, 3) when using the "Run Analysis" button in Fast Scan mode the Imaging related steps will not be run. See https://doc.castsoftware.com/display/AIPCONSOLE/Administration+Center+-+Settings+-+Imaging+Settings#AdministrationCenterSettingsImagingSettings-BehaviourwhenCASTImagingsettingsareincorrect. |
| UI - Overview panel Fast Scan mode - Tooltip for excluded files | A tooltip has been added to the right-hand panel of the "Zip/Folder Content" section in the "Overview panel" (Fast Scan mode) to show what pattern has excluded a specific file. See https://doc.castsoftware.com/display/AIPCONSOLE/Application+-+Overview+with+Fast+Scan#ApplicationOverviewwithFastScan-zipZipContent/FolderContent. |
| Technical - Application backup | Improvements have been made to ensure that all elements of an application (not just associated schemas and delivery folder) are backed up when requested (the backup action in previous releases did not include everything). CAST highly recommends that post restore, a new scan/version and analysis are actioned to ensure the application has been correctly restored. Some known issues exist for this feature, which are listed in the Known Issue section below. See also https://doc.castsoftware.com/display/AIPCONSOLE/Backing+up+an+Application and https://doc.castsoftware.com/display/AIPCONSOLE/Restoring+an+Application. |
| UI - Overview panel Fast Scan mode - Analysis Results Indicators - Minor UI updates | Improvements have been made to the Justification field (an icon has been added for adding a new or editing an existing Justification) and to the Remedy Action field (text is displayed directly in the list and a mouse roll-over will display the full text when it is too large for the list). |
| UI - Overview panel Fast Scan mode - Analysis Results Indicators - Update Banner | When any configuration is changed, Console will detect this and display a banner in the Analysis Results Indictors section explaining that a configuration change has been made and offering an "Update" button. This button re-computes the indicators. See https://doc.castsoftware.com/display/AIPCONSOLE/Application+-+Overview+with+Fast+Scan#ApplicationOverviewwithFastScan-AnalysisResultsIndicators. |
| UI - Overview panel Fast Scan mode - Warning for incorrect file encoding | When a Fast Scan has been completed (status = "Fast scan done"), Console will now provide a warning if any file that has been submitted for the Fast Scan uses a non UTF-8 encoding. The warning contains a link to a popup dialog box showing the number of these files per language. It is suggested to convert these files to UTF-8 encoding before proceeding with the analysis, since non UTF-8 encoded files can sometimes cause analysis crashes. |
Other Updates
| Internal Id | Details |
|---|
| WEBI-14533 | Fixes an issue where, when using the Gradle Discoverer ≥ 1.1.6 with CAST Console, the discovered AndroidManifest.xml is not displayed in the "Resources Files" section in CAST Console. This is a fix for a display issue only: the file was always correctly taken into account during the analysis. |
Known Issues
| Internal Id | Details |
|---|
| WEBI-14559 | The backup taken during an AIP Core upgrade is not "restorable" in CAST Console because of AIP Core release number mismatches. The workaround is to switch the Node back to the AIP Core release used before the upgrade, update the "application" table in the "aip_node" schema to set the application release number to the previous release number, and then perform the restore. |
| WEBI-14561 | After restoring a backup of an application that was analyzed or fully analyzed, and if you change some configuration settings and you then attempt to run an analysis with snapshot preparation, this step will fail with the error "local site is not up to date". The workaround is to add a new version and analysis/run a new scan and analysis with the existing source code. |
| WEBI-14580 | When restoring backups of application that were onboarded using Fast Scan mode or using legacy mode without version history, source code is not restored. The workaround is to add a new version and analysis/run a new scan and analysis with the existing source code. |
2.9.0-beta1
Feature Improvements
Other Updates
| Internal Id | Details |
|---|
| WEBI-14185 | Fixes an issue where applications from the two different workflows (with and without Fast Scan) were displayed in the "wrong" view, i.e. non Fast Scan mode Applications appearing in the Fast Scan mode application list and vice versa. |
| WEBI-14448 | Fixes an issue where an application created in non Fast Scan mode does not display immediately in the application list and requires a page refresh to get it to appear. |
| WEBI-14463 | Fixes an issue where an application created prior to the global license key expiry date could not be worked on after a new license key had been input: any job that was attempted failed with the error "license key has expired" even though the new license key was valid. |
| WEBI-14471 | Fixes an issue where any changes to exclusion rules/ignore patterns that are made after an initial application analysis are lost when a new analysis is attempted. |
| WEBI-14474 | Fixes an issue where after moving an application to Fast Scan mode, a 404 error is displayed in Console when trying to go to the legacy application overview page. |