• State Verified Answer
  • Replies 3 replies
  • Subscribers 391 subscribers
  • Views 2544 views
  • Users 0 members are here
Options
Related

Running automatic task for custom batch task plugin

Halil Kerimi

Hi,

I have a tool that creates a filebased project from given template and files and custom batch task that is added in template as task sequence

It was used with Trados 2019 SDK and it was working fine, now that I upgraded the tool to Trados 2021, I have issue.

When I run the tool to create project, I get an error:

"Could not find task template with ID Custom.Batch.Task
---> System.ArgumentException: Could not find task template with ID Custom.Batch.Task
---> System.ArgumentException: Could not find task template with ID Custom.Batch.Task
at Sdl.ProjectAutomation.FileBased.FileBasedProject.CreateComplexTaskTemplate(String[] taskTemplateIds)
at Sdl.ProjectAutomation.FileBased.FileBasedProject.RunAutomaticTasks(Guid[] projectFiles, String[] taskTemplateIds, EventHandler` 1 statusEventHandler, EventHandler`1 messageEventHandler)
--- End of inner exception stack trace ---

The Error happens on this line:

var result = project.RunAutomaticTasks(fileIds, taskId.ToArray());

The same project template works fine with Trados, it finds our Custom Batch Task plugin and processes the files

Also Plugin (Custom batch task) is upgraded to Trados 2021 SDK and installed in Trados

The tool works with templates that do not include our Custom Batch Task plugin

I have tested the Tool with project template that has Custom Batch task downloaded from Appstore (SDLBatchAnonymize)
The tool works if the installed plugin is downloaded from RWS AppStore
Tool doesn't work if I compile the same plugin from GitHub (RWScommunity)

Have someone Experienced something similar?

Thank you!
emoji
Rate translation
×
Suggest better translation
×
Parents
  • +1

    Hi , this issue is most likely due to the fact that the plugin compiled on your computer is not signed.

    While developing you can load and test your unsigned plugin in Trados Studio.  This is possible as the user will see an unsigned plugin message as Studio is loading and they can decide whether or not to continue loading it.

    This is not possible from the Project Automation and poses security concerns in loading, executing unsigned plugins passively. 

    I suggest the following: Once you have completed your development changes and tested it (loading it in Studio), request to sign the plugin from app-signing@rws.com before deploying it to be used in a project automation environment.

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

    emoji
Reply
  • +1

    Hi , this issue is most likely due to the fact that the plugin compiled on your computer is not signed.

    While developing you can load and test your unsigned plugin in Trados Studio.  This is possible as the user will see an unsigned plugin message as Studio is loading and they can decide whether or not to continue loading it.

    This is not possible from the Project Automation and poses security concerns in loading, executing unsigned plugins passively. 

    I suggest the following: Once you have completed your development changes and tested it (loading it in Studio), request to sign the plugin from app-signing@rws.com before deploying it to be used in a project automation environment.

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

    emoji
Children