Localizing ICI - Revision history

WikiSysop at 16:07, 14 February 2022

2022-02-14T16:07:43Z

Show changes

AmolRedij at 11:34, 19 January 2022

2022-01-19T11:34:02Z

Show changes

AR at 08:51, 16 December 2021

2021-12-16T08:51:57Z

Show changes

IDT-1 at 05:38, 20 August 2021

2021-08-20T05:38:50Z

WikiSysop at 09:26, 11 June 2021

2021-06-11T09:26:14Z

WikiSysop at 06:22, 21 October 2020

2020-10-21T06:22:54Z

WikiSysop at 06:22, 21 October 2020

2020-10-21T06:22:31Z

WikiSysop at 14:11, 11 September 2020

2020-09-11T14:11:20Z

WikiSysop: Created page with " = Localizing ICM = This topic discusses the scope for localization built as part of ICM. Goal is to enable localization for all English text seen across ICM, for some there..."

2020-09-11T14:09:23Z

Created page with " = Localizing ICM = This topic discusses the scope for localization built as part of ICM. Goal is to enable localization for all English text seen across ICM, for some there..."

Show changes

@@ Line 41: / Line 41: @@
 *ICI configurations should happen in English only.
 *For user-defined fields, localized strings will be added from the backend after configuration is completed. Subsequent additions and changes to these fields may require additional changes to the localized strings in the Database.
 == Localization support across ICI ==
@@ Line 57: / Line 58: @@
 *Notification Category and Events
 *Reason Codes
 For example, Administrators can enter corresponding German values for Draft Status as Entwurf through “Translations Editor” tool.
-<div class="image-green-border">[[File:7.16 Localization 1.png|720px]]</div>
+<div class="image-green-border">[[File:7.16 Localization 1.png|720px|7.16 Localization 1.png]]</div>
 The draft status will then be displayed in German for a user with language preferences set to German.
-<div class="image-green-border">[[File:7.16 Localization 2.png|720px]]</div>
+<div class="image-green-border">[[File:7.16 Localization 2.png|720px|7.16 Localization 2.png]]</div>
 The UI elements will be displayed in English if there are no local values available in preferred language for that specific element in the ICI system.

@@ Line 41: / Line 41: @@
 *ICI configurations should happen in English only.
 *For user-defined fields, localized strings will be added from the backend after configuration is completed. Subsequent additions and changes to these fields may require additional changes to the localized strings in the Database.
 == Rules implementation for localized masterdata attributes ==
@@ Line 211: / Line 235: @@
 #'''Verify '''and '''click '''''Create''. The ''Secondary Clause ''is created.
 <div class="image-green-border">[[File:7.12 Localized Cluases 2.2.png|720px|7.12 Localized Cluases 2.2.png]]</div> <div class="image-green-border">&nbsp;</div>
 ==== <span style="font-size:larger;">Create the Template</span> ====
@@ Line 333: / Line 356: @@
 Users can create a saved search on associations to tag in a template using the ''Saved Search'' functionality. The search is saved as a global search.<br/> For example, the ''SavedSearchwithculturecode_Annexure1'' is created for associated documents ''Automation Annexure Assembly.''
 <div class="image-green-border">[[File:7.12 Associations content localization 1.png|720px|7.12 Associations content localization 1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
 ==== <span style="font-size:larger;">Creating the Template with Associations</span> ====
@@ Line 370: / Line 392: @@
 Similarly, create a template with the tagged associations without language (without culture code) through ''Icertis Experience for Word.'' For example, the ''MDL Agreement Basic Template.''
 <div class="image-green-border">[[File:7.12 Associations content localization 6.png|720px|7.12 Associations content localization 6.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
-−
 ==== <span style="font-size:larger;">Configure the Template Selection Rule</span> ====

@@ Line 333: / Line 333: @@
 Users can create a saved search on associations to tag in a template using the ''Saved Search'' functionality. The search is saved as a global search.<br/> For example, the ''SavedSearchwithculturecode_Annexure1'' is created for associated documents ''Automation Annexure Assembly.''
 <div class="image-green-border">[[File:7.12 Associations content localization 1.png|720px|7.12 Associations content localization 1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
 ==== <span style="font-size:larger;">Creating the Template with Associations</span> ====
 User can create a Template with associations tagged as a table or as a saved search.
-<div class="note-box">Note: The template with tagged associations can only be created with Icertis Experience for Word Scribe.</div>
+<div class="note-box">Note: The template with tagged associations can only be created with Icertis Experience for Word.</div>
 To create a template with associations:
@@ Line 369: / Line 370: @@
 Similarly, create a template with the tagged associations without language (without culture code) through ''Icertis Experience for Word.'' For example, the ''MDL Agreement Basic Template.''
 <div class="image-green-border">[[File:7.12 Associations content localization 6.png|720px|7.12 Associations content localization 6.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
 ==== <span style="font-size:larger;">Configure the Template Selection Rule</span> ====

@@ Line 211: / Line 211: @@
 #'''Verify '''and '''click '''''Create''. The ''Secondary Clause ''is created.
 <div class="image-green-border">[[File:7.12 Localized Cluases 2.2.png|720px|7.12 Localized Cluases 2.2.png]]</div> <div class="image-green-border">&nbsp;</div>
 ==== <span style="font-size:larger;">Create the Template</span> ====
@@ Line 232: / Line 233: @@
 </ol>
-You can create clauses and the template with tagged localized clauses also through ''Icertis Experience for Word Scribe.''
+You can create clauses and the template with tagged localized clauses also through ''Icertis Experience for Word.''
 &nbsp;

@@ Line 1: / Line 1: @@
-= Localizing ICM =
+= Localizing ICI =
-This topic discusses the scope for localization built as part of ICM. Goal is to enable localization for all English text seen across ICM, for some there are technical challenges and hence are kept out of scope. This document calls out both in-scope and out-off scope areas to ensure there are no gaps.
+This topic discusses the scope for localization built as part of ICI. Goal is to enable localization for all English text seen across ICI, for some there are technical challenges and hence are kept out of scope. This document calls out both in-scope and out-off scope areas to ensure there are no gaps.
 Garbage in Garbage out (GIGO):&nbsp;User input in any language will be accepted, stored and displayed as entered/stored.
@@ Line 39: / Line 39: @@
 *Customers have the ability to add support for additional languages. Translations for a new language&nbsp;provided by the customer, will be uploaded from the backend.
-*ICM configurations should happen in English only.
+*ICI configurations should happen in English only.
 *For user-defined fields, localized strings will be added from the backend after configuration is completed. Subsequent additions and changes to these fields may require additional changes to the localized strings in the Database.
 == Rules implementation for localized masterdata attributes ==
-User can localize masterdata attribute values and further refer its values in lookup across ICM. If there is any rule configured for such lookup, changing lookup value will evaluate the rule. The rule configured in English will be evaluated upon changing its lookup values also in languages other than English.
+User can localize masterdata attribute values and further refer its values in lookup across ICI. If there is any rule configured for such lookup, changing lookup value will evaluate the rule. The rule configured in English will be evaluated upon changing its lookup values also in languages other than English.
 === Localizing Masterdata Attributes ===
-Users can localize masterdata attribute and further refer its values across ICM.<br/> To localize masterdata attribute:
+Users can localize masterdata attribute and further refer its values across ICI.<br/> To localize masterdata attribute:
 Let us consider an example where ''Chemical Product Master ''is a masterdata contract type with attributes such as ''Chemical Name, Chemical Usage Details'' which has localized values.
@@ Line 65: / Line 65: @@
 You can edit existing masterdata contract type to configure the attribute as localized.
-<div class="note-box">Note: Administrators need to upload translations for the localized attribute values in ICM through database upload or the ''Translator Tool ''from ''Admin Task''.</div>
+<div class="note-box">Note: Administrators need to upload translations for the localized attribute values in ICI through database upload or the ''Translator Tool ''from ''Admin Task''.</div>
 &nbsp;
@@ Line 184: / Line 184: @@
 === Localization support for Clauses into Templates ===
-Previously in ICM, there was no provision to have localization of clauses that could be used to create agreements in different languages. Hence, the users had to create multiple templates to be able to create agreements in different languages.<br/> With this release, users can create secondary clauses as the localized versions of a primary clause and enable them through configured template and rules. The corresponding clauses get assembled in the agreement as per the language selected in the Agreement Language attribute during the agreement instance creation. This considerably reduces the efforts of creating and managing multiple templates to support different languages.
+Previously in ICI, there was no provision to have localization of clauses that could be used to create agreements in different languages. Hence, the users had to create multiple templates to be able to create agreements in different languages.<br/> With this release, users can create secondary clauses as the localized versions of a primary clause and enable them through configured template and rules. The corresponding clauses get assembled in the agreement as per the language selected in the Agreement Language attribute during the agreement instance creation. This considerably reduces the efforts of creating and managing multiple templates to support different languages.
 ==== <span style="font-size:larger;">Create localized clauses</span> ====
@@ Line 217: / Line 217: @@
 To create a template through I''certis Experience for Word:''
-#'''Click '''''ICM ''tab on ''Icertis Experience for Word ''and log in to the ICM UI instance.
+#'''Click '''''ICI ''tab on ''Icertis Experience for Word ''and log in to the ICI UI instance.
 #'''Click '''''Create ''in ''Template ''ribbon. The ''Create Template ''window opens.
 #'''Select '''the ''Contract Type ''for which you have enabled the localization for clauses into template. For example, ''ClauseLocalizationCT''.
@@ Line 326: / Line 326: @@
 === Localization of Associated document content in the agreement ===
-Earlier in ICM, if the language preference was English and the user created an agreement using a French language template that had an association as a table, then the buyer could create the association instance and assemble the contract. However, the language for the entire assembled document would be French, but the association table header (title) would be in English.&nbsp;<br/> This functionality has been improved so that the table header also appears in the same language as the remaining text in the template. In the example above, the entire assembled document as well as the association table header would be in French.
+Earlier in ICI, if the language preference was English and the user created an agreement using a French language template that had an association as a table, then the buyer could create the association instance and assemble the contract. However, the language for the entire assembled document would be French, but the association table header (title) would be in English.&nbsp;<br/> This functionality has been improved so that the table header also appears in the same language as the remaining text in the template. In the example above, the entire assembled document as well as the association table header would be in French.
 ==== <span style="font-size:larger;">Creating a Saved search on associations&nbsp;</span> ====
@@ Line 338: / Line 338: @@
 To create a template with associations:
-#'''Click '''''Insert ''> ''Add-ins'' > ''My Add-ins ''> ''See All'' > ''Shared Folder ''in ''MS Word''. The list of ICM shared Add-ins opens.
+#'''Click '''''Insert ''> ''Add-ins'' > ''My Add-ins ''> ''See All'' > ''Shared Folder ''in ''MS Word''. The list of ICI shared Add-ins opens.
 #'''Select''' the instance. The ''Icertis Experience for Word ''opens.
 #'''Click '''''Create Template''. The ''Details ''tab opens.