CAST Engineering Dashboard - Action Plan - Action Button malfunction - Not able to add objects with violation to the Action plan

This page handles the below problems :

1. You are trying to add an entity (object with violation) to the action plan, you see the icon indicating "Action plan" next to the item, but if you navigate to another rule, and came back, the icon disappears. Also the object do not appear in the action plan page.
2. You are trying to add an entity (object with violation) to the action plan, you do not see the icon indicating "Action plan" next to the item (nothing changes after clicking on action and saving the comment). Also the object do not appear in the action plan page.

1. Add objects in the investigation quality model drilldown view to Action
2. The icon beside the item marked for action is not present
3. See that the objects are also not present in the action plan view

CASE 1:

you are trying to add an entity (object with violation) to the action plan, you do not see the icon indicating "Action plan" next to the item (nothing changes after clicking on action and saving the comment). Also the object do not appear in the action plan page.

Check that the objects that you have marked for action are present in the viewer_action_plans table by running the below query on Central Base

select * from viewer_action_plans where action_def like '%<comment/part of comment that you made while adding object to action>%';

If the objects are present in the viewer_action_plans table then you need to check for corruption in central base that prevent from adding the object in the action plan. Here are the list of known corruptions and how to clean them

Corruption 1:

check in the Action Plan view of older versions of snapshot for the presence of objects. If the objects are present in the ACtion Plan view of older versions of snapshot then the actions not seen are may be due to wrong last_snapshot_date equals to the first_snapshot_date in the table viewer_action_plans (this has happened due to corruptions in CB). You can verify this by running the below query on CB

select * from viewer_action_plans where first_snapshot_date = last_snapshot_date

If the above query returns rows then this confirms that the corruption. You can run the below query to clean the table

update viewer_action_plans set last_snapshot_date = '2100-01-01 00:00:00' where first_snapshot_date = last_snapshot_date

Corruption 2:

Action has been reset for this violation in a previous snapshot, as a consequence, the violation is marked as reset and cannot be planned for an action again. you need to run following query to check if you are in this situation:

select vap.metric_id, vap.first_snapshot_date, vap.last_snapshot_date, count(1)   from viewer_action_plans vap where vap.last_snapshot_date != '2100-01-01 00:00:00' group by vap.metric_id, vap.first_snapshot_date, vap.last_snapshot_date

If this query returns some rows, it means that you have some violations that have been either selected for action or excluded in a previous snapshot and then put to reset (reset button). As consequence, these violations cannot be selected for action again in current snapshot. This is a bug in the product as we could be able to select a reset violation for action. 

To remove this corruption you need to run the following query on your central (please perform a backup of your central before):

update viewer_action_plans  set last_snapshot_date = '2100-01-01 00:00:00'  where last_snapshot_date != '2100-01-01 00:00:00'

After running this query you should be able to mark the objects that have been reset for action again

Corruption 3:

Objects have been marked for for exclusion in a previous snapshot which has been deleted.
Due to this you can see some objects in DSS_OBJECT_EXCEPTIONS table for snapshot n that has been deleted by running the below query

select FIRST_SNAPSHOT_ID, count(1)
from DSS_OBJECT_EXCEPTIONS
where FIRST_SNAPSHOT_ID not in (select SNAPSHOT_ID from DSS_SNAPSHOTS)
group by FIRST_SNAPSHOT_ID

If the above query returns rows then it confirms the same. As workaround, you can remove all exceptions for non existing snapshots by running the below query :

delete from DSS_OBJECT_EXCEPTIONS
where FIRST_SNAPSHOT_ID not in (select SNAPSHOT_ID from DSS_SNAPSHOTS)

After applying the work around you can see that the objects can be added to action plan but you would have lost all the exclusions for non-existing snapshots. If you want back the exclusions, you need to manually add them(Click on exclusion button by selecting the object). To make a note of such exclusion you can use the below query before running the delete statement:

select dos.object_name as OBJECT_NAME,
dos.object_full_name as Object_Full_Name, 
doe.metric_id as Mertic_ID,
dmd.metric_description as Quality_Rule_Name 
from DSS_OBJECT_EXCEPTIONS doe,dss_objects dos,dss_metric_descriptions dmd
where dos.object_id = doe.object_id
and doe.metric_id = dmd.metric_id
and doe.FIRST_SNAPSHOT_ID not in (select SNAPSHOT_ID from DSS_SNAPSHOTS)
and dmd.description_type_id = 0
group by dos.object_name,
dos.object_full_name , 
doe.metric_id ,
dmd.metric_description

Analysis - N/A Dashboard - Objects are correctly marked for action and are present in Action Plan view