Last week we launched the Studio 2015 SR2 beta, more about that here. Together with this release we're adding 2 new API's that enable custom development for new scenarios.

Batch Task API

A task is a process that is performed on an individual file or group of files (for example an entire project). Until now batch tasks where defined by the system and all that it was possible was to add them in a task sequence and run them in a specific order. With this new API new custom batch task can be created that can perform various action on files.

Documentation

 Checkout our new developer hub page.

Things to consider

• For the time being the documentation is limited just to the source code and is not having any additional content.
• This is the first public release so please be patience and for any questions or problems don't hesitate to ask in the community.
• You can find a sample application here. This custom batch task is exporting a bilingual file in an excel file.

Terminology Provider API

Multiterm was the de facto terminology provider that was available in Studio until now. This new api allows development of all kinds of terminology providers that will work in a similar way as multiterm terminology inside Studio. Building a new terminology provider requires to build a custom viewer inside studio but the term recognition, search and adding terms are exactly the same.

Documentation

 Checkout our new developer hub page.

Things to consider

• For the time being the documentation is limited just to the source code and is not having any additional content.
• This is the first public release so please be patience and for any questions or problems don't hesitate to ask in the community.
• You can find a sample application here. This custom terminology provider is able to use excel files as terminology source and can work even with large excel files that have ten's of thousands of records even hundred of thousands.
• At the moment there is no way to edit the settings once a provider has been added. This will be fixed in the next CU's
• Credential store has a dependency on internal API that is not public and for the time being can't be used. This will be probably fixed in the next beta release or the final SR2 release
• Any custom provider must provide a custom term viewer. We are thinking of removing this mandatory dependency but we also want your feedback on this.

Happy coding.