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; } } }

files attached to a workflow

philipcz

I am working on a worklfow, and I want to check to see if a user attaches files to a workflow, and those files already belong to a another workflow.
If I do a properties on a file from Content Professional, I can see that a file is attached to a workflow, I also see a property called workflow with a value; see below
Workflow: Job 2160 > Task 2163

Is there a CLT that will give me the all the properties of a file, so that I can test in a external task if the attached file belong to another workflow.
I looked at iwattrib, but that will not list information if the file is attached to a workflow

Modified By: philcz
Modified: 5/13/04 4:30:47 PM

Locked: papoos:htdocs philcz 5/24/04 11:26:09 AM
Comment: This is locked by me

Version: 0+
Comment:

Workflow: Job 2160 > Task 2163

Owner:
Group:

Size: 16kB
Permissions: rw-rw-r--

Private: Do not submit

Thanks
Phil Czajkowski
phil@quotient-inc.com

Find more posts tagged with

Comments

JonathonG

Take a look at the iwgetfilejobs CLT:

iwgetfilejobs.exe
usage: iwgetfilejobs.exe [-h] [-v] [-s servername] path+
-h Print this message
-v Print version
-s servername Use servername as TeamSite server
path Path to look up

Jonathon
Independent Interwoven Contractor

Migrateduser

I think you have to call iwgetfilejobs once for each workarea on the branch as it only reports jobs in the specified workarea (I don't think you can specify a branch).

philipcz

Thanks Jonathon. This was exactly what I needed. Geat Stuff
Phil

philipcz

Jimmy,
I ran the file CLT like this:

bash-2.03# ./iwgetfilejobs /default/main/papoos/WORKAREA/htdocs/index-2.html
/default/main/papoos/WORKAREA/htdocs/index-2.html
job=2160 task=2163
job=2178 task=2179

And this is exactly what I need

Migrateduser

Cool, I didn't know you could do that - that should be more efficient than actually calling the CLT mulitple times. It even outputs a line before each result indicating which command line parameter file the set is for. In fact I always considered this tool kindof broken because it doesn't have an option to operate on a branch. Of course if you have many workareas on a long branch name and/or your file directory path is long you could exceed some command line length restriction (not sure what that would be). Also note that this may not report files associated with active dummy and potentially other task types.