Localizing ICI[edit]


= 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):&nbsp;User input in any language will be accepted, stored and displayed as entered/stored.

== Assumptions/Restrictions ==

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 ==

*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. 
*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 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 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.

#'''Click '''''Configuration'' > ''Create Contract Type'' > ''Masterdata'' on the&nbsp;''Home ''page. The ''Select Contract Type'' page opens. 
#'''Click '''''Next''. The ''Create Contract Type'' page opens. 
#'''Enter '''name in ''Contract Type Name''. For example, ''Chemical Product Master''. 
#'''Enter '''remaining details on ''Details ''tab. 
#'''Select '''the attribute you want to localize. For example, ''Chemical Name''. 
#'''Toggle '''''On ''the ''Is_Localised'' field. 
#'''Click '''''Save''. The ''Attribute updated successfully'' message is dispalyed. 
<div class="image-green-border">[[File:7.12 Localized Rule implementation 1.png|720px|7.12 Localized Rule implementation 1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">Note: Attributes of masterdata with only string data types have ''Is_Localised'' property.</div> <ol start="7">
<li>'''Enter '''the details in the remaining ''Display Preference'' and ''Team ''tabs.</li>
<li>'''Verify '''and '''click '''''Create''. The masterdata contract type is created.&nbsp;</li>
</ol>

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 ICI through database upload or the ''Translator Tool ''from ''Admin Task''.</div> 
&nbsp;

=== Creating Masterdata instances ===

#'''Click '''''Configuration'' > ''Masterdata ''> ''Create Masterdata ''on the&nbsp;''Home ''page. The ''Create Masterdata'' page opens. 
#'''Select '''''Masterdata''. For example, ''Chemcial Product Masterdata''. 
#'''Click '''''Next''. The ''Attributes ''page opens. 
#'''Enter '''''Chemical Name''. Fo example, ''Boron Nitride Powder''. 
#'''Enter '''''Chemical Usage Details''. For example, ''Disinfectant''. 
#'''Click '''''Save''. The masterdata instance is created. 
<div class="image-green-border">[[File:7.12 Localized Rule implementation 2.png|720px|7.12 Localized Rule implementation 2.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> 
=== Referencing localized masterdata attribute in lookup attribute on Agreement Contract Type ===

To reference localized masterdata attribute in lookup attribute:

#'''Click '''''Configuration ''> ''Create'' ''Contract Type ''> ''Agreement ''on the&nbsp;''Home ''page.&nbsp;The ''Select Contract Type'' page opens. 
#'''Click '''''Next''. The ''Create Contract Type'' page opens. 
#'''Enter '''name in ''Contract Type Name.'' For example, ''Saas Agreement''. 
#'''Enter '''remaining details on ''Details ''tab. 
#'''Click '''''Next''. The ''Attributes ''tab opens. 
#'''Select '''the attribute you want to add lookup for. For example, ''Chemical Name''. 
#'''Toggle '''''On ''for the ''Is_Lookup ''field. 
#'''Select''' masterdata contract type in Lookup section. For example, ''Chemical Product Masterdata''. 
#'''Select '''the attribute, where the look up value will be picked up from. For example,''Chemical Name''. 
#'''Click '''''Save''. The ''Attribute updated successfully ''message is displayed. 
#'''Enter '''the details in the remaining ''Association'', ''Display Preference ''and ''Team ''tabs. 
#'''Verify '''and '''click '''''Create''. The agreement contract type is created. 
<div class="image-green-border">[[File:7.12 Localized Rule implementation 3.png|720px|7.12 Localized Rule implementation 3.png]]</div> 
You can edit existing agreement contract type and configure a lookup type attribute to reference localized masterdata attribute.

&nbsp;

=== Configuring Rule referencing localized masterdata attributes ===

You can configure any type of rule for lookup attribute that references localized masterdata attribute.
<div class="note-box">Note: Rules should be configured in English language only.&nbsp;</div> 
For example, configure an event rule for ''Saas Agreement''&nbsp;contract tyep lookup attribute which references localized masterdata attribute ''Chemical Name.''&nbsp;<br/> To configure an event rule with localized masterdata attribute:

#'''Click '''''Configuration ''> ''Rule ''> ''Create Rule ''on the&nbsp;''Home ''page. The ''Create Rules'' page opens. 
#'''Select '''the contract type for which you want to create a rule on the ''Setup ''tab. For example, ''Saas Agreement''. 
#'''Enter '''a name in the ''Rule Name'' field. For example, ''Approval - RG''. 
#'''Select '''the ''Rule Type''. For example, ''Approval Rule''. 
#'''Select '''''Team Role''. For example, ''Approver''. 
<div class="image-green-border">[[File:7.12 Localized Rule implementation 4.png|720px|7.12 Localized Rule implementation 4.png]]</div> <div class="image-green-border">&nbsp;</div> <ol start="7">
<li>'''Click '''''Next''. The ''Build ''tab opens.</li>
<li>'''Click '''''Add Rule'' under ''Builder ''tab. The ''Add Rule'' section opens.</li>
<li>'''Enter '''''Condition''. For example, ''Chemical Name Has a Value''.</li>
<li>'''Select '''''Actions''. For example, ''Require Approval From Any''.</li>
<li>'''Add '''users from ''Search User'' window. For example, ''John Doe''.</li>
<li>'''Select '''''Minimun Approvers ''and ''Step Number''.</li>
<li>'''Select '''''No ''in ''Stop Processing More Rules'' field. The further evaluation of rules within a ruleset continues.</li>
</ol>
<div class="image-green-border">[[File:7.12 Localized Rule implementation 5.1.png|720px|7.12 Localized Rule implementation 5.1.png]]</div> <ol start="14">
<li>'''Click '''''Validate''. The page to validate the rule by entering attributes values of the selected contract type opens.</li>
<li>'''Click '''''Next''. The rule ''Summary ''tab opens.</li>
<li>'''Click '''''Create''. The ''Rule created successfully ''message appears. The rule is displayed in the list of rules of the selected contract type.</li>
</ol>

Refer to ''Rules ''for details on configuring other types of rules.

&nbsp;

=== Rule implementation for localized masterdata attributes for an Agreement ===

Users can create the agreement instance for the contract type which has a lookup attribute referencing localized masterdata attribute. The&nbsp;rule configured in English for such lookup will get evaluated upon changing its lookup values&nbsp;in languages other than English.&nbsp;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&nbsp;''contract type&nbsp;:

#'''Click '''''Agreement Management ''> ''Create Agreement'' on the ''Home ''page. The ''Create Agreement ''page opens. 
#'''Select '''''Contract Type Name''. For example, ''Saas Agreement''. &nbsp; 
#'''Click '''''Next''. The ''Attributes ''page opens. 
#'''Select '''''Chemical name''. for example,''Boron Nitride Powder''. 
<div class="image-green-border">[[File:7.12 Localized Rule implementation 6.1.png|720px|7.12 Localized Rule implementation 6.1.png]]</div> <ol start="5">
<li>'''Enter '''remaining details on ''Attributes ''and ''Select Template ''tab.</li>
<li>'''Verify''' and '''click '''''Create and Publish''. The agreement is created.</li>
</ol>

''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.
<div class="image-green-border">[[File:7.12 Localized Rule implementation 7.1.png|720px|7.12 Localized Rule implementation 7.1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">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.</div> 
&nbsp;

== Localization of&nbsp;content in the agreement ==

The masterdata ''Agreement Language Master'' defines the attributes to store languages that will be used to create the localized agreement.&nbsp;Users can create instances of the ''Agreement Language'' ''Master ''contract type to add new languages.&nbsp;

=== Creation of Agreement Language Masterdata instance ===

#'''Click '''''Configuration ''> ''Masterdata ''> ''Create Masterdata ''on the ''Home ''page. The ''Create Masterdata ''page opens. 
#'''Select '''''Agreement Language Master ''in ''Masterdata ''field on ''Masterdata Details ''tab. 
<div class="image-green-border">[[File:7.12 Localization support 1.1.png|720px|7.12 Localization support 1.1.png]]</div> <ol start="3">
<li>'''Click '''''Next''. The ''Attributes ''tab opens.</li>
<li>'''Enter '''language description in ''Description ''field. For example, ''Français‎ ''(''French'').</li>
<li>'''Enter '''remaining details and '''click '''''Save''. The masterdata instance is created.</li>
</ol>
<div class="image-green-border">[[File:7.12 Localization support 2.png|720px|7.12 Localization support 2.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> 
=== Addition of Agreement Language attribute to the Contract type ===

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:

#'''Click '''''Configuration ''> ''Create Contract Type ''> ''Agreement ''on the ''Home ''page. The ''Select Contract Type ''page opens. 
#'''Click '''''Next''. The ''Create Contract Type ''page opens. 
#'''Enter '''a name in ''Contract Type Name.'' For example,&nbsp;''ClauseLocalizationCT''. 
#'''Enter '''the remaining details on the&nbsp;''Details ''tab. 
#'''Click '''''Next''. The ''Attributes ''tab opens. 
#'''Select '''the attribute ''Agreement Language''. 
#'''Toggle '''''On ''the ''Is_Lookup ''field. 
#'''Select '''''Agreement Language Master ''in ''Select Contract Type ''field in ''Lookup ''section. 
#'''Select '''''Description ''in the ''Select Attribute ''field.&nbsp; 
#'''Click '''''Save''. The ''Attribute updated successfully ''message is displayed. 
#'''Enter '''the details in the remaining ''Association'', ''Display Preference ''and ''Team ''tabs. 
#'''Verify '''the details and '''click '''''Create and Publish''. The agreement contract type is created with agreement language attribute. 
<div class="image-green-border">[[File:7.12 Localization support 4.png|720px|7.12 Localization support 4.png]]</div> 
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 ===

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> ====

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.

<span style="font-size:larger;">'''To create a primary clause:'''</span>

#'''Click '''''Clause Management'' > ''Create Clause'' on the ''Home ''page. The ''Create Clause ''page opens. 
#'''Select '''''Contract Type ''for which you want to localize the clauses. For example, ''ClauseLocalizationCT''. 
#'''Enter''' a name in ''Name ''field. For example, ''Primary Clause 1_SD.'' 
#'''Select '''a language in the ''Clause Language ''field. For example, ''English''. 
#'''Toggle '''''Primary Clause ''field to ''Yes''. 
#'''Enter '''''Clause Text ''in ''English ''language. 
#'''Enter '''remaining details on the&nbsp;''Details ''and ''Team ''tab. 
#'''Verify '''and '''click '''''Create''. The ''Primary Clause ''is created. 
<div class="image-green-border">[[File:7.12 Localized Cluases 1.1.png|720px|7.12 Localized Cluases 1.1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="font-size:larger;">'''To create secondary clause:'''</span></div> 
#'''Click '''''Clause Management'' > ''Create Clause'' on the&nbsp;''Home ''page. The ''Create Clause ''page opens. 
#'''Select '''''Contract Type ''for which you want to localize the clauses. For example, ''ClauseLocalizationCT''. 
#'''Enter '''a name in ''Name ''field. For example, ''Secondary Italian Clause''. 
#'''Select''' language in ''Clause Language ''field. For example, ''Italian''. 
#'''Toggle '''''Primary Clause ''field to ''No''. 
#'''Select '''the primary clause in ''Linked Primary Clause''. For example, ''Primary'' ''Clause 1_SD''. 
#'''Enter '''''Clause Text ''in Italian language. 
#'''Enter '''remaining details on the&nbsp;''Details ''and ''Team ''tab. 
#'''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> ====

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.
<div class="note-box">Note: Clauses should always be tagged as rule based clauses.</div> 
To create a template through I''certis Experience for Word:''

#'''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''. 
#'''Enter '''the name in ''Name ''field. For example, ''Template with multiple Primary Clauses''. 
#'''Select '''''English ''in ''Template Language ''field. 
#'''Click '''the checkbox next to ''Primary Template''. 
<div class="image-green-border">[[File:7.12 Localized Cluases 3.png|720px|7.12 Localized Cluases 3.png]]</div> <ol start="7">
<li>'''Select''' ''Library Clauses''. The list of all clauses for the contract type selected opens.</li>
<li>'''Select '''a clause and right click. For example, ''Primary Clause 1_SD''.</li>
<li>'''Click '''''Add ''> ''Rule Based Clause''. The clause is added to the template.</li>
</ol>
<div class="image-green-border">[[File:7.12 Localized Cluases 4.2.png|720px|7.12 Localized Cluases 4.2.png]]</div> <ol start="10">
<li>'''Click''' ''Save ''and '''approve '''the template.</li>
</ol>

You can create clauses and the template with tagged localized clauses also through ''Icertis Experience for Word.''

&nbsp;

==== <span style="font-size:larger;">Configure Template Rules</span> ====

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 =====

To configure the ''Template Selection'' rule to select the template with tagged localized clauses:

#'''Click '''''Configuration ''> ''Rule ''> ''Create Rule ''on the ''Home ''page. The ''Create Rules ''page opens. 
#'''Select '''the ''Contract Type ''for which you want to create a rule on the ''Setup ''tab. For example, ''ClauseLocalizationCT''. 
#'''Enter''' a'''&nbsp;'''name in the ''Rule Name ''field. For example, ''Localized Clauses Template Assembly''. 
#'''Select '''''Template Selection ''in the ''Rule Type''. 
<div class="image-green-border">[[File:7.12 Localized Cluases 5.png|720px|7.12 Localized Cluases 5.png]]</div> <ol start="5">
<li>'''Click '''''Next''. The ''Build ''tab opens.</li>
<li>'''Click '''''Add Rule ''on the&nbsp;''Builder ''tab. The ''Add Rule ''section opens.</li>
<li>'''Enter '''''Conditions''. For example,&nbsp;''Name contains Localized Clauses Assembly''.</li>
<li>'''Select '''option ''Select Template'' in the&nbsp;''Actions ''section.</li>
<li>'''Select '''the template from the ''Select Templates ''window in&nbsp;the&nbsp;''Template ''field. For example, ''Template with multiple Primary Clauses''.</li>
<li>'''Select '''''No ''in ''Stop Processing More Rules'' field. The further evaluation of rules within a ruleset continues.</li>
</ol>
<div class="image-green-border">[[File:7.12 Localized Cluases 6.png|720px|7.12 Localized Cluases 6.png]]</div> <ol start="11">
<li>'''Click '''''Validate''. The page to validate the rule by entering attributes values of the selected contract type opens.</li>
<li>'''Click '''''Next''. The rule ''Summary ''tab opens.</li>
<li>'''Click '''''Create''. The ''Rule created successfully'' message appears. The rule is displayed in the list of ''Rules ''of the selected contract type.</li>
</ol>

&nbsp;

===== <span style="font-size:larger;">Configure a Clause Assembly rule</span> =====

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.<br/> To configure a rule:

#'''Click '''''Configuration ''> ''Rule ''> ''Create Rule ''on the ''Home ''page. The ''Create Rules ''page opens. 
#'''Select '''the ''Contract Type ''for which you want to create a rule on the ''Setup ''tab. For example, ''ClauseLocalizationCT''. 
#'''Enter '''a name in the ''Rule Name ''field. For example, ''Localized Clause Assembly Rule.'' 
#'''Select '''''Clause Assembly ''in the ''Rule Type''. 
<div class="image-green-border">[[File:7.12 Localized Cluases 7.png|720px|7.12 Localized Cluases 7.png]]</div> <ol start="5">
<li>'''Click '''''Next''. The ''Build ''tab opens.</li>
<li>'''Click '''''Add Rule ''on the&nbsp;''Builder ''tab. The ''Add Rule ''section opens.</li>
<li>'''Enter '''''Conditions''. For example, ''Name Contains Localized Clauses Assembly''.</li>
<li>'''Select '''option ''Select Clause ''in the&nbsp;''Actions ''section.&nbsp;</li>
<li>'''Select '''clauses from ''Select Clause ''window. For example, ''Primary Clause 1_SD''.</li>
<li>'''Select '''''No ''in ''Stop Processing More Rules ''field. The further evaluation of rules within a ruleset continues.<br/> &nbsp;</li>
</ol>
<div class="image-green-border">[[File:7.12 Localized Cluases 8.png|720px|7.12 Localized Cluases 8.png]]</div> <ol start="11">
<li>'''Click '''''Validate''. The page to validate the rule by entering attributes values of the selected contract type opens.</li>
<li>'''Click '''''Next''. The rule ''Summary ''tab opens.</li>
<li>'''Click '''''Create''. The ''Rule created successfully'' message appears. The rule is displayed in the list of ''Rules ''of the selected contract type.</li>
</ol>

&nbsp;

==== <span style="font-size:larger;">Create the agreement with localized clauses</span> ====

Users can create localized agreement instances from contract type which has enabled the clause localization on templates.

To create an agreement instance:

#'''Click '''''Agreement Management'' > ''Create Agreement ''on the&nbsp;''Home ''page. The ''Create Agreement ''page opens. 
#'''Select '''contract type that has clause localization enabled in ''Contract Type Name''. For example, ''ClauseLocalizationCT''. 
#'''Click '''''Next''. The ''Attributes ''page opens. 
#'''Select '''the language in ''Agreement Language ''field. For example, ''Italian''. 
#'''Enter '''remaining details and '''click '''''Next''. The ''Template Selection ''page opens. 
#'''Select '''the ''Template ''and '''click '''''Next''. For example,''Template with Multiple Primary Clauses.'' 
<div class="image-green-border">[[File:7.12 Localized Cluases 9.png|720px|7.12 Localized Cluases 9.png]]</div> <ol start="7">
<li>'''Verify '''the details&nbsp;and '''click '''''Create and Publish''. The agreement is created using the template with available secondary Italian clauses for the tagged primary clause.</li>
</ol>
<div class="image-green-border">[[File:7.12 Localized Cluases 12.1.png|720px|7.12 Localized Cluases 12.1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> 
<span style="font-size:larger;">'''To edit the agreement and change the agreement language:'''</span>
<div class="note-box">Note: When the agreement is updated, no deviation will be triggered as the agreement is getting assembled with localized clauses for the selected language.</div> <ol start="8">
<li>'''Click '''''Edit ''on agreement details page. The ''Edit Agreement ''page opens.</li>
<li>'''Select '''the language in ''Agreement Language ''field. For example, ''French''.</li>
</ol>
<div class="note-box">Note: &nbsp;The agreement language attribute is editable in the agreement only in draft state, the attribute is read-only in other states.</div> <ol start="11">
<li>'''Click '''''Next''. The ''Template Selection ''page opens.</li>
<li>'''Select '''the ''Template ''and '''click '''''Next''. For example, ''Template with Multiple Primary Clauses.''</li>
<li>'''Verify''' the details'''&nbsp;'''and '''click '''''Update''. The confirmation window with the edited field’s details opens.</li>
</ol>

[[File:7.12 Localized Cluases 11.png|720px|7.12 Localized Cluases 11.png]]
<div class="note-box">Note: The confirmation window is enabled through technical configuration.</div> <ol start="13">
<li>'''Click '''''Yes''. The agreement is updated.</li>
</ol>

The agreement is now created using the template with available secondary French clauses for the tagged primary clauses.
<div class="image-green-border">[[File:7.12 Localized Cluases 10.1.png|720px|7.12 Localized Cluases 10.1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">Note: The agreement is assembled with the primary clause if the localized secondary clause for the selected agreement language is not available.&nbsp;</div> 
&nbsp;

=== Localization of Associated document content in the agreement ===

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> ====

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> 
To create a template with associations:

#'''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. 
#'''Select '''''Contract Type''. For example, ''MDL Agreement''. 
#'''Enter '''a&nbsp;''Name''. For example, ''Template with Associations''. 
#'''Select''' the primary language in ''Select Language. ''For example, ''French''. 
#'''Select '''''Secondary Language''. For example, ''German''.<br/> &nbsp; 
<div class="image-green-border">[[File:7.12 Associations content localization 2.png|300px|7.12 Associations content localization 2.png]]</div> <ol start="8">
<li>'''Click '''''Library ''tab.&nbsp;</li>
<li>'''Click '''''Associations ''icon. The list of available associations open.</li>
<li>'''Click '''checkbox for ''Display Locale for Associations''. The selected languages are displayed in ''Select Localized Language ''field.</li>
<li>'''Select '''a language in ''Select Localized Language ''field. For example, ''French''.</li>
<li>'''Select '''the association you want to tag in the template. For example, ''Automation Annexure Assembly''.</li>
<li>'''Select '''one of the options:</li>
</ol>

*'''Select '''''Add as table''. The associations are tagged in a template as a table in French language. 
<div class="image-green-border">[[File:7.12 Associations content localization 3.png|500px|7.12 Associations content localization 3.png]]</div> 
*'''Select '''''Add with Saved Search''. The ''Select Saved Search'' ''and Tag ''window opens. 
<div class="image-green-border">[[File:7.12 Associations content localization 4.png|300px|7.12 Associations content localization 4.png]]</div> <ol start="14">
<li>'''Select '''the saved search in drop-down. For example, ''SavedSearchwithculturecode_Annexure1.''</li>
<li>'''Click '''''Add as table ''or ''Add as table with page break''.</li>
<li>'''Enter '''remaining details for creating a template.</li>
<li>'''Click '''''Save''. The ''Template has been saved successfully'' message is displayed. The template is created with tagged associations.</li>
</ol>
<div class="image-green-border">[[File:7.12 Associations content localization 5.png|720px|7.12 Associations content localization 5.png]]</div> <ol start="18">
<li>'''Click '''''Send For Approval''. The template is send for approval.</li>
</ol>

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> ====

Users can configure a rule to select the template during agreement creation that has tagged associations.

To configure a rule:

#'''Click '''''Configuration ''> ''Rule ''> ''Create Rule'' on the ''Home ''page. The ''Create Rules ''page opens. 
#'''Select '''the ''Contract Type'' for which you want to create a rule on the ''Setup ''tab. For example, ''MDL Agreement''. 
#'''Enter '''a name in the ''Rule Name ''field. For example, ''MDL Template selection.'' 
#'''Select '''''Template Selections ''in the ''Rule Type''. 
<div class="image-green-border">[[File:7.12 Associations content localization 7.png|720px|7.12 Associations content localization 7.png]]</div> <ol start="5">
<li>'''Click '''''Next''. The ''Build ''tab opens.</li>
<li>'''Click '''''Add Rule ''on the ''Builder ''tab. The ''Add Rule ''section opens.</li>
<li>'''Enter '''''Condition''. For example, ''Type Of Paper Contains Own.''</li>
<li>'''Select '''option ''Select Template ''in the ''Actions ''section.&nbsp;</li>
<li>'''Select '''the template from ''Select Template'' window. For example, ''Template with Associations'' (with culture code) and ''MDL Agreement with Template Selection'' (without culture code).</li>
<li>'''Select '''''No ''in ''Stop Processing More Rules ''field. The further evaluation of rules within a ruleset continues.</li>
</ol>
<div class="image-green-border">[[File:7.12 Associations content localization 8.png|720px|7.12 Associations content localization 8.png]]</div> <ol start="11">
<li>'''Click '''''Validate''. The page to validate the rule by entering attributes values of the selected contract type opens.</li>
<li>'''Click '''''Next''. The rule ''Summary ''tab opens.</li>
<li>'''Click '''''Create''. The ''Rule created successfully'' message appears. The rule is displayed in the list of ''Rules ''of the selected contract type.</li>
</ol>

&nbsp;

==== <span style="font-size:larger;">Creating an agreement with associations added as table</span> ====

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.''<br/> 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:

#'''Click '''''Agreement Management'' > ''Create Agreement ''on the&nbsp;''Home ''page. The ''Create Agreement ''page opens. 
#'''Select '''''Contract Type Name.'' For example, ''MDL Agreement.'' 
#'''Click '''''Next''. The ''Attributes ''page opens. 
#'''Select '''the language in the ''Agreement Language ''attribute. For example, ''Spanish''. 
<div class="image-green-border">[[File:7.12 Associations content localization 9.png|720px|7.12 Associations content localization 9.png]]</div> <ol start="5">
<li>'''Enter '''the remaining details.</li>
<li>'''Click '''''Next''. The ''Select Template'' page opens. The templates will be available as per the configured rule.</li>
<li>'''Select '''the ''Template''. For example, ''Template with Association.''</li>
</ol>
<div class="image-green-border">[[File:7.12 Associations content localization 10.png|720px|7.12 Associations content localization 10.png]]</div> <ol start="8">
<li>'''Click '''''Next''.</li>
<li>'''Verify '''the details and '''click '''''Create''. The agreement is created.</li>
</ol>
<div class="image-green-border">[[File:7.12 Associations content localization 11.png|720px|7.12 Associations content localization 11.png]]</div> 
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.
<ol start="10">
<li>'''Click '''''Edit ''on the agreement ''Details ''page.</li>
<li>'''Select '''the template ''MDL Agreement Basic Template ''on the&nbsp;''Select Template'' page.</li>
</ol>
<div class="image-green-border">[[File:7.12 Associations content localization 12.png|720px|7.12 Associations content localization 12.png]]</div> <ol start="12">
<li>'''Click '''''Update''. The agreement is updated.</li>
</ol>
<div class="image-green-border">[[File:7.12 Associations content localization 13.png|720px|7.12 Associations content localization 13.png]]</div> 
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.

&nbsp;

&nbsp;

Related Topic:&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;|&nbsp;[[Rule|Rule]]

&nbsp;