Why I cannot customize my batch task list in Trados Studio 2024?

Question

Hi all, 
 For some time now (probably jjuz in Rdos Studio 2022, but certainly in Trados studio 2024) it is no longer possible to customize (custom option) the list of Batch taks for processed plks. I know that this option was available before, and I used it and was able to set a list of tasks to be performed for an opened file. Now I have to do it one at a time, e.g. Analyze files first, and then after reopening the file Pre-Translate. 
 
 I don't really understand what has changed and why the custom option is no longer available. 
 Best regards, 
 Lech Lachowski

Jesús Prieto · Answer

Lech Lachowski 
 Customising batch tasks is a feature available only in the Professional licence of Trados Studio. If you have a Freelance version, you can&rsquo;t customise batch tasks. You don&rsquo;t mention the type of licence of your Trados Studio copy, but this is my first guess&hellip;

Paul · Answer

Antonio Jiménez Esteller 
 Can you provide the full error stack for the error please? These screenshots are not helpful: 
 
 Save the xml error you get and then attach to your reply ( Insert - Image/Video/File ). That may point to the problem which could be related to you using old templates in 2024 for example? You cannot do this, especially if you are using plugins as part of your tasks. I am guessing a bit based on your screenshot, but the error stack may tell us more.

Paul · Answer

Antonio Jiménez Esteller 
 It seems as though your project template is missing something and whilst Studio should really handle these things gracefully it's not, possibly because you do seem to use various plugins and have these in your template, so it's unlikely the QA team tested these specific things. Can you try creating a completely new template, not based on anything you had before, and create some custom tasks in there based on the things you have available right now. Then test again with this new template and see if you still have similar problems with it?

Paul · Answer

Lech Lachowski 
 Lech Lachowski said: In my case, after intalling Trados Studio 2024 my previous projects stopped beeing visible on the list. It no should be the case. 
 If you expected this to just be there then this is never the case. The projects list will be empty because there is no migration process of any resources between versions. All Studio versions are completely independent of one another and always have been. 
 Lech Lachowski said: Each upgrade should be compatybile withe the previous, but in the case of Trad Studio, before install any upgrage one shhould clean previous instalation including user file with settings and projects, and then they can install new version. 
 This is not the case. I never clean anything before an installation. 
 Most problems I see with these sorts of things are the result of users attempting (and I don't blame them for this as I would also try to find ways to make it easier if I didn't know better) to brings in resources from an older version to the new product. By resources, I am not referring to TM's, TB's as these always work between versions, but rather things like User Profiles, Project Templates, Filetype Settings. Unfortunately this is never a good idea as you can introduce problems because of incompatibility if you don't know enough about what will work and what won't. Often this can mean understanding more about the versions of specific resources within Studio and this probably goes beyond what any user would spend time on. 
 Antonio Jiménez Esteller 
 Antonio Jiménez Esteller said: Paul, the screenshots I showed are from the scenario you suggest: I deleted the default template, it was automatically re-created blank and I used it. I tried this several times already. 
 The error stack you provided tells us the most likely source of the problem is that somewhere in the code, the templates argument is not being properly initialized or assigned before being passed to the CreateComplexTaskTemplate method. This could be due to things like this: 
 
 A logical error where the templates array is not created. 
 A missing assignment where the templates array is not populated. 
 A condition where the templates array is conditionally assigned and the condition fails. 
 
 Based on the screenshot the areas I would be suspicious about would be where the custom tasks have used plugins. Perhaps you can provide details of the plugins you have used, so I don't have to guess them all, and also confirm what steps the custom tasks consist of? Then I can attempt to reproduce the errors... and I am very happy to try this. If I just reuse the default template on its own I definitely don't get problems, and if I create custom tasks using Studio features without plugins I also don't get problems. This all reinforces my opinion that the problem here lies with more specific actions that you have carried out on your templates.

Paul · Answer

Lech Lachowski 
 Lech Lachowski said: Paul, with all due respect, but a new software version should always be compatible with the previous one. Take, for example, the Google Chrome upgrade (retains user settings, passwords, cookies, history, etc.). Filezilla upgrade does not save saved servers and passwords. Such examples can be multiplied. 
 I agree. I am not disputing this at all, and in fact I do wish we had a better upgrade process that properly managed the transfer of data between versions, and the situation where new features make old ones redundant. We may not be able to automatically support them because we are talking about things a lot more complex than Google Chrome or Filezilla, but we could make sure that they are not taken across into the new software even when a user attempts to do so. 
 All I stated is that there is no migration process of any resources between versions. All Studio versions are completely independent of one another and always have been. This is a fact and I didn't make any reference about what should and shouldn't occur. 
 Lech Lachowski said: Paul said: This is not the case. I never clean anything before an installation. 
 Paul, you are contradicting yourself, since you are not deleting anything the projects and settings should be preserved, which is not the case. 
 No I'm not, you have misquoted me. Context is everything. You said this: 
 Lech Lachowski said: in the case of Trad Studio, before install any upgrage one shhould clean previous instalation including user file with settings and projects, and then they can install new version. 
 But this isn't true, you don't have to clean anything and this is what I was replying to. 
 On reflection I wonder if what you really meant was that you have to move your projects and files from one location to another and cannot reuse the ones that were located in the previous version? If this is the case then this is only partially true. The location of projects is down to you. If you decide to leave them in the default location which is indeed placed into a folder named after the version of the software you used at the time then this is your choice. A more sensible way to work would be to store your projects, Translation Memories and Termbases is a location completely independent of the installation directories. The software supports you doing this. If you work this way then you never have to move them at all. 
 Settings are a different thing and even here the picture is a little grey. Your project settings will stay with the projects, so these are indeed carried over as soon as you open the project in the new version. However, if there are new filetypes in the new version for exa,ple you'll see additional messages in the settings telling you that new filetypes exist for example. That seems logical since they were not in the previous version, but you probably won't really need them in an existing project anyway. 
 Older filetypes that are no longer supported and will not be in the new version are normally supported under the hood. This is so your existing projects created in the older version can be completed successfully, but you should not be able to create new projects with these old and defunct versions. There is a limit to this however, if you open a project from a really old version this may not be the case and you might not be able to save target files for example. But again this is to be expected I think. If users upgrade from version to version there is less likely to be problems but if they don't we cannot be expected to continually support, and provide legacy code in the product for every version we ever created. Fortunately most users upgrade from version to version. Sadly we don't see a balanced view of this in the forums for obvious reasons! 
 I did say that the picture with settings is a little grey and this is because things like project templates are better not reused. I would always advise users to recreate their project templates. This is because older templates will be using older code and potentially introduce problems into the new version. This is an area I wish we did have a neat migration process but this is more complex than you probably think through. That doesn't mean we shouldn't do it, it just means the complexity involved versus the benefits as a whole probably keep this lower in the overall priority and scheme of things. We did look at this once with the migration tool in the appstore but in my opinion it's more trouble than it's worth because we cannot do this properly using the APIs. It really needs to be done at the level of the core product. 
 All in all I'm not contradicting or arguing with you at all. I'm just trying to explain to you how this works and am clarifying the statements you make that seem to be incorrect. 
 Lech Lachowski said: Thank you for your support because no one else wants to report that Trados Studio is very unstable and unusable. 
 I wish!!

Trados Studio > 2. Trados Studio

Why I cannot customize my batch task list in Trados Studio 2024?

Top Replies