Expand my Community achievements bar.

SOLVED

Proof URL no longer allowing access to users

Avatar

Level 4

After successfully using proof URL's in a report for well over a year, they suddenly stopped working yesterday for my users.
They now come up with a message:

You do not have permission to view this proof. Ask the proof owner to add you to the workflow.

This is not practical in our 100's per day scenario, and has as I say been working fine.

We've made no changes to Workfront or users and these are the same users that have been active over the past year enjoying this facility.

Has something changed in Workfront ?

1 Accepted Solution

Avatar

Correct answer by
Level 2

We were able to get support to assist us for document reports. Then our team figured out how to adjust for proof reports. Hope this works for you.

 

This line works for us for document reports:

valueexpression=CONCAT("https://YOURINSTANCE.my.workfront.com/document/",{ID},"/proof/",{currentVersion}.{proofID},"/view")

 

This line works for us for proof approval reports:

valueexpression=CONCAT("https://YOURINSTANCE.my.workfront.com/document/",{documentVersion}.{documentID},"/proof/",{documentVersion}.{proofID},"/view")

View solution in original post

8 Replies

Avatar

Level 4

UPDATE: I've been on with support and where we've been changed to the unified experience, it would now appear we are pulling the wrong {documentVersion}.{ID} within our text mode.

Can anyone help with the correct text mode to pull a proof link once migrated to the unified experience?

This is what we WERE using:

URL=shortview=true
displayname=Proof Link
usewidth=true
valueexpression=CONCAT("https://YOURINSTANCE.my.workfront.com/document/",{documentVersion}.{ID},"/proof/",{documentVersion}.{proofID},"/view")
valueformat=HTML
width=130

Avatar

Level 2

We are having the same issue. We built a proof dashboard and now it's giving the same error. WF support told us it's the code in our report, but I told them we changed nothing so they'll need to help us correct the code. If they update me with the new code, will share here.  

Avatar

Correct answer by
Level 2

We were able to get support to assist us for document reports. Then our team figured out how to adjust for proof reports. Hope this works for you.

 

This line works for us for document reports:

valueexpression=CONCAT("https://YOURINSTANCE.my.workfront.com/document/",{ID},"/proof/",{currentVersion}.{proofID},"/view")

 

This line works for us for proof approval reports:

valueexpression=CONCAT("https://YOURINSTANCE.my.workfront.com/document/",{documentVersion}.{documentID},"/proof/",{documentVersion}.{proofID},"/view")

Avatar

Level 1

Thanks for your insight — glad to know this is a global issue and not just us.

 

I'm trying to find where to update the text mode — did you replace it in the Proof Report filters? If so, here what I am seeing currently and it doesn't include a line for value expression:

 

approverID=$$USER.ID
approverID_Mod=in
EXISTS:b:$$OBJCODE=DOCU
EXISTS:b:currentVersionID=FIELD:documentVersionID
EXISTS:b:project:status=CPL
EXISTS:b:project:status_Mod=notin
isAwaitingDecision=true
isAwaitingDecision_Mod=eq
isCurrentDocumentVersion=true
isCurrentDocumentVersion_Mod=eq

Am I looking in the wrong place? 

Thanks in advance!!!

Avatar

Level 2

We updated the code located in the columns view, text mode. Not the proof report filters.

Hope this helps.

Avatar

Level 4

Thank you for taking the time to reply @Jennifer1

This has worked for us too and made my users very happy again!

 

 

Avatar

Level 1

Anyone else receiving an a "permissions error" message when they try to access a proof via "My Proofs" — have tested across multiple users at my organization and all are experiencing the same result. We can access proofs other ways, and job info and proof link still appear under the "My Proofs" tab, but when we click on the proof link we get this. 

Avatar

Level 4

We are experiencing exactly the same issue since yesterday.

Support has suggested its because we have moved to the unified set up, but that happened a while back.

This is new... if you find a resolve, please post here.