I would like the ability to route custom forms for approval within Workfront. Alternatively also have the option to Print to PDF, particularly when there are multiple custom forms at the project or task level.
For example, I am in the process of converting our project charter template from Microsoft Word to a custom form in WF.
The idea being, the PM could complete the project charter within WF, route the custom form to the project sponsor for approval and/or comment, all within WF instead of having to do it outside the system.
With the Print PDF, you can do this, however, it will print all the custom forms on the project or task and you cannot select one custom form.
Interesting, so do you mean a system that would allow users to "request" new form - and then have an approval process tied to that request?
Not sure I am following...
Basically what I am suggesting is for a project manager to be able to pull a custom to a project (which they can do already) and be able to route that custom form (for example a project charter) to another user for approval. Currently, once the project manager pulls a custom form to a project there is not much they can do apart from filling it in and reporting on it. Please let me know if you need further clarification? Thanks!
Good idea! We're having to have quite a few stand alone forms in WF, as they need to be sent to other people for review/approval and we can't do it with the current forms. This links to a suggestion I put on here a while ago about being able to print/circulate custom forms.
Yes, we would love this functionality as well. Thanks.
We need this!
Great idea. We totally need this. ‚
i mean, please add this to the other custom form one - because custom forms as a whole need a giant overhaul
I would love the ability to export custom form details, or approval workflow information to PDF. This would be useful to share with users outside of Workfront, bring to meetings, etc.
We have very extensive deliverables on offer for our requestors within our custom forms. Many of those deliverable selections need to be routed directly to different teams to handle the work. Currently, the only way to route directly to a team is by using Queue Topics. Because we have so many deliverable types using conditional logic, it would be unfeasible to create the direct routing this way. Hence, we would be very interested in a future function that allows routing to specific teams based upon custom form selections.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.