Thanks Tambo, I read this tip in another thread, but seems not to work in CME 7.5, if I’m doing it correctly… the -d is an argument for the link to app, right?
Thanks Cav; I agree. My first thought was for deleted scripts too, but asked just to be shure 'cause usually other object have a creation/deletion date, but this table is different in structure, so it makes sense.
Here is how a strategy is saved into DB:
1.A new record is inserted into ird_strategies table.
This record has some long temporary negative number in DBID field (lets name it ‘tmpDBID’) and a new rbn-file in the RBN field.
2.If the step 1 is successful then IRD sends update/insert request to CfgServer to update/create a corresponding Script object in CME.
3.If the step 2 is successful then IRD deletes the original script record from ird_strategies and updates a temporary record created on step 1 with a permanent dbid. To do this IRDsends two sql statements:
delete from ird_strategies where dbid =
update ird_strategies set dbid = where dbid = tmpDBID.
I have found out that If strategies are “Stored in database” (stored in ird_strategies) then they should be deleted using Interaction Routing Designer.
If they are not “Stored in database” they they can be deleted using Config Manager or Interaction Routing Designer.
If deleted via CME, then you would certainly leave ‘orphan’ records in the ird_strategies table.
To prevent this, one could log the ‘scripts’ folder so that the average user could not delete the objects, but you would need to make sure your IRD users were not locked out.
Also, any IRD user that was logged in to CME could still delete directly…