Ability to Save versus Submit a request - many requests are large and require the ability to be built out and saved before final submission. This is becoming more and more important as we push towards having ALL required information in a Workfront request.
This would be a tremendous capability to have - sometimes our team begins a request but doesn't have all the required info, so has to go back and ends up losing all the previously entered info in the request. Please advise on an ETA for this feature.
Thank you for your votes and comments! This functionality is on our roadmap and planned for 2019. Be sure to attend our roadmap calls to get the most up-to-date information.
As a new user and in the process of launching WorkFront to my Marketing team, this is one of the issue we strongly feel that it need to be improve and put in place ASAP - many requests are large and require the ability to be built out and saved before final submission
Piggybacking on Jay's comment, to have this feature roll out sometime in 2019 is too long of a wait. What can we do in order to push development on this to influence an earlier release date?
In our organization, we're implementing a new process which will be more effective if this functionality exists. Thank you.
As an update on this, the feedback you have provided on this area in general is being incorporated in a large initiative on heavily improving the intake experience. As it is a large initiative, the ETA goes out of the guidelines set for Idea Exchange Planned ideas, hence we are marking this as Not Planned. However, we will be reaching out proactively during the research phase of the aforementioned initiative for further details and feedback on the topic.
This was one of the original requests from our clients when investigating a new system. Clients want to start a request but they might not have all of the detail right away. They want to save it (pre-submittal to the agency), add more info later, then submit it. This helps the client side, but also helps our agency side because then we could make more fields required before submitting. Right now we don't require certain fields to submit but we do require them before we can officially start work.
Yeah we developed a hack-around for this with our implementation specialist, but it's messy and our requestors are not happy. The lack of "save as draft" is going to leave our requestors groaning during adoption and may force us to really cut-back on using Custom Forms for intake (and go back to attached Word docs). The sooner we can make this work, the better.
This is something my organization needs and internal departments are begging for. Not having this on the intake process is hindering further adoption within the organization.
