Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

mhigdonNew Participant

Support Proofing for Google AssetsNew

Description - It's great that Microsoft documents like Word, PPT, etc. are supported by Workfront's Proofing tool. We have used this tool with MS products for roughly 10 years. However, Google Documents like Docs and Slides are not supported with the proofing tool. This means when someone includes a Google Doc in their Workfront request/issue, it cannot be converted to a proof by Workfront. This allows for the document to continually be revised without knowledge from those using Workfront or going back to review a document later. Why is this feature important - In order for us to continue using Workfront as a marketing request queue and compliance approval workflow, it's extremely important that the Google Document being added to Workfront does not change while the various teams are reviewing and providing their approvals. Often, our reviewing teams will reject and/or provide edits to a client using the proofing tool, which allows Marketing the opportunity to completely overhaul the document or simply make small edits. It depends on the feedback given from the reviewing team.Once approved, we need the proofing tool to freeze that document in time so that regardless of what the document owner is doing in Google Docs, it is clearly documented what was approved by compliance. This matters when government regulators come in to audit various marketing campaigns and assets. Up until this point, we have used Microsoft products which are all supported by the proofing tool. Google is not, and our entire organization has transitioned to using the Google suite of products.Current Behaviour and workaround - This means we have to institute a cumbersome work around until this is working for Google Docs. Our teams will have to download their Google document as a PDF, then upload it to Workfront so that the proofing tool can function as intended. This is not sustainable over time.We need Workfront's proofing tool to support Google documents.

skyehansen
skyehansenNew Participant

Reduce reauthentication between versions of an interactive proofNew

Description - This feature request is related to interactive proofs where the URL of the proof requires authentication, and the proof is being viewed using the desktop proofing viewer    Current Behaviour - Currently if we authenticate into the most recent version of the proof, and we wish to refer to a previous version of the proof, it will force us to authenticate into the previous version as well. If I try to skip the authentication process on the most recent version of the proof (because I already know I want to look at a previous version), the authentication process will error out on me.   How would you like the feature to work - If both proof versions are going to the same URL, and I have already authenticated to view one, I want to be able to switch to a previous version and not have to authenticate again. This could be done if the proofing viewer would allow all versions to access the same cookie, or if desktop proofing viewer integrated with microsoft authentication library (aka MSAL)   Why is this feature important to you - First, it is very time consuming to have to authenticate over and over (think if I have to reference a set of 5 versions of the same URL in order to see proof comments). Next, the error I am getting because I'm trying to avoid authenticating every time I open the proof (because I don't wish to look at the most recent proof) is very frustrating and I don't think our users will necessarily understand what is going on so it will waste time on our side to coach or troubleshoot them past this