Workfront and other Adobe tools unification - migration to cloud affected our document sharing | Community
Skip to main content
Level 4
July 26, 2024
Question

Workfront and other Adobe tools unification - migration to cloud affected our document sharing

  • July 26, 2024
  • 1 reply
  • 452 views

Hi All, 

I am curious to see if any of us here have moved/ migrated WF to cloud?

when i say that we would had our WF link https://<companyname>.my.workfront.com

and the new cloud link will redirect to open WF with new URL starts with https://experience.adobe.com

 

While this was a great release and as creative operation lead this was a great news for us to ensure we don't multi login our product, but having one time and switching between was a great unification. however, as this was released and within couple of hours we realised the document links to the project shared with other user who have to act on the document to review (yes, the user has manage access to project, so its not access issue) cannot open any document. Neither can I open document with experience cloud WF document link as an admin. 

I am curious to see if any of us have encountered this issue? and did you hear any solution for the same. 

 

Solution from support now to our issue - the production instance is pulled out of unification and asked us to use WF as previous with old link. 

 

Note: Fetching document link or project access is not an issue. Document links are fetched as usual and we share document links within our group who are assigned to the task and have access to projects.  

 

Enclosing errors that we see.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Kurt_Jones
Community Advisor
Community Advisor
August 21, 2024

Sujatha,

You may already have an answer by now but wanted to response.  Our instances also experienced this similar error after moving to the Adobe unified shell.  There were other clients seeing this issue and support was aware and looking into the overall issue.  I can say over the past month or so since the last monthly release that we've not experienced the error so corrective action may have come as part of a release.