This page will help you when you get the following message instead of the source code: No violation bookmarks or details are available on this violation object source code will be displayed instead when applicable
Access "Simple REST Client" by entering the following link in browser http://<server>: <port>/CAST-AED/static/default.html, Where <server>: <port> is the server from where the Deployment folder is deployed, CAST-AED is the name of the deployed deployment folder
If the query returns the source code, then the issue maybe occurring during the source code uploading, as a temporary fix you can try to upload manually the source code via the standalone GUI based or CLI based tools - ED - Using the GUI and CLI tools. then contact CAST Technical Support to investigate the root cause of the issue.
An example of root cause, is when the capture date of the snapshot was updated. This bug was fixed starting from CAST AIP 8.3.6
If the source code is not visible for power builder objects then please note that this feature is implemented starting from 8.3.13 AIP version. Before that it was a limitation to have no source code visible for power builder objects.
If the source code is not visible for particular quality rule called 'Avoid direct or indirect remote calls inside a loop' then try taking a new snapshot skipping analysis. This is a known scenario affecting this particular quality rule when latest snapshot is deleted and consolidated. In this case to synchronize the metric computation between KB&CB we need to take a new snapshot skipping analysis. If new snapshot is not resolving your issue then please apply the attached 2 procedures DSSAPP_SOURCE_POS_UPDATE & DIA_JEEPATH_GENERATE on KB and take snapshot skipping analysis.
If the source code is not available for the rule- 'Avoid cyclical calls and inheritances between namespaces content' then this is a normal behavior. This particular rule is not designed to provide any bookmark. Also, this rule is focusing on packages/namespace objects, so objects being violated are packages/namespace type and we don't have any source code stored for them normally. So the current behavior of the rule is just to show you the violated namespace object.