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.
Contents
- 1 Localizing ICI
- 1.1 Assumptions/Restrictions
- 1.2 Important Points
- 1.3 Localization support across ICI
- 1.4 Rules implementation for localized masterdata attributes
- 1.4.1 Localizing Masterdata Attributes
- 1.4.2 Creating Masterdata instances
- 1.4.3 Referencing localized masterdata attribute in lookup attribute on Agreement Contract Type
- 1.4.4 Configuring Rule referencing localized masterdata attributes
- 1.4.5 Rule implementation for localized masterdata attributes for an Agreement
- 1.5 Localization of content in the agreement
Localizing ICI[edit]
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.
Assumptions/Restrictions[edit]
Localization currently supports these languages out of the box:
- Brazilian pt-BR
- Chinese (Simplified/Mandarin) zh-CHS
- Chinese (Traditional) zh-CHT
- Croatian
- Czech cs-CS
- Danish
- Dutch nl-NL
- English en-US
- Finnish
- French fr-FR
- German de-DE
- Hungarian
- Italian it-IT
- Japanese ja-JP
- Korean
- Norwegian
- Polish pl-PL
- Portuguese pt-PT
- Russian
- Spanish es-ES
- Spanish (Lat Am)
- Slovak (Slovakia)
- Slovenian
- Swedish
- Turkish tr-TR
Important Points[edit]
- Customers have the ability to add support for additional languages. Translations for a new language provided by the customer, will be uploaded from the backend.
- 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[edit]
Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers.
ICI supports localization by translating values in local languages using its “Translations Editor” tool. Users can see localized values as per their preferred language settings across ICI for:
- Alias Master
- Status and Business Status
- Type of paper
- Signature Type and Signature Sequence
- Choice and Multi-choice attributes
- Contract Type Description
- Default text in the search field
- Notification Category and Events
- Reason Codes
- Association entities assembled as a file, table or saved search as a table in a single as well as bilingual template.
The localization covers data types such as Masterdata Lookup (String Attributes), Choice/Multi-choice, Date and Time format, Percentage, Number, Boolean and Currency attributes format in Icertis Experience for Word. Additional localization support is now provided for attribute groups and extension attributes on ICI Web.
When the localization is not defined, the attribute values for association entities will be displayed in a language depending on specific business criteria.
For example, Administrators can enter corresponding German values for Draft status as Entwurf through “Translations Editor” tool.
The draft status will then be displayed in German for a user with language preferences set to German.
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.
The localization of UI elements is supported for all entities such as agreements, associated documents, contract requests and masterdata and in History, Notes, Versions and Search across ICI.
Rules implementation for localized masterdata attributes[edit]
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[edit]
Users can localize masterdata attribute and further refer its values across ICI.
To localize masterdata attribute.
1. Click "Configure" > "Contract Types". A page displaying Contract Types opens.
2. Click the "Create" button. The "Create Contract Type" page opens.
3. Click the "Masterdata" menu option.
4, On the "Create Contract Type" page, under the "Details", tab enter appropriate values for "Contract Type Name", "Description", and
Category"
5. Click Next to go to the "Attributes" tab.
6. Select the attribute you want to localize. For example, "A2 Currency".
7. Toggle On the "Is_Localised" field.
Note: Attributes of masterdata with only string data types have Is_Localised property.
8. Enter the details in the remaining "Display Preference" and "Team"tabs.
9. On the Verify tab, click "Create". The masterdata contract type is created.
You can edit existing masterdata contract type to configure the attribute as localized.
Note: Administrators need to upload translations for the localized attribute values in ICI through database upload or the Translator Tool from Admin Task.
Creating Masterdata instances[edit]
1. Click "Configure" > "Masterdata".
2. Click the "Create" button.
3. On the "Masterdata Details" tab, enter the details for "Category" and "Masterdata" fields.
4. Click "Next". The "Attributes" tab opens.
5. Enter the details in the required details, and then click "Create". The masterdata instance is created.
Referencing localized masterdata attribute in lookup attribute on Agreement Contract Type[edit]
To reference localized masterdata attribute in lookup attribute:
1. Click "Configure" > "Contract Types" > "Create" > "Agreement" on the Home page. The Create Contract Type page opens.
2. Enter name in Contract Type Name. For example, Saas Agreement.
3. Enter appropriate information on Details tab.
4. Click Next. The Attributes tab opens.
5. Select the attribute you want to add lookup for.
6. Toggle On for the Is_Lookup field.
7. Select masterdata contract type in Lookup section.
8. Select the attribute, where the look up value will be picked up from.
9. Click Save. The Attribute updated successfully message is displayed.
10. Enter the details in the remaining Association, Display Preference and Team tabs.
11. On the 'Verify tab, 'click Create. The agreement contract type is created.
You can edit existing agreement contract type and configure a lookup type attribute to reference localized masterdata attribute.
Configuring Rule referencing localized masterdata attributes[edit]
You can configure any type of rule for lookup attribute that references localized masterdata attribute.
Note: Rules should be configured in English language only.
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:
1. Click "Configure" > "Rules" > "Create" on the Home page. The Create Rules page opens.
2. Select the contract type for which you want to create a rule on the Setup tab. For example. Supplier Agreement.
3. Enter a name in the Rule Name field.
4. Select the Rule Type. For example, Approval Rule
5. Select Team Role. For example, Approver.
6. Click "Next". The Build tab opens.
7. Click "Add Rule". The Add Rule section opens.
8. Enter Condition. For example, Supplier City Has a Value.
9. Select Actions. For example, Require Approval From Any.
10. Add users from Search User window. For example, First Approver.
11. Select Minimun Approvers and Step Number.
12. Select No in Stop Processing More Rules field. The further evaluation of rules within a ruleset continues.
13. Click "View Summary" button. The rule Summary page opens.
14. Click "Save & Close" button. The Rule created successfully message appears. The rule is displayed in the list of rules of the selected contract type.
Refer to Rules for details on configuring other types of rules.
Rule implementation for localized masterdata attributes for an Agreement[edit]
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.
1. Click "Agreements" tile on the Home page, and then click the "Create" button. The "Create Agreement"page opens.
2. Select "Contract Type Name". For example, Supplier Agreement.
3. Select the "Type of Paper" as "Own" or "Third Party", as required.
3. Click "Next". The "Attributes"page opens.
4. Enter remaining details on "Attributes" "Templates" pages.
5. On the "Verify" tab, click "Create and Publish". The agreement is created.
Note: Localization of rule implementation for lookup type attribute is supported for creation of agreement/contract request/associations/masterdata, Icertis Experience for Word and all rule types.
Localization of content in the agreement[edit]
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.
Creation of Agreement Language Masterdata instance[edit]
1. Click "Configure" > "Masterdata" > on the Home page.
2. Click the "Create" button. The Create Masterdata page opens.
3. Select the desired value from the "Masterdata" dropdown list on the "Masterdata Details"tab.
4. Click "Next". The "Attributes" tab opens.
5. Enter the values for mandatory fields, "Country", "Country Code",
6. Enter remaining details and click "Create". The masterdata instance is created.
Addition of Agreement Language attribute to the Contract type[edit]
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:
1. Click "Configure" > "Contract Types" > "Create". The Select Contract Type page opens.
2. Click "Agreement" menu option. The Create Contract Type page opens.
3. Enter a name in "Contract Type Name". For example, ClauseLocalizationCT.
4. Enter the remaining details on the "Details" tab.
5.Click "Next". The Attributes tab opens.
6. Select the attribute Agreement Language.
7. Toggle On the Is_Lookup field.
8. Select Agreement Language Master in Select Contract Type field in Lookup section.
9. Select Description in the Select Attribute field.
10. Click "Save".
11. Enter the details in the "Association", "Display Preference" and "Team" tabs.
12. On the "Verify" tab, click "Create and Publish". The agreement contract type is created with agreement language attribute.
You can edit existing contract type to add agreement language attribute and enable the clauses localization into template for that contract type.
Localization support for Clauses into Templates[edit]
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.
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 significantly reduces the efforts of creating and managing multiple templates to support different languages.
Create localized clauses[edit]
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:
1, Click "Clause" tile on Home page.
2. Click "Create" button on the Clauses page. The Create Clause page opens.
3. Select Contract Type for which you want to localize the clauses. For example, MandatoryClauseCT.
4. Enter a name in Name field. For example, Primary Clause 1_SD.
5. Select a language in the Clause Language field. For example, English (United States).
6. Toggle Primary Clause field to Yes.
7. Enter Clause Text in English language.
8. Enter remaining details on the Details and Team tab.
9. On the "Verify" tab, click Create. The Primary Clause is created.
To create secondary clause:
1, Click "Clause" tile on Home page.
2. Click "Create" button on the Clauses page. The Create Clause page opens.
3. Select Contract Type for which you want to localize the clauses. For example, MandatoryClauseCT.
4. Enter a name in Name field. For example, Secondary Italian Clause.
5. Select language in Clause Language field. For example, Italian.
6. Toggle Primary Clause field to No.
7. Select the primary clause in Linked Primary Clause. For example, Confidential Information.
7. Enter Clause Text in Italian language.
8. Enter remaining details on the Details and Team tab.
9. On the "Verify" tab, click Create. The Secondary Clause is created.
Create the Template[edit]
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.
Note: Clauses should always be tagged as rule based clauses.
To create a template through Icertis Experience for Word:
1. Click "ICI" tab on "Icertis Experience for Word" and log in to the ICI UI instance.
2. Click "Create" in "Template" ribbon. The Create Template window opens.
3. Select the "Contract Type" for which you have enabled the localization for clauses into template. For example, ClauseLocalizationCT.
4. Enter the name in "Name" field. For example, Template with multiple Primary Clauses.
5. Select "English" in "Template Language" field.
6. Click the checkbox next to "Primary Template".
- Select Library Clauses. The list of all clauses for the contract type selected opens.
- Select a clause and right click. For example, Primary Clause 1_SD.
- Click Add > Rule Based Clause. The clause is added to the template.
- Click Save and approve the template.
You can create clauses and the template with tagged localized clauses also through Icertis Experience for Word.
Configure Template Rules[edit]
Users can configure a rule to select the template that has tagged localized clauses while authoring and executing an agreement.
Configure the Template Selection rule[edit]
To configure the Template Selection rule to select the template with tagged localized clauses:
1. Click "Configure" > "Rules" > on the Home page.
2. Click "Create" button on the Rules page. The Create Rules page opens.
3. Select the "Contract Type" for which you want to create a rule on the "Setup" tab. For example, MadatoryClauseCT.
4. Enter a name in the "Rule Name" field. For example, Localized Clauses Template Assembly.
5. Select "Template Selection" in the "Rule Type" drop-down list.
6. Click "Next". The "Build" tab opens.
7. Click "Add Rule"on the "Build"tab. The "Add Rule"section opens.
8. Enter "Conditions".
9. Select option "Select Template" in the "Actions"section.
10. Select the required template from the drop-down list. For example, "Mandatory Alternate Clause Template".
11. Select the "Stop Processing More Rules" checkbox. The further evaluation of rules within a ruleset continues.
12. Click "Evaluate". The page to evaluate the rule by entering attributes values of the selected contract type opens.
13. Click "Save" The "Rule successfully saved" message appears. The rule is displayed in the list of Rulesof the selected contract type.
Configure a Clause Assembly rule[edit]
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:
1. Click "Configure" > "Rules" > on the Home page.
2. Click "Create" button on the Rules page. The Create Rules page opens.
3. Select the Contract Type for which you want to create a rule on the Setup tab. For example, MadatoryClauseCT.
4. Enter a name in the Rule Name field. For example, Localized Clause Assembly.
5. Select "Clause Assembly" in the "Rule Type" drop-down list.
6. Click "Next". The "Build" tab opens.
7. Click "Add Rule"on the"Build" tab. The "Add Rule" section opens.
8. Enter "Conditions".
9. Select option "Select Clause"in the "Actions"section.
10. Click the + icon next to the "Clause" drop-down list. The "Select Clause" window opens.
11. Select clauses from "Select Clause"window, and then click the "Select" button. For example, Trade Compliance.
12. Select the "Stop Processing More Rules" checkbox. The further evaluation of rules within a ruleset continues.
13. Click "Evaluate". The page to evaluate the rule by entering attributes values of the selected contract type opens.
14. Click "Save" The "Rule successfully saved" message appears. The rule is displayed in the list of Rulesof the selected contract type.
Create an agreement with localized clauses[edit]
Users can create localized agreement instances from contract type which has enabled the clause localization on templates.
To create an agreement instance:
1. Click "Agreements" tile on the Home page.
2. Click "Create" button on the Agreements page. The Create Agreements page opens.
3. Select contract type that has clause localization enabled in "Contract Type Name".
4. Click "Next". The Attributespage opens.
5. Select the language in "Agreement Language" field.
6. Enter remaining details and click "Next". The Template Selectionpage opens.
7. Select the "Template"and click "Next".
8. On the "Verify" tab, 'click "'Create and Publish" button. The agreement is created using the template with available secondary Italian clauses for the tagged primary clause.
To edit the agreement and change the agreement language:
Note: When the agreement is updated, no deviation will be triggered as the agreement is getting assembled with localized clauses for the selected language.
1. Click "Edit"on Agreement Details page. The Edit Agreementpage opens.
2. Select the language in "Agreement Language" field. For example, French.
Note: The agreement language attribute is editable in the agreement only in draft state, the attribute is read-only in other states.
3. Click "Next". The Template Selectionpage opens.
4. Select the required "Template"and click "Next". For example, AssoTwoColumn_TemplateWithClauses.
5. On the Verify tab, and click "Update". The confirmation window with the edited field’s details opens.
Note: The confirmation window is enabled through technical configuration.
6. Click "Yes". The agreement is updated.
The agreement is now created using the template with available secondary French clauses for the tagged primary clauses.
Note: The agreement is assembled with the primary clause if the localized secondary clause for the selected agreement language is not available.
Localization of Associated document content in the agreement[edit]
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.
Creating a Saved search on associations [edit]
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.
Creating the Template with Associations[edit]
User can create a Template with associations tagged as a table or as a saved search.
Note: The template with tagged associations can only be created with Icertis Experience for Word.
To create a template with associations:
1. Click Insert > Add-ins > My Add-ins > See All > Shared Folder in MS Word. The list of ICI shared Add-ins opens.
2. Select the instance. The Icertis Experience for Word opens.
3. Click Create Template. The Details tab opens.
5. Select Contract Type. For example, MDL Agreement.
6. Enter a Name. For example, Template with Associations.
7. Select the primary language in Select Language. For example, French.
8. Select Secondary Language. For example, German.
9. Click Library tab.
10. Click Associations icon. The list of available associations open.
11. Click checkbox for Display Locale for Associations. The selected languages are displayed in Select Localized Language field.
12. Select a language in Select Localized Language field. For example, French.
13. Select the association you want to tag in the template. For example, Automation Annexure Assembly.
14. Select one of the options:
- Select Add as table. The associations are tagged in a template as a table in French language.
- Select Add with Saved Search. The Select Saved Search and Tag window opens.
15. Select the saved search in drop-down. For example, SavedSearchwithculturecode_Annexure1.
16. Click Add as table or Add as table with page break.
17. Enter remaining details for creating a template.
18. Click Save. The Template has been saved successfully message is displayed. The template is created with tagged associations.
19. Click Send For Approval. The template is send for approval.
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.
Configure the Template Selection Rule[edit]
Users can configure a rule to select the template during agreement creation that has tagged associations.
To configure a rule:
1. Click "Configure" > "Rules" > on the Home page.
2. Click "Create" button on the Rules page. The Create Rules page opens.
3. Select the Contract Type for which you want to create a rule on the Setup tab.
4. 'E'nter a name in the "Rule Name" field. For example, Test Agreement.
5. Select "Template Selections" in the Rule Type field.
6. Click "Next". The "Build" tab opens.
7. Click "Add Rule"on the "Build"tab. The "Add Rule"section opens.
8. Enter "Condition". For example, Type Of Paper Contains Own.
9. Select option "Select Template" in the Actions section.
10. Click the + icon next to the "Select Value" drop-down list. The "Select Template" window opens.
11. Select clauses from "Select Template"window and then click the "Select" button.
12. Select the "Stop Processing More Rules" checkbox. The further evaluation of rules within a ruleset continues.
13. Click "Evaluate". The page to evaluate the rule by entering attributes values of the selected contract type opens.
14. Click "Save" The "Rule successfully saved" message appears. The rule is displayed in the list of Rulesof the selected contract type.
Creating an agreement with associations added as table[edit]
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:
- If the template has the associations tagged with localized language (with culture code), the table headers are displayed in that selected language.
- If the template has the associations tagged without language (without culture code), the table headers are displayed in the language selected in the Agreement Language attribute during agreement creation. If there is no language selected, the table headers are displayed in default language.
To create the agreement:
1. Click "Agreements" tile on the Home page. The Agreementspage opens.
2. Click on the "Create" button.
3. Select "Contract Type Name". For example, MandatoryClauseCT.
4. Click "Next". The Attributes page opens.
5. Select the language in the "Languages" field.
5. Enter the remaining details.
6. Click "Next". The Select Template page opens. The templates will be available as per the configured rule.
7. Select the required "Template".
8. Click "Next".
9. On the "Verify" tab, click appropriate option to Create, or Create and Publish or Create and Send for Approval.
As the Template with Associations has the associations tagged with the selected language (with culture code), the association’s table headers are displayed in that particular language.
10. Click "Edit"on the agreement Details page.
11. Select the desired template on the Select Template page.
12. Click "Update". The agreement is updated.
Related Topic: Agreement Management | Rule
