Question Re: RAR Mitigating Control Deletion in Additional Q&A

RAR Mitigating Control Deletion

Former Member — Wed, 01 Dec 2010 18:48:46 GMT

Hello,

I am having an issue where I've deleted all mitigating controls and now it will not let me delete the associated approvers and business units. When I search for mitigating controls the search comes up empty. The weird thing though is that the main page is still showing one inactive mitigating control. I've also checked users and roles to make sure none are assigned a mitigating control.

Error when deleting the business unit

com.virsa.cc.rulearchitect.dao.DAOException: Business unit: AAID is already assigned to Mitigation Control; it cannot be deleted

Error when deleting the administrator:

administrator ID is already assigned as approver to a business unit : Can't be deleted

I've also checked that Send e-mail notification to the monitor of the updated mitigated object is set to NO and all workflow integration with CUP is set to NO

Any suggestions where this thing might be hiding?

Re: RAR Mitigating Control Deletion

Former Member — Thu, 02 Dec 2010 01:34:12 GMT

Kyle,

Did you delete mitigating control via front-end? If you did then it should allow you to delete business unit etc. If you deleted them via file then there is an issue. You can load an empty mitigation import file which will wipe out any exisitng mitigating controls. I have seen this issue when I tried to manipulate controls via file.

Regards,

Alpesh

Re: RAR Mitigating Control Deletion

Former Member — Thu, 02 Dec 2010 06:28:19 GMT

Kyle,

Other solution will be to delete data at DB level.

All RAR mitigation table names contain MIT string VIRSA_CC_... MIT...

regards,

Surpreet

Re: RAR Mitigating Control Deletion

koehntopp — Thu, 02 Dec 2010 07:12:53 GMT

Do you still have an export file of your mitigations? (if not, create one...)

There are "M" rows with the table header, and "D" rows with data for those tables.

Go and delete all the "D" rows so that jiust the "M" rows are in the file, and import this via mitigation upload.

That should make sure all tables are empty.

Frank.

Re: RAR Mitigating Control Deletion

Former Member — Mon, 13 Dec 2010 18:03:35 GMT

Frank,

I was able to figure out what was in the text file and delete them manually. Thank you...

But this won't work for our needs when exporting the file making changes and importing the file back into the system.

We appear to be having another issue with this file: Mitigating Control Import/Export Issue

Scenario:

When exporting mitigating controls via the utilities functionality, converting to excel, saving and re-importing after changing (only text) causes Error "M is invalid system".

Things to note:

Systems are not populated within the utilities screen. Even though systems are not populated when selecting "all systems" no header data is populated in the export file to insert system. Also, if you dont change anything file will import.

Resolutions Tried:

Attempted to populate system data within the first column of the export file with no successful results.

Kyle

Re: RAR Mitigating Control Deletion

Former Member — Mon, 13 Dec 2010 19:25:41 GMT

Kyle,

You must leave first row of the file empty. If it starts with M, RAR will throw an error.

Regards,

Alpesh

Re: RAR Mitigating Control Deletion

Former Member — Mon, 13 Dec 2010 19:28:02 GMT

I've tried this as well... Still some how its grabing that "M" column header when blank.

Re: RAR Mitigating Control Deletion

koehntopp — Tue, 14 Dec 2010 10:36:45 GMT

Kyle,

the first row needs to have a system name (Connector ID) in order for the import to work.

Frank.

Re: RAR Mitigating Control Deletion

Former Member — Tue, 14 Dec 2010 21:57:54 GMT

Sorry, Frank. You must have the first line empty for the mitigation upload to work. Mitigation is not tied to any connector.

Regards,

Alpesh