BOE Schedule to File - Destination.Cleanup not working

[hilfy]

BOE XI R2 SP2 with Fix Pack 2.3
.NET SDK

I'm trying to schedule a report to a pdf file and then have the instance removed from BOE after the file is created. The file is created with no problems, but the instance is not being removed from BOE. I've tried doing this a couple of different ways:

destPI = (DestinationPlugin)destObj[1];
disk = (DiskUnmanaged)destPI;
destOps = disk.ScheduleOptions;
diskOps = new DiskUnmanagedOptions(destOps);
diskOps.DestinationFiles.Add(FileName);
sched.Destinations.Add("DiskUnmanaged");
sched.Destinations[1].SetFromPlugin(disk);
sched.Destinations[1].Cleanup = true;

and

destPI = (DestinationPlugin)destObj[1];
disk = (DiskUnmanaged)destPI;
destOps = disk.ScheduleOptions;
diskOps = new DiskUnmanagedOptions(destOps);
diskOps.DestinationFiles.Add(FileName);
sched.Destination.SetFromPlugin(disk);
sched.Destination.Cleanup = true;

I've also tried setting the Cleanup property before the .SetFromPlugin line and, with the first example, I've also tried setting sched.Destinations.Cleanup = true;

What am I doing wrong?

Thanks!

-Dell



A computer only does what you actually told it to do - not what you thought you told it to do.

 

[groggle]

Does it work if you do this manually from the CMC?

 

[hilfy]

No. Thanks for asking the question! I guess I'll have to check the readme for the to fix pack and, if it's not there, open a support case to see about getting it fixed as it looks like it is a bug.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[sudhach31]

HI,

There is an option in the CMC to remove the instance after the report was created. Open the report in CMC and go to schdule tab --> Destination Tab --> and under destination tab select Email(SMTP) under destination and there you can find the option for(looks like)

"Clean up Instance After scheduling"

Thnaks
Sudha

 

[hilfy]

That's what I've done. It doesn't work. However, I found a knowledgebase article that basically states that when you have auditing turned on and you schedule to a destination, Clean up Instance doesn't work. This is "as designed" because the auditing process "needs the CUID".

To me this is just plain STUPID and evidence of a poor design choice. I left feedback on the KB article and opened a support case on the issue. I figure if enough people complain, maybe they'll fix it.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.