Metadata- Workflow: Job 39292>Task 39296 not seen on staging content.

I am working on TS 6.7.1.Whenever i am attaching a file in a workflow,an extended attribute like Workflow: Job 39292>Task 39296 gets set on that file.But when i submit the file to staging the submitted content does not reflect that extended attribute.I need to search on files having that Extended attribute so that i know which files are active in a particular task and job.Is it possible to do so wrt to the Workflow attribute.
These attributes are updated at runtime ie when the workflow is complete the Workflow attribute is dropped of the file dynamically.
Also i've seen it happening in TS 6.7.1 and not in TS 6.5.Please can anyone explain the reasons for the same.

Find more posts tagged with

Comments

Adam Stoller

I am working on TS 6.7.1.Whenever i am attaching a file in a workflow,an extended attribute like Workflow: Job 39292>Task 39296 gets set on that file.But when i submit the file to staging the submitted content does not reflect that extended attribute.I need to search on files having that Extended attribute so that i know which files are active in a particular task and job.Is it possible to do so wrt to the Workflow attribute.
These attributes are updated at runtime ie when the workflow is complete the Workflow attribute is dropped of the file dynamically.
Also i've seen it happening in TS 6.7.1 and not in TS 6.5.Please can anyone explain the reasons for the same.

I don't know about that EA - but chances are if it's there it's only for as long as the workflow needs it (where do you see this EA?)
Instead you might try looking in the CLT manual for iwgetfilejobs

nikhil_palav

Its true that the Extended attribute (Workflow) stays on that file only as long as the workflow needs it.I see this attribute when i click on the properties tab of the file.
What i need to do is search through all the files which are part of a workflow by means of a search UI & i need to make use of the workflow attribute as the searching criterion.Is there a way i can get jobid's & taskids & then search through the directory structure for files associated with it.

Adam Stoller

Its true that the Extended attribute (Workflow) stays on that file only as long as the workflow needs it.I see this attribute when i click on the properties tab of the file.
What i need to do is search through all the files which are part of a workflow by means of a search UI & i need to make use of the workflow attribute as the searching criterion.Is there a way i can get jobid's & taskids & then search through the directory structure for files associated with it.

Are you talking about while the job is still active - or after the job no longer exists?

While the job is active - as I mentioned before - iwgetfilejobs will tell you what job/task a given file is associated with.
You could then turn around and create a simple script that took that information, created a TeamSite::WFtask object from the taskid and then dumped a list of all the files associated with that task.

After the job no longer exists - nothing OOTB will help. You would have to record [somewhere] the information about the files that were attached to the job - before the job ended. For most of us - we call this an audit trail script - an externaltask process that runs just prior to the endtask of the workflow - and either dumps the output of iwgetwfobj to a file or processes it and sends it to a database. If you've got the $$'s for it - you could also purchase Interwoven's ReportCenter which would then put this information into a database for you and then you buy CrystalReports to use the OOTB report generation features -- or write your own routines against the database in which ReportCenter stores the data.

nikhil_palav

Thanks very much for your reply.I did work out a solution as given by you.There was yet another way i could figure out by running iwgetwfobj -s .
The resultset would be an xml file comprising of active jobs,all jobs & task.Then retrieve all the jobids & then as told by you create a WFTask obj & retrieve all files associated with each of those tasks by doin getFiles().