Note that CAST highly recommends updating to the new release of AIP Console to take advantage of new features and bug fixes. See Upgrade process for more information about this.


Other Updates

Internal IdDetails
WEBI-11150Back port the "Job History Strategy" settings under "Global Configurations" introduced in AIP Console 1.26.

Resolved Issues

Customer Ticket IdDetails
32352Fixes an "AccessDeniedException" error seen while attempting to backup an Application.


Resolved Issues

Customer Ticket IdDetails
30503A "session expired" popup appears when user clicks on "Extensions" or "Function Points" icon in the left panel for an application.


Resolved Issues

Customer Ticket IdDetails
30798Rescan fails with an error, "path not matching" although there is not change in the source code.


Resolved Issues

Customer Ticket IdDetails
30257WPF extension is not getting updated to latest version.
30384While adding a version in Console for PL1 source code, the missing path popup is displayed even when there is no change in the source code between the versions.
30034Maven repo with system proxy does not work. The following error occurs: "Exception while executing a Groovy script. For input string: "8,080" Return value: 1000".
29795AIP Console 1.24 installed on a Linux server is crashing during start-up when SAML authorization is enabled.


New Features

GUI - Schema and delivery folder upgradeIt is now possible to perform a schema and delivery folder upgrade to a newer release of AIP Core directly from within the AIP Console GUI. When an application is eligible for a schema upgrade - in other words, the AIP Core release used for the Application is older than the AIP Core release installed on the AIP Node, AIP Console will detect this and display an icon in the list of Applications in the Admin Center. An option to upgrade is also made available. If an Admin user attempts to perform an action on the Application (such as run analysis/snapshot) a message is also displayed explaining the situation and offering the opportunity to upgrade. See and
Technical - Persistence database auto backupThe h2 persistence databases used by both AIP Console (front-end) and all AIP Nodes is now automatically backed up every night. See

Feature Improvements

Technology - C/C++ Technology options - Accept trigraphsThe "Accept trigraphs" option has been implemented in AIP Console (previously this option was only available in CAST Management Studio). See
GUI - Module managementThe ability to delete all Modules in one go (via checkboxes and a global delete button) has been added to the Module management page at Application level - see
GUI - Application OverviewThe Architecture Map section has been improved: 1) the list of Technologies has been replaced with a coloured treemap depicting the number of files in each discovered technology. 2) Discovered Frameworks are now displayed in their own dedicated section, rather than with Technologies. See
GUI - Transaction - RulesThe list of predefined Data Entities (known as "built-in types") is now displayed in the Application - Transactions - Rules page. Previously this section was not visible. See for more information.
GUI - Application - Config - ArchitectureAIP Console will now only offer Architecture Models that have already been added to or imported into the Architecture Studio, rather than offering a file upload option as in previous releases.
Technology - SQL - Sybase (legacy)AIP Console will now display the "Sybase Technology" entry in Application > Config when delivering the results (.castextraction or .uaxDirectory) of a Database Extraction for a Sybase ASE instance. See
Technology - Mainframe - AdvancedJCL.xmlIt is now possible to define an AdvancedJCL.xml file (containing parametrization rules for JCL) at application level - available in the Technologies > Mainframe > JCL section in the GUI. See for more information.
Tranasctions - Rules - Table prefixes excluded from PK/FK analysisIt is now possible to define table prefixes that are excluded from PK/FK analysis for the Built-in data entities sub-section of the Transaction - Rules section. Previously this section was only available in the legacy Transaction Configuration Center application. See
Transactions - Rules - Excluded table names via regular expressions (case insensitive)It is now possible to define excluded table names via regular expressions (case insensitive) for the Built-in data entities sub-section of the Transaction - Rules section. Previously this section was only available in the legacy Transaction Configuration Center application. See
Architecture Studio - Check overlapping objectsA new option has been added to the header toolbar when working in the Architecture Studio edit mode. This new option allows you to check whether any objects you are capturing in your model are present in more than one layer - in other words you may have multiple layers that target the same object types. See
Architecture Studio - Layer/Set creationWhen creating a new Layer or Set, you will no longer be prompted to name the item. This step has been withdrawn to improve the workflow. Items are given a generic name and can be renamed after they are created.
Architecture Studio - Check ModelWhen checking the violations in an Architecture Model or Quality Rule Model or the objects in a Layer or Set, it is now possible to add "path" information about the objects in question. The path information is not visible by default and must be added manually using the "Column" selector. This can help localize the object for remediation purposes. See
Architecture Studio - Model Editor - Shown external objectsA new option has been implemented called "Show results with External Objects" and is available in the configuration option in the Model Editor header. When activated, this option will show all links based on the scope of the caller Layer, even those starting from external objects if the Layer is configured to include such objects. In the list of violating links, a warning is added explaining that external objects are displayed and a new column called "Internal" is displayed, indicating if the the link involves internal objects or not. See
GUI - Prepare analysis data bannerA new banner will be displayed when changes are made to the Module configuration, Dynamic Links are reviewed or new Update Analysis Schema jobs are added. This banner indicates that the analysis results used by features such as the Architecture Studio, Transaction configuration and upload to CAST Imaging will not be up-to-date. The banner therefore offers the option of running a dedicated step called "Prepare analysis data" to bring the results back up-to-date. See for example
GUI - Reference FinderAn additional action has been added to the Reference Finder rule creation UI: "Save and Run". This option will save the Reference Finder rule configuration AND execute the rule (any links found will be saved). In addition, the existing action "Save Configuration" is renamed as "Save". See
GUI - Architecture Studio - Clone Layer or SetIt is now possible to clone an existing Layer or Set in the Model editor. The cloned item will be name using the existing item's name with the suffix "- Copy". See
GUI - Process Application dialog boxThe Process Application dialog box has been redesigned to improve its functionality. This dialog box is displayed when running actions such as generate snapshot, run analysis etc.

Other Updates

Internal IdDetails
WEBI-10039Delivery folder migration failed with "Error is: Unrecognized character escape '{'." This bug has been fixed.
WEBI-9961Delivered Engineering Dashboard release: 1.26.1-funcrel. Delivered Health Dashboard release: 1.26.1-funcrel.
WEBI-9961The "ISO-5055 Index" extension ( has been added to the list of extensions that are force installed with every Application. See
WEBI-9166Mainframe Library Extensions that use composite file extensions (such as XXX.YYY) are now correctly handled by AIP Console. In previous releases, only the very last part of the defined extension (after the last dot) was taken into account. See
WEBI-9984in previous releases of AIP Console, some metamodel types and categories displayed in Transaction rules/Architecture Studio layers/sets may have been displayed with a description ending in "- legacy" (or even "- legacy - legacy" in some rare cases) - this was so that it was possible to distinguish between multiple metamodel types or categories that used the same description. From ≥ 1.24, the use of - legacy to distinguish metamodel type or category descriptions is no longer used, instead where two metamodel type or category descriptions are the same, the name of the metamodel type or category is now appended in brackets.

Resolved Issues

Customer Ticket IdDetails
25915Not able to change extension strategy in Firefox Web browser.
27732Incorrect version status when upgrading extensions.
28991Mainframe Punch files are not recognized by AIP Console.
29002No analysis unit created for Perl source code.
29071User Defined Module - Module content overview failed with the error:
29320Incident-Snapshot/Version cleanup jobs are failing with message 'Version not found'.
29354Apps failing on Install extension step when there is a corrupt extension in Custom extension folder or the Extension folder.
29467Generate snapshot indicator on mainframe applications takes a really long time.