Trados Studio
Trados Live Essential/Live Team/Enterprise
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Professional Services
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
XyUser Group
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion UK Meetup
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Live Team Ideas
Trados Live Essential Ideas
Trados Live Terminology Ideas
Trados Enterprise Ideas
Trados Online Editor Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
Hello everyone,
Sometimes when delivering files, particularly to customers who aren't familiar with Flow, they may be unsure how to download their translated documents from the customer portal. If you encounter this situation, you may find the following Knowledge Base article useful:
https://gateway.sdl.com/apex/communityknowledge?articleName=000014387
This article explains certain parts of the interface which may cause confusion and shows where to download the target documents.
Any feedback or questions are welcome!
This is indeed a UX trap that just about every new user in our company falls into. In the early days of using MT7, we had to issue an extra communication to save people from this error (and save us countless…
This is indeed a UX trap that just about every new user in our company falls into. In the early days of using MT7, we had to issue an extra communication to save people from this error (and save us countless calls from users). A rethink on this symbol would be very welcome.