cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

translations should be stored in product context

0 Kudos

translations should be stored in product context

By default, translations of dynamic documents are stored in a common library for all products.

Normally, in an organization you have different products with different permission settings. Storing all translations in a library makes the restricted content available for all.

Now, we have to organize this library in folders for every windchill product and then set permissions on folders inside this library. Which is a hell of job.

Translations are just another representation of the same content and belong in the product where they are created. We consider the current methodology as a fundamental design flaw.

2 Comments
Marble

Although the default behavior is to put all translations of all products in a single library, it is possible to store them in their source product. Depending on how much content you have and how you access your data, you might suffer from performance issues if you do so. In that case you can decide to store your translations in a library per product so that you can manage your permissions better while you still keep them out of your product container so not impacting performance.

In our case, it is not a problem to keep them in the source product.

I consider this case closed. However, managing product specific data outside a product container is counter intuitive and in contrast with business rules. So I would still advise PTC to assess the default behavior.

Garnet

Yes, the location can be set at the context level.  We set the default as a shared Library to make it easier to try an example, but I agree that many customers need to change the default for their requirements.