Hi @imran rasheed ,
I have a lot of experience with archiving and I have done more than 3 years ago what you are trying to achieve. Let's see if I can help. To start with we will keep it simple so get it working the right way. Then you can add more related records to each archive rule so you don't leave orphan records in your instance while archive REQ/RITM/SCTASKs.
Your REQ archive rule looks just fine. Just make it active. The only related record you have is to trigger the archiving of any RITM related to the REQ that you are archiving. Clear the field you added on your second image. You could add more related records to the REQ for things like metrics, slas, etc.
The RITM archive rule does not need any conditions at all. You did it right by adding the REQ archive rule as the parent one. You will notice this will make the active field disappear which is fine. I like that you also add two related records. One to continue the daisy chain effect with the SCTASKs. And the other to delete any individual approvals associated with the RITM. So far so good.
You could stop here if you want, but you may want to add more related records to the RITM archive rule as well like metrics, slas, notifications, etc.
You could also create another archive rule for SCTASK records. Again, no conditions and the RITM one will be the parent. You could also add related records to the SCTASK to clean anything associated with it.
When you remove all the conditions from the RITM (and SCTASK if you create that) the active field will turn FALSE and that is fine.
