News & Blogs

Important Announcement: End of Life for TMS on December 31, 2025

Georgiana Iancu — Mon, 21 Oct 2024 07:01:34 GMT

Dear Customers, We have some significant news to share about our Translation Management System (TMS). After extensive feedback from you, we have decided to transition away from TMS, with an end-of-life date set for December 31, 2025. This decision is...(read more)

Vendors in SDL TMS

David Pooley — Tue, 12 Nov 2019 15:30:00 GMT

Introduction What is a Vendor? In SDL TMS, a Vendor is a localization service provider to an organization. In most cases, the vendor will be providing translation and/or linguistic review services to the organization. If the Vendor is not marked as p...(read more)

SDL TMS and filter deprecation

David Pooley — Mon, 14 Oct 2019 13:00:00 GMT

Some time ago, SDL announced the deprecation of the original SDL TMS filters that create ITD files, which were originally intended to be translated and reviewed using the SDLX desktop translation software. It is important to note that these filt...(read more)

Important announcement regarding SDL TMS

David Pooley — Wed, 12 Jun 2019 08:07:00 GMT

I wanted to make sure that you all saw the email that went out this week to existing SDL TMS customers. We’ve just announced the availability of a new translation management capability in SDL Language Cloud. It goes a step b...(read more)

TMS: Hierarchy and Setup Reuse - How many orgs and why?

Sandra Franco — Fri, 19 Jan 2018 15:12:00 GMT

SDL TMS is a powerful Translation Management System - and a lot of its power comes from the hierarchical structure.

The ability to have multiple levels (organizations) allows you to decide on:

visibility
content separation
reporting separation

That's great, but what does that mean in terms of setup? Do I need to create all my objects inside all the various organizations?

Not quite.

Of course different people have different ways of working - but my rule of thumb is: create each object at the highest level at which it is both useful, and allowed.

Admittedly, that sentence could sound a bit like it came from a fortune cookie, so let me explain.

First of all, let's look at what your organization structure should look like:

Root Organization: this level comes out of the box and is mandatory. It should be reserved for any Admin level users and any other objects which come out of the box with TMS (like content types).

Professional Services: Insert your company name here! This will be the main node in your setup - the common ground for all the objects which are widely shareable.

Other organizations: This is where you get to build your org structure; in my case, I have two organizations at the same level (siblings) and both with the same parent (Professional Services org). These are also often called sub-orgs to the Professional Services org, in this case.

At this point, you might be asking: yeah, that's great, but

... how do I decide which organizations I need?

Organization will normally be related to departments, or business units, or different teams within your company. They can also in some cases be related to different countries/geographical regions - it all depends on what kind of business, or even content separation makes sense in your particular case.

The Main Reasons for Separate Organizations are:

you want to restrict user visibility for certain parts of the business
- Perhaps you have a group within your business which deals with confidential content, for instance
you need invoicing/costing in different currencies
- each organization can only deal with one currency; if you require more than one, you will need multiple organizations
you need separate reporting across different parts of the business
- perhaps they are different business entities, or respond to different cost centres

You may also decide on having a set of organizations which reflects the structure of the business that TMS instance is associated with - just bear in mind that you will then have separate reporting and separate visibility across those organizations, so always try to find a balance between getting the results you want, and making it realistic to manage.

Remember to always have your corporate node underneath Root - and then work the rest out from there.

On the next post I will cover how to find the best balance between reusing setup and having the right level of visibility.

In the meantime, stay warm!

Announcing new features in SDL Community and SDL Customer Gateway

Sharon Luongo — Thu, 20 Apr 2017 18:56:00 GMT

It is our mission to provide you with a positive experience that helps you achieve maximum success with SDL products and services. In 2016 we launched SDL Customer Gateway, our new Support system, and saw significant expansion in features, forums and participation in SDL Community.

But we’re not stopping there…as part of our continued efforts, we used your recent feedback, and are very excited to announce two new features:

SDL Ideas for enhancement requests in SDL Community

Within SDL Community, you now have one channel, called SDL Ideas, to submit enhancement requests for all SDL products. In these new Ideas Forums, you can:

Submit your own ideas
View and endorse (up- and down-vote) other customers’ ideas
Interact with customers and with SDL Product Management to shape the direction of our products

View this short video on how to use SDL Ideas.

‘Product Requests’ tab in My Support section on SDL Customer Gateway

Within the SDL Customer Gateway, we’ve added a ‘Product Requests’ tab, which provides you with up-to-date visibility on the status of a Product Defect as it progresses from a logged support incident through to development validation, resolution and fix release.

View this short video on how to use the Product Requests tab for Product Defect visibility.

At SDL we’re always on the lookout for opportunities to make it easy for you to engage with us and to help you achieve your business objectives. Hopefully you’ll find these new features useful. We’re “Open for Ideas” so please do come participate and share yours!

Kind regards,

Betsy Fallon, Executive Vice President, Global Client Services Jim Saunders, Chief Product Officer

Coming Soon in SDL TMS

Nazia Sarfraz (former member) — Fri, 16 Dec 2016 10:53:00 GMT

New for 2017

SDL TMS inbox available in SDL Trados Studio - Enabling work in SDL Trados Studio only
REST API Extensions - Enhanced user experience for software integrations with the ability to create or terminate SDL TMS jobs and tasks from other products
Support for SDL Trados GroupShare 2017 - Continue to use the integration capabilities in the most up-to-date software versions
User Experience focus - Continued improvements to the usability of SDL TMS
Defect fixing - Continuous effort to provide smooth experience when using SDL TMS

Upgrade facts

3 days from the release of SDL TMS 11.2, November 2016, the first upgrades were completed
66% of SDL-hosted TMS environment are on TMS 11.2 - only two and a half weeks after the release
92% of SDL-hosted TMS environments are on TMS 11.1 or higher

To ask a question regarding any TMS release please post this in the TMS forum

For information on how to upgrade please review the TMS Upgrade page in SDL Access Customer Community. Please note this is a private customer area, please contact us to express your interest is joining.

For more content like this, please 'like' this page or leave a comment below;