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

This documentation is no longer maintained and may contain obsolete information.

Report Builder

Report in PDF Format

Length of Report Title

When generating a PDF file from a Report Builder report and when the report title has more than 99 characters without any space, the report title in the generated PDF file is truncated after 99 characters, although a name of up to 200 characters is allowed. However, you can use:

  • either a report title with less than 99 characters, when the report title must not contain any spaces.
  • or a report title with some spaces, when the report title needs to be longer than 99 characters.

Truncated Lines in section FlexReport - Items

When generating the PDF version of a report containing a Flex Report - Items section, the lines get truncated in the PDF report. Please note that the HTML version of the report contains all lines without truncation.

Late Snapshots in CAST Engineering Dashboard

In case

  1. you use the Capture Date to process older Application source code to enrich the history of the Application, and
  2. you can not end up processing up-to-date source code,

The Technical Details hyperlink and the Code Viewer will display the older version of the source code and of its properties.
As a workaround, you can re-analyze the latest source code (no need to generate the Snapshot) of the Application.

Deleted then recreated objects appear twice in the module tree

When objects are recreated, their internal IDs are changed as well. Hence, they are considered as two different objects.

Comparing Snapshots generated with different Assessment Model configurations

The mechanism that detects changes in Assessment Models between snapshot generations does not yet detect changes since the last snapshot computation.

CAST Engineering Dashboard consultation during snapshot generation

It is strongly recommended to avoid consulting the CAST Engineering Dashboard while a new snapshot is being generated.

Module weighting mechanism

The Module Weighting mechanism based on external data does not apply to the Technology aggregations. Instead, external data refers to Business Value metrics and Productivity metrics that can be upload into the central repository and assign to a Module.
As a reminder

  • Module Weighting mechanism based on Technical Size and Functional Weight metrics do apply to the Technology aggregations.
  • Module Weighting mechanism do apply to the aggregations along the Portfolio Tree and Organization Tree, regardless of the type of metric to use.

Results of shared Metrics are Displayed Even for Excluded Modules

When the same metric appears at several locations in the Metric Tree, and when the different higher level metrics that contain it have different configurations regarding the list of Modules to exclude, results for the metric can be displayed in the Dashboard even for the excluded modules. This occurs because the shared metric can only inherit its list of Modules to exclude from one of the higher level metrics that contain it. It inherits its list of Modules to exclude from the first higher level metric, not from the second or other ones. Therefore, metric results are calculated computed based on this first list of Modules to exclude. Result are then available for a Module that is excluded in the second, third, ... list of Modules to exclude.

As a workaround, duplicate the concerned metric to assign it to the higher level metric with specific list of Modules to exclude. You just have to give the copy a new name and a new ID, but you can reference the same procedures and parameters as in the original metric. Place the duplicated metric at the location of the Metric Tree for which exceptions are defined.

User/Role/Cost Profile Administration

User, Role and Cost Profile IDs are case-insensitive. Therefore, if you attempt to create a new User, Role or Cost Profile with the same ID (regardless of case - upper, lower or a mixture) as an existing User, Role or Cost Profile, then the creation process will be refused and an error message will be generated.

Running the CAST Engineering Dashboard on Oracle Application Server (OAS)

When deploying the delivered WAR file, Oracle Application Server deployment tool fails to deploy it on account of an invalid deployment descriptor file. This occurs because the delivered deployment description file - web.xml - is UTF-8 encoded. It starts with the Byte Order Mark (BOM) sequence, displayed as 

  1. Unzip the delivered WAR file,
  2. edit the web.xml file to remove first characters that are displayed as 
  3. take the opportunity to uncomment one of the connection bloc (so that the deployment plan can be updated throught the OAS GUI),
  4. zip the files back into the WAR file,
  5. deploy the WAR file through OAS GUI as any other WAR files.

Number of Violations Displayed on Metric Details page

The list of violations displayed in the Metric Detail page is truncated to the first 10000 rows. This limitation is designed to preserve performance levels without limiting the usability of the page (In case there are more than 10000 violations, the extensive display of all violations does not make sense in a user interface and could be achieved in a dedicated report if the extensive list is needed)

Technical Size Information After Re-consolidating an Existing Snapshot

When there were major changes in the composition of applications and modules between the initial generation of a snapshot and a new consolidation of the same snapshot, the quantity information given in the Technical Size section of the snapshot might be erroneous. The values displayed in the snapshot can be inferior to the actual values.

  • No labels