Hi all,
with the restriction of only being able to attach douments in one place to a request - causing issues when that request 'sporns' several tasks and so the attached document can't be 'attached' to the right task ...
has anyone got any workarounds .....
The only 1 I can think of is allowing the requestor to add the document name in a dedicated text field for that part of the request, and using FUSION to find that document (by name) and move/copy it into the created task when it becomes a project.
Any other ideas ???
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @GeraintJo
you're on the right track: this will require Fusion. And since there is no foldering/tagging of the files that get attached to a form I can see the difficulty of knowing which doc to attach to which task 🙂
As for providing fields for the user to enter a name - either it's a free-form text field (typo means I can't find the doc) or, you have them upload the docs first and in the request form, use an external lookup to provide a document selector.
Can you enforce document naming to be consistent? Then you can use naming conventions to figure out where to put which doc. I'd start there.
Hi @GeraintJo
you're on the right track: this will require Fusion. And since there is no foldering/tagging of the files that get attached to a form I can see the difficulty of knowing which doc to attach to which task 🙂
As for providing fields for the user to enter a name - either it's a free-form text field (typo means I can't find the doc) or, you have them upload the docs first and in the request form, use an external lookup to provide a document selector.
Can you enforce document naming to be consistent? Then you can use naming conventions to figure out where to put which doc. I'd start there.
Thanks for that.
This does seem a major shortcoming in the request process.
Can't believe it's not already on the dev plan
Views
Replies
Total Likes