nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filtering Deleted Files

Dmitry

I am using WFConstructor, and I have several parallel tasks that filter files. The tasks each take the same set of files, filter them based on the metadata and send the files down 2 different paths (some require additional approval before submitting and some don't).

The problem is, I can't get this to work with deleted files. When I take the submitted file list returned by Teamsite and expand it to list all deleted files (not just the top level deleted directories) and try to attach this file list to the external task, I get an error "The path deleted_directory/deleted_file does not exist in the workarea." What's weird is that it works fine if I just pass in the deleted_directory, even though it doesn't exist in the workarea either. When I add the files/directories below the top level deleted directories, the whole thing breaks.

Does anyone have a workaround for this or understand why this might be happening?

The only workarounds I thought of is a) not using WFconstructor and b) not allowing users to attach directories to workflows unless the directories are empty. Both of those are suboptimal though.

This is on TS 6.5 SP2

Thanks,
Dmitry

Edited by Dmitry on 10/14/05 01:44 PM (server time).

Find more posts tagged with

Comments

Adam Stoller

Did the files already exist in staging - or were these not-yet submitted files within a directory which had been created in staging by virtue of another submit?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Dmitry

Yep they do exist in staging.
TS complains about them not existing in the workarea, which is weird because naturally deleted files wouldn't show up in a workarea.

Edited by Dmitry on 10/14/05 02:03 PM (server time).

jed

That is just the way TeamSite works. If a tree is deleted, you can only add the top level deleted dir to the directory. For example, if you have this:

mkdir ./foo
touch ./foo/bar.html
./foo/bat.html

iwsubmit foo

rm -rf foo

Under this scenario, you will only be able to attach "foo" to the workflow. Fun, eh?

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems

Adam Stoller

Hmm - but in externaltasks or cgitasks, if you need to do additional processing of the files in the deleted directory - you can have that script traverse the directory in staging (prior to the submission of the deletion).

I've done that in the past for custom menu items that took care of deploying deletions - it's relatively straight forward

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jed

True. Or you can attach all files to the workflow before the deletion, but it sounds like that may not be possible in this scenario. (Files are already deleted by a parent workflow?)

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems

Dmitry

Since deleted files aren't actually attached to workflow tasks, you guys are saying it's impossible to send deleted files down different branches of a workflow?