On Mon, 20 Sep 2004 12:26:45 +1000, Johnstone, Colin wrote > Gidday all, > > In our CMS (Interwoven Teamsite) I need to write a content deletion workflow.
Typically a job (workflow) variable is set to indicate all files associated with the joy should be "deleted", maybe using a checkbox on the job instantiation form. Consider renaming the DCRs instead of deleting them so users can get back to the data, see history and restore lost content more easily. > If a user is deleting a html page I need to parse that page and > report on all assets (images, pdfs) attached to the page and delete > them as well. There are HTML parser modules, but what if something else references one of those assets? Review becomes important before deleting the files. A link check could also be important, but you also might not want to actually delete the files from TeamSite until the very end, so you may need to deploy a file list from an empty directory to delete the files from a "staging" environment before running link scan. If you are generating emails with CCI links, check the variable and put "WARNING" in the subject line. > How do I go about doing this? I'll do the legwork just broadbrush > the approach. You probably want an externaltask before approval that parses all .htm, .html, etc. files for img, href, etc. references, attaching each to the task. If those assets could be in another branch, that really complicates things as each task can only be associated with one area and you need a tasks for each area, or externaltask logic that knows about the other areas. You may need some special submittask options to ensure the deletions are committed (I usually implement submit as externalltask) and OpenDeploy configuration to support deletion. If you are using DataDeploy there are probably additional considerations. Thing modularization. Interwoven has tools representing job task; use the method for retrieving the list of files associated with that and any actions available for adding files, etc. Subclass these if the behaviours you need aren't provided; this generally involves calling the Command Line Tools. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
