Problem Description
Excluded violations are still visible in the dashboard after taking a new snapshot.
Observed in CAST AIP
Release | Yes/No |
---|---|
8.3.x |
Observed on RDBMS
RDBMS | Yes/No |
---|---|
CSS |
Step by Step Scenario
- Take a first snapshot v1 of the application.
- Exclude some violations from the dashboard.
- Take a second snapshot v2.
- Open the dashboard, excluded violations are still visible in the list of violations.
Impact of the Problem
The impact of the problem on the analysis or the dashboard is: *excluded violations are still visible in the dashboard after taking a new snapshot.
Action Plan
- Check the functional date of the v2 snapshot.
- If v2 functional date is older than v1 functional date,
v2 snapshot is seen as previous to the first snapshot v1 in the dashboard.
Same way, current snapshot visible in the dashboard is v1.
Hence the exclusion marked in this snapshot are still not reported to next snapshot. This is the expected behavior of the product.
- If v2 functional date is older than v1 functional date,
- To get the exclusion taking into account in v2 snapshot, please change the functional date (also called capture date) of v2 snapshot to a date more recent than v1 functional date and then consolidate v2 snapshot.
Refer to the online help of CAST-MS (CAST Management Studio - Help -> Infrastructure -> Editors -> Snapshot editor) to see how to change the snapshot capture date.
Impact of the solution
Impact of the solution on the analysis or the dashboard is: Once the functional date of snapshot v2 corrected, exclusions should no longer be part of the violation list in the dashboard.
Notes/comments
Ticket # 4565
Related Pages