======Translation Customization======

<wrap em>Produmex Manufacturing is a legacy product and Boyum IT Solutions no longer sells new installations for it.</wrap>

The translation customization feature can be used for creating custom translations. It is also possible to create custom translation for a given SBO user only. 

Open the Translation customization via the following path: Tools > Produmex Manufacturing > Developer Tools > Language BxDictionary > Translation Customization

{{ :implementation:manufacturing:customguide:translation:access_path.png |}}

=====1. Change the value on the Translation Customization form =====
====1.1. Find the value====
Add the text you would like to customize as the ‘Value’. Only the exact search text will be matched. To search based on partial text, use asterisk (*) as a wildcard. 

Space characters will be considered. 
The filter is not case sensitive on MSSQL.

Example: 
  * Search for ‘allocation window’ {{ :implementation:manufacturing:customguide:translation:allocation_window.png |}}
  * Search for ‘window’ {{ :implementation:manufacturing:customguide:translation:window.png |}}
  * Search for ‘allocation win*’ {{ :implementation:manufacturing:customguide:translation:allocation_win.png |}}
  * Search for ‘* window’ {{ :implementation:manufacturing:customguide:translation:window2.png |}}

Select the language from the dropdown list. Supported languages: 
  * cs-CZ: Czech
  * de-DE: German
  * en-US: English
  * es-MX: Spanish (MX)
  * fr-FR: French
  * hr-HR: Croatian
  * hu-HU: Hungarian
  * it-IT: Italian
  * ja-JP: Japanese
  * nl-NL: Dutch
  * pt-BR: Portuguese (BR)
  * pt-PT: Portuguese
  * ru-RU: Russian

The list also can be filtered based on the following:
  * Key 
  * User Code 
  * Customized (possible values: Yes, No, Both)
  * Resource File Name 

If you search for a value in a language other than English, and you would like to display the English value as well, check the 'Display Original' checkbox.
  
Press the ‘Find’ button to start the search.

Please note: The maximum number of rows to display is 500. If the specified filters add more than 500 lines as a result, only the first 500 lines will be displayed. It is recommended to select more restrictive filters. 

To clear the specified filters, click on the ‘Clear Filters’ button. 


===Grid===
**//Key//** \\
The localization key that will be used for translation. 

**//Value//** \\
The translation value. The text that will be displayed on the interface. 

**//User Code//** \\
The SBO user code. If a translation is applied for every user, the asterisk (*) is displayed.

**//Language//** \\
The language of the translation. 

**//Customized//** \\
Marks whether the translation value is customized or not. If the checkbox is checked, the translation value is customized.

**//Resource File Name//** \\
Identifies the origin of the translation value. 
  * D & T stand for the translation of database values (eg. user tables, user fields, valid values)
  * L & F stand for the translation of localization values (eg. buttons, functions, system messages)
  * R stands for the translation of report values

<WRAP round tip>To check the translation key and the resource file name code on the interface, enable ‘Change Debug Mode’ from Tools > Produmex Manufacturing > Developer Tools > Language BxDictionary.

Translation values are displayed in the following format: //(resource file name:key: value)//

{{ :implementation:manufacturing:customguide:translation:debugmode.png |}}

Please note: the key and resource file name code is not displayed on standard SBO documents.</WRAP>

====1.2. Add the custom value====
Click in the value field and enter the custom value. You can specify the user code and add a comment as well. 

Click on the ‘Update’ button. 

In order to apply the changes, restart the Produmex Manufacturing add-on. 

====1.3. Remove values====
Right-click on the row that you would like to remove and select the ‘Delete row’ option. Click on the ‘Update’ button to apply the changes. 

=====2. Import custom values =====
Custom translation values can be imported from a .csv file. Click on ‘Import Translation Customization from CSV’ option from Tools > Produmex Manufacturing > Developer Tools > Language BxDictionary. Then browse the .csv file.

After a successful import, the system reloads the translation files and displays the following message: 

//“Translation files reloaded. Current language is en-US. “//

===File structure===
  * Resource File Name: Identifies the origin of the translation value.
  * Key: The localization key. 
  * Language: The language code.
  * Value: Add the custom translation value here.
  * Comments: Remarks can be added here. It is possible to leave this field empty.
  * Customized: Marks whether the translation value is customized or not. Possible values: True/False.
  * User code: The SBO user code. To add a translation for every user, add *. 
  * Add-On: The identifier of the add-on. Add ‘BXPPS’.

Use TAB as the separator between the columns in the .csv file. 

Please note: Both the resource file name and the key are needed in order to identify the object. We recommend to check the resource file name and key on the Translation Customization for Produmex Manufacturing form or to export the Translation Customization table to a .csv file and customize the values in the exported .csv file. 

Example .csv file:
<code>Resource File Name	Key	Language	Value	Comments	Customized	User Code	Add On
D	BXPABSRSN	en-US	AbsReason		True	*	BXPPS
L	BoMTree	en-US	Product structure	For manager only	True	manager	BXPPS</code>

{{ :implementation:manufacturing:customguide:translation:imported.png |}}

{{ :implementation:manufacturing:customguide:translation:translation_result.png |}}

=====3. Export Translation Customization table=====
To export the Translation Customization table to a .csv file, select ‘Export Translation Customization table to CSV’ from Tools > Produmex Manufacturing > Developer Tools > Language BxDictionary. 

The entire table will be exported. It is not possible to only export selected lines of the table.