1 Reply Latest reply: Aug 20, 2012 3:37 PM by Ron M-Oracle RSS

    Any PLM4P Info on Multiple Language Configuration & Usage?

    BeckieC
      Are there any white papers or tutorials on how to best configure custom data elements in PLM4P application for multiple languages? We can translate with free text cells on custom sections, but I cannot find avenues to translate spec classification data and taxomony in ADMN or workflow status in WFA, etc ... so that we can configure these items to display in the users' UI language which is not English.
        • 1. Re: Any PLM4P Info on Multiple Language Configuration & Usage?
          Ron M-Oracle
          Setting alternate language values for some of these data admin items, like Specification Categories, must be done via database scripts.

          Please back up your database prior to performing inserts.

          Spec Categories are grouped by spec type (eg, 1004 for Material/Ingredient Spec, 2147 for Trade Spec, etc). The following query shows the various spec category groups.

          SELECT * FROM commonTaxonomyNamespace order by NamespaceID

          For Trade Specs, for instance, the NamespaceID is GSMTaxonomy2147, and the PKID you'll need is '21404D2D82BE-9342-4938-91F1-26D2DB1327A7'

          To see the values of the Trade spec categories, you can run the following:

          SELECT * FROM commonSMILTaxonomyNode cat
          inner join commonSMILTaxonomyNodeML catName on cat.pkid = catName.fkSMILTaxonomyNode
          where cat.fkTaxonomyNamespace = '21404D2D82BE-9342-4938-91F1-26D2DB1327A7'

          To insert new translations to an existing entry, you'll have to insert into the commonSMILTaxonomyNodeML using the same PKID and fkSMILTaxonomyNode values, but a different langID value. To see an example of multiple language values in this table, run the following, which will show the '* No Category Available' values:


          SELECT * FROM commonSMILTaxonomyNode cat
          inner join commonSMILTaxonomyNodeML catName on cat.pkid = catName.fkSMILTaxonomyNode
          where cat.fkTaxonomyNamespace = '21404D2D82BE-9342-4938-91F1-26D2DB1327A7'
          and fkSMILTaxonomyNode ='2141144016E5-3EB4-498E-B45C-F18187C2E7D7'