Uploads and downloads of what? T-Kits? Assets?

Hi Eric,

Many thanks for your quick reply! I am talking about translation files. The PM said that this may take 45 to 60 minutes per file and they have 150 for an upcoming project.

When you say translation files, are we talking about files that have already been translated or those that have yet to be translated? Given the above i anticipate it is the files that have yet to be translated.

That's correct, I asked for more details: "we select the tasks and then click the "export" button, which generate a WS package". I think what they want to automate is this action sequence. I understand this takes 45-60 minutes, then they have to go back again to do the next package. Please let me know if there is any existing automation similar to this? 

That's correct, I asked for more details: "we select the tasks and then click the "export" button, which generate a WS package". I think what they want to automate is this action sequence. I understand this takes 45-60 minutes, then they have to go back again to do the next package. Please let me know if there is any existing automation similar to this? 

They are creating what is otherwise referred to as a t-kit. What is taking so long is not the downloading of the files but rather the collection of the TM's that are being referenced by the files being downloaded. Are you familiar with what auto acitons are in WorldServer? I believe SDL has one that creates a t-kit and attaches it to a project attribute OOB. This would then give them the file they want and the waiting would be happening before a user got involved. The downside to this approach is that if there are new TM matches that come into the system before they download that file (but after the file was created), the package won't have those new TU entries.

Unfortunately I am not familiar with "t-kit". What I was thinking was to do a Python script runnng on the client. We did something similar for beglobal, it automatically download all output files, since there is no "download all" button. Note that I'm not sure if this is feasible yet. Please let me know if you know of any existing solution that is more of a web ui testing approach?

A tkit is just another name for the files you are already going to be working with. If you want to do it through the UI then i don''t know of any existing automated ways to do it. Automating the creation of the files to download per project using an AA is what i would do if the need were presented to me. Then downloading them would be a matter of a few minutes at most.

Hi Eric, thanks so much for looking into this! I will let you know if I find something.

Thierry, the Automatic action Eric refers to is the "Generate Translation Kit" and is a very popular automatic action among our customers. Export packages are exported automatically and in the background by the workflow engine and attached to a project attribute from which a user - i.e. a translator - can download the package from. As perfectly explained by Eric, what might take long is the export process, which includes converting the source files files to bilingual Studio files, exporting the relevant portion of the TM, the Term Database, and possibly a custom file type and include them in the WSXZ package.

The download part of the manually exported package is the fastest part. That is why using an Automatic Action is an efficient way to work with packages. Users will only need to download their package and open it in Studio 2019. This article explains how to configure such an Automatic action in your workflow:

https://gateway.sdl.com/CommunityKnowledge?articleName=000005487

The article is very detailed, but if you need assistance with the workflow configuration, I recommend that you engage the SDL Professional Services team. I hope this helps you!