<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=123.252.235.74&amp;*</id>
		<title>ICIHelp8.2 - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=123.252.235.74&amp;*"/>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Special:Contributions/123.252.235.74"/>
		<updated>2026-05-13T18:30:33Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.25.2</generator>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Linkage_Type&amp;diff=16221</id>
		<title>Linkage Type</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Linkage_Type&amp;diff=16221"/>
				<updated>2021-01-29T14:56:41Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: Created page with &amp;quot; = Linkage Type =  The ''Linkage Type'' and its sub menu tiles are enabled through technical configuration for an instance.  == Defining a Linkage Type label ==  1. '''Click '...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Linkage Type =&lt;br /&gt;
&lt;br /&gt;
The ''Linkage Type'' and its sub menu tiles are enabled through technical configuration for an instance.&lt;br /&gt;
&lt;br /&gt;
== Defining a Linkage Type label ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Configuration'' &amp;gt; ''Linkage Type'' on the ''Home ''page. The options to view and create ''Linkage Types'' open.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 1.png|720px|7.15 586492 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click '''''Create Linkage Type''. The ''Create Linkage Type'' page opens.&amp;lt;br/&amp;gt; 3. '''Select t'''he ''Linkage Type ''from options ''Peer, Parent ''or ''Child''. For example, ''Peer''. &amp;lt;br/&amp;gt; 4. '''Enter '''the ''Linkage Name''. For example, ''Related To''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 2.png|720px|7.15 586492 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 5. '''Toggle '''''Is Default ''to ''Yes ''or ''No ''as per the requirement. If set to ''Yes'', the linkage type will be set as default while creating peer associations for agreements.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
The ''Warning ''window opens with the message- ''Marking default for this linkage name will mark the existing linkage name as un-default.''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:7.15 586492 3.png|720px|7.15 586492 3.png]]''&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;br/&amp;gt; 6. '''Click''' ''Yes ''to continue. The ''Verify'' page opens.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 4.png|720px|7.15 586492 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 7. '''Verify '''the details and click ''Save''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 5.png|720px|7.15 586492 5.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;br/&amp;gt; The ''Linkage Type'' is created and displayed on the ''Linkage Type'' index page.&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;br/&amp;gt; Working with Linkage Types ==&lt;br /&gt;
&lt;br /&gt;
Users can view, edit, activate and deactivate the existing Linkage Types.&amp;lt;br/&amp;gt; 1. '''Click '''''Configuration ''&amp;gt; ''Linkage Type'' on the ''Home ''page. The options to view and create ''Linkage types'' open.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 6.png|720px|7.15 586492 6.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click '''''Linkage Type''. The ''Linkage Type ''index page opens.&amp;lt;br/&amp;gt; 3. '''Click''' ''View Record ''icon corresponding to the ''Linkage Type ''you want to open. The ''Linkage Type Details'' page opens.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 7.png|720px|7.15 586492 7.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;lt;br/&amp;gt; Users can take following actions on the ''Linkage Type:''&amp;lt;/div&amp;gt; &lt;br /&gt;
*''Edit'' &lt;br /&gt;
*''Activate'' &lt;br /&gt;
*''Deactivate'' &lt;br /&gt;
&lt;br /&gt;
To edit a Linkage Type:&amp;lt;br/&amp;gt; 4. '''Click '''''Edit ''on the ''Details ''page. The ''Edit Linkage Type'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 8.png|720px|7.15 586492 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 5. '''Modify''' the details as required and click ''Next''. The ''Verify ''page opens.&amp;lt;br/&amp;gt; 6. '''Verify''' the details and click ''Update''. The ''Linkage Type'' is updated.&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; To deactivate a Linkage Type:&amp;lt;br/&amp;gt; 7. '''Click '''''Deactivate ''on the ''Details ''page. The ''Warning ''window opens with the message- ''Do you want deactivate linkage name?''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:7.15 586492 9.png|720px|7.15 586492 9.png]]''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 8. '''Click '''''Yes''. The ''Linkage Type'' will be deactivated and will not be available for user selection in ''Linkage Type'' drop-down while creating associations.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 10.png|720px|7.15 586492 10.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;br/&amp;gt; To activate a Linkage Type:&amp;lt;br/&amp;gt; 9. '''Click '''''Activate'' on the ''Details ''page. The ''Warning'' window opens with the message- ''Do you want activate linkage name?''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:7.15 586492 11.png|720px|7.15 586492 11.png]]''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 10. '''Click''' ''Yes''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 12.png|720px|7.15 586492 12.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; The''Linkage Type'' will be activated and will be available for user selection in ''Linkage Type'' drop-down while creating ''Peer'' associations.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.15 586492 13.png|720px|7.15 586492 13.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Notes:&amp;amp;nbsp;&amp;lt;br/&amp;gt; Only linkage name is editable in case of parent and child linkage types.&amp;lt;br/&amp;gt; When users deactivate a parent-child linkage type, its corresponding parent/child linkage type will also be deactivated internally.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15675</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15675"/>
				<updated>2021-01-06T06:55:05Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Icertis Search for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Icertis&amp;amp;nbsp;Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Icertis Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Icertis&amp;amp;nbsp;search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Icertis&amp;amp;nbsp;Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Icertis&amp;amp;nbsp;'''''''''S'''earch Health''': This displays the Status (yellow/green/red), the Icertis&amp;amp;nbsp;Search version and the Uptime, and so on.'' &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Icertis Search Health'''&amp;lt;br/&amp;gt; The details for the Icertis&amp;amp;nbsp;Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the Icertis&amp;amp;nbsp;search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target&amp;amp;nbsp;environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;tool already supported&amp;amp;nbsp;contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The Icertis&amp;amp;nbsp;search sync is also supported by the tool.&lt;br /&gt;
&lt;br /&gt;
With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities&amp;amp;nbsp;:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;''Accessing P2P Tool''&amp;lt;/span&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home&amp;amp;nbsp;'''&amp;gt;&amp;amp;nbsp;'''Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;''Creating a P2P Request''&amp;lt;/span&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
Toggle&amp;amp;nbsp;''Resume P2P From Last Successful Step'' to Yes/No, as required.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''As stated in the disclaimer, while promoting configuration, target environment will be down during contract type publish. This tool must be used responsibly under project team’s approvals to avoid inconsistency and downtime.&amp;lt;/div&amp;gt; &lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&amp;amp;nbsp;The entities supported such as ''Org Group, Role Action Mapping, SLA Matrix,'' etc. will be available for selection.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users on&amp;amp;nbsp;the&amp;amp;nbsp;''Select Users''&amp;amp;nbsp;page. For example, ''01ux user, 02ux 2, 05ux 2''.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''''Selected Users'' to view the list of users that have been selected.&lt;br /&gt;
&lt;br /&gt;
33. '''Click&amp;amp;nbsp;'''''Filter Users ''to view the list of users by an attribute or click ''Add Another Attribute ''to filter users by additional attributes. For example, ''Email ID, Phone Number''.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''''Remove''&amp;amp;nbsp;to remove an added attribute.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, transactional master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15674</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15674"/>
				<updated>2021-01-06T06:54:36Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Icertis Search for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Icertis&amp;amp;nbsp;Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Icertis Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Icertis&amp;amp;nbsp;search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Icertis&amp;amp;nbsp;Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Icertis&amp;amp;nbsp;'''''''''S'''earch Health''': This displays the Status (yellow/green/red), the Icertis&amp;amp;nbsp;Search version and the Uptime, and so on.'' &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Icertis Search Health'''&amp;lt;br/&amp;gt; The details for the Icertis&amp;amp;nbsp;Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the Icertis&amp;amp;nbsp;search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target&amp;amp;nbsp;environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;tool already supported&amp;amp;nbsp;contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The Icertis&amp;amp;nbsp;search sync is also supported by the tool.&lt;br /&gt;
&lt;br /&gt;
With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities&amp;amp;nbsp;:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;''Accessing P2P Tool''&amp;lt;/span&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home&amp;amp;nbsp;'''&amp;gt;&amp;amp;nbsp;'''Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== &amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Creating a P2P Request'''''&amp;lt;/span&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
Toggle&amp;amp;nbsp;''Resume P2P From Last Successful Step'' to Yes/No, as required.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''As stated in the disclaimer, while promoting configuration, target environment will be down during contract type publish. This tool must be used responsibly under project team’s approvals to avoid inconsistency and downtime.&amp;lt;/div&amp;gt; &lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&amp;amp;nbsp;The entities supported such as ''Org Group, Role Action Mapping, SLA Matrix,'' etc. will be available for selection.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users on&amp;amp;nbsp;the&amp;amp;nbsp;''Select Users''&amp;amp;nbsp;page. For example, ''01ux user, 02ux 2, 05ux 2''.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''''Selected Users'' to view the list of users that have been selected.&lt;br /&gt;
&lt;br /&gt;
33. '''Click&amp;amp;nbsp;'''''Filter Users ''to view the list of users by an attribute or click ''Add Another Attribute ''to filter users by additional attributes. For example, ''Email ID, Phone Number''.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''''Remove''&amp;amp;nbsp;to remove an added attribute.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, transactional master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15673</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15673"/>
				<updated>2021-01-06T06:54:02Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Icertis Search for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Icertis&amp;amp;nbsp;Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Icertis Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Icertis&amp;amp;nbsp;search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Icertis&amp;amp;nbsp;Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Icertis&amp;amp;nbsp;'''''''''S'''earch Health''': This displays the Status (yellow/green/red), the Icertis&amp;amp;nbsp;Search version and the Uptime, and so on.'' &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Icertis Search Health'''&amp;lt;br/&amp;gt; The details for the Icertis&amp;amp;nbsp;Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the Icertis&amp;amp;nbsp;search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target&amp;amp;nbsp;environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;tool already supported&amp;amp;nbsp;contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The Icertis&amp;amp;nbsp;search sync is also supported by the tool.&lt;br /&gt;
&lt;br /&gt;
With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities&amp;amp;nbsp;:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;''Accessing P2P Tool''&amp;lt;/span&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home&amp;amp;nbsp;'''&amp;gt;&amp;amp;nbsp;'''Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Creating a P2P Request'''''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
Toggle&amp;amp;nbsp;''Resume P2P From Last Successful Step'' to Yes/No, as required.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''As stated in the disclaimer, while promoting configuration, target environment will be down during contract type publish. This tool must be used responsibly under project team’s approvals to avoid inconsistency and downtime.&amp;lt;/div&amp;gt; &lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&amp;amp;nbsp;The entities supported such as ''Org Group, Role Action Mapping, SLA Matrix,'' etc. will be available for selection.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users on&amp;amp;nbsp;the&amp;amp;nbsp;''Select Users''&amp;amp;nbsp;page. For example, ''01ux user, 02ux 2, 05ux 2''.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''''Selected Users'' to view the list of users that have been selected.&lt;br /&gt;
&lt;br /&gt;
33. '''Click&amp;amp;nbsp;'''''Filter Users ''to view the list of users by an attribute or click ''Add Another Attribute ''to filter users by additional attributes. For example, ''Email ID, Phone Number''.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''''Remove''&amp;amp;nbsp;to remove an added attribute.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, transactional master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15664</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15664"/>
				<updated>2021-01-06T06:31:39Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Icertis Search for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Icertis&amp;amp;nbsp;Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Icertis Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Icertis&amp;amp;nbsp;search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Icertis&amp;amp;nbsp;Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Icertis&amp;amp;nbsp;'''''''''S'''earch Health''': This displays the Status (yellow/green/red), the Icertis&amp;amp;nbsp;Search version and the Uptime, and so on.'' &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Icertis Search Health'''&amp;lt;br/&amp;gt; The details for the Icertis&amp;amp;nbsp;Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the Icertis&amp;amp;nbsp;search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target&amp;amp;nbsp;environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;tool already supported&amp;amp;nbsp;contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The Icertis&amp;amp;nbsp;search sync is also supported by the tool.&lt;br /&gt;
&lt;br /&gt;
With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities&amp;amp;nbsp;:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Accessing P2P Tool'''''&amp;lt;/span&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home&amp;amp;nbsp;'''&amp;gt;&amp;amp;nbsp;'''Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Creating a P2P Request'''''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
Toggle&amp;amp;nbsp;''Resume P2P From Last Successful Step'' to Yes/No, as required.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''As stated in the disclaimer, while promoting configuration, target environment will be down during contract type publish. This tool must be used responsibly under project team’s approvals to avoid inconsistency and downtime.&amp;lt;/div&amp;gt; &lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&amp;amp;nbsp;The entities supported such as ''Org Group, Role Action Mapping, SLA Matrix,'' etc. will be available for selection.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users on&amp;amp;nbsp;the&amp;amp;nbsp;''Select Users''&amp;amp;nbsp;page. For example, ''01ux user, 02ux 2, 05ux 2''.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''''Selected Users'' to view the list of users that have been selected.&lt;br /&gt;
&lt;br /&gt;
33. '''Click&amp;amp;nbsp;'''''Filter Users ''to view the list of users by an attribute or click ''Add Another Attribute ''to filter users by additional attributes. For example, ''Email ID, Phone Number''.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''''Remove''&amp;amp;nbsp;to remove an added attribute.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, transactional master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15663</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15663"/>
				<updated>2021-01-06T06:24:11Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Icertis Search for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Icertis&amp;amp;nbsp;Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Icertis Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Icertis&amp;amp;nbsp;search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Icertis&amp;amp;nbsp;Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Icertis&amp;amp;nbsp;'''''''''S'''earch Health''': This displays the Status (yellow/green/red), the Icertis&amp;amp;nbsp;Search version and the Uptime, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Icertis Search Health'''&amp;lt;br/&amp;gt; The details for the Icertis&amp;amp;nbsp;Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the Icertis&amp;amp;nbsp;search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target (production) environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;tool already supported&amp;amp;nbsp;contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The Icertis&amp;amp;nbsp;search sync is also supported by the tool.&lt;br /&gt;
&lt;br /&gt;
With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities&amp;amp;nbsp;:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Accessing P2P Tool ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home&amp;amp;nbsp;'''&amp;gt;&amp;amp;nbsp;'''Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Creating a P2P Request'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
Toggle&amp;amp;nbsp;''Resume P2P From Last Successful Step'' to Yes/No, as required.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''As stated in the disclaimer, while promoting configuration, target environment will be down during contract type publish. This tool must be used responsibly under project team’s approvals to avoid inconsistency and downtime.&amp;lt;/div&amp;gt; &lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&amp;amp;nbsp;The entities supported such as ''Org Group, Role Action Mapping, SLA Matrix,'' etc. will be available for selection.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users on&amp;amp;nbsp;the&amp;amp;nbsp;''Select Users''&amp;amp;nbsp;page. For example, ''01ux user, 02ux 2, 05ux 2''.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''''Selected Users'' to view the list of users that have been selected.&lt;br /&gt;
&lt;br /&gt;
33. '''Click&amp;amp;nbsp;'''''Filter Users ''to view the list of users by an attribute or click ''Add Another Attribute ''to filter users by additional attributes. For example, ''Email ID, Phone Number''.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''''Remove''&amp;amp;nbsp;to remove an added attribute.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, transactional master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15662</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15662"/>
				<updated>2021-01-05T07:44:41Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Elastic Search (ES) for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Elastic Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Elastic Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Elastic search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Elastic Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Elastic Search Health''': This displays the Status (yellow/green/red), the Elastic Search version and the Uptime, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Elastic Search Health'''&amp;lt;br/&amp;gt; The details for the Elastic Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the elastic search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target (production) environment, thus reducing the manual efforts to do so. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;tool already supported&amp;amp;nbsp;contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The elastic search sync is also supported by the tool.&lt;br /&gt;
&lt;br /&gt;
With the 7.15 release, to provide a seamless P2P experience, enhancements have been made in ICI to support the following additional entities :&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Accessing P2P Tool ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home&amp;amp;nbsp;'''&amp;gt;&amp;amp;nbsp;'''Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Creating a P2P Request'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
Toggle&amp;amp;nbsp;''Resume P2P From Last Successful Step'' to Yes/No, as required.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''As stated in the disclaimer, while promoting configuration, target environment will be down during contract type publish. This tool must be used responsibly under project team’s approvals to avoid inconsistency and downtime.&amp;lt;/div&amp;gt; &lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&amp;amp;nbsp;The entities supported such as ''Org Group, Role Action Mapping, SLA Matrix,'' etc. will be available for selection.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users on&amp;amp;nbsp;the&amp;amp;nbsp;''Select Users''&amp;amp;nbsp;page. For example, ''01ux user, 02ux 2, 05ux 2''.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''''Selected Users'' to view the list of users that have been selected.&lt;br /&gt;
&lt;br /&gt;
33. '''Click&amp;amp;nbsp;'''''Filter Users ''to view the list of users by an attribute or click ''Add Another Attribute ''to filter users by additional attributes. For example, ''Email ID, Phone Number''.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''''Remove''&amp;amp;nbsp;to remove an added attribute.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, transactional master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15661</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15661"/>
				<updated>2021-01-04T14:25:15Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Elastic Search (ES) for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Elastic Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Elastic Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Elastic search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Elastic Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Elastic Search Health''': This displays the Status (yellow/green/red), the Elastic Search version and the Uptime, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Elastic Search Health'''&amp;lt;br/&amp;gt; The details for the Elastic Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the elastic search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target (production) environment. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
With the 7.11 release, the Promote to Production (P2P) tool to enable users with the following enhancements:&lt;br /&gt;
&lt;br /&gt;
*Vulnerability and Penetration Testing (VAPT) fixes &lt;br /&gt;
*Testing open bugs in P2P engine &lt;br /&gt;
*Some new validations in the P2P engine &lt;br /&gt;
*Better user interface to provide support to P2P and DevOps teams &lt;br /&gt;
&lt;br /&gt;
With the 7.12 release, changes have been made in ICI to support the P2P engine. This functionality, provided to Administrators, can promote ICI configurations/modifications that are made to ICI configurations in pre-production environments to production environments. This tool provides support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The elastic search sync is also supported by the tool.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' UI changes on contract type, rule set, notification template are not included. Customers using ICI version before 7.12 need to upgrade for this capability.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Accessing P2P Tool ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home&amp;amp;nbsp;'''&amp;gt;&amp;amp;nbsp;'''Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Creating a P2P Request'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users from the&amp;amp;nbsp;''Available Users''&amp;amp;nbsp;column.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''the arrow key to move the selected user to the S''elected Users'' column.&lt;br /&gt;
&lt;br /&gt;
33. '''Select&amp;amp;nbsp;'''the user group from the&amp;amp;nbsp;''Available User Groups''&amp;amp;nbsp;column.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''the arrow key to move the selected user to the S''elected User Groups'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15660</id>
		<title>Self-Serve Tools</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Self-Serve_Tools&amp;diff=15660"/>
				<updated>2021-01-04T14:24:01Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
= Self-Serve Tools =&lt;br /&gt;
&lt;br /&gt;
Self-Serve tools include tools and features of ICI that can be used out-of-the-box by authorized users. Besides serving ICI users with specific feature and performance goals, being self-sufficient is the primary goal of these tools. These tools are user-friendly and time-saving, enabling users to perform tasks by themselves instead of reaching out to Icertis Solutions Engineering, Database or Support teams based on the requirement. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
The ICI Self-Serve tools include:&lt;br /&gt;
&lt;br /&gt;
*Search Sync Tool &lt;br /&gt;
*Translations Editor Tool &lt;br /&gt;
*Improved ICI Health Check Tool &lt;br /&gt;
*Configurations Key Editor Tool &lt;br /&gt;
*Promote to Production (P2P) Tool &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Prerequisites&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
*The ICI application, version 7.11 and above &lt;br /&gt;
*The user must have valid credentials to access ICI and the ''User Administration'' tile. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Search Sync Tool ==&lt;br /&gt;
&lt;br /&gt;
The Search Sync tool gets data from Elastic Search (ES) for a given instance’s&amp;amp;nbsp;''Sys Id ''and synchronizes it if required.&amp;amp;nbsp;Using the fetched ES value, the tool validates if the Sys Id is the latest for the respective instance or if a sync is required. This tool can be accessed by the Administrator from the ''Admin Task'' on ''User Administration'' tile.&lt;br /&gt;
&lt;br /&gt;
If the key exists, the latest value from ES will be displayed. If the key does not exist, the system displays an error message indicating that the value could not be fetched for the provided Sys Id. The Sys Id can be provided as input CSV file or as comma separated. Either comma separated Sys Ids can be entered or a CSV file can be uploaded.&lt;br /&gt;
&lt;br /&gt;
This helps to make the entity search more streamlined and efficient. Users can quickly refer to related agreements at the time of deals or audits.&lt;br /&gt;
&lt;br /&gt;
'''Note''': Data can be fetched from only one instance at a time. A dedicated key must exist for ES sync to work with ''Sys ID''.&lt;br /&gt;
&lt;br /&gt;
You can search the documents that an Agreement is linked to.&lt;br /&gt;
&lt;br /&gt;
To use the Search Sync Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;Home &amp;gt; User Administration &amp;gt;&amp;amp;nbsp;''Admin Task''.&amp;amp;nbsp;The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 1.png|720px|Search Sync 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Search Sync ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 2.png|720px|Search Sync 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Entity Type&amp;amp;nbsp;''from the drop-down to sync data to the Elastic Search. For example, Agreement.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the drop-down''.''&lt;br /&gt;
&lt;br /&gt;
5. '''Toggle '''''Skip Agreement Document Indexing ''to ''Yes/No'' as required.&lt;br /&gt;
&lt;br /&gt;
6. To get the ''Sys Ids,''&amp;amp;nbsp;'''click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Upload CSV&amp;amp;nbsp;button'' to upload the .CSV Agreement or&amp;amp;nbsp;enter&amp;amp;nbsp;the Sys Id using comma separated value in the box.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' the&amp;amp;nbsp;''Upload CSV''&amp;amp;nbsp;button to upload the CSV document. The&amp;amp;nbsp;''Upload Document''&amp;amp;nbsp;window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 3.png|720px|Search Sync3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click''' ''SelectFile'' to upload a CSV file and add a note if required.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 4.png|720px|Search Sync 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Upload File''. The file is uploaded to the ''File Path ''displayed.If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&lt;br /&gt;
If the uploaded file format is incorrect, an alert message is displayed. The supported file formats will be also be displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 6.png|720px|Search Sync 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10. '''Click'''&amp;amp;nbsp;''Sync''. The&amp;amp;nbsp;''Sync Request Accepted''&amp;amp;nbsp;message is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 7.png|720px|Search Sync7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click'''&amp;amp;nbsp;''Ok''. Users can now get data from ES for a given instance’s&amp;amp;nbsp;SysId&amp;amp;nbsp;and can check if it has the latest value or if a sync is needed.&lt;br /&gt;
&lt;br /&gt;
12. '''Select''' ''Get ES Value''.&lt;br /&gt;
&lt;br /&gt;
13. Enter the SysId and '''click''' ''Go''. If the key exists, the latest value from ES will be displayed. If the key does not exist, the error message ''Please enter valid SysId'' is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync 8.png|720px|Search Sync 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Elastic Search Sync'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can now get data from Elastic search for a given instance’s ''SysId'' so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message “Could not fetch value for provided SysId”.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Data can be fetched from only one instance at a time.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Search Sync ES.png|720px|Search Sync ES.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Translations Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform is available in different languages and different languages label text are available&amp;amp;nbsp;for&amp;amp;nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.&lt;br /&gt;
&lt;br /&gt;
Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized.&lt;br /&gt;
&lt;br /&gt;
Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICI. Once the values are updated in ICI, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.&lt;br /&gt;
&lt;br /&gt;
Using this tool, users can now:&lt;br /&gt;
&lt;br /&gt;
*Search for a specific string using the search bar and update the Resource Key value for Language and Locale. &lt;br /&gt;
*Update multiple language strings by selecting and saving the Resource Key value. &lt;br /&gt;
*Download and upload the localization key values using Microsoft Excel. &lt;br /&gt;
*View the modified values in the ICI instance immediately. &lt;br /&gt;
&lt;br /&gt;
To use the Translations Editor Tool:&lt;br /&gt;
&lt;br /&gt;
1. '''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''User Administration'' tile on the ''Home'' page.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''''Admin Task''&amp;amp;nbsp;from the drop-down. The ''Admin Task'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:User Administration.PNG|720px|User Administration]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Translation Editor ''task from the left pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 1.png|720px|Translation Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
Users can update translations in the following ways:&lt;br /&gt;
&lt;br /&gt;
1. For selective editing, select a language and a resource key to update the translations.&lt;br /&gt;
&lt;br /&gt;
2. For bulk editing and updation of multiple languages and resource keys, use the Download / Upload option to download an MS Excel sheet.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Selective Editing to Update Translations&amp;lt;/span&amp;gt;'''''&amp;lt;/div&amp;gt; &lt;br /&gt;
For editing Resource Key values selectively:&lt;br /&gt;
&lt;br /&gt;
1. From the ''Select Language'' drop-down, select a language in which you want to edit the labels.&amp;amp;nbsp; For example, français (French).&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 2.png|720px|Translation Editor 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The Resource Key and respective values of the selected language are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 3.png|720px|Translation Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Ente'''r a ''ResourceKey ''value in the''Search'' field to edit. For example, default. All ResourceKey(s) with the ''Par défaut (default)'' values from the French language are displayed.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' ResourceKey is a unique key by which the application gets its label text for different languages.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 4.png|720px|Translation Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Edit this Resource Key for Multiple Languages&amp;amp;nbsp;'''''icon '''in the ''Actions'' column.&lt;br /&gt;
&lt;br /&gt;
You can change the key for a single language or for multiple languages as required. For example, change ''Par défaut'' to ''défaut'' in French or ''Predeterminado'' in Español (Spanish) to&amp;amp;nbsp;''Defecto''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 5.png|720px|Translation Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Update''. The ResourceKey value for ''default ''is updated to ''défaut ''for French and to ''Defecto'' in Spanish.&lt;br /&gt;
&lt;br /&gt;
5. The ''Resources Updated Successfully'' message is displayed. '''Click''' ''Ok''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 6.png|720px|Translation Editor 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can select the respective languages (French or Spanish) to verify that the resources have been successfully updated.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 7.png|720px|Translation Editor 7]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;'''&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;Bulk Editing in Multiple Languages&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;For editing Resource Key values of multiple languages in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Download File''. A Microsoft Excel file (named BulkActionWorkBookStringResource) that contains all the Resource keys and values for all supported languages in ICI is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Translation Editor 9.png|720px|Translation Editor 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Open''' the downloaded Microsoft Excel file.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Enable Editing''. All ICI supported language Resource keys and their respective values are displayed.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Edit''' the ResouceKey of multiple languages as required.&lt;br /&gt;
&lt;br /&gt;
5. '''Save''' the Excel file.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Upload File''. The ''Upload Translations'' window opens.&lt;br /&gt;
&lt;br /&gt;
7. '''Click''' ''SelectFile''. The ''Open ''window opens.&lt;br /&gt;
&lt;br /&gt;
8. '''Select''' the updated Excel file.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Open''. A warning window opens indicating that this is a heavy operation and can potentially affect overall application performance.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' ''Ok''. The ''Upload Summary'' displays the number ''of Records Uploaded, Records Processed, ''and''Records Updated Successfully ''values.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click''' ''Close''. The label translations have been achieved for multiple languages in bulk.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Health Check Tool ==&lt;br /&gt;
&lt;br /&gt;
The ICI platform hosted on Azure Cloud uses services such as Elastic Search, Redis along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ICI Health Check page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.&lt;br /&gt;
&lt;br /&gt;
The ICI Health Check page has been further extended to cover additional parameters to help identify potential outages and diagnose issues. The health insights will provide information on how well the ICI Instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICI) that tracks application health alongside usage metrics and application crash data.&lt;br /&gt;
&lt;br /&gt;
The health statuses are classified into three categories:&lt;br /&gt;
&lt;br /&gt;
*''Warning ''- This is indicated with a yellow warning icon &lt;br /&gt;
*''Healthy ''- This is indicated with a green check mark icon &lt;br /&gt;
*''Unhealthy ''- This is indicated with a red warning icon &lt;br /&gt;
&lt;br /&gt;
The following details are displayed in the Health Check:&lt;br /&gt;
&lt;br /&gt;
*'''Elastic Search Health''': This displays the Status (yellow/green/red), the Elastic Search version and the Uptime, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Redis Cache Health''': This displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on. &lt;br /&gt;
&lt;br /&gt;
*'''API Health''': This displays the API Response Time, Status and Issues and so on. &lt;br /&gt;
&lt;br /&gt;
*'''Database Server Metrics''': This displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec and so on. &lt;br /&gt;
&lt;br /&gt;
*'''IIS Server Metrics''': This displays&amp;amp;nbsp;% 404 HTTP Response Sent,&amp;amp;nbsp;% 500&amp;amp;nbsp; HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;To view the Health Check, add &amp;quot;Health/ViewHealth&amp;quot;&amp;amp;nbsp;(without quotes) to your ICI URL.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To check the health of your system:&amp;lt;br/&amp;gt; 1. Enter '''''/health/viewhealth''''' at the end of the URL of your ICI instance. For example, [https://apexorg.icertis.com/health/viewhealth https://apexorg.icertis.com/health/viewhealth]. The various tools and their health are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 1.png|720px|Health Check 1]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 2. '''Click''' the + icon next to the tool to view details regarding its health. The details for each of the tools are displayed in 2 columns with the Keys and their respective values as shown below.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Elastic Search Health'''&amp;lt;br/&amp;gt; The details for the Elastic Search Health include the status, node total, primary and relocating shards, version, heap percent, uptime, and so on. For example, the Status is green.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 2.png|720px|Health Check 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Redis Cache Health'''&amp;lt;br/&amp;gt; The details for the Redis Cache Health include the uptime in days. Connected or blocked clients, rejected connections, CPU usage, and so on. For example, the Uptime in Days is 28.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 3.png|720px|Health Check 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''API Health'''&amp;lt;br/&amp;gt; The API Health provides the response time. For example, 94 ms.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 4.png|720px|Health Check 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Task Service Health&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;'''&amp;lt;br/&amp;gt; The Task Service Health provides the failed count for keys and when it was last successful.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 5.png|720px|Health Check 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Database Server Metrics'''&amp;lt;br/&amp;gt; The details for the Database Server Metrics Health include the edition, SQL server resource pool stats, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 6.png|720px|Health Check 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''IIS Server Metrics'''&amp;lt;br/&amp;gt; The details for the IIS Server Metrics Health include the total method requests/sec, number of seconds an IIS Worker process has been running, the percentage of CPU utilization per process, and so on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Health Check 7.png|720px|Health Check 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Configuration Key Editor Tool ==&lt;br /&gt;
&lt;br /&gt;
The Configuration Key Editor tool facilitates a logged-in user (who has access to Azure subscription) to search and update configuration keys, as and when required. It has been introduced for easier instance management and improved productivity, thus reducing the dependency on the Engineering and DevOps teams.&lt;br /&gt;
&lt;br /&gt;
It includes:&lt;br /&gt;
&lt;br /&gt;
*The ''Config Editor'' &lt;br /&gt;
*The ''Redis Flush'' &lt;br /&gt;
&lt;br /&gt;
The ''Config Editor'' is a self-service tool that allows teams to edit instance configurations without having to connect to the instance machines. Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.&lt;br /&gt;
&lt;br /&gt;
The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform ''Role Restart'' on the instances to which the user has access.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp; The user must have access privileges to an Environment CName in Config Editor.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 1.png|720px|Config Editor 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To use the Configuration Key Editor Tool:&amp;lt;br/&amp;gt; 1. Login to the ICI Tools portal (icmtools.icertis.com) with your ICI credentials.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 2.png|720px|Config Editor 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''the''Config Editor'' tab on the ''Home ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 3.png|720px|Config Editor 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select '''the environment from the ''Environment CName'' drop-down that you need to access for configuration. All the instances that have you have access to will be displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''Submit after selecting the environment. The configuration json files for the selected environment are displayed for all available features, security details, database connections, and so on related to the selected instance.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 4.png|720px|Config Editor 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Select''' a Config Key from the list to change its value as required. For example, the Config Key AgreementAutoRenewReminderNotificationPeriod has the reminder period set at 3 days may be changes to 2 days.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Config Editor 5.png|720px|Config Editor 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Save and Role Restart'' to save the new value of 2 days. The specific json file for the respective CName will be reset (i.e. perform a role restart). This means that the configuration is reset in the elastic search and the server is restarted, so that the new value is reflected on the instance.&amp;lt;br/&amp;gt; 7. '''Click''' ''Download'' to download the entire file so that you can edit it offline and then upload it directly to the instance.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Promote Configurations (P2P) Tool ==&lt;br /&gt;
&lt;br /&gt;
The Promote to Production (P2P) process of the ICI platform helps to move ICI Configuration from source (Config/UAT) environment to target (production) environment. P2P process enables to selectively move ICI configuration. The Promote Configuration Tool or P2P is designed to accomplish just that.&lt;br /&gt;
&lt;br /&gt;
With the 7.11 release, the Promote to Production (P2P) tool to enable users with the following enhancements:&lt;br /&gt;
&lt;br /&gt;
*Vulnerability and Penetration Testing (VAPT) fixes &lt;br /&gt;
*Testing open bugs in P2P engine &lt;br /&gt;
*Some new validations in the P2P engine &lt;br /&gt;
*Better user interface to provide support to P2P and DevOps teams &lt;br /&gt;
&lt;br /&gt;
With the 7.12 release, changes have been made in ICI to support the P2P engine. This functionality, provided to Administrators, can promote ICI configurations/modifications that are made to ICI configurations in pre-production environments to production environments. This tool provides support for contract types, contract type attributes, clauses and templates (along with the documents), notification templates, rules, masterdata, users, user groups and security groups. The elastic search sync is also supported by the tool.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' UI changes on contract type, rule set, notification template are not included. Customers using ICI version before 7.12 need to upgrade for this capability.&amp;lt;/div&amp;gt; &lt;br /&gt;
Here is an overview of the P2P process:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 1.png|720px|P2P 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Accessing P2P Tool ===&lt;br /&gt;
&lt;br /&gt;
To access the P2P tool:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''''Home''''&amp;gt;&amp;amp;nbsp;Configuration&amp;amp;nbsp;''tile. The ''Configuration ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''the ''Promote'' ''Configurations'' tile. The ''Promote Configuration'' page opens.&amp;amp;nbsp;The ''Promote Configurations ''displays the current status of P2P requests and their status.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Users cannot edit a request that is in ''Completed'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 2.png|720px|P2P 2]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-caption&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''''Creating a P2P Request'''''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
To create a P2P Request:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Configurations &amp;gt; Promote Configurations &amp;gt; Create Request''. The&amp;amp;nbsp;''Create P2P Request''&amp;amp;nbsp;page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 3.png|720px|P2P 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;a&amp;amp;nbsp;''Request Name''. For example,&amp;amp;nbsp;''Procurement''.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;a ''Target'' from the drop-down. For example,&amp;amp;nbsp;''Acme Dev''.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''P2P Request Start Date Time''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the time to trigger an email to the recipient from the&amp;amp;nbsp;''Intimation Email minutes before P2P Starts&amp;amp;nbsp;''drop-down list. For example,&amp;amp;nbsp;''15 Min''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the intimation recipient Email Id in the&amp;amp;nbsp;''Notification Email – Intimation&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient Email Id in the&amp;amp;nbsp;''Notification Email – Success&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Failure&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Enter'''&amp;amp;nbsp;the notification recipient email Id in the&amp;amp;nbsp;''Notification Email – Cancel&amp;amp;nbsp;''field.&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Type''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the&amp;amp;nbsp;''Contract Type&amp;amp;nbsp;''from the&amp;amp;nbsp;''Available Contract Types''. For example,&amp;amp;nbsp;''Fiscal Year Master''. The selected Contract Type attributes are available in the&amp;amp;nbsp;''Attributes Of Selected Contract Type''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
12.&amp;amp;nbsp;'''Select '''the attributes for the selected contract type'''. '''For example, ''Created By''.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''the right arrow to move the selected contract type and attribute to ''the Selected Contract Types'' and ''Attributes Of Selected Contract Type'' columns respectively.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 4.png|720px|P2P 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
14.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''. The&amp;amp;nbsp;''Templates and Clauses&amp;amp;nbsp;tab'' opens.&lt;br /&gt;
&lt;br /&gt;
15.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a template from the&amp;amp;nbsp;''Available Templates''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Demo Template''.&lt;br /&gt;
&lt;br /&gt;
16.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Templates'' column.&lt;br /&gt;
&lt;br /&gt;
17.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a clause from the''&amp;amp;nbsp;Available Clauses''&amp;amp;nbsp;columns. For example,&amp;amp;nbsp;''Clause 1_Demo''.&lt;br /&gt;
&lt;br /&gt;
18.&amp;amp;nbsp;'''Click '''the arrow key to move the selected clause to the S''elected Clauses'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 5.png|720px|P2P 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
19.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Rules'' tab opens.&lt;br /&gt;
&lt;br /&gt;
20.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;a Rule from the&amp;amp;nbsp;''Available Rule Set Information''&amp;amp;nbsp;column. For example, ''ICI_Master I Master_Exec Summary on Agr Add Association''.&lt;br /&gt;
&lt;br /&gt;
21.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Rule Set Information'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 6.png|720px|P2P 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
22.&amp;amp;nbsp;'''Click '''''Next''. The&amp;amp;nbsp;''Notifications ''tab opens.&lt;br /&gt;
&lt;br /&gt;
23.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the notification template from the&amp;amp;nbsp;''Available Notification Template''&amp;amp;nbsp;columns. For example, ''UserInformation I User Information Expired I UserInformationExpired I User Notifications''.&lt;br /&gt;
&lt;br /&gt;
24.&amp;amp;nbsp;'''Click '''the arrow key to move the selected template to the S''elected Notification Templates'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 7.png|720px|P2P 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
25.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Next''.&amp;amp;nbsp;The&amp;amp;nbsp;''Master Data &amp;amp; Core Seed Data''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;Users can use the ''P2P tool&amp;amp;nbsp;Master Data''&amp;amp;nbsp;tab for the faster transition of Master Data to production than the Bulk utility tool option.&amp;lt;/div&amp;gt; &lt;br /&gt;
27.&amp;amp;nbsp;'''Click '''the arrow key to move the selected rule to the S''elected Master Data'' column.&lt;br /&gt;
&lt;br /&gt;
28.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the seed data from the&amp;amp;nbsp;''Available Core Seed Data''&amp;amp;nbsp;column.&lt;br /&gt;
&lt;br /&gt;
29.&amp;amp;nbsp;'''Click '''the arrow key to move the selected master data to the S''elected Core Seed Data ''column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 8.png|720px|P2P 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
30.&amp;amp;nbsp;'''Click '''''Next. ''The&amp;amp;nbsp;''Users &amp;amp; User groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
31.&amp;amp;nbsp;'''Select'''&amp;amp;nbsp;the users from the&amp;amp;nbsp;''Available Users''&amp;amp;nbsp;column.&lt;br /&gt;
&lt;br /&gt;
32.&amp;amp;nbsp;'''Click '''the arrow key to move the selected user to the S''elected Users'' column.&lt;br /&gt;
&lt;br /&gt;
33. '''Select&amp;amp;nbsp;'''the user group from the&amp;amp;nbsp;''Available User Groups''&amp;amp;nbsp;column.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
34. '''Click '''the arrow key to move the selected user to the S''elected User Groups'' column.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 9.png|720px|P2P 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
35. '''Click'''''&amp;amp;nbsp;Next'' if any or no user or user group is selected.&amp;amp;nbsp;The&amp;amp;nbsp;''Security Groups''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
36. '''Select&amp;amp;nbsp;'''the security group from the&amp;amp;nbsp;''Available Security Groups''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
37. '''Click '''the arrow key to move the selected security group to the S''elected Security Groups'' column.&lt;br /&gt;
&lt;br /&gt;
38.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the KPI from the&amp;amp;nbsp;''Available KPI’s''&amp;amp;nbsp;columns.&lt;br /&gt;
&lt;br /&gt;
39.&amp;amp;nbsp;'''Click '''the arrow key to move the selected KPI to the S''elected SaveSearchKPIs'' column. For example, ''Product Authorization''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 10.png|720px|P2P 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
40. '''Click'''&amp;amp;nbsp;''Next''. The''&amp;amp;nbsp;Verify''&amp;amp;nbsp;tab opens.&lt;br /&gt;
&lt;br /&gt;
41. '''Verify''' details of the contract types, attributes, templates, clauses, rule set information, notification templates, master data, core seed data, user and user groups, save search KPI and security groups that you have selected.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 11.png|720px|P2P 11]]&amp;lt;/div&amp;gt; &lt;br /&gt;
42. '''Click&amp;amp;nbsp;'''''Create''.&amp;amp;nbsp;The&amp;amp;nbsp;''Please Confirm''&amp;amp;nbsp;window opens indicating that downtime is required for this request.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''''Note''''':&amp;amp;nbsp;The P2P tool verifies all the information entered by the user before creating a P2P request.&amp;lt;/div&amp;gt; &lt;br /&gt;
43.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Yes ''if you wish to proceed.&amp;amp;nbsp;The&amp;amp;nbsp;''Information&amp;amp;nbsp;''window opens indicating that the P2P request created successfully.&lt;br /&gt;
&lt;br /&gt;
44.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Ok''.&amp;amp;nbsp;The P2P request&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''ADDED''.&lt;br /&gt;
&lt;br /&gt;
45. On completion of the P2P request, the&amp;amp;nbsp;status&amp;amp;nbsp;changes to&amp;amp;nbsp;''Completed''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Users cannot edit a request that is in&amp;amp;nbsp;''Completed''&amp;amp;nbsp;state.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:P2P 12.png|720px|P2P 12]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== AI Apps Rules Engine ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Management|Agreement Management]] |&amp;amp;nbsp;[[Association_Management|Association Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Compliance_Management|Compliance Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Template_Management|Template Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Clause_Management|Clause Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15644</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15644"/>
				<updated>2021-01-03T12:38:21Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== Overview of Release 7.15 ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514613 – Introducing the ability to preview agreements before publishing'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, contract owners had to view the first version of an agreement in order to get a comprehensive view of the agreement that they had created.&lt;br /&gt;
&lt;br /&gt;
With this release, a preview functionality is being introduced, so that primary owners or contract creators can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A “Generate Preview” button has been introduced on the “Verify stage” of agreement creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. Associated documents, coming through inline associations, for example, will also be included and displayed in the preview document.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''The preview functionality is configurable and will not be available by default.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575640 – Creating associations on create or edit wizard of agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, contract authors had to create associations for agreements using the association management functionality. However, in practical terms associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of agreement information that is critical to business.&lt;br /&gt;
&lt;br /&gt;
In view of this, the ability to create association instances as part of agreement creation is being introduced in this release. A separate page is displayed to the user during agreement or amendment creation to create, view or delete inline associations. The user also has an option to select the columns and their order in the association grid.&lt;br /&gt;
&lt;br /&gt;
Support is also provided to copy attribute rules, association events and agreement assembly, in case associations are tagged in the agreement template.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''549900 – Supporting localized reason code values as per logged in user language'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Adapting existing products to new markets through translation and localization is the key for global growth. The localized versions of the product improve the overall user experience and helps to better connect with new and potential global customers.&lt;br /&gt;
&lt;br /&gt;
ICI now extends its localization support to reason code values. Users can see localized reason codes as per their preferred language settings. Administrators can enter the translated values in the local language for each reason code using the “Translations Editor” tool. The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''614944 – Initiating termination for parent agreement from contract request'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, to terminate an agreement, users create and execute a termination agreement on a main agreement. ICI has now extended this capability to contract requests also.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can enable the termination process at contract type level using the seeded attribute &amp;quot;Request for Termination&amp;quot;, select the parent contract request, and create the termination contract on a contract request. The termination instance for contract request will have all the common attribute values inherited, if the inheritance is enabled. The termination record will be displayed as a peer association under the “Association” tab for the contract request.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The access privileges for the contract requests termination process is controlled through role action mapping.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;506398 – Enabling search for external users with login privileges&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
ICI’s collaboration portal allows external users with login privileges to access the platform and perform tasks assigned to them within ICI itself.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In our continuous effort to improve usability, a search option has been introduced on index pages, so that external users can easily search records. To perform a more refined search, the attributes displayed as columns of the search grid are included as facets in the filter options. This is applicable to index pages of contract requests, agreements, associations and masterdata.&amp;lt;br/&amp;gt; '''Note:&amp;amp;nbsp;'''This is not applicable for:&lt;br /&gt;
&lt;br /&gt;
*Global search. &lt;br /&gt;
*Attribute group privilege restrictions on search results, filters and categories.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514605 – Supporting extended clause attributes in agreements and reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for a clause in the extension attributes. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to view these clause extension attributes on the agreement entity for easy reference while working with agreements.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs. &lt;br /&gt;
*View the hyperlink “Show Clause Information”, which displays all clause extension attributes in a separate window. &lt;br /&gt;
*Select and save extension attributes to display in the grid view. &lt;br /&gt;
*View clause extension attributes in the “Clause Profiling Report”. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514615 – Approving a contract from emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Email notifications, in ICI, allow users to customize text, add tags (attributes) inside the email body, define recipients, and so on. This capability has been further enhanced such that approvers can directly approve or reject an agreement from within the email itself, as part of the approval or request review process, thus reducing the overall turnaround time and increasing efficiency.&lt;br /&gt;
&lt;br /&gt;
They can also add notes on approval, add reason code on rejection, and enable download or upload of the agreement document along with comments. This is applicable to contract requests, agreements, associations, amendments, masterdata, templates, clauses and user information instances.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514643 – Ordering of clauses as tagged in an agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, list of clauses available inside the agreement or amendment displayed clauses in a random order on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
With this release, the tagged clauses are displayed on respective pages in ICI Web and Icertis Experience for Word, in the same order in which they are tagged inside the agreement, thus making it easier for users to identify them. The order is refreshed on every upload to display the latest.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514621 – Reviving terminated agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users may terminate an agreement with the other party for various business reasons. To improve usability, ICI now provides the capability to add and execute amendments on a terminated agreement. This considerably saves the time for users who may want to re-instantiate their existing relationship with the other party, as they no longer need to create an entirely new agreement, and go through several workflows such as clause deviations clearance, template process, and so on.&lt;br /&gt;
&lt;br /&gt;
Adding and executing an amendment on a terminated agreement will move the agreement back to the “Executed” or “Expired” state, based on its expiry date, thus reviving the terminated agreement. It will also revive any amendments of the base agreement terminated through the agreement termination process and move them back to their respective previous states. However, any previous amendments terminated through review process will remain in the terminated state. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can set an identifier attribute &amp;quot;Is Termination Revived&amp;quot; for such revived base agreements and use them in search filters, configuring saved searches, notification rules, and so on.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''By default, only primary owners and contract managers can add an amendment to the terminated agreement. The access privileges are controlled through role action mapping.&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514625 – Terminating agreements in bulk'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users may need to terminate agreements in bulk in many business scenarios such as regulatory changes, changes in product offerings, and so on. Users can now initiate termination of agreements in bulk, thereby reducing the manual errors and saving the time to terminate agreements one by one. Bulk termination is carried out using ICI’s existing “Bulk Actions” process. The termination related attributes will be pre-selected, and the Workbook for the bulk action batch will be generated with the executed agreement records from the saved search, as per the selected contract type and termination contract type.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch. &amp;amp;nbsp; &lt;br /&gt;
*Generate and view a status report for agreements terminated in bulk.&amp;amp;nbsp; &lt;br /&gt;
*Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk action. &lt;br /&gt;
&lt;br /&gt;
'''Note: '''All the prerequisite configurations applicable for the Termination workflow should also be set for the bulk termination process.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555898 – Defining display sequence on lookup attributes at contract type level'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, users could not define the display order for lookup attribute’s values in a drop-down on ICI UI to reference masterdata. Users then had to scroll through all populated values in order to find the desired values during agreement creation. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The configurators can now define and maintain the display sequence for masterdata records, starting from 1 to n, at the contract type level, using a seeded display sequence attribute. The configurators can also define the order only for selected records in the masterdata. The frequently selected values will be thus displayed at the top for easier and faster selection in lookup attributes, without the need to scroll through all values. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This setting of display sequence is supported on create, edit and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause and template entities, and template variables.&lt;br /&gt;
&lt;br /&gt;
The display will revert to the default alphabetical order if the display sequence is not configured in masterdata.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''558605 – Viewing amendments in grid view on agreement details page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, users could only view the agreement’s amendments in a “Tile” view, when opened from the left navigation pane on the agreement “Details” page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now allows users to view amendments in “Grid” view as well, and have the capability to toggle between the grid view and existing tile view. The grid view is the default view for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''561410 – Enhancing the multi-select drop-down&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The multi-select choice drop-down has been enhanced for better usability, data input and post-selection data review of contract requests, agreements, amendments and masterdata entities.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View eight default options in a drop-down list (instead of six), without scrolling.&amp;amp;nbsp; &lt;br /&gt;
*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&amp;amp;nbsp; &lt;br /&gt;
*View all selected values at the top of the drop-down. &lt;br /&gt;
*Deselect the selected values individually or all with a single-click, without opening the drop-down.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''819453 – Configuring opening of drop-down menus on mouse hover'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI has improved usability by providing the capability to configure the expansion of drop-downs on mouse hover, instead of a mouse click.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be configured at a contract type level and supports contract requests, agreements, associated documents and masterdata. It is applicable for lookup, multi-select lookup, choice, multi-select choice and currency drop-downs.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''620411 – Defining IN operator when applying lookup filters'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, the configurator can filter the lookup masterdata table with “Must” and “Must Not” conditions, to achieve necessary business scenarios, while configuring a lookup attribute on contract types.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now also provides the ability to configure a lookup attribute with the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Configurators can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Use the &amp;quot;IN” operator in lookup filter attribute on agreement contract types.&amp;amp;nbsp; &lt;br /&gt;
*View applied filter on the attribute “Details” tab on ICI UI for the selected attribute.&amp;amp;nbsp; &lt;br /&gt;
*Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute. &amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''573339 – Managing user preferences as part of profile management'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now provides the capability for administrators to set preferences as default, for users, according to their locations or offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after first log-in, and presents the system with appropriate and specific pre-settings. &amp;amp;nbsp;&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Set and manage preferences for single user through single user update, and for multiple users through bulk process. &lt;br /&gt;
*View preference settings modifications details in the “History” tab for audit.&amp;amp;nbsp; &lt;br /&gt;
*Search users based on parameters related to preference settings. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Access the ICI system with appropriate details as default after first login.&amp;amp;nbsp; &lt;br /&gt;
*Override the default preference settings as per individual preferences. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''604775 – Moving agreement to executed state without uploading document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, users could not move agreements and amendments from “Waiting For Signature” to “Executed” state without uploading the supporting document, in case of manually signed agreements.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can now skip uploading the document to move agreements from “Waiting For Signature” to the “Executed - Document Upload Pending” state. Users can then search or create a saved search for such agreements and upload the required documents later using the “Upload Fully Signed Copy” action.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Notifications can be configured to inform users about skipped document uploads, so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This functionality is available for agreements, amendments and orphan amendments.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''614860 – Attaching associated documents to agreement notifications'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI users could share the main agreement document as part of various email notifications that get triggered for the agreement from time to time.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This capability has now been extended to supporting (associated) documents as well, so that users no longer need to manually share them offline.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements and amendments. &lt;br /&gt;
*Users can define the notification as internal or external.&amp;amp;nbsp; &lt;br /&gt;
*Users can define the type of associated document instance as internal, external or restricted. &lt;br /&gt;
*Based on the type of notification and type of tagged associated documents, documents are attached to the email notification. &lt;br /&gt;
&lt;br /&gt;
​​​​​​​&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''586492 – Defining different relationship types while associating peer instance'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to define the linkage type as parent, child or peer while associating peer entities with each other.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users now have the capability to define custom labels for peer associations by configuring the “Linkage Type” masterdata. The custom labels define various business relationships in the context of contracts. For example, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The custom labels will support existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as peer, with default peer linkage type label, defined in default peer mapping for amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select custom peer linkage type labels in the linkage type drop-down list and view them on various ICI functionalities as: &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Agreement creation workflows for peer entities, assignment, initiate termination flow.&amp;amp;nbsp; &lt;br /&gt;
*Associate and Inheritance icons. &lt;br /&gt;
*Legacy upload and bulk actions. &lt;br /&gt;
*Agreement creation through business APIs. &lt;br /&gt;
*Broadcast – “Attachments” tab, beside peer-to-peer instances. &lt;br /&gt;
&lt;br /&gt;
'''Note: '''Custom labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''619558 – Downloading amendments using download all functionality'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements and bulk operations.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can also selectively download amendments of an agreement with corresponding parent child associations in the downloaded zip package.&lt;br /&gt;
&lt;br /&gt;
For ease of access, each selected amendment will be downloaded with its selected associations in separate folders. The folders are named “Amendment_1”, “Amendment_2”, and so on (from oldest to latest), instead of actual amendment names. This helps to overcome the Windows limitation of supporting 260 characters in the file path, and gives users the flexibility while creating association’s names.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''615291 – Configuring attributes inheritance for amendments at contract type level'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already provided the capability to exclude certain agreement attributes from being copied to the amendment through technical configuration which applied to all agreement contract types by default.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now provides the flexibility for users to decide which attributes of an agreement can be copied to amendments, per contract type, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using “Is Inherit On Amendments” attribute, at the agreement contract type and template variable levels. Users can then copy these defined attributes values from base agreement to amendment during amendment creation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The technical configuration settings for excluding parent agreement attributes from its amendments will always take preference over the settings at agreement contract type and template level. &lt;br /&gt;
*The existing validations or dependencies for an attribute’s properties set for agreement will not be inherited to amendments.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''614877 – Replacing a user with multiple users'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Replace the user with one or more users by selecting the entity and all/selective instances of that entity. &amp;amp;nbsp; &lt;br /&gt;
*Validate the replaced user role against the assigned role.&amp;amp;nbsp; &lt;br /&gt;
*Get notification on adding or completing a task.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided for these admin actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''614963 – Superseding agreement values as per amendment using rules'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users could supersede all parent agreement’s attributes configured as supersedable with values from its amendment, either manually using “Supersede” action or automatically through auto-supersede backend task.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can now selectively supersede individual entities based on business conditions.&lt;br /&gt;
&lt;br /&gt;
The administrator can control the supersede functionality for agreements by configuring rules with:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The rule type “Supersede Rule” with an “Auto Supersede option”, as true or false.&amp;amp;nbsp; &lt;br /&gt;
*The rule actions as “Is Auto Supersede by Amendment”, “Is Auto Supersede by Termination” and “Is Auto Supersede by Assignment for Amendment”, “Assignment and Termination”, with required attributes set, as per the business condition. &lt;br /&gt;
*The attribute selection field with all or multi-select capability.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Users can preview the attribute’s supersede value on the agreement and view the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing behavior.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''615293 – Showing or hiding the no team available message'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users may encounter specific workflow configurations such as self-approval process that do not require users to be added to the team. The “No Team Available” messages, displayed in such cases, add to the number of non-value clicks for users to continue. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now provides the capability to suppress this message, thereby minimizing the number of unnecessary clicks through technical configuration.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Selectively enable or disable the “No Team Available” message window, at entity contract type level, appearing at various states.&amp;amp;nbsp; &lt;br /&gt;
*Disable the “No Team Available” message window completely, at instance level, for all entities. The instance level settings will override any entity level settings.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note:''' This capability is available across ICI for all entities, events, integrations and add-ins in ICI.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''618345 – Defining complex conditional logic for attributes visibility'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, configurators can now set multiple, complex conditions to display attributes on ICI Web UI dynamically, based on business scenarios. Configurators can define conditions for attributes for all entities, except for template variables. For example, the configurator can set conditions to display an attribute based on the selection of specific value in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Apply multiple and complex conditions to display an attribute by enhancing the enable expression (visibility expression) for contract requests, agreements, associations and masterdata contract types.&amp;amp;nbsp; &lt;br /&gt;
*Support conditional expressions for extension attributes. &amp;amp;nbsp; &lt;br /&gt;
*Define conditions with different operators based on the selected attribute datatype.&amp;amp;nbsp; &lt;br /&gt;
*View the conditional attribute value according to the value entered in the attribute on which a condition is set, which in turn helps to enter the information in the required attribute as per business requirements.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''616901 – Applying facets to business status search filter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI search functionality supported filters on “Business Status” for users to narrow down results. However, manually selecting filters often becomes a tedious task in case of several business statuses.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In order to provide a better user experience, faceted filters using string operators, such as “Contains”, “Starts With”, “Does Not Contain”, and so on, are being added to the “Business Status” filters for ease of use.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''694211 – Improving handling of exceptions for string combinations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions. The parsing logic in ICI is now improved for handling string combinations with special and alphanumeric characters, so that no errors are generated.&lt;br /&gt;
&lt;br /&gt;
This is applicable to all entities across ICI, where a combination of special characters, alphabets and numbers can be used.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732929 – Uploading clauses and templates in bulk'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
New customers or new groups, onboarding to ICI, mostly have their templates and clauses already created in a separate file. Previously, manual efforts were needed to onboard the hundreds to thousands of templates and clauses.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, an automation has been provided for bulk import, which will reduce any human dependency, manual approvals and delays for onboarding templates and clauses using the current capabilities. ICI administrators can now import templates and upload clauses to ICI in bulk.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''655507 – Uploading and downloading large files with file path attribute'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI now provides support for larger files. This is applicable to masterdata and associations.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Upload files up to 4GB under the file selection attribute.&amp;amp;nbsp; &lt;br /&gt;
*Upload files with all supported files extensions allowed in the file selection attribute. &lt;br /&gt;
*Download All/Download Package up to 6 GB. &lt;br /&gt;
&lt;br /&gt;
ICI supports virus scanning of large files if the virus scan feature is enabled.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''This is not applicable for contract requests, agreements, associations with large files in the DocuSign/Adobe Sign association selection pop-up, document assembly, bulk actions, legacy upload, integrations (Salesforce, Workday, etc.), and APIs.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''697367 – Enhancing contract type publish to limit schema change for entity'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI has made the following enhancements to the contract type publish capability:&lt;br /&gt;
&lt;br /&gt;
*There is zero downtime when a contract type is published.&amp;amp;nbsp; &lt;br /&gt;
*The schema of only selected contract types that are being published will be blocked for write operations, hence they will not be available at the time of contract creation. However, all other contract types will be available to the user.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''618994 – Supporting special characters in agreement templates'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, attribute names did not support special characters.&lt;br /&gt;
&lt;br /&gt;
Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash), : (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (dot) can be used in the display name of attributes for contract requests, agreements, associations and masterdata contract types. The same attribute display name as provided by the configurator will now be displayed including special characters.&lt;br /&gt;
&lt;br /&gt;
Also, during template creation, user can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table. This allows empty columns to be skipped in document assembly, thereby reducing unnecessary empty columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI provides new controls for multi-select and single-select choice attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can configure an alternate UI control for drop-downs with limited number of values for choice attributes at contract type, global attribute and template variable levels. This improves the user experience as the number of clicks and scrolls required to view options in a drop-down are considerably reduced, and provides better readability in terms of post-selection data review. &amp;amp;nbsp;&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Radio button for single-select choice attributes.&amp;amp;nbsp; &lt;br /&gt;
*Checkbox list for multi-select choice attributes. &lt;br /&gt;
&lt;br /&gt;
The configuration is applicable for creation and editing of contract requests, agreements and amendments.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''752540 – Upgrading client-side libraries'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, some client-side libraries have been upgraded, whereas some that were not being used have been removed.&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Mobile App Updates ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI API Enhancements&amp;amp;nbsp; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to ICI Add-ins&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to Artificial Intelligence Applications in ICI ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &amp;amp;nbsp; &lt;br /&gt;
*View playbook details in a separate resizable window.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected contract type with options to search and filter within.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected agreement clause.&amp;amp;nbsp; &lt;br /&gt;
*Add deviation to the clause from playbook “Details” page.&amp;amp;nbsp; &lt;br /&gt;
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575475 – Automating user feedback for clauses, obligations and attributes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''539492 – Improving clause delineation in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&amp;amp;nbsp; &lt;br /&gt;
*Create a sub-clause within a discovered clause.&amp;amp;nbsp; &lt;br /&gt;
*Change the clause category and the level (parent or child) of the discovered clause. &amp;amp;nbsp; &lt;br /&gt;
*Choose to view only the level 0 clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''770375 – Merging metadata discovery page with attribute page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the discovery completion progress.&amp;amp;nbsp; &lt;br /&gt;
*Identify discoverable attributes marked with the spinner icon. &lt;br /&gt;
*Get side-by-side document view for discoverable attributes. &lt;br /&gt;
*Get side-by-side document view for tagged attributes upon completion of discovery. &lt;br /&gt;
&lt;br /&gt;
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727312 – Formatting based clause delineation for additional document types'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.&lt;br /&gt;
&lt;br /&gt;
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.&lt;br /&gt;
&lt;br /&gt;
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727314 – Supporting additional languages in AI apps'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.&lt;br /&gt;
&lt;br /&gt;
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''710739 – Configuring custom rules in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to Reports ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.&lt;br /&gt;
&lt;br /&gt;
With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.&lt;br /&gt;
&lt;br /&gt;
This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514611 – Enhancing Notifications History Report for an entity'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&amp;amp;nbsp; &lt;br /&gt;
*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''742607 – Supporting localization for status and business status'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Obligation Management Health Report, Obligation Management Dashboard Report.&amp;amp;nbsp; &lt;br /&gt;
*Contract type names, if the respective entity has locale resource key values in database.&amp;amp;nbsp; &lt;br /&gt;
*Status filter on all reports, drop-down with Yes/No values.&amp;amp;nbsp; &lt;br /&gt;
*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&amp;amp;nbsp; &lt;br /&gt;
*Dynamic column headers (for example, RFx Details Report in Sourcing).&amp;amp;nbsp; &lt;br /&gt;
*Any error or validation messages, informative messages such as “No data available”. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583297 – Filtering additional reports by agreement status'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Previously the &amp;quot;Agreement Status&amp;quot; filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, this filter is also available for the &amp;quot;Agreement Deviation Report&amp;quot; and &amp;quot;Agreements Pending Execution Report&amp;quot;. Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''746607 – Enhancing the Cycle Time Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The “Cycle Time Report” displays the cycles for contracts requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''737196 – Adding hyperlink in PowerBI for agreement code'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Integrations ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''605434 – Providing a unified flexible signature process'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved the electronic signature process to provide a unified flexible signature workflow.&lt;br /&gt;
&lt;br /&gt;
With this release, the following capabilities have been added to the ICI signature process:&lt;br /&gt;
&lt;br /&gt;
*Introducing the hybrid signature process. &lt;br /&gt;
*Enabling DocuSign console for users to add and modify the signatories. &lt;br /&gt;
*Support for preview in DocuSign console. &lt;br /&gt;
*Support for tagging signatories in DocuSign console. &lt;br /&gt;
*Support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''641289 – Allowing parallel signatures using DocuSign'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, DocuSign integration provided support for sequential signatures. This capability has been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can define the parallel signatories using rules. &lt;br /&gt;
*Users can configure parallel signatories via the DocuSign console. &lt;br /&gt;
*DocuSign process can be triggered in parallel for the configured signatories. &lt;br /&gt;
*Sync back, audit and history can be captured in the ICI agreement. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''701825– Supporting multiple vendors for electronic signature'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can:&lt;br /&gt;
&lt;br /&gt;
*Select the provider at the agreement or amendment level, for electronic signature and execution. This is achieved by using the choice attribute “Esignature Provider” with “DocuSign” and “Adobe Sign” as options. &lt;br /&gt;
*Define standard rules and conditions to automatically select the provider for agreements and amendments. &lt;br /&gt;
&lt;br /&gt;
'''Note: '''This is applicable to DocuSign and Adobe Sign.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any changes on the agreement document.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Document assembly is triggered automatically after every update from Salesforce. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”. &lt;br /&gt;
*Upon completion of data sync task for an opportunity, the Salesforce data sync task raises a “Data Sync Complete/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for the given opportunity. &lt;br /&gt;
*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''796155 – Improving data flow between Salesforce and ICI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when changes were made to an agreement in the &amp;quot;Sent for External Signature&amp;quot; status, the data was synced from Salesforce to the ICI UI, but not in the template document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Additionally, the agreement status changed only when an attribute which is tagged in the template was changed. However, if an attribute which was not tagged in the template changed, it was updated in the ICI UI and the status of agreement also remained the same.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&amp;amp;nbsp; &lt;br /&gt;
*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from &amp;quot;Waiting for Approval&amp;quot; or &amp;quot;Approved&amp;quot; to &amp;quot;Draft&amp;quot;; unless it is a tracking attribute.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''674469 – Sending success or failures alerts for monitoring in Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&amp;amp;nbsp; &lt;br /&gt;
*Additional logging has been introduced for ICI-Salesforce integration messages. Every message log will include the status, message Id and the incoming JSON details.&amp;amp;nbsp; &lt;br /&gt;
*Configurators also send email notifications to ICI users on forward/reverse data sync so that the recipients can take appropriate actions. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''679797 – Supporting OAuth in Salesforce adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user Id and password for authentication and authorization of production systems in an enterprise. Security organizations also had stringent security policies which do not approve user id or password authentication process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is provided for OAuth, a more secured authentication and authorization process. This makes the ICI application more secured and is easy for customers to manage using an actual business user Id, instead of a service user to update the records in ICI. It also removes any access issues involved in the business process. Customers do not have to add owners of the record to contracts team to obtain access.&lt;br /&gt;
&lt;br /&gt;
When entities in Salesforce are updated by a user, the process builder sends a message to ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
When data in Salesforce is updated and data sync job is triggered, the Salesforce adapter will use client Id and secret key from AKV to fetch a user token, for invoking Salesforce APIs, using OAuth protocol.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''749083 – Supporting OAuth in the MS CRM adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, MS CRM plugin used logged in user credentials to invoke ICI APIs when sales users updated any entity in MS CRM. Also, reverse data sync flow used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now uses the client id and secret key instead of user id and password for authentication/authorization process between Salesforce and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users will have the option to choose the authentication mechanism to be used. The system will provide the support for backward compatibility of old username and password flow.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Platform Tools ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Partner Enablement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''&amp;amp;nbsp;'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''&amp;amp;nbsp;'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Technical Requirements for Release 7.15 ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15643</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15643"/>
				<updated>2021-01-03T12:20:12Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== Overview of Release 7.15 ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Mobile App Updates ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI API Enhancements&amp;amp;nbsp; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to ICI Add-ins&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to Artificial Intelligence Applications in ICI ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &amp;amp;nbsp; &lt;br /&gt;
*View playbook details in a separate resizable window.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected contract type with options to search and filter within.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected agreement clause.&amp;amp;nbsp; &lt;br /&gt;
*Add deviation to the clause from playbook “Details” page.&amp;amp;nbsp; &lt;br /&gt;
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575475 – Automating user feedback for clauses, obligations and attributes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''539492 – Improving clause delineation in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&amp;amp;nbsp; &lt;br /&gt;
*Create a sub-clause within a discovered clause.&amp;amp;nbsp; &lt;br /&gt;
*Change the clause category and the level (parent or child) of the discovered clause. &amp;amp;nbsp; &lt;br /&gt;
*Choose to view only the level 0 clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''770375 – Merging metadata discovery page with attribute page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the discovery completion progress.&amp;amp;nbsp; &lt;br /&gt;
*Identify discoverable attributes marked with the spinner icon. &lt;br /&gt;
*Get side-by-side document view for discoverable attributes. &lt;br /&gt;
*Get side-by-side document view for tagged attributes upon completion of discovery. &lt;br /&gt;
&lt;br /&gt;
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727312 – Formatting based clause delineation for additional document types'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.&lt;br /&gt;
&lt;br /&gt;
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.&lt;br /&gt;
&lt;br /&gt;
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727314 – Supporting additional languages in AI apps'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.&lt;br /&gt;
&lt;br /&gt;
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''710739 – Configuring custom rules in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to Reports ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.&lt;br /&gt;
&lt;br /&gt;
With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.&lt;br /&gt;
&lt;br /&gt;
This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514611 – Enhancing Notifications History Report for an entity'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&amp;amp;nbsp; &lt;br /&gt;
*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''742607 – Supporting localization for status and business status'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Obligation Management Health Report, Obligation Management Dashboard Report.&amp;amp;nbsp; &lt;br /&gt;
*Contract type names, if the respective entity has locale resource key values in database.&amp;amp;nbsp; &lt;br /&gt;
*Status filter on all reports, drop-down with Yes/No values.&amp;amp;nbsp; &lt;br /&gt;
*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&amp;amp;nbsp; &lt;br /&gt;
*Dynamic column headers (for example, RFx Details Report in Sourcing).&amp;amp;nbsp; &lt;br /&gt;
*Any error or validation messages, informative messages such as “No data available”. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583297 – Filtering additional reports by agreement status'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Previously the &amp;quot;Agreement Status&amp;quot; filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, this filter is also available for the &amp;quot;Agreement Deviation Report&amp;quot; and &amp;quot;Agreements Pending Execution Report&amp;quot;. Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''746607 – Enhancing the Cycle Time Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The “Cycle Time Report” displays the cycles for contracts requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''737196 – Adding hyperlink in PowerBI for agreement code'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Integrations ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''605434 – Providing a unified flexible signature process'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved the electronic signature process to provide a unified flexible signature workflow.&lt;br /&gt;
&lt;br /&gt;
With this release, the following capabilities have been added to the ICI signature process:&lt;br /&gt;
&lt;br /&gt;
*Introducing the hybrid signature process. &lt;br /&gt;
*Enabling DocuSign console for users to add and modify the signatories. &lt;br /&gt;
*Support for preview in DocuSign console. &lt;br /&gt;
*Support for tagging signatories in DocuSign console. &lt;br /&gt;
*Support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''641289 – Allowing parallel signatures using DocuSign'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, DocuSign integration provided support for sequential signatures. This capability has been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can define the parallel signatories using rules. &lt;br /&gt;
*Users can configure parallel signatories via the DocuSign console. &lt;br /&gt;
*DocuSign process can be triggered in parallel for the configured signatories. &lt;br /&gt;
*Sync back, audit and history can be captured in the ICI agreement. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''701825– Supporting multiple vendors for electronic signature'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can:&lt;br /&gt;
&lt;br /&gt;
*Select the provider at the agreement or amendment level, for electronic signature and execution. This is achieved by using the choice attribute “Esignature Provider” with “DocuSign” and “Adobe Sign” as options. &lt;br /&gt;
*Define standard rules and conditions to automatically select the provider for agreements and amendments. &lt;br /&gt;
&lt;br /&gt;
'''Note: '''This is applicable to DocuSign and Adobe Sign.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any changes on the agreement document.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Document assembly is triggered automatically after every update from Salesforce. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”. &lt;br /&gt;
*Upon completion of data sync task for an opportunity, the Salesforce data sync task raises a “Data Sync Complete/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for the given opportunity. &lt;br /&gt;
*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''796155 – Improving data flow between Salesforce and ICI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when changes were made to an agreement in the &amp;quot;Sent for External Signature&amp;quot; status, the data was synced from Salesforce to the ICI UI, but not in the template document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Additionally, the agreement status changed only when an attribute which is tagged in the template was changed. However, if an attribute which was not tagged in the template changed, it was updated in the ICI UI and the status of agreement also remained the same.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&amp;amp;nbsp; &lt;br /&gt;
*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from &amp;quot;Waiting for Approval&amp;quot; or &amp;quot;Approved&amp;quot; to &amp;quot;Draft&amp;quot;; unless it is a tracking attribute.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''674469 – Sending success or failures alerts for monitoring in Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&amp;amp;nbsp; &lt;br /&gt;
*Additional logging has been introduced for ICI-Salesforce integration messages. Every message log will include the status, message Id and the incoming JSON details.&amp;amp;nbsp; &lt;br /&gt;
*Configurators also send email notifications to ICI users on forward/reverse data sync so that the recipients can take appropriate actions. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''679797 – Supporting OAuth in Salesforce adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user Id and password for authentication and authorization of production systems in an enterprise. Security organizations also had stringent security policies which do not approve user id or password authentication process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is provided for OAuth, a more secured authentication and authorization process. This makes the ICI application more secured and is easy for customers to manage using an actual business user Id, instead of a service user to update the records in ICI. It also removes any access issues involved in the business process. Customers do not have to add owners of the record to contracts team to obtain access.&lt;br /&gt;
&lt;br /&gt;
When entities in Salesforce are updated by a user, the process builder sends a message to ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
When data in Salesforce is updated and data sync job is triggered, the Salesforce adapter will use client Id and secret key from AKV to fetch a user token, for invoking Salesforce APIs, using OAuth protocol.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''749083 – Supporting OAuth in the MS CRM adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, MS CRM plugin used logged in user credentials to invoke ICI APIs when sales users updated any entity in MS CRM. Also, reverse data sync flow used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now uses the client id and secret key instead of user id and password for authentication/authorization process between Salesforce and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users will have the option to choose the authentication mechanism to be used. The system will provide the support for backward compatibility of old username and password flow.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Platform Tools ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Partner Enablement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''&amp;amp;nbsp;'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''&amp;amp;nbsp;'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Technical Requirements for Release 7.15 ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15642</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15642"/>
				<updated>2021-01-03T12:19:46Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== Overview of Release 7.15 ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Mobile App Updates ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI API Enhancements&amp;amp;nbsp; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to ICI Add-ins&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to Artificial Intelligence Applications in ICI ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &amp;amp;nbsp; &lt;br /&gt;
*View playbook details in a separate resizable window.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected contract type with options to search and filter within.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected agreement clause.&amp;amp;nbsp; &lt;br /&gt;
*Add deviation to the clause from playbook “Details” page.&amp;amp;nbsp; &lt;br /&gt;
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575475 – Automating user feedback for clauses, obligations and attributes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''539492 – Improving clause delineation in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&amp;amp;nbsp; &lt;br /&gt;
*Create a sub-clause within a discovered clause.&amp;amp;nbsp; &lt;br /&gt;
*Change the clause category and the level (parent or child) of the discovered clause. &amp;amp;nbsp; &lt;br /&gt;
*Choose to view only the level 0 clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''770375 – Merging metadata discovery page with attribute page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the discovery completion progress.&amp;amp;nbsp; &lt;br /&gt;
*Identify discoverable attributes marked with the spinner icon. &lt;br /&gt;
*Get side-by-side document view for discoverable attributes. &lt;br /&gt;
*Get side-by-side document view for tagged attributes upon completion of discovery. &lt;br /&gt;
&lt;br /&gt;
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727312 – Formatting based clause delineation for additional document types'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.&lt;br /&gt;
&lt;br /&gt;
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.&lt;br /&gt;
&lt;br /&gt;
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727314 – Supporting additional languages in AI apps'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.&lt;br /&gt;
&lt;br /&gt;
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''710739 – Configuring custom rules in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Enhancements to Reports ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.&lt;br /&gt;
&lt;br /&gt;
With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.&lt;br /&gt;
&lt;br /&gt;
This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514611 – Enhancing Notifications History Report for an entity'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&amp;amp;nbsp; &lt;br /&gt;
*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''742607 – Supporting localization for status and business status'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Obligation Management Health Report, Obligation Management Dashboard Report.&amp;amp;nbsp; &lt;br /&gt;
*Contract type names, if the respective entity has locale resource key values in database.&amp;amp;nbsp; &lt;br /&gt;
*Status filter on all reports, drop-down with Yes/No values.&amp;amp;nbsp; &lt;br /&gt;
*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&amp;amp;nbsp; &lt;br /&gt;
*Dynamic column headers (for example, RFx Details Report in Sourcing).&amp;amp;nbsp; &lt;br /&gt;
*Any error or validation messages, informative messages such as “No data available”. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583297 – Filtering additional reports by agreement status'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Previously the &amp;quot;Agreement Status&amp;quot; filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, this filter is also available for the &amp;quot;Agreement Deviation Report&amp;quot; and &amp;quot;Agreements Pending Execution Report&amp;quot;. Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''746607 – Enhancing the Cycle Time Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The “Cycle Time Report” displays the cycles for contracts requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''737196 – Adding hyperlink in PowerBI for agreement code'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Integrations ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''605434 – Providing a unified flexible signature process'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved the electronic signature process to provide a unified flexible signature workflow.&lt;br /&gt;
&lt;br /&gt;
With this release, the following capabilities have been added to the ICI signature process:&lt;br /&gt;
&lt;br /&gt;
*Introducing the hybrid signature process. &lt;br /&gt;
*Enabling DocuSign console for users to add and modify the signatories. &lt;br /&gt;
*Support for preview in DocuSign console. &lt;br /&gt;
*Support for tagging signatories in DocuSign console. &lt;br /&gt;
*Support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''641289 – Allowing parallel signatures using DocuSign'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, DocuSign integration provided support for sequential signatures. This capability has been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can define the parallel signatories using rules. &lt;br /&gt;
*Users can configure parallel signatories via the DocuSign console. &lt;br /&gt;
*DocuSign process can be triggered in parallel for the configured signatories. &lt;br /&gt;
*Sync back, audit and history can be captured in the ICI agreement. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''701825– Supporting multiple vendors for electronic signature'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can:&lt;br /&gt;
&lt;br /&gt;
*Select the provider at the agreement or amendment level, for electronic signature and execution. This is achieved by using the choice attribute “Esignature Provider” with “DocuSign” and “Adobe Sign” as options. &lt;br /&gt;
*Define standard rules and conditions to automatically select the provider for agreements and amendments. &lt;br /&gt;
&lt;br /&gt;
'''Note: '''This is applicable to DocuSign and Adobe Sign.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any changes on the agreement document.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Document assembly is triggered automatically after every update from Salesforce. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”. &lt;br /&gt;
*Upon completion of data sync task for an opportunity, the Salesforce data sync task raises a “Data Sync Complete/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for the given opportunity. &lt;br /&gt;
*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''796155 – Improving data flow between Salesforce and ICI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when changes were made to an agreement in the &amp;quot;Sent for External Signature&amp;quot; status, the data was synced from Salesforce to the ICI UI, but not in the template document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Additionally, the agreement status changed only when an attribute which is tagged in the template was changed. However, if an attribute which was not tagged in the template changed, it was updated in the ICI UI and the status of agreement also remained the same.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&amp;amp;nbsp; &lt;br /&gt;
*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from &amp;quot;Waiting for Approval&amp;quot; or &amp;quot;Approved&amp;quot; to &amp;quot;Draft&amp;quot;; unless it is a tracking attribute.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''674469 – Sending success or failures alerts for monitoring in Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&amp;amp;nbsp; &lt;br /&gt;
*Additional logging has been introduced for ICI-Salesforce integration messages. Every message log will include the status, message Id and the incoming JSON details.&amp;amp;nbsp; &lt;br /&gt;
*Configurators also send email notifications to ICI users on forward/reverse data sync so that the recipients can take appropriate actions. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''679797 – Supporting OAuth in Salesforce adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user Id and password for authentication and authorization of production systems in an enterprise. Security organizations also had stringent security policies which do not approve user id or password authentication process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is provided for OAuth, a more secured authentication and authorization process. This makes the ICI application more secured and is easy for customers to manage using an actual business user Id, instead of a service user to update the records in ICI. It also removes any access issues involved in the business process. Customers do not have to add owners of the record to contracts team to obtain access.&lt;br /&gt;
&lt;br /&gt;
When entities in Salesforce are updated by a user, the process builder sends a message to ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
When data in Salesforce is updated and data sync job is triggered, the Salesforce adapter will use client Id and secret key from AKV to fetch a user token, for invoking Salesforce APIs, using OAuth protocol.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''749083 – Supporting OAuth in the MS CRM adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, MS CRM plugin used logged in user credentials to invoke ICI APIs when sales users updated any entity in MS CRM. Also, reverse data sync flow used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now uses the client id and secret key instead of user id and password for authentication/authorization process between Salesforce and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users will have the option to choose the authentication mechanism to be used. The system will provide the support for backward compatibility of old username and password flow.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== ICI Platform Tools ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Partner Enablement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release.''' &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release.''' &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Technical Requirements for Release 7.15 ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15641</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15641"/>
				<updated>2021-01-03T12:17:47Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Overview of Release 7.15 ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &amp;amp;nbsp; &lt;br /&gt;
*View playbook details in a separate resizable window.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected contract type with options to search and filter within.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected agreement clause.&amp;amp;nbsp; &lt;br /&gt;
*Add deviation to the clause from playbook “Details” page.&amp;amp;nbsp; &lt;br /&gt;
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575475 – Automating user feedback for clauses, obligations and attributes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''539492 – Improving clause delineation in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&amp;amp;nbsp; &lt;br /&gt;
*Create a sub-clause within a discovered clause.&amp;amp;nbsp; &lt;br /&gt;
*Change the clause category and the level (parent or child) of the discovered clause. &amp;amp;nbsp; &lt;br /&gt;
*Choose to view only the level 0 clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''770375 – Merging metadata discovery page with attribute page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the discovery completion progress.&amp;amp;nbsp; &lt;br /&gt;
*Identify discoverable attributes marked with the spinner icon. &lt;br /&gt;
*Get side-by-side document view for discoverable attributes. &lt;br /&gt;
*Get side-by-side document view for tagged attributes upon completion of discovery. &lt;br /&gt;
&lt;br /&gt;
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727312 – Formatting based clause delineation for additional document types'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.&lt;br /&gt;
&lt;br /&gt;
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.&lt;br /&gt;
&lt;br /&gt;
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727314 – Supporting additional languages in AI apps'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.&lt;br /&gt;
&lt;br /&gt;
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''710739 – Configuring custom rules in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.&lt;br /&gt;
&lt;br /&gt;
With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.&lt;br /&gt;
&lt;br /&gt;
This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514611 – Enhancing Notifications History Report for an entity'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&amp;amp;nbsp; &lt;br /&gt;
*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''742607 – Supporting localization for status and business status'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Obligation Management Health Report, Obligation Management Dashboard Report.&amp;amp;nbsp; &lt;br /&gt;
*Contract type names, if the respective entity has locale resource key values in database.&amp;amp;nbsp; &lt;br /&gt;
*Status filter on all reports, drop-down with Yes/No values.&amp;amp;nbsp; &lt;br /&gt;
*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&amp;amp;nbsp; &lt;br /&gt;
*Dynamic column headers (for example, RFx Details Report in Sourcing).&amp;amp;nbsp; &lt;br /&gt;
*Any error or validation messages, informative messages such as “No data available”. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583297 – Filtering additional reports by agreement status'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Previously the &amp;quot;Agreement Status&amp;quot; filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, this filter is also available for the &amp;quot;Agreement Deviation Report&amp;quot; and &amp;quot;Agreements Pending Execution Report&amp;quot;. Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''746607 – Enhancing the Cycle Time Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The “Cycle Time Report” displays the cycles for contracts requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''737196 – Adding hyperlink in PowerBI for agreement code'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Integrations ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''605434 – Providing a unified flexible signature process'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved the electronic signature process to provide a unified flexible signature workflow.&lt;br /&gt;
&lt;br /&gt;
With this release, the following capabilities have been added to the ICI signature process:&lt;br /&gt;
&lt;br /&gt;
*Introducing the hybrid signature process. &lt;br /&gt;
*Enabling DocuSign console for users to add and modify the signatories. &lt;br /&gt;
*Support for preview in DocuSign console. &lt;br /&gt;
*Support for tagging signatories in DocuSign console. &lt;br /&gt;
*Support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''641289 – Allowing parallel signatures using DocuSign'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, DocuSign integration provided support for sequential signatures. This capability has been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can define the parallel signatories using rules. &lt;br /&gt;
*Users can configure parallel signatories via the DocuSign console. &lt;br /&gt;
*DocuSign process can be triggered in parallel for the configured signatories. &lt;br /&gt;
*Sync back, audit and history can be captured in the ICI agreement. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''&amp;lt;br/&amp;gt; 701825– Supporting multiple vendors for electronic signature'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can:&lt;br /&gt;
&lt;br /&gt;
*Select the provider at the agreement or amendment level, for electronic signature and execution. This is achieved by using the choice attribute “Esignature Provider” with “DocuSign” and “Adobe Sign” as options. &lt;br /&gt;
*Define standard rules and conditions to automatically select the provider for agreements and amendments. &lt;br /&gt;
&lt;br /&gt;
'''Note: '''This is applicable to DocuSign and Adobe Sign.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any changes on the agreement document.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Document assembly is triggered automatically after every update from Salesforce. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”. &lt;br /&gt;
*Upon completion of data sync task for an opportunity, the Salesforce data sync task raises a “Data Sync Complete/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for the given opportunity. &lt;br /&gt;
*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''&amp;lt;br/&amp;gt; 796155 – Improving data flow between Salesforce and ICI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when changes were made to an agreement in the &amp;quot;Sent for External Signature&amp;quot; status, the data was synced from Salesforce to the ICI UI, but not in the template document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Additionally, the agreement status changed only when an attribute which is tagged in the template was changed. However, if an attribute which was not tagged in the template changed, it was updated in the ICI UI and the status of agreement also remained the same.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&amp;amp;nbsp; &lt;br /&gt;
*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from &amp;quot;Waiting for Approval&amp;quot; or &amp;quot;Approved&amp;quot; to &amp;quot;Draft&amp;quot;; unless it is a tracking attribute.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''674469 – Sending success or failures alerts for monitoring in Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&amp;amp;nbsp; &lt;br /&gt;
*Additional logging has been introduced for ICI-Salesforce integration messages. Every message log will include the status, message Id and the incoming JSON details.&amp;amp;nbsp; &lt;br /&gt;
*Configurators also send email notifications to ICI users on forward/reverse data sync so that the recipients can take appropriate actions. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''&amp;lt;br/&amp;gt; 679797 – Supporting OAuth in Salesforce adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user Id and password for authentication and authorization of production systems in an enterprise. Security organizations also had stringent security policies which do not approve user id or password authentication process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is provided for OAuth, a more secured authentication and authorization process. This makes the ICI application more secured and is easy for customers to manage using an actual business user Id, instead of a service user to update the records in ICI. It also removes any access issues involved in the business process. Customers do not have to add owners of the record to contracts team to obtain access.&lt;br /&gt;
&lt;br /&gt;
When entities in Salesforce are updated by a user, the process builder sends a message to ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
When data in Salesforce is updated and data sync job is triggered, the Salesforce adapter will use client Id and secret key from AKV to fetch a user token, for invoking Salesforce APIs, using OAuth protocol.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''749083 – Supporting OAuth in the MS CRM adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, MS CRM plugin used logged in user credentials to invoke ICI APIs when sales users updated any entity in MS CRM. Also, reverse data sync flow used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now uses the client id and secret key instead of user id and password for authentication/authorization process between Salesforce and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users will have the option to choose the authentication mechanism to be used. The system will provide the support for backward compatibility of old username and password flow.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15640</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15640"/>
				<updated>2021-01-03T12:17:27Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &amp;amp;nbsp; &lt;br /&gt;
*View playbook details in a separate resizable window.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected contract type with options to search and filter within.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected agreement clause.&amp;amp;nbsp; &lt;br /&gt;
*Add deviation to the clause from playbook “Details” page.&amp;amp;nbsp; &lt;br /&gt;
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575475 – Automating user feedback for clauses, obligations and attributes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''539492 – Improving clause delineation in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&amp;amp;nbsp; &lt;br /&gt;
*Create a sub-clause within a discovered clause.&amp;amp;nbsp; &lt;br /&gt;
*Change the clause category and the level (parent or child) of the discovered clause. &amp;amp;nbsp; &lt;br /&gt;
*Choose to view only the level 0 clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''770375 – Merging metadata discovery page with attribute page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the discovery completion progress.&amp;amp;nbsp; &lt;br /&gt;
*Identify discoverable attributes marked with the spinner icon. &lt;br /&gt;
*Get side-by-side document view for discoverable attributes. &lt;br /&gt;
*Get side-by-side document view for tagged attributes upon completion of discovery. &lt;br /&gt;
&lt;br /&gt;
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727312 – Formatting based clause delineation for additional document types'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.&lt;br /&gt;
&lt;br /&gt;
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.&lt;br /&gt;
&lt;br /&gt;
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727314 – Supporting additional languages in AI apps'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.&lt;br /&gt;
&lt;br /&gt;
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''710739 – Configuring custom rules in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.&lt;br /&gt;
&lt;br /&gt;
With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.&lt;br /&gt;
&lt;br /&gt;
This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514611 – Enhancing Notifications History Report for an entity'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&amp;amp;nbsp; &lt;br /&gt;
*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''742607 – Supporting localization for status and business status'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Obligation Management Health Report, Obligation Management Dashboard Report.&amp;amp;nbsp; &lt;br /&gt;
*Contract type names, if the respective entity has locale resource key values in database.&amp;amp;nbsp; &lt;br /&gt;
*Status filter on all reports, drop-down with Yes/No values.&amp;amp;nbsp; &lt;br /&gt;
*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&amp;amp;nbsp; &lt;br /&gt;
*Dynamic column headers (for example, RFx Details Report in Sourcing).&amp;amp;nbsp; &lt;br /&gt;
*Any error or validation messages, informative messages such as “No data available”. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583297 – Filtering additional reports by agreement status'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Previously the &amp;quot;Agreement Status&amp;quot; filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, this filter is also available for the &amp;quot;Agreement Deviation Report&amp;quot; and &amp;quot;Agreements Pending Execution Report&amp;quot;. Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''746607 – Enhancing the Cycle Time Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The “Cycle Time Report” displays the cycles for contracts requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''737196 – Adding hyperlink in PowerBI for agreement code'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Integrations ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''605434 – Providing a unified flexible signature process'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved the electronic signature process to provide a unified flexible signature workflow.&lt;br /&gt;
&lt;br /&gt;
With this release, the following capabilities have been added to the ICI signature process:&lt;br /&gt;
&lt;br /&gt;
*Introducing the hybrid signature process. &lt;br /&gt;
*Enabling DocuSign console for users to add and modify the signatories. &lt;br /&gt;
*Support for preview in DocuSign console. &lt;br /&gt;
*Support for tagging signatories in DocuSign console. &lt;br /&gt;
*Support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''641289 – Allowing parallel signatures using DocuSign'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, DocuSign integration provided support for sequential signatures. This capability has been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can define the parallel signatories using rules. &lt;br /&gt;
*Users can configure parallel signatories via the DocuSign console. &lt;br /&gt;
*DocuSign process can be triggered in parallel for the configured signatories. &lt;br /&gt;
*Sync back, audit and history can be captured in the ICI agreement. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''&amp;lt;br/&amp;gt; 701825– Supporting multiple vendors for electronic signature'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can:&lt;br /&gt;
&lt;br /&gt;
*Select the provider at the agreement or amendment level, for electronic signature and execution. This is achieved by using the choice attribute “Esignature Provider” with “DocuSign” and “Adobe Sign” as options. &lt;br /&gt;
*Define standard rules and conditions to automatically select the provider for agreements and amendments. &lt;br /&gt;
&lt;br /&gt;
'''Note: '''This is applicable to DocuSign and Adobe Sign.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any changes on the agreement document.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Document assembly is triggered automatically after every update from Salesforce. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”. &lt;br /&gt;
*Upon completion of data sync task for an opportunity, the Salesforce data sync task raises a “Data Sync Complete/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for the given opportunity. &lt;br /&gt;
*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''&amp;lt;br/&amp;gt; 796155 – Improving data flow between Salesforce and ICI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when changes were made to an agreement in the &amp;quot;Sent for External Signature&amp;quot; status, the data was synced from Salesforce to the ICI UI, but not in the template document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Additionally, the agreement status changed only when an attribute which is tagged in the template was changed. However, if an attribute which was not tagged in the template changed, it was updated in the ICI UI and the status of agreement also remained the same.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&amp;amp;nbsp; &lt;br /&gt;
*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from &amp;quot;Waiting for Approval&amp;quot; or &amp;quot;Approved&amp;quot; to &amp;quot;Draft&amp;quot;; unless it is a tracking attribute.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''674469 – Sending success or failures alerts for monitoring in Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&amp;amp;nbsp; &lt;br /&gt;
*Additional logging has been introduced for ICI-Salesforce integration messages. Every message log will include the status, message Id and the incoming JSON details.&amp;amp;nbsp; &lt;br /&gt;
*Configurators also send email notifications to ICI users on forward/reverse data sync so that the recipients can take appropriate actions. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''&amp;lt;br/&amp;gt; 679797 – Supporting OAuth in Salesforce adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user Id and password for authentication and authorization of production systems in an enterprise. Security organizations also had stringent security policies which do not approve user id or password authentication process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is provided for OAuth, a more secured authentication and authorization process. This makes the ICI application more secured and is easy for customers to manage using an actual business user Id, instead of a service user to update the records in ICI. It also removes any access issues involved in the business process. Customers do not have to add owners of the record to contracts team to obtain access.&lt;br /&gt;
&lt;br /&gt;
When entities in Salesforce are updated by a user, the process builder sends a message to ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
When data in Salesforce is updated and data sync job is triggered, the Salesforce adapter will use client Id and secret key from AKV to fetch a user token, for invoking Salesforce APIs, using OAuth protocol.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''749083 – Supporting OAuth in the MS CRM adapter'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, MS CRM plugin used logged in user credentials to invoke ICI APIs when sales users updated any entity in MS CRM. Also, reverse data sync flow used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI now uses the client id and secret key instead of user id and password for authentication/authorization process between Salesforce and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users will have the option to choose the authentication mechanism to be used. The system will provide the support for backward compatibility of old username and password flow.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15639</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15639"/>
				<updated>2021-01-03T12:12:52Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &amp;amp;nbsp; &lt;br /&gt;
*View playbook details in a separate resizable window.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected contract type with options to search and filter within.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected agreement clause.&amp;amp;nbsp; &lt;br /&gt;
*Add deviation to the clause from playbook “Details” page.&amp;amp;nbsp; &lt;br /&gt;
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575475 – Automating user feedback for clauses, obligations and attributes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''539492 – Improving clause delineation in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&amp;amp;nbsp; &lt;br /&gt;
*Create a sub-clause within a discovered clause.&amp;amp;nbsp; &lt;br /&gt;
*Change the clause category and the level (parent or child) of the discovered clause. &amp;amp;nbsp; &lt;br /&gt;
*Choose to view only the level 0 clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''770375 – Merging metadata discovery page with attribute page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the discovery completion progress.&amp;amp;nbsp; &lt;br /&gt;
*Identify discoverable attributes marked with the spinner icon. &lt;br /&gt;
*Get side-by-side document view for discoverable attributes. &lt;br /&gt;
*Get side-by-side document view for tagged attributes upon completion of discovery. &lt;br /&gt;
&lt;br /&gt;
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727312 – Formatting based clause delineation for additional document types'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.&lt;br /&gt;
&lt;br /&gt;
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.&lt;br /&gt;
&lt;br /&gt;
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727314 – Supporting additional languages in AI apps'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.&lt;br /&gt;
&lt;br /&gt;
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''710739 – Configuring custom rules in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.&lt;br /&gt;
&lt;br /&gt;
With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.&lt;br /&gt;
&lt;br /&gt;
This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514611 – Enhancing Notifications History Report for an entity'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&amp;amp;nbsp; &lt;br /&gt;
*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''742607 – Supporting localization for status and business status'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Obligation Management Health Report, Obligation Management Dashboard Report.&amp;amp;nbsp; &lt;br /&gt;
*Contract type names, if the respective entity has locale resource key values in database.&amp;amp;nbsp; &lt;br /&gt;
*Status filter on all reports, drop-down with Yes/No values.&amp;amp;nbsp; &lt;br /&gt;
*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&amp;amp;nbsp; &lt;br /&gt;
*Dynamic column headers (for example, RFx Details Report in Sourcing).&amp;amp;nbsp; &lt;br /&gt;
*Any error or validation messages, informative messages such as “No data available”. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583297 – Filtering additional reports by agreement status'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Previously the &amp;quot;Agreement Status&amp;quot; filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, this filter is also available for the &amp;quot;Agreement Deviation Report&amp;quot; and &amp;quot;Agreements Pending Execution Report&amp;quot;. Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''746607 – Enhancing the Cycle Time Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The “Cycle Time Report” displays the cycles for contracts requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''737196 – Adding hyperlink in PowerBI for agreement code'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15638</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15638"/>
				<updated>2021-01-03T12:08:46Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &amp;amp;nbsp; &lt;br /&gt;
*View playbook details in a separate resizable window.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected contract type with options to search and filter within.&amp;amp;nbsp; &lt;br /&gt;
*View all playbook positions for a selected agreement clause.&amp;amp;nbsp; &lt;br /&gt;
*Add deviation to the clause from playbook “Details” page.&amp;amp;nbsp; &lt;br /&gt;
*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575475 – Automating user feedback for clauses, obligations and attributes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''539492 – Improving clause delineation in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&amp;amp;nbsp; &lt;br /&gt;
*Create a sub-clause within a discovered clause.&amp;amp;nbsp; &lt;br /&gt;
*Change the clause category and the level (parent or child) of the discovered clause. &amp;amp;nbsp; &lt;br /&gt;
*Choose to view only the level 0 clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''770375 – Merging metadata discovery page with attribute page'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the discovery completion progress.&amp;amp;nbsp; &lt;br /&gt;
*Identify discoverable attributes marked with the spinner icon. &lt;br /&gt;
*Get side-by-side document view for discoverable attributes. &lt;br /&gt;
*Get side-by-side document view for tagged attributes upon completion of discovery. &lt;br /&gt;
&lt;br /&gt;
The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727312 – Formatting based clause delineation for additional document types'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.&lt;br /&gt;
&lt;br /&gt;
With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.&lt;br /&gt;
&lt;br /&gt;
Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''727314 – Supporting additional languages in AI apps'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.&lt;br /&gt;
&lt;br /&gt;
With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.&lt;br /&gt;
&lt;br /&gt;
'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''710739 – Configuring custom rules in DiscoverAI'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15637</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15637"/>
				<updated>2021-01-03T12:05:40Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''745266 – Supporting online editing of agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.&lt;br /&gt;
&lt;br /&gt;
With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.&lt;br /&gt;
&lt;br /&gt;
It is now possible for:&lt;br /&gt;
&lt;br /&gt;
*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&amp;amp;nbsp; &lt;br /&gt;
*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information. &lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
*The online Word editor is available only for users with valid Office 365 subscription. &lt;br /&gt;
*Only users with edit privileges on a document can make changes to the document online. &lt;br /&gt;
*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''588686 – Tagging clause extended attributes in clause text'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI allows users to capture additional details for clauses in the extended attributes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.&lt;br /&gt;
&lt;br /&gt;
The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''668859 – Enhancing filtering and searching of clauses &amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.&lt;br /&gt;
&lt;br /&gt;
Users can now:&lt;br /&gt;
&lt;br /&gt;
*Search and filter clauses and templates based on the name or text inside the clause or template respectively. &lt;br /&gt;
*Perform free text search on clauses and templates. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''603690 – Updating templates automatically with latest clause version'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.&lt;br /&gt;
&lt;br /&gt;
To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593421 – Labeling agreement document versions as per signature copy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.&lt;br /&gt;
&lt;br /&gt;
This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15636</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15636"/>
				<updated>2021-01-03T12:03:09Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''704069 – Enhancing ICI API 2.0 implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:&lt;br /&gt;
&lt;br /&gt;
*Contract Requests &lt;br /&gt;
*Agreements &lt;br /&gt;
*Associations &lt;br /&gt;
*Amendments &lt;br /&gt;
&lt;br /&gt;
New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''756815 – Downloading associated document API'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI already supports downloading agreements.&lt;br /&gt;
&lt;br /&gt;
As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''731961 – Provisioning success or failure message for workflow operations'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.&lt;br /&gt;
&lt;br /&gt;
Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660859 – Supporting correlation Id in APIs'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To work with ICI entities, at times, multiple API calls are needed to complete an operation.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following API changes have been made to ensure that the existing implementation and code do not break:&lt;br /&gt;
&lt;br /&gt;
*Provided support for a Tracking Id header in every request for logging.&amp;amp;nbsp; &lt;br /&gt;
*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return). &lt;br /&gt;
*The called API path with query string will be logged in Kibana.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.&lt;br /&gt;
&lt;br /&gt;
This can be used for:&lt;br /&gt;
&lt;br /&gt;
*Related API Calls &lt;br /&gt;
*Async operations &lt;br /&gt;
*Bulk operations &lt;br /&gt;
*Status check operations &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15635</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15635"/>
				<updated>2021-01-03T12:00:35Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*ICI Coding Guidelines (version 2):&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Tasks: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Working with ICI Hooks:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*ICI Developer Library: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Local Environment Setup using ICI Binaries: Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*Self-Serve Tools:'''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15634</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15634"/>
				<updated>2021-01-03T11:59:03Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines (version 2)''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Tasks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Hooks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Self-Serve Tools: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15633</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15633"/>
				<updated>2021-01-03T11:58:39Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773907 – Refreshing tasks and commitments'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''850259 – Updating logo and attributes to new guidelines'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773923 – Changing compatibility in Android 11'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''773917 – Deprecating the UI WebView component for iOS'''&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; With this release, the UI WebView component for iOS has been deprecated.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines (version 2)''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Tasks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Hooks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Self-Serve Tools: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15632</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15632"/>
				<updated>2021-01-03T11:56:36Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.   &lt;br /&gt;
**'''''Icertis Experience for MS CRM''''' &lt;br /&gt;
***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&amp;amp;nbsp;     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660965 – Refresh agreement list on approval'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines (version 2)''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Tasks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Hooks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Self-Serve Tools: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15631</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15631"/>
				<updated>2021-01-03T11:50:14Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660965 – Refresh agreement list on approval'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI Platform Tools&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;514636 – Enhancing P2P Tool in ICI Admin user interface&amp;lt;/span&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.&amp;lt;br/&amp;gt; The following entities are now supported:&lt;br /&gt;
&lt;br /&gt;
*Organizations (Orgs), Organization Groups (Org Groups) &lt;br /&gt;
*Users, User Groups, Security Groups &lt;br /&gt;
*Role Action Mapping &lt;br /&gt;
*Currencies &lt;br /&gt;
*Reasons &lt;br /&gt;
*Attribute Group &lt;br /&gt;
*SLA Matrix &lt;br /&gt;
*Notification Category &lt;br /&gt;
*Default Search Columns &lt;br /&gt;
*Cascade Team &lt;br /&gt;
*Application Settings &lt;br /&gt;
*Global/Admin Saved Searches &lt;br /&gt;
&lt;br /&gt;
'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines (version 2)''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Tasks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Hooks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Self-Serve Tools: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15630</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15630"/>
				<updated>2021-01-03T11:45:33Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660965 – Refresh agreement list on approval'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines (version 2)''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases (version 2): '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Tasks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Working with ICI Hooks: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
*'''Self-Serve Tools: '''Updated for the 7.15 release. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15629</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15629"/>
				<updated>2021-01-03T11:40:58Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''User Experience''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation. &lt;br /&gt;
***Providing &amp;amp;nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally. &lt;br /&gt;
***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results. &lt;br /&gt;
***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience. &lt;br /&gt;
***Viewing amendments in the grid view by default, for ease of use. &lt;br /&gt;
***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience. &lt;br /&gt;
***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels. &lt;br /&gt;
***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.   &lt;br /&gt;
**'''''Workflow Enhancements''''' &lt;br /&gt;
***Introducing &amp;amp;nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability. &lt;br /&gt;
***Allowing &amp;amp;nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience. &lt;br /&gt;
***Viewing clause extension attributes on the agreement entity for easy reference. &lt;br /&gt;
***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles. &lt;br /&gt;
***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch. &lt;br /&gt;
***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&amp;amp;nbsp; &lt;br /&gt;
***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &amp;amp;nbsp; &lt;br /&gt;
***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable. &lt;br /&gt;
***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents. &lt;br /&gt;
***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately. &lt;br /&gt;
***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &amp;amp;nbsp; entities with one or more users, by selecting a subset of an entity &amp;amp;nbsp; or on all instances of the entity, for all records available for the user. &lt;br /&gt;
***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level. &lt;br /&gt;
***Providing the capability to control the supersede functionality for agreements by configuring rules. &lt;br /&gt;
***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios. &lt;br /&gt;
***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks. &lt;br /&gt;
***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata. &lt;br /&gt;
***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access. &lt;br /&gt;
***Supporting larger files for masterdata and associations. &lt;br /&gt;
***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results. &lt;br /&gt;
***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters. &lt;br /&gt;
***Providing the ability to configure filter on a lookup attribute &amp;amp;nbsp; with the “IN” operator on agreement contract type and template variables.&amp;amp;nbsp; &lt;br /&gt;
***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation. &lt;br /&gt;
***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates. &lt;br /&gt;
***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing &amp;amp;nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users. &lt;br /&gt;
**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments. &lt;br /&gt;
**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break. &lt;br /&gt;
**Provisioning success or failure message for workflow operations.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Icertis Experience for Word''''' &lt;br /&gt;
***Supporting &amp;amp;nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session. &lt;br /&gt;
***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries. &lt;br /&gt;
***Improving labeling of internal, external and fully signed copies of agreements for easy identification. &lt;br /&gt;
***Defining and updating clause groups as per business requirements for easy categorization and management.&amp;amp;nbsp; &lt;br /&gt;
***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses. &lt;br /&gt;
***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word. &lt;br /&gt;
**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause. &lt;br /&gt;
**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration. &lt;br /&gt;
**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries. &lt;br /&gt;
**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights. &lt;br /&gt;
**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&amp;amp;nbsp; &lt;br /&gt;
**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&amp;amp;nbsp; &lt;br /&gt;
**Improving &amp;amp;nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. &lt;br /&gt;
**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users. &lt;br /&gt;
**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&amp;amp;nbsp; &lt;br /&gt;
**Enhancing the “Clause Summary Report” to display information on extended clause attribute version. &lt;br /&gt;
**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information. &lt;br /&gt;
**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability. &lt;br /&gt;
**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI. &lt;br /&gt;
**Enhancing localization support in reports.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**'''''Signature Workflow''''' &lt;br /&gt;
***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).&amp;lt;br/&amp;gt; Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.&amp;lt;br/&amp;gt; Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &amp;amp;nbsp;   &lt;br /&gt;
**'''''Icertis Experience for Salesforce''''' &lt;br /&gt;
***Providing the ability to send success and failures alerts for improved monitoring of messages. &lt;br /&gt;
***Triggering document assembly for automatic data sync and displaying completion notification. &lt;br /&gt;
***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;font color=&amp;quot;#800080&amp;quot;&amp;gt;'''Enhancements to Platform Tools'''&amp;lt;/font&amp;gt; &lt;br /&gt;
**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660965 – Refresh agreement list on approval'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have created the following documents in this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. This will help them reduce time in development, reduce errors, maintain consistency and enhance collaboration. The document focuses primarily on the .Net framework as platform and C# as the object-oriented programming language. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library''': This document provides a detailed insight into the ICI developer methods library used for various functions and functionalities. It provides a detailed listing of all the methods in ICI development covering multiple parameters such as the summary of the functionality, dependencies, input parameters, return parameters, exceptions and code snippets on how to call the methods. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries''': This document provides guidance to Icertis partner developers on how to set up and deploy ICI on their development machines using ICI’s deployable binaries and packages. These binaries and packages are published by Icertis for every GA version.&amp;amp;nbsp;'''&amp;amp;nbsp;''' &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases: '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15628</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15628"/>
				<updated>2021-01-03T11:22:39Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15&amp;amp;nbsp;Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''''User Experience''''' &lt;br /&gt;
**Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. &lt;br /&gt;
**Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement. &lt;br /&gt;
**Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks. &lt;br /&gt;
**Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level. &lt;br /&gt;
**Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated.   &lt;br /&gt;
*'''''Workflow Enhancements''''' &lt;br /&gt;
**Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation. &lt;br /&gt;
**Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle. &lt;br /&gt;
**Providing the ability to add amendments to expired agreements. &amp;amp;nbsp; &lt;br /&gt;
**Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement. &lt;br /&gt;
**Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record.&amp;amp;nbsp;   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**''Icertis Experience for Word'' &lt;br /&gt;
***Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages. &lt;br /&gt;
***Providing extended attributes within the add-in for creation and modification of clauses and templates. &lt;br /&gt;
***Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in. &lt;br /&gt;
***Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it.   &lt;br /&gt;
**''Outlook Add-in'' &lt;br /&gt;
***Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing a legal playbook in the NegotiateAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks. &lt;br /&gt;
**Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process. &lt;br /&gt;
**Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese. &lt;br /&gt;
**Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version. &lt;br /&gt;
**Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause. &lt;br /&gt;
**Providing users the capability to generate a report as per the time zone of their choice from within the report itself.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself. &lt;br /&gt;
**Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication. &lt;br /&gt;
**Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660965 – Refresh agreement list on approval'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have created the following documents in this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. This will help them reduce time in development, reduce errors, maintain consistency and enhance collaboration. The document focuses primarily on the .Net framework as platform and C# as the object-oriented programming language. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library''': This document provides a detailed insight into the ICI developer methods library used for various functions and functionalities. It provides a detailed listing of all the methods in ICI development covering multiple parameters such as the summary of the functionality, dependencies, input parameters, return parameters, exceptions and code snippets on how to call the methods. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries''': This document provides guidance to Icertis partner developers on how to set up and deploy ICI on their development machines using ICI’s deployable binaries and packages. These binaries and packages are published by Icertis for every GA version.&amp;amp;nbsp;'''&amp;amp;nbsp;''' &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases: '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15627</id>
		<title>Release Notes</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Release_Notes&amp;diff=15627"/>
				<updated>2021-01-03T11:21:53Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICI&amp;amp;nbsp;Release Notes - Release 7.15 =&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Overview of Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The 7.15&amp;amp;nbsp;Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICI functionalities and the user interface.&lt;br /&gt;
&lt;br /&gt;
The key enhancements of this release include:&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to the ICI Application'''&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''''User Experience''''' &lt;br /&gt;
**Introducing a horizontal chevron which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron, namely Generate, Approve, Execute and Manage, prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. &lt;br /&gt;
**Allowing users to create peer agreements from within the base agreement and inheriting all the attribute values of the base agreement. &lt;br /&gt;
**Facilitating one-click navigation from the ICI record to any related entities (multi-hierarchy level). For example, from RFx to Bid Response which would otherwise require multiple clicks. &lt;br /&gt;
**Providing administrators the ability to configure access control for users who are not part of the team to sections or sub-sections in the left navigation pane at the contract type level. &lt;br /&gt;
**Enhancing document usability by placing content control tags such that the end-user no longer views separate lines in the assembled document for assembled clauses that are not evaluated.   &lt;br /&gt;
*'''''Workflow Enhancements''''' &lt;br /&gt;
**Displaying the organization unit path of the parent document by default as the path for the associated document, so that both parent and child documents have the same organization path at the time of creation and updation. &lt;br /&gt;
**Introducing a Contract Manager role to manage agreement ownership throughout its lifecycle. &lt;br /&gt;
**Providing the ability to add amendments to expired agreements. &amp;amp;nbsp; &lt;br /&gt;
**Adding a time zone attribute to provide enterprise organizations the flexibility to track the time zone or region-based activities as needed for the instance of the agreement. &lt;br /&gt;
**Providing the capability to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications and allowing configuration of the sender’s email ID dynamically based on the specific contract type or instance of the record.&amp;amp;nbsp;   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Mobile App Updates'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Improving the usability of the mobile app by refreshing the agreement or requests list automatically after an approve, reject or request review action is performed.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI API 2.0'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing some masterdata APIs that will allow business applications to interact with ICI using standard API nomenclature for masterdata.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to ICI Add-ins'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**''Icertis Experience for Word'' &lt;br /&gt;
***Displaying a set of 30 clauses per page with pagination for easy navigation between clauses listed on the clauses, clauses in templates and clauses in agreement pages. &lt;br /&gt;
***Providing extended attributes within the add-in for creation and modification of clauses and templates. &lt;br /&gt;
***Allowing the deviation approver to view and directly approve or reject clause deviations in an agreement from within the add-in. &lt;br /&gt;
***Displaying a validation message in clause content control enabling users to insert and tag clauses at the correct location in the document before publishing it.   &lt;br /&gt;
**''Outlook Add-in'' &lt;br /&gt;
***Enhancing the Outlook Add-in by providing the ability to upload email in .docx or .msg format as associated documents for an agreement from within Outlook.     &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Artificial Intelligence Applications'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing a legal playbook in the NegotiateAI app that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks. &lt;br /&gt;
**Enhancing DiscoverAI to identify the different levels within a clause through a distinct visual representation of clauses with sub-sections displayed in a delineated view during the clause discovery process. &lt;br /&gt;
**Enhancing the ICI discovery models to support clause and obligation discovery for additional languages such as German, Spanish and Portuguese. &lt;br /&gt;
**Improving the inbuilt DiscoverAI model to identify additional attributes such as City, State, Zip Code, and so on.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Enhancements to Reports'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Introducing the Risk Assessment Report which is a trendline chart report that depicts the agreement aggregate risk score by their version. ICI’s AI algorithm identifies the playbook exceptions for a new version. &lt;br /&gt;
**Introducing the Clause Summary Report to help clause administrators to understand and assess the impact of changes made to a clause. &lt;br /&gt;
**Providing users the capability to generate a report as per the time zone of their choice from within the report itself.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Improving the Icertis Experience'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**Extending support for ICI dashboard widgets in the Icertis Experience for Salesforce Home page, so that users can perform all necessary actions from within Salesforce itself. &lt;br /&gt;
**Supporting auto-renewal and reset expiry functionalities in Icertis Experience for Workday, thus saving time and avoiding data duplication. &lt;br /&gt;
**Enhancing the generic integration framework to support custom pre- and post-processing hooks to considerably reduce implementation time, and allowing users to define and configure folder structure and file names as per the business requirement.   &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''Additions to Icertis Software Development Kit for Partner Enablement'''&amp;lt;/span&amp;gt; &lt;br /&gt;
**In release 7.12, the Software Development Kit (SDK) was released to support partners for technical configuration. With this release, documentation for ICI coding guidelines, ICI developer methods, local environment setup using ICI binaries, and ICI customization and use cases are also available.   &lt;br /&gt;
&lt;br /&gt;
These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== '''&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family: GothamMedium, sans-serif; font-size: 1.4em;&amp;quot;&amp;gt;ICI Application Enhancements&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;''' ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659853 – Upfront chevron view of agreement journey'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the Team tab, and logged audit details on the History tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, a horizontal chevron has been introduced, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan.&lt;br /&gt;
&lt;br /&gt;
The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&lt;br /&gt;
&lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. It displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Generate:''' Displays the list of actions taken by the user on the agreement before it is published.&lt;br /&gt;
&lt;br /&gt;
2.'''Approve:'''&amp;amp;nbsp;Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute:&amp;amp;nbsp;'''Displays details such as internal/ external signatories that have either signed the agreement or whose signatures are pending.&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:&amp;amp;nbsp;'''Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution.&lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreement&amp;amp;nbsp;and amendment). &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512931 – Visibility of sections on the left navigation pane to non-team users'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
The administrator can configure access control for users who are not part of the team to sections/ sub-sections in the left navigation pane at the contract type level. The non-team users are generally at a higher level in the organization and may want a quick glance at the contract.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This can be achieved through a backend configuration for the non-team user role in panel mapping as required and is applicable to agreements, amendments, contract requests and association.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''659725 – Ability to easily navigate to related entities in multi-level hierarchy'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI Business Applications and Implementation teams get the flexibility to set smart link as a means of easy navigation across related entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Configurators can:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Configure a smart link across any ICI entity that defines the entity relationships. &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities. &lt;br /&gt;
&lt;br /&gt;
Users can:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid.&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/ search will also work for the right pane grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop-down and under Smart Links icon on Entity Details page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; For example, consider&amp;amp;nbsp;entities related in multi-level hierarchy as ''Agreement &amp;gt; Obligations &amp;gt; Fulfillments''. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now navigate directly from parent agreement to grand-child fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''584439 – Introducing the Contract Manager role for agreements&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the contracting process, a Contract Manager/ Owner manages or owns the agreement and is generally different from the user who has created/ initiated the agreement.&lt;br /&gt;
&lt;br /&gt;
This user who is managing the agreement might change from time to time. For example, User A may have ownership during authoring process, whereas User B might look after the agreement during the negotiation process.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hence, the Contract Manager role has been introduced to manage agreement ownership throughout the agreement lifecycle.&lt;br /&gt;
&lt;br /&gt;
With this release:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Assignment of the user against contract manager role in the team can be only achieved through event rules using the ''Add To Team&amp;amp;nbsp;''action. &lt;br /&gt;
*Only one contract manager is available inside the agreement at any given point of time. &lt;br /&gt;
*The contract manager will have provisions same as that of primary owner. &lt;br /&gt;
*The contract manager name is displayed on the agreement summary page. &lt;br /&gt;
*Agreements can be searched using the contract manager name. &lt;br /&gt;
*Managing adhoc modification for the contract manager role user will be restricted inside the agreement''Team'' tab similar to primary owner role user. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''555890 – Ability to create peer agreement from within the base agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, it was possible to create an agreement from the Create Agreement page and link it to another agreement contract type and inherit values from it.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, you can create peer agreements directly from within their associated base agreement inheriting all the attribute values of the base agreement. For example, you can create a SOW directly from the MSA. This is achieved by enabling the following flags - ''Allow Peer Creation Wizard, Allow Multiple Instances ''and ''Allow Two-Way Linkage''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''732038 – Ability to use parent’s Organization Unit path when creating associated document'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, when creating an associated document, the Organization Unit path of the logged in user gets set, irrespective of the parent agreement’s organization unit path. However, when the parent document is updated, the associated document’s organization unit path is updated to reflect the parent document’s organization path.&lt;br /&gt;
&lt;br /&gt;
With this release, during creation, the organization unit path of the parent document will be displayed by default as the organization path for the associated document, thus improving the usability.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;For example, if the organization unit path of the logged in user is /Icertis, but the path of the parent agreement is /Icertis/autoproducts, then the associated document will now display&amp;amp;nbsp;the parent entity’s path i.e. /Icertis/autoproducts. Hence, both parent and child documents will have the same organization unit path at the time of creation as well as updation.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This is applicable to the following associations:&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Import of Association (Line Item) &lt;br /&gt;
*Auto Attachment Association &lt;br /&gt;
*Obligation/ Fulfillment (Association of Association) &lt;br /&gt;
&lt;br /&gt;
The existing event rules apply for the association creation and changes made to organization path via event rules are captured in the History.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575665 – Ability to capture multiple email IDs in a single data type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, while processing agreements/ requests, email notifications were only being sent to the users who were provisioned in the ICI system.&lt;br /&gt;
&lt;br /&gt;
With this release, users will now be able to capture multiple email addresses at run time in a single attribute configured at the contract type level and send automated email notifications. With this, the business processes and requirements emails are communicated in a better way.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Capture multiple valid internal or external email addresses while working on agreements/ requests. &lt;br /&gt;
*Configure email attribute in Notification Subscriptions as To, Cc and Bcc recipients. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583186 – Ability to add amendment on expired agreement'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently in ICI, users have to revive the agreement from ''Expired ''to ''Executed ''state by resetting its expiry date and then add amendments to it.&lt;br /&gt;
&lt;br /&gt;
With this release, the process is standardized by providing the option to add amendments to expired agreements. The amendment creation for expired agreement follows the existing ICI amendment workflow. The agreement is then revived by extending its expiry date as per the amendment.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The ''Add Amendment ''action is configurable through role action mapping on the expired state of&amp;amp;nbsp;the agreement. By default, the primary owner, secondary owner and contract manager can add amendments to the expired agreements.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593928 – Ability to configure sender email ID for automated emails'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously in ICI, all automated emails were sent with one generic email ID based on the set up done for subscription under the notifications.&lt;br /&gt;
&lt;br /&gt;
With this release, the capability is provided to configure the sender’s email ID (From email address) dynamically based on the specific contract type or instance of a record.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Administrators can now:&lt;br /&gt;
&lt;br /&gt;
*Configure the sender information while setting up the subscription under ''Notifications'' using the specific user and/ or user attribute information in the agreement. &lt;br /&gt;
*Configure the email addresses for ''Reply To'' in the subscriptions setup which recipients can revert to. &lt;br /&gt;
*Send automated notifications from the configured email address with the configured ''Reply To'' user email addresses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''593938&amp;amp;nbsp;– Time Zone support for date-dependent automated processes'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, there are scheduled jobs that perform certain actions on&amp;amp;nbsp;agreements based on conditions. For example, an executed/ reviewed agreement gets expired based on the expiry date by a scheduled job. These scheduled jobs followed the Universal Time Zone (UTC) for taking actions on activities of agreement status changes.&lt;br /&gt;
&lt;br /&gt;
To satisfy the requirements of our customers worldwide, ICI now provides the flexibility for enterprise organizations to track the time zone/ region based on their regional offices or as needed by their vendors/ suppliers, etc. A time zone attribute is now provided that supports date factor which needs to be considered for the instance of an agreement.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Users can configure a time zone attribute to track activities such as expiration, termination, auto-renewal, assignment and auto-supersede (supersedable by assignment, supersedable by amendment, supersedable by termination). &lt;br /&gt;
*Based on selected time zone, day light saving constraint will be taken care of by mentioned scheduled job activities. &lt;br /&gt;
*Scheduled jobs can be run based on the time zone captured on the agreement instance or based on the default behavior to follow UTC if the time zone is not configured or not captured on the agreement instance. &lt;br /&gt;
*ICI application will take care of running scheduled jobs in different time zones which helps to consider multiple time zones used by an organization within the same ICI instance. &lt;br /&gt;
*Expiry task is enhanced so that agreements expire at end of the day based on the expiry date. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&amp;amp;nbsp;The time zone-based processing can be enabled for all contract types across&amp;amp;nbsp;ICI through a technical configuration. If time zone selection is enabled for the specific agreement at the contract type level, it then overrides the time zone at the system level.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''512930 – Triggering service bus events for all actions'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For implementation of outbound integrations, they will be listed on various event messages to performance downstream or upstream actions as per customer requirements. To do so, the missing event messages must be added for outbound integrations. Icertis integrates with customers using message bus, where they will be actively subscribing to all the events triggered by ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, subscribers will receive a notification if the agreement expiry has been reset. The subscriber will be informed about the update only when the agreement is updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following system events are published on the message bus - Reset Agreement Expiry, Peer Agreement Association Creation, Peer Agreement Association Deletion, and Confidential and Non-Confidential Actions.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''545126 – Availability of business status value in ICI event messages'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For outbound integrations to work seamlessly, the business status values along with the ICI status is required. Previously, the business status values were not available in event messages.&lt;br /&gt;
&lt;br /&gt;
With this release, the event messages will also be available on adding items in the data properties via a hook to add the key/ values. This will be fetched at the time of custom integration. This flexibility can also be extended to add other key/ values as per the business requirement.&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Mobile App Updates&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660965 – Refresh agreement list on approval'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, Icertis mobile app users perform actions on agreements/ requests such as approve, reject and request review. However, the status of the agreement/ request list did not refresh automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In our effort to consistently improve usability of the mobile app, the agreements/ requests list will now be refreshed once the action (approve, reject or request review) is performed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 release note 11.png|720px|7.14 release note 11.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;ICI API Enhancements&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''607867 – ICI API 2.0 Implementation'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, masterdata APIs have been introduced that will allow business applications to interact with ICI using standard API nomenclature for masterdata.&lt;br /&gt;
&lt;br /&gt;
Enhancements include:&lt;br /&gt;
&lt;br /&gt;
*Addition of Masterdata APIs&amp;amp;nbsp; &lt;br /&gt;
**Users can now update the masterdata instance &lt;br /&gt;
**UserName field is returned in Get Team API as part of the response.   &lt;br /&gt;
&lt;br /&gt;
*Support for hook framework in API 2.0. customization written at the model layer using hook framework will run seamlessly when invoking API 2.0 as well. &lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to ICI Add-ins&amp;amp;nbsp;&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''714872 – Improved document usability'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Earlier, ICI placed each content control in a separate paragraph line. Dynamic clauses are added inside the blank content control and they get assembled when the rule is satisfied. Content controls of dynamic clauses for which the rules are not satisfied remain as placeholders.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These placeholders show up as an extra line if the “paragraph control -is switched on. This is true for most of the legal user persona as when they review the document, they always keep this control on. This is identified as a usability concern as this is not only an issue for the customer user, but a bigger one for their customers/ suppliers as well.&lt;br /&gt;
&lt;br /&gt;
With this new functionality, now the end-user no longer views these as separate lines in the assembled document for assembled clauses that are not evaluated, thus improving the user experience and usability.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release:&amp;lt;/div&amp;gt; &lt;br /&gt;
*All the content controls are put together in a single paragraph on any line with valid content. &lt;br /&gt;
*One paragraph is added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*An empty paragraph following the clause is added if the preceding content is a clause. This will contain all the clauses that are not satisfied by the clause assembly rules. &lt;br /&gt;
*If all the content controls are together, they appear in Icertis Experience for Word as part of the main paragraph.&amp;amp;nbsp; &lt;br /&gt;
*Clauses removed in the previous version are marked as deleted in the Clause Comparison Report and the user can insert a comment when editing the document. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*Only file-based clauses are supported. &lt;br /&gt;
*Custom fonts at the content control level of the rule-based clauses are currently not supported in the template. &lt;br /&gt;
*Location-specific (such as center-justified) rule-based clauses cannot be tagged. &lt;br /&gt;
*Numbering at the template level is not supported. &lt;br /&gt;
*One paragraph will be added after the resolved clauses, so that it does not affect the deviation analysis of the previous clause. &lt;br /&gt;
*A clause with comments only will not be reassembled after the approved state unless the agreement is edited. This is handled through a technical configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660390 – Ability to show more clauses per group'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, clauses are displayed in a set of 30 clauses per page and pagination has been provided on the clauses, clauses in templates and clauses in agreement pages.&lt;br /&gt;
&lt;br /&gt;
This gives users the option to view clauses that are available in the library in sets of 30 using the previous and next action arrows.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''707652 – Availability of extended attributes for clauses and templates in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In ICI, users capture additional details for clauses and templates in the extended attributes.&lt;br /&gt;
&lt;br /&gt;
These extended attributes are now available in Icertis Experience for Word itself, thus reducing the effort for users to swap between ICI and the add-in to complete simple activities like creation or modification of clauses and templates.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''664488 – Ability to take deviation workflow actions from Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &lt;br /&gt;
Earlier, users were able to view clause deviations details within Icertis Experience for Word, but not take actions on them.&lt;br /&gt;
&lt;br /&gt;
Now, the deviation approver can not only view the deviation details, but also approve or reject them directly from the add-in instead of having to navigate to ICI to take these actions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''660383 – Validation on incorrect tagging of clauses in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Previously, depending on the cursor position in Icertis Experience for Word, a newly added clause would get added to a template/ document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Now, clause content control has been improved so that a validation message is displayed informing users that they are trying to insert a clause within an existing clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;This allows them to take corrective actions and ensure that the clause is inserted at the appropriate position to be tagged before publishing the document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''667815 – Ability to upload email as association of an agreement using Outlook Add-in'''&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Earlier, ICI provided support to directly upload files received over email as associated documents using the ICI Outlook plug-in.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, the Outlook Add-in has been further enhanced so that users can now directly upload emails as associated documents for an agreement from within Outlook.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Users can now upload the entire email conversation in .docx and .msg format to create a new instance of the associated document or to supplement an existing associated document, thereby considerably saving time and effort for contract authors.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Artificial Intelligence Applications in ICI&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''662334/716399 – Introducing AI powered Playbook in Icertis Experience for Word'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With this release, ICI is introducing a legal playbook in Icertis Experience for Word&amp;amp;nbsp;that uses artificial intelligence to identify exceptions in the contract and actions taken on them, as well as assess the risk when these exceptions are accepted by the negotiators to be able to take corrective actions and mitigate risks.&lt;br /&gt;
&lt;br /&gt;
Earlier, negotiators had to manually review each clause to find deviations or track how the negotiations have proceeded through multiple exchanges over a period of time and detect the risks of the agreement.&lt;br /&gt;
&lt;br /&gt;
Now, ICI supports digitization of the legal playbook using masterdata that allows users to define and parameterize multiple playbook positions (data types) for standard library clauses or contract types, define rules for playbook exceptions, and assign risk scores for each playbook exception.&lt;br /&gt;
&lt;br /&gt;
The exceptions are identified by the ''NegotiateAI'' app using the discovery process allowing users to review and take corrective actions. Based on the actions taken, a risk assessment is done and a risk report is then available which displays the cumulative risk scores across different versions.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Negotiators can now:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Define the structure and setup the playbook by configuring a masterdata in ICI. &lt;br /&gt;
*Define the parameters and rules to raise playbook exceptions for supported data types (number, currency, percentage and string). For example, define the range for limitation of liability and raise an exception if it is out of range. &lt;br /&gt;
*Use artificial intelligence to identify and highlight the playbook exceptions in the document. &lt;br /&gt;
*Review all discovered exceptions that are listed down on the page and take corrective actions as required. &lt;br /&gt;
*Assess the risk of each revised contract version when exceptions are accepted using risk assessment scores. &lt;br /&gt;
*Review the version-wise cumulative risk using a risk report. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;By default, the playbook is disabled and can be enabled by setting parameters in the configuration key.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575450 – Supporting clause hierarchy in .docx agreements'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract, each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&lt;br /&gt;
&lt;br /&gt;
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections, and so on.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Also, document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Currently, only well-structured .docx files are supported. Refer to the detailed recommendation in Wiki for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''663666 – Enhancing inbuilt discovery model to include additional attributes&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ICI discovery model offers inbuilt support for 14 attributes and more than 40 clauses from MSA, NDA or SoW type of agreement documents.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following 9 additional attributes has been introduced - ''City, State, Zip Code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone''.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''575466 – Support for additional languages in AI apps&amp;amp;nbsp;'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the ICI clause and obligation discovery models were primarily based on the English language.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
In this release, these discovery models have been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in the original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user-preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Enhancements to Reports&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514594 – Capability of time zone in reports'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICI reports display the date and time values based on the ''Time Zone'' selected in the ''Locale Settings'' under ''Preferences''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;With this release, a new time zone parameter has been added to the reports mentioned below, where users can select a time zone of their choice. When the report is run, the date and time information displayed in the report would be displayed as per this selected time zone.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The ''Time Zone'' parameter is applicable to the following default reports in ICI - Agreements Pending Execution Report, Agreements Pending Approval Report, Clauses Pending Approval Report, Templates Pending Approval Report, Agreement Clause Content Report, User Login Report, Signature Type Report, Cycle Time Report, Approved Requests Waiting For Contract Creation Report, Masterdata Information Report, Clause Deviations Report, Clause Summary Report and Detailed Report.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''514609 – Introducing the Clause Summary Report'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clause library maintenance is a crucial activity for any enterprise managing its contracts digitally. Administrators working with clause libraries also need to handle several recurring clause changes.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, the Clause Summary Report is being introduced in order to help clause administrators to understand the impact that changes made to a clause would have. This enables them to assess how a clause has been used across different agreements, amendments, associations and templates. Also, users can now identify which version of a clause was used in a particular entity.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
This default report is accessible from the Admin category of reports and its access is based on Security Groups.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Integrations&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''554867 – Support for ICI dashboard in Icertis Experience for Salesforce'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the previous release, we integrated ICI Task Notifications into Salesforce Tasks object, so when users logged on to the Icertis Experience for Salesforce, the standard Salesforce Home page with configurable widgets displayed ICI Tasks within Salesforce Tasks.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support has been extended to include additional ICI dashboard widgets on the Salesforce Home page, so that users can also perform those actions from within Salesforce that are typically done only through ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Salesforce users can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Manage and track the ICI Performance Metrices and My Recent Activities widgets from within the Salesforce Home page under the Home tab.&amp;amp;nbsp; &lt;br /&gt;
*View any changes made by users to these widgets in ICI using the Edit Dashboard option refected in the respective Salesforce widgets.&amp;amp;nbsp; &lt;br /&gt;
*Take actions through these widgets in Salesforce either through an iframe or by opening the ICI app in a new tab. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''583132 – Support for auto-renewal and reset expiry date in Icertis Experience for Workday'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Icertis Experience for Workday supports Create and Update events for agreements and amendments.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, users will be able to set auto-renewal and/ or reset the expiry date for a contract, when the corresponding contract type is enabled for Workday. In both cases, an amendment record with a revised expiry date gets created for the main agreement in Workday.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
These enhancements save time and avoid data duplication, as the updates made on the ICI side are also reflected in Workday.&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; '''Note''':&amp;amp;nbsp;Only one amendment can be in-process at any given time in the Workday; users need to ensure there are no amendments in progress when initiating both Auto Renewal and Reset Expiry events.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635822 – Support for pre- and post-processing in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the execution of a custom business logic was not supported in the Generic Integration Framework (GIF) while creating and updating data from an external source to ICI and vice-versa.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
With this release, support is being provided for custom pre- and post-processing hooks to GIF in order to considerably reduce implementation time. These hooks are now provided to:&lt;br /&gt;
&lt;br /&gt;
*Pre-process inbound data through file-based integrations. &lt;br /&gt;
*Pre-process inbound and outbound data through ASB-based integrations. &lt;br /&gt;
&lt;br /&gt;
ICI administrators will now be able to:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Enable or disable the hook as part of file-based and ASB integration. &lt;br /&gt;
*Pass parameters to the hook for executing a custom logic. &lt;br /&gt;
*Enable or disable the hook at file or record level. &lt;br /&gt;
**When a hook is enabled at file level, the system will process all records in the file before handing off control to the hook. &lt;br /&gt;
**When a hook is enabled at record level, system will wait for the hook to complete processing at record level before processing the next record.   &lt;br /&gt;
*Execute any custom logic in the system for a file or record when a hook is configured. &lt;br /&gt;
*Complete GIF process even when custom logic encounters any error while processing a record or file. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''635823&amp;amp;nbsp;– Support for defining folder structure in Generic Integration Framework'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Previously, the generic integration framework provided a fixed folder structure for file-based inbound masterdata integration.&lt;br /&gt;
&lt;br /&gt;
Now, support is being extended so that users will be able to define and configure the folder structure and file names depending on their business requirement. This reduces the effort during implementation while aiding better adoption of changes on the customer’s system.&lt;br /&gt;
&lt;br /&gt;
With this release, users have:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Support for single or multiple folders in the folder structure. &lt;br /&gt;
*A folder and file naming convention which is flexible and configurable via masterdata (in JSON format). &lt;br /&gt;
*Folders which are easy to configure and flexible to modify via JSON structure, whenever business needs change. &lt;br /&gt;
*A choice to use standard folders as per the requirement. If JSON structure is not added, then the ICI default folder structure will automatically be used. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Partner Enablement&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;'''703386 – Icertis Software Development Kit for Partner Enablemen'''&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''t'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide them with the resources and tools that they need while implementing ICI.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
As part of our continuous efforts to support our partners, we have created the following documents in this release:&lt;br /&gt;
&lt;br /&gt;
*'''ICI Coding Guidelines''':&amp;amp;nbsp;This document helps developers to follow specific guidelines and best practices while coding. This will help them reduce time in development, reduce errors, maintain consistency and enhance collaboration. The document focuses primarily on the .Net framework as platform and C# as the object-oriented programming language. &lt;br /&gt;
&lt;br /&gt;
*'''ICI Developer Library''': This document provides a detailed insight into the ICI developer methods library used for various functions and functionalities. It provides a detailed listing of all the methods in ICI development covering multiple parameters such as the summary of the functionality, dependencies, input parameters, return parameters, exceptions and code snippets on how to call the methods. &lt;br /&gt;
&lt;br /&gt;
*'''Local Environment Setup using ICI Binaries''': This document provides guidance to Icertis partner developers on how to set up and deploy ICI on their development machines using ICI’s deployable binaries and packages. These binaries and packages are published by Icertis for every GA version.&amp;amp;nbsp;'''&amp;amp;nbsp;''' &lt;br /&gt;
&lt;br /&gt;
*'''ICI Customization and Use Cases: '''This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;span style=&amp;quot;color:#800080;&amp;quot;&amp;gt;Technical Requirements for Release 7.15&amp;lt;/span&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 22.png|720px|7.14 release note 22.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 23.png|720px|7.14 release note 23.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 24.png|720px|7.14 release note 24.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 25.png|720px|7.14 release note 25.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:7.14 release note 26.png|720px|7.14 release note 26.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&amp;amp;nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile_App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Agreement_Details_Page&amp;diff=15615</id>
		<title>Agreement Details Page</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Agreement_Details_Page&amp;diff=15615"/>
				<updated>2020-12-03T13:23:14Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Agreement Details Page =&lt;br /&gt;
&lt;br /&gt;
You can see the current&amp;amp;nbsp;''Status ''and all the information related to the Agreement in various sections on the left navigation. You can&amp;amp;nbsp;also perform various actions depending upon your role and the state of the Agreement.&lt;br /&gt;
&lt;br /&gt;
Here are the details you can see when you click on different sections in the left pane:&lt;br /&gt;
&lt;br /&gt;
'''Agreement''': this section shows the basic information of the Agreement. It has the following sections:&lt;br /&gt;
&lt;br /&gt;
*''Summary:''&amp;amp;nbsp;displays the&amp;amp;nbsp;''Agreement Name'', the ''Status ''and the&amp;amp;nbsp;name of the&amp;amp;nbsp;Agreement creator. It also displays the ''Template Name ''and the&amp;amp;nbsp;''Template Version''&amp;amp;nbsp;used to create the Agreement. &lt;br /&gt;
*''Details:'' show the attributes of the Agreement along with the rich&amp;amp;nbsp;text area. Only the Primary Owner can edit the values of these attributes.&amp;amp;nbsp;Note, if&amp;amp;nbsp;''Primary Owner''&amp;amp;nbsp;is replaced within the&amp;amp;nbsp;''Team'', the&amp;amp;nbsp;''Primary Owner Name&amp;amp;nbsp;''and&amp;amp;nbsp;''Primary Owner Email''&amp;amp;nbsp;fields will get updated with the current&amp;amp;nbsp;information. &lt;br /&gt;
*''Preview:'' shows what the Agreement will look like if printed. If the Agreement is in ''Draft'' state, the preview only shows the attributes defined in the Agreement. If it is in ''Approved'' state, the preview also shows the actual values of the attributes.&amp;amp;nbsp;You can control the size of the document preview by resizing the browser window or print the document or export the agreement attributes to the desired format. &lt;br /&gt;
*Versions&amp;amp;nbsp;shows the various versions created for the specific Agreement. &lt;br /&gt;
*History shows the entire life cycle of the agreement till now. &lt;br /&gt;
&lt;br /&gt;
'''Note''': The&amp;amp;nbsp;''Summary'' and ''Details'' section can both contain attributes with rich text area. '''Click''' the ''View'' icon to see the details of the attribute.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Details page rich text area 7.8.png|720px|Agreement Details page rich text area 7.8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Association:'''&amp;amp;nbsp;'''Click''' ''Add''&amp;amp;nbsp;[[File:Add.PNG|RTENOTITLE]]&amp;amp;nbsp;icon to add Associated Documents''&amp;amp;nbsp;''to the Agreement.&amp;amp;nbsp;You can also add Associated Documents instances with a simple drag-and-drop action. For this, click the specific Associated Document under the ''Associations'' tab. This displays the drop zone if it is configured to be displayed. Drag-and-drop multiple files into the drop area provided. The name of the resulting Associations will display the file name.&lt;br /&gt;
&lt;br /&gt;
This option is available only for the Associated Documents which are created using the specific Associated Document Contract Type:&lt;br /&gt;
&lt;br /&gt;
*that has the&amp;amp;nbsp;''Show File Drop Zone'' field set as&amp;amp;nbsp;''Yes'', and &lt;br /&gt;
*that does not contain any mandatory fields other than ''Name''. &lt;br /&gt;
&lt;br /&gt;
Associated Documents created using this Contract Type will have this feature enabled.&lt;br /&gt;
&lt;br /&gt;
'''Deviations:'''&amp;amp;nbsp;allow you to add any changes to the Clauses. This may require the Agreement to be sent to the ''Deviation Approver''&amp;amp;nbsp;for review and approvals.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
You can add deviation approvers directly from the&amp;amp;nbsp;''Deviations&amp;amp;nbsp;''section by clicking the''&amp;amp;nbsp;Deviation Approver&amp;amp;nbsp;''icon. This eliminates the need to navigate to the&amp;amp;nbsp;''Team&amp;amp;nbsp;''tab to add the Deviation Approvers.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Deviation approver agreement details.PNG|720px|Deviation approver agreement details.PNG]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
=== Addition of action buttons on the Deviations tab ===&lt;br /&gt;
&lt;br /&gt;
The ''ApproveAll, RejectAll'' and ''ClearAll ''buttons have been added on the ''Deviations'' tab of the agreement ''Details'' page to approve, reject or clear the selected deviations respectively.&lt;br /&gt;
&lt;br /&gt;
This makes it easier for the user to take actions on multiple deviations of the agreement in one go, considerably reducing the effort of approving, rejecting or clearing each one individually.&lt;br /&gt;
&lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 1.png|720px|7.10 Addition of Action Buttons on Deviations Tab 1.png]]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Deviated Clauses ===&lt;br /&gt;
&lt;br /&gt;
To view or add deviations for clauses:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the&amp;amp;nbsp;view record icon on the ''Agreement Management'' page. The ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
2. '''Click '''the ''Deviations''&amp;amp;nbsp;tab.&lt;br /&gt;
&lt;br /&gt;
3. '''Click '''the plus icon next to ''Add Deviation'' to manually add deviations to the agreement’s clauses. The ''Add Deviation'' window opens.&lt;br /&gt;
&lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 2.png|720px|7.10 Addition of Action Buttons on Deviations Tab 2.png]]&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''To automatically add deviations, you have to download the agreement, modify the clauses and upload the agreement in ICI.&amp;amp;nbsp;To deviate a clause, the ''Deviation Analysis'' attribute should be set to ''Yes'' when creating the clause from the ''Create Clause'' page of ''Clause Management''.&amp;lt;/div&amp;gt; &lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 3.png|720px|7.10 Addition of Action Buttons on Deviations Tab 3.png]]&lt;br /&gt;
&lt;br /&gt;
*'''Click''' the search icon to select and add the deviated clause. &lt;br /&gt;
*'''Enter''' the text for the deviated clause. &lt;br /&gt;
*'''Enter''' your comments for the deviated clause. &lt;br /&gt;
*'''Click''' ''Save''. &lt;br /&gt;
&lt;br /&gt;
4. '''Click''' the plus icon next to ''Deviation Approver'' to manually add approvers for your deviated clauses.&lt;br /&gt;
&lt;br /&gt;
5. '''Click''' the ''Send for Approval'' button.&lt;br /&gt;
&lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 4.png|720px|7.10 Addition of Action Buttons on Deviations Tab 4.png]]&lt;br /&gt;
&lt;br /&gt;
*'''Click''' &amp;amp;nbsp;[[File:7.10 Addition of Action Buttons on Deviations Tab 9.png|RTENOTITLE]]&amp;amp;nbsp;to view the comments provided by other users in the team or other stakeholders. &lt;br /&gt;
*'''Click'''&amp;amp;nbsp; [[File:7.10 Addition of Action Buttons on Deviations Tab 10.png|RTENOTITLE]]&amp;amp;nbsp;to open the ''Deviation Details''&amp;amp;nbsp;window. It displays the standard clause text, the deviated clause text and the comments provided by other users. You can add your own comments too. &lt;br /&gt;
*'''Click'''&amp;amp;nbsp;&amp;amp;nbsp;[[File:7.10 Addition of Action Buttons on Deviations Tab 11.png|RTENOTITLE]]&amp;amp;nbsp;to remove a deviation. &lt;br /&gt;
&lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*Only deviations that are added manually can be removed. If deviations have been added by downloading the agreement and then uploading the agreement back to ICI, those deviations cannot be removed. &lt;br /&gt;
*Deviation approvers can also be added by defining rules from the ''Rules'' page. &lt;br /&gt;
*The Primary owner can send the reviewed agreement to&amp;amp;nbsp;the ''Deviation Approver''. As a&amp;amp;nbsp;''Deviation Approver'', you can approve or reject clauses inside the agreement if a&amp;amp;nbsp;''Deviation Approver''&amp;amp;nbsp;role is assigned to you. &lt;br /&gt;
&lt;br /&gt;
6. Clicking the ''Send for Approval'' button in Step 5 enables the ''Approve, Reject, Approve All, Reject All'' and ''Save'' ''Changes'' buttons. The ''Clear All'' button will be enabled when an action is taken on any deviated clause. Only the ''Deviation Approver'' can view these buttons.&lt;br /&gt;
&lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 5.png|720px|7.10 Addition of Action Buttons on Deviations Tab 5.png]]&lt;br /&gt;
&lt;br /&gt;
*''Approve'': '''Click''' to approve each individual clause. &lt;br /&gt;
*''Reject'': '''Click''' to reject each individual clause. &lt;br /&gt;
&lt;br /&gt;
Clicking the ''Approve'' and ''Reject'' buttons opens the ''Deviation Details''&amp;amp;nbsp;window, displaying the details of the clause. You can also put in your comments in the ''Comments'' box. You do not have to click ''Save Changes'' to save your comments; they will be saved automatically.&lt;br /&gt;
&lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 6.png|720px|7.10 Addition of Action Buttons on Deviations Tab 6.png]]&lt;br /&gt;
&lt;br /&gt;
*To approve or reject deviations in one go, click the ''Approve All'' or ''Reject All'' button. &lt;br /&gt;
&lt;br /&gt;
In the above example, as we have already selected one clause for approval and one clause for rejection, clicking ''Approve All'' or ''Reject All'' will select the remaining 2 clauses (i.e. clauses that are not already selected). You can also add a common comment for the clauses. Comments will not be saved until you click the ''Save Changes'' button.&lt;br /&gt;
&lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 7.png|720px|7.10 Addition of Action Buttons on Deviations Tab 7.png]]&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''When you have taken actions for all the deviations, the ''Approve All'' and ''Reject All'' buttons will be disabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
*''Clear All: ''Clears all selections. &lt;br /&gt;
*'''Click''' ''Save Changes ''to save your changes. &lt;br /&gt;
&lt;br /&gt;
The clauses that have been approved will have the status ''Approved, ''whereas the ones that have been rejected or no actions have been taken will have the status ''Requires Approval.''&lt;br /&gt;
[[File:7.10 Addition of Action Buttons on Deviations Tab 8.png|720px|7.10 Addition of Action Buttons on Deviations Tab 8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Amendments:'''&amp;amp;nbsp;allow&amp;amp;nbsp;you to make changes to an ''Executed'' Agreement. This section will be blank if there are no Amendments made to the Agreement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''Commitments:'''&amp;amp;nbsp;displays the Commitments that may have been manually added for the Agreement.&amp;amp;nbsp;Commitments are contractual obligations or deliverables that you may have for a particular Agreement. The&amp;amp;nbsp;Commitment functionality in ICI is used to track the action items&amp;amp;nbsp;and assign owners to each action item. ICI triggers email alerts to owners before Commitment due date as reminders. When a Commitment is actioned, the ''Commitment State'' is reflected in the ''Commitments'' tab of the Agreement. On completion of respective tasks, owners update the status of Commitment in ICI. These states are visible on the ''Agreement Details'' and the ''Compliance Management'' pages.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Details Page - Commitment States gr actions.png|720px|Agreement Details Page - Commitment States gr actions.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Details Page Categories Commitment State gr action 1.png|720px|Agreement Details Page Categories Commitment State.PNG]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;Commitments are searchable using these new states and can be localized as per user preferences. ''Search ''allows you to search the localized values and the facet ''Search ''displays unique values of the commitment state names and the appropriate count. The existing Reports also reflect these localized values.&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Agreement Clauses:'''&amp;amp;nbsp;displays the clauses that have been defined for this Agreement. These include Rule-based Clauses.&lt;br /&gt;
&lt;br /&gt;
'''Team:'''&amp;amp;nbsp;displays the members that are added to the team working on this Agreement for it's complete life cycle. '''Click''' ''Add''&amp;amp;nbsp;+ icon to [[Managing_Team_Members|add more members]].&lt;br /&gt;
&lt;br /&gt;
You can also Replace a User&amp;amp;nbsp;through ''Team'' tab.&lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&amp;amp;nbsp;displays the comments added for the Agreement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:C5-AgreementDetailPage.jpg|720px|C5-AgreementDetailPage.jpg]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The left pane on the Agreements, Requests and Associations Details pages displays the count for important sections such as Deviations, Amendments, Commitments and Notes. This makes it easy for business users to immediately identify the number of instances in these sections, without having to open each of them. If an Agreement does not have any attached entities, the count for each will be displayed as zero.&lt;br /&gt;
&lt;br /&gt;
[[File:Agreement Executed.PNG|720px|Agreement Executed.PNG]]&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
You can perform the following actions&amp;amp;nbsp;from an ''Agreement Details'' page:&lt;br /&gt;
&lt;br /&gt;
*Use Smart Links: to see any documents related to the selected Agreement. &lt;br /&gt;
*Edit:&amp;amp;nbsp;an Agreement to update any information which was either not provided or was not correct. After editing, '''click''' ''Update and Publish'' so that all the team members can view the updated Agreement. &lt;br /&gt;
*Compare the changes made between any two available&amp;amp;nbsp;Agreement Document versions.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
To&amp;amp;nbsp;view and download the redlined document of the selected agreement versions:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Compare Document'' icon. The ''Show Comparison'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.11-CompareAgreement1.png|720px|7.11-CompareAgreement1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Select''' the two versions that you want to compare.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;The Agreement document version comparison always takes place between a higher version on the right panel and a lower version on the&amp;lt;/div&amp;gt; &lt;br /&gt;
3.'''Click''' the ''View Comparison'' button. A preview of the redline version is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.11-ViewComparison.png|720px|7.11-ViewComparison.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Download Comparison'' to download the redlined version of the Agreement document in .docx format. Any deleted text appears with a strikethrough and any added text is underlined.&lt;br /&gt;
&lt;br /&gt;
*Send: the Agreement to various users within ICI. &lt;br /&gt;
*Send For Approval: sends the Agreement for approval to the assigned team. Before sending the Agreement for approval, select specific ''Associated Documents'' that need to be approved with the Agreement. This helps the Approvers to review and approve only the required&amp;amp;nbsp;''Associated Documents''&amp;amp;nbsp;instead of going through the entire&amp;amp;nbsp;list. '''Click''' ''Send For Approval. ''This opens ''Please select document(s) for approver review ''dialog box. '''Click''' ''Submit&amp;amp;nbsp;''after selecting the required ''Associated Documents''.&amp;amp;nbsp; &lt;br /&gt;
*Copy the existing Agreement. This option with be shown only if the Agreement is in the approved state. &lt;br /&gt;
*Upload Signed Copy:&amp;amp;nbsp;''Upload Signed Copy&amp;amp;nbsp;''button will be available to Contract Admin and Primary as well as Secondary Owners , so they can scan an upload an Agreement manually signed by the Internal Signatory and proceed with the Workflow. The button will be available only when the Agreement is in&amp;amp;nbsp;''Waiting for Internal Signatory&amp;amp;nbsp;''state.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement-Team-Upload Signed Copy.png|720px|Agreement-Team-Upload Signed Copy.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*Upload Document &lt;br /&gt;
*Cancel &lt;br /&gt;
*Download document. You&amp;amp;nbsp;can continue with the Agreement workflow seamlessly after a document has been downloaded. After&amp;amp;nbsp;downloading the document, you will be able to handle the: &lt;br /&gt;
**Workflow changes when a document is recalled &lt;br /&gt;
**Removal of an Agreement from Adobe Sign during recall &lt;br /&gt;
**Call back when a document is signed or rejected &lt;br /&gt;
**Workflow movement when a document is signed or rejected &lt;br /&gt;
**Confidential &lt;br /&gt;
**Download All:&amp;amp;nbsp;You can download an Agreement with all ''Associated Documents'' attached to it.   &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;[[File:Agreement DownloadAll.PNG|720px|Agreement DownloadAll.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; Follow these steps to download an Agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Click''' ''Agreement Management &amp;gt; Agreements''&amp;amp;nbsp;on the ''Home ''page''. ''The Agreements index page opens. &lt;br /&gt;
#'''Click''' ''View Record&amp;amp;nbsp;[[File:View.png|RTENOTITLE]]'' icon next to the Agreement you would like to download. &lt;br /&gt;
#'''Click''' ''Download All. ''This opens the dialog box with a message that all ''Associated Documents&amp;amp;nbsp;''with this Agreement will be downloaded. &lt;br /&gt;
#'''Click''' ''Download.''&amp;amp;nbsp;Only the&amp;amp;nbsp;Agreement will be download''.'' &lt;br /&gt;
&lt;br /&gt;
When downloading a file in ICI, users can retain the original file name for any entity when uploading it to ICI, making it easier for users to identify and manage them. This is achieved through a technical configuration.&amp;lt;br/&amp;gt; This is applicable to agreements, amendments, associations and file attributes in agreements/associations.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' The original file name cannot be retained for existing files (like those uploaded using the Own type of paper) where a user has not uploaded the file, for ICI generated files, and when&amp;amp;nbsp;users perform operations like Recall or Reject.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can download all associated documents together throughout the agreement and amendment lifecycle including the expired state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''The Administrator can control the access privileges for ''Download'' and ''Download All'' actions through ''Role Action Mapping'', ''User Groups'' and ''Security Groups ''as per ICI existing functionality. By default, only primary owner and secondary owner can download all the associations of the agreements and amendments.&amp;lt;/div&amp;gt; &lt;br /&gt;
To download all associations of the agreement in expired state:&lt;br /&gt;
&lt;br /&gt;
#'''Click''' ''Configuration'' &amp;gt; ''Agreement'' ''Management'' on the ''Home'' page. The agreement index page opens. &lt;br /&gt;
#'''Click''' ''View'' ''Record'' icon next to the agreement you want to download. For example, ''MDL Agreement''. The agreement ''Details'' page opens. &lt;br /&gt;
#'''Click''' ''Download'' ''All''. The ''Download'' window opens. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Download All 1.png|720px|7.12 Download All 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''associations you want to download.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Download All 2.png|720px|7.12 Download All 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Download All. ''The selected associations with the agreement are downloaded in a zip file on the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Download All 3.png|720px|7.12 Download All 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Reset the Expiry Date of the agreement and amendment'''&lt;br /&gt;
&lt;br /&gt;
User can reset the expiry date of the expired agreement and amendments as per the business need.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:'''&amp;amp;nbsp;The Administrator can control the access to ''Reset Expiry Date'' action through ''Role Action Mapping'', ''User Groups'' and ''Security Groups ''as per ICI existing functionality. By default, only Administrators and primary owner can reset expiry date of agreements and amendments.&amp;lt;/div&amp;gt; &lt;br /&gt;
To reset the expiry date of the agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Click''' ''Configuration'' &amp;gt; ''Agreement'' ''Management'' on the&amp;amp;nbsp;''Home ''page. The agreement index page opens. &lt;br /&gt;
#'''Click''' ''View'' ''Record'' icon next to the agreement you want to open. The agreement ''Details'' page opens. For example, ''MDL Agreement''. &lt;br /&gt;
#'''Click''' ''Reset'' ''Expiry'' ''Date''. The ''Reset Agreement Expiry Date'' window opens. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Download All 4.png|720px|7.12 Download All 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter '''the date in ''New Expiry Date ''field. For example, ''July 11, 2020''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Download All 5.png|720px|7.12 Download All 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Update''. The agreement will move back to the previous state if the expiry date is set to future date.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Download All 6.png|720px|7.12 Download All 6.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Assigning Executed Agreements:'''&amp;amp;nbsp;ICIs additional workflow state&amp;amp;nbsp;allows you to assign&amp;amp;nbsp;the executed Agreements to other parties with updated metadata, in order to fulfil obligations and responsibilities, depending on the business requirements. The assignment Agreement goes through the workflow of approval and execution processes, and then supersedes the parent Agreement attributes as configured. Thus, the parent Agreement gets assigned to the new parties on the assignment date.&lt;br /&gt;
&lt;br /&gt;
'''Terminating&amp;amp;nbsp;Executed Agreements:'''&amp;amp;nbsp;ICIs additional&amp;amp;nbsp;workflow state allows you to terminate&amp;amp;nbsp;executed Agreements.This&amp;amp;nbsp;is useful in business scenarios where an executed Agreement can be terminated only after executing a termination Agreement for it. The termination Agreement goes through the workflow of approval and execution processes, and then supersedes the parent Agreement attributes including the termination date as per the configuration. Thus, the parent agreement gets terminated on that termination date.&lt;br /&gt;
&lt;br /&gt;
'''Reports''': this section shows reports that are agreement specific and provide information that you are authorized to view. You can select filters and based on the permutation and combinations of the applied filter, the appropriate columns are displayed.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The following reports are accessible on this page:&lt;br /&gt;
&lt;br /&gt;
#Clause Deviations &lt;br /&gt;
#Association Report &lt;br /&gt;
#Attribute Value Report &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Details page reports.png|300px|Agreement Details page reports.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
An error message is displayed if no results are generated or in case an incorrect filter is applied. You should be able to export the report into Excel, CSV or PDF. You can also schedule an email to be triggered when the report is generated.&lt;br /&gt;
&lt;br /&gt;
To learn more about these reports, go to the Agreement Details Page Reports page.&lt;br /&gt;
&lt;br /&gt;
All other reports can be viewed on various tabs of the Reports tile. To view other reports, go to the Reports Overview page.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding a smart link for related entities to the left navigation pane ==&lt;br /&gt;
&lt;br /&gt;
ICI Business Applications and Implementation Teams can to set smart link as a means of easy navigation across related entities.&amp;lt;br/&amp;gt; Configurators can: &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Configure a smart link across any ICM entity that defines the entity relationships&amp;amp;nbsp; &lt;br /&gt;
*Set the configured smart link in the left navigation pane and control its access privileges using ICI standard left pane configuration capabilities &lt;br /&gt;
&lt;br /&gt;
Users can:&lt;br /&gt;
&lt;br /&gt;
*Click on the left navigation link from an agreement contract type that will render the smart link result in grid&amp;amp;nbsp; &lt;br /&gt;
*Access existing ICM grid’s capabilities such as searching, sorting, filtering or exporting results as CSV/Excel for Smart Link results &lt;br /&gt;
&lt;br /&gt;
Any changes made to the smart link configuration, will reflect in any subsequent smart link results rendered from the left navigation pane. The filter/search will also work for the right pane grid.&amp;lt;br/&amp;gt; The smart link configured for left pane through saved search settings will only be available on the left navigation pane and will not appear in the 3 dots select action drop down and under Smart links icon on Entity Details page.&lt;br /&gt;
&lt;br /&gt;
Let’s consider an example of entities related in multi-level hierarchy as Agreement &amp;gt; Obligations &amp;gt; Fulfillments. Earlier users had to navigate through obligations in order to access the child fulfillments.&amp;amp;nbsp;Users can now navigate directly from parent agreement to grandchild fulfillments using the smart link added to the agreement’s left navigation pane, thus saving number of clicks and page loads, and improving efficiency.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 multi level hierarchy 0.png|720px|7.14 multi level hierarchy 0.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Defining the relationship between entities using common attributes ===&lt;br /&gt;
&lt;br /&gt;
Users can define the relationship between any non related ICI entities using their common attributes by creating a smart link. Users can then add this link to the contract type’s left navigation pane for easy navigation to the linked entities.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The provision to configure these smart links is available on the Save Search window.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; To create a Saved Search:&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;1.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''''Search ''tile on the ''Home ''page. The ''Advanced Search ''page opens.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; [[File:7.14 multi level hierarchy 1.png|720px|7.14 multi level hierarchy 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2.&amp;amp;nbsp;&amp;amp;nbsp;'''Select '''the entity you want to create a smart link for, in the ''Please select Entities to search ''field. For example, ''Statement of Work''.&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;&amp;amp;nbsp;'''Apply '''the filters and keywords to fine tune the search result you want.&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''''Save Search'' icon. The ''Save Search ''window opens.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; [[File:7.14 multi level hierarchy 2.png|720px|7.14 multi level hierarchy 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;5.&amp;amp;nbsp;&amp;amp;nbsp;'''Enter '''a name for a ''Saved Search'' in the ''Save search as:'' field. For example, ''Statement of Work.''&amp;lt;br/&amp;gt; 6.&amp;amp;nbsp;&amp;amp;nbsp;'''Toggle '''the ''Global Search'' to ''Yes''.&amp;lt;br/&amp;gt; 7.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''''AdvancedCriteria''. The advanced criteria section expands.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; [[File:7.14 multi level hierarchy 3.png|720px|7.14 multi level hierarchy 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Toggle '''the ''Smart Link'' to ''Yes ''to set up a smart link. More fields show up to set the smart link properties.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 multi level hierarchy 4.1.png|720px|7.14 multi level hierarchy 4.1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;&amp;amp;nbsp; '''Edit''' the query for the search criteria as required in ''Edit query'' field. To edit the query, replace the text in the [] brackets in the query with “?”.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 10.&amp;amp;nbsp;'''Toggle '''the ''Smart Link for linked entities'' to ''Yes''. This creates the smart link to the selected entity in the search, in this case, entity''Statement of Work''. More fields show up to set this smart link properties.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; [[File:7.14 multi level hierarchy 5.1.png|720px|7.14 multi level hierarchy 5.1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;11.&amp;amp;nbsp;&amp;amp;nbsp;'''Toggle '''the ''Treat Statement of Work as child'' contract to ''No''. The field dynamically displays the name of the selected entity for which the smart link is being created.&amp;lt;br/&amp;gt; 12.&amp;amp;nbsp;&amp;amp;nbsp;'''Select '''the contract type in the ''Linked entity'' field. The linked entity drop-down displays all contract types available in the ICI. For example, select ''Master Services Agreement''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; This field lets you link the selected entity with any other ICI contract type if they have common attributes. In this case, attribute ''Created By''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; [[File:7.14 multi level hierarchy 6.png|720px|7.14 multi level hierarchy 6.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;13.&amp;amp;nbsp;&amp;amp;nbsp;'''Toggle '''the ''Treat Statement of Work'' ''as child contrac''t to ''Yes''. The ''Parent contracts'' field is displayed. The field displays only those contract types related as parent to the selected entity.&amp;lt;br/&amp;gt; 14.&amp;amp;nbsp;&amp;amp;nbsp;'''Select '''the contract type in the ''Parent contracts ''field. For example, select ''Statement of Work.''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; [[File:7.14 multi level hierarchy 7.png|720px|7.14 multi level hierarchy 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
15.&amp;amp;nbsp; '''Toggle '''the ''Show on left pane ''to ''Yes''. This will mark the configured smart link to be displayed on the left navigation pane of the selected contract type in the ''Linked entity'' or ''Parent contracts ''fields.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.14 multi level hierarchy 8.png|720px|7.14 multi level hierarchy 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
16.&amp;amp;nbsp;&amp;amp;nbsp;'''Toggle '''''For all contracts ''to ''Yes/No ''as required.&amp;lt;br/&amp;gt; 17.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''''Save''. The smart link&amp;amp;nbsp;is created.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The configured smart link in the saved search is then enabled on the selected contract type’s left navigation pane through technical configuration. The smart link can be added at any location on the left navigation pane on the entity details page. For Associations pane, configured smart link can be added either above or below All link, just before the individual associations links are displayed.&amp;lt;br/&amp;gt; For example, Statement of Work saved search created for Statement of Work contract type, is added as smart link to the Master Services Agreement on the left navigation pane.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 18.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''on the entity’s smart link tab. The smart link's saved search&amp;amp;nbsp;result will be displayed in the grid.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; [[File:7.14 multi level hierarchy 9.png|720px|7.14 multi level hierarchy 9.png]]&amp;lt;br/&amp;gt;  &amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:&amp;amp;nbsp;'''[[Agreement_Details_Page_Reports|Agreement Details Page Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;&amp;amp;nbsp;[[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Agreement_Management&amp;diff=15604</id>
		<title>Agreement Management</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Agreement_Management&amp;diff=15604"/>
				<updated>2020-11-23T05:27:55Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Agreement Management =&lt;br /&gt;
&lt;br /&gt;
The Agreement Management section enables you to manage all aspects of creating and editing Agreements from a single page. From this page, you can do the following tasks:&lt;br /&gt;
&lt;br /&gt;
*View and manage all your Agreements on the ''Agreements ''page. &lt;br /&gt;
*Create new Agreements on the Creating an Agreement. &lt;br /&gt;
*Search, view, and manage all your existing requests on the ''Requests'' page. &lt;br /&gt;
*Create new Requests on the ''Create Request''&amp;amp;nbsp;page. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Mgmt.PNG|720px|Agreement Mgmt]]&amp;lt;/div&amp;gt; &lt;br /&gt;
In ICI, the terms Agreement and Contract are used interchangeably and mean the same thing. In this Help, we will use the word ''Agreement''&amp;amp;nbsp;when discussing&amp;amp;nbsp;Agreements, whereas Contracts will be discussed with&amp;amp;nbsp;reference to Contract Types.&lt;br /&gt;
&lt;br /&gt;
While the actual workflow of an Agreement in ICI can be quite complex and involved, it is summarized in these five steps:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Management - Agreement Overview.png|720px|Agreement Management - Agreement Overview.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
1.&amp;amp;nbsp;'''Create Contract Request:''' When someone in your organization, such as a department manager wants to engage a vendor for certain services over a length of time, the individual can raise that request with the procurement department that can then work on that Agreement. Depending on the workflow adopted, your organization may:&lt;br /&gt;
&lt;br /&gt;
*Enforce this step so that all contracts are initiated and drafted only by one department, or &lt;br /&gt;
*Make this step completely optional, so it can be skipped by someone who is an expert at contracting and its process. &lt;br /&gt;
&lt;br /&gt;
2. '''Create Agreement:''' In this step, the primary owner or the creator of the agreement&amp;amp;nbsp;select the contract type, selects attributes and template, and verifies the details that you entered in the agreement.&amp;amp;nbsp;See Create Agreement Page for complete details.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Review Agreement: '''After the primary owner has created an internal draft of the agreement, it is published. The published draft can be sent for reviews (optional, if decided by the Primary Owner of the Agreement) .&lt;br /&gt;
&lt;br /&gt;
4. '''Approve Agreement: '''Once the Agreement is reviewed, it can be sent for approvals to the team of people that are working on this Agreement in various roles.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Execute Agreement:''' Several people can review and approve the Agreement before it is ready to be signed. After all approvals are obtained, the Agreement is sent to be signed by both the parties. With both parties signing (known as internal and external signatories in ICI), the Agreement is said to be executed&amp;amp;nbsp;and is now in force.&lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&amp;lt;br/&amp;gt; If an incorrect document was initially uploaded by a signatory, a&amp;amp;nbsp;user with the appropriate privilege can upload the correct document even after the agreement is executed.&amp;amp;nbsp;The uploaded document must be a PDF.'''&amp;amp;nbsp;'''The ''Executed''&amp;amp;nbsp;state of the Agreement remains unchanged. Only the following roles have this privilege:&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* Primary Owner&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* Secondary Owner&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* Contributor&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; If changes are required in the Agreement that is in an ''Executed'' state, the Primary Owner of the Agreement can add an Amendment. Changes may be required due to any of the following business reasons:&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* The payment terms of the Agreement have changed.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;*&amp;amp;nbsp;The Statement of Work (SOW) in the Agreement has changed.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;amp;nbsp; *&amp;amp;nbsp;The terms and conditions of the Agreement have changed due to the introduction of a new regulation.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Support Multi-party Agreements''': ICI offers full platform support for multi-party Agreements.&amp;amp;nbsp;You can now use a single system for managing all your Agreements and capture multiple other parties and divisions on an Agreement seamlessly. It allows you to search only metadata instead of searching multiple attributes, thus making it user-friendly. There is no limit on the number of parties that can be added. All parties can sign the Agreements either manually or electronically, based on the signing sequence set in ICI. It also supports parallel signatures independent of the status of either party.&lt;br /&gt;
&lt;br /&gt;
Such Agreements include Non-Disclosure Agreements, Sell Agreements or business-specific Agreements. For example, A healthcare business group needs Contract Types for managing their contracts, but the Mergers and Acquisitions department needs their own Contract Types.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;br/&amp;gt; Key capabilities of Multi-Party:&lt;br /&gt;
&lt;br /&gt;
*Captures multiple values of Attributes and/or Masterdata &lt;br /&gt;
*Tags these multiple instances in the Template &lt;br /&gt;
*Supports the signature workflow with these multiple instances of customer data &lt;br /&gt;
*Supports multiple Rules (say for approval workflow) based on the individual values selected. For example,&amp;amp;nbsp;in an Agreement, if 3 Divisions are selected, the approval process should support approvals from all 3 divisions. &lt;br /&gt;
*Supports visibility in such a one-to-many environment; For example, in the multi-division scenario, the Agreement visibility too should be enabled for multiple divisions. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Upfront chevron view of agreement journey ==&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the ''Team'' tab, and logged audit details on the ''History ''tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A horizontal chevron is displayed, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 1.png|720px|Chevron 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. For example, if the theme color as per user preferences is green, then the previous stage is displayed in a light green color, the current stage is displayed in a dark green color, and the future stages are displayed in grey color.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The chevron displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.'''Generate: '''Displays list of actions taken by the user on the agreement before it is published. It includes the 5 most recent logs of the actions taken (such as ''Agreement Copied, Agreement Published'') including details such as role of the user who performed the task, date and time of the action, and user name. The icons displayed next to the user name are similar to those in the agreement’s ''History ''log (such as green thumb icon for actions completed).&lt;br /&gt;
&lt;br /&gt;
2. '''Approve:''' Displays the list of queued approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them. The icons and information in this tab are similar to those displayed in the agreement’s ''Progress'' view.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute: '''Displays details such as internal/external signatories that have either signed the agreement or whose signatures are pending. By default, the external signatory details are displayed first. The icons and information in this tab are similar to those displayed in the agreement’s ''Progress'' view.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:''' Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution. (such as ''Agreement Terminated, Agreement Superseded''). The icons displayed next to the user name are similar to those in the agreement’s ''History ''log.&lt;br /&gt;
&lt;br /&gt;
The icons displayed on the chevron include:&lt;br /&gt;
&lt;br /&gt;
*[[File:Chevron 1 icon.png|Chevron tick mark]]&amp;amp;nbsp;-&amp;amp;nbsp;indicates stage completed &lt;br /&gt;
*[[File:Chevron clock icon.PNG|Chevron clock icon]]&amp;amp;nbsp;- indicates stage in progress &lt;br /&gt;
&lt;br /&gt;
'''Note:'''&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreements and amendments).&amp;amp;nbsp; &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Let’s consider an example of an agreement named ''Automation Basic Agreement'' and view its journey through the &amp;lt;u&amp;gt;4 stages&amp;lt;/u&amp;gt; of the chevron.&lt;br /&gt;
&lt;br /&gt;
1.'''Generate: '''Displays the following details:&lt;br /&gt;
&lt;br /&gt;
*List of 5 most recent logs of the actions taken by the user who created the agreement – e.g. ''Agreement Copied, Agreement Created, Agreement Modified, Agreement Team Member Added, ''and finally''Agreement Published''. &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
*User details – e.g. user name&amp;amp;nbsp;''Automation user1'' and user role ''Primary Owner''.&amp;amp;nbsp; &lt;br /&gt;
*Time stamp – e.g. the agreement was copied on ''8/28/2020'' at ''14:05:02''. &lt;br /&gt;
*Icons next to the user name – similar to those in the agreement’s History log, e.g. ''green thumb icon'' for actions completed. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 2.png|720px|Chevron 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Approve:''' Displays the following details:&lt;br /&gt;
&lt;br /&gt;
*List of queued approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them. The list of approvers is similar to those mentioned in the ''Team'' tab. &lt;br /&gt;
*Number of approvers required for agreement approval – e.g.''1 of 2 required''. If no approvers are added, then a message will be displayed that no approvers are added to the team and the agreement is directly approved. &lt;br /&gt;
*Approver details – e.g. approver 1 - ''AE User13'', approver 2 – ''AE User11''.&amp;amp;nbsp; &lt;br /&gt;
*Hovering over the user names opens a box displaying the user (approver) email and ''Notes'' added by the user, if any. &lt;br /&gt;
*The icons and information in this tab are similar to those displayed in the agreement’s ''Progress'' view.&amp;amp;nbsp; &lt;br /&gt;
*Approvers are queued as per the rules. For example:&amp;lt;br/&amp;gt; - Step 1: Completed i.e. ''AE User 13'' has approved the content (&amp;amp; the ''Step 1'' tab color is light green).&amp;lt;br/&amp;gt; - Step 2: In Progress i.e. Agreement is currently waiting for approval from ''AE User 11'' (&amp;amp; the ''Step 2 ''tab color is dark green).&amp;lt;br/&amp;gt; - Step 3: Not Started i.e. ''Rasika ''is in queue and the agreement will be sent to her after approval from ''AE User 11'' (&amp;amp; the Step 3 tab color is grey). &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron Approve.PNG|720px|Chevron Approve]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; 3. '''Execute: '''Displays the following details:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Internal/ external signatories that have either signed the agreement or whose signatures are pending e.g. ''Internal Signature'' by ''ami'' and ''External Signature ''by AE''User 10''. &lt;br /&gt;
*Minimum number of external and internal signatures required at each step e.g. 1 of 1 required external signature at ''Step 1 ''by external signatory ''AE User 10''.&amp;amp;nbsp; &lt;br /&gt;
*Hovering over the user names opens a box displaying the user (approver) email, with whom the agreement currently is, and for how long it has been pending with the user. &lt;br /&gt;
*By default, the external signatory details are displayed first. The icons and information in this tab are similar to those displayed in the agreement’s ''Team'' tab. If no signatories are part of the team, then a message will be displayed indicating that and the agreement will directly move to the ''Executed'' state. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 4.png|720px|Chevron 4]]&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; '''4. Manage:''' Displays the following details:&amp;lt;/div&amp;gt; &lt;br /&gt;
*The 5 most recent logs of the actions taken by the user to manage the agreement post-execution e.g. ''Agreement Downloaded, Agreement Sent For Review''.&amp;amp;nbsp; &lt;br /&gt;
*The icons displayed next to the user name are similar to those in the agreement’s ''History'' log. &lt;br /&gt;
*User details – e.g. user name ''Automation user1'' and user role ''Primary Owner''.&amp;amp;nbsp; &lt;br /&gt;
*Time stamp – e.g. the agreement was copied on ''8/28/2020 ''at ''14:08:09''. &lt;br /&gt;
*Icons next to the user name – similar to those in the agreement’s ''History ''log, e.g. ''green thumb icon ''for actions completed. &lt;br /&gt;
*The ''clock icon'' on the ''Manage ''tab indicates the stage that is in progress e.g. the user has to take actions on the agreement and is currently in the ''Agreement Sent For Review ''state, whereas the tick mark icon on the ''Generate, Approve ''and''Execute ''tabs indicate that these stages of the agreement’s journey are complete.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 5.png|720px|Chevron 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Contract Lifecycle Management, Artificial Intelligence, and Bulk Upload ==&lt;br /&gt;
&lt;br /&gt;
For organizations looking to optimize their contract lifecycle management processes and digital transformation, this release includes capabilities to manage the bulk upload of larger volumes of legacy contracts, and Artificial Intelligence (AI) driven enhancements to improve discovery, identification, and digitization of third-party, legacy and federal contracts.&lt;br /&gt;
&lt;br /&gt;
Using ICI, you have the:&lt;br /&gt;
&lt;br /&gt;
*Ability to create US Federal Acquisition Regulations clause repository and to manage US Federal Contracts using ICI. &lt;br /&gt;
*Accelerate contract digitalization and management by quickly converting legacy contracts into live contracts with AI-enhanced contract digitization capabilities which also help in AI-powered clause and attribute discovery. Excel based bulk upload capability to do so at scale. &lt;br /&gt;
*Upload&amp;amp;nbsp;legacy Agreements in bulk supporting a larger volume of agreements and other entities using Excel utility. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;related_topics&amp;quot;&amp;gt;'''Related Topics:'''&amp;amp;nbsp;[[Searching_agreements_and_requests|Searching Agreements and Requests]]&amp;amp;nbsp;| [[Adding_Supporting_Documents_to_an_Agreement|Adding Supporting Documents to an Agreement]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Setting_auto-expiry_for_an_Agreement|Setting auto-expiry for an Agreement]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Bulk_Actions|Bulk Actions]]&amp;amp;nbsp;| [[User_Administration|User Administration]] | [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15496</id>
		<title>Outlook Add-in</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15496"/>
				<updated>2020-09-30T14:06:40Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Outlook Add-in =&lt;br /&gt;
&lt;br /&gt;
A&amp;amp;nbsp;.JS version of the ICI Outlook Plugin is available in ICI. The overall turnaround time for the author is reduced as he no longer needs to download the documents received over email to the local machine, then switch applications and log in to ICI, search the Agreement and then upload the documents.&amp;lt;br/&amp;gt; The provisioned user can now:&lt;br /&gt;
&lt;br /&gt;
*Upload the next version of the Agreement document received over an Email to the Agreement &lt;br /&gt;
*Upload the next version of the Associated document (supporting Attachments) received over an Email to the Agreement &lt;br /&gt;
*Create a new Association instance and then upload the Associated Document received over an Email to the Agreement &lt;br /&gt;
&lt;br /&gt;
The configuration of the Outlook Add-in is driven by the Masterdata, whereas the list of Agreements and their details are configured by the Saved Searches. You can configure multiple saved searches.&lt;br /&gt;
&lt;br /&gt;
The Outlook Add-in (.JS version) is supported on 2 different platforms:&lt;br /&gt;
&lt;br /&gt;
*For MAC OS (Mojave): it is tested and verified on Microsoft Office 365 (2016 and above). &lt;br /&gt;
*For Windows 10: it is tested and verified on Microsoft Office Professional Plus 2013 (15.0.5007.1000) and 2016 (16.0.4849.1000) 64-bit and above. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Uploading the next version of an Agreement received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To add the the next version of the Agreement received over Outlook Email:&amp;lt;br/&amp;gt; 1. '''Open''' the Email with the next version of the Agreement.&amp;lt;br/&amp;gt; 2. '''Open''' the ICI Outlook Add-in.&amp;lt;br/&amp;gt; 3. On the ''Details ''tab, '''click '''''Select ICI Agreement / Association'' to look for the Agreement that you&amp;amp;nbsp;want to upload as the next version.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 1.png|820px|Email Outlook Plugin 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed. If the Agreement fails to be attached, then a message will be displayed indicating that you can retry sending the Attachment.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 2.png|820px|Email Outlook Plugin 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can&amp;amp;nbsp;''Preview'' the Agreement in the ICI application&amp;amp;nbsp;on the Agreement ''Details ''page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 03.png|720px|Email Outlook Plugin 03.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding the next version of the Associated Document received over MS Outlook Email to the Agreement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; To add the next version of the&amp;amp;nbsp;Associated Document received over Outlook Email to the Agreement&amp;amp;nbsp;:&amp;lt;br/&amp;gt; 1. '''Open '''the Email with the Associated Documents.&amp;lt;br/&amp;gt; 2. '''Open '''the ICI Outlook Add-in.&lt;br /&gt;
&lt;br /&gt;
3. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association'' to add the next version of the Association.&amp;amp;nbsp;For example, ''Payment Details''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 4.png|820px|Email Outlook Plugin 4]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 5 gr actions.png|820px|Email Outlook Plugin 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click''' the ''View Record'' icon to view the Attachment details.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 6.png|820px|Email Outlook Plugin 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click '''the&amp;amp;nbsp;''Preview'' icon to view the Attachment.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 7.png|820px|Email Outlook Plugin 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Creating a new instance of an Association and adding an Associated Document received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To create a new instance of an Association and add the Associated Document received over Outlook Email to the Agreement:&amp;lt;br/&amp;gt; 1. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association ''to create a new instance of the&amp;amp;nbsp;Association. For example, adding an Association to the''Payment Details A''ssociation.&amp;lt;br/&amp;gt; 2. Enter a name for the new instance of the Association.&amp;lt;br/&amp;gt; 3. '''Click''' the ''Add Association'' button to add the new instance of the Association.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 8.png|820px|Email Outlook Plugin 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 4. '''Click '''the ''Select Email Attachment'' field to select the document that you want to attach to the newly created instance.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 9.png|820px|Email Outlook Plugin 9]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 5.'''Click''' ''Upload''. The document is now attached to the newly created instance. The ''File(s) uploaded successfully'' message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''The Association is only created with the name. The remaining mandatory fields need to be entered in the ICI application.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 10.png|820px|Email Outlook Plugin 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. The document is now available on the ''Associations'' tab in the ICI application as the next version.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Adding an email as an associated document to an existing association ==&lt;br /&gt;
&lt;br /&gt;
To upload an email conversation by creating a new instance of association in .docx and .msg formats:&lt;br /&gt;
&lt;br /&gt;
1. On the Agreement Details page of the Outlook add-in, '''click '''on the association instance, for example Supplier Communication.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2. '''Click '''''Add Association''. A text field is displayed.&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Enter '''a name for the new associated document, for example PriceList for August 2020.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''the plus icon next to the text field. The association instance gets created and it appears as an option in the ''Select ICM Agreement/Association'' drop-down.&lt;br /&gt;
&lt;br /&gt;
5. In the ''Select ICM Agreement/Association'' drop-down '''select '''the association created in Step 4.&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''the ''Select Email Attachment'' drop down. The following options are displayed:&lt;br /&gt;
&lt;br /&gt;
*''Email as Outlook format (.msg)'': Use this option to upload the email thread to the association as is. &lt;br /&gt;
*''Email as document (.docx)'': Use this option to upload the email thread to the association as a Word document. &lt;br /&gt;
&lt;br /&gt;
7. '''Select''', for example, Email as document. The selected file name is displayed in the ''Mapping Result(s)'' section.&lt;br /&gt;
&lt;br /&gt;
8. '''Click '''''Upload''. The selected email gets uploaded and the ''File(s) uploaded successfully'' message is displayed.&amp;lt;br/&amp;gt; The uploaded email appears in .docx format on ICM Web and is displayed as an Association instance against the PriceList association.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
9. On the agreement ''Details'' page, '''click''' the ''Association'' tab. In this example ''Supplier Communication'' is the association for the agreement. The associated document ''PriceList for August 2020'' uploaded using the Outlook add-in is displayed in the list of instances.&lt;br /&gt;
&lt;br /&gt;
10. '''Click '''the ''View ''icon for the created associated document instance ''PriceList for August 2020''. The associated document ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
11. '''Click '''the ''Versions ''tab. The uploaded email thread is displayed and is available to download in PDF and in Word formats.&lt;br /&gt;
&lt;br /&gt;
12. '''Click '''an icon below the ''Document ''column, for example Word icon. A .docx file will be downloaded.&lt;br /&gt;
&lt;br /&gt;
'''Note''': If you have selected the option to upload ''Email as Outlook format'', the email thread is indicated with an Outlook Message icon in Step 11, clicking which downloads the email thread in .msg format in Step 12.&lt;br /&gt;
&lt;br /&gt;
13. Open the downloaded file. The uploaded email thread content will be displayed in the file contents. In this example, the .docx file displays the email uploaded as an association.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding an email as a new version of an associated document using Outlook Add-in ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Select ICM Agreement / Association'' on the ''Details ''tab on the Outlook add-in. A drop down is displayed.&lt;br /&gt;
&lt;br /&gt;
2. '''Select''' the Association instance for which you want to add the current email as an association attachment (for example, ''PriceList for August 2020'').&lt;br /&gt;
&lt;br /&gt;
3. '''Click '''''Upload''. The File(s) uploaded successfully message will be displayed.&lt;br /&gt;
&lt;br /&gt;
The uploaded email (in .docx or in .msg format) gets uploaded on ICM Web as a version of the Association selected in Step 2, and is displayed as an Association instance against the ''PriceList'' association.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;'''Related Topics:''' [[Agreement_Management|Agreement Management]] | [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] |&amp;amp;nbsp;[[Clause_Management|Clause Management]] | [[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]] |&amp;amp;nbsp;[[Power_BI_Integration_with_ICM|Advanced Analytics]]&amp;amp;nbsp;|&amp;amp;nbsp;[[User_Administration|User Administration]]&amp;amp;nbsp;| [[ICI_Add-ins|ICI Add-ins]]&amp;amp;nbsp;| &amp;amp;nbsp;[http://int-wiki.cloudapp.net:8085/ICMHelp7.12/index.php?title=Icertis_Experience_for_Word Icertis Experience for Word] |&amp;amp;nbsp;[[Release_Notes|Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15454</id>
		<title>Outlook Add-in</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15454"/>
				<updated>2020-09-30T11:40:06Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Outlook Add-in =&lt;br /&gt;
&lt;br /&gt;
A&amp;amp;nbsp;.JS version of the ICI Outlook Plugin is available in ICI. The overall turnaround time for the author is reduced as he no longer needs to download the documents received over email to the local machine, then switch applications and log in to ICI, search the Agreement and then upload the documents.&amp;lt;br/&amp;gt; The provisioned user can now:&lt;br /&gt;
&lt;br /&gt;
*Upload the next version of the Agreement document received over an Email to the Agreement &lt;br /&gt;
*Upload the next version of the Associated document (supporting Attachments) received over an Email to the Agreement &lt;br /&gt;
*Create a new Association instance and then upload the Associated Document received over an Email to the Agreement &lt;br /&gt;
&lt;br /&gt;
The configuration of the Outlook Add-in is driven by the Masterdata, whereas the list of Agreements and their details are configured by the Saved Searches. You can configure multiple saved searches.&lt;br /&gt;
&lt;br /&gt;
The Outlook Add-in (.JS version) is supported on 2 different platforms:&lt;br /&gt;
&lt;br /&gt;
*For MAC OS (Mojave): it is tested and verified on Microsoft Office 365 (2016 and above). &lt;br /&gt;
*For Windows 10: it is tested and verified on Microsoft Office Professional Plus 2013 (15.0.5007.1000) and 2016 (16.0.4849.1000) 64-bit and above. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Uploading the next version of an Agreement received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To add the the next version of the Agreement received over Outlook Email:&amp;lt;br/&amp;gt; 1. '''Open''' the Email with the next version of the Agreement.&amp;lt;br/&amp;gt; 2. '''Open''' the ICI Outlook Add-in.&amp;lt;br/&amp;gt; 3. On the ''Details ''tab, '''click '''''Select ICI Agreement / Association'' to look for the Agreement that you&amp;amp;nbsp;want to upload as the next version.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 1.png|820px|Email Outlook Plugin 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed. If the Agreement fails to be attached, then a message will be displayed indicating that you can retry sending the Attachment.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 2.png|820px|Email Outlook Plugin 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can&amp;amp;nbsp;''Preview'' the Agreement in the ICI application&amp;amp;nbsp;on the Agreement ''Details ''page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 03.png|720px|Email Outlook Plugin 03.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding the next version of the Associated Document received over MS Outlook Email to the Agreement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; To add the next version of the&amp;amp;nbsp;Associated Document received over Outlook Email to the Agreement&amp;amp;nbsp;:&amp;lt;br/&amp;gt; 1. '''Open '''the Email with the Associated Documents.&amp;lt;br/&amp;gt; 2. '''Open '''the ICI Outlook Add-in.&lt;br /&gt;
&lt;br /&gt;
3. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association'' to add the next version of the Association.&amp;amp;nbsp;For example, ''Payment Details''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 4.png|820px|Email Outlook Plugin 4]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 5 gr actions.png|820px|Email Outlook Plugin 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click''' the ''View Record'' icon to view the Attachment details.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 6.png|820px|Email Outlook Plugin 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click '''the&amp;amp;nbsp;''Preview'' icon to view the Attachment.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 7.png|820px|Email Outlook Plugin 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Creating a new instance of an Association and adding an Associated Document received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To create a new instance of an Association and add the Associated Document received over Outlook Email to the Agreement:&amp;lt;br/&amp;gt; 1. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association ''to create a new instance of the&amp;amp;nbsp;Association. For example, adding an Association to the''Payment Details A''ssociation.&amp;lt;br/&amp;gt; 2. Enter a name for the new instance of the Association.&amp;lt;br/&amp;gt; 3. '''Click''' the ''Add Association'' button to add the new instance of the Association.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 8.png|820px|Email Outlook Plugin 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 4. '''Click '''the ''Select Email Attachment'' field to select the document that you want to attach to the newly created instance.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 9.png|820px|Email Outlook Plugin 9]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 5.'''Click''' ''Upload''. The document is now attached to the newly created instance. The ''File(s) uploaded successfully'' message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''The Association is only created with the name. The remaining mandatory fields need to be entered in the ICI application.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 10.png|820px|Email Outlook Plugin 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. The document is now available on the ''Associations'' tab in the ICI application as the next version.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding an email as an associated document to an existing association ==&lt;br /&gt;
&lt;br /&gt;
To upload an email conversation by creating a new instance of association in .docx and .msg formats:&lt;br /&gt;
&lt;br /&gt;
1. On the Agreement Details page of the Outlook add-in, '''click '''on the association instance, for example Supplier Communication.&lt;br /&gt;
&lt;br /&gt;
2. '''Click '''''Add Association''. A text field is displayed.&lt;br /&gt;
&lt;br /&gt;
3. '''Enter '''a name for the new associated document, for example PriceList for August 2020.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''the plus icon next to the text field. The association instance gets created and it appears as an option in the ''Select ICM Agreement/Association'' drop-down.&lt;br /&gt;
&lt;br /&gt;
5. In the ''Select ICM Agreement/Association'' drop-down '''select '''the association created in Step 4.&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''the ''Select Email Attachment'' drop down. The following options are displayed:&lt;br /&gt;
&lt;br /&gt;
*''Email as Outlook format (.msg)'': Use this option to upload the email thread to the association as is. &lt;br /&gt;
*''Email as document (.docx)'': Use this option to upload the email thread to the association as a Word document. &lt;br /&gt;
&lt;br /&gt;
7. '''Select''', for example, Email as document. The selected file name is displayed in the ''Mapping Result(s)'' section.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;The capability to embed the attachments in the email thread into in the .docx file is currently not supported. Selecting the ''Email as document'' option only uploads the text content and not any attachments.&amp;lt;/div&amp;gt; &lt;br /&gt;
You can delete the selected email by '''clicking '''the ''Delete ''icon.&lt;br /&gt;
&lt;br /&gt;
8. '''Click '''''Upload''. The selected email gets uploaded and the ''File(s) uploaded successfully'' message is displayed.&amp;lt;br/&amp;gt; The uploaded email appears in .docx format on ICM Web and is displayed as an Association instance against the PriceList association.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
9. On the agreement ''Details'' page, '''click''' the ''Association'' tab. In this example ''Supplier Communication'' is the association for the agreement. The associated document ''PriceList for August 2020'' uploaded using the Outlook add-in is displayed in the list of instances.&lt;br /&gt;
&lt;br /&gt;
10. '''Click '''the ''View ''icon for the created associated document instance ''PriceList for August 2020''. The associated document ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
11. '''Click '''the ''Versions ''tab. The uploaded email thread is displayed and is available to download in PDF and in Word formats.&lt;br /&gt;
&lt;br /&gt;
12. '''Click '''an icon below the ''Document ''column, for example Word icon. A .docx file will be downloaded.&lt;br /&gt;
&lt;br /&gt;
'''Note''': If you have selected the option to upload ''Email as Outlook format'', the email thread is indicated with an Outlook Message icon in Step 11, clicking which downloads the email thread in .msg format in Step 12.&lt;br /&gt;
&lt;br /&gt;
13. Open the downloaded file. The uploaded email thread content will be displayed in the file contents. In this example, the .docx file displays the email uploaded as an association.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding an email as a new version of an associated document using Outlook Add-in ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Select ICM Agreement / Association'' on the ''Details ''tab on the Outlook add-in. A drop down is displayed.&lt;br /&gt;
&lt;br /&gt;
2. '''Select''' the Association instance for which you want to add the current email as an association attachment (for example, ''PriceList for August 2020'').&lt;br /&gt;
&lt;br /&gt;
3. '''Click '''''Upload''. The File(s) uploaded successfully message will be displayed.&lt;br /&gt;
&lt;br /&gt;
The uploaded email (in .docx or in .msg format) gets uploaded on ICM Web as a version of the Association selected in Step 2, and is displayed as an Association instance against the ''PriceList'' association.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;'''Related Topics:''' [[Agreement_Management|Agreement Management]] | [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] |&amp;amp;nbsp;[[Clause_Management|Clause Management]] | [[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]] |&amp;amp;nbsp;[[Power_BI_Integration_with_ICM|Advanced Analytics]]&amp;amp;nbsp;|&amp;amp;nbsp;[[User_Administration|User Administration]]&amp;amp;nbsp;| [[ICI_Add-ins|ICI Add-ins]]&amp;amp;nbsp;| &amp;amp;nbsp;[http://int-wiki.cloudapp.net:8085/ICMHelp7.12/index.php?title=Icertis_Experience_for_Word Icertis Experience for Word] |&amp;amp;nbsp;[[Release_Notes|Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15436</id>
		<title>Outlook Add-in</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15436"/>
				<updated>2020-09-30T10:52:48Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Outlook Add-in =&lt;br /&gt;
&lt;br /&gt;
A&amp;amp;nbsp;.JS version of the ICI Outlook Plugin is available in ICI. The overall turnaround time for the author is reduced as he no longer needs to download the documents received over email to the local machine, then switch applications and log in to ICI, search the Agreement and then upload the documents.&amp;lt;br/&amp;gt; The provisioned user can now:&lt;br /&gt;
&lt;br /&gt;
*Upload the next version of the Agreement document received over an Email to the Agreement &lt;br /&gt;
*Upload the next version of the Associated document (supporting Attachments) received over an Email to the Agreement &lt;br /&gt;
*Create a new Association instance and then upload the Associated Document received over an Email to the Agreement &lt;br /&gt;
&lt;br /&gt;
The configuration of the Outlook Add-in is driven by the Masterdata, whereas the list of Agreements and their details are configured by the Saved Searches. You can configure multiple saved searches.&lt;br /&gt;
&lt;br /&gt;
The Outlook Add-in (.JS version) is supported on 2 different platforms:&lt;br /&gt;
&lt;br /&gt;
*For MAC OS (Mojave): it is tested and verified on Microsoft Office 365 (2016 and above). &lt;br /&gt;
*For Windows 10: it is tested and verified on Microsoft Office Professional Plus 2013 (15.0.5007.1000) and 2016 (16.0.4849.1000) 64-bit and above. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Uploading the next version of an Agreement received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To add the the next version of the Agreement received over Outlook Email:&amp;lt;br/&amp;gt; 1. '''Open''' the Email with the next version of the Agreement.&amp;lt;br/&amp;gt; 2. '''Open''' the ICI Outlook Add-in.&amp;lt;br/&amp;gt; 3. On the ''Details ''tab, '''click '''''Select ICI Agreement / Association'' to look for the Agreement that you&amp;amp;nbsp;want to upload as the next version.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 1.png|820px|Email Outlook Plugin 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed. If the Agreement fails to be attached, then a message will be displayed indicating that you can retry sending the Attachment.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 2.png|820px|Email Outlook Plugin 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can&amp;amp;nbsp;''Preview'' the Agreement in the ICI application&amp;amp;nbsp;on the Agreement ''Details ''page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 03.png|720px|Email Outlook Plugin 03.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding the next version of the Associated Document received over MS Outlook Email to the Agreement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; To add the next version of the&amp;amp;nbsp;Associated Document received over Outlook Email to the Agreement&amp;amp;nbsp;:&amp;lt;br/&amp;gt; 1. '''Open '''the Email with the Associated Documents.&amp;lt;br/&amp;gt; 2. '''Open '''the ICI Outlook Add-in.&lt;br /&gt;
&lt;br /&gt;
3. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association'' to add the next version of the Association.&amp;amp;nbsp;For example, ''Payment Details''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 4.png|820px|Email Outlook Plugin 4]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 5 gr actions.png|820px|Email Outlook Plugin 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click''' the ''View Record'' icon to view the Attachment details.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 6.png|820px|Email Outlook Plugin 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click '''the&amp;amp;nbsp;''Preview'' icon to view the Attachment.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 7.png|820px|Email Outlook Plugin 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Creating a new instance of an Association and adding an Associated Document received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To create a new instance of an Association and add the Associated Document received over Outlook Email to the Agreement:&amp;lt;br/&amp;gt; 1. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association ''to create a new instance of the&amp;amp;nbsp;Association. For example, adding an Association to the''Payment Details A''ssociation.&amp;lt;br/&amp;gt; 2. Enter a name for the new instance of the Association.&amp;lt;br/&amp;gt; 3. '''Click''' the ''Add Association'' button to add the new instance of the Association.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 8.png|820px|Email Outlook Plugin 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 4. '''Click '''the ''Select Email Attachment'' field to select the document that you want to attach to the newly created instance.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 9.png|820px|Email Outlook Plugin 9]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 5.'''Click''' ''Upload''. The document is now attached to the newly created instance. The ''File(s) uploaded successfully'' message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''The Association is only created with the name. The remaining mandatory fields need to be entered in the ICI application.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 10.png|820px|Email Outlook Plugin 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. The document is now available on the ''Associations'' tab in the ICI application as the next version.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Adding an email as an associated document to an existing association ==&lt;br /&gt;
&lt;br /&gt;
To upload an email conversation by creating a new instance of association in .docx and .msg formats:&lt;br /&gt;
&lt;br /&gt;
1. On the Agreement Details page of the Outlook add-in, '''click '''on the association instance, for example Supplier Communication.&lt;br /&gt;
&lt;br /&gt;
2. '''Click '''''Add Association''. A text field is displayed.&lt;br /&gt;
&lt;br /&gt;
3. '''Enter '''a name for the new associated document, for example PriceList for August 2020.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''the plus icon next to the text field. The association instance gets created and it appears as an option in the ''Select ICM Agreement/Association'' drop-down.&lt;br /&gt;
&lt;br /&gt;
5. In the ''Select ICM Agreement/Association'' drop-down '''select '''the association created in Step 4.&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''the ''Select Email Attachment'' drop down. The following options are displayed:&lt;br /&gt;
&lt;br /&gt;
*''Email as Outlook format (.msg)'': Use this option to upload the email thread to the association as is. &lt;br /&gt;
*''Email as document (.docx)'': Use this option to upload the email thread to the association as a Word document. &lt;br /&gt;
&lt;br /&gt;
7. '''Select''', for example, Email as document. The selected file name is displayed in the ''Mapping Result(s)'' section.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;The capability to embed the attachments in the email thread into in the .docx file is currently not supported. Selecting the ''Email as document'' option only uploads the text content and not any attachments.&amp;lt;/div&amp;gt; &lt;br /&gt;
You can delete the selected email by '''clicking '''the ''Delete ''icon.&lt;br /&gt;
&lt;br /&gt;
8. '''Click '''''Upload''. The selected email gets uploaded and the ''File(s) uploaded successfully'' message is displayed.&amp;lt;br/&amp;gt; The uploaded email appears in .docx format on ICM Web and is displayed as an Association instance against the PriceList association.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
9. On the agreement ''Details'' page, '''click''' the ''Association'' tab. In this example ''Supplier Communication'' is the association for the agreement. The associated document ''PriceList for August 2020'' uploaded using the Outlook add-in is displayed in the list of instances.&lt;br /&gt;
&lt;br /&gt;
10. '''Click '''the ''View ''icon for the created associated document instance ''PriceList for August 2020''. The associated document ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
11. '''Click '''the ''Versions ''tab. The uploaded email thread is displayed and is available to download in PDF and in Word formats.&lt;br /&gt;
&lt;br /&gt;
12. '''Click '''an icon below the ''Document ''column, for example Word icon. A .docx file will be downloaded.&lt;br /&gt;
&lt;br /&gt;
'''Note''': If you have selected the option to upload ''Email as Outlook format'', the email thread is indicated with an Outlook Message icon in Step 11, clicking which downloads the email thread in .msg format in Step 12.&lt;br /&gt;
&lt;br /&gt;
13. Open the downloaded file. The uploaded email thread content will be displayed in the file contents. In this example, the .docx file displays the email uploaded as an association.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding an email as a new version of an associated document using Outlook Add-in ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Select ICM Agreement / Association'' on the ''Details ''tab on the Outlook add-in. A drop down is displayed.&lt;br /&gt;
&lt;br /&gt;
2. '''Select''' the Association instance for which you want to add the current email as an association attachment (for example, ''PriceList for August 2020'').&lt;br /&gt;
&lt;br /&gt;
3. '''Click '''''Upload''. The File(s) uploaded successfully message will be displayed.&lt;br /&gt;
&lt;br /&gt;
The uploaded email (in .docx or in .msg format) gets uploaded on ICM Web as a version of the Association selected in Step 2, and is displayed as an Association instance against the ''PriceList'' association.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding an email as a new version of an associated document using Outlook Add-in ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Select ICM Agreement / Association ''on the ''Details ''tab on the Outlook add-in. A drop down is displayed.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''the Association instance for which you want to add the current email as an association attachment (for example, PriceList for August 2020).&lt;br /&gt;
&lt;br /&gt;
3. '''Click '''''Upload''. The File(s) uploaded successfully message is displayed.&lt;br /&gt;
&lt;br /&gt;
The uploaded email (in .docx or in .msg format)&amp;amp;nbsp;gets uploaded on ICM Web as a version of the Association selected in Step 2, and is displayed as an Association instance against the PriceList association.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;'''Related Topics:''' [[Agreement_Management|Agreement Management]] | [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] |&amp;amp;nbsp;[[Clause_Management|Clause Management]] | [[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]] |&amp;amp;nbsp;[[Power_BI_Integration_with_ICM|Advanced Analytics]]&amp;amp;nbsp;|&amp;amp;nbsp;[[User_Administration|User Administration]]&amp;amp;nbsp;| [[ICI_Add-ins|ICI Add-ins]]&amp;amp;nbsp;| &amp;amp;nbsp;[http://int-wiki.cloudapp.net:8085/ICMHelp7.12/index.php?title=Icertis_Experience_for_Word Icertis Experience for Word] |&amp;amp;nbsp;[[Release_Notes|Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15385</id>
		<title>Outlook Add-in</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Outlook_Add-in&amp;diff=15385"/>
				<updated>2020-09-30T04:12:55Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Outlook Add-in =&lt;br /&gt;
&lt;br /&gt;
A&amp;amp;nbsp;.JS version of the ICI Outlook Plugin is available in ICI. The overall turnaround time for the author is reduced as he no longer needs to download the documents received over email to the local machine, then switch applications and log in to ICI, search the Agreement and then upload the documents.&amp;lt;br/&amp;gt; The provisioned user can now:&lt;br /&gt;
&lt;br /&gt;
*Upload the next version of the Agreement document received over an Email to the Agreement &lt;br /&gt;
*Upload the next version of the Associated document (supporting Attachments) received over an Email to the Agreement &lt;br /&gt;
*Create a new Association instance and then upload the Associated Document received over an Email to the Agreement &lt;br /&gt;
&lt;br /&gt;
The configuration of the Outlook Add-in is driven by the Masterdata, whereas the list of Agreements and their details are configured by the Saved Searches. You can configure multiple saved searches.&lt;br /&gt;
&lt;br /&gt;
The Outlook Add-in (.JS version) is supported on 2 different platforms:&lt;br /&gt;
&lt;br /&gt;
*For MAC OS (Mojave): it is tested and verified on Microsoft Office 365 (2016 and above). &lt;br /&gt;
*For Windows 10: it is tested and verified on Microsoft Office Professional Plus 2013 (15.0.5007.1000) and 2016 (16.0.4849.1000) 64-bit and above. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Uploading the next version of an Agreement received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To add the the next version of the Agreement received over Outlook Email:&amp;lt;br/&amp;gt; 1. '''Open''' the Email with the next version of the Agreement.&amp;lt;br/&amp;gt; 2. '''Open''' the ICI Outlook Add-in.&amp;lt;br/&amp;gt; 3. On the ''Details ''tab, '''click '''''Select ICI Agreement / Association'' to look for the Agreement that you&amp;amp;nbsp;want to upload as the next version.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 1.png|820px|Email Outlook Plugin 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed. If the Agreement fails to be attached, then a message will be displayed indicating that you can retry sending the Attachment.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 2.png|820px|Email Outlook Plugin 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can&amp;amp;nbsp;''Preview'' the Agreement in the ICI application&amp;amp;nbsp;on the Agreement ''Details ''page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 03.png|720px|Email Outlook Plugin 03.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding the next version of the Associated Document received over MS Outlook Email to the Agreement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; To add the next version of the&amp;amp;nbsp;Associated Document received over Outlook Email to the Agreement&amp;amp;nbsp;:&amp;lt;br/&amp;gt; 1. '''Open '''the Email with the Associated Documents.&amp;lt;br/&amp;gt; 2. '''Open '''the ICI Outlook Add-in.&lt;br /&gt;
&lt;br /&gt;
3. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association'' to add the next version of the Association.&amp;amp;nbsp;For example, ''Payment Details''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 4.png|820px|Email Outlook Plugin 4]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;4. '''Click''' ''Select Email Attachment'' that you want to upload from the drop-down.&amp;lt;br/&amp;gt; 5. '''Click''' ''Upload''.&amp;amp;nbsp;The ''File(s) uploaded successfully ''message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 5 gr actions.png|820px|Email Outlook Plugin 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click''' the ''View Record'' icon to view the Attachment details.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 6.png|820px|Email Outlook Plugin 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click '''the&amp;amp;nbsp;''Preview'' icon to view the Attachment.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 7.png|820px|Email Outlook Plugin 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Creating a new instance of an Association and adding an Associated Document received over MS Outlook Email ==&lt;br /&gt;
&lt;br /&gt;
To create a new instance of an Association and add the Associated Document received over Outlook Email to the Agreement:&amp;lt;br/&amp;gt; 1. On the ''Details'' tab,'''click''' ''Select ICI Agreement / Association ''to create a new instance of the&amp;amp;nbsp;Association. For example, adding an Association to the''Payment Details A''ssociation.&amp;lt;br/&amp;gt; 2. Enter a name for the new instance of the Association.&amp;lt;br/&amp;gt; 3. '''Click''' the ''Add Association'' button to add the new instance of the Association.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 8.png|820px|Email Outlook Plugin 8]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 4. '''Click '''the ''Select Email Attachment'' field to select the document that you want to attach to the newly created instance.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 9.png|820px|Email Outlook Plugin 9]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; 5.'''Click''' ''Upload''. The document is now attached to the newly created instance. The ''File(s) uploaded successfully'' message is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''The Association is only created with the name. The remaining mandatory fields need to be entered in the ICI application.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Email Outlook Plugin 10.png|820px|Email Outlook Plugin 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. The document is now available on the ''Associations'' tab in the ICI application as the next version.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding an email as an associated document to an existing association ==&lt;br /&gt;
&lt;br /&gt;
To upload an email conversation by creating a new instance of association in .docx and .msg formats:&lt;br /&gt;
&lt;br /&gt;
1. On the Agreement Details page of the Outlook add-in, '''click '''on the association instance, for example Supplier Communication.&lt;br /&gt;
&lt;br /&gt;
2. '''Click '''''Add Association''. A text field is displayed.&lt;br /&gt;
&lt;br /&gt;
3. '''Enter '''a name for the new associated document, for example PriceList for August 2020.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''the plus icon, the association instance gets created and it appears as an option in the ''Select ICM Agreement/Association'' drop-down.&lt;br /&gt;
&lt;br /&gt;
5. In the ''Select ICM Agreement/Association'' drop-down '''select '''the association created in Step 4.&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''the ''Select Email Attachment'' drop down. The following options are displayed:&lt;br /&gt;
&lt;br /&gt;
*''Email as Outlook format (.msg)'': Use this option to upload the email thread to the association as is. &lt;br /&gt;
*''Email as document (.docx)'': Use this option to upload the email thread to the association as a Word document. &lt;br /&gt;
&lt;br /&gt;
7. '''Select''', for example, Email as document. The selected file name is displayed in the ''Mapping Result(s)'' section.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;The capability to embed the attachments in the email thread into in the .docx file is currently not supported. Selecting the Email as document option only uploads the text content and not any attachments.&amp;lt;/div&amp;gt; &lt;br /&gt;
You can delete the selected email by '''clicking '''the ''Delete ''icon.&lt;br /&gt;
&lt;br /&gt;
8. '''Click '''''Upload''. The selected email gets uploaded and the ''File(s) uploaded successfully'' message is displayed.&amp;lt;br/&amp;gt; The uploaded email appears in .docx format on ICM Web and is displayed as an Association instance against the PriceList association.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
9. '''Click '''the ''PriceList ''tab. The associated document PriceList for August 2020 is uploaded and displayed in the list of instances.&lt;br /&gt;
&lt;br /&gt;
10. '''Click '''the ''View ''icon for the created associated document instance PriceList for August 2020. The associated document ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
11. '''Click '''the ''Versions ''tab. The uploaded email thread is displayed and available to download in PDF and in Word formats.&lt;br /&gt;
&lt;br /&gt;
12. '''Click '''the Word icon in the ''Document ''column. The file is downloaded.&lt;br /&gt;
&lt;br /&gt;
13. Open the downloaded Word file. The uploaded email thread content will be displayed in the document.&lt;br /&gt;
&lt;br /&gt;
'''Note''': If you have selected the option to upload Email as Outlook format, the email thread is indicated with an Outlook Message icon in Step 11, clicking which downloads the email thread in .msg format in Step 12.&lt;br /&gt;
&lt;br /&gt;
== Adding an email as a new version of an associated document using Outlook Add-in ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Select ICM Agreement / Association ''on the ''Details ''tab on the Outlook add-in. A drop down is displayed.&lt;br /&gt;
&lt;br /&gt;
2. '''Select '''the Association instance for which you want to add the current email as an association attachment (for example, PriceList for August 2020).&lt;br /&gt;
&lt;br /&gt;
3. '''Click '''''Upload''. The File(s) uploaded successfully message is displayed.&lt;br /&gt;
&lt;br /&gt;
The uploaded email (in .docx or in .msg format)&amp;amp;nbsp;gets uploaded on ICM Web as a version of the Association selected in Step 2, and is displayed as an Association instance against the PriceList association.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;'''Related Topics:''' [[Agreement_Management|Agreement Management]] | [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] |&amp;amp;nbsp;[[Clause_Management|Clause Management]] | [[Configuration|Configuration]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Reports|Reports]] |&amp;amp;nbsp;[[Power_BI_Integration_with_ICM|Advanced Analytics]]&amp;amp;nbsp;|&amp;amp;nbsp;[[User_Administration|User Administration]]&amp;amp;nbsp;| [[ICI_Add-ins|ICI Add-ins]]&amp;amp;nbsp;| &amp;amp;nbsp;[http://int-wiki.cloudapp.net:8085/ICMHelp7.12/index.php?title=Icertis_Experience_for_Word Icertis Experience for Word] |&amp;amp;nbsp;[[Release_Notes|Release Notes]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15298</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15298"/>
				<updated>2020-09-29T09:01:50Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
The discovery support has been further extended for URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following attributes in the document has additionally been introduced: ''City, State, Zip, Point of contact – Name, Point of contact – Title, Point of contact – Email'' and ''Point of contact – Phone''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support for additional languages in AI apps ==&lt;br /&gt;
&lt;br /&gt;
The discovery models have now been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Attribute and table discovery, Playbook discovery, contract highlights and discovery of similar agreements currently do not include multi-language support and will continue to be supported in English only.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Supporting clause hierarchy in agreements in .docx format ==&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&amp;lt;br/&amp;gt; With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections and so on.&amp;lt;br/&amp;gt; Further, any document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Currently only well-structured .docx files are supported. Refer to the detailed recommendation below for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The discovered clauses are displayed in a delineated view to indicate the main section, sub-sections and so on, of each identified clause.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Only well-structured Word documents (.docx) are currently supported. Refer to the Recommendation section at the end of this page for guidelines on structuring a document for clause delineation.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''License/Grant of License''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported for Clause Discovery are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review, for example ''License''. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
You can review an entire section as a clause or review each sub-section separately and confirm each as a separate clause.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15297</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15297"/>
				<updated>2020-09-29T08:43:38Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
The discovery support has been further extended for URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following attributes in the document has additionally been introduced: ''City, State, Zip, Point of contact – Name, Point of contact – Title, Point of contact – Email'' and ''Point of contact – Phone''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support for additional languages in AI apps ==&lt;br /&gt;
&lt;br /&gt;
The discovery models have now been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Attribute and table discovery, Playbook discovery, contract highlights and discovery of similar agreements currently do not include multi-language support and will continue to be supported in English only.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Supporting clause hierarchy in agreements in .docx format ==&lt;br /&gt;
&lt;br /&gt;
Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.&amp;lt;br/&amp;gt; With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections and so on.&amp;lt;br/&amp;gt; Further, any document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Currently only well-structured .docx files are supported. Refer to the detailed recommendation below for the definition of a well-structured document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''non solicitation''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported for Clause Discovery are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15296</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15296"/>
				<updated>2020-09-29T08:36:27Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
The discovery support has been further extended for URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following attributes in the document has additionally been introduced: ''City, State, Zip, Point of contact – Name, Point of contact – Title, Point of contact – Email'' and ''Point of contact – Phone''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support for additional languages in AI apps ==&lt;br /&gt;
&lt;br /&gt;
The discovery models have now been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Attribute and table discovery, Playbook discovery, contract highlights and discovery of similar agreements currently do not include multi-language support and will continue to be supported in English only.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''non solicitation''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported for Clause Discovery are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15295</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15295"/>
				<updated>2020-09-29T08:33:34Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
The discovery support has been further extended for URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following attributes in the document has additionally been introduced: ''City, State, Zip, Point of contact – Name, Point of contact – Title, Point of contact – Email'' and ''Point of contact – Phone''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support for additional languages in AI apps ==&lt;br /&gt;
&lt;br /&gt;
The discovery models have now been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Attribute and table discovery, Playbook discovery, contract highlights and discovery of similar agreements currently do not include multi-language support and will continue to be supported in English only.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''non solicitation''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported for Clause Discovery are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15294</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15294"/>
				<updated>2020-09-29T08:32:24Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
The discovery support has been further extended for URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following attributes in the document has additionally been introduced: ''City, State, Zip, Point of contact – Name, Point of contact – Title, Point of contact – Email'' and ''Point of contact – Phone''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Support for additional languages in AI apps ==&lt;br /&gt;
&lt;br /&gt;
The discovery models have now been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.&lt;br /&gt;
&lt;br /&gt;
With this release:&lt;br /&gt;
&lt;br /&gt;
*Additional language support is available in NegotiateAI and DiscoverAI for legacy migration. &lt;br /&gt;
*Discovered clauses and obligations are displayed and then linked back to the matching text in original document. &lt;br /&gt;
*Identified clause and obligation categories/ sub-categories are displayed in user preferred language on the UI. &lt;br /&gt;
*While discovering or matching the clause from clause library, document language is taken into consideration. &lt;br /&gt;
*The additional languages are supported while discovering similar clauses. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''non solicitation''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported for Clause Discovery are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15282</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15282"/>
				<updated>2020-09-28T13:21:06Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
The discovery support has been further extended for URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following attributes in the document has additionally been introduced: ''City, State, Zip, Point of contact – Name, Point of contact – Title, Point of contact – Email'' and ''Point of contact – Phone''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''non solicitation''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported for Clause Discovery are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The additional languages currently supported are German, Spanish and Portuguese.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15281</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15281"/>
				<updated>2020-09-28T13:07:44Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
The discovery support has been further extended for URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
With this release, identification of the following attributes in the document has additionally been introduced: ''City, State, Zip, Point of contact – Name, Point of contact – Title, Point of contact – Email'' and ''Point of contact – Phone''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''non solicitation''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Agreement_Management&amp;diff=15269</id>
		<title>Agreement Management</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Agreement_Management&amp;diff=15269"/>
				<updated>2020-09-28T10:21:27Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Agreement Management =&lt;br /&gt;
&lt;br /&gt;
The Agreement Management section enables you to manage all aspects of creating and editing Agreements from a single page. From this page, you can do the following tasks:&lt;br /&gt;
&lt;br /&gt;
*View and manage all your Agreements on the ''Agreements ''page. &lt;br /&gt;
*Create new Agreements on the Creating an Agreement. &lt;br /&gt;
*Search, view, and manage all your existing requests on the ''Requests'' page. &lt;br /&gt;
*Create new Requests on the ''Create Request''&amp;amp;nbsp;page. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Mgmt.PNG|720px|Agreement Mgmt]]&amp;lt;/div&amp;gt; &lt;br /&gt;
In ICI, the terms Agreement and Contract are used interchangeably and mean the same thing. In this Help, we will use the word ''Agreement''&amp;amp;nbsp;when discussing&amp;amp;nbsp;Agreements, whereas Contracts will be discussed with&amp;amp;nbsp;reference to Contract Types.&lt;br /&gt;
&lt;br /&gt;
While the actual workflow of an Agreement in ICI can be quite complex and involved, it is summarized in these five steps:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Agreement Management - Agreement Overview.png|720px|Agreement Management - Agreement Overview.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
1.&amp;amp;nbsp;'''Create Contract Request:''' When someone in your organization, such as a department manager wants to engage a vendor for certain services over a length of time, the individual can raise that request with the procurement department that can then work on that Agreement. Depending on the workflow adopted, your organization may:&lt;br /&gt;
&lt;br /&gt;
*Enforce this step so that all contracts are initiated and drafted only by one department, or &lt;br /&gt;
*Make this step completely optional, so it can be skipped by someone who is an expert at contracting and its process. &lt;br /&gt;
&lt;br /&gt;
2. '''Create Agreement:''' In this step, the primary owner or the creator of the agreement&amp;amp;nbsp;select the contract type, selects attributes and template, and verifies the details that you entered in the agreement.&amp;amp;nbsp;See Create Agreement Page for complete details.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Review Agreement: '''After the primary owner has created an internal draft of the agreement, it is published. The published draft can be sent for reviews (optional, if decided by the Primary Owner of the Agreement) .&lt;br /&gt;
&lt;br /&gt;
4. '''Approve Agreement: '''Once the Agreement is reviewed, it can be sent for approvals to the team of people that are working on this Agreement in various roles.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Execute Agreement:''' Several people can review and approve the Agreement before it is ready to be signed. After all approvals are obtained, the Agreement is sent to be signed by both the parties. With both parties signing (known as internal and external signatories in ICI), the Agreement is said to be executed&amp;amp;nbsp;and is now in force.&lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&amp;lt;br/&amp;gt; If an incorrect document was initially uploaded by a signatory, a&amp;amp;nbsp;user with the appropriate privilege can upload the correct document even after the agreement is executed.&amp;amp;nbsp;The uploaded document must be a PDF.'''&amp;amp;nbsp;'''The ''Executed''&amp;amp;nbsp;state of the Agreement remains unchanged. Only the following roles have this privilege:&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* Primary Owner&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* Secondary Owner&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* Contributor&amp;lt;br/&amp;gt; &amp;lt;br/&amp;gt; If changes are required in the Agreement that is in an ''Executed'' state, the Primary Owner of the Agreement can add an Amendment. Changes may be required due to any of the following business reasons:&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;* The payment terms of the Agreement have changed.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &amp;amp;nbsp;*&amp;amp;nbsp;The Statement of Work (SOW) in the Agreement has changed.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;amp;nbsp; *&amp;amp;nbsp;The terms and conditions of the Agreement have changed due to the introduction of a new regulation.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Support Multi-party Agreements''': ICI offers full platform support for multi-party Agreements.&amp;amp;nbsp;You can now use a single system for managing all your Agreements and capture multiple other parties and divisions on an Agreement seamlessly. It allows you to search only metadata instead of searching multiple attributes, thus making it user-friendly. There is no limit on the number of parties that can be added. All parties can sign the Agreements either manually or electronically, based on the signing sequence set in ICI. It also supports parallel signatures independent of the status of either party.&lt;br /&gt;
&lt;br /&gt;
Such Agreements include Non-Disclosure Agreements, Sell Agreements or business-specific Agreements. For example, A healthcare business group needs Contract Types for managing their contracts, but the Mergers and Acquisitions department needs their own Contract Types.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;br/&amp;gt; Key capabilities of Multi-Party:&lt;br /&gt;
&lt;br /&gt;
*Captures multiple values of Attributes and/or Masterdata &lt;br /&gt;
*Tags these multiple instances in the Template &lt;br /&gt;
*Supports the signature workflow with these multiple instances of customer data &lt;br /&gt;
*Supports multiple Rules (say for approval workflow) based on the individual values selected. For example,&amp;amp;nbsp;in an Agreement, if 3 Divisions are selected, the approval process should support approvals from all 3 divisions. &lt;br /&gt;
*Supports visibility in such a one-to-many environment; For example, in the multi-division scenario, the Agreement visibility too should be enabled for multiple divisions. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upfront chevron view of agreement journey ==&lt;br /&gt;
&lt;br /&gt;
In ICI, as per the contracting business paradigm, an agreement entity goes through different workflows and stages starting from authoring to execution, and expiration or termination.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Users can view the current status of an agreement on the ''Agreement Index ''or ''Details'' page, a generic progress view on the ''Team'' tab, and logged audit details on the ''History ''tab. To understand the progress of the agreement and find relevant information, the user needs to navigate through multiple tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A horizontal chevron is displayed, which is a visual depiction of the agreement’s journey that provides a simple, upfront and consolidated view of the agreement’s lifespan. The 4 stages of the chevron prominently communicate an entity’s journey including the previous, current and possible future states of the agreement. This considerably improves usability for new and existing users as they can now find information easily and with minimum clicks.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 1.png|720px|Chevron 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The colors of the chevron are indicative of the stage of the agreement. For example, if the theme color as per user preferences is green, then the previous stage is displayed in a light green color, the current stage is displayed in a dark green color, and the future stages are displayed in grey color.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The chevron displays the following 4 tabs corresponding to the various stages of the agreement’s journey:&lt;br /&gt;
&lt;br /&gt;
1.'''Generate: '''Displays list of actions taken by the user on the agreement before it is published. It includes the 5 most recent logs of the actions taken (such as ''Agreement Copied, Agreement Published'') including details such as role of the user who performed the task, date and time of the action, and user name. The icons displayed next to the user name are similar to those in the agreement’s ''History ''log (such as green thumb icon for actions completed).&lt;br /&gt;
&lt;br /&gt;
2. '''Approve:''' Displays the list of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them. The icons and information in this tab are similar to those displayed in the agreement’s ''Progress'' view.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3. '''Execute: '''Displays details such as internal/external signatories that have either signed the agreement or whose signatures are pending. By default, the external signatory details are displayed first. The icons and information in this tab are similar to those displayed in the agreement’s ''Progress'' view.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4. '''Manage:''' Displays the 5 most recent logs of the actions taken by the user to manage the agreement post-execution. (such as ''Agreement Terminated, Agreement Superseded''). The icons displayed next to the user name are similar to those in the agreement’s ''History ''log.&lt;br /&gt;
&lt;br /&gt;
The icons displayed on the chevron include:&lt;br /&gt;
&lt;br /&gt;
*[[File:Chevron 1 icon.png|Chevron tick mark]]&amp;amp;nbsp;-&amp;amp;nbsp;indicates stage completed &lt;br /&gt;
*[[File:Chevron clock icon.PNG|Chevron clock icon]]&amp;amp;nbsp;- indicates stage in progress &lt;br /&gt;
&lt;br /&gt;
'''Note:'''&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*The chevron view is only applicable to agreement contract type (agreements and amendments).&amp;amp;nbsp; &lt;br /&gt;
*By default, the chevron is disabled; it can be enabled for selected contract types. &lt;br /&gt;
*The chevron labels support localization. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Let’s consider an example of an agreement named ''Automation Basic Agreement'' and view its journey through the &amp;lt;u&amp;gt;4 stages&amp;lt;/u&amp;gt; of the chevron.&lt;br /&gt;
&lt;br /&gt;
1.'''Generate: '''Displays the following details:&lt;br /&gt;
&lt;br /&gt;
*List of 5 most recent logs of the actions taken by the user who created the agreement – e.g. ''Agreement Copied, Agreement Created, Agreement Modified, Agreement Team Member Added, ''and finally''Agreement Published''. &amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
*User details – e.g. user name''Automation user1'' and user role ''Primary Owner''.&amp;amp;nbsp; &lt;br /&gt;
*Time stamp – e.g. the agreement was copied on ''8/28/2020'' at ''14:05:02''. &lt;br /&gt;
*Icons next to the user name – similar to those in the agreement’s History log, e.g. ''green thumb icon'' for actions completed. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 2.png|720px|Chevron 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Approve:''' Displays the following details:&lt;br /&gt;
&lt;br /&gt;
*List of approvers as per the defined steps in the agreement, users that have approved the agreement, users with pending approval actions and for how long it has been pending with them. The list of approvers is similar to those mentioned in the ''Team'' tab. &lt;br /&gt;
*Number of approvers required for agreement approval – e.g.''1 of 2 required''. If no approvers are added, then a message will be displayed that no approvers are added to the team and the agreement is directly approved. &lt;br /&gt;
*Approver details – e.g. approver 1 - ''AE User13'', approver 2 – ''AE User11''.&amp;amp;nbsp; &lt;br /&gt;
*Hovering over the user names opens a box displaying the user (approver) email and ''Notes'' added by the user, if any. &lt;br /&gt;
*The icons and information in this tab are similar to those displayed in the agreement’s ''Progress'' view.&amp;amp;nbsp; &lt;br /&gt;
*Approvers are queued as per the rules. For example:&amp;lt;br/&amp;gt; - Step 1: Completed i.e. AE User 13 has approved the content (&amp;amp; the Step 1 tab color is light green).&amp;lt;br/&amp;gt; - Step 2: In Progress i.e. Agreement is currently waiting for approval from AE User 11 (&amp;amp; the Step 2 tab color is dark green).&amp;lt;br/&amp;gt; - Step 3: Not Started i.e. Rasika is in queue and the agreement will be sent to her after approval from AE User 11 (&amp;amp; the Step 3 tab color is grey).&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; 3. '''Execute: '''Displays the following details:&amp;lt;/div&amp;gt; &lt;br /&gt;
*Internal/ external signatories that have either signed the agreement or whose signatures are pending e.g. ''Internal Signature'' by ''ami'' and ''External Signature ''by AE''User 10''. &lt;br /&gt;
*Minimum number of external and internal signatures required at each step e.g. 1 of 1 required external signature at ''Step 1 ''by external signatory ''AE User 10''.&amp;amp;nbsp; &lt;br /&gt;
*Hovering over the user names opens a box displaying the user (approver) email, with whom the agreement currently is, and for how long it has been pending with the user. &lt;br /&gt;
*By default, the external signatory details are displayed first. The icons and information in this tab are similar to those displayed in the agreement’s ''Team'' tab. If no signatories are part of the team, then a message will be displayed indicating that and the agreement will directly move to the ''Executed'' state. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 4.png|720px|Chevron 4]]&amp;lt;br/&amp;gt;  &amp;lt;br/&amp;gt; '''4. Manage:''' Displays the following details:&amp;lt;/div&amp;gt; &lt;br /&gt;
*The 5 most recent logs of the actions taken by the user to manage the agreement post-execution e.g. ''Agreement Downloaded, Agreement Sent For Review''.&amp;amp;nbsp; &lt;br /&gt;
*The icons displayed next to the user name are similar to those in the agreement’s ''History'' log. &lt;br /&gt;
*User details – e.g. user name ''Automation user1'' and user role ''Primary Owner''.&amp;amp;nbsp; &lt;br /&gt;
*Time stamp – e.g. the agreement was copied on ''8/28/2020 ''at ''14:08:09''. &lt;br /&gt;
*Icons next to the user name – similar to those in the agreement’s ''History ''log, e.g. ''green thumb icon ''for actions completed. &lt;br /&gt;
*The ''clock icon'' on the ''Manage ''tab indicates the stage that is in progress e.g. the user has to take actions on the agreement and is currently in the ''Agreement Sent For Review ''state, whereas the tick mark icon on the ''Generate, Approve ''and''Execute ''tabs indicate that these stages of the agreement’s journey are complete.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Chevron 5.png|720px|Chevron 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Contract Lifecycle Management, Artificial Intelligence, and Bulk Upload ==&lt;br /&gt;
&lt;br /&gt;
For organizations looking to optimize their contract lifecycle management processes and digital transformation, this release includes capabilities to manage the bulk upload of larger volumes of legacy contracts, and Artificial Intelligence (AI) driven enhancements to improve discovery, identification, and digitization of third-party, legacy and federal contracts.&lt;br /&gt;
&lt;br /&gt;
Using ICI, you have the:&lt;br /&gt;
&lt;br /&gt;
*Ability to create US Federal Acquisition Regulations clause repository and to manage US Federal Contracts using ICI. &lt;br /&gt;
*Accelerate contract digitalization and management by quickly converting legacy contracts into live contracts with AI-enhanced contract digitization capabilities which also help in AI-powered clause and attribute discovery. Excel based bulk upload capability to do so at scale. &lt;br /&gt;
*Upload&amp;amp;nbsp;legacy Agreements in bulk supporting a larger volume of agreements and other entities using Excel utility. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;related_topics&amp;quot;&amp;gt;'''Related Topics:'''&amp;amp;nbsp;[[Searching_agreements_and_requests|Searching Agreements and Requests]]&amp;amp;nbsp;| [[Adding_Supporting_Documents_to_an_Agreement|Adding Supporting Documents to an Agreement]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Setting_auto-expiry_for_an_Agreement|Setting auto-expiry for an Agreement]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Bulk_Actions|Bulk Actions]]&amp;amp;nbsp;| [[User_Administration|User Administration]] | [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Localizing_ICI|Localizing ICI]]&amp;amp;nbsp;|&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15268</id>
		<title>Discover AI</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Discover_AI&amp;diff=15268"/>
				<updated>2020-09-28T10:06:22Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= DiscoverAI =&lt;br /&gt;
&lt;br /&gt;
== Contract Highlights ==&lt;br /&gt;
&lt;br /&gt;
Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.&lt;br /&gt;
&lt;br /&gt;
With this release,&lt;br /&gt;
&lt;br /&gt;
*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience. &lt;br /&gt;
*In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance. &lt;br /&gt;
*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user. &lt;br /&gt;
*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator &lt;br /&gt;
&lt;br /&gt;
To configure generating contract highlights from an agreement:&lt;br /&gt;
&lt;br /&gt;
#'''Create''' an ''Agreement Contract Type'' using ''Third Party Paper''. You can use an existing ''Agreement Contract Type'' as well. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 01.png|620px|Discover AI Contract Highlights 01.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To be able to generate contract highlights from an Agreement, '''include''' the following attributes in the ''Agreement Contract Type'':&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 02.png|620px|Discover AI Contract Highlights 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Associated Document Contract Type'', for example, ''ICILegalHighlights'' to generate contract highlights for your legal department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': ''Allow Document Assembly'' must be set to ''Yes''.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 03.png|420px|Discover AI Contract Highlights 03.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To add contract highlights in an ''Associated Document'', '''include''' the following attributes in the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Contract Highlight Terms''': The ''Data Type'' must be selected as ''String''. In the ''Default Value'' attribute, '''enter''' the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10. &lt;br /&gt;
*'''Contract Highlights''': Here the ''Data Type RichTextArea'' must be selected. &lt;br /&gt;
&lt;br /&gt;
To add the created ''Associated Document Contract Type'' to the ''Agreement Contract Type'':&lt;br /&gt;
&amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;On the ''Contract Types'' page, '''click''' the ''Agreement Contract Type'' created earlier. The ''Details'' page for that contract type opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' the ''Edit'' button. The ''Edit Contract Type'' wizard opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Navigate''' to the ''Association'' tab by clicking ''Next''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the plus icon next to ''Association''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''an ''Association'' for the ''Associated Document Contract Type''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 04.png|620px|Discover AI Contract Highlights 04.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select''' the created ''Associated Document Contract Type''. You can set the ''Allow Multiple Instance'' option to ''Yes'', to allow different contract highlight associated documents to be created for different departments, such as legal or finance. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a template for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 05.png|520px|Discover AI Contract Highlights 05.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Both the contract highlights attributes (''Contract Highlight Terms'' and ''Contract Highlights'') must&amp;amp;nbsp; be tagged within the template.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' a ''Template Selection Rule'' for the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;13&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an ''Event Rule'' with the action ''AITriggerContractHighlights''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Event'' selected must be any other than ''Agreement Created'', for example ''Agreement Published''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 06.png|520px|Discover AI Contract Highlights 06.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;To get the contract highlights in the ''Associated Document'', you need to '''create''' an ''Association'' with the ''Parent Agreement''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI Contract Highlights 07.png|420px|Discover AI Contract Highlights 07.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;15&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next''. The ''Meta Data'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Enter''' the keywords in the ''Contract Highlight Terms''. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Add''' ''NoOfRecords:n'' where 'n' denotes the number of contract highlights to be extracted. The default is ''NoOfRecords:20'', if the value of n is not specified in the keywords.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;When an Agreement created using the selected ''Agreement Contract Type'' is published, the configured contract highlights will be extracted and compiled in the ''Associated Document''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': There are no changes to the existing Agreement workflow while configuring and generating the contract highlights.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Bulk Upload with Clause Discovery ==&lt;br /&gt;
&lt;br /&gt;
To upload Agreements in bulk:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Agreement Management&amp;amp;nbsp;&amp;gt; Agreements''&amp;amp;nbsp;on the dashboard. The ''Agreement Management ''page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 Adobe 01.PNG|720px|7.12 Adobe 01.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Bulk Actions &amp;gt; Bulk Actions''&amp;amp;nbsp;on the dashboard. The&amp;amp;nbsp;''Bulk Action Management''&amp;amp;nbsp;page opens.&lt;br /&gt;
&lt;br /&gt;
3.'''&amp;amp;nbsp;Click'''&amp;amp;nbsp;''Add Batch''. The ''Add Batch'' pop up window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Select Batch File''&amp;amp;nbsp;button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:&amp;amp;nbsp;'''Upload a .zip file here which should have been created containing 2 Excel files (Meta.xls, Data.xls) and Third Party Agreement files in PDF and docx format. This does not work for Own Party Agreements.&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 3.png|720px|SP6 Bulk Upload 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file.&amp;amp;nbsp;5.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Submit&amp;amp;nbsp;''button. The&amp;amp;nbsp;''File Uploaded Successfully''message is displayed.&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 4.png|720px|SP6 Bulk Upload 4]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Submit''&amp;amp;nbsp;button. The&amp;amp;nbsp;''File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 5.png|SP6 Bulk Upload 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''OK''. The file is now displayed in the&amp;amp;nbsp;''Grid''&amp;amp;nbsp;view with the status ''Not Started''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 6.png|720px|SP6 Bulk Upload 6]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;''Refresh''&amp;amp;nbsp;icon twice. On first Refresh, the Status changes to&amp;amp;nbsp;''In Progress''&amp;amp;nbsp;and then to&amp;amp;nbsp;''Needs Validati''on.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 7.png|720px|SP6 Bulk Upload 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''an&amp;amp;nbsp;''Actions&amp;amp;nbsp;''radio button for the file that you want to finalize. The&amp;amp;nbsp;''Validate''&amp;amp;nbsp;and&amp;amp;nbsp;''Finalize''&amp;amp;nbsp;buttons are enabled.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 8.png|720px|SP6 Bulk Upload 8]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.''&amp;amp;nbsp;'''''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Validate''&amp;amp;nbsp;button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:&amp;amp;nbsp;'''The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
10.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save''&amp;amp;nbsp;to save the changes.&lt;br /&gt;
&lt;br /&gt;
11.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the&amp;amp;nbsp;''Finalize&amp;amp;nbsp;''button, the PopulatedData.xlsx file can be uploaded. The&amp;amp;nbsp;''Finalized File Uploaded Successfully''&amp;amp;nbsp;message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 9.png|SP6 Bulk Upload 9]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12.&amp;amp;nbsp;The&amp;amp;nbsp;''Needs Validation''&amp;amp;nbsp;status changes to&amp;amp;nbsp;''Completed''.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:SP6 Bulk Upload 10.png|720px|SP6 Bulk Upload 10]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click'''&amp;amp;nbsp;the Agreements tile to view the Agreements which will be in the&amp;amp;nbsp;''Draft''&amp;amp;nbsp;state.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Table Discovery =&lt;br /&gt;
&lt;br /&gt;
Along with clauses&amp;amp;nbsp;and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the ''Tables ''tab (on the ''Details'' page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.&lt;br /&gt;
&lt;br /&gt;
You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.&lt;br /&gt;
&lt;br /&gt;
The table discovery allows you to:&lt;br /&gt;
&lt;br /&gt;
*Identify and discover the table(s) in the Agreement Document &lt;br /&gt;
*Update the data in the discovered table as required &lt;br /&gt;
*Create new instances of the Associations for the uploaded Agreement &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' Both .docx and .pdf formats are supported.&amp;lt;/div&amp;gt; &lt;br /&gt;
The table discovery in PDF agreements works well with:&lt;br /&gt;
&lt;br /&gt;
*Tables with well-defined borders in text PDFs and high-quality scanned PDFs &lt;br /&gt;
*Tables that may be slightly skewed or tilted &lt;br /&gt;
*Table cells with light-colored backgrounds &lt;br /&gt;
&lt;br /&gt;
The table discovery in PDF agreements may not work well with:&lt;br /&gt;
&lt;br /&gt;
*Tables in low-quality scanned PDFs and those without borders &lt;br /&gt;
*Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations &lt;br /&gt;
*Certain non-table elements, such as flowcharts and diagrams &lt;br /&gt;
*Tables with merged columns and rows &lt;br /&gt;
*Nested tables, which may be discovered as multiple tables &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Tables in an Agreement ==&lt;br /&gt;
&lt;br /&gt;
To discover tables in an Agreement:&lt;br /&gt;
&lt;br /&gt;
1. '''Create''' an Agreement (''Third Party Type Of Paper'').&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 2.png|720px|7.9 Table Discovery 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2. '''Ensure''' that the&amp;amp;nbsp;''Clause Discovery'' functionality is turned&amp;amp;nbsp;''On''&amp;amp;nbsp;and the Contract Type is enabled for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 3.png|720px|7.9 Table Discovery 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 3. '''Create and Publish'''&amp;amp;nbsp;the Agreement. ICI automatically queues the Agreement for table discovery.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' To enable discovery, the hooks must be enabled.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Viewing Discovered Tables in an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Tables''&amp;amp;nbsp;tab on the uploaded Agreement&amp;amp;nbsp;''Details'' page.&amp;lt;br/&amp;gt; 2. ICI displays a list of the ''Discovered Tables'' for that Agreement Document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 1.png|720px|7.10 Table Discovery 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Editing Table Data ===&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Edit Table Name ''icon next the table that you want to edit. For example, Table 2.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 1.png|720px|.9 Edit Table Data 1]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Toggle '''the ''Has Header'' button to''Yes'' if you want the table to have a header.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 2.png|720px|.9 Edit Table Data 2]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click''' inside the header box to add the header name. For example, PSE Workers, Term, etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 3.png|720px|.9 Edit Table Data 3]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Click '''''Save Changes ''to save changes if you want to review or edit them later. The Table data saved message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 2.png|720px|7.10 Table Discovery 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select '''the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 5.png|720px|.9 Edit Table Data 5]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. A validation message is displayed to check if you want to save the updated data. '''Click&amp;amp;nbsp;'''''Save'' to update the data in the table, else '''click''' ''Discard''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 6.png|720px|.9 Edit Table Data 6]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Select''' the checkbox for the rows and columns that you want to update.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Edit Table Data 7.png|720px|7.9 Edit Table Data 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click '''''Yes'' if you are sure that you want to update the table and proceed.&lt;br /&gt;
&lt;br /&gt;
11. A message is displayed indicating that the table data is saved and the Associations are being created. '''Click '''''Yes'' if you are sure that you want to update the table and proceed, else click&amp;amp;nbsp;''No''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 3.png|720px|7.10 Table Discovery 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
12. You can view the associations on the ''Associations ''tab.&lt;br /&gt;
&lt;br /&gt;
13.&amp;amp;nbsp;'''Click '''''View Record ''to view the details of the individual records.&lt;br /&gt;
&lt;br /&gt;
14. You can take further action as needed. For example, send it for Approval.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Selecting the Type of Table to be able to create Associations for it ===&lt;br /&gt;
&lt;br /&gt;
You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.&lt;br /&gt;
&lt;br /&gt;
To do so:&lt;br /&gt;
&lt;br /&gt;
1.'''&amp;amp;nbsp;Click''' the ''Tables ''tab on the uploaded Agreement Details page.&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;In the ''Discovered Tables'' window when matching data is present, the exact Associations with that table are discovered. For example, the ''Payment Details ''are&amp;amp;nbsp;discovered. These are associated and the names of the header are also discovered.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 4.png|720px|7.10 Table Discovery 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;You can select whether the table should have a header or not by enabling the ''Has Header ''flag to ''Yes''.&amp;amp;nbsp;&amp;lt;br/&amp;gt; By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the ''Tables ''tab.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 4.&amp;amp;nbsp;In the ''Discovered Tables'' window, make changes in the table as required. For example, '''select''' 3 rows and columns.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Saving the changes of the Table Discovery for the Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Save Changes''. The ''Table data saved'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Table Discovery 5.png|720px|7.10 Table Discovery 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Table Identification for an Agreement ===&lt;br /&gt;
&lt;br /&gt;
You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 1.'''&amp;amp;nbsp;Click''' ''Finish.&amp;amp;nbsp;''A message will be displayed indicating that you will not be able to make any changes to the table data.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Table Discovery 7.png|720px|7.9 Table Discovery 7]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;br/&amp;gt; 2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''&amp;lt;i&amp;gt;Yes&amp;lt;/i&amp;gt; ''if you are certain that you want to make the changes, else you can save changes and review them later.&amp;amp;nbsp;&amp;lt;br/&amp;gt; 3.&amp;amp;nbsp;'''''Click''' ''the ''Associations&amp;amp;nbsp;''tab to see the Associations that are discovered, as shown in the screenshot below:''&amp;amp;nbsp;''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:1080px-7.10 Table Discovery 6 gr actions.png|720px|7.10 Table Discovery 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the ''Payment Details ''association to view the details and send for approval.&amp;lt;br/&amp;gt; 5.&amp;amp;nbsp;'''Click''' ''Export to Excel'' if you want to export the table&amp;amp;nbsp;that has been discovered.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to ''Review Completed''. &lt;br /&gt;
*It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality. &lt;br /&gt;
&lt;br /&gt;
= DiscoverAI - Support for Own Paper =&lt;br /&gt;
&lt;br /&gt;
ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.&lt;br /&gt;
&lt;br /&gt;
'''Note:'''&lt;br /&gt;
&lt;br /&gt;
*Tagging is supported only in Word documents. &lt;br /&gt;
*The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document. &lt;br /&gt;
&lt;br /&gt;
== Discovering Attributes, Clauses, Tables and Obligations ==&lt;br /&gt;
&lt;br /&gt;
To discover attributes, clauses, tables and obligations using own type of paper:&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Own Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 1.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3. '''Select'''&amp;amp;nbsp;''Discover AI'' from the ''Clause Discovery Type'' drop-down and ''ML based''&amp;amp;nbsp;from the&amp;amp;nbsp;''Obligation Discovery Type''&amp;amp;nbsp;drop-down.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 2.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''&amp;amp;nbsp;Note: Select''' the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down for obligation discovery.&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' ''Next. ''The ''Select Template'' page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a template or '''upload''' a file.&lt;br /&gt;
&lt;br /&gt;
6. '''Click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 3.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click''' ''Create and Publish''. The agreement ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the ''Obligation Discovery Type''&amp;amp;nbsp;drop-down) are discovered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 4.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' It may take some time for the discovery process to complete. Click the individual entities below the ''AI Discovery'' tab to view the discovered attributes, clauses, tables and obligations.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Attributes ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Attributes'' tab.&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Save'' to confirm the attributes. You can also modify the discovered attribute values by clicking the ''View potential matching values'' icon and then click ''Save''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 5.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
The AI model will learn and recommend values when:&lt;br /&gt;
&lt;br /&gt;
*The discovered attribute value is incomplete, and the user selects the complete value, such as selecting the complete address line if the system has discovered only partial address &lt;br /&gt;
*Manual corrections are made to incorrectly identified attribute values, such as correction in vendor name &lt;br /&gt;
*A different attribute value is selected using the ''Keep selected text'' option &lt;br /&gt;
&lt;br /&gt;
The newly learnt values will, from thereon, be presented as default to the user and any changes will continue to be learnt and recommended by the AI model.&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
3. The ''Metadata Save Confirmation'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 6.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''There will be now be 2 versions of the agreement.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 7.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' '''Click''' ''Save Draft'' in Step 2 to save the selected attribute values; this will not create a new version.&amp;lt;/div&amp;gt; &lt;br /&gt;
5. '''Download''' the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 8.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 8.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note:''' If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will trigger, but the attributes that were already confirmed and tagged to the agreement are not discovered. However, they will be displayed, as shown in the screenshot below:&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 9.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Tagging Discovered Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Clauses'' tab. The discovered clauses are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 10.PNG|720px|7.10 Discover AI Obligation AI Support for Own Paper 10.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Take '''actions (such as ''Confirm, Confirm with Deviation, Ignore, Review Later'') on the discovered clauses.&lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Finish ''to complete the review process, as shown in the screenshot below:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 11.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 11.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Versions'' tab. A new version of the agreement is created in both Word and PDF formats.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 12.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 12.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Download''' the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.10 Discover AI Obligation AI Support for Own Paper 13.png|720px|7.10 Discover AI Obligation AI Support for Own Paper 13.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Note''':&lt;br /&gt;
&lt;br /&gt;
*If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed. &lt;br /&gt;
*Only when the agreement is published, the clauses that you confirm on clicking ''Finish'' will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details'' page. &lt;br /&gt;
*A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Inbuilt Discovery of Attributes and Clauses =&lt;br /&gt;
&lt;br /&gt;
Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.&lt;br /&gt;
&lt;br /&gt;
Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.&lt;br /&gt;
&lt;br /&gt;
The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:&lt;br /&gt;
&lt;br /&gt;
*'''Attributes: '''''Party Name'', ''Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law,&amp;amp;nbsp;Notice Period For Termination,&amp;amp;nbsp;LiabilityType'' and ''ComplianceType'' &lt;br /&gt;
&lt;br /&gt;
'''Note: '''The ''Contract Value'' attribute supports the following currencies - USD, CAD, EUR, INR and CAN&lt;br /&gt;
&lt;br /&gt;
*'''Clauses:''' ''Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination'',&amp;amp;nbsp;''Waiver,&amp;amp;nbsp;Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability and Uncapped'' &lt;br /&gt;
&lt;br /&gt;
In this release, we have extended the discovery support to URL datatype attributes. ''DiscoverAI'' &amp;amp;nbsp;would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Discovering Common Attributes and Clauses ==&lt;br /&gt;
&lt;br /&gt;
1. '''Create '''an agreement using ''Third Party Type of Paper''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 1.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Upload''' a file and '''click''' ''Next''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 2.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click''' ''Create and Publish''. The agreement ''Details'' page opens.&lt;br /&gt;
&lt;br /&gt;
The most common attributes and clauses from the agreement document that you uploaded in Step 3 are discovered and displayed in the ''Attributes'' and ''Clauses'' tab, as shown in the screenshots below for Attributes and Clauses respectively:&lt;br /&gt;
&lt;br /&gt;
'''Attributes:'''&lt;br /&gt;
&lt;br /&gt;
*'''Click '''the ''View potential matching values'' icon next to the discovered attribute values to take actions on them such as ''Accept, Reject or Keep Selected Text.&amp;amp;nbsp;'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 3.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*The attribute values are normalized and displayed based on the defined rules. For example, the ''Effective Date'' is displayed in the ICI-supported format, as shown in the screenshot below: &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 4.png|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
'''Clauses:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;'''[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG|720px|71.0 Out-of-the-Box Support for Attributes and Clauses 5.PNG]]'''&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses based on ''Action Status'', ''Clause categories ''and ''Confidence''. &lt;br /&gt;
&lt;br /&gt;
*&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;The level of confidence associated with ''Discovered'' ''Clauses'' is displayed using different color indicators to depict ''High (green)'', ''Medium (orange)'' and ''Low'' (''pink'') confidence. All discovered clauses have the ''Review'' link next to them until you click it to take an action (such as ''Confirm'', ''Confirm with Deviation'', ''Ignore ''or ''Review Later''). In addition, clauses with obligations have the&amp;amp;nbsp;&amp;amp;nbsp;[[File:71.0 Out-of-the-Box Support for Attributes and Clauses 6.PNG|RTENOTITLE]]&amp;amp;nbsp;&amp;amp;nbsp;icon next to them. You can click the icon to view the obligations.&amp;lt;/div&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
*Click the ''Finish'' button to complete the review process. &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== eDiscovery using AI ==&lt;br /&gt;
&lt;br /&gt;
With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.&lt;br /&gt;
&lt;br /&gt;
With eDiscovery using AI:&lt;br /&gt;
&lt;br /&gt;
*ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually &lt;br /&gt;
*Auto confirmed clauses can be searched same as any other agreement clauses. &lt;br /&gt;
*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses. &lt;br /&gt;
*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically. &lt;br /&gt;
*While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category. &lt;br /&gt;
&lt;br /&gt;
This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:&lt;br /&gt;
&lt;br /&gt;
#'''Configure''' an ''Agreement Contract Type'' specific to eDiscovery. While configuring the attributes for the agreement contract type, the ''eDiscovery Mode'' and ''Clause Discovery Type'' attributes must be added. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 00.png|420px|Discover AI eDiscovery 00.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Configure '''a ''Masterdata Contract Type ''named ''EDiscoveryAutoConfirmList.&amp;amp;nbsp;''It should contain two attributes:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Contract Type ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Clauses ''(''Datatype: String'')&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create '''Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Contract Type'' name for eDiscovery (created in Step 1).&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Specify''' the ''Clauses''&amp;amp;nbsp;that need to be auto-confirmed post eDiscovery, for example ''preamble, payment terms ''and''signature.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:Discover AI eDiscovery 01.png|520px|Discover AI eDiscovery 01.png]]''&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Create''' an Agreement using a contract type configured for eDiscovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 02.png|520px|Discover AI eDiscovery 02.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Next'', the ''Attributes'' page opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' an Agreement file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''Clause Discovery Type'' as ''Discover AI''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 03.png|520px|Discover AI eDiscovery 03.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The eDiscovery Mode functionality is only available when the ''Clause Discovery Type Discover AI'' is selected.&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select''' the ''eDiscovery Mode.''&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The eDiscovery Mode attribute has 3 options: ''None, Auto ''and''Manual Review.''&lt;br /&gt;
&lt;br /&gt;
*'''Auto''': By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses. &lt;br /&gt;
*'''Manual Review''': By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the ''Finish'' button. &lt;br /&gt;
*'''None''': By selecting this option, the user can opt out of eDiscovering clauses in the agreements. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;9&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Create and Publish''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Go to the ''Agreement Details'' page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;In the ''AI Discovery'' tab, click ''Clauses'' to trigger the Clause Discovery.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:Discover AI eDiscovery 04.png|720px|Discover AI eDiscovery 04.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;12&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This functionality can especially be leveraged for legacy upload for bulk upload scenarios as well.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== UX revamp to display discovered entities and original document side-by-side ==&lt;br /&gt;
&lt;br /&gt;
Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.&amp;lt;br/&amp;gt; With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page.&amp;amp;nbsp;&amp;lt;br/&amp;gt; When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new tab/window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#'''Create '''an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement ''Details ''page is displayed. The ''AI Discovery'' tab shows an hourglass icon to indicate that the discovery is in progress. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 1.png|720px|7.12 AIML UX 1.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Hover '''over the hourglass icon to view the discovery progress in percentage. If the discovery is complete for one or more than one entities, the ''View ''icon is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 2.png|720px|7.12 AIML UX 2.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''View ''icon. A new page opens, displaying tabs for the discovered Clauses, Attributes, Table and Obligations, with a parallel view of the agreement document for each entity. The Clauses tab is displayed first by default.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Table and Obligation discovery tabs are only displayed if these&amp;amp;nbsp;are present in the agreement document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;4&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''on the clause which you want to review, for example ''non solicitation''. The ''Document View'' section displays the page of the document where this clause is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 3.png|720px|7.12 AIML UX 3.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the clause you want to review. The ''Library clause comparison with discovered clause'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 4.png|720px|7.12 AIML UX 4.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;6&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Take '''actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review process. The ''Clause discovery progress saved'' message is displayed and the ''Discovered Clauses Status'' changes to ''Review Completed''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 5.png|720px|7.12 AIML UX 5.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;8&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Clause Data'' if you want to export the clause which has been discovered.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Attributes ''tab. Similar to clauses, the discovered attributes and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the attribute is present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 6.png|720px|7.12 AIML UX 6.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;11&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Available suggestions will be displayed for the discovered attributes. '''Click '''the suggestions, for example ''3 suggestion(s)'' to view the potential matching values.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the appropriate value, for example ''$ 3,250,000.00''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click''' ''Accept ''to add the value to the respective attribute, for example ''Contract Value''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 7.png|720px|7.12 AIML UX 7.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;14&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save''. The ''Your data has been saved successfully'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Tables ''tab. Similar to attributes, the discovered tables and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the table is present. &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 8.png|720px|7.12 AIML UX 8.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;17&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Edit Table Name'' icon next the table that you want to edit. For example, Table 1.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Toggle '''the ''Has Header'' flag to ''Yes ''if you want the table to have a header.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 9.png|720px|7.12 AIML UX 9.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;19&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside the header box to add the header name. For example, SKU Name, Service Name, etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 10.png|720px|7.12 AIML UX 10.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;21&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Select '''the checkbox for the rows and columns that you want to update.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Save Changes ''to save changes if you want to review or edit them later.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish''. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 11.png|720px|7.12 AIML UX 11.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;24&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Yes ''if you are sure that you want to update the table and proceed.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the ''Obligations ''tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The ''Document View'' section displays the page of the document where the obligations are present.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 12.png|720px|7.12 AIML UX 12.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;26&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Review ''on the obligation you want to review. The ''Library Obligation comparison with discovered Obligation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 13.png|720px|7.12 AIML UX 13.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;27&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The following actions can be taken on selected Obligation:&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Click '''''Confirm ''to confirm the Obligation. &lt;br /&gt;
*'''Click '''''Review Later'' if you are unsure and want to review the Obligation later. &lt;br /&gt;
*'''Click '''''Ignore ''to ignore the Obligation. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;28&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Metadata ''to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on.&amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Parent Clause'' to see the parent Clause that the Obligation is linked to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Finish ''to complete the review and continue with the workflow as expected. The ''Obligation Save Confirmation'' window opens.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 14.png|720px|7.12 AIML UX 14.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;32&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Mark Confirmed, Mark Ignored'' or ''Cancel ''as required. The obligations are marked as ''Review Completed'' and the ''Obligation discovery progress saved'' message is displayed.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;[[File:7.12 AIML UX 15.png|720px|7.12 AIML UX 15.png]]&amp;lt;/div&amp;gt; &amp;lt;ol start=&amp;quot;33&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Ok''.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''''Export Obligation Data'' to export the Obligation information to an Excel file.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 16.png|720px|7.12 AIML UX 16.png]]&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Using Filters ===&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; '''Click '''''Filters ''on the clauses tab. The ''Document View'' tab minimizes and the filters panel is displayed.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 17.png|720px|7.12 AIML UX 17.png]]&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status. &lt;br /&gt;
*The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the &amp;amp;nbsp; &amp;amp;nbsp; icon next to them. You can click the icon to view the obligations. &lt;br /&gt;
*Click the ''Finish ''button to complete the review process. &lt;br /&gt;
&amp;lt;ol start=&amp;quot;35&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Click '''the link above the tabs to go back to the agreement ''Details ''page.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12 AIML UX 18.png|720px|7.12 AIML UX 18.png]]&amp;amp;nbsp;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Only when the agreement is published, the clauses that you confirm on clicking ''Finish ''will be saved as ICI clauses and displayed in the ''Agreement Clauses'' tab on the ''Details ''page.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking ''Finish''.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Auto-scroll will not work if the discovery process has already been carried out on a document.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;Page navigation to the selected clause, attribute, etc. in the ''Document View'' is currently not supported on Internet Explorer 11.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:'''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|Obligation Management]] |&amp;amp;nbsp;[[Managing_US_Federal_Contracts_using_ICM|Managing US Federal Contracts using&amp;amp;nbsp;ICI]]&amp;amp;nbsp; |&amp;amp;nbsp;[[Contract_Digitalization|Contract Digitalization]]&amp;amp;nbsp;| [[Negotiate_AI|NegotiateAI]] | [[Obligation_AI|ObligationAI]] | [[Visualize_AI|VisualizeAI]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Pages with broken file links]]&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14297</id>
		<title>Icertis Business Apps</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14297"/>
				<updated>2020-08-12T08:54:24Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICM Business Applications =&lt;br /&gt;
&lt;br /&gt;
ICM Business Applications, built on the Icertis Contract Management (ICM) platform, help customers address specific business requirements and get even more out of their investment in the ICM platform.&lt;br /&gt;
&lt;br /&gt;
== ICM Sourcing Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing application places contracts at the center of the sourcing process to ensure compliance, minimize risk, and create long term strategic agility. Get full visibility into supplier’s risk profile and ensure compliance throughout the procurement process. Leverage AI/ML based contract terms and clause recommendations to better negotiate RFx events and surface opportunities for savings. Perform side-by-side analysis of bids or proposals, and score them with both qualitative and quantitative criteria. Get a complete view of your relationship with suppliers including current and past contracts, historical performance and complete risk profile for a unified view for sourcing events.&lt;br /&gt;
&lt;br /&gt;
== ICM Obligation Management Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Obligation Management application enables companies to better manage their commitments and to realize the full value of their entitlements. This helps optimize business performance, and protects organizations from reputational, commercial and financial risks. Built on the ICM platform and infused with artificial intelligence, the new app transforms how organizations identify, create, manage and fulfill obligations that were previously hidden in complex contract language. The app includes automatic obligation discovery, powerful rule-based obligation ownership, workflow tools to ensure seamless obligation fulfillment, and sophisticated analytics – all designed to protect your business and maximize the ROI of your relationships.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''Extend Contract Type definition to be able to describe the Application Type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICM offers the ability to determine the Application Type (''Contracting'',&amp;amp;nbsp;''Sourcing'',&amp;amp;nbsp;''Proposal'',&amp;amp;nbsp;''Obligation Management'', and&amp;amp;nbsp;''Supplier Lifecycle Management'') when creating a Contract Type.&amp;amp;nbsp;The access privileges for Business Applications such as Sourcing, are driven through Security Groups.&lt;br /&gt;
&lt;br /&gt;
== ICM Risk Management Application ==&lt;br /&gt;
&lt;br /&gt;
The Icertis&amp;amp;nbsp; Risk Management application to make it easier for professionals to carry out their tasks related to risk management such as assessment, due diligence, remediation, monitoring and reassessment. Risk Management is the process of identifying the potential risk, assessing the magnitude of risk based on the business objectives and devising strategies to mitigate them and tracking the performance until they are completely mitigated.&lt;br /&gt;
&lt;br /&gt;
The platform’s modern, scalable and integration friendly cloud architecture can model even the most complex risk management scenarios. It enables secure communication with different parties involved in the process of risk management that is more effective than the traditional ways of communication such as email. Its user-friendly interface makes it possible for anyone in the enterprise, from the risk management personnel to the supply analytics team, to be able to use the platform with ease.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:''' [[ICM_Sourcing_App|ICM Sourcing App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|ICM Obligation Management App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[ICM_Risk_Management_App|ICM_Risk_Management_App]] |&amp;amp;nbsp;&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14295</id>
		<title>Icertis Business Apps</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14295"/>
				<updated>2020-08-12T08:47:34Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICM Business Applications =&lt;br /&gt;
&lt;br /&gt;
ICM Business Applications, built on the Icertis Contract Management (ICM) platform, help customers address specific business requirements and get even more out of their investment in the ICM platform.&lt;br /&gt;
&lt;br /&gt;
== ICM Sourcing Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing application places contracts at the center of the sourcing process to ensure compliance, minimize risk, and create long term strategic agility. Get full visibility into supplier’s risk profile and ensure compliance throughout the procurement process. Leverage AI/ML based contract terms and clause recommendations to better negotiate RFx events and surface opportunities for savings. Perform side-by-side analysis of bids or proposals, and score them with both qualitative and quantitative criteria. Get a complete view of your relationship with suppliers including current and past contracts, historical performance and complete risk profile for a unified view for sourcing events.&lt;br /&gt;
&lt;br /&gt;
== ICM Obligation Management Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Obligation Management application enables companies to better manage their commitments and to realize the full value of their entitlements. This helps optimize business performance, and protects organizations from reputational, commercial and financial risks. Built on the ICM platform and infused with artificial intelligence, the new app transforms how organizations identify, create, manage and fulfill obligations that were previously hidden in complex contract language. The app includes automatic obligation discovery, powerful rule-based obligation ownership, workflow tools to ensure seamless obligation fulfillment, and sophisticated analytics – all designed to protect your business and maximize the ROI of your relationships.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''Extend Contract Type definition to be able to describe the Application Type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICM offers the ability to determine the Application Type (''Contracting'',&amp;amp;nbsp;''Sourcing'',&amp;amp;nbsp;''Proposal'',&amp;amp;nbsp;''Obligation Management'', and&amp;amp;nbsp;''Supplier Lifecycle Management'') when creating a Contract Type.&amp;amp;nbsp;The access privileges for Business Applications such as Sourcing, are driven through Security Groups.&lt;br /&gt;
&lt;br /&gt;
== ICM Risk Management Application ==&lt;br /&gt;
&lt;br /&gt;
The Icertis&amp;amp;nbsp; Risk Management application to make it easier for professionals to carry out their tasks related to risk management such as assessment, due diligence, remediation, monitoring and reassessment. Risk Management is the process of identifying the potential risk, assessing the magnitude of risk based on the business objectives and devising strategies to mitigate them and tracking the performance until they are completely mitigated.&lt;br /&gt;
&lt;br /&gt;
The platform’s modern, scalable and integration friendly cloud architecture can model even the most complex risk management scenarios. It enables secure communication with different parties involved in the process of risk management that is more effective than the traditional ways of communication such as email. Its user-friendly interface makes it possible for anyone in the enterprise, from the risk management personnel to the supply analytics team, to be able to use the platform with ease.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:''' [[ICM_Sourcing_App|ICM Sourcing App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|ICM Obligation Management App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[ICM_Risk_Management_App|ICM_Risk_Management_App]] |&amp;amp;nbsp;[[ICM_Mobile_App|ICM Mobile App]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14293</id>
		<title>Icertis Business Apps</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14293"/>
				<updated>2020-08-12T08:43:32Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICM Business Applications =&lt;br /&gt;
&lt;br /&gt;
ICM Business Applications, built on the Icertis Contract Management (ICM) platform, help customers address specific business requirements and get even more out of their investment in the ICM platform.&lt;br /&gt;
&lt;br /&gt;
== ICM Sourcing Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing application places contracts at the center of the sourcing process to ensure compliance, minimize risk, and create long term strategic agility. Get full visibility into supplier’s risk profile and ensure compliance throughout the procurement process. Leverage AI/ML based contract terms and clause recommendations to better negotiate RFx events and surface opportunities for savings. Perform side-by-side analysis of bids or proposals, and score them with both qualitative and quantitative criteria. Get a complete view of your relationship with suppliers including current and past contracts, historical performance and complete risk profile for a unified view for sourcing events.&lt;br /&gt;
&lt;br /&gt;
== ICM Obligation Management Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Obligation Management application enables companies to better manage their commitments and to realize the full value of their entitlements. This helps optimize business performance, and protects organizations from reputational, commercial and financial risks. Built on the ICM platform and infused with artificial intelligence, the new app transforms how organizations identify, create, manage and fulfill obligations that were previously hidden in complex contract language. The app includes automatic obligation discovery, powerful rule-based obligation ownership, workflow tools to ensure seamless obligation fulfillment, and sophisticated analytics – all designed to protect your business and maximize the ROI of your relationships.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''Extend Contract Type definition to be able to describe the Application Type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICM offers the ability to determine the Application Type (''Contracting'',&amp;amp;nbsp;''Sourcing'',&amp;amp;nbsp;''Proposal'',&amp;amp;nbsp;''Obligation Management'', and&amp;amp;nbsp;''Supplier Lifecycle Management'') when creating a Contract Type.&amp;amp;nbsp;The access privileges for Business Applications such as Sourcing, are driven through Security Groups.&lt;br /&gt;
&lt;br /&gt;
== ICM Risk Management Application ==&lt;br /&gt;
&lt;br /&gt;
The Icertis&amp;amp;nbsp; Risk Management application to make it easier for professionals to carry out their tasks related to risk management such as assessment, due diligence, remediation, monitoring and reassessment. Risk Management is the process of identifying the potential risk, assessing the magnitude of risk based on the business objectives and devising strategies to mitigate them and tracking the performance until they are completely mitigated.&lt;br /&gt;
&lt;br /&gt;
The platform’s modern, scalable and integration friendly cloud architecture can model even the most complex risk management scenarios. It enables secure communication with different parties involved in the process of risk management that is more effective than the traditional ways of communication such as email. Its user-friendly interface makes it possible for anyone in the enterprise, from the risk management personnel to the supply analytics team, to be able to use the platform with ease.&lt;br /&gt;
&lt;br /&gt;
== &amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:''' [[ICM_Sourcing_App|ICM Sourcing App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|ICM Obligation Management App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[ICM_Risk_Management_App|ICM_Risk_Management_App]] |&amp;amp;nbsp;[[ICM_Mobile_App|ICM Mobile App]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Working_with_RFx&amp;diff=14252</id>
		<title>Working with RFx</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Working_with_RFx&amp;diff=14252"/>
				<updated>2020-08-11T17:29:52Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Working with RFx Instances =&lt;br /&gt;
&lt;br /&gt;
The Icertis Sourcing app enables buyers to create and manage end-to-end RFx process. RFx is an acronym for Request for '''x''', where '''x''' may stand for ''Information ''or''Proposal ''or ''Quotation''. Buyers can create an RFx instance, add line items, select suppliers and supplier contacts, create agreements with the suppliers, add team members to the instance for review and approval process and send the instance for approval. Here is the RFx workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing RFX Instances 1.png|720px|7.9 Sourcing RFX Instances 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating the RFx Instance ===&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Sourcing'' tile on the ''Dashboard''. The ''Sourcing'' page opens. A list of all the RFx instances is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SourcingTile.PNG|720px|7.12-SourcingTile.PNG]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2.&amp;amp;nbsp;'''Click '''the ''Create RFx'' tile. The ''Create RFx'' page opens.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;3.&amp;amp;nbsp;'''Select '''a Sourcing Entity from the ''Select Sourcing Entity'' drop-down in the ''Contract Type Details'' ''(Step 1 of 4)'' section. The contract type is configured in the system with default Attributes.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;4.&amp;amp;nbsp;'''Click''' ''Next''. The ''Attributes'' ''(Step 2 of 4)'' page opens. The attributes are grouped under various categories. For example, ''RFx Information'', ''RFx Configs, etc''.&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Select '''or&amp;amp;nbsp;'''enter '''the values for all the required Attributes in the ''RFx Information'' group:&lt;br /&gt;
&lt;br /&gt;
*Enter the RFx Name. For example, ''Procurement for Admin department''. &lt;br /&gt;
*Enter the information of the RFx instance in the ''Description'' field. &lt;br /&gt;
*Select an ''AppSrc Category'' from the drop-down. For example, ''Office Supplies''. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can also add a new category by clicking the plus icon next to&amp;amp;nbsp;''Category'' option.&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select '''the ''Round Start Date'' and ''Round End Date''. When you enter the dates, a round is created automatically as soon as the RFx instance is approved. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing RFX Instances 5.png|720px|7.9 Sourcing RFX Instances 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select''' appropriate values and settings under the ''RFx Configs'' group.&lt;br /&gt;
&lt;br /&gt;
*''View Bids'': '''Select''' an appropriate option from the drop-down. There are following options: &lt;br /&gt;
**''Sealed Envelope'': When you select this option, the bid and bid responses are not visible to the buyer until the round is closed. &lt;br /&gt;
**''Open RFx'': When you select this option, the bid and bid responses are visible to the buyer throughout the duration of the round, as and when the supplier submits the bid.   &lt;br /&gt;
&lt;br /&gt;
*'''Select''' ''Yes'' or ''No'' for the following Configuration settings as per your requirement: &lt;br /&gt;
**''Auto Copy Bids from Previous Rounds: '''''Select '''''Yes ''if you want to allow copying bids from previous rounds to the new round. This displays the bids from the current rounds and the bid responses with values added in the most recently closed round in ''Draft ''state to the suppliers. The default value for this option is set to ''Yes.&amp;amp;nbsp;'' &lt;br /&gt;
**''Allow Foreclosure of Rounds'': '''Select''' ''Yes'' if you want to close the round before the selected round end date. This displays the ''Close Round ''button on the ''Round Details ''page to close the round manually. If you select ''No, ''then the round will be closed automatically only after the selected round end date. The default value for this option is set to ''Yes.'' &lt;br /&gt;
**''Allow New Supplier During RFx Phase'': '''Select''' ''Yes'' if you want to allow new supplier(s) to be added during the entire RFx lifecycle. However, the newly added supplier(s) can participate in a new round only, not in an ongoing round. The default value for this option is set to ''No.''   &lt;br /&gt;
&lt;br /&gt;
*'''Enter '''the ''Terms For Participation'' in the given field. They will be visible to the suppliers only if the buyer adds it when creating the RFx. The suppliers should accept the Terms before they can participate in the bidding process of the RFx. For example, if a supplier has multiple contacts and if one of the contacts accepts the terms for participation, then other contacts are not required to take any action on that and the ''Terms for Participation ''will not be displayed to the remaining contacts. &lt;br /&gt;
*''Allow New Line Item During RFx Phase'': '''Select''' ''Yes'' if you want to allow new line items to be added during the entire RFx lifecycle, However, the newly added line item(s) can be part of a round only before it starts and not in an ongoing round. The default value of this option is set to ''No.'' &lt;br /&gt;
*'''Select''' the following contracts (if applicable) by clicking&amp;amp;nbsp;the drop-down arrow or the ''Lookup Search icon:'' &lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Associate Contracts'': Sourcing app allows the buyers to create contracts such as NDA, for all the suppliers selected when creating RFx. A separate contract will be created for each supplier.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Mandatory Contracts'': It is the contract that should be present for all the suppliers before the RFx moves to the next phase. The value in this option will be populated automatically based on the value selected in the earlier option. You cannot select any value in this option if you don’t select anything in the&amp;amp;nbsp;''Associate Contracts ''option.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Prerequisite Contracts'': The Supplier can access the RFx instance only after it is in ''Approved'' state. After the Round is started, a ''Terms for Participation ''window is displayed to the supplier with an option to accept or decline. The Suppliers can access the RFx only after they sign the Prerequisite Contract after accepting the terms for participation. If the Suppliers do not sign the contracts a message is displayed by ICM, along with a list of documents asking the suppliers to complete the documents before accessing the RFx.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The values selected in these fields are populated on the RFx ''Details'' page under the ''Agreements'' tab. This enables the buyer to create Agreements relevant to the RFx that is created.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Selecting an Associate Contract automatically populates the values in ''Mandatory Contracts ''and ''Prerequisite Contracts. ''If you do not select any values in any of the contracts, these values be displayed as blank when you create the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
The attributes for mandatory and prerequisite contracts are interlinked and both the attributes display the list of different contract types that can be associated with the RFx. ICM validates whether the prerequisite and mandatory contracts added to the RFx are in ''Approved'' state.&lt;br /&gt;
&lt;br /&gt;
*Primary Currency: '''Select''' the primary currency for the RFx. If the user preferred currency is not added in the currency master, then the corporate currency is set as the primary currency of the RFx. For example, if user preferred currency is SGD which is not added in currency master, then the primary currency is set as USD assuming it is set as the corporate currency.&amp;amp;nbsp; &lt;br /&gt;
*Allowed Currency:&amp;amp;nbsp;'''Select''' the allowed currency for the RFx. This is the currency allowed by the buyers for the suppliers operating from a different country. The selected allowed currencies can be used by suppliers for bidding. Suppliers can view the newly added currencies even when the round is Open and select them as required. Buyers can update the allowed currency at any time using ''Modify RFx'' option. The allowed currencies cannot be deleted after the RFx is approved. &lt;br /&gt;
*Exchange Rate Basis:Buyers can view the exchange rate throughout the RFx lifecycle by clicking the View Exchange Rate Table icon at RFx, Line Items, Bids, Bid Responses. The exchange rate basis can have one of the following values: &lt;br /&gt;
**RFx Open Date: This is selected by default.&amp;amp;nbsp;When this is selected, system uses the start date of first round for determining exchange rates &lt;br /&gt;
**RFx Closed Date: This date must be selected same as the round end date. When this is selected, system uses close date of the last round for determining applicable exchange rates &lt;br /&gt;
**User selected: This is the date from when the exchange rates are made applicable by the buyers. It is mandatory to select the Exchange Rate Date that is enabled after selecting User Selected as the Exchange Rate Basis. The selected date is used as the date to determine the exchange rate and all calculations of currency conversion.&amp;amp;nbsp;Buyers can view the exchange rate information when selecting the Exchange Rate Basis as RFx Open Date or RFx Closed Date after the RFx is approved and the round is created.   &lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Click''' ''Next''. The ''Select Template'' ''(Step 3 of 4)'' page opens. This is an optional step depending upon how the application is configured. Usually there would be only one template associated with the RFx that is selected automatically. However, multiple templates can be configured in ICM as per the business requirement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;8.&amp;amp;nbsp;'''Click''' ''Next''. The ''Verify'' ''(Step 4 of 4)'' page opens. Verify all the information you have just entered.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;9.&amp;amp;nbsp;'''Click''' the ''Create RFx'' button. The RFx ''Details'' page opens.&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== RFx Details Page ===&lt;br /&gt;
&lt;br /&gt;
Buyers can view the current status and details of the RFx in various sections of the left navigation pane on ''RFx Details'' page. Buyers can also perform a variety of actions based on the current state of the RFx.&lt;br /&gt;
&lt;br /&gt;
Here is a brief description of the options in the left navigation pane of ''RFx Details ''page.&lt;br /&gt;
&lt;br /&gt;
*RFx Information: This section displays the basic details of the current RFx instance. It has the following sub-sections. &lt;br /&gt;
**Summary: Displays the name of the RFx instance (that is added while creating), who created it, and RFx instance details. &lt;br /&gt;
**Details: Displays the details specified while creating the RFx instance. &lt;br /&gt;
**Preview: Displays how the RFx document would actually look. '''Click '''the ''click here ''in ''To see full document click here ''to download and view the full document in pdf format.   &lt;br /&gt;
*RFx Package: This section displays the following details. &lt;br /&gt;
**Line Items: '''Click '''this option to view the list of line items associated with the RFx. '''Click '''the plus icon next to ''Line Items ''on RFx ''Details'' page to add a new line item. &lt;br /&gt;
**Internal Attachments: Displays the list of existing internal attachments associated with the RFx. Internal attachments are associated documents uploaded by the buyers and only available to the buyer team. '''Click '''the plus icon next to internal attachments to add new to the list. &lt;br /&gt;
**External Attachments: Displays the list of existing external attachments associated with the RFx. External attachments are associated documents uploaded by the buyers and available to both buyers and suppliers. '''Click '''the plus icon next to external attachments to add new to the list.   &lt;br /&gt;
*Supplier Information: Displays the list of existing suppliers and allows buyers to add new suppliers along with their contact information. &lt;br /&gt;
**Suppliers: Displays the list of suppliers added to the RFx created by the buyer. '''Click '''the plus icon next to ''Suppliers ''to add a new supplier. &lt;br /&gt;
**Supplier Contacts: Displays the list of supplier contacts that are populated automatically after you select the suppliers in the previous step.   &lt;br /&gt;
*Agreements: Displays all the agreements that were selected initially when creating the RFx. &lt;br /&gt;
*Collaboration: Allows the internal or external team members to communicate with other internal or external team members by creating topics and posting messages in it. &lt;br /&gt;
*Round: Displays the list of rounds associated with the RFx along with their current state. '''Click '''the plus icon next to Round to add a new round. &lt;br /&gt;
*Awarding: Displays the RFx instance awarded to the supplier. After the rounds are closed and awarding is initiated by the buyer, an awarding object is created. &lt;br /&gt;
*Team: Displays the members added to the team for this RFx instance. '''Click '''the plus icon to add new team members to the RFx. &lt;br /&gt;
*Notes: Displays the additional information about the RFx if it is added. &lt;br /&gt;
*History: Displays how the RFx has progressed till now. The actions performed by the buyer are displayed by the buyer on the RFx instance are displayed under ''History'' in the left navigation pane on RFx ''Details'' page. &lt;br /&gt;
&lt;br /&gt;
Buyers can perform the following actions from the ''RFx Details ''page:&lt;br /&gt;
&lt;br /&gt;
*''Download RFx Document: '''''Click '''this button to download the RFx document in Microsoft Word format. The downloaded document is based on the template selected while creating the RFx instance. &lt;br /&gt;
*Edit: '''Click '''this button to go back and make changes to the RFx that you created. &lt;br /&gt;
*Send for Approval: '''Click '''this button to send the RFx instance for approval. &lt;br /&gt;
*Download Package: '''Click '''this button to download the RFx instance along with all its associations. You can select specific associations that you want to download or select the RFx instance checkbox to download the RFx package. RFx package is downloaded as a zip file that contains all the attachments relevant to the RFx. When the zip file is exported on user’s local machine, a folder structure is created that resembles the RFx structure, and the files are located in the respective locations.The files names will be the same when downloading or uploading them to ICM. The files will be downloaded as per the defined folder structure and folder naming conventions&amp;amp;nbsp;which helps users to easily identify files under individual folders of the RFx and avoid any discrepancies.&amp;amp;nbsp;The folder names for associations are now same as the contract type display names such as line items, internal attachments, round, bid response and so on.Downloading the RFx package displays the folders for RFx, round, bid, RFI Response as they are displayed in ICM. The rounds and bids folders are merged in a single folder and the template files are added to the relevant round or bid folder. This is applicable for RFx and RFI.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
*Delete: '''Click '''this button to delete the RFx instance. After deleting the RFx instance, the ''Sourcing ''page opens and the deleted RFx will not be available on the user interface. &lt;br /&gt;
&lt;br /&gt;
=== Copy RFx&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can copy the RFx which not only saves time but also reduces duplication of efforts. Additionally global sourcing involves globally distributed buyer team that may clone the sourcing event at the regional level and link them with one another. Linking the copied RFx to the original RFx can be achieved by selecting&amp;amp;nbsp;''Yes ''next to&amp;amp;nbsp;''Link to RFx&amp;amp;nbsp;''on&amp;amp;nbsp;''Copy Record&amp;amp;nbsp;''window.&lt;br /&gt;
&lt;br /&gt;
Along with the RFx, users now have the ability to select any associated documents (parent-child or peer associations) where the Allow Copy with Associations is set to Yes at the Contract Type level. If this flag is set to ''No'', then only the RFx will be copied without its associations.&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Copy the Sourcing event. &lt;br /&gt;
*Select and copy associations such as line items, questions, questionnaires, suppliers, supplier contacts, internal and external attachments, and commitments.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Copying the RFx helps:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Exclude associations from being copied. &lt;br /&gt;
*Exclude the attributes of associations &lt;br /&gt;
*Exclude the automatic attachments from being copied to the new RFx &lt;br /&gt;
&lt;br /&gt;
Users can copy the RFx team based on the configured role. If RFx is copied by a user who is not primary owner of that RFx, then that user becomes the primary owner of the RFx.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Viewing the audit log by clicking&amp;amp;nbsp;''History&amp;amp;nbsp;''on RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. &lt;br /&gt;
&lt;br /&gt;
If the source role and target role is configured, the user roles will be same for the RFx being copied.&lt;br /&gt;
&lt;br /&gt;
If the source role is:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Primary owner and the same user is copying the current RFx, then target role is ignored (the copying user is part of the team as primary owner)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Same as target role, then team member role is set as source role&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the target role is:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Primary owner, then a log gets added and the team member role is set as source role. For the rest of role mappings, the target role properties are set for the team member. If they are blank, then a log gets added and no action taken.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Authorized users can configure the Agreement Contract Type and set ''Allow Copy with Associations'' field to ''Yes'' to enable copying the existing RFx.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;You can copy an RFx from the:&lt;br /&gt;
&lt;br /&gt;
*''Sourcing index&amp;amp;nbsp;''page &lt;br /&gt;
*RFx&amp;amp;nbsp;''details&amp;amp;nbsp;''page &lt;br /&gt;
&lt;br /&gt;
To copy an RFx from the&amp;amp;nbsp;''Sourcing&amp;amp;nbsp;''index page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''dots&amp;amp;nbsp;next to the RFx on the Sourcing index page and then '''click&amp;amp;nbsp;'''''Copy Record''. The ''Copy Record'' window opens''.''&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' ''Yes'' next to ''Link To RFx'' that is being copied.&amp;amp;nbsp;This links the RFx copy that is being created with the source RFx. If you select No, it will not be linked with the source RFx. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.'''Click''' ''Copy Record'' to copy the RFx without the associations. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.'''Click''' ''Expand All'' on the ''Copy Record'' window to display all the associations of the RFx to be copied. You can click ''Collapse All'' to display only the parent level associations.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select''' the ''Associations'' checkbox to select all the associations of the RFx to copy. You can select specific associations that you want to copy.&amp;amp;nbsp;You can select the commitments from the Copy Record window to be copied from the source RFx to the destination RFx.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Copy''. The name of the copied RFx is same as the source RFx. The ''Initiate RFx'' button is displayed on RFx Details page after the copy of the RFx is created.The primary owner of the copied RFx will be the&amp;amp;nbsp;user who initiates the copy operation.&lt;br /&gt;
&lt;br /&gt;
The RFx copy is created and RFx ''Details ''page opens with the status of the RFx as ''Draft.''&lt;br /&gt;
&lt;br /&gt;
To copy the RFx from RFx ''Details ''page:&lt;br /&gt;
&lt;br /&gt;
The RFx can also be copied from RFx ''Details ''page by following steps 2-5 in the To copy RFx from Sourcing Index page section.&lt;br /&gt;
&lt;br /&gt;
'''Viewing the audit log of Copy RFx'''&lt;br /&gt;
&lt;br /&gt;
You can view the audit log of the copy RFx event by clicking ''History ''on the RFx ''Details ''page.&lt;br /&gt;
&lt;br /&gt;
'''Viewing the Linked RFx&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
You can view the linked RFx from the RFx ''Details ''page.&lt;br /&gt;
&lt;br /&gt;
To view the linked RFx:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Related RFx&amp;amp;nbsp;''on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. The list&amp;amp;nbsp;of related RFx is displayed.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' ''View Record'' icon next to the RFx that allows viewing the original RFx using which its copy was created.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Linking the RFx'''&lt;br /&gt;
&lt;br /&gt;
Linking RFx with another RFx allows keeping track of the activities happening with both RFx thereby allowing to manage multiple RFx within one another. &amp;amp;nbsp; Linking the RFx helps in supporting global sourcing that involves globally distributed buyers’ team. This team may clone the sourcing event at the regional level to identify and shortlist suppliers and link the sourcing events with one another. ICM allows to link the source and destination RFx.&lt;br /&gt;
&lt;br /&gt;
To configure the two way linkage:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''the ''View record ''icon next to the RFx Contract Type on the ''Configuration ''page. The contract type ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;&amp;amp;nbsp;'''Navigate '''to the ''Associations ''section and '''select '''the attribute ''ICMAppSrcRelatedRFx.''&lt;br /&gt;
&lt;br /&gt;
*If ''Yes ''is selected next to ''Allow Two-way linkage'', it allows the source RFx to display the target RFx in the related RFx; likewise, the target RFx displays the source RFx. &lt;br /&gt;
*If ''No'' is selected next to Allow Two-way linkage, then the target RFx will display source RFx linkage in related RFx. not link the RFx copy with the source RFx. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Update'' and navigate to ''Verify'' page and '''click''' ''Update'' to update the RFx contract type. This links the copied RFx with Source RFx.&lt;br /&gt;
&lt;br /&gt;
You can also add linked RFx from RFx ''Details'' page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To add linked RFx from RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''the plus icon next to ''Related RFx ''on RFx ''Details ''page. The ''Related RFx ''window opens displaying the list of related source RFx that you can link with the copied RFx.&lt;br /&gt;
&lt;br /&gt;
2.'''Click '''''Select ''to select and link the copied RFx with the source RFx from the available list.&lt;br /&gt;
&lt;br /&gt;
'''Exclude&amp;amp;nbsp;auto-attached associated documents during copy'''&lt;br /&gt;
&lt;br /&gt;
When a user copies the RFx with auto-attached associations, ICM excludes all auto attached associations from being copied to the new RFx. The auto-attached associations won’t be displayed on the ''Copy Record'' window. The resulting RFx has the selected manual associations and its own auto-attached associations as per the configured rules. This avoids the unnecessary upload of files into the ICM repository and duplication of association records on copied RFx.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding Line Items ==&lt;br /&gt;
&lt;br /&gt;
You can add line items at any stage of the RFx instance depending upon RFx configuration settings. Line items are products that the buyer is looking to procure through the RFx instance. When you create the RFx instance, the RFx ''Details'' page opens with the RFx status displayed as ''Draft''. You can use the left navigation pane to add one or more line items. You can also add line items using Microsoft Excel import by selecting the file from your local machine and uploading it to ICM Sourcing.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 1.png|720px|7.9 Sourcing Adding Line Items 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To add line items:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Create Association'' icon next to ''Line Items'' under the ''RFx Package'' tab. The ''Line Items'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 2.png|720px|7.9 Sourcing Adding Line Items 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Enter '''the values in the following fields:&lt;br /&gt;
&lt;br /&gt;
*''Name'': '''Enter''' the name of the items you want to procure. For example, ''Laptops''. &lt;br /&gt;
*''Part Number'': '''Enter''' the specific details of the item. For example, Model number. &lt;br /&gt;
*''Description'': '''Enter''' more information of the item. &lt;br /&gt;
*''Unit of Measure'': '''Select''' appropriate unit of measure depending upon the item. For example, ''Piece, Each, Pack'', etc. &lt;br /&gt;
*''Unit of Order'': '''Select''' the unit of order you want to procure. For example, in the multiples of 10s or 100s etc. &lt;br /&gt;
*''Desired Quantity'': '''Enter''' the quantity of the item you wish to procure. &lt;br /&gt;
*''Bid Currency'': '''Select''' the currency from the drop-down. &lt;br /&gt;
*''Additional Details'': You can upload a file that contains additional details about the item. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 3.png|720px|7.9 Sourcing Adding Line Items 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Create''. The Line Item is created. The Count is updated in the left navigation pane on the RFx&amp;amp;nbsp;''Details'' page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 4.png|720px|7.9 Sourcing Adding Line Items 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''Repeat steps 1-3 to add more line items.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Adding Bulk Line Items&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
The bulk associations capability has enabled ICM to handle large number of associations in the tune of thousands, by presenting itself as a lightweight association as well as tremendously improving performance. The Sourcing event can include many line items for an RFx ranging from 500 to 50,000 maximum. In Sourcing, line items are considered as associations.&amp;amp;nbsp;&amp;lt;br/&amp;gt; The bulk association configuration has now been simplified by providing a Enable Bulk Processing flag at contract type definition level which triggers a set of defaults that has been intentionally restricted. The end user experience for the bulk association has not changed from the way that the conventional association is handled from the UI, rather the underlying data structure has been further enhanced to make it go the distance.&amp;amp;nbsp;&amp;lt;br/&amp;gt; Performance has been the key while introducing and designing this new association, which has given way to the new type of instance, namely the Proxy Instance, which is retrieved in every GET call. The actual instances are referred by using this proxy instance, thereby reducing the load on the GET APIs. Specialized GET and SET APIs have also been introduced for bulk associations to improve its adaptability and ease-of-use.&amp;lt;br/&amp;gt; Bulk associations have very effectively consumed the Elastic Search Bulk API to sync a large set of data at one go, rather than the traditional way of one instance at a time, adding to the boost in performance.&amp;lt;br/&amp;gt; Bulk association is enhanced&amp;amp;nbsp;to be able to address the large volume of data&amp;amp;nbsp;that Sourcing apps require, including:&lt;br /&gt;
&lt;br /&gt;
*The associations do not have a workflow. &lt;br /&gt;
*Simplifying the association team by maintaining single team at proxy level for all instances, instead of each instance having its own team. &lt;br /&gt;
*Restricting document assembly, for individual instances, but the instances can be assembled in the parent agreement as a table or saved search.&amp;amp;nbsp; &lt;br /&gt;
*Reduced the attributes to be indexed in the parent, so as to cater to more number of instances driven by the configuration key.&amp;lt;br/&amp;gt; &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
To enable the Bulk Processing flag:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Configuration'' &amp;gt; ''Create Contract Type''. &amp;amp;nbsp;The ''Select a type of contract'' window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Select '''the Contract Type. For example, ''Associated Document.''&lt;br /&gt;
&lt;br /&gt;
3''.&amp;amp;nbsp;'''''Click'''''Next. ''The ''Create Contract Type Wizard ''page opens.&lt;br /&gt;
&lt;br /&gt;
4. '''E''''''nter '''a ''Contract Type Name''. For example,''Acme Bulk Pro''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Toggle '''''Enable Bulk Processing'' flag to ''Yes''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Next.''&lt;br /&gt;
&lt;br /&gt;
''7.&amp;amp;nbsp;'''''Enter&amp;amp;nbsp;'''details on the following tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Create''&amp;amp;nbsp;on the&amp;amp;nbsp;''Verify&amp;amp;nbsp;''tab to create the contract type. It will now be in the&amp;amp;nbsp;''Draft&amp;amp;nbsp;''status.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Send for Approval'' to send the contract type for approval. When approved, the contract type ''Acme Bulk Pro'' will be displayed in the grid in the ''Approved'' status.&lt;br /&gt;
&lt;br /&gt;
To upload bulk associations (line items)&lt;br /&gt;
&lt;br /&gt;
'''Prerequisites:'''&lt;br /&gt;
&lt;br /&gt;
*RFx is created''.'' &lt;br /&gt;
*In the RFx, line item exists as an association with&amp;amp;nbsp;''Enable Bulk Processing&amp;amp;nbsp;''flag as&amp;amp;nbsp;''Yes.'' &lt;br /&gt;
*The event rule&amp;amp;nbsp;''Associated Document Created&amp;amp;nbsp;''is created. &lt;br /&gt;
&lt;br /&gt;
To upload bulk associations:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Import associated document data template&amp;amp;nbsp;''icon. The&amp;amp;nbsp;''Upload Document&amp;amp;nbsp;''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Select File''. Upload the file with the list of line items.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Upload File.&amp;amp;nbsp;''The record processing details will be updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Ok.&amp;amp;nbsp;''The RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page opens. The line item associations are updated.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The team for any one instance of line item is same for any other instances of line items.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Selecting Suppliers ==&lt;br /&gt;
&lt;br /&gt;
Suppliers are the businesses that participate in the RFx bidding process. The suppliers and their information such as ''Names, Addresses, Contact Numbers, Email Addresses,'' and&amp;amp;nbsp;''Supplier Contacts'' are added to the Masterdata. The name of the existing&amp;amp;nbsp;''Supplier Contact Name''&amp;amp;nbsp;has been modified to&amp;amp;nbsp;''Supplier Contact Full Name.&amp;amp;nbsp;''For example, John Doe.&amp;amp;nbsp;Buyers can remove the supplier contact from the Supplier Contact page. This updates the count of selected supplier contact.The selected supplier contact’s full name is displayed on the new selected supplier contacts interface.The suppliers and supplier contacts saved earlier are now displayed as pre-selected when adding more suppliers and supplier contacts.&lt;br /&gt;
&lt;br /&gt;
Now, the buyers can use any supplier and supplier contact masterdata contract type to add suppliers.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;supplier contact full name column will be displayed by default on:&lt;br /&gt;
&lt;br /&gt;
*''Supplier Contact&amp;amp;nbsp;''selection page &lt;br /&gt;
*''Details&amp;amp;nbsp;''page of Supplier Contact &lt;br /&gt;
*Grid view of the supplier contact association&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This makes it is easier for buyers and Administrators to identify and select the correct supplier if there are multiple suppliers with the same first name. This is applicable for bulk agreements too.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This is applicable for RFx, RFI and Rounds.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To add suppliers:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''the ''Create Association'' icon next to ''Suppliers''. The ''Supplier'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 1.png|720px|7.9 Sourcing Selecting Suppliers 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Search''' for the desired supplier(s) or '''select''' the suppliers from the displayed list under the ''Supplier'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 2.png|720px|7.9 Sourcing Selecting Suppliers 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Next''. The ''Supplier Contacts'' tab opens displaying the contact details of the suppliers.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SupplierContactFullName.png|720px|7.12-SupplierContactFullName.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''''the View Record ''icon next to the supplier’s name. The supplier’s contact details are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SupplierContactRecord.PNG|720px|7.12-SupplierContactRecord.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Select''' the desired ''Supplier Contact(s)''.&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''''Save''. The selected supplier(s) and supplier contact(s) are added to the RFx instance. The count is updated under the ''Supplier Information'' tab in the left navigation pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 5.png|720px|7.9 Sourcing Selecting Suppliers 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Error Validations&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers have the option to select mandatory and pre-requisite contracts while creating the RFx. The attributes for mandatory and prerequisite contracts are interlinked. The prerequisite contracts are derived from the mandatory contracts. So, if the buyers select the following contracts – NDA, Warranty Agreement, Fixed Cost Agreement as mandatory, then they have the option to select one or more, or all as prerequisite contracts.&lt;br /&gt;
&lt;br /&gt;
Suppose the NDA is the prerequisite contract for accessing the RFx, then the validations are done such that ICM expects that the Instance of an NDA contract type for all the suppliers is associated with the RFx and contract should be in Approved state. Similarly, if Contract Types are made mandatory, then the instances of these should exist before RFx is sent for approval.&lt;br /&gt;
&lt;br /&gt;
Buyers will now receive a system message when:&lt;br /&gt;
&lt;br /&gt;
*Sending an RFx for approval in case prerequisite contracts are not in the Approved status for suppliers. &lt;br /&gt;
*Sending an RFx for approval in case mandatory contracts are either not created or exist in one of the states - ''Cancelled'', ''Expired'', or ''Terminated'' for suppliers.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Buyers will be able to view the validations for the prerequisite and mandatory contracts for the shortlisted suppliers only.&amp;lt;br/&amp;gt; For a shortlisted supplier, if all the prerequisite contracts are inactive or if any one of the contracts is active but not in Approved or later state, then the validations will be displayed.&amp;amp;nbsp;&amp;lt;br/&amp;gt; For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Draft state) and NDA 2 (in Waiting for Approval) state, then validations will be displayed.&amp;amp;nbsp;&amp;lt;br/&amp;gt; The validations will not be displayed for shortlisted suppliers when at least one active prerequisite contract exists, and all such contracts are in Approved or later state.&amp;amp;nbsp;&amp;lt;br/&amp;gt; For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Approved state) and NDA 2 (in Expired state), no validations will be displayed since one of the two prerequisite contracts (NDA 1) is in Approved or later state.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To view the error validations:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Send for Approval&amp;amp;nbsp;''on RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. The&amp;amp;nbsp;''Contract Status Validation&amp;amp;nbsp;''window opens.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-1.png|720px|7.12-Validations-1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the ''Mandatory Contracts&amp;amp;nbsp;''tab next to the&amp;amp;nbsp;''Prerequisite Contracts&amp;amp;nbsp;''tab.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-2.png|720px|7.12-Validations-2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
A message is displayed as above indicating that the contract types are either not created or exist in one of the statuses as Expired, Terminated, or Cancelled. In this example, the contract types Fixed Cost and NDA are not created.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the plus icon to the mandatory contract that was configured when creating the RFx and create the mandatory contracts using the process to create the bulk agreement.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Send for Approval.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Status Validation&amp;amp;nbsp;''window opens displaying only the Prerequisite contracts.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-3.png|720px|7.12-Validations-3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Creating Bulk Agreements ===&lt;br /&gt;
&lt;br /&gt;
The Sourcing App offers you a convenient way of creating bulk agreements with the suppliers, without having to move out of RFx instance that you are working on. The agreements must be already configured in ICM. These agreements may be made mandatory for the supplier to sign before the supplier can participate in the RFx. The RFx displays all the agreements created from the RFx and they have all the agreement information. This allows the buyer to conveniently navigate between the RFx and the agreement associated with the RFx.&lt;br /&gt;
&lt;br /&gt;
To create an agreement:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Create Association'' icon next to the agreements in the left navigation pane on the RFx ''Details'' page. For example, NDA, Warranty Agreement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 1.png|720px|7.9 Sourcing Creating Bulk Agreements 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 2.png|720px|7.9 Sourcing Creating Bulk Agreements 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. The ''Attributes (Step 2 of 4)'' page opens in the new browser tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 3.png|720px|7.9 Sourcing Creating Bulk Agreements 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Enter''' values for all the attributes, some of which may be mandatory.&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''the ''Select Multiple Suppliers ''icon next to ''Suppliers and Agreement Details. ''The ''Supplier ''page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 4.png|720px|7.9 Sourcing Creating Bulk Agreements 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. Repeat steps 2 to 6 from the ''Selecting Suppliers'' section to add a supplier.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click '''''Next''. The ''Select Template'' ''(Step 3 of 4) ''page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 5.png|720px|7.9 Sourcing Creating Bulk Agreements 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Select''' a Template.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 6.png|720px|7.9 Sourcing Creating Bulk Agreements 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click '''''Next. ''The ''Verify'' page opens. Verify all the information you have entered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 7.png|720px|7.9 Sourcing Creating Bulk Agreements 7.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9. '''Click''' the ''Bulk Create Agreement ''button. The agreement is created.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 8.png|720px|7.9 Sourcing Creating Bulk Agreements 8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' the ''View Record'' icon next to the NDA instance on the ''Sourcing'' page. The NDA’s ''Details'' page opens with the NDA in the ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The number of instances of the selected NDA Agreement created matches with the number of suppliers selected while creating the RFx.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 9.png|720px|7.9 Sourcing Creating Bulk Agreements 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
After the Agreement is created for a supplier, you can proceed with the agreement workflow as configured. For example, you can send the agreement for approval.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 10.png|720px|7.9 Sourcing Creating Bulk Agreements 10.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click''' the ''Send For External Signature'' button on the ''Details'' page. The agreement is sent to the supplier(s) for signatures. The status of the agreement changes to ''Executed'' when all the suppliers sign the NDA.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 11.png|720px|7.9 Sourcing Creating Bulk Agreements 11.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Link Existing Contracts&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Link existing supplier contracts (prerequisite, mandatory, associated contracts) allowing buyers to leverage existing contracts with suppliers.&amp;amp;nbsp; &lt;br /&gt;
*View the contracts of the supplier when creating the bulk agreement that allows assigning any supplier contact as a signatory for the agreement. &lt;br /&gt;
*View the signatory of the prerequisite contracts that allows the suppliers to connect with the signatory if there are any issues with the contracts.&amp;amp;nbsp; &lt;br /&gt;
*Send the agreements for approval in bulk that helps avoid sending the agreements for approval individually.&amp;amp;nbsp; &lt;br /&gt;
*Select the new signature type&amp;amp;nbsp;''Click to Sign&amp;amp;nbsp;''allowing suppliers to participate in the sourcing event by previewing, accepting, or declining the terms and conditions set by the buyer.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
To link existing contracts:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Create Association&amp;amp;nbsp;''next to the agreements in the left navigation pane on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. For example, NDA, Warranty Agreement. The&amp;amp;nbsp;''Please Confirm&amp;amp;nbsp;''window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Existing Contracts. ''The&amp;amp;nbsp;''Select existing contracts to link to RFx page&amp;amp;nbsp;''opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the contract that you want to link with the RFx and&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Link Contracts.&amp;amp;nbsp;''&lt;br /&gt;
&lt;br /&gt;
The selected contract is linked with the RFx.&amp;amp;nbsp;&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Adding Team Members ===&lt;br /&gt;
&lt;br /&gt;
A team of Approvers, Reviewers, and Observers can be added to the RFx instance for completing the workflow.&lt;br /&gt;
&lt;br /&gt;
To add team members:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Team'' tab on the RFx ''Details'' page. The ''Add Team'' page opens in the right pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Team Members 1.png|720px|7.9 Sourcing Adding Team Members 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''Add Team'' icon. The ''Select User'' window opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter '''the search term in the ''Search User'' field to search for a desired user.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select '''a User from the displayed user tiles.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select '''a ''Role''. For example, ''Approver'', ''Business Owner'', ''Observer'', etc.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Select''' or '''enter''' the ''Step Number'' if you select ''Approver'' in the ''Select Role'' field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter '''a comment in the ''Add Note'' field (optional). You can see this comment under the ''Notes'' tab.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Select '''the ''Send Notification ''checkbox if you want to the user to receive a notification of the task.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Add''. The ''User has been added successfully'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Team Members 2.png|720px|7.9 Sourcing Adding Team Members 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Sending the RFx Instance for Approval ===&lt;br /&gt;
&lt;br /&gt;
The RFx instance must be in ''Approved ''state before a round is created automatically and the RFx workflow can be completed.&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Send For Approval ''button on the RFx ''Details'' page. The RFX instance is sent for approval to the approver(s) you have selected in the ''Team''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Internal Approval for RFX Instance 1.png|720px|7.9 Sourcing Internal Approval for RFX Instance 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The status changes to ''Waiting For Approval. ''A task is created for each approver.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Internal Approval for RFX Instance 2.png|720px|7.9 Sourcing Internal Approval for RFX Instance 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
When all the approvers approve the RFx instance, the status changes to ''Approved''. After the RFx is approved, the first round is created automatically.&lt;br /&gt;
&lt;br /&gt;
== Working with Rounds ==&lt;br /&gt;
&lt;br /&gt;
One cycle of seeking proposals/bids from suppliers and evaluating them is referred to as a round. A complete Sourcing event may comprise of multiple rounds. The first round is created automatically (if the start and end dates are entered) as soon as the RFx instance is approved. You can see the round on the RFX ''Details'' page. You must open the round instance and fill in additional details. There can be multiple rounds for one RFx instance.&lt;br /&gt;
&lt;br /&gt;
Here is the round workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Working With Rounds 1.png|720px|7.9 Sourcing Working With Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Starting the Scheduled Rounds ===&lt;br /&gt;
&lt;br /&gt;
You can schedule a round by entering the ''Round Start Date'' and ''End Date'' when creating the RFx instance. The buyer must click the ''Start Round'' button on the ''Round'' ''Details'' page to start the round.&lt;br /&gt;
&lt;br /&gt;
To start the round:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Round'' on the RFx ''Details'' page. The auto created round instance is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Only the first round is created automatically. The buyers must create the other rounds manually as required.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Scheduling Rounds 1.png|720px|7.9 Sourcing Scheduling Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''the ''View Record'' icon. The Round&amp;amp;nbsp;''Details'' page opens with the round in ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Scheduling Rounds 2.png|720px|7.9 Sourcing Scheduling Rounds 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click '''the ''Start Round'' button to start the Round. The status of the round changes to ''Approved ''when the round is approved and the status of the RFx changes to&amp;amp;nbsp;''Bidding&amp;amp;nbsp;''''Open'''''&amp;lt;b&amp;gt;.&amp;lt;/b&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''When the round is approved the status changes to ''Scheduled''. When the current date is equal to start date of the round, the status changes to ''Open''.&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating Rounds ===&lt;br /&gt;
&lt;br /&gt;
The buyer can also create a round manually if they need to conduct multiple rounds with the supplier. The buyer can create the round manually only if the RFx instance is in ''Approved ''state.&lt;br /&gt;
&lt;br /&gt;
To create a round (manually):&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Create Association'' icon under the ''Round'' tab on the RFx ''Details'' page. The ''Create RFx -Round'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 1.png|720px|7.9 Sourcing Creating Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''Organization Unit'' icon to select the ''Organization Unit''.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter''' an appropriate name for the round.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Enter''' relevant details in the ''AppSrc Description'' field.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a ''Round Start Date''. This field is already populated with the current date. You can select a different date and time if required.&lt;br /&gt;
&lt;br /&gt;
6. '''Select''' a ''Round End Date ''and time.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The date and time is displayed based on the user’s locale settings. When the user with different locale views the RFx, the date and time are converted to their locale.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 2.png|720px|7.9 Sourcing Creating Rounds 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click '''''Next''. The ''Verify'' page opens. Verify all the information.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 3.png|720px|7.9 Sourcing Creating Rounds 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8. '''Click '''the ''Create Round'' button. The Round’s ''Details'' page opens. The round is now created in ''Draft ''state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 4.png|720px|7.9 Sourcing Creating Rounds 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9. '''Click '''the ''Start Round'' button to begin the Round. The status of the round changes to ''Approved and Scheduled''. When the round is approved the status changes to ''Approved and Scheduled''. When the current date is equal to start date of the round the status changes to ''Published''.&lt;br /&gt;
&lt;br /&gt;
=== Editing Round start and end dates&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&lt;br /&gt;
&lt;br /&gt;
*Edit the&amp;amp;nbsp;round start and end date when the round is in one of the below states: &lt;br /&gt;
**Draft &lt;br /&gt;
**Waiting for Approval &lt;br /&gt;
**On Hold &lt;br /&gt;
**Open &lt;br /&gt;
**Approved&amp;amp;nbsp;   &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;You can make changes only to the round end date when the round is in ''Open'' state. The changes made to the round start and end date are captured in the ''History'' on round ''Details'' page.It is not mandatory to run the approval workflow for the round after changing the ''Planned Start Date'' and ''Planned End Date''.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To edit the round start and end date:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Round'' on RFx ''Details'' page. The list of rounds is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate1.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''View Record'' icon next to the round for which you want to edit the start and end date. The round ''Details'' page opens and displays the existing start and end date of the rounds.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;3.&amp;amp;nbsp;'''Click''' ''Edit''. The ''Edit'' round page opens.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate2.png|720px|7.12-EditRound-Start-EndDate2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;Make the necessary changes to the start and end date of the round depending on the state of the round. You can edit just the time of start and end date of the round and not required to change the date always.&amp;amp;nbsp;For example, the&amp;amp;nbsp;''Planned Start Date&amp;amp;nbsp;''was July 8, 2020, 12:00 AM and the&amp;amp;nbsp;''Planned End Date&amp;amp;nbsp;''was August 8, 2020 12:00 AM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Open:&amp;amp;nbsp;You can make the changes only to the ''Planned End Date'' of the round. For example, you can change the ''Planned End Date'' to September 8, 2020 in place of the earlier date August 8, 2020 &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Buyers can edit the round end date when the status of the RFx changes to In Modification when the previous status of the round is Open.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate3.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*''Approved/''On Hold:&amp;amp;nbsp;You can make the changes to the ''Planned Start Date'' and ''Planned End Date'' values of the round. For example, you can change the ''Planned Start Date'' to July 15, 2020 in place of the earlier date July 8, 2020 earlier and ''Planned End Date'' to September 15, 2020 as against August 8, 2020 earlier. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate4.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Buyers can enter the planned start and end date of the RFx when creating the round manually. The values for Actual Start Date and Actual End Date are populated based on the actual date when the round is opened or closed.&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Update&amp;amp;nbsp;''on round&amp;amp;nbsp;''Verify&amp;amp;nbsp;''page.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate5.png|720px|7.12-EditRound-Start-EndDate5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The round ''Details'' page opens and displays the edited round start and end date.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate6.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;The changes made to the round start and end date are captured in the ''History'' on round ''Details'' page.It is not mandatory to run the approval workflow for the round after changing the ''Planned Start Date'' and ''Planned End Date''.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Working with Bids ==&lt;br /&gt;
&lt;br /&gt;
A bid is a collection of quotes for each Line Item.&amp;amp;nbsp;The system generates bids when a round is in ''Published'' state. The supplier can view the bids that were submitted in the previous rounds if the buyer selects ''Yes ''in the ''AppSrc Auto Copy Bids from the Previous Round ''option when creating the RFx.&lt;br /&gt;
&lt;br /&gt;
Depending upon how the RFx instance is configured in the organization, suppliers must sign all the prerequisite agreements before submitting the bid responses. The suppliers won’t be able to view the RFx instance until the prerequisite agreement is in ''Executed'' state.&lt;br /&gt;
&lt;br /&gt;
Here is the bid workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Working With Bids 1.png|720px|7.9 Sourcing Working With Bids 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Submitting&amp;amp;nbsp;Bids ===&lt;br /&gt;
&lt;br /&gt;
A supplier can submit bid responses when the round is published.&lt;br /&gt;
&lt;br /&gt;
To submit bid responses:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Sourcing ''tile on the ''Dashboard'' after logging on to ICM. The ''Sourcing'' page opens. This page displays a list of all the RFx instances, rounds, and bids that the supplier is a part of.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 1.png|720px|7.9 Sourcing Submitting Bids 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' the ''View Record'' icon next to the bid that you want to respond to. The Bid’s ''Details'' page opens with the bid is in ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 2.png|720px|7.9 Sourcing Submitting Bids 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Bid Response'' under ''Quotation Details ''tab. The bid response is displayed in the grid along with its details such as ''Item Name'', ''Quotation ID'' etc. As the buyer had added two line items, the count is updated to 2 next to ''Bid Response''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 3.png|720px|7.9 Sourcing Submitting Bids 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Edit'' icon. The ''Edit Bid Response'' window opens. It displays the information of the line item given by the buyer.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 4.png|720px|7.9 Sourcing Submitting Bids 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 5.png|720px|7.9 Sourcing Submitting Bids 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
5. '''Enter''' values for the following fields:&lt;br /&gt;
&lt;br /&gt;
*''AppSrc Base Price'': The price for one unit of the product mentioned in the line item. &lt;br /&gt;
*''AppSrc Total Price'': Calculated automatically by ICM depending upon the buyers requirement of the number of pieces and the base price you entered. &lt;br /&gt;
*''AppSrc Quote Currency'': '''Select''' the appropriate currency from the drop-down. &lt;br /&gt;
&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 6.png|720px|7.9 Sourcing Submitting Bids 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' the ''Update ''button. The bid response is updated. The ''Bid Response'' window closes.&lt;br /&gt;
&lt;br /&gt;
7. '''Click '''''Submit ''on the ''Bid'' ''Details'' page. The bid response is now submitted to the buyer. The status of the bid changes to ''Submitted.''&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp; You should click on submit only after you have entered values for all items.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 7.png|720px|7.9 Sourcing Submitting Bids 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can submit the bid responses for one or all line items. Follow steps 1-7 to do so.&amp;lt;/div&amp;gt; &lt;br /&gt;
After submitting bids, suppliers cannot edit bids. To edit the bids, the suppliers must '''click '''''Withdraw''. This changes the status of the bid to ''Withdrawn. ''Suppliers can revert withdrawal by clicking ''Revert Withdrawal. ''They can also edit their bids and submit again.&lt;br /&gt;
&lt;br /&gt;
As soon as one supplier submits a bid, the status of the round changes to ''In Bidding''. When all the bid responses are submitted, the buyer can:&lt;br /&gt;
&lt;br /&gt;
*Manually close the round by clicking the ''Close Round'' button on the Round’s ''Details'' page if the ''AppSrc'' ''Allow Foreclosure of Rounds ''is toggled to ''Yes ''when creating the RFx by the buyer. &lt;br /&gt;
&lt;br /&gt;
Or&lt;br /&gt;
&lt;br /&gt;
*The round closes as per the scheduled ''Round End Date ''and Time. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The buyer can choose to close the round even when only one supplier has submitted the bid or even if no one has submitted a bid. The status of the RFx changes to ''Round'' ''Closed''.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 8.png|720px|7.9 Sourcing Submitting Bids 8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Buyers can now view the status of bids for each supplier regardless of whether the RFx is an open or sealed envelope depending on the status of the bid. These statuses include:&lt;br /&gt;
&lt;br /&gt;
*''Submitted and Closed'': Buyers and the user assigned as a surrogate buyer can view the bids in ''Submitted ''status, and the rounds are closed. &lt;br /&gt;
*''Declined'': The suppliers declining the bid cannot participate in the upcoming rounds. The status of the bid is displayed according to the type of RFx when the bid is in Declined state. &amp;amp;nbsp;&amp;amp;nbsp; &lt;br /&gt;
**''Open RFx'': Buyers and the user assigned as a surrogate buyer can view the round in Open and Closed state. &lt;br /&gt;
**''Sealed Envelope'': Buyers can view the bid when the state of RFx changes to ''Closed'' state. The suppliers who declined the bid cannot participate in the ongoing or upcoming rounds nor can they revert decline to participate in the round again.   &lt;br /&gt;
&lt;br /&gt;
Buyers cannot view the status of the bids depending on the following status of the bid.&lt;br /&gt;
&lt;br /&gt;
*''Not Submitted and Closed'': Buyers and the user assigned as a surrogate buyer cannot view the bid response when the bid is not submitted, and the round is closed. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The bid responses are displayed or hidden based on whether the bid was submitted or not submitted by the suppliers.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Bid Analysis ===&lt;br /&gt;
&lt;br /&gt;
It is the process of analyzing supplier responses with an intent to compare one against the others along the evaluation criteria. When all the desired ''Bid Responses'' are received, you can view and analyze all the responses to be able to take informed decision.&lt;br /&gt;
&lt;br /&gt;
At least one round should be completed for conducting bid analysis, otherwise the user gets an error message indicating that the round must be started to download bid analysis. For an RFx with ''Sealed Envelope'', at least one round must be in ''Closed'' state to download the excel sheet for bid analysis.&lt;br /&gt;
&lt;br /&gt;
The bid analysis Excel will contain all the bids, for all the suppliers, for all the rounds. The bid analysis will also contain currency information of bid currency and RFx primary currency, along with bid analysis attributes converted to RFx primary currencies. An attribute for bid analysis is defined in the masterdata. Users can add the bid analysis attribute for each RFx item and specify its value while creating an RFx or associated document. This helps the buyer to get all the information in the Excel sheet to be able to easily analyze a bid for a supplier.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&lt;br /&gt;
&lt;br /&gt;
*Download bid analysis excel on bid level and round level. When bid analysis is performed on bid, the downloaded bid analysis Excel it will include the responses for a specific respective supplier whose bid was chosen. Whereas, when bid analysis is performed on round level, downloaded bid analysis Excel will include the bid responses data for all the suppliers present in the round. &lt;br /&gt;
*&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Enter the values for bid analysis attributes and upload the bid analysis Excel sheet. The value of bid analysis attributes will be updated in the bid response.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Downloading and Uploading Bid Analysis for round'''&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Bid Analysis'' button, on the ''Round'' ''Details'' page. The ''Bid Analysis'' page opens.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Download File. ''The Excel file of Bid Analysis is downloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Open '''the downloaded Excel. View the Bid Analysis attributes.&lt;br /&gt;
&lt;br /&gt;
Once downloaded, you can edit the Bid analysis attributes such as ''Bonus'', ''Net Landed Cost'', ''Difference''.&lt;br /&gt;
&lt;br /&gt;
4.'''Enter '''''Bid Analysis attribute'' values. For example: '''Enter''' value of ''Bonus as 2.44 instead of 1.05. &amp;amp;nbsp;''&lt;br /&gt;
&lt;br /&gt;
5.'''Click''' ''Save'' to '''save''' the file'''.'''&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''''Select File To Upload'' on the Bid Analysis window. The updates will be made, and the''Bid Analysis has been Saved successfully'' message will be displayed in the ''Upload Summary'' section.&lt;br /&gt;
&lt;br /&gt;
7.'''Click''' ok.&lt;br /&gt;
&lt;br /&gt;
'''Downloading and uploading bid analysis for bid:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
1.'''Click the '''''Bid Analysis'' button, on ''Bid'' ''Details'' page.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.'''Click''' ''Download File. ''The Excel file of Bid Analysis is downloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Open '''the downloaded Excel file. View the Bid Analysis attributes.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;You can add the bid analysis attribute for each RFx item and specify its value while creating an agreement or associated document.&lt;br /&gt;
&lt;br /&gt;
If you add any invalid value in Bid Analysis attribute, error validation message will be displayed in last column.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example: '''Enter''' ''hdsjbvshd'' in ''Bonus, and enter ''any random value in ''Net Landed Cost'' ''chdsjbcs'', then Error message is displayed, indicating that Bonus and Net landed Cost are invalid.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
You can not edit other attributes such as ''Freight, Insurance, landed Cost''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''To analyze bid response:'''&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Download Bid Analysis'' button on the RFx ''Details'' page. An Excel sheet containing the bid responses is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Bid Analysis 1.png|720px|7.9 Sourcing Bid Analysis 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Open''' the Excel sheet. You can view the all the data collected from the bid responses such as ''Supplier ID, Item Name, Item Description'', etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Bid Analysis 2.png|720px|7.9 Sourcing Bid Analysis 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Downloading Associations and Attachments&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing app offers an ability to download either all or selected associations (line items, attachments, supplier documents) and attachments (files uploaded to the RFx instance) for review and analysis purposes. This is applicable for all types of RFx instances and all documents (buyer’s and suppliers). The application retains the file names of the attachments as they were while uploading them so that they could be recognized easily.&lt;br /&gt;
&lt;br /&gt;
The files names will be the same when downloading or uploading them to ICM. The files will be downloaded as per the defined folder structure and folder naming conventions &amp;amp;nbsp; which helps users to easily identify files under individual folders of the RFx and avoid any discrepancies. The folder names for associations are now same as the contract type display names such as line items, internal attachments, round, bid response and so on.&lt;br /&gt;
&lt;br /&gt;
Downloading the RFx package displays the folders for RFx, round, bid, RFI Response as they are displayed in ICM. The rounds and bids folders are merged in a single folder and the template files are added to the relevant round or bid folder. This is applicable for both RFx and RFI.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Buyers can select and download attachments of buyers and suppliers as required. Suppliers can only download the attachments to which they have access or the attachments they upload.&amp;lt;/div&amp;gt; &lt;br /&gt;
The attachments can be viewed under ''RFx Package'' tab on the RFx ''Details'' page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Downloading Associations and Attachments 1.png|720px|7.9 Sourcing Downloading Associations and Attachments 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To download associations and attachments:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Download Package'' button on the RFx ''Details'' page. The ''Download'' window opens displaying all the Associations and attachments.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Downloading Associations and Attachments 2.png|720px|7.9 Sourcing Downloading Associations and Attachments 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' the items you wish to download.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage1.png|720px|7.12-DownloadPackage1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Download''. The selected files are downloaded in a zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage2.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage3.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage4.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The selected attachments are downloaded as per the folder structure they are part of in the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
== Awarding Workflow ==&lt;br /&gt;
&lt;br /&gt;
You can initiate the Awarding workflow after receiving all the required bid responses and after all the rounds are in ''Round(s) Closed ''state. Buyers can award multiple suppliers using Excel upload.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': After the awarding is initiated, the buyer cannot create new rounds. If a new round is required to be created after awarding is initiated, you must delete the awarding object and then create a new Round.&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating Awarding Instances ===&lt;br /&gt;
&lt;br /&gt;
To create award instances:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Initiate Award'' button on the RFx ''Details'' page.&amp;amp;nbsp; The ''Attributes (Step 2 of 4)'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 1.png|720px|7.9 Sourcing Creating Awarding Instances 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' the ''Organization Unit''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Agreement Code'' is system generated.&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select''' the Business Status (Default value - ''Draft'').&lt;br /&gt;
&lt;br /&gt;
4. '''Enter '''the ''Name'' of the Awarding instance. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Upload '''an ''AppSrc Supporting Document,'' if any.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 2.png|720px|7.9 Sourcing Creating Awarding Instances 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Next''. The ''Select Template (Step 3 of 4)'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 3.png|720px|7.9 Sourcing Creating Awarding Instances 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Select '''the template.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Click '''''Next''. The ''Verify'' page opens. Verify all the information.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 4.png|720px|7.9 Sourcing Creating Awarding Instances 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' the ''Create Award Agreement'' button. The RFx ''Details'' page opens with the status ''Awarding Initiated''. The RFx Awarding instance is created with the status ''Draft''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 5.png|720px|7.9 Sourcing Creating Awarding Instances 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Awarding Decision ===&lt;br /&gt;
&lt;br /&gt;
After creating the Awarding instance, you must create an Awarding ''Decision'' as an Association. The awarding decision contains all the details of all items and the Supplier(s) who are being awarded the RFx along with the other details such as award quantity and price.&lt;br /&gt;
&lt;br /&gt;
To create awarding decision:&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''RFx Awarding'' on the RFx ''Details'' page. The awarding instance is displayed in the right pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 1.png|720px|7.9 Sourcing Awarding Decision 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''the ''View Record'' icon. The Awarding ''Details'' page opens with the status ''Draft''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 2.png|720px|7.9 Sourcing Awarding Decision 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Create Association'' icon next to ''AppSrc Awarding Decision''. The ''Awarding Decision'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 3.png|720px|7.9 Sourcing Awarding Decision 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the icon next to ''Download File. ''The ''Awarding Decision ''excel sheet is downloaded on your computer. This excel sheet displays the information such as the price submitted by the supplier, the quantity of line items, currency, etc. This excel sheet contains all the bids for all suppliers for all rounds.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 4.png|720px|7.9 Sourcing Awarding Decision 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Enter '''values for the required fields entered on Excel.&lt;br /&gt;
&lt;br /&gt;
*''Awarded Quantity: '''''Enter''' the quantity you are procuring through this awarding decision. &lt;br /&gt;
*''Awarded Percentage: '''''Enter''' a value for ''Awarding Percentage''. Awarding can be given to one or more suppliers at a time. For example, the selected supplier may get 60% of the order. If it’s not being shared, it is 100 percent. This process is known as ''Split Awarding''. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can add either the awarded quantity or the awarded percentage and the other is automatically derived. For example, if you enter the awarded percentage, the awarded quantity will be calculated automatically.&amp;lt;/div&amp;gt; &lt;br /&gt;
Some of the important points to note when splitting the award between multiple suppliers are:&lt;br /&gt;
&lt;br /&gt;
*The awarding percentage will be calculated automatically up to 2 decimal places when you add the awarding quantity. &lt;br /&gt;
*The awarding quantity will be calculated automatically based on the percentage entered to the nearest integer. &lt;br /&gt;
*If you want to delete a particular Line Item, delete the records from ''Awarded Quantity ''and ''Awarded Percentage ''columns. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 5.png|720px|7.9 Sourcing Awarding Decision 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Select File to Upload ''and then '''click '''''Upload File ''to upload the file. The awarding decisions are created automatically after uploading the File.&lt;br /&gt;
&lt;br /&gt;
=== Sending the Awarding Instance for Approval ===&lt;br /&gt;
&lt;br /&gt;
After creating the awarding instance and adding the awarding decision, you must send the awarding instance for approval.&lt;br /&gt;
&lt;br /&gt;
To send the awarding instance for approval:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Publish'' on the Awarding ''Details'' page. The ''Published Successfully'' message is displayed.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' ''Send For Approval''. The status of the Awarding instance changes to ''Approved'' once the Approver(s) approve it.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 1.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 2.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
After the awarding instance is approved, the status of the RFx instance changes to ''Awarded''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 3.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Updating the Awarding Contracts ===&lt;br /&gt;
&lt;br /&gt;
Contracts are created for the selected suppliers who are awarded with RFx. You can update the pricing information of the awarded line items in the awarded contracts.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can update the RFx only when it is in ''Awarded ''state and awarding contracts such as NDA is present in the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
To update awarded contracts:&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Update Awarding Contracts ''on the ''RFx Details ''page. The ''Please Confirm ''window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Updating Awarded Contracts 1.png|720px|7.9 Sourcing Updating Awarded Contracts 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Updating Awarded Contracts 2.png|720px|7.9 Sourcing Updating Awarded Contracts 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This validates whether the awarding decision contains any associations.&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Yes. ''The ''Information ''window opens displaying a message ''Update to agreements for awarding decision initiated. Please check the agreements after some time.''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:7.9 Sourcing Updating Awarded Contracts 3.png|720px|7.9 Sourcing Updating Awarded Contracts 3.png]]''&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click '''''Ok. ''The process of updating awarding contracts starts in the background and the status of the RFx changes to ''Contract Initiated. ''After the process is completed successfully, the status of the RFx changes to ''Contract Created.''&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''the agreement associated with the RFx in the left pane on ''RFx Details ''page. The ''Agreement Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Click '''''Awarding Decision ''in the left pane on ''Agreement Details ''page. The awarding decision will be displayed with the updated pricing information.&lt;br /&gt;
&lt;br /&gt;
== Currency Support ==&lt;br /&gt;
&lt;br /&gt;
ICM administrators can now configure the corporate currency in the currency master.&lt;br /&gt;
&lt;br /&gt;
*Add currencies to the currency masterdata that contains the list of currencies that can be used in the RFx event.&amp;amp;nbsp; &lt;br /&gt;
*Manage currencies from the currency master by adding new currency &lt;br /&gt;
*Set a single currency as a corporate currency for the organization to be used in Sourcing events.&amp;amp;nbsp; &lt;br /&gt;
*Restrict the option to delete the currency and only allow to make it inactive. &lt;br /&gt;
&lt;br /&gt;
=== Configuring the Corporate Currency in Currency Master ===&lt;br /&gt;
&lt;br /&gt;
You can create a new currency record in ICM using the extended currency master.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Configuration&amp;amp;nbsp;''and then&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Masterdata&amp;amp;nbsp;''on the&amp;amp;nbsp;''Home&amp;amp;nbsp;''page. The&amp;amp;nbsp;''Create Masterdata&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Configure Corporate Currency 1.png|720px|7.12-Configure Corporate Currency 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the&amp;amp;nbsp;''Extended Currency Master&amp;amp;nbsp;''from the drop-down list and&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Attributes&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Configure Corporate Currency 2.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the following information on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Masterdata code: This is generated automatically after the masterdata is created.&amp;amp;nbsp; &lt;br /&gt;
*Currency Name:&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the name of the currency. For example, Singapore Dollar.&amp;amp;nbsp; &lt;br /&gt;
*Currency Code:&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the code of the currency. For example, SGD.&amp;amp;nbsp; &lt;br /&gt;
*Symbol:&amp;amp;nbsp;'''Enter''' the symbol for the currency you are creating. This helps in identifying the currency used in the financial transactions happening between the buyers and suppliers. For example, $.&amp;amp;nbsp; &lt;br /&gt;
*Country Name:&amp;amp;nbsp;Enter the name of the country to which this currency would belong to. For example, Singapore. &lt;br /&gt;
*Valid Until:&amp;amp;nbsp;'''Select''' the date until which this currency will be considered valid. For example, the currency can be valid for one year from the date it was created which could be July 8 2022. &lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save.&amp;amp;nbsp;''The currency will be created and saved in ICM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To be configure corporate currency in currency master:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''User Administration'' and then '''click''' ''Application Settings''. The ''Application Settings'' page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Next&amp;amp;nbsp;''on ''Entity Color Configuration'' and ''User Theme'' pages. The ''Other Configuration'' page opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Select''' the Corporate Currency from the drop-down list. For example, select SGD (Singapore Dollar).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Update&amp;amp;nbsp;''to set the corporate currency for the RFx.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Exchange rate of different currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
ICM administrators can add, remove, or edit the exchange rates in the currency masterdata. The specified currency exchange rate must have a defined validity period and also set currency exchange rates for supported currencies.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To set exchange rate of different currencies:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1. Repeat step 1 from the configuring the corporate currency in currency master section.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.'''Select''' the ''Exchange Rate Master'' from the drop-down list and '''click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the following information on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Masterdata Code: This is generated automatically after the masterdata is created. &lt;br /&gt;
*From Currency Code: '''Select&amp;amp;nbsp;'''the&amp;amp;nbsp;''From Currency Code. ''This denotes the currency from which you want to convert a particular amount to a different currency. For example, '''select&amp;amp;nbsp;'''''SGD.&amp;amp;nbsp;'' &lt;br /&gt;
*To Currency Code:&amp;amp;nbsp;'''Select '''the&amp;amp;nbsp;''To Currency Code. ''This denotes the currency to which you want to convert a particular amount. For example,&amp;amp;nbsp;'''select '''''USD.'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;You can only select the From Currency Code and To Currency Code for the currencies that are still valid.&amp;lt;/div&amp;gt; &lt;br /&gt;
*&amp;amp;nbsp;Exchange From Date:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the date from which you want to make the exchange rate applicable. For example,&amp;amp;nbsp;'''select&amp;amp;nbsp;'''July 8, 2020.&amp;amp;nbsp; &lt;br /&gt;
*Exchange To Date:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the date to which you want to make the exchange rate applicable. The&amp;amp;nbsp;''To Date&amp;amp;nbsp;''must always be greater than the&amp;amp;nbsp;''From Date.&amp;amp;nbsp;''For example,&amp;amp;nbsp;'''select&amp;amp;nbsp;'''''August 8, 2020.&amp;amp;nbsp;'' &lt;br /&gt;
*Exchange Rate:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''or&amp;amp;nbsp;'''enter&amp;amp;nbsp;'''the exchange rate. This is the value of one currency used to convert to another currency. For example, 1 SGD equals to 0.72 USD.&amp;amp;nbsp; &lt;br /&gt;
*Rate Type:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the type of rate from the available list. For example, Fixed Rate which is the rule applied by the government that ties the country's currency official exchange rate with another country's currency.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save.&amp;amp;nbsp;''The masterdata record for exchange rate between two currencies is added successfully. The masterdata&amp;amp;nbsp;''Details&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
You can perform the following operations on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Edit&amp;amp;nbsp;''to make changes to the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
*Deactivate:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Deactivate&amp;amp;nbsp;''to deactivate but not delete the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
*Delete:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Delete&amp;amp;nbsp;''to delete the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Selecting RFx currency and allowed currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
You can select the RFx currency (primary currency) and allowed currency on Create RFx page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*&amp;amp;nbsp;Primary Currency: '''Select''' the primary currency for the RFx. If the user preferred currency is not added in the currency master, then the corporate currency is set as the primary currency of the RFx. For example, if user preferred currency is SGD which is not added in currency master, then the primary currency is set as USD assuming it is set as the corporate currency.&amp;amp;nbsp; &lt;br /&gt;
*Allowed Currency: '''Select''' the allowed currency for the RFx. This is the currency allowed by the buyers for the suppliers operating from a different country. The selected allowed currencies can be used by suppliers for bidding. Suppliers can view the newly added currencies even when the round is Open and select them as required. Buyers can update the allowed currency at any time using ''Modify RFx'' option. The allowed currencies cannot be deleted after the RFx is approved. &lt;br /&gt;
&lt;br /&gt;
=== Selecting the exchange rate for RFx&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can view the exchange rate throughout the RFx lifecycle by clicking the View Exchange Rate Table icon at RFx, Line Items, Bids, Bid Responses. The exchange rate basis can have one of the following values:&lt;br /&gt;
&lt;br /&gt;
*RFx Open Date: This is selected by default. When this is selected, system uses the start date of first round for determining exchange rates. &lt;br /&gt;
*RFx Closed Date: This date must be selected same as the round end date. When this is selected, system uses close date of the last round for determining applicable exchange rates. &lt;br /&gt;
*User selected:&amp;amp;nbsp;This is the date from when the exchange rates are made applicable by the buyers. It is mandatory to select the Exchange Rate Date that is enabled after selecting User Selected as the Exchange Rate Basis. The selected date is used as the date to determine the exchange rate and all calculations of currency conversion. &lt;br /&gt;
&lt;br /&gt;
Buyers can view the exchange rate information when selecting the Exchange Rate Basis as RFx Open Date or RFx Closed Date after the RFx is approved and the round is created.&lt;br /&gt;
&lt;br /&gt;
=== Selecting currencies from the list of allowed currencies ===&lt;br /&gt;
&lt;br /&gt;
Buyers can select the currencies for the RFx from the list of allowed currencies. The allowed currencies of the RFx can be used as the bid currency by the suppliers. The currency attributes for the line item are restricted to RFx currency. The modified allowed currencies for RFx are displayed as bid currencies for all items.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Changing the currency type in any of the line item displays a validation message in the Validation Description column in the Microsoft Excel if the values selected in Primary and Allowed Currency is different.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Using currency conversion rate in Bid Analysis ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Download the bid analysis excel file that allows to view all the bids received from multiple suppliers. &lt;br /&gt;
*Download the flexible bid analysis excel file for each round after it is closed that allows viewing bids received and converted to RFx primary currency. This file contains information for specific rounds only. &lt;br /&gt;
&lt;br /&gt;
=== Bidding in multiple currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can take the following actions when the bid is created:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Select the bid currency that allows submitting the surrogate bid on behalf of the supplier.&amp;amp;nbsp; &lt;br /&gt;
*View the changes made to the bid that are logged in the&amp;amp;nbsp;''History&amp;amp;nbsp;''section on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Suppliers can take the following actions when bidding in multiple currencies:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the supported currencies for RFx that allows viewing the applicable exchange rates&amp;amp;nbsp; &lt;br /&gt;
*Select the currency from the list of allowed currencies that allows submitting the bid in the selected currency.&amp;amp;nbsp; &lt;br /&gt;
*Submit the bids for items in selected currencies. &lt;br /&gt;
*Upload or download the bidding template that allows adding bid information in excel sheet and upload to ICM.&amp;amp;nbsp; &lt;br /&gt;
*Update the bid currency using ICM and Microsoft Excel.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Currency information in awarding contracts&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can take the following actions when updating the awarding object for RFx using multiple currencies.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Download the awarding decision template that will allow to award the desired suppliers and upload the awarding decision. &lt;br /&gt;
*Include the bid currency in awarding decision that allows including bid currency and other bid information in the contract.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
== Glossary ==&lt;br /&gt;
&lt;br /&gt;
*'''Sourcing event:''' Refers to any solicitation process whether informational, commercial or technical. &lt;br /&gt;
*'''RFx:''' An acronym for X where X may stand for Information, Proposal or Quotation. &lt;br /&gt;
*'''Round:''' A single cycle of seeking proposals or bids from suppliers and evaluating them may be referred to as a Round. There can be multiple Rounds in the complete RFx lifecycle. &lt;br /&gt;
*'''Bid:''' The response submitted by a supplier for an RFx created by the buyer is referred to as a bid. Typically, bid is part of a round and may be revised and resubmitted by the supplier till the round is open. &lt;br /&gt;
*'''Bid Analysis: '''The process of comparing and analyzing the bid responses received from one or more suppliers along with the evaluation criteria created by the buyer. &lt;br /&gt;
*'''Awarding: '''When all the Rounds are closed, and bids are analyzed, the buyer creates the awarding instance that will be awarded to the suppliers that match the evaluation criteria. &lt;br /&gt;
*'''Split Awarding: '''It is the process of awarding the RFx to multiple suppliers with specifically decided quantity or percentage. &lt;br /&gt;
&lt;br /&gt;
'''Related Topics''':''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[ICM_Sourcing_App|ICM Sourcing&amp;amp;nbsp;App]]&amp;amp;nbsp;|&amp;amp;nbsp;''&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Working_with_RFx&amp;diff=14251</id>
		<title>Working with RFx</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Working_with_RFx&amp;diff=14251"/>
				<updated>2020-08-11T17:16:29Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Working with RFx Instances =&lt;br /&gt;
&lt;br /&gt;
The Icertis Sourcing app enables buyers to create and manage end-to-end RFx process. RFx is an acronym for Request for '''x''', where '''x''' may stand for ''Information ''or''Proposal ''or ''Quotation''. Buyers can create an RFx instance, add line items, select suppliers and supplier contacts, create agreements with the suppliers, add team members to the instance for review and approval process and send the instance for approval. Here is the RFx workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing RFX Instances 1.png|720px|7.9 Sourcing RFX Instances 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating the RFx Instance ===&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Sourcing'' tile on the ''Dashboard''. The ''Sourcing'' page opens. A list of all the RFx instances is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SourcingTile.PNG|720px|7.12-SourcingTile.PNG]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2.&amp;amp;nbsp;'''Click '''the ''Create RFx'' tile. The ''Create RFx'' page opens.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;3.&amp;amp;nbsp;'''Select '''a Sourcing Entity from the ''Select Sourcing Entity'' drop-down in the ''Contract Type Details'' ''(Step 1 of 4)'' section. The contract type is configured in the system with default Attributes.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;4.&amp;amp;nbsp;'''Click''' ''Next''. The ''Attributes'' ''(Step 2 of 4)'' page opens. The attributes are grouped under various categories. For example, ''RFx Information'', ''RFx Configs, etc''.&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Select '''or&amp;amp;nbsp;'''enter '''the values for all the required Attributes in the ''RFx Information'' group:&lt;br /&gt;
&lt;br /&gt;
*Enter the RFx Name. For example, ''Procurement for Admin department''. &lt;br /&gt;
*Enter the information of the RFx instance in the ''Description'' field. &lt;br /&gt;
*Select an ''AppSrc Category'' from the drop-down. For example, ''Office Supplies''. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can also add a new category by clicking the plus icon next to&amp;amp;nbsp;''Category'' option.&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select '''the ''Round Start Date'' and ''Round End Date''. When you enter the dates, a round is created automatically as soon as the RFx instance is approved. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing RFX Instances 5.png|720px|7.9 Sourcing RFX Instances 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select''' appropriate values and settings under the ''RFx Configs'' group.&lt;br /&gt;
&lt;br /&gt;
*''View Bids'': '''Select''' an appropriate option from the drop-down. There are following options: &lt;br /&gt;
**''Sealed Envelope'': When you select this option, the bid and bid responses are not visible to the buyer until the round is closed. &lt;br /&gt;
**''Open RFx'': When you select this option, the bid and bid responses are visible to the buyer throughout the duration of the round, as and when the supplier submits the bid.   &lt;br /&gt;
&lt;br /&gt;
*'''Select''' ''Yes'' or ''No'' for the following Configuration settings as per your requirement: &lt;br /&gt;
**''Auto Copy Bids from Previous Rounds: '''''Select '''''Yes ''if you want to allow copying bids from previous rounds to the new round. This displays the bids from the current rounds and the bid responses with values added in the most recently closed round in ''Draft ''state to the suppliers. The default value for this option is set to ''Yes.&amp;amp;nbsp;'' &lt;br /&gt;
**''Allow Foreclosure of Rounds'': '''Select''' ''Yes'' if you want to close the round before the selected round end date. This displays the ''Close Round ''button on the ''Round Details ''page to close the round manually. If you select ''No, ''then the round will be closed automatically only after the selected round end date. The default value for this option is set to ''Yes.'' &lt;br /&gt;
**''Allow New Supplier During RFx Phase'': '''Select''' ''Yes'' if you want to allow new supplier(s) to be added during the entire RFx lifecycle. However, the newly added supplier(s) can participate in a new round only, not in an ongoing round. The default value for this option is set to ''No.''   &lt;br /&gt;
&lt;br /&gt;
*'''Enter '''the ''Terms For Participation'' in the given field. They will be visible to the suppliers only if the buyer adds it when creating the RFx. The suppliers should accept the Terms before they can participate in the bidding process of the RFx. For example, if a supplier has multiple contacts and if one of the contacts accepts the terms for participation, then other contacts are not required to take any action on that and the ''Terms for Participation ''will not be displayed to the remaining contacts. &lt;br /&gt;
*''Allow New Line Item During RFx Phase'': '''Select''' ''Yes'' if you want to allow new line items to be added during the entire RFx lifecycle, However, the newly added line item(s) can be part of a round only before it starts and not in an ongoing round. The default value of this option is set to ''No.'' &lt;br /&gt;
*'''Select''' the following contracts (if applicable) by clicking&amp;amp;nbsp;the drop-down arrow or the ''Lookup Search icon:'' &lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Associate Contracts'': Sourcing app allows the buyers to create contracts such as NDA, for all the suppliers selected when creating RFx. A separate contract will be created for each supplier.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Mandatory Contracts'': It is the contract that should be present for all the suppliers before the RFx moves to the next phase. The value in this option will be populated automatically based on the value selected in the earlier option. You cannot select any value in this option if you don’t select anything in the&amp;amp;nbsp;''Associate Contracts ''option.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Prerequisite Contracts'': The Supplier can access the RFx instance only after it is in ''Approved'' state. After the Round is started, a ''Terms for Participation ''window is displayed to the supplier with an option to accept or decline. The Suppliers can access the RFx only after they sign the Prerequisite Contract after accepting the terms for participation. If the Suppliers do not sign the contracts a message is displayed by ICM, along with a list of documents asking the suppliers to complete the documents before accessing the RFx.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The values selected in these fields are populated on the RFx ''Details'' page under the ''Agreements'' tab. This enables the buyer to create Agreements relevant to the RFx that is created.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Selecting an Associate Contract automatically populates the values in ''Mandatory Contracts ''and ''Prerequisite Contracts. ''If you do not select any values in any of the contracts, these values be displayed as blank when you create the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
The attributes for mandatory and prerequisite contracts are interlinked and both the attributes display the list of different contract types that can be associated with the RFx. ICM validates whether the prerequisite and mandatory contracts added to the RFx are in ''Approved'' state.&lt;br /&gt;
&lt;br /&gt;
*Primary Currency: '''Select''' the primary currency for the RFx. If the user preferred currency is not added in the currency master, then the corporate currency is set as the primary currency of the RFx. For example, if user preferred currency is SGD which is not added in currency master, then the primary currency is set as USD assuming it is set as the corporate currency.&amp;amp;nbsp; &lt;br /&gt;
*Allowed Currency:&amp;amp;nbsp;'''Select''' the allowed currency for the RFx. This is the currency allowed by the buyers for the suppliers operating from a different country. The selected allowed currencies can be used by suppliers for bidding. Suppliers can view the newly added currencies even when the round is Open and select them as required. Buyers can update the allowed currency at any time using ''Modify RFx'' option. The allowed currencies cannot be deleted after the RFx is approved. &lt;br /&gt;
*Exchange Rate Basis:Buyers can view the exchange rate throughout the RFx lifecycle by clicking the View Exchange Rate Table icon at RFx, Line Items, Bids, Bid Responses. The exchange rate basis can have one of the following values: &lt;br /&gt;
**RFx Open Date: This is selected by default.&amp;amp;nbsp;When this is selected, system uses the start date of first round for determining exchange rates &lt;br /&gt;
**RFx Closed Date: This date must be selected same as the round end date. When this is selected, system uses close date of the last round for determining applicable exchange rates &lt;br /&gt;
**User selected: This is the date from when the exchange rates are made applicable by the buyers. It is mandatory to select the Exchange Rate Date that is enabled after selecting User Selected as the Exchange Rate Basis. The selected date is used as the date to determine the exchange rate and all calculations of currency conversion.&amp;amp;nbsp;Buyers can view the exchange rate information when selecting the Exchange Rate Basis as RFx Open Date or RFx Closed Date after the RFx is approved and the round is created.   &lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Click''' ''Next''. The ''Select Template'' ''(Step 3 of 4)'' page opens. This is an optional step depending upon how the application is configured. Usually there would be only one template associated with the RFx that is selected automatically. However, multiple templates can be configured in ICM as per the business requirement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;8.&amp;amp;nbsp;'''Click''' ''Next''. The ''Verify'' ''(Step 4 of 4)'' page opens. Verify all the information you have just entered.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;9.&amp;amp;nbsp;'''Click''' the ''Create RFx'' button. The RFx ''Details'' page opens.&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== RFx Details Page ===&lt;br /&gt;
&lt;br /&gt;
Buyers can view the current status and details of the RFx in various sections of the left navigation pane on ''RFx Details'' page. Buyers can also perform a variety of actions based on the current state of the RFx.&lt;br /&gt;
&lt;br /&gt;
Here is a brief description of the options in the left navigation pane of ''RFx Details ''page.&lt;br /&gt;
&lt;br /&gt;
*RFx Information: This section displays the basic details of the current RFx instance. It has the following sub-sections. &lt;br /&gt;
**Summary: Displays the name of the RFx instance (that is added while creating), who created it, and RFx instance details. &lt;br /&gt;
**Details: Displays the details specified while creating the RFx instance. &lt;br /&gt;
**Preview: Displays how the RFx document would actually look. '''Click '''the ''click here ''in ''To see full document click here ''to download and view the full document in pdf format.   &lt;br /&gt;
*RFx Package: This section displays the following details. &lt;br /&gt;
**Line Items: '''Click '''this option to view the list of line items associated with the RFx. '''Click '''the plus icon next to ''Line Items ''on RFx ''Details'' page to add a new line item. &lt;br /&gt;
**Internal Attachments: Displays the list of existing internal attachments associated with the RFx. Internal attachments are associated documents uploaded by the buyers and only available to the buyer team. '''Click '''the plus icon next to internal attachments to add new to the list. &lt;br /&gt;
**External Attachments: Displays the list of existing external attachments associated with the RFx. External attachments are associated documents uploaded by the buyers and available to both buyers and suppliers. '''Click '''the plus icon next to external attachments to add new to the list.   &lt;br /&gt;
*Supplier Information: Displays the list of existing suppliers and allows buyers to add new suppliers along with their contact information. &lt;br /&gt;
**Suppliers: Displays the list of suppliers added to the RFx created by the buyer. '''Click '''the plus icon next to ''Suppliers ''to add a new supplier. &lt;br /&gt;
**Supplier Contacts: Displays the list of supplier contacts that are populated automatically after you select the suppliers in the previous step.   &lt;br /&gt;
*Agreements: Displays all the agreements that were selected initially when creating the RFx. &lt;br /&gt;
*Collaboration: Allows the internal or external team members to communicate with other internal or external team members by creating topics and posting messages in it. &lt;br /&gt;
*Round: Displays the list of rounds associated with the RFx along with their current state. '''Click '''the plus icon next to Round to add a new round. &lt;br /&gt;
*Awarding: Displays the RFx instance awarded to the supplier. After the rounds are closed and awarding is initiated by the buyer, an awarding object is created. &lt;br /&gt;
*Team: Displays the members added to the team for this RFx instance. '''Click '''the plus icon to add new team members to the RFx. &lt;br /&gt;
*Notes: Displays the additional information about the RFx if it is added. &lt;br /&gt;
*History: Displays how the RFx has progressed till now. The actions performed by the buyer are displayed by the buyer on the RFx instance are displayed under ''History'' in the left navigation pane on RFx ''Details'' page. &lt;br /&gt;
&lt;br /&gt;
Buyers can perform the following actions from the ''RFx Details ''page:&lt;br /&gt;
&lt;br /&gt;
*''Download RFx Document: '''''Click '''this button to download the RFx document in Microsoft Word format. The downloaded document is based on the template selected while creating the RFx instance. &lt;br /&gt;
*Edit: '''Click '''this button to go back and make changes to the RFx that you created. &lt;br /&gt;
*Send for Approval: '''Click '''this button to send the RFx instance for approval. &lt;br /&gt;
*Download Package: '''Click '''this button to download the RFx instance along with all its associations. You can select specific associations that you want to download or select the RFx instance checkbox to download the RFx package. RFx package is downloaded as a zip file that contains all the attachments relevant to the RFx. When the zip file is exported on user’s local machine, a folder structure is created that resembles the RFx structure, and the files are located in the respective locations.The files names will be the same when downloading or uploading them to ICM. The files will be downloaded as per the defined folder structure and folder naming conventions&amp;amp;nbsp;which helps users to easily identify files under individual folders of the RFx and avoid any discrepancies.&amp;amp;nbsp;The folder names for associations are now same as the contract type display names such as line items, internal attachments, round, bid response and so on.Downloading the RFx package displays the folders for RFx, round, bid, RFI Response as they are displayed in ICM. The rounds and bids folders are merged in a single folder and the template files are added to the relevant round or bid folder. This is applicable for RFx and RFI.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
*Delete: '''Click '''this button to delete the RFx instance. After deleting the RFx instance, the ''Sourcing ''page opens and the deleted RFx will not be available on the user interface. &lt;br /&gt;
&lt;br /&gt;
=== Copy RFx&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can copy the RFx which not only saves time but also reduces duplication of efforts. Additionally global sourcing involves globally distributed buyer team that may clone the sourcing event at the regional level and link them with one another. Linking the copied RFx to the original RFx can be achieved by selecting&amp;amp;nbsp;''Yes ''next to&amp;amp;nbsp;''Link to RFx&amp;amp;nbsp;''on&amp;amp;nbsp;''Copy Record&amp;amp;nbsp;''window.&lt;br /&gt;
&lt;br /&gt;
Along with the RFx, users now have the ability to select any associated documents (parent-child or peer associations) where the Allow Copy with Associations is set to Yes at the Contract Type level. If this flag is set to ''No'', then only the RFx will be copied without its associations.&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Copy the Sourcing event. &lt;br /&gt;
*Select and copy associations such as line items, questions, questionnaires, suppliers, supplier contacts, internal and external attachments, and commitments.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Copying the RFx helps:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Exclude associations from being copied. &lt;br /&gt;
*Exclude the attributes of associations &lt;br /&gt;
*Exclude the automatic attachments from being copied to the new RFx &lt;br /&gt;
&lt;br /&gt;
Users can copy the RFx team based on the configured role. If RFx is copied by a user who is not primary owner of that RFx, then that user becomes the primary owner of the RFx.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Viewing the audit log by clicking&amp;amp;nbsp;''History&amp;amp;nbsp;''on RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. &lt;br /&gt;
&lt;br /&gt;
If the source role and target role is configured, the user roles will be same for the RFx being copied.&lt;br /&gt;
&lt;br /&gt;
If the source role is:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Primary owner and the same user is copying the current RFx, then target role is ignored (the copying user is part of the team as primary owner)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Same as target role, then team member role is set as source role&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the target role is:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Primary owner, then a log gets added and the team member role is set as source role. For the rest of role mappings, the target role properties are set for the team member. If they are blank, then a log gets added and no action taken.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Authorized users can configure the Agreement Contract Type and set ''Allow Copy with Associations'' field to ''Yes'' to enable copying the existing RFx.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;You can copy an RFx from the:&lt;br /&gt;
&lt;br /&gt;
*''Sourcing index&amp;amp;nbsp;''page &lt;br /&gt;
*RFx&amp;amp;nbsp;''details&amp;amp;nbsp;''page &lt;br /&gt;
&lt;br /&gt;
To copy an RFx from the&amp;amp;nbsp;''Sourcing&amp;amp;nbsp;''index page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''dots&amp;amp;nbsp;next to the RFx on the Sourcing index page and then '''click&amp;amp;nbsp;'''''Copy Record''. The ''Copy Record'' window opens''.''&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' ''Yes'' next to ''Link To RFx'' that is being copied.&amp;amp;nbsp;This links the RFx copy that is being created with the source RFx. If you select No, it will not be linked with the source RFx. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.'''Click''' ''Copy Record'' to copy the RFx without the associations. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.'''Click''' ''Expand All'' on the ''Copy Record'' window to display all the associations of the RFx to be copied. You can click ''Collapse All'' to display only the parent level associations.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select''' the ''Associations'' checkbox to select all the associations of the RFx to copy. You can select specific associations that you want to copy.&amp;amp;nbsp;You can select the commitments from the Copy Record window to be copied from the source RFx to the destination RFx.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Copy''. The name of the copied RFx is same as the source RFx. The ''Initiate RFx'' button is displayed on RFx Details page after the copy of the RFx is created.The primary owner of the copied RFx will be the&amp;amp;nbsp;user who initiates the copy operation.&lt;br /&gt;
&lt;br /&gt;
The RFx copy is created and RFx ''Details ''page opens with the status of the RFx as ''Draft.''&lt;br /&gt;
&lt;br /&gt;
To copy the RFx from RFx ''Details ''page:&lt;br /&gt;
&lt;br /&gt;
The RFx can also be copied from RFx ''Details ''page by following steps 2-5 in the To copy RFx from Sourcing Index page section.&lt;br /&gt;
&lt;br /&gt;
'''Viewing the audit log of Copy RFx'''&lt;br /&gt;
&lt;br /&gt;
You can view the audit log of the copy RFx event by clicking ''History ''on the RFx ''Details ''page.&lt;br /&gt;
&lt;br /&gt;
'''Viewing the Linked RFx&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
You can view the linked RFx from the RFx ''Details ''page.&lt;br /&gt;
&lt;br /&gt;
To view the linked RFx:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Related RFx&amp;amp;nbsp;''on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. The list&amp;amp;nbsp;of related RFx is displayed.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' ''View Record'' icon next to the RFx that allows viewing the original RFx using which its copy was created.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Linking the RFx'''&lt;br /&gt;
&lt;br /&gt;
Linking RFx with another RFx allows keeping track of the activities happening with both RFx thereby allowing to manage multiple RFx within one another. &amp;amp;nbsp; Linking the RFx helps in supporting global sourcing that involves globally distributed buyers’ team. This team may clone the sourcing event at the regional level to identify and shortlist suppliers and link the sourcing events with one another. ICM allows to link the source and destination RFx.&lt;br /&gt;
&lt;br /&gt;
To configure the two way linkage:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''the ''View record ''icon next to the RFx Contract Type on the ''Configuration ''page. The contract type ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;&amp;amp;nbsp;'''Navigate '''to the ''Associations ''section and '''select '''the attribute ''ICMAppSrcRelatedRFx.''&lt;br /&gt;
&lt;br /&gt;
*If ''Yes ''is selected next to ''Allow Two-way linkage'', it allows the source RFx to display the target RFx in the related RFx; likewise, the target RFx displays the source RFx. &lt;br /&gt;
*If ''No'' is selected next to Allow Two-way linkage, then the target RFx will display source RFx linkage in related RFx. not link the RFx copy with the source RFx. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Update'' and navigate to ''Verify'' page and '''click''' ''Update'' to update the RFx contract type. This links the copied RFx with Source RFx.&lt;br /&gt;
&lt;br /&gt;
You can also add linked RFx from RFx ''Details'' page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To add linked RFx from RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''the plus icon next to ''Related RFx ''on RFx ''Details ''page. The ''Related RFx ''window opens displaying the list of related source RFx that you can link with the copied RFx.&lt;br /&gt;
&lt;br /&gt;
2.'''Click '''''Select ''to select and link the copied RFx with the source RFx from the available list.&lt;br /&gt;
&lt;br /&gt;
'''Exclude&amp;amp;nbsp;auto-attached associated documents during copy'''&lt;br /&gt;
&lt;br /&gt;
When a user copies the RFx with auto-attached associations, ICM excludes all auto attached associations from being copied to the new RFx. The auto-attached associations won’t be displayed on the ''Copy Record'' window. The resulting RFx has the selected manual associations and its own auto-attached associations as per the configured rules. This avoids the unnecessary upload of files into the ICM repository and duplication of association records on copied RFx.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding Line Items ==&lt;br /&gt;
&lt;br /&gt;
You can add line items at any stage of the RFx instance depending upon RFx configuration settings. Line items are products that the buyer is looking to procure through the RFx instance. When you create the RFx instance, the RFx ''Details'' page opens with the RFx status displayed as ''Draft''. You can use the left navigation pane to add one or more line items. You can also add line items using Microsoft Excel import by selecting the file from your local machine and uploading it to ICM Sourcing.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 1.png|720px|7.9 Sourcing Adding Line Items 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To add line items:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Create Association'' icon next to ''Line Items'' under the ''RFx Package'' tab. The ''Line Items'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 2.png|720px|7.9 Sourcing Adding Line Items 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Enter '''the values in the following fields:&lt;br /&gt;
&lt;br /&gt;
*''Name'': '''Enter''' the name of the items you want to procure. For example, ''Laptops''. &lt;br /&gt;
*''Part Number'': '''Enter''' the specific details of the item. For example, Model number. &lt;br /&gt;
*''Description'': '''Enter''' more information of the item. &lt;br /&gt;
*''Unit of Measure'': '''Select''' appropriate unit of measure depending upon the item. For example, ''Piece, Each, Pack'', etc. &lt;br /&gt;
*''Unit of Order'': '''Select''' the unit of order you want to procure. For example, in the multiples of 10s or 100s etc. &lt;br /&gt;
*''Desired Quantity'': '''Enter''' the quantity of the item you wish to procure. &lt;br /&gt;
*''Bid Currency'': '''Select''' the currency from the drop-down. &lt;br /&gt;
*''Additional Details'': You can upload a file that contains additional details about the item. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 3.png|720px|7.9 Sourcing Adding Line Items 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Create''. The Line Item is created. The Count is updated in the left navigation pane on the RFx&amp;amp;nbsp;''Details'' page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 4.png|720px|7.9 Sourcing Adding Line Items 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''Repeat steps 1-3 to add more line items.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Adding Bulk Line Items&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
The bulk associations capability has enabled ICM to handle large number of associations in the tune of thousands, by presenting itself as a lightweight association as well as tremendously improving performance. The Sourcing event can include many line items for an RFx ranging from 500 to 50,000 maximum. In Sourcing, line items are considered as associations.&amp;amp;nbsp;&amp;lt;br/&amp;gt; The bulk association configuration has now been simplified by providing a Enable Bulk Processing flag at contract type definition level which triggers a set of defaults that has been intentionally restricted. The end user experience for the bulk association has not changed from the way that the conventional association is handled from the UI, rather the underlying data structure has been further enhanced to make it go the distance.&amp;amp;nbsp;&amp;lt;br/&amp;gt; Performance has been the key while introducing and designing this new association, which has given way to the new type of instance, namely the Proxy Instance, which is retrieved in every GET call. The actual instances are referred by using this proxy instance, thereby reducing the load on the GET APIs. Specialized GET and SET APIs have also been introduced for bulk associations to improve its adaptability and ease-of-use.&amp;lt;br/&amp;gt; Bulk associations have very effectively consumed the Elastic Search Bulk API to sync a large set of data at one go, rather than the traditional way of one instance at a time, adding to the boost in performance.&amp;lt;br/&amp;gt; Bulk association is tweaked to be able to address the large data situation that Sourcing apps require, including:&lt;br /&gt;
&lt;br /&gt;
*Disabling the workflow &lt;br /&gt;
*Restricting the system associations to just team&amp;amp;nbsp; &lt;br /&gt;
*Restricting document assembly &lt;br /&gt;
*Simplifying the association team by maintaining team at proxy level to use access level as ALL or NONE, using a layer over the existing robust ICM authorization &lt;br /&gt;
*Restricting indexing of bulk associations attributes in the parent, which can be achieved through a technical configuration.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
You can enable the bulk processing flag, when you want to process large number of associations. For normal associations or non-BACT associations, bulk processing flag need not be enabled. Enabling this flag, accelerates the performance in handling large number of instances. &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To enable the Bulk Processing flag:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Configuration'' &amp;gt; ''Create Contract Type''. &amp;amp;nbsp;The ''Select a type of contract'' window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Select '''the Contract Type. For example, ''Associated Document.''&lt;br /&gt;
&lt;br /&gt;
3''.&amp;amp;nbsp;'''''Click'''''Next. ''The ''Create Contract Type Wizard ''page opens.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''E''''''nter '''a ''Contract Type Name''. For example,''Acme Bulk Pro''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Toggle '''''Enable Bulk Processing'' flag to ''Yes''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Next.''&lt;br /&gt;
&lt;br /&gt;
''7.&amp;amp;nbsp;'''''Enter&amp;amp;nbsp;'''details on the following tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Create''&amp;amp;nbsp;on the&amp;amp;nbsp;''Verify&amp;amp;nbsp;''tab to create the contract type. It will now be in the&amp;amp;nbsp;''Draft&amp;amp;nbsp;''status.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Send for Approval'' to send the contract type for approval. When approved, the contract type ''Acme Bulk Pro'' will be displayed in the grid in the ''Approved'' status.&lt;br /&gt;
&lt;br /&gt;
To upload bulk associations (line items)&lt;br /&gt;
&lt;br /&gt;
'''Prerequisites'''&lt;br /&gt;
&lt;br /&gt;
*RFx is created''.'' &lt;br /&gt;
*In the RFx, line item exists as an association with&amp;amp;nbsp;''Enable Bulk Processing&amp;amp;nbsp;''flag as&amp;amp;nbsp;''Yes.'' &lt;br /&gt;
*The event rule&amp;amp;nbsp;''Associated Document Created&amp;amp;nbsp;''is created. &lt;br /&gt;
&lt;br /&gt;
To upload bulk associations:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Import associated document data template&amp;amp;nbsp;''icon. The&amp;amp;nbsp;''Upload Document&amp;amp;nbsp;''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Select File''. Upload the file with the list of line items.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Upload File.&amp;amp;nbsp;''The record processing details will be updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Ok.&amp;amp;nbsp;''The RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page opens. The line item associations are updated.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The team for any one instance of line item is same for any other instances of line items.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Selecting Suppliers ==&lt;br /&gt;
&lt;br /&gt;
Suppliers are the businesses that participate in the RFx bidding process. The suppliers and their information such as ''Names, Addresses, Contact Numbers, Email Addresses,'' and&amp;amp;nbsp;''Supplier Contacts'' are added to the Masterdata. The name of the existing&amp;amp;nbsp;''Supplier Contact Name''&amp;amp;nbsp;has been modified to&amp;amp;nbsp;''Supplier Contact Full Name.&amp;amp;nbsp;''For example, John Doe.&amp;amp;nbsp;Buyers can remove the supplier contact from the Supplier Contact page. This updates the count of selected supplier contact.The selected supplier contact’s full name is displayed on the new selected supplier contacts interface.The suppliers and supplier contacts saved earlier are now displayed as pre-selected when adding more suppliers and supplier contacts.&lt;br /&gt;
&lt;br /&gt;
Now, the buyers can use any supplier and supplier contact masterdata contract type to add suppliers.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;supplier contact full name column will be displayed by default on:&lt;br /&gt;
&lt;br /&gt;
*''Supplier Contact&amp;amp;nbsp;''selection page &lt;br /&gt;
*''Details&amp;amp;nbsp;''page of Supplier Contact &lt;br /&gt;
*Grid view of the supplier contact association&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This makes it is easier for buyers and Administrators to identify and select the correct supplier if there are multiple suppliers with the same first name. This is applicable for bulk agreements too.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This is applicable for RFx, RFI and Rounds.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To add suppliers:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''the ''Create Association'' icon next to ''Suppliers''. The ''Supplier'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 1.png|720px|7.9 Sourcing Selecting Suppliers 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Search''' for the desired supplier(s) or '''select''' the suppliers from the displayed list under the ''Supplier'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 2.png|720px|7.9 Sourcing Selecting Suppliers 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Next''. The ''Supplier Contacts'' tab opens displaying the contact details of the suppliers.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SupplierContactFullName.png|720px|7.12-SupplierContactFullName.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''''the View Record ''icon next to the supplier’s name. The supplier’s contact details are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SupplierContactRecord.PNG|720px|7.12-SupplierContactRecord.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Select''' the desired ''Supplier Contact(s)''.&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''''Save''. The selected supplier(s) and supplier contact(s) are added to the RFx instance. The count is updated under the ''Supplier Information'' tab in the left navigation pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 5.png|720px|7.9 Sourcing Selecting Suppliers 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Error Validations&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers have the option to select mandatory and pre-requisite contracts while creating the RFx. The attributes for mandatory and prerequisite contracts are interlinked. The prerequisite contracts are derived from the mandatory contracts. So, if the buyers select the following contracts – NDA, Warranty Agreement, Fixed Cost Agreement as mandatory, then they have the option to select one or more, or all as prerequisite contracts.&lt;br /&gt;
&lt;br /&gt;
Suppose the NDA is the prerequisite contract for accessing the RFx, then the validations are done such that ICM expects that the Instance of an NDA contract type for all the suppliers is associated with the RFx and contract should be in Approved state. Similarly, if Contract Types are made mandatory, then the instances of these should exist before RFx is sent for approval.&lt;br /&gt;
&lt;br /&gt;
Buyers will now receive a system message when:&lt;br /&gt;
&lt;br /&gt;
*Sending an RFx for approval in case prerequisite contracts are not in the Approved status for suppliers. &lt;br /&gt;
*Sending an RFx for approval in case mandatory contracts are either not created or exist in one of the states - ''Cancelled'', ''Expired'', or ''Terminated'' for suppliers.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Buyers will be able to view the validations for the prerequisite and mandatory contracts for the shortlisted suppliers only.&amp;lt;br/&amp;gt; For a shortlisted supplier, if all the prerequisite contracts are inactive or if any one of the contracts is active but not in Approved or later state, then the validations will be displayed.&amp;amp;nbsp;&amp;lt;br/&amp;gt; For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Draft state) and NDA 2 (in Waiting for Approval) state, then validations will be displayed.&amp;amp;nbsp;&amp;lt;br/&amp;gt; The validations will not be displayed for shortlisted suppliers when at least one active prerequisite contract exists, and all such contracts are in Approved or later state.&amp;amp;nbsp;&amp;lt;br/&amp;gt; For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Approved state) and NDA 2 (in Expired state), no validations will be displayed since one of the two prerequisite contracts (NDA 1) is in Approved or later state.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To view the error validations:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Send for Approval&amp;amp;nbsp;''on RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. The&amp;amp;nbsp;''Contract Status Validation&amp;amp;nbsp;''window opens.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-1.png|720px|7.12-Validations-1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the ''Mandatory Contracts&amp;amp;nbsp;''tab next to the&amp;amp;nbsp;''Prerequisite Contracts&amp;amp;nbsp;''tab.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-2.png|720px|7.12-Validations-2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
A message is displayed as above indicating that the contract types are either not created or exist in one of the statuses as Expired, Terminated, or Cancelled. In this example, the contract types Fixed Cost and NDA are not created.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the plus icon to the mandatory contract that was configured when creating the RFx and create the mandatory contracts using the process to create the bulk agreement.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Send for Approval.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Status Validation&amp;amp;nbsp;''window opens displaying only the Prerequisite contracts.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-3.png|720px|7.12-Validations-3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Creating Bulk Agreements ===&lt;br /&gt;
&lt;br /&gt;
The Sourcing App offers you a convenient way of creating bulk agreements with the suppliers, without having to move out of RFx instance that you are working on. The agreements must be already configured in ICM. These agreements may be made mandatory for the supplier to sign before the supplier can participate in the RFx. The RFx displays all the agreements created from the RFx and they have all the agreement information. This allows the buyer to conveniently navigate between the RFx and the agreement associated with the RFx.&lt;br /&gt;
&lt;br /&gt;
To create an agreement:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Create Association'' icon next to the agreements in the left navigation pane on the RFx ''Details'' page. For example, NDA, Warranty Agreement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 1.png|720px|7.9 Sourcing Creating Bulk Agreements 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 2.png|720px|7.9 Sourcing Creating Bulk Agreements 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. The ''Attributes (Step 2 of 4)'' page opens in the new browser tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 3.png|720px|7.9 Sourcing Creating Bulk Agreements 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Enter''' values for all the attributes, some of which may be mandatory.&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''the ''Select Multiple Suppliers ''icon next to ''Suppliers and Agreement Details. ''The ''Supplier ''page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 4.png|720px|7.9 Sourcing Creating Bulk Agreements 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. Repeat steps 2 to 6 from the ''Selecting Suppliers'' section to add a supplier.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click '''''Next''. The ''Select Template'' ''(Step 3 of 4) ''page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 5.png|720px|7.9 Sourcing Creating Bulk Agreements 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Select''' a Template.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 6.png|720px|7.9 Sourcing Creating Bulk Agreements 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click '''''Next. ''The ''Verify'' page opens. Verify all the information you have entered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 7.png|720px|7.9 Sourcing Creating Bulk Agreements 7.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9. '''Click''' the ''Bulk Create Agreement ''button. The agreement is created.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 8.png|720px|7.9 Sourcing Creating Bulk Agreements 8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' the ''View Record'' icon next to the NDA instance on the ''Sourcing'' page. The NDA’s ''Details'' page opens with the NDA in the ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The number of instances of the selected NDA Agreement created matches with the number of suppliers selected while creating the RFx.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 9.png|720px|7.9 Sourcing Creating Bulk Agreements 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
After the Agreement is created for a supplier, you can proceed with the agreement workflow as configured. For example, you can send the agreement for approval.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 10.png|720px|7.9 Sourcing Creating Bulk Agreements 10.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click''' the ''Send For External Signature'' button on the ''Details'' page. The agreement is sent to the supplier(s) for signatures. The status of the agreement changes to ''Executed'' when all the suppliers sign the NDA.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 11.png|720px|7.9 Sourcing Creating Bulk Agreements 11.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Link Existing Contracts&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Link existing supplier contracts (prerequisite, mandatory, associated contracts) allowing buyers to leverage existing contracts with suppliers.&amp;amp;nbsp; &lt;br /&gt;
*View the contracts of the supplier when creating the bulk agreement that allows assigning any supplier contact as a signatory for the agreement. &lt;br /&gt;
*View the signatory of the prerequisite contracts that allows the suppliers to connect with the signatory if there are any issues with the contracts.&amp;amp;nbsp; &lt;br /&gt;
*Send the agreements for approval in bulk that helps avoid sending the agreements for approval individually.&amp;amp;nbsp; &lt;br /&gt;
*Select the new signature type&amp;amp;nbsp;''Click to Sign&amp;amp;nbsp;''allowing suppliers to participate in the sourcing event by previewing, accepting, or declining the terms and conditions set by the buyer.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
To link existing contracts:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Create Association&amp;amp;nbsp;''next to the agreements in the left navigation pane on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. For example, NDA, Warranty Agreement. The&amp;amp;nbsp;''Please Confirm&amp;amp;nbsp;''window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Existing Contracts. ''The&amp;amp;nbsp;''Select existing contracts to link to RFx page&amp;amp;nbsp;''opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the contract that you want to link with the RFx and&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Link Contracts.&amp;amp;nbsp;''&lt;br /&gt;
&lt;br /&gt;
The selected contract is linked with the RFx.&amp;amp;nbsp;&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Adding Team Members ===&lt;br /&gt;
&lt;br /&gt;
A team of Approvers, Reviewers, and Observers can be added to the RFx instance for completing the workflow.&lt;br /&gt;
&lt;br /&gt;
To add team members:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Team'' tab on the RFx ''Details'' page. The ''Add Team'' page opens in the right pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Team Members 1.png|720px|7.9 Sourcing Adding Team Members 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''Add Team'' icon. The ''Select User'' window opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter '''the search term in the ''Search User'' field to search for a desired user.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select '''a User from the displayed user tiles.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select '''a ''Role''. For example, ''Approver'', ''Business Owner'', ''Observer'', etc.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Select''' or '''enter''' the ''Step Number'' if you select ''Approver'' in the ''Select Role'' field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter '''a comment in the ''Add Note'' field (optional). You can see this comment under the ''Notes'' tab.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Select '''the ''Send Notification ''checkbox if you want to the user to receive a notification of the task.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Add''. The ''User has been added successfully'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Team Members 2.png|720px|7.9 Sourcing Adding Team Members 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Sending the RFx Instance for Approval ===&lt;br /&gt;
&lt;br /&gt;
The RFx instance must be in ''Approved ''state before a round is created automatically and the RFx workflow can be completed.&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Send For Approval ''button on the RFx ''Details'' page. The RFX instance is sent for approval to the approver(s) you have selected in the ''Team''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Internal Approval for RFX Instance 1.png|720px|7.9 Sourcing Internal Approval for RFX Instance 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The status changes to ''Waiting For Approval. ''A task is created for each approver.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Internal Approval for RFX Instance 2.png|720px|7.9 Sourcing Internal Approval for RFX Instance 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
When all the approvers approve the RFx instance, the status changes to ''Approved''. After the RFx is approved, the first round is created automatically.&lt;br /&gt;
&lt;br /&gt;
== Working with Rounds ==&lt;br /&gt;
&lt;br /&gt;
One cycle of seeking proposals/bids from suppliers and evaluating them is referred to as a round. A complete Sourcing event may comprise of multiple rounds. The first round is created automatically (if the start and end dates are entered) as soon as the RFx instance is approved. You can see the round on the RFX ''Details'' page. You must open the round instance and fill in additional details. There can be multiple rounds for one RFx instance.&lt;br /&gt;
&lt;br /&gt;
Here is the round workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Working With Rounds 1.png|720px|7.9 Sourcing Working With Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Starting the Scheduled Rounds ===&lt;br /&gt;
&lt;br /&gt;
You can schedule a round by entering the ''Round Start Date'' and ''End Date'' when creating the RFx instance. The buyer must click the ''Start Round'' button on the ''Round'' ''Details'' page to start the round.&lt;br /&gt;
&lt;br /&gt;
To start the round:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Round'' on the RFx ''Details'' page. The auto created round instance is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Only the first round is created automatically. The buyers must create the other rounds manually as required.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Scheduling Rounds 1.png|720px|7.9 Sourcing Scheduling Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''the ''View Record'' icon. The Round&amp;amp;nbsp;''Details'' page opens with the round in ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Scheduling Rounds 2.png|720px|7.9 Sourcing Scheduling Rounds 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click '''the ''Start Round'' button to start the Round. The status of the round changes to ''Approved ''when the round is approved and the status of the RFx changes to&amp;amp;nbsp;''Bidding&amp;amp;nbsp;''''Open'''''&amp;lt;b&amp;gt;.&amp;lt;/b&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''When the round is approved the status changes to ''Scheduled''. When the current date is equal to start date of the round, the status changes to ''Open''.&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating Rounds ===&lt;br /&gt;
&lt;br /&gt;
The buyer can also create a round manually if they need to conduct multiple rounds with the supplier. The buyer can create the round manually only if the RFx instance is in ''Approved ''state.&lt;br /&gt;
&lt;br /&gt;
To create a round (manually):&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Create Association'' icon under the ''Round'' tab on the RFx ''Details'' page. The ''Create RFx -Round'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 1.png|720px|7.9 Sourcing Creating Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''Organization Unit'' icon to select the ''Organization Unit''.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter''' an appropriate name for the round.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Enter''' relevant details in the ''AppSrc Description'' field.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a ''Round Start Date''. This field is already populated with the current date. You can select a different date and time if required.&lt;br /&gt;
&lt;br /&gt;
6. '''Select''' a ''Round End Date ''and time.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The date and time is displayed based on the user’s locale settings. When the user with different locale views the RFx, the date and time are converted to their locale.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 2.png|720px|7.9 Sourcing Creating Rounds 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click '''''Next''. The ''Verify'' page opens. Verify all the information.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 3.png|720px|7.9 Sourcing Creating Rounds 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8. '''Click '''the ''Create Round'' button. The Round’s ''Details'' page opens. The round is now created in ''Draft ''state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 4.png|720px|7.9 Sourcing Creating Rounds 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9. '''Click '''the ''Start Round'' button to begin the Round. The status of the round changes to ''Approved and Scheduled''. When the round is approved the status changes to ''Approved and Scheduled''. When the current date is equal to start date of the round the status changes to ''Published''.&lt;br /&gt;
&lt;br /&gt;
=== Editing Round start and end dates&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&lt;br /&gt;
&lt;br /&gt;
*Edit the&amp;amp;nbsp;round start and end date when the round is in one of the below states: &lt;br /&gt;
**Draft &lt;br /&gt;
**Waiting for Approval &lt;br /&gt;
**On Hold &lt;br /&gt;
**Open &lt;br /&gt;
**Approved&amp;amp;nbsp;   &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;You can make changes only to the round end date when the round is in ''Open'' state. The changes made to the round start and end date are captured in the ''History'' on round ''Details'' page.It is not mandatory to run the approval workflow for the round after changing the ''Planned Start Date'' and ''Planned End Date''.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To edit the round start and end date:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Round'' on RFx ''Details'' page. The list of rounds is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate1.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''View Record'' icon next to the round for which you want to edit the start and end date. The round ''Details'' page opens and displays the existing start and end date of the rounds.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;3.&amp;amp;nbsp;'''Click''' ''Edit''. The ''Edit'' round page opens.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate2.png|720px|7.12-EditRound-Start-EndDate2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;Make the necessary changes to the start and end date of the round depending on the state of the round. You can edit just the time of start and end date of the round and not required to change the date always.&amp;amp;nbsp;For example, the&amp;amp;nbsp;''Planned Start Date&amp;amp;nbsp;''was July 8, 2020, 12:00 AM and the&amp;amp;nbsp;''Planned End Date&amp;amp;nbsp;''was August 8, 2020 12:00 AM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Open:&amp;amp;nbsp;You can make the changes only to the ''Planned End Date'' of the round. For example, you can change the ''Planned End Date'' to September 8, 2020 in place of the earlier date August 8, 2020 &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Buyers can edit the round end date when the status of the RFx changes to In Modification when the previous status of the round is Open.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate3.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*''Approved/''On Hold:&amp;amp;nbsp;You can make the changes to the ''Planned Start Date'' and ''Planned End Date'' values of the round. For example, you can change the ''Planned Start Date'' to July 15, 2020 in place of the earlier date July 8, 2020 earlier and ''Planned End Date'' to September 15, 2020 as against August 8, 2020 earlier. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate4.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Buyers can enter the planned start and end date of the RFx when creating the round manually. The values for Actual Start Date and Actual End Date are populated based on the actual date when the round is opened or closed.&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Update&amp;amp;nbsp;''on round&amp;amp;nbsp;''Verify&amp;amp;nbsp;''page.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate5.png|720px|7.12-EditRound-Start-EndDate5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The round ''Details'' page opens and displays the edited round start and end date.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate6.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;The changes made to the round start and end date are captured in the ''History'' on round ''Details'' page.It is not mandatory to run the approval workflow for the round after changing the ''Planned Start Date'' and ''Planned End Date''.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Working with Bids ==&lt;br /&gt;
&lt;br /&gt;
A bid is a collection of quotes for each Line Item.&amp;amp;nbsp;The system generates bids when a round is in ''Published'' state. The supplier can view the bids that were submitted in the previous rounds if the buyer selects ''Yes ''in the ''AppSrc Auto Copy Bids from the Previous Round ''option when creating the RFx.&lt;br /&gt;
&lt;br /&gt;
Depending upon how the RFx instance is configured in the organization, suppliers must sign all the prerequisite agreements before submitting the bid responses. The suppliers won’t be able to view the RFx instance until the prerequisite agreement is in ''Executed'' state.&lt;br /&gt;
&lt;br /&gt;
Here is the bid workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Working With Bids 1.png|720px|7.9 Sourcing Working With Bids 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Submitting&amp;amp;nbsp;Bids ===&lt;br /&gt;
&lt;br /&gt;
A supplier can submit bid responses when the round is published.&lt;br /&gt;
&lt;br /&gt;
To submit bid responses:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Sourcing ''tile on the ''Dashboard'' after logging on to ICM. The ''Sourcing'' page opens. This page displays a list of all the RFx instances, rounds, and bids that the supplier is a part of.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 1.png|720px|7.9 Sourcing Submitting Bids 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' the ''View Record'' icon next to the bid that you want to respond to. The Bid’s ''Details'' page opens with the bid is in ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 2.png|720px|7.9 Sourcing Submitting Bids 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Bid Response'' under ''Quotation Details ''tab. The bid response is displayed in the grid along with its details such as ''Item Name'', ''Quotation ID'' etc. As the buyer had added two line items, the count is updated to 2 next to ''Bid Response''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 3.png|720px|7.9 Sourcing Submitting Bids 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Edit'' icon. The ''Edit Bid Response'' window opens. It displays the information of the line item given by the buyer.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 4.png|720px|7.9 Sourcing Submitting Bids 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 5.png|720px|7.9 Sourcing Submitting Bids 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
5. '''Enter''' values for the following fields:&lt;br /&gt;
&lt;br /&gt;
*''AppSrc Base Price'': The price for one unit of the product mentioned in the line item. &lt;br /&gt;
*''AppSrc Total Price'': Calculated automatically by ICM depending upon the buyers requirement of the number of pieces and the base price you entered. &lt;br /&gt;
*''AppSrc Quote Currency'': '''Select''' the appropriate currency from the drop-down. &lt;br /&gt;
&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 6.png|720px|7.9 Sourcing Submitting Bids 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' the ''Update ''button. The bid response is updated. The ''Bid Response'' window closes.&lt;br /&gt;
&lt;br /&gt;
7. '''Click '''''Submit ''on the ''Bid'' ''Details'' page. The bid response is now submitted to the buyer. The status of the bid changes to ''Submitted.''&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp; You should click on submit only after you have entered values for all items.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 7.png|720px|7.9 Sourcing Submitting Bids 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can submit the bid responses for one or all line items. Follow steps 1-7 to do so.&amp;lt;/div&amp;gt; &lt;br /&gt;
After submitting bids, suppliers cannot edit bids. To edit the bids, the suppliers must '''click '''''Withdraw''. This changes the status of the bid to ''Withdrawn. ''Suppliers can revert withdrawal by clicking ''Revert Withdrawal. ''They can also edit their bids and submit again.&lt;br /&gt;
&lt;br /&gt;
As soon as one supplier submits a bid, the status of the round changes to ''In Bidding''. When all the bid responses are submitted, the buyer can:&lt;br /&gt;
&lt;br /&gt;
*Manually close the round by clicking the ''Close Round'' button on the Round’s ''Details'' page if the ''AppSrc'' ''Allow Foreclosure of Rounds ''is toggled to ''Yes ''when creating the RFx by the buyer. &lt;br /&gt;
&lt;br /&gt;
Or&lt;br /&gt;
&lt;br /&gt;
*The round closes as per the scheduled ''Round End Date ''and Time. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The buyer can choose to close the round even when only one supplier has submitted the bid or even if no one has submitted a bid. The status of the RFx changes to ''Round'' ''Closed''.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 8.png|720px|7.9 Sourcing Submitting Bids 8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Buyers can now view the status of bids for each supplier regardless of whether the RFx is an open or sealed envelope depending on the status of the bid. These statuses include:&lt;br /&gt;
&lt;br /&gt;
*''Submitted and Closed'': Buyers and the user assigned as a surrogate buyer can view the bids in ''Submitted ''status, and the rounds are closed. &lt;br /&gt;
*''Declined'': The suppliers declining the bid cannot participate in the upcoming rounds. The status of the bid is displayed according to the type of RFx when the bid is in Declined state. &amp;amp;nbsp;&amp;amp;nbsp; &lt;br /&gt;
**''Open RFx'': Buyers and the user assigned as a surrogate buyer can view the round in Open and Closed state. &lt;br /&gt;
**''Sealed Envelope'': Buyers can view the bid when the state of RFx changes to ''Closed'' state. The suppliers who declined the bid cannot participate in the ongoing or upcoming rounds nor can they revert decline to participate in the round again.   &lt;br /&gt;
&lt;br /&gt;
Buyers cannot view the status of the bids depending on the following status of the bid.&lt;br /&gt;
&lt;br /&gt;
*''Not Submitted and Closed'': Buyers and the user assigned as a surrogate buyer cannot view the bid response when the bid is not submitted, and the round is closed. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The bid responses are displayed or hidden based on whether the bid was submitted or not submitted by the suppliers.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Bid Analysis ===&lt;br /&gt;
&lt;br /&gt;
It is the process of analyzing supplier responses with an intent to compare one against the others along the evaluation criteria. When all the desired ''Bid Responses'' are received, you can view and analyze all the responses to be able to take informed decision.&lt;br /&gt;
&lt;br /&gt;
At least one round should be completed for conducting bid analysis, otherwise the user gets an error message indicating that the round must be started to download bid analysis. For an RFx with ''Sealed Envelope'', at least one round must be in ''Closed'' state to download the excel sheet for bid analysis.&lt;br /&gt;
&lt;br /&gt;
The bid analysis Excel will contain all the bids, for all the suppliers, for all the rounds. The bid analysis will also contain currency information of bid currency and RFx primary currency, along with bid analysis attributes converted to RFx primary currencies. An attribute for bid analysis is defined in the masterdata. Users can add the bid analysis attribute for each RFx item and specify its value while creating an RFx or associated document. This helps the buyer to get all the information in the Excel sheet to be able to easily analyze a bid for a supplier.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&lt;br /&gt;
&lt;br /&gt;
*Download bid analysis excel on bid level and round level. When bid analysis is performed on bid, the downloaded bid analysis Excel it will include the responses for a specific respective supplier whose bid was chosen. Whereas, when bid analysis is performed on round level, downloaded bid analysis Excel will include the bid responses data for all the suppliers present in the round. &lt;br /&gt;
*&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Enter the values for bid analysis attributes and upload the bid analysis Excel sheet. The value of bid analysis attributes will be updated in the bid response.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Downloading and Uploading Bid Analysis for round'''&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Bid Analysis'' button, on the ''Round'' ''Details'' page. The ''Bid Analysis'' page opens.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Download File. ''The Excel file of Bid Analysis is downloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Open '''the downloaded Excel. View the Bid Analysis attributes.&lt;br /&gt;
&lt;br /&gt;
Once downloaded, you can edit the Bid analysis attributes such as ''Bonus'', ''Net Landed Cost'', ''Difference''.&lt;br /&gt;
&lt;br /&gt;
4.'''Enter '''''Bid Analysis attribute'' values. For example: '''Enter''' value of ''Bonus as 2.44 instead of 1.05. &amp;amp;nbsp;''&lt;br /&gt;
&lt;br /&gt;
5.'''Click''' ''Save'' to '''save''' the file'''.'''&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''''Select File To Upload'' on the Bid Analysis window. The updates will be made, and the''Bid Analysis has been Saved successfully'' message will be displayed in the ''Upload Summary'' section.&lt;br /&gt;
&lt;br /&gt;
7.'''Click''' ok.&lt;br /&gt;
&lt;br /&gt;
'''Downloading and uploading bid analysis for bid:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
1.'''Click the '''''Bid Analysis'' button, on ''Bid'' ''Details'' page.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.'''Click''' ''Download File. ''The Excel file of Bid Analysis is downloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Open '''the downloaded Excel file. View the Bid Analysis attributes.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;You can add the bid analysis attribute for each RFx item and specify its value while creating an agreement or associated document.&lt;br /&gt;
&lt;br /&gt;
If you add any invalid value in Bid Analysis attribute, error validation message will be displayed in last column.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example: '''Enter''' ''hdsjbvshd'' in ''Bonus, and enter ''any random value in ''Net Landed Cost'' ''chdsjbcs'', then Error message is displayed, indicating that Bonus and Net landed Cost are invalid.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
You can not edit other attributes such as ''Freight, Insurance, landed Cost''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''To analyze bid response:'''&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Download Bid Analysis'' button on the RFx ''Details'' page. An Excel sheet containing the bid responses is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Bid Analysis 1.png|720px|7.9 Sourcing Bid Analysis 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Open''' the Excel sheet. You can view the all the data collected from the bid responses such as ''Supplier ID, Item Name, Item Description'', etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Bid Analysis 2.png|720px|7.9 Sourcing Bid Analysis 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Downloading Associations and Attachments&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing app offers an ability to download either all or selected associations (line items, attachments, supplier documents) and attachments (files uploaded to the RFx instance) for review and analysis purposes. This is applicable for all types of RFx instances and all documents (buyer’s and suppliers). The application retains the file names of the attachments as they were while uploading them so that they could be recognized easily.&lt;br /&gt;
&lt;br /&gt;
The files names will be the same when downloading or uploading them to ICM. The files will be downloaded as per the defined folder structure and folder naming conventions &amp;amp;nbsp; which helps users to easily identify files under individual folders of the RFx and avoid any discrepancies. The folder names for associations are now same as the contract type display names such as line items, internal attachments, round, bid response and so on.&lt;br /&gt;
&lt;br /&gt;
Downloading the RFx package displays the folders for RFx, round, bid, RFI Response as they are displayed in ICM. The rounds and bids folders are merged in a single folder and the template files are added to the relevant round or bid folder. This is applicable for both RFx and RFI.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Buyers can select and download attachments of buyers and suppliers as required. Suppliers can only download the attachments to which they have access or the attachments they upload.&amp;lt;/div&amp;gt; &lt;br /&gt;
The attachments can be viewed under ''RFx Package'' tab on the RFx ''Details'' page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Downloading Associations and Attachments 1.png|720px|7.9 Sourcing Downloading Associations and Attachments 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To download associations and attachments:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Download Package'' button on the RFx ''Details'' page. The ''Download'' window opens displaying all the Associations and attachments.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Downloading Associations and Attachments 2.png|720px|7.9 Sourcing Downloading Associations and Attachments 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' the items you wish to download.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage1.png|720px|7.12-DownloadPackage1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Download''. The selected files are downloaded in a zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage2.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage3.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage4.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The selected attachments are downloaded as per the folder structure they are part of in the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
== Awarding Workflow ==&lt;br /&gt;
&lt;br /&gt;
You can initiate the Awarding workflow after receiving all the required bid responses and after all the rounds are in ''Round(s) Closed ''state. Buyers can award multiple suppliers using Excel upload.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': After the awarding is initiated, the buyer cannot create new rounds. If a new round is required to be created after awarding is initiated, you must delete the awarding object and then create a new Round.&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating Awarding Instances ===&lt;br /&gt;
&lt;br /&gt;
To create award instances:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Initiate Award'' button on the RFx ''Details'' page.&amp;amp;nbsp; The ''Attributes (Step 2 of 4)'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 1.png|720px|7.9 Sourcing Creating Awarding Instances 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' the ''Organization Unit''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Agreement Code'' is system generated.&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select''' the Business Status (Default value - ''Draft'').&lt;br /&gt;
&lt;br /&gt;
4. '''Enter '''the ''Name'' of the Awarding instance. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Upload '''an ''AppSrc Supporting Document,'' if any.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 2.png|720px|7.9 Sourcing Creating Awarding Instances 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Next''. The ''Select Template (Step 3 of 4)'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 3.png|720px|7.9 Sourcing Creating Awarding Instances 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Select '''the template.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Click '''''Next''. The ''Verify'' page opens. Verify all the information.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 4.png|720px|7.9 Sourcing Creating Awarding Instances 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' the ''Create Award Agreement'' button. The RFx ''Details'' page opens with the status ''Awarding Initiated''. The RFx Awarding instance is created with the status ''Draft''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 5.png|720px|7.9 Sourcing Creating Awarding Instances 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Awarding Decision ===&lt;br /&gt;
&lt;br /&gt;
After creating the Awarding instance, you must create an Awarding ''Decision'' as an Association. The awarding decision contains all the details of all items and the Supplier(s) who are being awarded the RFx along with the other details such as award quantity and price.&lt;br /&gt;
&lt;br /&gt;
To create awarding decision:&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''RFx Awarding'' on the RFx ''Details'' page. The awarding instance is displayed in the right pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 1.png|720px|7.9 Sourcing Awarding Decision 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''the ''View Record'' icon. The Awarding ''Details'' page opens with the status ''Draft''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 2.png|720px|7.9 Sourcing Awarding Decision 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Create Association'' icon next to ''AppSrc Awarding Decision''. The ''Awarding Decision'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 3.png|720px|7.9 Sourcing Awarding Decision 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the icon next to ''Download File. ''The ''Awarding Decision ''excel sheet is downloaded on your computer. This excel sheet displays the information such as the price submitted by the supplier, the quantity of line items, currency, etc. This excel sheet contains all the bids for all suppliers for all rounds.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 4.png|720px|7.9 Sourcing Awarding Decision 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Enter '''values for the required fields entered on Excel.&lt;br /&gt;
&lt;br /&gt;
*''Awarded Quantity: '''''Enter''' the quantity you are procuring through this awarding decision. &lt;br /&gt;
*''Awarded Percentage: '''''Enter''' a value for ''Awarding Percentage''. Awarding can be given to one or more suppliers at a time. For example, the selected supplier may get 60% of the order. If it’s not being shared, it is 100 percent. This process is known as ''Split Awarding''. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can add either the awarded quantity or the awarded percentage and the other is automatically derived. For example, if you enter the awarded percentage, the awarded quantity will be calculated automatically.&amp;lt;/div&amp;gt; &lt;br /&gt;
Some of the important points to note when splitting the award between multiple suppliers are:&lt;br /&gt;
&lt;br /&gt;
*The awarding percentage will be calculated automatically up to 2 decimal places when you add the awarding quantity. &lt;br /&gt;
*The awarding quantity will be calculated automatically based on the percentage entered to the nearest integer. &lt;br /&gt;
*If you want to delete a particular Line Item, delete the records from ''Awarded Quantity ''and ''Awarded Percentage ''columns. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 5.png|720px|7.9 Sourcing Awarding Decision 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Select File to Upload ''and then '''click '''''Upload File ''to upload the file. The awarding decisions are created automatically after uploading the File.&lt;br /&gt;
&lt;br /&gt;
=== Sending the Awarding Instance for Approval ===&lt;br /&gt;
&lt;br /&gt;
After creating the awarding instance and adding the awarding decision, you must send the awarding instance for approval.&lt;br /&gt;
&lt;br /&gt;
To send the awarding instance for approval:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Publish'' on the Awarding ''Details'' page. The ''Published Successfully'' message is displayed.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' ''Send For Approval''. The status of the Awarding instance changes to ''Approved'' once the Approver(s) approve it.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 1.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 2.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
After the awarding instance is approved, the status of the RFx instance changes to ''Awarded''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 3.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Updating the Awarding Contracts ===&lt;br /&gt;
&lt;br /&gt;
Contracts are created for the selected suppliers who are awarded with RFx. You can update the pricing information of the awarded line items in the awarded contracts.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can update the RFx only when it is in ''Awarded ''state and awarding contracts such as NDA is present in the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
To update awarded contracts:&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Update Awarding Contracts ''on the ''RFx Details ''page. The ''Please Confirm ''window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Updating Awarded Contracts 1.png|720px|7.9 Sourcing Updating Awarded Contracts 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Updating Awarded Contracts 2.png|720px|7.9 Sourcing Updating Awarded Contracts 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This validates whether the awarding decision contains any associations.&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Yes. ''The ''Information ''window opens displaying a message ''Update to agreements for awarding decision initiated. Please check the agreements after some time.''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:7.9 Sourcing Updating Awarded Contracts 3.png|720px|7.9 Sourcing Updating Awarded Contracts 3.png]]''&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click '''''Ok. ''The process of updating awarding contracts starts in the background and the status of the RFx changes to ''Contract Initiated. ''After the process is completed successfully, the status of the RFx changes to ''Contract Created.''&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''the agreement associated with the RFx in the left pane on ''RFx Details ''page. The ''Agreement Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Click '''''Awarding Decision ''in the left pane on ''Agreement Details ''page. The awarding decision will be displayed with the updated pricing information.&lt;br /&gt;
&lt;br /&gt;
== Currency Support ==&lt;br /&gt;
&lt;br /&gt;
ICM administrators can now configure the corporate currency in the currency master.&lt;br /&gt;
&lt;br /&gt;
*Add currencies to the currency masterdata that contains the list of currencies that can be used in the RFx event.&amp;amp;nbsp; &lt;br /&gt;
*Manage currencies from the currency master by adding new currency &lt;br /&gt;
*Set a single currency as a corporate currency for the organization to be used in Sourcing events.&amp;amp;nbsp; &lt;br /&gt;
*Restrict the option to delete the currency and only allow to make it inactive. &lt;br /&gt;
&lt;br /&gt;
=== Configuring the Corporate Currency in Currency Master ===&lt;br /&gt;
&lt;br /&gt;
You can create a new currency record in ICM using the extended currency master.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Configuration&amp;amp;nbsp;''and then&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Masterdata&amp;amp;nbsp;''on the&amp;amp;nbsp;''Home&amp;amp;nbsp;''page. The&amp;amp;nbsp;''Create Masterdata&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Configure Corporate Currency 1.png|720px|7.12-Configure Corporate Currency 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the&amp;amp;nbsp;''Extended Currency Master&amp;amp;nbsp;''from the drop-down list and&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Attributes&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Configure Corporate Currency 2.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the following information on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Masterdata code: This is generated automatically after the masterdata is created.&amp;amp;nbsp; &lt;br /&gt;
*Currency Name:&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the name of the currency. For example, Singapore Dollar.&amp;amp;nbsp; &lt;br /&gt;
*Currency Code:&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the code of the currency. For example, SGD.&amp;amp;nbsp; &lt;br /&gt;
*Symbol:&amp;amp;nbsp;'''Enter''' the symbol for the currency you are creating. This helps in identifying the currency used in the financial transactions happening between the buyers and suppliers. For example, $.&amp;amp;nbsp; &lt;br /&gt;
*Country Name:&amp;amp;nbsp;Enter the name of the country to which this currency would belong to. For example, Singapore. &lt;br /&gt;
*Valid Until:&amp;amp;nbsp;'''Select''' the date until which this currency will be considered valid. For example, the currency can be valid for one year from the date it was created which could be July 8 2022. &lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save.&amp;amp;nbsp;''The currency will be created and saved in ICM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To be configure corporate currency in currency master:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''User Administration'' and then '''click''' ''Application Settings''. The ''Application Settings'' page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Next&amp;amp;nbsp;''on ''Entity Color Configuration'' and ''User Theme'' pages. The ''Other Configuration'' page opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Select''' the Corporate Currency from the drop-down list. For example, select SGD (Singapore Dollar).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Update&amp;amp;nbsp;''to set the corporate currency for the RFx.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Exchange rate of different currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
ICM administrators can add, remove, or edit the exchange rates in the currency masterdata. The specified currency exchange rate must have a defined validity period and also set currency exchange rates for supported currencies.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To set exchange rate of different currencies:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1. Repeat step 1 from the configuring the corporate currency in currency master section.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.'''Select''' the ''Exchange Rate Master'' from the drop-down list and '''click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the following information on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Masterdata Code: This is generated automatically after the masterdata is created. &lt;br /&gt;
*From Currency Code: '''Select&amp;amp;nbsp;'''the&amp;amp;nbsp;''From Currency Code. ''This denotes the currency from which you want to convert a particular amount to a different currency. For example, '''select&amp;amp;nbsp;'''''SGD.&amp;amp;nbsp;'' &lt;br /&gt;
*To Currency Code:&amp;amp;nbsp;'''Select '''the&amp;amp;nbsp;''To Currency Code. ''This denotes the currency to which you want to convert a particular amount. For example,&amp;amp;nbsp;'''select '''''USD.'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;You can only select the From Currency Code and To Currency Code for the currencies that are still valid.&amp;lt;/div&amp;gt; &lt;br /&gt;
*&amp;amp;nbsp;Exchange From Date:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the date from which you want to make the exchange rate applicable. For example,&amp;amp;nbsp;'''select&amp;amp;nbsp;'''July 8, 2020.&amp;amp;nbsp; &lt;br /&gt;
*Exchange To Date:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the date to which you want to make the exchange rate applicable. The&amp;amp;nbsp;''To Date&amp;amp;nbsp;''must always be greater than the&amp;amp;nbsp;''From Date.&amp;amp;nbsp;''For example,&amp;amp;nbsp;'''select&amp;amp;nbsp;'''''August 8, 2020.&amp;amp;nbsp;'' &lt;br /&gt;
*Exchange Rate:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''or&amp;amp;nbsp;'''enter&amp;amp;nbsp;'''the exchange rate. This is the value of one currency used to convert to another currency. For example, 1 SGD equals to 0.72 USD.&amp;amp;nbsp; &lt;br /&gt;
*Rate Type:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the type of rate from the available list. For example, Fixed Rate which is the rule applied by the government that ties the country's currency official exchange rate with another country's currency.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save.&amp;amp;nbsp;''The masterdata record for exchange rate between two currencies is added successfully. The masterdata&amp;amp;nbsp;''Details&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
You can perform the following operations on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Edit&amp;amp;nbsp;''to make changes to the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
*Deactivate:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Deactivate&amp;amp;nbsp;''to deactivate but not delete the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
*Delete:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Delete&amp;amp;nbsp;''to delete the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Selecting RFx currency and allowed currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
You can select the RFx currency (primary currency) and allowed currency on Create RFx page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*&amp;amp;nbsp;Primary Currency: '''Select''' the primary currency for the RFx. If the user preferred currency is not added in the currency master, then the corporate currency is set as the primary currency of the RFx. For example, if user preferred currency is SGD which is not added in currency master, then the primary currency is set as USD assuming it is set as the corporate currency.&amp;amp;nbsp; &lt;br /&gt;
*Allowed Currency: '''Select''' the allowed currency for the RFx. This is the currency allowed by the buyers for the suppliers operating from a different country. The selected allowed currencies can be used by suppliers for bidding. Suppliers can view the newly added currencies even when the round is Open and select them as required. Buyers can update the allowed currency at any time using ''Modify RFx'' option. The allowed currencies cannot be deleted after the RFx is approved. &lt;br /&gt;
&lt;br /&gt;
=== Selecting the exchange rate for RFx&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can view the exchange rate throughout the RFx lifecycle by clicking the View Exchange Rate Table icon at RFx, Line Items, Bids, Bid Responses. The exchange rate basis can have one of the following values:&lt;br /&gt;
&lt;br /&gt;
*RFx Open Date: This is selected by default. When this is selected, system uses the start date of first round for determining exchange rates. &lt;br /&gt;
*RFx Closed Date: This date must be selected same as the round end date. When this is selected, system uses close date of the last round for determining applicable exchange rates. &lt;br /&gt;
*User selected:&amp;amp;nbsp;This is the date from when the exchange rates are made applicable by the buyers. It is mandatory to select the Exchange Rate Date that is enabled after selecting User Selected as the Exchange Rate Basis. The selected date is used as the date to determine the exchange rate and all calculations of currency conversion. &lt;br /&gt;
&lt;br /&gt;
Buyers can view the exchange rate information when selecting the Exchange Rate Basis as RFx Open Date or RFx Closed Date after the RFx is approved and the round is created.&lt;br /&gt;
&lt;br /&gt;
=== Selecting currencies from the list of allowed currencies ===&lt;br /&gt;
&lt;br /&gt;
Buyers can select the currencies for the RFx from the list of allowed currencies. The allowed currencies of the RFx can be used as the bid currency by the suppliers. The currency attributes for the line item are restricted to RFx currency. The modified allowed currencies for RFx are displayed as bid currencies for all items.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Changing the currency type in any of the line item displays a validation message in the Validation Description column in the Microsoft Excel if the values selected in Primary and Allowed Currency is different.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Using currency conversion rate in Bid Analysis ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Download the bid analysis excel file that allows to view all the bids received from multiple suppliers. &lt;br /&gt;
*Download the flexible bid analysis excel file for each round after it is closed that allows viewing bids received and converted to RFx primary currency. This file contains information for specific rounds only. &lt;br /&gt;
&lt;br /&gt;
=== Bidding in multiple currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can take the following actions when the bid is created:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Select the bid currency that allows submitting the surrogate bid on behalf of the supplier.&amp;amp;nbsp; &lt;br /&gt;
*View the changes made to the bid that are logged in the&amp;amp;nbsp;''History&amp;amp;nbsp;''section on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Suppliers can take the following actions when bidding in multiple currencies:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the supported currencies for RFx that allows viewing the applicable exchange rates&amp;amp;nbsp; &lt;br /&gt;
*Select the currency from the list of allowed currencies that allows submitting the bid in the selected currency.&amp;amp;nbsp; &lt;br /&gt;
*Submit the bids for items in selected currencies. &lt;br /&gt;
*Upload or download the bidding template that allows adding bid information in excel sheet and upload to ICM.&amp;amp;nbsp; &lt;br /&gt;
*Update the bid currency using ICM and Microsoft Excel.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Currency information in awarding contracts&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can take the following actions when updating the awarding object for RFx using multiple currencies.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Download the awarding decision template that will allow to award the desired suppliers and upload the awarding decision. &lt;br /&gt;
*Include the bid currency in awarding decision that allows including bid currency and other bid information in the contract.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
== Glossary ==&lt;br /&gt;
&lt;br /&gt;
*'''Sourcing event:''' Refers to any solicitation process whether informational, commercial or technical. &lt;br /&gt;
*'''RFx:''' An acronym for X where X may stand for Information, Proposal or Quotation. &lt;br /&gt;
*'''Round:''' A single cycle of seeking proposals or bids from suppliers and evaluating them may be referred to as a Round. There can be multiple Rounds in the complete RFx lifecycle. &lt;br /&gt;
*'''Bid:''' The response submitted by a supplier for an RFx created by the buyer is referred to as a bid. Typically, bid is part of a round and may be revised and resubmitted by the supplier till the round is open. &lt;br /&gt;
*'''Bid Analysis: '''The process of comparing and analyzing the bid responses received from one or more suppliers along with the evaluation criteria created by the buyer. &lt;br /&gt;
*'''Awarding: '''When all the Rounds are closed, and bids are analyzed, the buyer creates the awarding instance that will be awarded to the suppliers that match the evaluation criteria. &lt;br /&gt;
*'''Split Awarding: '''It is the process of awarding the RFx to multiple suppliers with specifically decided quantity or percentage. &lt;br /&gt;
&lt;br /&gt;
'''Related Topics''':''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[ICM_Sourcing_App|ICM Sourcing&amp;amp;nbsp;App]]&amp;amp;nbsp;|&amp;amp;nbsp;''&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Working_with_RFx&amp;diff=14248</id>
		<title>Working with RFx</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Working_with_RFx&amp;diff=14248"/>
				<updated>2020-08-11T17:14:01Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Working with RFx Instances =&lt;br /&gt;
&lt;br /&gt;
The Icertis Sourcing app enables buyers to create and manage end-to-end RFx process. RFx is an acronym for Request for '''x''', where '''x''' may stand for ''Information ''or''Proposal ''or ''Quotation''. Buyers can create an RFx instance, add line items, select suppliers and supplier contacts, create agreements with the suppliers, add team members to the instance for review and approval process and send the instance for approval. Here is the RFx workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing RFX Instances 1.png|720px|7.9 Sourcing RFX Instances 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating the RFx Instance ===&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Sourcing'' tile on the ''Dashboard''. The ''Sourcing'' page opens. A list of all the RFx instances is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SourcingTile.PNG|720px|7.12-SourcingTile.PNG]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;2.&amp;amp;nbsp;'''Click '''the ''Create RFx'' tile. The ''Create RFx'' page opens.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;3.&amp;amp;nbsp;'''Select '''a Sourcing Entity from the ''Select Sourcing Entity'' drop-down in the ''Contract Type Details'' ''(Step 1 of 4)'' section. The contract type is configured in the system with default Attributes.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;4.&amp;amp;nbsp;'''Click''' ''Next''. The ''Attributes'' ''(Step 2 of 4)'' page opens. The attributes are grouped under various categories. For example, ''RFx Information'', ''RFx Configs, etc''.&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Select '''or&amp;amp;nbsp;'''enter '''the values for all the required Attributes in the ''RFx Information'' group:&lt;br /&gt;
&lt;br /&gt;
*Enter the RFx Name. For example, ''Procurement for Admin department''. &lt;br /&gt;
*Enter the information of the RFx instance in the ''Description'' field. &lt;br /&gt;
*Select an ''AppSrc Category'' from the drop-down. For example, ''Office Supplies''. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can also add a new category by clicking the plus icon next to&amp;amp;nbsp;''Category'' option.&amp;lt;/div&amp;gt; &lt;br /&gt;
*'''Select '''the ''Round Start Date'' and ''Round End Date''. When you enter the dates, a round is created automatically as soon as the RFx instance is approved. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing RFX Instances 5.png|720px|7.9 Sourcing RFX Instances 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Select''' appropriate values and settings under the ''RFx Configs'' group.&lt;br /&gt;
&lt;br /&gt;
*''View Bids'': '''Select''' an appropriate option from the drop-down. There are following options: &lt;br /&gt;
**''Sealed Envelope'': When you select this option, the bid and bid responses are not visible to the buyer until the round is closed. &lt;br /&gt;
**''Open RFx'': When you select this option, the bid and bid responses are visible to the buyer throughout the duration of the round, as and when the supplier submits the bid.   &lt;br /&gt;
&lt;br /&gt;
*'''Select''' ''Yes'' or ''No'' for the following Configuration settings as per your requirement: &lt;br /&gt;
**''Auto Copy Bids from Previous Rounds: '''''Select '''''Yes ''if you want to allow copying bids from previous rounds to the new round. This displays the bids from the current rounds and the bid responses with values added in the most recently closed round in ''Draft ''state to the suppliers. The default value for this option is set to ''Yes.&amp;amp;nbsp;'' &lt;br /&gt;
**''Allow Foreclosure of Rounds'': '''Select''' ''Yes'' if you want to close the round before the selected round end date. This displays the ''Close Round ''button on the ''Round Details ''page to close the round manually. If you select ''No, ''then the round will be closed automatically only after the selected round end date. The default value for this option is set to ''Yes.'' &lt;br /&gt;
**''Allow New Supplier During RFx Phase'': '''Select''' ''Yes'' if you want to allow new supplier(s) to be added during the entire RFx lifecycle. However, the newly added supplier(s) can participate in a new round only, not in an ongoing round. The default value for this option is set to ''No.''   &lt;br /&gt;
&lt;br /&gt;
*'''Enter '''the ''Terms For Participation'' in the given field. They will be visible to the suppliers only if the buyer adds it when creating the RFx. The suppliers should accept the Terms before they can participate in the bidding process of the RFx. For example, if a supplier has multiple contacts and if one of the contacts accepts the terms for participation, then other contacts are not required to take any action on that and the ''Terms for Participation ''will not be displayed to the remaining contacts. &lt;br /&gt;
*''Allow New Line Item During RFx Phase'': '''Select''' ''Yes'' if you want to allow new line items to be added during the entire RFx lifecycle, However, the newly added line item(s) can be part of a round only before it starts and not in an ongoing round. The default value of this option is set to ''No.'' &lt;br /&gt;
*'''Select''' the following contracts (if applicable) by clicking&amp;amp;nbsp;the drop-down arrow or the ''Lookup Search icon:'' &lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Associate Contracts'': Sourcing app allows the buyers to create contracts such as NDA, for all the suppliers selected when creating RFx. A separate contract will be created for each supplier.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Mandatory Contracts'': It is the contract that should be present for all the suppliers before the RFx moves to the next phase. The value in this option will be populated automatically based on the value selected in the earlier option. You cannot select any value in this option if you don’t select anything in the&amp;amp;nbsp;''Associate Contracts ''option.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;''Prerequisite Contracts'': The Supplier can access the RFx instance only after it is in ''Approved'' state. After the Round is started, a ''Terms for Participation ''window is displayed to the supplier with an option to accept or decline. The Suppliers can access the RFx only after they sign the Prerequisite Contract after accepting the terms for participation. If the Suppliers do not sign the contracts a message is displayed by ICM, along with a list of documents asking the suppliers to complete the documents before accessing the RFx.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The values selected in these fields are populated on the RFx ''Details'' page under the ''Agreements'' tab. This enables the buyer to create Agreements relevant to the RFx that is created.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Selecting an Associate Contract automatically populates the values in ''Mandatory Contracts ''and ''Prerequisite Contracts. ''If you do not select any values in any of the contracts, these values be displayed as blank when you create the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
The attributes for mandatory and prerequisite contracts are interlinked and both the attributes display the list of different contract types that can be associated with the RFx. ICM validates whether the prerequisite and mandatory contracts added to the RFx are in ''Approved'' state.&lt;br /&gt;
&lt;br /&gt;
*Primary Currency: '''Select''' the primary currency for the RFx. If the user preferred currency is not added in the currency master, then the corporate currency is set as the primary currency of the RFx. For example, if user preferred currency is SGD which is not added in currency master, then the primary currency is set as USD assuming it is set as the corporate currency.&amp;amp;nbsp; &lt;br /&gt;
*Allowed Currency:&amp;amp;nbsp;'''Select''' the allowed currency for the RFx. This is the currency allowed by the buyers for the suppliers operating from a different country. The selected allowed currencies can be used by suppliers for bidding. Suppliers can view the newly added currencies even when the round is Open and select them as required. Buyers can update the allowed currency at any time using ''Modify RFx'' option. The allowed currencies cannot be deleted after the RFx is approved. &lt;br /&gt;
*Exchange Rate Basis:Buyers can view the exchange rate throughout the RFx lifecycle by clicking the View Exchange Rate Table icon at RFx, Line Items, Bids, Bid Responses. The exchange rate basis can have one of the following values: &lt;br /&gt;
**RFx Open Date: This is selected by default.&amp;amp;nbsp;When this is selected, system uses the start date of first round for determining exchange rates &lt;br /&gt;
**RFx Closed Date: This date must be selected same as the round end date. When this is selected, system uses close date of the last round for determining applicable exchange rates &lt;br /&gt;
**User selected: This is the date from when the exchange rates are made applicable by the buyers. It is mandatory to select the Exchange Rate Date that is enabled after selecting User Selected as the Exchange Rate Basis. The selected date is used as the date to determine the exchange rate and all calculations of currency conversion.&amp;amp;nbsp;Buyers can view the exchange rate information when selecting the Exchange Rate Basis as RFx Open Date or RFx Closed Date after the RFx is approved and the round is created.   &lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Click''' ''Next''. The ''Select Template'' ''(Step 3 of 4)'' page opens. This is an optional step depending upon how the application is configured. Usually there would be only one template associated with the RFx that is selected automatically. However, multiple templates can be configured in ICM as per the business requirement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;8.&amp;amp;nbsp;'''Click''' ''Next''. The ''Verify'' ''(Step 4 of 4)'' page opens. Verify all the information you have just entered.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;9.&amp;amp;nbsp;'''Click''' the ''Create RFx'' button. The RFx ''Details'' page opens.&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== RFx Details Page ===&lt;br /&gt;
&lt;br /&gt;
Buyers can view the current status and details of the RFx in various sections of the left navigation pane on ''RFx Details'' page. Buyers can also perform a variety of actions based on the current state of the RFx.&lt;br /&gt;
&lt;br /&gt;
Here is a brief description of the options in the left navigation pane of ''RFx Details ''page.&lt;br /&gt;
&lt;br /&gt;
*RFx Information: This section displays the basic details of the current RFx instance. It has the following sub-sections. &lt;br /&gt;
**Summary: Displays the name of the RFx instance (that is added while creating), who created it, and RFx instance details. &lt;br /&gt;
**Details: Displays the details specified while creating the RFx instance. &lt;br /&gt;
**Preview: Displays how the RFx document would actually look. '''Click '''the ''click here ''in ''To see full document click here ''to download and view the full document in pdf format.   &lt;br /&gt;
*RFx Package: This section displays the following details. &lt;br /&gt;
**Line Items: '''Click '''this option to view the list of line items associated with the RFx. '''Click '''the plus icon next to ''Line Items ''on RFx ''Details'' page to add a new line item. &lt;br /&gt;
**Internal Attachments: Displays the list of existing internal attachments associated with the RFx. Internal attachments are associated documents uploaded by the buyers and only available to the buyer team. '''Click '''the plus icon next to internal attachments to add new to the list. &lt;br /&gt;
**External Attachments: Displays the list of existing external attachments associated with the RFx. External attachments are associated documents uploaded by the buyers and available to both buyers and suppliers. '''Click '''the plus icon next to external attachments to add new to the list.   &lt;br /&gt;
*Supplier Information: Displays the list of existing suppliers and allows buyers to add new suppliers along with their contact information. &lt;br /&gt;
**Suppliers: Displays the list of suppliers added to the RFx created by the buyer. '''Click '''the plus icon next to ''Suppliers ''to add a new supplier. &lt;br /&gt;
**Supplier Contacts: Displays the list of supplier contacts that are populated automatically after you select the suppliers in the previous step.   &lt;br /&gt;
*Agreements: Displays all the agreements that were selected initially when creating the RFx. &lt;br /&gt;
*Collaboration: Allows the internal or external team members to communicate with other internal or external team members by creating topics and posting messages in it. &lt;br /&gt;
*Round: Displays the list of rounds associated with the RFx along with their current state. '''Click '''the plus icon next to Round to add a new round. &lt;br /&gt;
*Awarding: Displays the RFx instance awarded to the supplier. After the rounds are closed and awarding is initiated by the buyer, an awarding object is created. &lt;br /&gt;
*Team: Displays the members added to the team for this RFx instance. '''Click '''the plus icon to add new team members to the RFx. &lt;br /&gt;
*Notes: Displays the additional information about the RFx if it is added. &lt;br /&gt;
*History: Displays how the RFx has progressed till now. The actions performed by the buyer are displayed by the buyer on the RFx instance are displayed under ''History'' in the left navigation pane on RFx ''Details'' page. &lt;br /&gt;
&lt;br /&gt;
Buyers can perform the following actions from the ''RFx Details ''page:&lt;br /&gt;
&lt;br /&gt;
*''Download RFx Document: '''''Click '''this button to download the RFx document in Microsoft Word format. The downloaded document is based on the template selected while creating the RFx instance. &lt;br /&gt;
*Edit: '''Click '''this button to go back and make changes to the RFx that you created. &lt;br /&gt;
*Send for Approval: '''Click '''this button to send the RFx instance for approval. &lt;br /&gt;
*Download Package: '''Click '''this button to download the RFx instance along with all its associations. You can select specific associations that you want to download or select the RFx instance checkbox to download the RFx package. RFx package is downloaded as a zip file that contains all the attachments relevant to the RFx. When the zip file is exported on user’s local machine, a folder structure is created that resembles the RFx structure, and the files are located in the respective locations.The files names will be the same when downloading or uploading them to ICM. The files will be downloaded as per the defined folder structure and folder naming conventions&amp;amp;nbsp;which helps users to easily identify files under individual folders of the RFx and avoid any discrepancies.&amp;amp;nbsp;The folder names for associations are now same as the contract type display names such as line items, internal attachments, round, bid response and so on.Downloading the RFx package displays the folders for RFx, round, bid, RFI Response as they are displayed in ICM. The rounds and bids folders are merged in a single folder and the template files are added to the relevant round or bid folder. This is applicable for RFx and RFI.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp; &lt;br /&gt;
*Delete: '''Click '''this button to delete the RFx instance. After deleting the RFx instance, the ''Sourcing ''page opens and the deleted RFx will not be available on the user interface. &lt;br /&gt;
&lt;br /&gt;
=== Copy RFx&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can copy the RFx which not only saves time but also reduces duplication of efforts. Additionally global sourcing involves globally distributed buyer team that may clone the sourcing event at the regional level and link them with one another. Linking the copied RFx to the original RFx can be achieved by selecting&amp;amp;nbsp;''Yes ''next to&amp;amp;nbsp;''Link to RFx&amp;amp;nbsp;''on&amp;amp;nbsp;''Copy Record&amp;amp;nbsp;''window.&lt;br /&gt;
&lt;br /&gt;
Along with the RFx, users now have the ability to select any associated documents (parent-child or peer associations) where the Allow Copy with Associations is set to Yes at the Contract Type level. If this flag is set to ''No'', then only the RFx will be copied without its associations.&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Copy the Sourcing event. &lt;br /&gt;
*Select and copy associations such as line items, questions, questionnaires, suppliers, supplier contacts, internal and external attachments, and commitments.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Copying the RFx helps:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Exclude associations from being copied. &lt;br /&gt;
*Exclude the attributes of associations &lt;br /&gt;
*Exclude the automatic attachments from being copied to the new RFx &lt;br /&gt;
&lt;br /&gt;
Users can copy the RFx team based on the configured role. If RFx is copied by a user who is not primary owner of that RFx, then that user becomes the primary owner of the RFx.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Viewing the audit log by clicking&amp;amp;nbsp;''History&amp;amp;nbsp;''on RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. &lt;br /&gt;
&lt;br /&gt;
If the source role and target role is configured, the user roles will be same for the RFx being copied.&lt;br /&gt;
&lt;br /&gt;
If the source role is:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Primary owner and the same user is copying the current RFx, then target role is ignored (the copying user is part of the team as primary owner)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Same as target role, then team member role is set as source role&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the target role is:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;ul style=&amp;quot;margin-left: 40px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Primary owner, then a log gets added and the team member role is set as source role. For the rest of role mappings, the target role properties are set for the team member. If they are blank, then a log gets added and no action taken.&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Authorized users can configure the Agreement Contract Type and set ''Allow Copy with Associations'' field to ''Yes'' to enable copying the existing RFx.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp;You can copy an RFx from the:&lt;br /&gt;
&lt;br /&gt;
*''Sourcing index&amp;amp;nbsp;''page &lt;br /&gt;
*RFx&amp;amp;nbsp;''details&amp;amp;nbsp;''page &lt;br /&gt;
&lt;br /&gt;
To copy an RFx from the&amp;amp;nbsp;''Sourcing&amp;amp;nbsp;''index page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''dots&amp;amp;nbsp;next to the RFx on the Sourcing index page and then '''click&amp;amp;nbsp;'''''Copy Record''. The ''Copy Record'' window opens''.''&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' ''Yes'' next to ''Link To RFx'' that is being copied.&amp;amp;nbsp;This links the RFx copy that is being created with the source RFx. If you select No, it will not be linked with the source RFx. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.'''Click''' ''Copy Record'' to copy the RFx without the associations. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.'''Click''' ''Expand All'' on the ''Copy Record'' window to display all the associations of the RFx to be copied. You can click ''Collapse All'' to display only the parent level associations.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select''' the ''Associations'' checkbox to select all the associations of the RFx to copy. You can select specific associations that you want to copy.&amp;amp;nbsp;You can select the commitments from the Copy Record window to be copied from the source RFx to the destination RFx.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' ''Copy''. The name of the copied RFx is same as the source RFx. The ''Initiate RFx'' button is displayed on RFx Details page after the copy of the RFx is created.The primary owner of the copied RFx will be the&amp;amp;nbsp;user who initiates the copy operation.&lt;br /&gt;
&lt;br /&gt;
The RFx copy is created and RFx ''Details ''page opens with the status of the RFx as ''Draft.''&lt;br /&gt;
&lt;br /&gt;
To copy the RFx from RFx ''Details ''page:&lt;br /&gt;
&lt;br /&gt;
The RFx can also be copied from RFx ''Details ''page by following steps 2-5 in the To copy RFx from Sourcing Index page section.&lt;br /&gt;
&lt;br /&gt;
'''Viewing the audit log of Copy RFx'''&lt;br /&gt;
&lt;br /&gt;
You can view the audit log of the copy RFx event by clicking ''History ''on the RFx ''Details ''page.&lt;br /&gt;
&lt;br /&gt;
'''Viewing the Linked RFx&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
You can view the linked RFx from the RFx ''Details ''page.&lt;br /&gt;
&lt;br /&gt;
To view the linked RFx:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Related RFx&amp;amp;nbsp;''on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. The list&amp;amp;nbsp;of related RFx is displayed.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' ''View Record'' icon next to the RFx that allows viewing the original RFx using which its copy was created.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Linking the RFx'''&lt;br /&gt;
&lt;br /&gt;
Linking RFx with another RFx allows keeping track of the activities happening with both RFx thereby allowing to manage multiple RFx within one another. &amp;amp;nbsp; Linking the RFx helps in supporting global sourcing that involves globally distributed buyers’ team. This team may clone the sourcing event at the regional level to identify and shortlist suppliers and link the sourcing events with one another. ICM allows to link the source and destination RFx.&lt;br /&gt;
&lt;br /&gt;
To configure the two way linkage:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;&amp;amp;nbsp;'''Click '''the ''View record ''icon next to the RFx Contract Type on the ''Configuration ''page. The contract type ''Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;&amp;amp;nbsp;'''Navigate '''to the ''Associations ''section and '''select '''the attribute ''ICMAppSrcRelatedRFx.''&lt;br /&gt;
&lt;br /&gt;
*If ''Yes ''is selected next to ''Allow Two-way linkage'', it allows the source RFx to display the target RFx in the related RFx; likewise, the target RFx displays the source RFx. &lt;br /&gt;
*If ''No'' is selected next to Allow Two-way linkage, then the target RFx will display source RFx linkage in related RFx. not link the RFx copy with the source RFx. &amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
3. '''Click''' ''Update'' and navigate to ''Verify'' page and '''click''' ''Update'' to update the RFx contract type. This links the copied RFx with Source RFx.&lt;br /&gt;
&lt;br /&gt;
You can also add linked RFx from RFx ''Details'' page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To add linked RFx from RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''the plus icon next to ''Related RFx ''on RFx ''Details ''page. The ''Related RFx ''window opens displaying the list of related source RFx that you can link with the copied RFx.&lt;br /&gt;
&lt;br /&gt;
2.'''Click '''''Select ''to select and link the copied RFx with the source RFx from the available list.&lt;br /&gt;
&lt;br /&gt;
'''Exclude&amp;amp;nbsp;auto-attached associated documents during copy'''&lt;br /&gt;
&lt;br /&gt;
When a user copies the RFx with auto-attached associations, ICM excludes all auto attached associations from being copied to the new RFx. The auto-attached associations won’t be displayed on the ''Copy Record'' window. The resulting RFx has the selected manual associations and its own auto-attached associations as per the configured rules. This avoids the unnecessary upload of files into the ICM repository and duplication of association records on copied RFx.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Adding Line Items ==&lt;br /&gt;
&lt;br /&gt;
You can add line items at any stage of the RFx instance depending upon RFx configuration settings. Line items are products that the buyer is looking to procure through the RFx instance. When you create the RFx instance, the RFx ''Details'' page opens with the RFx status displayed as ''Draft''. You can use the left navigation pane to add one or more line items. You can also add line items using Microsoft Excel import by selecting the file from your local machine and uploading it to ICM Sourcing.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 1.png|720px|7.9 Sourcing Adding Line Items 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To add line items:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Create Association'' icon next to ''Line Items'' under the ''RFx Package'' tab. The ''Line Items'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 2.png|720px|7.9 Sourcing Adding Line Items 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Enter '''the values in the following fields:&lt;br /&gt;
&lt;br /&gt;
*''Name'': '''Enter''' the name of the items you want to procure. For example, ''Laptops''. &lt;br /&gt;
*''Part Number'': '''Enter''' the specific details of the item. For example, Model number. &lt;br /&gt;
*''Description'': '''Enter''' more information of the item. &lt;br /&gt;
*''Unit of Measure'': '''Select''' appropriate unit of measure depending upon the item. For example, ''Piece, Each, Pack'', etc. &lt;br /&gt;
*''Unit of Order'': '''Select''' the unit of order you want to procure. For example, in the multiples of 10s or 100s etc. &lt;br /&gt;
*''Desired Quantity'': '''Enter''' the quantity of the item you wish to procure. &lt;br /&gt;
*''Bid Currency'': '''Select''' the currency from the drop-down. &lt;br /&gt;
*''Additional Details'': You can upload a file that contains additional details about the item. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 3.png|720px|7.9 Sourcing Adding Line Items 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Create''. The Line Item is created. The Count is updated in the left navigation pane on the RFx&amp;amp;nbsp;''Details'' page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Line Items 4.png|720px|7.9 Sourcing Adding Line Items 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''Repeat steps 1-3 to add more line items.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Adding '''B'''ulk Line Items&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
The bulk associations capability has enabled ICM to handle large number of associations in the tune of thousands, by presenting itself as a lightweight association as well as tremendously improving performance. The Sourcing event can include many line items for an RFx ranging from 500 to 50,000 maximum. In Sourcing, line items are considered as associations.&amp;amp;nbsp;&amp;lt;br/&amp;gt; The bulk association configuration has now been simplified by providing a Enable Bulk Processing flag at contract type definition level which triggers a set of defaults that has been intentionally restricted. The end user experience for the bulk association has not changed from the way that the conventional association is handled from the UI, rather the underlying data structure has been further enhanced to make it go the distance.&amp;amp;nbsp;&amp;lt;br/&amp;gt; Performance has been the key while introducing and designing this new association, which has given way to the new type of instance, namely the Proxy Instance, which is retrieved in every GET call. The actual instances are referred by using this proxy instance, thereby reducing the load on the GET APIs. Specialized GET and SET APIs have also been introduced for bulk associations to improve its adaptability and ease-of-use.&amp;lt;br/&amp;gt; Bulk associations have very effectively consumed the Elastic Search Bulk API to sync a large set of data at one go, rather than the traditional way of one instance at a time, adding to the boost in performance.&amp;lt;br/&amp;gt; Bulk association is tweaked to be able to address the large data situation that Sourcing apps require, including:&lt;br /&gt;
&lt;br /&gt;
*Disabling the workflow &lt;br /&gt;
*Restricting the system associations to just team&amp;amp;nbsp; &lt;br /&gt;
*Restricting document assembly &lt;br /&gt;
*Simplifying the association team by maintaining team at proxy level to use access level as ALL or NONE, using a layer over the existing robust ICM authorization &lt;br /&gt;
*Restricting indexing of bulk associations attributes in the parent, which can be achieved through a technical configuration.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
You can enable the bulk processing flag, when you want to process large number of associations. For normal associations or non-BACT associations, bulk processing flag need not be enabled. Enabling this flag, accelerates the performance in handling large number of instances. &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To enable the Bulk Processing flag:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Configuration'' &amp;gt; ''Create Contract Type''. &amp;amp;nbsp;The ''Select a type of contract'' window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Select '''the Contract Type. For example, ''Associated Document.''&lt;br /&gt;
&lt;br /&gt;
3''.&amp;amp;nbsp;'''''Click'''''Next. ''The ''Create Contract Type Wizard ''page opens.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''E''''''nter '''a ''Contract Type Name''. For example,''Acme Bulk Pro''.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Toggle '''''Enable Bulk Processing'' flag to ''Yes''.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Next.''&lt;br /&gt;
&lt;br /&gt;
''7.&amp;amp;nbsp;'''''Enter&amp;amp;nbsp;'''details on the following tabs.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Create''&amp;amp;nbsp;on the&amp;amp;nbsp;''Verify&amp;amp;nbsp;''tab to create the contract type. It will now be in the&amp;amp;nbsp;''Draft&amp;amp;nbsp;''status.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' ''Send for Approval'' to send the contract type for approval. When approved, the contract type ''Acme Bulk Pro'' will be displayed in the grid in the ''Approved'' status.&lt;br /&gt;
&lt;br /&gt;
To upload bulk associations (line items)&lt;br /&gt;
&lt;br /&gt;
'''Prerequisites'''&lt;br /&gt;
&lt;br /&gt;
*RFx is created''.'' &lt;br /&gt;
*In the RFx, line item exists as an association with&amp;amp;nbsp;''Enable Bulk Processing&amp;amp;nbsp;''flag as&amp;amp;nbsp;''Yes.'' &lt;br /&gt;
*The event rule&amp;amp;nbsp;''Associated Document Created&amp;amp;nbsp;''is created. &lt;br /&gt;
&lt;br /&gt;
To upload bulk associations:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Import associated document data template&amp;amp;nbsp;''icon. The&amp;amp;nbsp;''Upload Document&amp;amp;nbsp;''page opens.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Select File''. Upload the file with the list of line items.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Upload File.&amp;amp;nbsp;''The record processing details will be updated.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Ok.&amp;amp;nbsp;''The RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page opens. The line item associations are updated.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The team for any one instance of line item is same for any other instances of line items.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Selecting Suppliers ==&lt;br /&gt;
&lt;br /&gt;
Suppliers are the businesses that participate in the RFx bidding process. The suppliers and their information such as ''Names, Addresses, Contact Numbers, Email Addresses,'' and&amp;amp;nbsp;''Supplier Contacts'' are added to the Masterdata. The name of the existing&amp;amp;nbsp;''Supplier Contact Name''&amp;amp;nbsp;has been modified to&amp;amp;nbsp;''Supplier Contact Full Name.&amp;amp;nbsp;''For example, John Doe.&amp;amp;nbsp;Buyers can remove the supplier contact from the Supplier Contact page. This updates the count of selected supplier contact.The selected supplier contact’s full name is displayed on the new selected supplier contacts interface.The suppliers and supplier contacts saved earlier are now displayed as pre-selected when adding more suppliers and supplier contacts.&lt;br /&gt;
&lt;br /&gt;
Now, the buyers can use any supplier and supplier contact masterdata contract type to add suppliers.&lt;br /&gt;
&lt;br /&gt;
The&amp;amp;nbsp;supplier contact full name column will be displayed by default on:&lt;br /&gt;
&lt;br /&gt;
*''Supplier Contact&amp;amp;nbsp;''selection page &lt;br /&gt;
*''Details&amp;amp;nbsp;''page of Supplier Contact &lt;br /&gt;
*Grid view of the supplier contact association&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
This makes it is easier for buyers and Administrators to identify and select the correct supplier if there are multiple suppliers with the same first name. This is applicable for bulk agreements too.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This is applicable for RFx, RFI and Rounds.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To add suppliers:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click '''the ''Create Association'' icon next to ''Suppliers''. The ''Supplier'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 1.png|720px|7.9 Sourcing Selecting Suppliers 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Search''' for the desired supplier(s) or '''select''' the suppliers from the displayed list under the ''Supplier'' tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 2.png|720px|7.9 Sourcing Selecting Suppliers 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Next''. The ''Supplier Contacts'' tab opens displaying the contact details of the suppliers.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SupplierContactFullName.png|720px|7.12-SupplierContactFullName.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''''the View Record ''icon next to the supplier’s name. The supplier’s contact details are displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-SupplierContactRecord.PNG|720px|7.12-SupplierContactRecord.PNG]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Select''' the desired ''Supplier Contact(s)''.&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''''Save''. The selected supplier(s) and supplier contact(s) are added to the RFx instance. The count is updated under the ''Supplier Information'' tab in the left navigation pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Selecting Suppliers 5.png|720px|7.9 Sourcing Selecting Suppliers 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Error Validations&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers have the option to select mandatory and pre-requisite contracts while creating the RFx. The attributes for mandatory and prerequisite contracts are interlinked. The prerequisite contracts are derived from the mandatory contracts. So, if the buyers select the following contracts – NDA, Warranty Agreement, Fixed Cost Agreement as mandatory, then they have the option to select one or more, or all as prerequisite contracts.&lt;br /&gt;
&lt;br /&gt;
Suppose the NDA is the prerequisite contract for accessing the RFx, then the validations are done such that ICM expects that the Instance of an NDA contract type for all the suppliers is associated with the RFx and contract should be in Approved state. Similarly, if Contract Types are made mandatory, then the instances of these should exist before RFx is sent for approval.&lt;br /&gt;
&lt;br /&gt;
Buyers will now receive a system message when:&lt;br /&gt;
&lt;br /&gt;
*Sending an RFx for approval in case prerequisite contracts are not in the Approved status for suppliers. &lt;br /&gt;
*Sending an RFx for approval in case mandatory contracts are either not created or exist in one of the states - ''Cancelled'', ''Expired'', or ''Terminated'' for suppliers.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Buyers will be able to view the validations for the prerequisite and mandatory contracts for the shortlisted suppliers only.&amp;lt;br/&amp;gt; For a shortlisted supplier, if all the prerequisite contracts are inactive or if any one of the contracts is active but not in Approved or later state, then the validations will be displayed.&amp;amp;nbsp;&amp;lt;br/&amp;gt; For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Draft state) and NDA 2 (in Waiting for Approval) state, then validations will be displayed.&amp;amp;nbsp;&amp;lt;br/&amp;gt; The validations will not be displayed for shortlisted suppliers when at least one active prerequisite contract exists, and all such contracts are in Approved or later state.&amp;amp;nbsp;&amp;lt;br/&amp;gt; For example, if there is one shortlisted supplier with two prerequisite contracts NDA 1 (in Approved state) and NDA 2 (in Expired state), no validations will be displayed since one of the two prerequisite contracts (NDA 1) is in Approved or later state.&amp;lt;br/&amp;gt; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To view the error validations:&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Send for Approval&amp;amp;nbsp;''on RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. The&amp;amp;nbsp;''Contract Status Validation&amp;amp;nbsp;''window opens.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-1.png|720px|7.12-Validations-1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the ''Mandatory Contracts&amp;amp;nbsp;''tab next to the&amp;amp;nbsp;''Prerequisite Contracts&amp;amp;nbsp;''tab.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-2.png|720px|7.12-Validations-2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
A message is displayed as above indicating that the contract types are either not created or exist in one of the statuses as Expired, Terminated, or Cancelled. In this example, the contract types Fixed Cost and NDA are not created.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the plus icon to the mandatory contract that was configured when creating the RFx and create the mandatory contracts using the process to create the bulk agreement.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Send for Approval.&amp;amp;nbsp;''The&amp;amp;nbsp;''Contract Status Validation&amp;amp;nbsp;''window opens displaying only the Prerequisite contracts.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Validations-3.png|720px|7.12-Validations-3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Creating Bulk Agreements ===&lt;br /&gt;
&lt;br /&gt;
The Sourcing App offers you a convenient way of creating bulk agreements with the suppliers, without having to move out of RFx instance that you are working on. The agreements must be already configured in ICM. These agreements may be made mandatory for the supplier to sign before the supplier can participate in the RFx. The RFx displays all the agreements created from the RFx and they have all the agreement information. This allows the buyer to conveniently navigate between the RFx and the agreement associated with the RFx.&lt;br /&gt;
&lt;br /&gt;
To create an agreement:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Create Association'' icon next to the agreements in the left navigation pane on the RFx ''Details'' page. For example, NDA, Warranty Agreement.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 1.png|720px|7.9 Sourcing Creating Bulk Agreements 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 2.png|720px|7.9 Sourcing Creating Bulk Agreements 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. The ''Attributes (Step 2 of 4)'' page opens in the new browser tab.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 3.png|720px|7.9 Sourcing Creating Bulk Agreements 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Enter''' values for all the attributes, some of which may be mandatory.&lt;br /&gt;
&lt;br /&gt;
4. '''Click '''the ''Select Multiple Suppliers ''icon next to ''Suppliers and Agreement Details. ''The ''Supplier ''page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 4.png|720px|7.9 Sourcing Creating Bulk Agreements 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5. Repeat steps 2 to 6 from the ''Selecting Suppliers'' section to add a supplier.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Click '''''Next''. The ''Select Template'' ''(Step 3 of 4) ''page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 5.png|720px|7.9 Sourcing Creating Bulk Agreements 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Select''' a Template.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 6.png|720px|7.9 Sourcing Creating Bulk Agreements 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8.&amp;amp;nbsp;'''Click '''''Next. ''The ''Verify'' page opens. Verify all the information you have entered.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 7.png|720px|7.9 Sourcing Creating Bulk Agreements 7.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9. '''Click''' the ''Bulk Create Agreement ''button. The agreement is created.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 8.png|720px|7.9 Sourcing Creating Bulk Agreements 8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
10.&amp;amp;nbsp;'''Click''' the ''View Record'' icon next to the NDA instance on the ''Sourcing'' page. The NDA’s ''Details'' page opens with the NDA in the ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The number of instances of the selected NDA Agreement created matches with the number of suppliers selected while creating the RFx.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 9.png|720px|7.9 Sourcing Creating Bulk Agreements 9.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
After the Agreement is created for a supplier, you can proceed with the agreement workflow as configured. For example, you can send the agreement for approval.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 10.png|720px|7.9 Sourcing Creating Bulk Agreements 10.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
11. '''Click''' the ''Send For External Signature'' button on the ''Details'' page. The agreement is sent to the supplier(s) for signatures. The status of the agreement changes to ''Executed'' when all the suppliers sign the NDA.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Bulk Agreements 11.png|720px|7.9 Sourcing Creating Bulk Agreements 11.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Link Existing Contracts&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Link existing supplier contracts (prerequisite, mandatory, associated contracts) allowing buyers to leverage existing contracts with suppliers.&amp;amp;nbsp; &lt;br /&gt;
*View the contracts of the supplier when creating the bulk agreement that allows assigning any supplier contact as a signatory for the agreement. &lt;br /&gt;
*View the signatory of the prerequisite contracts that allows the suppliers to connect with the signatory if there are any issues with the contracts.&amp;amp;nbsp; &lt;br /&gt;
*Send the agreements for approval in bulk that helps avoid sending the agreements for approval individually.&amp;amp;nbsp; &lt;br /&gt;
*Select the new signature type&amp;amp;nbsp;''Click to Sign&amp;amp;nbsp;''allowing suppliers to participate in the sourcing event by previewing, accepting, or declining the terms and conditions set by the buyer.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
To link existing contracts:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''the&amp;amp;nbsp;''Create Association&amp;amp;nbsp;''next to the agreements in the left navigation pane on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page. For example, NDA, Warranty Agreement. The&amp;amp;nbsp;''Please Confirm&amp;amp;nbsp;''window opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Existing Contracts. ''The&amp;amp;nbsp;''Select existing contracts to link to RFx page&amp;amp;nbsp;''opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the contract that you want to link with the RFx and&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Link Contracts.&amp;amp;nbsp;''&lt;br /&gt;
&lt;br /&gt;
The selected contract is linked with the RFx.&amp;amp;nbsp;&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Adding Team Members ===&lt;br /&gt;
&lt;br /&gt;
A team of Approvers, Reviewers, and Observers can be added to the RFx instance for completing the workflow.&lt;br /&gt;
&lt;br /&gt;
To add team members:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Team'' tab on the RFx ''Details'' page. The ''Add Team'' page opens in the right pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Team Members 1.png|720px|7.9 Sourcing Adding Team Members 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''Add Team'' icon. The ''Select User'' window opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter '''the search term in the ''Search User'' field to search for a desired user.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Select '''a User from the displayed user tiles.&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Select '''a ''Role''. For example, ''Approver'', ''Business Owner'', ''Observer'', etc.&lt;br /&gt;
&lt;br /&gt;
6.&amp;amp;nbsp;'''Select''' or '''enter''' the ''Step Number'' if you select ''Approver'' in the ''Select Role'' field.&lt;br /&gt;
&lt;br /&gt;
7.&amp;amp;nbsp;'''Enter '''a comment in the ''Add Note'' field (optional). You can see this comment under the ''Notes'' tab.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Select '''the ''Send Notification ''checkbox if you want to the user to receive a notification of the task.&lt;br /&gt;
&lt;br /&gt;
9.&amp;amp;nbsp;'''Click '''''Add''. The ''User has been added successfully'' message is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Adding Team Members 2.png|720px|7.9 Sourcing Adding Team Members 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Sending the RFx Instance for Approval ===&lt;br /&gt;
&lt;br /&gt;
The RFx instance must be in ''Approved ''state before a round is created automatically and the RFx workflow can be completed.&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Send For Approval ''button on the RFx ''Details'' page. The RFX instance is sent for approval to the approver(s) you have selected in the ''Team''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Internal Approval for RFX Instance 1.png|720px|7.9 Sourcing Internal Approval for RFX Instance 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The status changes to ''Waiting For Approval. ''A task is created for each approver.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Internal Approval for RFX Instance 2.png|720px|7.9 Sourcing Internal Approval for RFX Instance 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
When all the approvers approve the RFx instance, the status changes to ''Approved''. After the RFx is approved, the first round is created automatically.&lt;br /&gt;
&lt;br /&gt;
== Working with Rounds ==&lt;br /&gt;
&lt;br /&gt;
One cycle of seeking proposals/bids from suppliers and evaluating them is referred to as a round. A complete Sourcing event may comprise of multiple rounds. The first round is created automatically (if the start and end dates are entered) as soon as the RFx instance is approved. You can see the round on the RFX ''Details'' page. You must open the round instance and fill in additional details. There can be multiple rounds for one RFx instance.&lt;br /&gt;
&lt;br /&gt;
Here is the round workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Working With Rounds 1.png|720px|7.9 Sourcing Working With Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Starting the Scheduled Rounds ===&lt;br /&gt;
&lt;br /&gt;
You can schedule a round by entering the ''Round Start Date'' and ''End Date'' when creating the RFx instance. The buyer must click the ''Start Round'' button on the ''Round'' ''Details'' page to start the round.&lt;br /&gt;
&lt;br /&gt;
To start the round:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Round'' on the RFx ''Details'' page. The auto created round instance is displayed.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Only the first round is created automatically. The buyers must create the other rounds manually as required.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Scheduling Rounds 1.png|720px|7.9 Sourcing Scheduling Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''the ''View Record'' icon. The Round&amp;amp;nbsp;''Details'' page opens with the round in ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Scheduling Rounds 2.png|720px|7.9 Sourcing Scheduling Rounds 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click '''the ''Start Round'' button to start the Round. The status of the round changes to ''Approved ''when the round is approved and the status of the RFx changes to&amp;amp;nbsp;''Bidding&amp;amp;nbsp;''''Open'''''&amp;lt;b&amp;gt;.&amp;lt;/b&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note: '''When the round is approved the status changes to ''Scheduled''. When the current date is equal to start date of the round, the status changes to ''Open''.&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating Rounds ===&lt;br /&gt;
&lt;br /&gt;
The buyer can also create a round manually if they need to conduct multiple rounds with the supplier. The buyer can create the round manually only if the RFx instance is in ''Approved ''state.&lt;br /&gt;
&lt;br /&gt;
To create a round (manually):&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Create Association'' icon under the ''Round'' tab on the RFx ''Details'' page. The ''Create RFx -Round'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 1.png|720px|7.9 Sourcing Creating Rounds 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''Organization Unit'' icon to select the ''Organization Unit''.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter''' an appropriate name for the round.&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Enter''' relevant details in the ''AppSrc Description'' field.&lt;br /&gt;
&lt;br /&gt;
5. '''Select''' a ''Round Start Date''. This field is already populated with the current date. You can select a different date and time if required.&lt;br /&gt;
&lt;br /&gt;
6. '''Select''' a ''Round End Date ''and time.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The date and time is displayed based on the user’s locale settings. When the user with different locale views the RFx, the date and time are converted to their locale.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 2.png|720px|7.9 Sourcing Creating Rounds 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7. '''Click '''''Next''. The ''Verify'' page opens. Verify all the information.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 3.png|720px|7.9 Sourcing Creating Rounds 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
8. '''Click '''the ''Create Round'' button. The Round’s ''Details'' page opens. The round is now created in ''Draft ''state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Rounds 4.png|720px|7.9 Sourcing Creating Rounds 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9. '''Click '''the ''Start Round'' button to begin the Round. The status of the round changes to ''Approved and Scheduled''. When the round is approved the status changes to ''Approved and Scheduled''. When the current date is equal to start date of the round the status changes to ''Published''.&lt;br /&gt;
&lt;br /&gt;
=== Editing Round start and end dates&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&lt;br /&gt;
&lt;br /&gt;
*Edit the&amp;amp;nbsp;round start and end date when the round is in one of the below states: &lt;br /&gt;
**Draft &lt;br /&gt;
**Waiting for Approval &lt;br /&gt;
**On Hold &lt;br /&gt;
**Open &lt;br /&gt;
**Approved&amp;amp;nbsp;   &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;You can make changes only to the round end date when the round is in ''Open'' state. The changes made to the round start and end date are captured in the ''History'' on round ''Details'' page.It is not mandatory to run the approval workflow for the round after changing the ''Planned Start Date'' and ''Planned End Date''.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
To edit the round start and end date:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' ''Round'' on RFx ''Details'' page. The list of rounds is displayed.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate1.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' the ''View Record'' icon next to the round for which you want to edit the start and end date. The round ''Details'' page opens and displays the existing start and end date of the rounds.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;3.&amp;amp;nbsp;'''Click''' ''Edit''. The ''Edit'' round page opens.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate2.png|720px|7.12-EditRound-Start-EndDate2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4.&amp;amp;nbsp;Make the necessary changes to the start and end date of the round depending on the state of the round. You can edit just the time of start and end date of the round and not required to change the date always.&amp;amp;nbsp;For example, the&amp;amp;nbsp;''Planned Start Date&amp;amp;nbsp;''was July 8, 2020, 12:00 AM and the&amp;amp;nbsp;''Planned End Date&amp;amp;nbsp;''was August 8, 2020 12:00 AM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Open:&amp;amp;nbsp;You can make the changes only to the ''Planned End Date'' of the round. For example, you can change the ''Planned End Date'' to September 8, 2020 in place of the earlier date August 8, 2020 &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Buyers can edit the round end date when the status of the RFx changes to In Modification when the previous status of the round is Open.&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate3.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
*''Approved/''On Hold:&amp;amp;nbsp;You can make the changes to the ''Planned Start Date'' and ''Planned End Date'' values of the round. For example, you can change the ''Planned Start Date'' to July 15, 2020 in place of the earlier date July 8, 2020 earlier and ''Planned End Date'' to September 15, 2020 as against August 8, 2020 earlier. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate4.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Buyers can enter the planned start and end date of the RFx when creating the round manually. The values for Actual Start Date and Actual End Date are populated based on the actual date when the round is opened or closed.&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Update&amp;amp;nbsp;''on round&amp;amp;nbsp;''Verify&amp;amp;nbsp;''page.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate5.png|720px|7.12-EditRound-Start-EndDate5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
The round ''Details'' page opens and displays the edited round start and end date.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-EditRound-Start-EndDate6.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;The changes made to the round start and end date are captured in the ''History'' on round ''Details'' page.It is not mandatory to run the approval workflow for the round after changing the ''Planned Start Date'' and ''Planned End Date''.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
== Working with Bids ==&lt;br /&gt;
&lt;br /&gt;
A bid is a collection of quotes for each Line Item.&amp;amp;nbsp;The system generates bids when a round is in ''Published'' state. The supplier can view the bids that were submitted in the previous rounds if the buyer selects ''Yes ''in the ''AppSrc Auto Copy Bids from the Previous Round ''option when creating the RFx.&lt;br /&gt;
&lt;br /&gt;
Depending upon how the RFx instance is configured in the organization, suppliers must sign all the prerequisite agreements before submitting the bid responses. The suppliers won’t be able to view the RFx instance until the prerequisite agreement is in ''Executed'' state.&lt;br /&gt;
&lt;br /&gt;
Here is the bid workflow at a glance:&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Working With Bids 1.png|720px|7.9 Sourcing Working With Bids 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Submitting&amp;amp;nbsp;Bids ===&lt;br /&gt;
&lt;br /&gt;
A supplier can submit bid responses when the round is published.&lt;br /&gt;
&lt;br /&gt;
To submit bid responses:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Sourcing ''tile on the ''Dashboard'' after logging on to ICM. The ''Sourcing'' page opens. This page displays a list of all the RFx instances, rounds, and bids that the supplier is a part of.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 1.png|720px|7.9 Sourcing Submitting Bids 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click''' the ''View Record'' icon next to the bid that you want to respond to. The Bid’s ''Details'' page opens with the bid is in ''Draft'' state.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 2.png|720px|7.9 Sourcing Submitting Bids 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Bid Response'' under ''Quotation Details ''tab. The bid response is displayed in the grid along with its details such as ''Item Name'', ''Quotation ID'' etc. As the buyer had added two line items, the count is updated to 2 next to ''Bid Response''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 3.png|720px|7.9 Sourcing Submitting Bids 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click''' the ''Edit'' icon. The ''Edit Bid Response'' window opens. It displays the information of the line item given by the buyer.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 4.png|720px|7.9 Sourcing Submitting Bids 4.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 5.png|720px|7.9 Sourcing Submitting Bids 5.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&lt;br /&gt;
5. '''Enter''' values for the following fields:&lt;br /&gt;
&lt;br /&gt;
*''AppSrc Base Price'': The price for one unit of the product mentioned in the line item. &lt;br /&gt;
*''AppSrc Total Price'': Calculated automatically by ICM depending upon the buyers requirement of the number of pieces and the base price you entered. &lt;br /&gt;
*''AppSrc Quote Currency'': '''Select''' the appropriate currency from the drop-down. &lt;br /&gt;
&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 6.png|720px|7.9 Sourcing Submitting Bids 6.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6.&amp;amp;nbsp;'''Click''' the ''Update ''button. The bid response is updated. The ''Bid Response'' window closes.&lt;br /&gt;
&lt;br /&gt;
7. '''Click '''''Submit ''on the ''Bid'' ''Details'' page. The bid response is now submitted to the buyer. The status of the bid changes to ''Submitted.''&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp; You should click on submit only after you have entered values for all items.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 7.png|720px|7.9 Sourcing Submitting Bids 7.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can submit the bid responses for one or all line items. Follow steps 1-7 to do so.&amp;lt;/div&amp;gt; &lt;br /&gt;
After submitting bids, suppliers cannot edit bids. To edit the bids, the suppliers must '''click '''''Withdraw''. This changes the status of the bid to ''Withdrawn. ''Suppliers can revert withdrawal by clicking ''Revert Withdrawal. ''They can also edit their bids and submit again.&lt;br /&gt;
&lt;br /&gt;
As soon as one supplier submits a bid, the status of the round changes to ''In Bidding''. When all the bid responses are submitted, the buyer can:&lt;br /&gt;
&lt;br /&gt;
*Manually close the round by clicking the ''Close Round'' button on the Round’s ''Details'' page if the ''AppSrc'' ''Allow Foreclosure of Rounds ''is toggled to ''Yes ''when creating the RFx by the buyer. &lt;br /&gt;
&lt;br /&gt;
Or&lt;br /&gt;
&lt;br /&gt;
*The round closes as per the scheduled ''Round End Date ''and Time. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The buyer can choose to close the round even when only one supplier has submitted the bid or even if no one has submitted a bid. The status of the RFx changes to ''Round'' ''Closed''.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Submitting Bids 8.png|720px|7.9 Sourcing Submitting Bids 8.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Buyers can now view the status of bids for each supplier regardless of whether the RFx is an open or sealed envelope depending on the status of the bid. These statuses include:&lt;br /&gt;
&lt;br /&gt;
*''Submitted and Closed'': Buyers and the user assigned as a surrogate buyer can view the bids in ''Submitted ''status, and the rounds are closed. &lt;br /&gt;
*''Declined'': The suppliers declining the bid cannot participate in the upcoming rounds. The status of the bid is displayed according to the type of RFx when the bid is in Declined state. &amp;amp;nbsp;&amp;amp;nbsp; &lt;br /&gt;
**''Open RFx'': Buyers and the user assigned as a surrogate buyer can view the round in Open and Closed state. &lt;br /&gt;
**''Sealed Envelope'': Buyers can view the bid when the state of RFx changes to ''Closed'' state. The suppliers who declined the bid cannot participate in the ongoing or upcoming rounds nor can they revert decline to participate in the round again.   &lt;br /&gt;
&lt;br /&gt;
Buyers cannot view the status of the bids depending on the following status of the bid.&lt;br /&gt;
&lt;br /&gt;
*''Not Submitted and Closed'': Buyers and the user assigned as a surrogate buyer cannot view the bid response when the bid is not submitted, and the round is closed. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The bid responses are displayed or hidden based on whether the bid was submitted or not submitted by the suppliers.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Bid Analysis ===&lt;br /&gt;
&lt;br /&gt;
It is the process of analyzing supplier responses with an intent to compare one against the others along the evaluation criteria. When all the desired ''Bid Responses'' are received, you can view and analyze all the responses to be able to take informed decision.&lt;br /&gt;
&lt;br /&gt;
At least one round should be completed for conducting bid analysis, otherwise the user gets an error message indicating that the round must be started to download bid analysis. For an RFx with ''Sealed Envelope'', at least one round must be in ''Closed'' state to download the excel sheet for bid analysis.&lt;br /&gt;
&lt;br /&gt;
The bid analysis Excel will contain all the bids, for all the suppliers, for all the rounds. The bid analysis will also contain currency information of bid currency and RFx primary currency, along with bid analysis attributes converted to RFx primary currencies. An attribute for bid analysis is defined in the masterdata. Users can add the bid analysis attribute for each RFx item and specify its value while creating an RFx or associated document. This helps the buyer to get all the information in the Excel sheet to be able to easily analyze a bid for a supplier.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&lt;br /&gt;
&lt;br /&gt;
*Download bid analysis excel on bid level and round level. When bid analysis is performed on bid, the downloaded bid analysis Excel it will include the responses for a specific respective supplier whose bid was chosen. Whereas, when bid analysis is performed on round level, downloaded bid analysis Excel will include the bid responses data for all the suppliers present in the round. &lt;br /&gt;
*&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Enter the values for bid analysis attributes and upload the bid analysis Excel sheet. The value of bid analysis attributes will be updated in the bid response.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Downloading and Uploading Bid Analysis for round'''&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Bid Analysis'' button, on the ''Round'' ''Details'' page. The ''Bid Analysis'' page opens.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2. '''Click''' ''Download File. ''The Excel file of Bid Analysis is downloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Open '''the downloaded Excel. View the Bid Analysis attributes.&lt;br /&gt;
&lt;br /&gt;
Once downloaded, you can edit the Bid analysis attributes such as ''Bonus'', ''Net Landed Cost'', ''Difference''.&lt;br /&gt;
&lt;br /&gt;
4.'''Enter '''''Bid Analysis attribute'' values. For example: '''Enter''' value of ''Bonus as 2.44 instead of 1.05. &amp;amp;nbsp;''&lt;br /&gt;
&lt;br /&gt;
5.'''Click''' ''Save'' to '''save''' the file'''.'''&lt;br /&gt;
&lt;br /&gt;
6. '''Click '''''Select File To Upload'' on the Bid Analysis window. The updates will be made, and the''Bid Analysis has been Saved successfully'' message will be displayed in the ''Upload Summary'' section.&lt;br /&gt;
&lt;br /&gt;
7.'''Click''' ok.&lt;br /&gt;
&lt;br /&gt;
'''Downloading and uploading bid analysis for bid:&amp;amp;nbsp;'''&lt;br /&gt;
&lt;br /&gt;
1.'''Click the '''''Bid Analysis'' button, on ''Bid'' ''Details'' page.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.'''Click''' ''Download File. ''The Excel file of Bid Analysis is downloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Open '''the downloaded Excel file. View the Bid Analysis attributes.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;You can add the bid analysis attribute for each RFx item and specify its value while creating an agreement or associated document.&lt;br /&gt;
&lt;br /&gt;
If you add any invalid value in Bid Analysis attribute, error validation message will be displayed in last column.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For example: '''Enter''' ''hdsjbvshd'' in ''Bonus, and enter ''any random value in ''Net Landed Cost'' ''chdsjbcs'', then Error message is displayed, indicating that Bonus and Net landed Cost are invalid.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
You can not edit other attributes such as ''Freight, Insurance, landed Cost''.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''To analyze bid response:'''&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click''' the ''Download Bid Analysis'' button on the RFx ''Details'' page. An Excel sheet containing the bid responses is downloaded.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Bid Analysis 1.png|720px|7.9 Sourcing Bid Analysis 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Open''' the Excel sheet. You can view the all the data collected from the bid responses such as ''Supplier ID, Item Name, Item Description'', etc.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Bid Analysis 2.png|720px|7.9 Sourcing Bid Analysis 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Downloading Associations and Attachments&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing app offers an ability to download either all or selected associations (line items, attachments, supplier documents) and attachments (files uploaded to the RFx instance) for review and analysis purposes. This is applicable for all types of RFx instances and all documents (buyer’s and suppliers). The application retains the file names of the attachments as they were while uploading them so that they could be recognized easily.&lt;br /&gt;
&lt;br /&gt;
The files names will be the same when downloading or uploading them to ICM. The files will be downloaded as per the defined folder structure and folder naming conventions &amp;amp;nbsp; which helps users to easily identify files under individual folders of the RFx and avoid any discrepancies. The folder names for associations are now same as the contract type display names such as line items, internal attachments, round, bid response and so on.&lt;br /&gt;
&lt;br /&gt;
Downloading the RFx package displays the folders for RFx, round, bid, RFI Response as they are displayed in ICM. The rounds and bids folders are merged in a single folder and the template files are added to the relevant round or bid folder. This is applicable for both RFx and RFI.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': Buyers can select and download attachments of buyers and suppliers as required. Suppliers can only download the attachments to which they have access or the attachments they upload.&amp;lt;/div&amp;gt; &lt;br /&gt;
The attachments can be viewed under ''RFx Package'' tab on the RFx ''Details'' page.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Downloading Associations and Attachments 1.png|720px|7.9 Sourcing Downloading Associations and Attachments 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
To download associations and attachments:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Download Package'' button on the RFx ''Details'' page. The ''Download'' window opens displaying all the Associations and attachments.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Downloading Associations and Attachments 2.png|720px|7.9 Sourcing Downloading Associations and Attachments 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' the items you wish to download.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage1.png|720px|7.12-DownloadPackage1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click''' ''Download''. The selected files are downloaded in a zip file.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage2.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage3.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-DownloadPackage4.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The selected attachments are downloaded as per the folder structure they are part of in the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
== Awarding Workflow ==&lt;br /&gt;
&lt;br /&gt;
You can initiate the Awarding workflow after receiving all the required bid responses and after all the rounds are in ''Round(s) Closed ''state. Buyers can award multiple suppliers using Excel upload.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': After the awarding is initiated, the buyer cannot create new rounds. If a new round is required to be created after awarding is initiated, you must delete the awarding object and then create a new Round.&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Creating Awarding Instances ===&lt;br /&gt;
&lt;br /&gt;
To create award instances:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' the ''Initiate Award'' button on the RFx ''Details'' page.&amp;amp;nbsp; The ''Attributes (Step 2 of 4)'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 1.png|720px|7.9 Sourcing Creating Awarding Instances 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select''' the ''Organization Unit''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': The ''Agreement Code'' is system generated.&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Select''' the Business Status (Default value - ''Draft'').&lt;br /&gt;
&lt;br /&gt;
4. '''Enter '''the ''Name'' of the Awarding instance. &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
5.&amp;amp;nbsp;'''Upload '''an ''AppSrc Supporting Document,'' if any.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 2.png|720px|7.9 Sourcing Creating Awarding Instances 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Next''. The ''Select Template (Step 3 of 4)'' page opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 3.png|720px|7.9 Sourcing Creating Awarding Instances 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
7.&amp;amp;nbsp;'''Select '''the template.&lt;br /&gt;
&lt;br /&gt;
8.&amp;amp;nbsp;'''Click '''''Next''. The ''Verify'' page opens. Verify all the information.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 4.png|720px|7.9 Sourcing Creating Awarding Instances 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
9.&amp;amp;nbsp;'''Click''' the ''Create Award Agreement'' button. The RFx ''Details'' page opens with the status ''Awarding Initiated''. The RFx Awarding instance is created with the status ''Draft''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Creating Awarding Instances 5.png|720px|7.9 Sourcing Creating Awarding Instances 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Awarding Decision ===&lt;br /&gt;
&lt;br /&gt;
After creating the Awarding instance, you must create an Awarding ''Decision'' as an Association. The awarding decision contains all the details of all items and the Supplier(s) who are being awarded the RFx along with the other details such as award quantity and price.&lt;br /&gt;
&lt;br /&gt;
To create awarding decision:&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''RFx Awarding'' on the RFx ''Details'' page. The awarding instance is displayed in the right pane.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 1.png|720px|7.9 Sourcing Awarding Decision 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2. '''Click '''the ''View Record'' icon. The Awarding ''Details'' page opens with the status ''Draft''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 2.png|720px|7.9 Sourcing Awarding Decision 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Click '''the ''Create Association'' icon next to ''AppSrc Awarding Decision''. The ''Awarding Decision'' window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 3.png|720px|7.9 Sourcing Awarding Decision 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
4. '''Click '''the icon next to ''Download File. ''The ''Awarding Decision ''excel sheet is downloaded on your computer. This excel sheet displays the information such as the price submitted by the supplier, the quantity of line items, currency, etc. This excel sheet contains all the bids for all suppliers for all rounds.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 4.png|720px|7.9 Sourcing Awarding Decision 4.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
5.&amp;amp;nbsp;'''Enter '''values for the required fields entered on Excel.&lt;br /&gt;
&lt;br /&gt;
*''Awarded Quantity: '''''Enter''' the quantity you are procuring through this awarding decision. &lt;br /&gt;
*''Awarded Percentage: '''''Enter''' a value for ''Awarding Percentage''. Awarding can be given to one or more suppliers at a time. For example, the selected supplier may get 60% of the order. If it’s not being shared, it is 100 percent. This process is known as ''Split Awarding''. &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can add either the awarded quantity or the awarded percentage and the other is automatically derived. For example, if you enter the awarded percentage, the awarded quantity will be calculated automatically.&amp;lt;/div&amp;gt; &lt;br /&gt;
Some of the important points to note when splitting the award between multiple suppliers are:&lt;br /&gt;
&lt;br /&gt;
*The awarding percentage will be calculated automatically up to 2 decimal places when you add the awarding quantity. &lt;br /&gt;
*The awarding quantity will be calculated automatically based on the percentage entered to the nearest integer. &lt;br /&gt;
*If you want to delete a particular Line Item, delete the records from ''Awarded Quantity ''and ''Awarded Percentage ''columns. &lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Awarding Decision 5.png|720px|7.9 Sourcing Awarding Decision 5.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
6. '''Click '''''Select File to Upload ''and then '''click '''''Upload File ''to upload the file. The awarding decisions are created automatically after uploading the File.&lt;br /&gt;
&lt;br /&gt;
=== Sending the Awarding Instance for Approval ===&lt;br /&gt;
&lt;br /&gt;
After creating the awarding instance and adding the awarding decision, you must send the awarding instance for approval.&lt;br /&gt;
&lt;br /&gt;
To send the awarding instance for approval:&lt;br /&gt;
&lt;br /&gt;
1. '''Click''' ''Publish'' on the Awarding ''Details'' page. The ''Published Successfully'' message is displayed.&lt;br /&gt;
&lt;br /&gt;
2.&amp;amp;nbsp;'''Click''' ''Send For Approval''. The status of the Awarding instance changes to ''Approved'' once the Approver(s) approve it.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 1.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 2.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 2.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
After the awarding instance is approved, the status of the RFx instance changes to ''Awarded''.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Sending Awarding Instance for Approval 3.png|720px|7.9 Sourcing Sending Awarding Instance for Approval 3.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
=== Updating the Awarding Contracts ===&lt;br /&gt;
&lt;br /&gt;
Contracts are created for the selected suppliers who are awarded with RFx. You can update the pricing information of the awarded line items in the awarded contracts.&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': You can update the RFx only when it is in ''Awarded ''state and awarding contracts such as NDA is present in the RFx.&amp;lt;/div&amp;gt; &lt;br /&gt;
To update awarded contracts:&lt;br /&gt;
&lt;br /&gt;
1. '''Click '''''Update Awarding Contracts ''on the ''RFx Details ''page. The ''Please Confirm ''window opens.&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Updating Awarded Contracts 1.png|720px|7.9 Sourcing Updating Awarded Contracts 1.png]]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.9 Sourcing Updating Awarded Contracts 2.png|720px|7.9 Sourcing Updating Awarded Contracts 2.png]]&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''': This validates whether the awarding decision contains any associations.&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Yes. ''The ''Information ''window opens displaying a message ''Update to agreements for awarding decision initiated. Please check the agreements after some time.''&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;''[[File:7.9 Sourcing Updating Awarded Contracts 3.png|720px|7.9 Sourcing Updating Awarded Contracts 3.png]]''&amp;lt;/div&amp;gt; &lt;br /&gt;
3. '''Click '''''Ok. ''The process of updating awarding contracts starts in the background and the status of the RFx changes to ''Contract Initiated. ''After the process is completed successfully, the status of the RFx changes to ''Contract Created.''&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click '''the agreement associated with the RFx in the left pane on ''RFx Details ''page. The ''Agreement Details ''page opens.&lt;br /&gt;
&lt;br /&gt;
5. '''Click '''''Awarding Decision ''in the left pane on ''Agreement Details ''page. The awarding decision will be displayed with the updated pricing information.&lt;br /&gt;
&lt;br /&gt;
== Currency Support ==&lt;br /&gt;
&lt;br /&gt;
ICM administrators can now configure the corporate currency in the currency master.&lt;br /&gt;
&lt;br /&gt;
*Add currencies to the currency masterdata that contains the list of currencies that can be used in the RFx event.&amp;amp;nbsp; &lt;br /&gt;
*Manage currencies from the currency master by adding new currency &lt;br /&gt;
*Set a single currency as a corporate currency for the organization to be used in Sourcing events.&amp;amp;nbsp; &lt;br /&gt;
*Restrict the option to delete the currency and only allow to make it inactive. &lt;br /&gt;
&lt;br /&gt;
=== Configuring the Corporate Currency in Currency Master ===&lt;br /&gt;
&lt;br /&gt;
You can create a new currency record in ICM using the extended currency master.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Configuration&amp;amp;nbsp;''and then&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Masterdata&amp;amp;nbsp;''on the&amp;amp;nbsp;''Home&amp;amp;nbsp;''page. The&amp;amp;nbsp;''Create Masterdata&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Configure Corporate Currency 1.png|720px|7.12-Configure Corporate Currency 1.png]]&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the&amp;amp;nbsp;''Extended Currency Master&amp;amp;nbsp;''from the drop-down list and&amp;amp;nbsp;'''click&amp;amp;nbsp;'''''Next.&amp;amp;nbsp;''The&amp;amp;nbsp;''Attributes&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;[[File:7.12-Configure Corporate Currency 2.png|RTENOTITLE]]&amp;lt;/div&amp;gt; &lt;br /&gt;
3.&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the following information on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Masterdata code: This is generated automatically after the masterdata is created.&amp;amp;nbsp; &lt;br /&gt;
*Currency Name:&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the name of the currency. For example, Singapore Dollar.&amp;amp;nbsp; &lt;br /&gt;
*Currency Code:&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the code of the currency. For example, SGD.&amp;amp;nbsp; &lt;br /&gt;
*Symbol:&amp;amp;nbsp;'''Enter''' the symbol for the currency you are creating. This helps in identifying the currency used in the financial transactions happening between the buyers and suppliers. For example, $.&amp;amp;nbsp; &lt;br /&gt;
*Country Name:&amp;amp;nbsp;Enter the name of the country to which this currency would belong to. For example, Singapore. &lt;br /&gt;
*Valid Until:&amp;amp;nbsp;'''Select''' the date until which this currency will be considered valid. For example, the currency can be valid for one year from the date it was created which could be July 8 2022. &lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save.&amp;amp;nbsp;''The currency will be created and saved in ICM.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To be configure corporate currency in currency master:&lt;br /&gt;
&lt;br /&gt;
1.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''User Administration'' and then '''click''' ''Application Settings''. The ''Application Settings'' page opens.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;image-green-border&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
2.&amp;amp;nbsp;'''Click '''''Next&amp;amp;nbsp;''on ''Entity Color Configuration'' and ''User Theme'' pages. The ''Other Configuration'' page opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Select''' the Corporate Currency from the drop-down list. For example, select SGD (Singapore Dollar).&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Update&amp;amp;nbsp;''to set the corporate currency for the RFx.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Exchange rate of different currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
ICM administrators can add, remove, or edit the exchange rates in the currency masterdata. The specified currency exchange rate must have a defined validity period and also set currency exchange rates for supported currencies.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To set exchange rate of different currencies:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
1. Repeat step 1 from the configuring the corporate currency in currency master section.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
2.'''Select''' the ''Exchange Rate Master'' from the drop-down list and '''click''' ''Next''. The ''Attributes'' page opens.&lt;br /&gt;
&lt;br /&gt;
3.&amp;amp;nbsp;'''Enter&amp;amp;nbsp;'''the following information on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Masterdata Code: This is generated automatically after the masterdata is created. &lt;br /&gt;
*From Currency Code: '''Select&amp;amp;nbsp;'''the&amp;amp;nbsp;''From Currency Code. ''This denotes the currency from which you want to convert a particular amount to a different currency. For example, '''select&amp;amp;nbsp;'''''SGD.&amp;amp;nbsp;'' &lt;br /&gt;
*To Currency Code:&amp;amp;nbsp;'''Select '''the&amp;amp;nbsp;''To Currency Code. ''This denotes the currency to which you want to convert a particular amount. For example,&amp;amp;nbsp;'''select '''''USD.'' &lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;You can only select the From Currency Code and To Currency Code for the currencies that are still valid.&amp;lt;/div&amp;gt; &lt;br /&gt;
*&amp;amp;nbsp;Exchange From Date:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the date from which you want to make the exchange rate applicable. For example,&amp;amp;nbsp;'''select&amp;amp;nbsp;'''July 8, 2020.&amp;amp;nbsp; &lt;br /&gt;
*Exchange To Date:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the date to which you want to make the exchange rate applicable. The&amp;amp;nbsp;''To Date&amp;amp;nbsp;''must always be greater than the&amp;amp;nbsp;''From Date.&amp;amp;nbsp;''For example,&amp;amp;nbsp;'''select&amp;amp;nbsp;'''''August 8, 2020.&amp;amp;nbsp;'' &lt;br /&gt;
*Exchange Rate:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''or&amp;amp;nbsp;'''enter&amp;amp;nbsp;'''the exchange rate. This is the value of one currency used to convert to another currency. For example, 1 SGD equals to 0.72 USD.&amp;amp;nbsp; &lt;br /&gt;
*Rate Type:&amp;amp;nbsp;'''Select&amp;amp;nbsp;'''the type of rate from the available list. For example, Fixed Rate which is the rule applied by the government that ties the country's currency official exchange rate with another country's currency.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
4.&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Save.&amp;amp;nbsp;''The masterdata record for exchange rate between two currencies is added successfully. The masterdata&amp;amp;nbsp;''Details&amp;amp;nbsp;''page opens.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
You can perform the following operations on this page:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Edit:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Edit&amp;amp;nbsp;''to make changes to the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
*Deactivate:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Deactivate&amp;amp;nbsp;''to deactivate but not delete the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
*Delete:&amp;amp;nbsp;'''Click&amp;amp;nbsp;'''''Delete&amp;amp;nbsp;''to delete the masterdata record.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Selecting RFx currency and allowed currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
You can select the RFx currency (primary currency) and allowed currency on Create RFx page.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*&amp;amp;nbsp;Primary Currency: '''Select''' the primary currency for the RFx. If the user preferred currency is not added in the currency master, then the corporate currency is set as the primary currency of the RFx. For example, if user preferred currency is SGD which is not added in currency master, then the primary currency is set as USD assuming it is set as the corporate currency.&amp;amp;nbsp; &lt;br /&gt;
*Allowed Currency: '''Select''' the allowed currency for the RFx. This is the currency allowed by the buyers for the suppliers operating from a different country. The selected allowed currencies can be used by suppliers for bidding. Suppliers can view the newly added currencies even when the round is Open and select them as required. Buyers can update the allowed currency at any time using ''Modify RFx'' option. The allowed currencies cannot be deleted after the RFx is approved. &lt;br /&gt;
&lt;br /&gt;
=== Selecting the exchange rate for RFx&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can view the exchange rate throughout the RFx lifecycle by clicking the View Exchange Rate Table icon at RFx, Line Items, Bids, Bid Responses. The exchange rate basis can have one of the following values:&lt;br /&gt;
&lt;br /&gt;
*RFx Open Date: This is selected by default. When this is selected, system uses the start date of first round for determining exchange rates. &lt;br /&gt;
*RFx Closed Date: This date must be selected same as the round end date. When this is selected, system uses close date of the last round for determining applicable exchange rates. &lt;br /&gt;
*User selected:&amp;amp;nbsp;This is the date from when the exchange rates are made applicable by the buyers. It is mandatory to select the Exchange Rate Date that is enabled after selecting User Selected as the Exchange Rate Basis. The selected date is used as the date to determine the exchange rate and all calculations of currency conversion. &lt;br /&gt;
&lt;br /&gt;
Buyers can view the exchange rate information when selecting the Exchange Rate Basis as RFx Open Date or RFx Closed Date after the RFx is approved and the round is created.&lt;br /&gt;
&lt;br /&gt;
=== Selecting currencies from the list of allowed currencies ===&lt;br /&gt;
&lt;br /&gt;
Buyers can select the currencies for the RFx from the list of allowed currencies. The allowed currencies of the RFx can be used as the bid currency by the suppliers. The currency attributes for the line item are restricted to RFx currency. The modified allowed currencies for RFx are displayed as bid currencies for all items.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;div class=&amp;quot;note-box&amp;quot;&amp;gt;'''Note''':&amp;amp;nbsp;Changing the currency type in any of the line item displays a validation message in the Validation Description column in the Microsoft Excel if the values selected in Primary and Allowed Currency is different.&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Using currency conversion rate in Bid Analysis ===&lt;br /&gt;
&lt;br /&gt;
Buyers can now:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Download the bid analysis excel file that allows to view all the bids received from multiple suppliers. &lt;br /&gt;
*Download the flexible bid analysis excel file for each round after it is closed that allows viewing bids received and converted to RFx primary currency. This file contains information for specific rounds only. &lt;br /&gt;
&lt;br /&gt;
=== Bidding in multiple currencies&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can take the following actions when the bid is created:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Select the bid currency that allows submitting the surrogate bid on behalf of the supplier.&amp;amp;nbsp; &lt;br /&gt;
*View the changes made to the bid that are logged in the&amp;amp;nbsp;''History&amp;amp;nbsp;''section on the RFx&amp;amp;nbsp;''Details&amp;amp;nbsp;''page.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Suppliers can take the following actions when bidding in multiple currencies:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*View the supported currencies for RFx that allows viewing the applicable exchange rates&amp;amp;nbsp; &lt;br /&gt;
*Select the currency from the list of allowed currencies that allows submitting the bid in the selected currency.&amp;amp;nbsp; &lt;br /&gt;
*Submit the bids for items in selected currencies. &lt;br /&gt;
*Upload or download the bidding template that allows adding bid information in excel sheet and upload to ICM.&amp;amp;nbsp; &lt;br /&gt;
*Update the bid currency using ICM and Microsoft Excel.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Currency information in awarding contracts&amp;amp;nbsp; ===&lt;br /&gt;
&lt;br /&gt;
Buyers can take the following actions when updating the awarding object for RFx using multiple currencies.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*Download the awarding decision template that will allow to award the desired suppliers and upload the awarding decision. &lt;br /&gt;
*Include the bid currency in awarding decision that allows including bid currency and other bid information in the contract.&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
== Glossary ==&lt;br /&gt;
&lt;br /&gt;
*'''Sourcing event:''' Refers to any solicitation process whether informational, commercial or technical. &lt;br /&gt;
*'''RFx:''' An acronym for X where X may stand for Information, Proposal or Quotation. &lt;br /&gt;
*'''Round:''' A single cycle of seeking proposals or bids from suppliers and evaluating them may be referred to as a Round. There can be multiple Rounds in the complete RFx lifecycle. &lt;br /&gt;
*'''Bid:''' The response submitted by a supplier for an RFx created by the buyer is referred to as a bid. Typically, bid is part of a round and may be revised and resubmitted by the supplier till the round is open. &lt;br /&gt;
*'''Bid Analysis: '''The process of comparing and analyzing the bid responses received from one or more suppliers along with the evaluation criteria created by the buyer. &lt;br /&gt;
*'''Awarding: '''When all the Rounds are closed, and bids are analyzed, the buyer creates the awarding instance that will be awarded to the suppliers that match the evaluation criteria. &lt;br /&gt;
*'''Split Awarding: '''It is the process of awarding the RFx to multiple suppliers with specifically decided quantity or percentage. &lt;br /&gt;
&lt;br /&gt;
'''Related Topics''':''&amp;amp;nbsp;[[Agreement_Management|Agreement Management]]&amp;amp;nbsp;|&amp;amp;nbsp;[[ICM_Sourcing_App|ICM Sourcing&amp;amp;nbsp;App]]&amp;amp;nbsp;|&amp;amp;nbsp;''&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14240</id>
		<title>Icertis Business Apps</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14240"/>
				<updated>2020-08-11T04:56:46Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICM Business Applications =&lt;br /&gt;
&lt;br /&gt;
ICM Business Applications, built on the Icertis Contract Management (ICM) platform, help customers address specific business requirements and get even more out of their investment in the ICM platform.&lt;br /&gt;
&lt;br /&gt;
== ICM Sourcing Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing application places contracts at the center of the sourcing process to ensure compliance, minimize risk, and create long term strategic agility. Get full visibility into supplier’s risk profile and ensure compliance throughout the procurement process. Leverage AI/ML based contract terms and clause recommendations to better negotiate RFx events and surface opportunities for savings. Perform side-by-side analysis of bids or proposals, and score them with both qualitative and quantitative criteria. Get a complete view of your relationship with suppliers including current and past contracts, historical performance and complete risk profile for a unified view for sourcing events.&lt;br /&gt;
&lt;br /&gt;
== ICM Obligation Management Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Obligation Management application enables companies to better manage their commitments and to realize the full value of their entitlements. This helps optimize business performance, and protects organizations from reputational, commercial and financial risks. Built on the ICM platform and infused with artificial intelligence, the new app transforms how organizations identify, create, manage and fulfill obligations that were previously hidden in complex contract language. The app includes automatic obligation discovery, powerful rule-based obligation ownership, workflow tools to ensure seamless obligation fulfillment, and sophisticated analytics – all designed to protect your business and maximize the ROI of your relationships.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''Extend Contract Type definition to be able to describe the Application Type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICM offers the ability to determine the Application Type (''Contracting'',&amp;amp;nbsp;''Sourcing'',&amp;amp;nbsp;''Proposal'',&amp;amp;nbsp;''Obligation Management'', and&amp;amp;nbsp;''Supplier Lifecycle Management'') when creating a Contract Type.&amp;amp;nbsp;The access privileges for Business Applications such as Sourcing, are driven through Security Groups.&lt;br /&gt;
&lt;br /&gt;
== ICM Risk Management Application ==&lt;br /&gt;
&lt;br /&gt;
The Icertis&amp;amp;nbsp; Risk Management application to make it easier for professionals to carry out their tasks related to risk management such as assessment, due diligence, remediation, monitoring and reassessment. Risk Management is the process of identifying the potential risk, assessing the magnitude of risk based on the business objectives and devising strategies to mitigate them and tracking the performance until they are completely mitigated.&lt;br /&gt;
&lt;br /&gt;
The platform’s modern, scalable and integration friendly cloud architecture can model even the most complex risk management scenarios. It enables secure communication with different parties involved in the process of risk management that is more effective than the traditional ways of communication such as email. Its user-friendly interface makes it possible for anyone in the enterprise, from the risk management personnel to the supply analytics team, to be able to use the platform with ease.&lt;br /&gt;
&lt;br /&gt;
== ICM Mobile Application ==&lt;br /&gt;
&lt;br /&gt;
Icertis Contract Management (ICM) is a secure, scalable and integrated platform for contract lifecycle management. It transforms contracts into strategic business assets, giving global enterprises powerful new capabilities to increase compliance, improve governance, enhance user productivity, control costs, maximize ROI and mitigate risks.&amp;amp;nbsp;&amp;lt;br/&amp;gt; ICM is available both as a Cloud (Web) offering and a Mobile application. The mobile version in an innovative, easy-to-use, and convenient platform that provides a subset of the features available on the Cloud platform. It allows you to quickly and easily access Agreements, Requests, Tasks and Commitments that you are authorized to view and perform key actions on them. You can approve or reject Agreements/Requests, or delegate tasks, anytime, anywhere from your mobile devices.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:''' [[ICM_Sourcing_App|ICM Sourcing App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|ICM Obligation Management App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[ICM_Risk_Management_App]] |&amp;amp;nbsp;[[ICM_Mobile_App|ICM Mobile App]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	<entry>
		<id>https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14239</id>
		<title>Icertis Business Apps</title>
		<link rel="alternate" type="text/html" href="https://iciwikiapac.icertis.com:443/ICIHelp8.2/index.php?title=Icertis_Business_Apps&amp;diff=14239"/>
				<updated>2020-08-11T04:56:10Z</updated>
		
		<summary type="html">&lt;p&gt;123.252.235.74: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= ICM Business Applications =&lt;br /&gt;
&lt;br /&gt;
ICM Business Applications, built on the Icertis Contract Management (ICM) platform, help customers address specific business requirements and get even more out of their investment in the ICM platform.&lt;br /&gt;
&lt;br /&gt;
== ICM Sourcing Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Sourcing application places contracts at the center of the sourcing process to ensure compliance, minimize risk, and create long term strategic agility. Get full visibility into supplier’s risk profile and ensure compliance throughout the procurement process. Leverage AI/ML based contract terms and clause recommendations to better negotiate RFx events and surface opportunities for savings. Perform side-by-side analysis of bids or proposals, and score them with both qualitative and quantitative criteria. Get a complete view of your relationship with suppliers including current and past contracts, historical performance and complete risk profile for a unified view for sourcing events.&lt;br /&gt;
&lt;br /&gt;
== ICM Obligation Management Application ==&lt;br /&gt;
&lt;br /&gt;
The ICM Obligation Management application enables companies to better manage their commitments and to realize the full value of their entitlements. This helps optimize business performance, and protects organizations from reputational, commercial and financial risks. Built on the ICM platform and infused with artificial intelligence, the new app transforms how organizations identify, create, manage and fulfill obligations that were previously hidden in complex contract language. The app includes automatic obligation discovery, powerful rule-based obligation ownership, workflow tools to ensure seamless obligation fulfillment, and sophisticated analytics – all designed to protect your business and maximize the ROI of your relationships.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#008000;&amp;quot;&amp;gt;'''Extend Contract Type definition to be able to describe the Application Type'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ICM offers the ability to determine the Application Type (''Contracting'',&amp;amp;nbsp;''Sourcing'',&amp;amp;nbsp;''Proposal'',&amp;amp;nbsp;''Obligation Management'', and&amp;amp;nbsp;''Supplier Lifecycle Management'') when creating a Contract Type.&amp;amp;nbsp;The access privileges for Business Applications such as Sourcing, are driven through Security Groups.&lt;br /&gt;
&lt;br /&gt;
== ICM Risk Management Application ==&lt;br /&gt;
&lt;br /&gt;
The Icertis&amp;amp;nbsp; Risk Management application to make it easier for professionals to carry out their tasks related to risk management such as assessment, due diligence, remediation, monitoring and reassessment. Risk Management is the process of identifying the potential risk, assessing the magnitude of risk based on the business objectives and devising strategies to mitigate them and tracking the performance until they are completely mitigated.&lt;br /&gt;
&lt;br /&gt;
The platform’s modern, scalable and integration friendly cloud architecture can model even the most complex risk management scenarios. It enables secure communication with different parties involved in the process of risk management that is more effective than the traditional ways of communication such as email. Its user-friendly interface makes it possible for anyone in the enterprise, from the risk management personnel to the supply analytics team, to be able to use the platform with ease.&lt;br /&gt;
&lt;br /&gt;
== ICM Mobile Application ==&lt;br /&gt;
&lt;br /&gt;
Icertis Contract Management (ICM) is a secure, scalable and integrated platform for contract lifecycle management. It transforms contracts into strategic business assets, giving global enterprises powerful new capabilities to increase compliance, improve governance, enhance user productivity, control costs, maximize ROI and mitigate risks.&amp;amp;nbsp;&amp;lt;br/&amp;gt; ICM is available both as a Cloud (Web) offering and a Mobile application. The mobile version in an innovative, easy-to-use, and convenient platform that provides a subset of the features available on the Cloud platform. It allows you to quickly and easily access Agreements, Requests, Tasks and Commitments that you are authorized to view and perform key actions on them. You can approve or reject Agreements/Requests, or delegate tasks, anytime, anywhere from your mobile devices.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
'''Related Topics:''' [[ICM_Sourcing_App|ICM Sourcing App]]&amp;amp;nbsp;|&amp;amp;nbsp;[[Obligation_Management|ICM Obligation Management App]]&amp;amp;nbsp;|&amp;amp;nbsp;ICM Risk Management App |&amp;amp;nbsp;[[ICM_Mobile_App|ICM Mobile App]]&amp;amp;nbsp;|&lt;/div&gt;</summary>
		<author><name>123.252.235.74</name></author>	</entry>

	</feed>