Following is the scenario which describes the problem of abnormality in date value of Last Update column:
- From CAST AIP 7.0 till CAST 7.3.8, this is a known behaviour of the application that the Last Update column of the FRAME_PORTAL_FAQ_VIEW_EXCLUSION view has the date which is earlier than the First Snapshot date.
Open the report - List of Objects Excluded from Quality Rule Computations.
See the First snapshot and Last update column.
- The Last Update column will have a date which is before or earlier than the First Snapshot date.
This is a known behaviour of the CAST AIP and this functionality is going to change in the CAST AIP 7.3.9 release. Following is the explanation of the existing functionality/behaviour:
When an object is excluded:
- The column 'LAST_UPDATE' is set to the date when the dashboard user is performing the action of "Exclude Objects".
- The column 'FIRST_SNAPSHOT_ID' is set to the current snapshot id + 1 in order to activate the exclusion to the next computed snapshot.
So, by default the associated date to FIRST_SNAPSHOT_ID is always greater or later than the LAST_UPDATE column.
So as of now there is nothing that can be done in the CAST AIP product.
But, this behaviour will be updated in CAST AIP 7.3.9. The column FIRST_SNAPSHOT_ID will be set to the current available snapshot_ID and all related procedure and dashboard pages will be updated accordingly.