Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
How to get the full path of attached files
System
Hi
I will be starting a workflow from one workarea and after that within workflow i will be attaching files to this workflow from some other branch.
In submit task i want that all the files should be submitted to their own STAGING Area.
For this i am planning to create a perl file that will read the full path of attached files and will then store the workarea path and Staging path for all the files in a variable and then will be submitting all these files to their respective STAGING area
But i don't know how to get the full path of attached files.
i guess it is possible with help of iwattrib-Not sure about this
If anyone knows about that and tried similar thing before plz let me know
thanx in advance
Saurabh
Find more posts tagged with
Comments
Adam Stoller
I'd consider this to be in the realm of "Advanced Workflow Development" - so if you don't feel particularly strong in your ability to develop workflows, I wouldn't suggest trying to take this on without some additional, knowledgable, assistance.
Since any individual task in a workflow can only have files associated with that task's areavpath - trying to attach files from multiple areavpaths to a single task is unlikely to work without a LOT of pain and suffering.
Instead, consider either using nested workflows for each of the different areas, or a multi-path / concurrent workflow in which after the workflow has forked to the distinct transition paths, the files from the different areas are associated with the different paths. Not sure if this will make it any clearer - but you're basically looking at is something like:
/---B1-->C1...N1--\
A---+----B2-->C2...N2---+->End
\---B3-->C3...N3--/
Where generally somewhere along the B->C->...N path you will have an externaltask or cgitask that will allow you to add files for distinct areavpaths to that thread of the workflow and your submittask will also have to happen somewhere within that B->C->...N path as well. After all the separate processing, you can then have all the threads transition to a single endtask.
Hope that helps.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com