You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page:
Return to Localizing ICI.
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): User input in any language will be accepted, stored and displayed as entered/stored.
Localization currently supports these languages out of the box:
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.
Users can localize masterdata attribute and further refer its values across ICI.
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.
You can edit existing masterdata contract type to configure the attribute as localized.
To reference localized masterdata attribute in lookup attribute:
You can edit existing agreement contract type and configure a lookup type attribute to reference localized masterdata attribute.
You can configure any type of rule for lookup attribute that references localized masterdata attribute.
For example, configure an event rule for Saas Agreement contract tyep lookup attribute which references localized masterdata attribute Chemical Name.
To configure an event rule with localized masterdata attribute:
Refer to Rules for details on configuring other types of rules.
Users can create the agreement instance for the contract type which has a lookup attribute referencing localized masterdata attribute. The rule configured in English for such lookup will get evaluated upon changing its lookup values in languages other than English. Localization of rule implementation will work with the languages set through Locale Settings in Preferences.
For example, create a new agreement instance in French language for Saas Agreement contract type :
Chemical Name lookup references localized masterdata attribute Chemical Name. Changing its value evalutes the Approver rule (Approver – RG) and adds the approvers to the agreement’s team.
The masterdata Agreement Language Master defines the attributes to store languages that will be used to create the localized agreement. Users can create instances of the Agreement Language Master contract type to add new languages.
The Agreement Language attribute is added to the contract type to enable the localization support for agreements. The localized agreement is displayed in a language selected in the Agreement Language attribute during agreement instance creation.
To add the agreement language attribute to the contract type to enable the clauses localization in a template:
You can edit existing contract type to add agreement language attribute and enable the clauses localization into template for that contract type.
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.
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.
Users can create secondary clauses in different languages as the localized versions of a primary clause in a parent-child relationship. Then a template can be configured with the primary clause that will be replaced with secondary clauses as per the selected agreement language and the configured rule to create localized agreements. This reduces the efforts to create and maintain many localized templates.
To create a primary clause:
Users can create a template in which the localized clauses can be tagged and assembled as per the configured rules. With this, only one template with primary clause needs to be created which saves efforts to create and maintain number of localized templates.
To create a template through Icertis Experience for Word:
You can create clauses and the template with tagged localized clauses also through Icertis Experience for Word Scribe.
Users can configure a rule to select the template that has tagged localized clauses while authoring and executing an agreement.
To configure the Template Selection rule to select the template with tagged localized clauses:
Users need to configure a Clause Assembly rule on a primary clause to assemble the localized secondary clauses in the template while authoring and executing an agreement.
To configure a rule:
Users can create localized agreement instances from contract type which has enabled the clause localization on templates.
To create an agreement instance:
To edit the agreement and change the agreement language:
The agreement is now created using the template with available secondary French clauses for the tagged primary clauses.
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.
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.
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.
For example, the SavedSearchwithculturecode_Annexure1 is created for associated documents Automation Annexure Assembly.
User can create a Template with associations tagged as a table or as a saved search.
To create a template with associations:
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.
Users can configure a rule to select the template during agreement creation that has tagged associations.
To configure a rule:
Users can add the associations in the agreement as a table. The association table headers will be displayed in localized language if the respective localized values have been uploaded in the database through technical configuration or the Translation Tool in Admin Task.
The language of the association table headers is based on the following conditions:
To create the agreement:
As the Template with Associations has the associations tagged with French language (with culture code), the association’s table headers are displayed in French language.
Now, as the MDL Agreement Basic Template has the associations tagged without language (without culture code), the association table headers are displayed in Spanish, language selected in Agreement Language attribute.
Related Topic: Agreement Management | Rule
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in one of the groups: Users, User.
You can view and copy the source of this page:
Return to Localizing ICI.