This page provides information on new violations showing up for Architecture Checker rules for unchanged code.

Applicable in CAST Version
Applicable RDBMS
Action Plan

In certain circumstances, you may see new Architecture Checker violations on unchanged code. 

Case 1:  New Dynamic Links cause layer violations

One case is when you may have a new dynamic link, which you may not have expected that violates the Architecture layer rules that you have set up.

For example, you may have added a procedure with the name of 'A' which then is matching several items in your code and creating links to them, even though this code may not officially make database calls. 

This would result in a new violation for unchanged code for a layer violation due to this dynamic link being created.

Here is an example screenshot of the violation in the dashboard:

  1. Use Enlighten to identify any improper links that may have been created. 
  2. In Enlighten, add both the calling and called object (the violated object and the object listed in the associated value) to the same graphical view and then examine the link between them. 
  3. If there is an incorrect link that was created, then you can 
    1. Use the dynamic link manager to ignore this improper dynamic link. 

 Ticket # 2841