110
edits
Changes
no edit summary
This article will provide you an overview of the configuration of custom fields in multiple languages. [[System Administrator]]s are able to '''export''' [[Custom Fields|custom field]] translation settings and '''import''' [[Custom Fields|custom field]] translation setting files. The '''Translation Import''' and '''Translation Export''' tabs are available within any Custom Fields Settings page. ==Best Practices==* The usual process to deploy a system in multiple languages would be to first configure all of the processes in one language. Then, all of the custom fields are translated in the additional language(s). External user pages are enabled in multiple languages more often than entire systems.* Unless you are a native speaker, use a translation service to provide the translated field captions.* The exported translation file can contain tags such as HTML formatting or sslogic so when translating the content, remember to retain the original format.* For [[Custom Field Type: Select One – Combo Box]], ensure your translation file retains the store-value= Creating Translation File display-value syntax.* Some custom field types such as [[Custom Field Type: Special - Arcadia Advanced Data Table]] benefit from manual updating rather than import of the translation file. ==Configuration – Essentials==
1. Go to the UTA, in this case we will go to the Submission Manager<br />
2. Go to Configuration Settings<br />
3. Go to Level 1 Custom Fields<br />
4. We want to Create a Translation File for all custom fields in this UTA.<br />
5. Select the check box at the top to Select All custom fields. <br />[[File:TranslationExport1.png|thumb|none|800px|Create translation file export button]]<br />
6. Click the "Create Translation File" button at the top.<br />
7. Select the file format, for this case we will use Excel 2010.<br />
[[File:Translationfile2.PNG|750px|Select file format]]<br />8. Delete Go back to the first column of each Setting/Property as Custom Field page and click the second (duplicate) column will be what "Text Import" button at the translation will betop.<br /> == Accessing the Translation Import/Export Tabs - Classic ==# Go to [[Global Settings]]#: [[File:GlobalsettingsTranslationImport2.PNGpng|thumb|none|800px|Select Text Import]]<br /># Under [[System Variables and Custom Fields]], click on 9. Paste the data from above in the hyperlink for [[Custom Fields]]#: [[File:GSCustomFieldsbox shown.PNG]]# Using Make sure to select the left menuColumn Delimiter, we will select the [[Custom Fields]] you would like to translateTab in this case. The associated custom fields will load within the main window once selected.#: [[File:CFSelect.PNG]]# Above Select the list of custom fields you will see a imported language dropdown selection field. Use this to select Select the language you wish to add translations for.#: [[File:CFlanguage.png]]# With a language other than English (Default) selected you will notice appropriate options in the ''Import'' box and ''Export'' tabs have now changed to ''Translation Import'' and ''Translation Export''. These tabs provide you click the ability to export the existing field translation settings for the selected language in XML format, or import XML-formatted field translation settings"Analyze" button. <br />#: [[File:CFtranslate_imp-expTranslationImport2.png]] == Translation XML Sample Breakdown ==The following are samples of Translation XML files and how to update |thumb|none|800px|Choose the data.<pre><customfield> <language>14</language> <id>1234567</id> <caption><span style="color:red">Are you a charitable organization?</span></caption> <captiontranslation><span style="color:red">¿Eres una organización de caridad registrada?</span></captiontranslation> <formatxml> <audit>1</audit> <maxp>0</maxp> <searchable>0</searchable> <wvp>,</wvp> </formatxml> <formatxmltranslation> <audit>1</audit> <maxp>0</maxp> <searchable>0</searchable> <wvp>,</wvp> </formatxmltranslation> <options>No;Yes</options> <optionstranslation>No;Sí</optionstranslation> <numberformat></numberformat> <numberformattranslation></numberformattranslation> <tabname></tabname> <tabnametranslation></tabnametranslation></customfield></pre> Translations for the above field are contained within the following XML tags:* <captiontranslation> </captiontranslation>* <formatxmltranslation> </formatxmltranslation>* <optionstranslation> </optionstranslation>* <numberformattranslation> </numberformattranslation>* <tabnametranslation> </tabnametranslation> ; <language>14</language>: This tag contains the language ID. See the [[Languageimport]] page for a list of language IDs.; <id>1234567<br /id>: This tag contains the [[Custom Field ID]]. This is used for matching when importing the file and must remain exactly as exported10.; <captiontranslation> </captiontranslation>: These tags contain Map the translated [[caption]] as will be visible columns to match the columns in the end user with excel sheet followed by clicking the matching language ID settings"Parse Data" button.; <optionstranslation> <br /optionstranslation>: Should the field be a [[Custom Field TypeFile: Select Many – Check BoxesTranslationfile6.PNG|checkbox]] or [[Custom Field Type: Select One – Combo Box1000px|combo boxMap the columns for import]] field, you will be provided with this tag in which to enter the translations for the options. ; <tabnametranslation><br /tabnametranslation>: 11. This tag controls window will make sure that the translation fields are mapped correctly, if there seems to be an error in any of these, it will not be parsed into the [[Tabs#Navigation_Bar_Tabs|tab]] in which instance. Once checked, click the "Upload" button, it will then show if the field existsfields are Successful or Failed.
==See Also==