Revision as of 08:56, 13 September 2019 (view source) IDT-5 (Talk | contribs) ← Older edit		Latest revision as of 05:14, 27 January 2021 (view source) WikiSysop (Talk | contribs)
(211 intermediate revisions by 5 users not shown)
Line 1:		Line 1:
−	= ICM Release Notes - Release 7.9 =	+	= ICI Release Notes - Release 7.15 =
−	== Overview of Release 7.9 ==	+	== List of Enhancements 7.15 ==
−	The 7.9 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience and intuitiveness by continually improving ICM functionalities and user interface.	+	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.
	The key enhancements of this release include:		The key enhancements of this release include:
−	*Enhancements in AI applications such as providing the agreement/clause similarity functions and some UX improvements in the ''NegotiateAI'' app, supporting obligation discovery on templates and incorporating user actions feedback in the ''ObligationAI'' app, adding support for implementation of custom visualization in the ''VisualizeAI ''app, and adding support for Table discovery in the ''DiscoverAI'' app.	+	*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>
−	*Allowing multiple stakeholders to collaborate within ICM itself in the context of contract, thus eliminating the need for using external tools such as Email, Skype, etc.	+	**'''''User Experience'''''
−	*Supporting the ability to apply nested filters to search entities. The search capabilities now also allow searching agreements and associated documents based on clause usage, so that users can tackle the high-risk agreements first and mitigate risks.	+	***To ensure that the agreement document is generated with the correct clauses and metadata, we now can preview an agreement from the pre-draft stage to the Approved stage, enabling a comprehensive review before publishing the contract.&nbsp;
−	*Ability to compare ''Associations tagged as a Table'' across versions	+	***Improved usability for the global user base and their individual UI language preferences via expanded localization coverage which now includes support for localized “Reason Codes”.
−	*Improving usability by providing the ability to compare Associations tagged as a table across versions, allowing comparison of any two versions of the agreement document, and displaying a banner for an announcement or scheduled event.	+	***Friction-free collaboration enabled via the Collaboration Portal’s external user interface which now enables external users to search contract requests, agreements, associations and masterdata records.&nbsp;
−	*Improving Power Business Intelligence (BI) usability by displaying the power BI dashboard on the ''Advanced Analytics'' tile and making some UX related changes to improve user experience.	+	***Improved document review process where the display order for clauses in the ICI web and in Icertis Experience for Word match the order in which the clauses are configured in the respective template and generated agreement. &nbsp; &nbsp;
−	*Introducing the bulk import tool to import templates/clauses in bulk along with tagging and rules, enhancing bulk upload capability to create an assignment or initiate termination, provision users, and add team members when creating or updating an agreement/amendment.	+	***Improved usability whereby the attribute multi-selection interface, when creating an agreement, can be configured as either radio buttons or checkboxes to tailor the agreement creation experience per the contract type.&nbsp;
−	*Enhancing the ICM infrastructure to support multiple application types (''Contracting, Sourcing, Proposal, Obligation Management, and Supplier Lifecycle Management'') when creating a contract type.	+	***Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export.&nbsp;
−	*Introducing the ability to tag the string masterdata localized attributes to support bilingual templates within ICM.	+	***Improved usability where the sequence of values displayed in a masterdata lookup drop-down can now be configured to have the most frequently accessed values available at the top of the list.&nbsp;<br/> &nbsp;
−	*Improving the ability to create rules by introducing new conditions such as ''Has A Value'' and supporting power set conditions for multi-select data.&nbsp;	+
−	*Extending support for template variables to be able to track the dependency between the contract type attributes and template variables.	+	*'''''Workflow Enhancements'''''
−	*Refining reports to display the date and time as per user preferences in addition to more reports now being available on the dashboard as KPIs.	+	**Greatly improved system availability during Publish operations where now only the contract types being published are not available during this system operation as opposed to the whole system being unavailable.
−	*Improving the Icertis Experience by:	+	**Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.
−	**Introducing a new .JS version of the ICM Outlook plugin to be able to upload the next version of the agreement document and associated document, or creating a new association instance and the uploading the associated document received over email to the agreement, thus reducing the overall turnaround time for the author.	+	**To continue bringing Extension Attributes capabilities at par with regular attributes, these are now quickly viewable for easy reference in the agreement entity’s “Agreement Clauses” tab.
−	**Enhancing the Office.js based Add-in experience in ICM for MS Office Word 2016 onwards that enables you to have richer, more secure and centralized Web experience of managing ICM functions right inside MS Office Word.	+	**Agreements can be Approved or Rejected from within an agreement notification email itself making it faster to take actions on an agreement and reducing turnaround time for approval cycles.&nbsp;
−	**Introducing a new field for Salesforce users named ''Field Set Name'' so that the adapter reads the metadata and sends only the attributes defined for the entity when the integration is triggered from Salesforce. It also allows using attributes defined at the template level to store critical data as part of the agreement and sync with Salesforce, thus avoiding data duplication and redundancy in the process.	+	**Expanded contract request experience now includes the ability to request Contract Terminations.
−	**Collaborating in Microsoft Teams using ICM Bot to provide a seamless user experience when authoring contracts, negotiations or when discussing ideas, and in turn significantly improving the cycle time.	+	**Bulk actions support now extended to Terminating agreements in bulk to support situations that require it, such as regulatory changes, or business partner insolvency. &nbsp;
−	**Configuring the ICM Workday adapter so that executed agreements can be attached as .PDF, instead of .docx.	+	**To save time when re-instantiating a terminated agreement, due to reasons such as reviving a business relationship, you can now do so by simply adding amendments to the terminated agreement rather than by having to create a new agreement from scratch.
−	**Extending support of wet signatures available in Adobe Sign to ICM, and supporting redlining in associations tagged as a table in a template or agreement document, in addition to allowing the user to send supporting documents along with the main agreement for signature when using Adobe Sign.	+	**Simplified administration of the first run default user preference which can now be pre-set or updated for users based on their location or department.
−	<div class="note-box">'''Note: '''The ICM-Coupa integration adapter that supported the exchange of data between ICM and Coupa Spend Management platform is no longer supported.</div>	+	**Simplified signature status labels of “External”, “Internal,” and “Fully Signed” are shown in agreement versions.
−	These Release Notes provide an overview of enhancements to ICM and the ICM Experience for Integrations. Refer to the detailed Wiki documentation for explanation and capabilities of these and all other ICM features and functionalities.	+	**Enhanced flexibility when executing a large volume of contracts by not requiring the immediate upload of documents to change the status to “Executed”. Instead, the agreement status will change from “Waiting For Signature” to “Executed – Document Upload Pending”.
		+	**Enabling sharing of Associated Documents as well via the email notifications that are triggered for an agreement.
		+	**For organizational changes or employee turnover, we now provide a data management interface that enables replacing users with multiple users on supported agreement entities.
		+	**Support for granularly defining which agreement attributes for a given contract type should be cascaded to the agreement’s amendments via the “Is Inherit On Amendments” flag at the agreement contract type and template variable level.
		+	**In addition to the currently available functionality of all attributes to be superseded capability, we now offer the ability to selectively supersede an attribute through rules.&nbsp;
		+	**Conditional attributes’ comparison operators now support multiple complex conditions to dynamically display attributes based on a range of business scenarios.
		+	**Simplifying agreement workflow navigation by enabling the option to show a “No Team Available” message during workflows when a team is not needed.
		+	**Expanded support for special characters in the Attribute display name for contract requests, agreements, associations and masterdata.
		+	**Selectively download amendments with the corresponding parent and child associations in a zip package with corresponding sub-folders.&nbsp;
		+	**Larger file size support when uploading (4GB) and downloading (6GB) larger files for masterdata and associations.&nbsp;
		+	**Boost smart filter creation using string operators such as “Contains”, “Starts With”, “Does Not Contain” for the “Business Status” search facet.
		+	**Expanded support for automating the bulk upload of clauses and templates reducing the dependency on manual approvals and delays in onboarding clauses and templates.
		+	**Enhanced configurable labels for peer associations that define the contractual relationship. (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).
	&nbsp;		&nbsp;
−	== ICM Application Enhancements ==	+	*<span style="color:#800080;">'''Mobile App Updates'''</span>
−	<div class="image-green-border"><span style="color:#008000;">'''390639 – Collaboration in contracts &nbsp;'''</span>	+	**Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users.
−	Previously, stakeholders involved in the contracting/sourcing process used to communicate via external tools such as Email, Skype, etc. Managing these conversations that involved multiple stakeholders and multiple discussions was a cumbersome task. With this release, ICM has eliminated the need to use external tools and created a dedicated space available within the agreement itself.	+
−	To collaborate, multiple stakeholders involved in the contracting/sourcing process can:	+	&nbsp;
−	*Use the ''Collaboration'' tab available inside the agreement	+	*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>
−	*Provision an internal/external team member to communicate with other internal or external team member(s) by creating topics and posting messages in it	+	**Improving the filtering and searching capability which now supports searching text inside clauses or templates to allow more powerful deep searches especially when searching across large libraries.&nbsp;
−	*Provision users to send and receive attachments along with the message	+	**Improved labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
−	*Provision users to mark the topic as closed once the discussion is concluded	+	**Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
−	*Send Email notifications to participants when messages are posted in the topic	+
−	This can be achieved by setting the ''Enable Collaboration'' flag to ''Yes'' for the agreement contract type, which displays a ''Collaboration'' tab on the agreement ''Details ''page. To prevent data loss, once ''Collaboration'' is enabled for a contract type, it cannot be disabled.	+	&nbsp;
−	[[File:7.9 Release Notes 390639.PNG|720px|7.9 Release Notes 390639]]	+	*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>
		+	**'''''Icertis Experience for Word'''''
		+	***Improving the filtering and searching capability with support for searching text inside clauses or templates to allow more powerful search especially when searching across large libraries.&nbsp;
		+	***Improving labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
		+	***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;
	&nbsp;		&nbsp;
−	<div class="image-green-border">'''<span style="color:#008000;">400058 – Searching entities using nested filters</span>'''&nbsp;</div> <div class="image-green-border">
−	With this release, ICM now supports the ability to apply nested filters to search entities. This allows users to derive out-of-the-box saved search KPIs that help them manage agreements and amendments easily. For example, you can search for all agreements where John Doe is present in the agreement as the deviation approver by nesting of filters.
−	You can search and filter agreements based on any user roles using the following ''Categories'' – ''Team Member: Role Name, Is Group, Role Display Name, and User Name.''	+	*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>
		+	**Multiple enhancements to the AI-powered legal playbook capabilities:
		+	***Improved usability by enabling larger window views of the “Details” page and also including deviations.&nbsp;
		+	***All the playbook positions for a contract type now have the option to search and filter.&nbsp;
		+	***Administrators can create a new playbook record or update the existing one from within Icertis Experience for Word itself.
		+	**Improving the clause delineation logic so that users can rearrange the AI identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.
		+	**Extending the clause hierarchy discovery feature to support text PDFs in addition to .docx documents.&nbsp;
		+	**Improving library clause recommendations for discovered clause based on learnings from user’s action in previous discoveries.&nbsp;
		+	**Providing support for additional languages including “French”, “Dutch”, “Norwegian” and “Swedish” in AI apps.
		+	**Enabling users to flexibly leverage AI on-demand by manually triggering attribute discovery on an agreement from the “Attributes” page to accelerate workflows. Discovered values will be auto-filled in empty attributes, instead of redundant manual entry.
		+	**Enhancing and optimizing the performance of Machine Learning services to simplify deployment and run the workload on-demand while significantly reducing infrastructure management needs.
−	[[File:7.9 Release Notes 400058.PNG|720px|7.9 Release Notes 400058]]	+	&nbsp;
		+
		+	*<span style="color:#800080;">'''Enhancements to Reports'''</span>
		+	**Introducing the “Tagged Attributes Report” enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. This will help the Legal/admin users to assess the impact of configuration changes to the clauses and templates.&nbsp;
		+	**Introducing the “Notifications History Report” for an entity, enabling users to track what notifications were sent to which recipient and when. This provides better visibility and compliance for the users.
		+	**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.
		+	**Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.
		+	**Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis. &nbsp;
		+	**Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.
		+	**Multiple localization enhancements within reports.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''288372 – Inclusion of clauses and clause properties in search facets&nbsp;'''</span>	+	*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>
		+	**'''''Signature Workflow'''''
		+	***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid (manual and/or electronic) 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).
		+	***Enabling the ICI platform to support more than one E-signature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.
		+	***Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process.&nbsp;<br/> &nbsp;
		+	**'''''Icertis Experience for Salesforce'''''
		+	***Providing the ability to send success and failure alerts for improved monitoring of messages.
		+	***Triggering document assembly for automatic data sync and displaying completion notification.
		+	***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.<br/> &nbsp;
		+	**'''''Icertis Experience for MS CRM'''''
		+	***Providing server-to-server OAuth support, so that the adapter and the task service will use ‘client Id’ and ‘secret key’ from AKV, invoking the MS CRM APIs.
−	ICM has further enhanced the search capabilities by allowing searches on agreements,&nbsp;amendments, and advanced search based on clause usage. This allows users to prioritize the agreements they plan to work on based on clause usage, thus being able to tackle high-risk agreements first and mitigating risks.	+	&nbsp;
−	You can now search and filter agreements using the following clause categories:&nbsp;''Clause Group, Clause Language, Clause Name, Is Alternate Clause, Is Dependent Clause, Is Deviated, Is Editable, Is Mandatory, Perform Deviation Analysis, Primary Clause, and Clause Code.''	+	*<font color="#800080">'''Enhancements to Platform Tools'''</font>
		+	**Enhancing ICI to allow administrators to promote additional configurable entities from pre-production to target environments. These include organizations and organization groups, users and user groups, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings, global and admin saved searches.
		+
		+	&nbsp;
−	<span style="color:#FF0000;">Note:</span>'''&nbsp;'''''Clause Description'',&nbsp;''Clause Text'',&nbsp;''Linked Primary Clauses'',&nbsp;''Clause Status'', ''Linked Primary Template Clause'', and search based on clause text area are not supported in clause categories''.''	+	*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>
		+	**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.
−	''[[File:7.9 Release Notes 288372.PNG|720px|7.9 Release Notes 288372.PNG]]''	+	These release notes provide an overview of the enhancements to ICI, the mobile app, the ICI experience for integrations, and so on.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''384321 – Ability to compare ''Associations tagged as a Table'' across versions'''</span>	+	== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancement Details</span> ==
−	When a user uploads a new version of the document, ICM provides the ability to compare the changes in clause language or the attributes. Version-wise changed history is also stored in the ''Versions'' section on the ''Details'' page.	+	<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>
−	With this release, modifications made to associations or saved search that were tagged as a table in a template (such as adding or removing rows/columns or changing the values in individual cells) will be visible at the time of upload as well as on the ''Versions'' tab of the agreement document. This will allow the contract negotiator to make informed decisions accordingly. ICM Scribe has also been enhanced to support this capability, but provides limited information.	+	Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.
−	<span style="color:#FF0000;">Note: </span>Deviation tracking and syncing back of the changed table data to the respective association instances is not supported. Table comparison is only shown when cell values get changed, not when empty cells get added or removed.	+	With this release, a preview functionality is being introduced, so that the primary owner or contract creator 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. The preview document would also include tagged associated documents, coming through inline or inheritance associations.
−	[[File:382235.png|720px|382235]]	+	A preview section is available on the “Verify” stage of agreement/amendment creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. The preview is available till the Approved state of the agreement/amendment.
		+	'''Note: '''This functionality is configurable. It is not available by default and can be enabled or disabled for chosen contract types.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 1.png|720px|7.15 Release Notes Screenshot 1]]</div>
	&nbsp;		&nbsp;
−	<div class="image-green-border">
−	<span style="color:#008000;">'''452265 – Ability to compare any two&nbsp;versions of the agreement&nbsp;document'''</span>
−	</div> <div class="image-green-border">
−	Previously, users could only see the comparison between the last and the current version of the agreement document version. This functionality has now been enhanced and is accomplished through the ''Compare Documents'' icon on the agreement ''Details'' page, so that the user can compare any two of the available versions of the agreement as required.
−	<span style="color:#FF0000;">Note:</span> The agreement document version comparison always takes place between a higher version on the right panel and a lower version on the left panel.	+	<span style="color:#800080;">'''575640 – Creating associations on the create or edit wizard of agreement'''</span>
−	[[File:7.9 Release Notes 452265.png|720px|7.9 Release Notes 452265]]	+	Previously in ICI, contract authors had to create associations for agreements after the agreement is already created. 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 the business, and some associations are required to be created along with the agreement.
		+
		+	Hence, the ability to create association instances as part of agreement creation or update wizard is being introduced in this release. A separate page is displayed, when creating or updating the agreement or amendment, for the user to create, view, or delete inline associations. The user also has an option to select the columns and their order in the association grid.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 2.png|720px|7.15 Release Notes Screenshot 2]]<br/>  <br/> This new page also supports page navigation. Support is also provided to copy attribute rules, association events, and agreement assembly, in case associations are tagged in the agreement template.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 Release Notes Screenshot 3.png|720px|7.15 Release Notes Screenshot 3]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#800080;">'''549900 – Supporting localized reason code values as per logged in user language'''</span></div>
		+	Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers.
		+	<div class="image-green-border">ICI now extends its localization support to reason code values. Administrators can enter the translated values in the local language, for each reason code, using the “Translations Editor” tool.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.15 Release Notes Screenshot 4.png|720px|7.15 Release Notes Screenshot 4]]</div>
		+	Users can see localized reason codes as per their preferred language settings.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 5.png|720px|7.15 Release Notes Screenshot 5]]</div>
		+	The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.
	&nbsp;		&nbsp;
−	</div> </div>
−	<br/> '''<span style="color:#008000;">382235 – Default dashboards in advanced analytics</span>'''
−	</div> <div class="image-green-border">
−	With this release, in an effort to improve advanced analytics usability, additional functionalities have been added and some changes have been made.
−	Default Dashboards are now available in the ''Advanced Analytics'' section. The ''Advanced Analytics'' tile now displays the following 3 tabs:	+	<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from the contract request'''</span>
−	*'''''Business Summary:''''' displays the following charts based on the defined KPIs and the authorization of the user (for example, Finance Head):	+	In ICI, users create and execute a termination agreement on the main agreement instance to terminate an agreement. ICI has now extended this capability to initiate the termination from contract requests too.&nbsp;
−	**Agreement Summary such as Top Agreements by Value, Top Expiring Agreements, etc. (based on the defined KPIs).	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 6.png|720px|7.15 Release Notes Screenshot 6]]</div>
−	**Deviations Summary such as Deviated Agreements and Contract Value (s) by Org Unit, Deviated Agreements by Contract Type, etc.&nbsp;	+	Users can now enable the termination process at the contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for the contract request will have all the common attribute values inherited if the inheritance is enabled.&nbsp;
−	**Expiring Agreements such as Expiring Agreements by Month, Agreements marked for Auto-Renewal, etc.&nbsp;	+
−	**Cycle Time Report such as Cycle Time (in Days) by Contract Types, Trend of Cycle Time by Month, etc.&nbsp;	+
−	**Configuration Statistics such as Distribution of Templates by Contract Types, Clauses by Category, etc.&nbsp;	+
−	*'''''Legal Summary:'' '''displays the following based on the defined KPIs and the authorization of the user (for example, Legal Head):	+	The termination record will be displayed as a peer association under the “Association” tab for the contract request. The access privileges for the contract requests termination process is controlled through role action mapping.
−	**''Agreement Summary'' such as ''Top Agreements by Value, Top Expiring Agreements'', etc. (based on the defined KPIs).	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 7.png|720px|7.15 Release Notes Screenshot 7]]</div>
−	**''Deviations Summary'' such as ''Deviated Agreements and Agreement Value (s) by Org Unit, Deviations Trend'', etc.	+	&nbsp;
−	**''Expiring Agreements ''such ''as Expiring Agreements by Month, Agreements Value Expiring in next 12 Months by Org Unit'', etc.	+
−	**''Cycle Time Report ''such as ''Cycle Time (in Days) by Contract Types, Trend of Cycle Time by Month'', etc.	+
−	**''Configuration Statistics ''such as ''Distribution of Templates by Contract Types, User Information,'' etc.	+
−	*'''''Legal Details:''''' displays the legal details at a more granular level based on the defined KPIs and the authorization of the user (for example, Legal Head):	+	'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''
−	**''Agreement Summary'' such as ''Count of Agreements by Contract Type or Org Unit, Agreements by Status'', etc. (based on the defined KPIs).	+
−	**''Deviations Summary'' such as ''Deviated Agreements by Org Unit, Deviated Clause Cloud'', etc.	+
−	**''Expiring Agreements ''such ''as Expiring Agreements in 30 Days by their Org Unit, Agreements marked for Auto-Renewal in 30 Days by Org Unit'', etc.	+
−	**''Cycle Time Report ''such as ''Average'' ''Cycle Time (in Days) of Agreements, Month-wise Cycle Time Trend,'' etc.	+
−	*When creating reports, you can select which data model you want to use. For example, you can select the Agreements data model to get agreement centric attributes and other data. If you select Clauses data model, then you would get clauses centric attributes and other data. The same applies using the ''Ask a question'' functionality.	+	ICI’s collaboration portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&nbsp;
−	*The following UX related changes have been made:	+
−	**''Last Updated On'' text is changed to&nbsp;''Data Source updated successfully&nbsp;''	+	In our continuous effort to improve usability, a search option has been introduced on contract requests, agreements, associations, and masterdata index pages, so that external users can easily search records. The attributes displayed as columns of the search grid are included as facets in the filter options to perform a more refined search.
−	**The ''Refresh'' icon (which shows the minimum time of refresh cycle among all datasets) is changed to the ''Refresh page'' button	+
−	*The ''Save your report'' option is now available for global reports. Users can save a copy of the global report. It is visible in the user’s''My Reports'' section and can be modified as required. If special characters are added to the report name, an error message will be displayed.	+
−	*You can change the name of the report using the ''Edit Report Name'' option. If special characters are added when renaming a report, an error message will be displayed.	+
−	*You can also delete this report using the ''Delete Report'' option if it is no longer relevant.	+
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''456074/439569/439668/467828 &nbsp;– Enhancements to Bulk Upload - beta version'''</span>	+	<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements'''</span>
−	The beta version of the ''Bulk Upload'' functionality has been enhanced. This allows you to:	+	In ICI, users can capture additional details for a clause in extension attributes. With this release, users can view these clause extension attributes on the agreement entity for easy reference while working with agreements.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 8.png|720px|7.15 Release Notes Screenshot 8]]</div>
		+	Users can now:&nbsp;
−	*Provision users (which was earlier only available for Legacy Upload)	+	*Select and save extension attributes to display in the grid view, via the “Default Search” column functionality.
−	*Add team members when creating an agreement or amendment	+	*View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.
		+	*View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 9.png|720px|7.15 Release Notes Screenshot&nbsp;9]]</div>
		+	&nbsp;
−	[[File:7.9 Release Notes 456074-439569-439668-467828.PNG|720px|7.9 Release Notes 456074-439569-439668-467828 - 01]]	+	<span style="color:#800080;">'''514615 – Streamlining&nbsp;the approval process over emails'''</span>
−	*Add team members when updating agreement or amendment	+	The approval process has now been streamlined by allowing approvers to directly approve or reject an agreement from within the email itself, through a hyperlink to the webpage, instead of logging in to the system to do so. External users, who do not have access to ICI can now review or approve the documents from the notification email, instead of sending offline copies to do so and then uploading them to ICI. This reduces the overall turnaround time and increases productivity.&nbsp;
−	*Create assignment and initiate the termination of agreements	+
−	[[File:7.9 Release Notes 456074-439569-439668-467828-2nd.PNG|720px|7.9 Release Notes 456074-439569-439668-467828 - 02]]	+	The internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. The external users are authenticated by sending them a code in the email, which has limited validity.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 10.png|720px|7.15 Release Notes Screenshot&nbsp;10]]</div>
		+	With this release:
		+	*Administrators can add tag an Approve/Reject link in the notification template.
		+	*Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.
		+	*Approvers can approve/reject the agreement or amendment from the email, only if the task approval or review is assigned to them. Based on the access, the user can approve or reject the agreement by entering notes or reasons for rejection respectively.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 11.png|720px|7.15 Release Notes Screenshot]]</div>
	&nbsp;		&nbsp;
−	<div class="image-green-border"><span style="color:#008000;">'''420230 – Extending contract type definition to determine the Application type'''</span></div>
−	ICM offers the ability to determine the Application type (''Contracting'',&nbsp;''Sourcing'',&nbsp;''Proposal'',&nbsp;''Obligation Management'', and&nbsp;''Supplier Lifecycle Management'') when creating a contract type. This is possible with the inclusion of two new choice type attributes,&nbsp;''Business Application Type''&nbsp;and&nbsp;''Business Application Category''&nbsp;at the contract type level. This feature helps effortlessly drive business applications on the ICM platform.&nbsp;These attributes are applicable for agreements and associated document contract types, after the business application is enabled through a technical configuration. The access privileges for business applications (such as Sourcing)&nbsp;are driven through Security Groups.
−	[[File:7.9 Release Notes 420230.PNG|720px|7.9 Release Notes 420230]]	+	<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>
		+	To improve the user experience, clauses are now displayed in the same order in the agreement document as they are tagged inside the agreement, on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 12.png|720px|7.15 Release Notes Screenshot 12]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">408652 – Displaying an announcement banner</span>'''	+	<span style="color:#800080;">'''617385&nbsp;– Ability to define additional clause group under clause entity'''</span>
−	ICM has now improved user experience by providing the capability of displaying a scrolling banner message to inform users of a scheduled event or an announcement. For example, you can inform users that a maintenance activity is scheduled in 24 hours. A banner will scroll at the top of the ICM window alerting the users of the downtime, so that they can plan their work accordingly.	+	Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.
−	This can be achieved through ''Application Settings'' by toggling the ''Show announcement banner'' field to ''Yes'' and entering the message to be displayed in the ''Announcement message'' box.	+	With this release, this capability has been further enhanced so that the configurator can configure various clause group names in ICI. These clause groups can be categorized or grouped as per business requirements for better identification and negotiations during the contract workflow.
−	[[File:7.9 Release Notes 408652.PNG|720px|7.9 Release Notes 408652]]	+	Administrators can now:
		+	*Define and update clause groups.
		+	*Edit, delete, activate or deactivate clause group entities.
		+	*View additionally added clause group values in the clause entity when creating or editing a clause.
		+	*Search agreement records or clauses on the index page on clause group attributes with added values.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>
		+
		+	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 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.
		+
		+	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. The system sets an identifier attribute "Is Termination Revived" for such revived base agreements, and users can use them in search filters, notification rules while configuring saved searches, and so on.
		+
		+	'''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.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 13.png|720px|7.15 Release Notes Screenshot 13]]<br/> &nbsp;</div>
		+	<span style="color:#800080;">'''514625 – Terminating agreements in bulk'''</span>
		+
		+	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 the termination of agreements in bulk, thereby saving the time to terminate agreements one by one and reducing manual errors.
		+
		+	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.&nbsp;
		+
		+	Users can now:&nbsp;
		+
		+	*Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch. &nbsp;
		+	*Generate and view a status report for agreements terminated in bulk.&nbsp;
		+	*Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk action.
		+
		+	'''Note:''' All prerequisite configurations applicable for the termination workflow should also be set for the bulk termination process.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''555898 – Defining display sequence on lookup attributes at the contract type level'''</span>
		+
		+	Previously in ICI, users could not define the display order for lookup attribute values in a drop-down on the UI that references masterdata. Users had to scroll through all the populated values to find the desired values during agreement creation. &nbsp;
		+
		+	Configurators can now define and maintain the display sequence for selected masterdata records, starting from 1 to n, at the contract type level, using a seeded display sequence attribute. The values will thus be displayed at the top for easier and faster selection in lookup attributes. &nbsp;
		+
		+	This display sequence setting is supported on the create, edit, and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause entities, and template variables. The display will follow the default alphabetical order if the display sequence is not configured in masterdata.&nbsp;<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 14.png|720px|7.15 Release Notes Screenshot 14]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''408644 – Google cloud Pub/Sub support'''</span>	+	<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the agreement details page'''</span>
−	ICM has introduced out-of-the-box support for Google Pub/Sub (which is a fully managed real-time messaging service provided by Google Cloud) for ICM internal communication and also for any third party integrations.	+	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.&nbsp;
−	In ICM, the ''Message Pull'' option is used to receive messages from Pub/Sub. This change is transparent for ICM and there is no change as to how the communication between ICM Application (UI/API/Task) is perpetual.	+	ICI now allows users to view amendments in the “Grid” view, and toggle between grid view or 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.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 15.png|720px|7.15 Release Notes Screenshot 15]]</div>
		+	&nbsp;
		+	<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>
		+
		+	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.&nbsp;
		+
		+	Users can now:&nbsp;
		+
		+	*View eight options in a drop-down list (instead of six), without scrolling.&nbsp;
		+	*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;
		+	*View all selected values at the top of the drop-down.
		+	*Deselect the selected values, individually or all with a single click, without opening the drop-down.<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 16.png|720px|7.15 Release Notes Screenshot 16]]</div>
	&nbsp;		&nbsp;
−	</div>
−	=== Enhancements to Rules ===
−	'''<span style="color:#008000;">397346 – Ability to create a rule with ''Has A Value ''condition</span>'''&nbsp;	+	<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>
−	With this release, the&nbsp;''Has A Value''&nbsp;condition has been enhanced to include all data types and system defined attributes such that rules can be set up for an attribute having any value.	+	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.&nbsp;
−	For example, you want to set up a rule so that an approver John Doe should approve the contract if a discount is applicable to it, irrespective of the value of the discount. Then, user can add a rule using the&nbsp;''Has A Value''&nbsp;condition, such that John Doe is added as an approver if the discount has a value of 5%, 10% or whatever value is desired.&nbsp;	+	With this release, ICI provides the ability to configure a lookup attribute using the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute.&nbsp;
−	Earlier this condition supported only a limited set of user defined and system attributes, but now it has been enhanced to support all data types and additional system attributes. It is now also available for the following contract type attributes and data types:&nbsp;''Contract Type Lookup'',&nbsp;''Contract Type Multi-Select Lookup'',&nbsp;''Choice'',&nbsp;''Multi-Select Choice'',&nbsp;''Number'',&nbsp;''Currency'',&nbsp;''Percentage'',&nbsp;''Date'',&nbsp;''DateTime'', and&nbsp;''URL''. In addition, it is also available for system attributes such as&nbsp;''Template Name''&nbsp;and&nbsp;''Type Of Paper''.	+	Configurators can now:&nbsp;
−	<div class="image-green-border">[[File:7.9 Release Notes 397346.PNG|720px|7.9 Release Notes 387346]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>	+
−	<span style="color:#008000;">'''408653 – Enhancing rules to support power set conditions for multi-select data&nbsp;'''</span>	+
−	Currently, ICM supports only the ''Contains/Does Not Contain'' conditions for multi-select data. The ''Contains'' operator does not check whether all selected values of the attribute are a subset of expected values, but only checks for any one of them. Thus, when the rules were evaluated, even the templates, approvers, clauses, etc. that are not required to get executed.	+	*Use the "IN” operator in the lookup filter attribute on agreement contract types.&nbsp;
		+	*View the applied filter on the “Attributes” page on the UI for the selected attribute.&nbsp;
		+	*Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute. &nbsp;<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 17.png|720px|7.15 Release Notes Screenshot 17]]</div>
		+	&nbsp;
−	To avoid this confusion, rules have been further augmented so that the user can configure conditions for power sets (i.e. cases where the user wants a rule to be executed only if the entity field contains a subset of the configured values). This is achieved by introducing the new operator, ''Subset of, ''which is applicable only to multi-select lookup that supports evaluation of string, number, user, percentage and email data types.	+	<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>
−	Let’s consider the example of a template selection rule to select multiple products using the ''Subset of&nbsp;''the operator. Suppose, the rule is defined such that ''Template 1 ''should be selected if the selection is a subset of ''Products A, B, C'', then:	+	Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;
−	*If the user selects any subset of products {A,B,C} like A,B or B,C or A,C or A,B,C, then ''Template 1'' will be available for selection	+	ICI now provides administrators the capability to set preferences as default, for users, according to their locations or the offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after the first log-in and presents the system with appropriate and specific pre-settings. &nbsp;&nbsp;
−	*If the user selects any subset of products {A,B,C} & any other product like A,B,C,D or A,B,E, then ''Template 1'' will NOT be available for selection	+
−	<div class="image-green-border">[[File:7.9 Release Notes 408653.PNG|720px|7.9 Release Notes 408653]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>	+
−	=== Enhancements to Templates ===	+
−	<span style="color:#008000;">'''419834 – Localization of masterdata attributes to support tagging of bilingual agreements/templates using Word Add-in'''</span>	+	Administrators can:&nbsp;
−	Earlier, ICM did not directly support bilingual agreements and templates tagging using Word Add-in. As a result, users had to tag multiple attributes in a template for different languages, thereby ending up duplicating multiple attributes in a contract type.	+	*Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.
		+	*View preference settings modifications details in the “History” tab for audit.&nbsp;
		+	*Search users based on parameters related to preference settings.
−	To simplify this process and facilitate bilingual templates, ICM has introduced the ability to tag the same masterdata localized attribute multiple times for different languages which can be tagged in a bilingual template via Word Add-in. This allows the user to manage the same attribute with a different language in the same template or agreement. The support for bilingual templates allows the user to specify the second language for the template and also be able to tag localized attributes in the template with the second language.<br/> <br/> <span style="color:#FF0000;">Note:'''&nbsp;'''</span>	+	Users can:&nbsp;
−	*It only supports string attributes	+	*Access the ICI system with appropriate details as default after the first login.&nbsp;
−	*Localization of masterdata attributes is applicable for - template level support for primary/secondary language, Word Add-in (.NET and Scribe), agreement and clause tags, document assembly, and rule-based assembly	+	*Override the default preference settings as per individual preferences.
−	*Rules will be evaluated in English for the masterdata localized attributes	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 18.png|720px|7.15 Release Notes Screenshot 18]]</div>
−	*Advanced search also supports the localization of masterdata attributes	+	&nbsp;
−	*It is not applicable for associations, template variables, reverse sync, and support tags on the parent agreement clause	+
		+	<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the document'''</span>
		+
		+	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.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 19.png|720px|7.15 Release Notes Screenshot 19]]</div>
		+	With this release, users can now skip uploading the document, to move agreements from “Waiting For External Signature” or “Waiting For Internal Signature” to the “Executed - (Pending Signed Document)” state.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 20.png|720px|7.15 Release Notes Screenshot 20]]</div>
		+	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. Notifications can be configured to inform users about skipped document uploads&nbsp;so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&nbsp;
		+
		+	This functionality is available for agreements, amendments, and orphan amendments.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''614860 – Attaching associated documents to agreement notifications'''</span>
		+
		+	ICI users can share the main agreement document as part of various email notifications that get triggered for the agreement from time to time.&nbsp;
		+
		+	In addition to the main agreement document, users can now also send associated documents as part of various email notifications that get triggered for the agreement from time to time. Access to these documents can be controlled based on the type of document – internal, external, or restricted. For example, some documents may only be shared with internal users, some may be shared with internal and external users, whereas some may not be shared with anyone.
		+
		+	With this release:
		+
		+	*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements, and amendments.
		+	*Users can define:
		+	**The type of notification as internal or external.&nbsp;
		+	**The type of associated document instance as internal, external, or restricted.
		+	*Based on the type of notification and type of tagged associated documents, attachments are added to the email notification.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>
		+
		+	ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.
		+
		+	With this release, users can define configurable labels for peer associations between existing contracts by configuring the “Linkage Type” masterdata. The configurable 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. The labels can be activated or deactivated as per business requirements.
		+
		+	The configurable labels support the existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as a peer, with default peer linkage type label, defined in default peer mapping for amendment.&nbsp;
		+
		+	Users can select configurable peer linkage type labels in the “Linkage Type” drop-down list and view them on various ICI functionalities such as: &nbsp;
		+
		+	*Agreement creation workflows for peer entities, assignment, and initiate termination flow.&nbsp;
		+	*Associate and Inheritance icons.
		+	*Bulk actions.
		+	*Agreement creation through business APIs.
		+	*Broadcast – “Attachments” tab and captured notes.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 21.png|720px|7.15 Release Notes Screenshot 21]]</div>
		+	'''Note:''' Multiple configurable labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 22.png|720px|7.15 Release Notes Screenshot 22]]</div>
	&nbsp;		&nbsp;
−	<div class="image-green-border"><span style="color:#008000;">'''275828 &nbsp;– Template and clause harmonization – Beta version'''</span>
−	The beta version of the ''Legacy Upload'' functionality now provides an option to upload templates and clauses in bulk. This allows users to upload templates, template metadata, extended template entity metadata, template variables, template team, clauses, clause metadata and clause team. It also supports auto-tagging in templates and clauses of template variables, contract type attributes, associations, signatories and clauses.
−	<span style="color:#FF0000;">Note:</span> To enable auto-tagging, the details need to be provided in a set format/syntax.&nbsp;	+	<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>
		+	ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements.&nbsp;
		+
		+	With this release, users will download amendments of an agreement with corresponding parent-child associations in the downloaded zip package. This is supported on the selective download option too.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 23.png|720px|7.15 Release Notes Screenshot 23]]</div>
		+	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.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 24.png|720px|7.15 Release Notes Screenshot 24]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''428153 – Promote to Production (P2P) enhancements – beta version'''</span>	+	<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at the contract type level'''</span>
		+
		+	ICI already provided the capability to exclude specific agreement attributes from being copied to amendments through technical configuration, which applied to all agreement contract types by default.&nbsp;
		+
		+	ICI now provides the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using the “Is Inherit On Amendments” flag, at the agreement contract type and template variable levels. Users can then copy these defined attribute values from base agreement to amendment during amendment creation.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 25.png|720px|7.15 Release Notes Screenshot 25]]</div>
		+	'''Note:&nbsp;'''
		+
		+	*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.
		+	*The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''614877 – Replacing a user with multiple users'''</span>
		+
		+	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.&nbsp;
		+
		+	Administrators can now:&nbsp;
		+
		+	*Replace the user with one or more users, by selecting the entity and all/selective instances of that entity, and create a saved search for records to replace users. &nbsp;
		+	*Validate the replaced user role against the assigned role.&nbsp;
		+	*Get a notification on adding or completing a task.&nbsp;<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 26.png|720px|7.15 Release Notes Screenshot 26]]</div>
		+	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 to carry out these user management actions.
		+
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>
		+
		+	In ICI, users could supersede all attributes of a parent agreement configured as ‘supersedable’ with values from its amendment, either manually using the “Supersede” action or automatically through the auto-supersede task. Users can now selectively supersede individual entities based on business conditions.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 27.png|720px|7.15 Release Notes Screenshot 27]]</div>
		+	The administrator can control the supersede functionality for agreements by:
		+
		+	*Enabling auto supersede option at the contract type level.
		+	*Configuring the “Supersede Rule” with “Is Supersede by Amendments” or “Is Supersede by Termination” options.&nbsp;
		+	*Selecting attributes in rule actions based on the selected Supersede On option.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 28.png|720px|7.15 Release Notes Screenshot 28]]</div>
		+	Users can view the attribute’s supersede value on the agreement and the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing ICI behavior.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 29.png|720px|7.15 Release Notes Screenshot 29]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>
		+
		+	In ICI, users may encounter specific workflow configurations, such as the self-approval process, that do not require users added to the team. The “No Team Available” message, displayed in such cases, adds to the number of non-value clicks for users to continue.&nbsp;
		+
		+	ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks.&nbsp;
		+
		+	Administrators can:&nbsp;
		+
		+	*Selectively enable or disable the “No Team Available” message window, at the entity contract type level, appearing at various states.&nbsp;
		+	*Disable the “No Team Available” message window altogether, at the instance level, for all entities. The instance level settings will override the entity level settings.&nbsp;
		+
		+	'''Note:''' This capability is available across ICI for all entities, events, integrations and add-ins in ICI.
		+
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>
		+
		+	Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&nbsp;
		+
		+	With this release, configurators can now set multiple, complex conditions to display ICI Web UI attributes 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 values in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality. &nbsp;
		+
		+	Users can now:&nbsp;
		+
		+	*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.&nbsp;
		+	*Support conditional expressions for extension attributes. &nbsp;
		+	*Define conditions with different operators based on the selected attribute datatype.&nbsp;
		+	*View the conditional attribute value according to the value entered in the attribute on which a condition is set.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 30.png|720px|7.15 Release Notes Screenshot 30]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''616901 – Applying facets to business status search filter'''</span>
		+
		+	Business statuses are prominently used across all customers as they reflect the actual status in business terms compared to the system workflow status. 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 the case of several business statuses.&nbsp;
		+
		+	To provide a better user experience and ease of use, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” are being added to the “Business Status” filters.<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 31.png|720px|7.15 Release Notes Screenshot 31]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>
		+
		+	Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;
		+
		+	ICI's parsing logic is now improved for handling string combinations with special and alphanumeric characters so that no errors are generated. This applies to all entities across ICI, where a combination of special characters, alphabets, and numbers can be used.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''732929 – Uploading clauses and templates in bulk'''</span>
		+
		+	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.&nbsp;
		+
		+	With this release, automation has been provided for bulk import using the “Legacy Upload” tool, 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.
		+
		+	Along with the tool, an XML specification document is also released which can be used for creating tags in the input document files of clauses and templates.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''655507 – Uploading and downloading large files with the file path attribute'''</span>
		+
		+	ICI now provides support for larger files. This is applicable to masterdata and associations.
		+
		+	Users can now:
		+
		+	*Upload files up to 4GB under the file selection attribute.&nbsp;
		+	*Upload files with all supported file extensions allowed in the file selection attribute.
		+	*Download All/Download Package up to 6 GB.
		+
		+	ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;
		+
		+	'''Note:&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.&nbsp;The Upload/Download of the files would be supported for Azure and Windows Storage.
		+
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''618994 – Supporting special characters in agreement templates and support to skip empty columns while a saved search/association is tagged in a template'''</span>
		+
		+	Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space.&nbsp;
		+
		+	Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash),&nbsp;: (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (period) 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.
		+
		+	In scenarios where the association or saved search is tagged as a table in the agreement, and a particular column of the table does not have any data, we have introduced a functionality to skip such empty columns.&nbsp;
		+
		+	During template creation from Icertis Experience for Word, the configurator can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table. This property needs to be added manually in the “Content Control Properties”, at any position after the contract type GUID, separated by a '|' (pipe separator). This enables empty columns to be skipped in document assembly, thereby eliminating unnecessary empty columns in the agreement version. The order of the columns in the table is determined by the attributes in the display preference of the associated document contract type.&nbsp;
		+
		+	Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 32.png|720px|7.15 Release Notes Screenshot 32]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>
		+
		+	With this release, ICI provides new controls for multi-select and single-select choice attributes.&nbsp;
		+
		+	Users can configure an alternate UI control for drop-downs with a 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. &nbsp;&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 33.png|720px|7.15 Release Notes Screenshot 33]]</div>
		+	Users can select:&nbsp;
		+
		+	*The radio button for single-select choice attributes.&nbsp;
		+	*The checkbox list for multi-select choice attributes.
		+
		+	The configuration applies across ICI for the creation and editing of agreement, amendment, associated document, masterdata, and contract request entities.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 34.png|720px|7.15 Release Notes Screenshot 34]]</div>
		+	&nbsp;
		+
		+	<span style="color:#4B0082;">'''593421 – Labeling agreement document versions as per signature copy'''</span>
		+
		+	While agreements go through various signature states till executed, users can now navigate to the “Versions” tab and easily identify which version of the agreement is internally signed, externally signed, or fully signed.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 35.png|720px|7.15 Release Notes Screenshot 35]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''872309 – Providing flexibility for assembling associations tagged as clauses'''</span>
		+
		+	In ICI, on publishing and updating actions, all clauses are evaluated, assembled and changes are reflected in the agreement document. However, if associations are tagged in clauses, on “Assemble Contract” and “Send For Approval” actions, clauses do not get assembled and associations do not get populated in the agreement document.
		+
		+	As part of our continuous effort to provide flexibility to ICI users and improve the user experience, a key “Core.Agreement.EnableDynamicClauseAssemblyPostCreate” has been introduced.&nbsp;
		+
		+	*If the key is enabled, when an associated document is uploaded, the entire document will be automatically assembled (Clause, Attribute, Associations, Saved Search) on the “Assemble Contract” and “Send For Approval” actions.
		+	*If the key is not enabled, the ICI document will be assembled on “Publish” and “Edit Agreement” actions. Only associations will be assembled on the “Assemble Contract” and “Send For Approval” actions.
		+
		+	'''Note: '''By default, the key is set to false.<br/> &nbsp;
		+
		+	== Mobile App Enhancement Details ==
		+
		+	<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>
		+
		+	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 on the mobile app.&nbsp;Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to refresh on these actions and improve usability automatically.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</span>
		+
		+	As part of our new branding, “ICM” has been updated to “ICI”, and the new logo has also been added to the mobile app.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>
		+
		+	Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.
		+
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>
		+
		+	With this release, the UI WebView component for iOS has been deprecated.<br/> &nbsp;
		+
		+	== ICI API Enhancement Details&nbsp; ==
	<div class="image-green-border">		<div class="image-green-border">
−	The beta version of the Promote to Production tool is now enabled. This functionality, provided to administrators, can promote ICM configurations/modifications that are made to ICM configurations in pre-production environments to production environments.	+	<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>
−	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.	+	With this release, support has been added for the script and integrated attributes. They are available as cascaded attributes for lookup fields when configured at the contract type level.&nbsp;
−	<span style="color:#FF0000;">Note: </span>This tool does not support the movement of agreements and amendments.&nbsp;	+	This is applicable for visualizing, retrieval, creation, and updating of the instances of the following entities:<br/> Contract Requests
		+
		+	*Agreements
		+	*Associations
		+	*Amendments
		+
		+	New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.
	&nbsp;		&nbsp;
		+
		+	<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>
		+
		+	ICI already supports downloading agreements.
		+
		+	As part of our efforts to continually improve ICI, new API endpoints have been added in this release to download associated documents of agreements and contract requests.
		+
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>
		+
		+	A new service bus topic has been created to publish messages about workflow operations. The messages will notify if any failures are encountered during workflow actions.
		+
		+	As workflow APIs are asynchronous, customers using Actions API and API 2.0 get a return success code, only on the initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.
		+
		+	Users will now get a definite response, with required details of the error and cause on services bus. Based on the topic notification, integration developers can take follow-up actions based on success and failure.<br/> &nbsp;
		+
		+	<br/> <span style="color:#800080;">'''660859 – Supporting TrackingId in APIs'''</span>
		+
		+	To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;
		+
		+	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).&nbsp;
		+
		+	In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused the failure of the agreement creation. An identifier has been added to resolve this issue which subsequent APIs for correlating from a logging perspective can pass.&nbsp;
		+
		+	The following API changes have been made to ensure that the existing implementation and code remains intact:
		+
		+	*Provided support for a “TrackingId” header in every logging request.&nbsp;
		+	*Users will receive the “TrackingId” 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).
		+	*The called API path with query string will be logged in Kibana. In Kibana, developers must look for “CorrelationID” which maps the “TrackingId” used in API.<br/> &nbsp;
		+
		+	'''Note: '''The implementation of the "TrackingId" is optional and the value must be GUID only.&nbsp;Supported in API 1.0 as well.
		+
		+	This can be used for:
		+
		+	*Related API Calls
		+	*Async operations
		+	*Bulk operations
		+	*Status check operations &nbsp; &nbsp;
	</div>		</div>
−	'''<span style="color:#008000;">397327 – Ability to drive dependency of template variables on agreement attributes&nbsp;</span>'''	+	&nbsp;
−	With this release, ICM has extended support to template variables being conditional to the value of the attributes that are part of a contract type. The user can track the dependency between the contract type attribute and template variable as well as eliminate the creation of duplicate attributes between them.&nbsp;	+	== ICI Add-ins Enhancement Details ==
−	This can be achieved by any user with&nbsp;''Manage''&nbsp;access on&nbsp;''Template Management''&nbsp;tile by enabling the&nbsp;''Is Conditional&nbsp;''flag for each template variable when creating or editing a template. When the&nbsp;''Is Conditional''&nbsp;flag is&nbsp;''On'', a user is able to set a dependent condition on the template variable by using&nbsp;''Depends on Contract Type Attribute'' (set to ''On'') and&nbsp;its related conditions -&nbsp;''Depends On Attribute&nbsp;''drop-down and&nbsp;''Depends On Value&nbsp;''field.&nbsp;The following conditions decide the dependency between the template variable and contract type attribute:&nbsp;&nbsp;	+	<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>
−	*When&nbsp;''Depends on Contract Type Attribute''&nbsp;is&nbsp;''On'',&nbsp;then it displays the contract type attribute in the&nbsp;''Depends On Attribute''&nbsp;drop-down list.&nbsp;	+	ICI users may need to modify an agreement as per business requirements by adding a clause. The clauses are displayed by “Clause Group” in the clause library by default and then searched by the clause name.&nbsp;
−	*When&nbsp;''Depends on Contract Type Attribute''&nbsp;is&nbsp;''Off'',&nbsp;then it displays the template variable in the&nbsp;''Depends On Attribute''&nbsp;drop-down list.&nbsp;	+
−	For each selected attribute from&nbsp;''Depends On Attribute&nbsp;''drop-down list, the user can then enter the&nbsp;''Depends On''&nbsp;''Value''&nbsp;that will drive the dependency.	+	Multiple filters can now be configured at the template and clause level to help users easily retrieve relevant data. This improves usability for customers having a large number of clauses and templates in their clause and template library.
−	</div> <div class="image-green-border">[[File:7.9 Release Notes 397327.PNG|720px|7.9 Release Notes 397327]]</div> <div class="image-green-border">&nbsp;</div>	+
−	== Enhancements to Artificial Intelligence Apps in ICM ==	+
−	<span style="color:#008000;">'''386571 – Enhancements in AI Apps&nbsp;'''</span>	+	Users can now:
−	With the 7.9 release, the NegotiateAI, ObligationAI, VisualizeAI and DiscoverAI apps have been further enhanced to improve their usability. These apps are available in ICM through a technical configuration.<span style="color:#FF0000;">&nbsp;</span>These apps are available in ICM through a technical configuration.	+	*Filter and search clauses and templates by clause metadata in the clause and template library respectively.
		+	*Filter and search clauses and templates by extended clause metadata in the clause and template library respectively.
		+	*Perform&nbsp;free-text search on the clause and template content.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 36.png|720px|7.15 Release Notes Screenshot 36]]</div>
		+	&nbsp;
−	=== NegotiateAI ===	+	&nbsp;
−	While negotiating a particular clause, the contract negotiator would like to quickly find similar clauses in contracts that have already been executed to be able to make informed decisions. This depends on the rule configuration in ICM based on which the similarity will index the agreements. The similarity of clauses or agreements will be within these agreements. This also applies to the agreement as a whole where the negotiator can refer to historical data from similar agreements.	+	== AI Applications Enhancement&nbsp;Details ==
−	With this release, the following options are provided within the Add-in so that the user can:	+	<span style="color:#800080;">'''727318 – Enhancing AI-powered playbook in Icertis Experience for Word'''</span>
−	*Select a clause/text to find similar clauses from the ICM repository and compare them with the selected one	+	ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document and allows users to review and take corrective actions on them, and assess the risk when negotiators accept these exceptions. &nbsp;
−	*Select similar agreements present in the ICM repository	+
−	*Choose a filter to narrow down the similarity search (for clauses and agreements) within particular type of agreements	+
−	<span style="color:#FF0000;">'''Note:'''</span>	+	The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word.&nbsp;
−	*It is tested and verified on:	+	With this release:
−	**Microsoft Office 2016 or later for Windows (build 16.0.4639.1000 or later (64-bit)).	+
−	**Microsoft Office on Windows (connected to Office 365 subscription) – version 1902 (build 11328.20368) or later.	+
−	**There is no separate installation required for Office .JS.	+
−	*Discovery workflow is supported only for non-ICM third party agreements, but the similarity workflow is supported for both ICM and non-ICM agreements.	+
−	*The supported attribute data types include ''Choice'', ''Currency'', ''Date'', ''Email'', ''Text Area'', ''Number'' and ''String''.	+
−	=== ObligationAI ===	+	*Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page. &nbsp;
		+	*Negotiators now have an option to view playbook details in a separate resizable window as the details of the playbook position for a clause can be lengthy.
		+	*As AI may not be able to find all the playbook positions for a type of a contract, an option has been added to view all playbook positions for a selected type of the contract, with options to search and filter within, so that negotiators have a ready reference for all applicable playbook positions while reviewing the contract.
		+	*Negotiators can view all the applicable playbook positions for a selected agreement clause.&nbsp;
		+	*Negotiators can request approval for a playbook exception from the playbook “Details” page.&nbsp;
		+	*Legal administrators can add a new playbook position for a type of contract or edit the existing playbook position from within Icertis Experience for Word itself.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 37.png|720px|7.15 Release Notes Screenshot 37]]</div>
		+	<br/> &nbsp;
−	Often business is interested in finding certain types of obligations only. Our ML based obligation discovery finds all the obligations available in the document. In this release, we have enhanced ObligationAI to discover only the specific obligations from the agreement document.&nbsp;In this release, we have enhanced the ObligationAI to immediately learn from user actions, which is the most important aspect of ML algorithms.&nbsp;	+	<span style="color:#800080;">'''575475 – Automating user feedback during clause review'''</span>
−	With this release, the user can:	+	ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery recommends values to users, it is expected that users would select the correct value at the time of review. &nbsp;
−	*Choose the type of obligation discovery method to be run for a contract i.e. from a ML based generic discovery model or from a predefined set of obligation templates.	+	During clause review of a discovered clause, AI suggests a list of library clauses to be matched with the discovered clause. If a user selects one of them or selects a completely new clause from the library, the AI algorithm learns from such user actions. These learnings are incorporated in the next discoveries to improve the accuracy of clause recommendations.&nbsp;
−	*Self-train from the ML obligation discovery model based on the actions taken by the user on the discovered obligations, and display higher confidence the next time similar obligations are discovered.	+
−	*This is supported only for third party agreements.	+
−	=== Visualize AI ===	+	<br/> <br/> <span style="color:#800080;">'''539492 – Rearranging discovered clauses'''</span>
−	With this release, we have provided server hooks at the following stages to implement custom visualization:	+	Clauses found using DiscoverAI in an agreement document are displayed with clause categories in the “Clause Discovery” section on the web UI. Sometimes, AI may identify the clause boundaries incorrectly. Users can now review and rearrange boundaries for such clauses on the “Clause Discovery” page. &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 38.png|720px|7.15 Release Notes Screenshot 38]]</div>
		+	In rearrangement mode, users can:&nbsp;
−	*Data fetching (for example, fetching data from external Web services)	+	*Merge multiple discovered clauses into a single clause or split a large discovered clause into multiple clauses.&nbsp;
−	*Data transformation (for example, adding a custom metadata property node)	+	*Identify a section of the discovered clause as its sub-clause.
−	*Data rendering (for example, adding custom nodes in visualization)	+	*Rearrange the clause hierarchy in case of misclassification by AI. Users can change clause hierarchy and identify a clause as a parent or child or peer of another clause(s).
		+	*Change the AI recommended category of a clause. &nbsp;
		+	*Choose to view only the parent clauses.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 39.png|720px|7.15 Release Notes Screenshot 39]]<br/> &nbsp;</div>
		+	<span style="color:#800080;">'''770375 – Infusing attribute discovery in agreement creation workflow'''</span>
−	=== DiscoverAI ===	+	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. Typically, users might have already entered attribute values by the time they trigger/perform the create/publish action, thereby making the attributes discovery process redundant. Also, two different attribute pages had to be maintained, with personalization and validations not being available on the attribute discovery page.&nbsp;
−	'''387056 – Add support for Table discovery&nbsp;'''	+	With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during the agreement creation process. Discovered values will then be auto-filled in empty attributes and users can view additional potential options for the discovered attributes.&nbsp;
−	<div class="image-green-border">	+
−	With this release, the DiscoverAI app has been further enhanced to include Table discovery. Along with clause and metadata, ICM now also extracts tables (including information such as SLAs, price list, etc.) in agreements and displays them on the ''Table Discovery'' tab (on the ''Details'' page).	+	Users can:&nbsp;
		+
		+	*View the progress of the attribute discovery.&nbsp;
		+	*Identify AI discoverable attributes on the “Attributes” page of the agreement creation wizard.
		+	*View the values recommended by AI for discoverable attributes.
		+	*View the agreement document on the “Attributes” page itself, for quick validation of AI recommended values for discoverable attributes as well as attributes values already tagged in the agreement document
		+
		+	'''Note: '''When an attribute discovery is triggered from the “Attributes” page, a two-column attributes layout is converted to a single column layout to accommodate the agreement document view.<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 40.png|7.15 Release Notes Screenshot 40]]</div>
		+	&nbsp;
		+
		+	<span style="color:#800080;">'''727312 – Clause hierarchy discovery in text PDFs'''</span>
		+
		+	In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.
		+
		+	With this release, the clause delineation functionality has been enhanced to support text PDF documents and Word documents that do not use any styles. This enhancement helps to get better clause delineation, eliminates a large number of incorrectly classified clauses, and allows users to review the parent clause and child clause individually.
		+
		+	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 also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in a hierarchical format.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''727314 – A generalized framework to support additional languages in AI apps'''</span>
		+
		+	In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.
		+
		+	With this release, a language framework has been implemented for AI discovery which can support a large number of languages. Using this generalized framework, DiscoverAI, NegotiateAI, and DiscoverAI for legacy apps have been enhanced to support additional European languages – French, Dutch, Norwegian, and Swedish.&nbsp;
		+
		+	Along with the clause and obligation discovery support, AI models would be able to discover attributes too, in all the supported languages.&nbsp;<br/> &nbsp;
−	ICM 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. 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. The table discovery allows you to:	+	== Reports Enhancement Details ==
−	*Identify and discover the table(s) in the agreement document	+	<span style="color:#800080;">'''514593 – Introducing the&nbsp;Tagged Attributes Report'''</span>
−	*Update the data in the discovered table as required	+
−	*Create new instances of the associations for the uploaded agreement	+
−	</div> <div class="image-green-border"><span style="color:#FF0000;">Note: </span>Only the .docx document format is supported.&nbsp;</div> <div class="image-green-border">[[File:7.9 Release Notes 387056.PNG|720px|7.9 Release Notes 387056]]</div>	+
−	== Enhancements to ICM Add-ins ==	+
−	=== Email Outlook Plugin (.JS version) &nbsp; ===	+	With this release, a new “Tagged Attributes Report”, which helps administrators understand the complete profile of an attribute and how it has been tagged across different clauses and templates. This provides them better visibility into attribute usage and saves them considerable time.
−	'''<span style="color:#008000;">334171 – Enhancements in Email Outlook Plugin (.JS version) &nbsp;</span>'''	+	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, Attribute tagged as Clause Extended Attribute and Attribute Display Name.<br/> &nbsp;
−	With this release, a new .JS version of the ICM Outlook plugin has been introduced. The overall turnaround time for authoring is reduced as the user no longer needs to download the documents received over email to the local machine, then switch applications and log on to ICM, search the agreement and then upload the documents.	+	<span style="color:#800080;">'''769602 – Displaying clause extension attribute summary in the Clause Summary Report'''</span>
−	The provisioned user can now:	+	Previously, the “Clause Summary Report” displayed “Clause Summary” and “Clause Version Summary” sections on the report index page.
−	*Upload the next version of the agreement document received over an email to the agreement	+	In this release, the report is being enhanced to display “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 of the clause extension attributes. The “Clause Extension Version Summary” will display the latest values of clause extension attributes.&nbsp;<br/> &nbsp;
−	*Upload the next version of the associated document (supporting attachments) received over an email to the agreement	+
−	*Create a new association instance and then upload the associated document received over an email to the agreement	+
−	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.&nbsp;The Outlook Add-in (.JS version) is supported on 2 different platforms:	+	<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</span>
−	*For MAC OS (Mojave): it is tested and verified on Microsoft Office 365 (2016 and above).	+	ICI administrators can set up subscriptions for different entities, for notifications to be sent to subscribed users at the occurrence of certain events. Notifications can also be sent using the broadcast functionality. 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.&nbsp;
−	*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.	+
		+	The default 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. This report displays a list of notifications sent for an entity, including details such as the event that triggered the notification, the message body, subject, the To, CC, BCC recipient names, and email addresses; along with other details such as the attachment filename or sent date and time.&nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 41.png|720px|7.15 Release Notes Screenshot 41]]</div>
	&nbsp;		&nbsp;
		+	<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>
		+	With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas:&nbsp;
−	=== Scribe – ICM’s Office Add-in plugin&nbsp;(.JS version)&nbsp; ===	+	*Contract type names, if the respective entity has locale resource key values in the database.&nbsp;
		+	*Drop-down with Yes/No values.
		+	*Graph and Time zone tooltips, if present in the report.
		+	*Column headers. &nbsp;
		+	*Any error or validation messages.
		+	*Informative messages such as “No data available”. &nbsp;
−	'''<span style="color:#008000;">Enhancements to ICM Scribe – the new .JS version Office Add-in (Upgraded in 7.8)</span>'''	+	<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>
−	The Office.js based Add-in experience in ICM for MS Office Word 2016 onwards, enables you to have a richer, more secure and centralized web experience of managing ICM functions right inside MS Office Word. It will reference the office.js library, which is a script loader.	+	Previously the "Agreement Status" filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&nbsp;
−	<div class="image-green-border">[[File:7.9 Release Notes Scribe 1.png|860px|7.9 Release Notes Scribe 1]]</div>	+
−	Advantages of Office.js based Add-ins over old add-ins built using VBA, COM, or VSTO include:	+
−	*Cross-platform support: Office Add-ins run in Office on the Web, Windows, Mac, and iPad.	+	This filter is now also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". 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.
−	*Centralized deployment and distribution: Administrators can deploy Office Add-ins centrally and more securely across an organization, with no need of individual desktop client installation.	+
−	*Based on standard Web technology.	+
−	<div class="image-green-border">[[File:7.9 Release Notes Scribe 2.png|7.9 Release Notes Scribe 2]]</div>	+
−	Enhancements were made to the Office.js Add-in to improve:	+
−	*'''Reliability:''' By adding validation for incorrect data, providing a light weight engine, removing redundant information, introducing the retry mechanism, replacing unreliable user controls (such as the ''Attribute pane'',''login button'',''Search'',''Add Team,'' etc.), and introducing the ''Something went wrong'' screen in case of connectivity issues.	+	&nbsp;
−	*'''Usability:''' By restricting the user interface, restricting all entities to 10, sending intuitive messages and warning, increasing real estate, correcting the formatting, reducing user clicks, replacing links with buttons, replacing hidden tabs with ICM product icons, adding tooltips wherever necessary, adding Login, Logout and Home page, adding the Splash screen, adding support for user groups, and adding status indicators.	+
−	*'''Productivity:''' By reducing the waiting and operational time, fixing priority functional issues, introducing manual Refresh button to increase concurrency (for Clause, Template Variables, Lists), restricting older version updates (Template and Clause updates), and handing Header and Footer scenarios in the Template module.	+
−	<div class="image-green-border">[[File:7.9 Release Notes Scribe 3.png|720px|7.9 Release Notes Scribe 3]]</div> <div class="image-green-border">&nbsp;</div>	+
−	== Enhancements to Reports ==	+	<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
−	<span style="color:#008000;">'''275838 – Extended support for user's preferred time zone settings in reports'''</span>	+	The “Cycle Time Report” displays the cycles for contract 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.
−	Previously, all the date related columns and parameters in all ICM reports were displayed in the UTC time zone, in the ''mm/dd/yyyy ''format. ICM allowed users to set the date and time format as per their preferred locale settings.&nbsp;With this release, all reports will display the date and time as per the ''Time Zone'' set by the user in the user preferences.	+	With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.
−	However, the following points need to be noted:	+	&nbsp;
−	*When reports are exported to CSV format, due to the inherent property of the CSVS files, the date and time format of the date columns will be as per the user's local machine format, not as per the user preferences set in ICM.	+	<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>
−	*In all reports, where the parameters to generate the reports have dates (for example, ''Created Start Date ''and&nbsp;''Created End Date'' in the ''Cycle Time Report''), the default value in these fields are displayed in the UTC time zone. However, when the user changes values in these fields and generates the reports, the dates will then be displayed as per the user’s local time.	+
−	<div class="image-green-border">[[File:7.9 Release Notes 275838.PNG|720px|7.9 Release Notes 275838 - 01]]</div>	+
−	If the ''Date Format ''selected in the user’s preferences is ''dd-mmm-yy'', the date value in the field gets converted to the month and vice-versa. As a workaround, the date format in this field has been set as ''mmmm-dd-yyy'', so that the default value is displayed as per the user’s expectations. However, the date format when the report is generated is displayed as per the user’s preferences. For example, if the user selects the ''Date Format'' as ''dd-MMM-yy'' in ''My Preferences'', then the dates displayed in the ''Cycle Time Report'' fields ''Created Start Date ''and ''Created End Date ''are actually set as ''mmmm-dd-yy''.	+
−	<div class="image-green-border">[[File:7.9 Release Notes 275838-2nd.PNG|720px|7.9 Release Notes 275838 - 02]]</div> <div class="image-green-border">&nbsp;</div>	+
−	<span style="color:#008000;">'''385409 – Additional reports added to KPIs&nbsp;'''</span>	+
−	In addition to the reports that are already available on the Dashboard as KPIs (''Agreement Deviation Report, Agreements Pending Approval Report, Agreements Pending Execution Reports, Average Agreement Turn Around Time Report, Clauses Pending Approval Report, Expiring Agreement Report, and Templates Pending Approval Report''), users can now also add the reports shown in the table below. This can be achieved by providing access through ''Security Groups''.	+	With this release, the user creating a PowerBI report can hyperlink "Agreement Code" using conditional formatting with the Web URL option, so that on clicking an agreement code, the user is navigated to the corresponding agreement in ICI.&nbsp;
−	<div class="image-green-border">[[File:7.9 Release Notes 385409.PNG|720px|7.9 Release Notes 385409 - 01]]</div>	+
−	For example, the ''Signature Type Report'' KPI depicts the percentage of electronic signatures in ICM. If the number of electronic signatures is 6 and the number of manual signatures is 83, then the KPI is calculated as 6/83+6 = 6/89 (total number of agreements). Therefore, the percentage of electronic signatures displayed on the KPI tile on the Dashboard is 6 (rounded off to nearest digit).	+
−	<div class="image-green-border">[[File:7.9 Release Notes 385409-2nd.PNG|720px|7.9 Release Notes 385409 - 02]]</div> <div class="image-green-border">&nbsp;</div>	+
−	== Integrations ==	+
−	=== Integration&nbsp;with Collaboration Tools ===	+	&nbsp;
−	<span style="color:#008000;">'''370460 – ICM Bot integration with MS Teams&nbsp;'''</span>	+	== Integration Details ==
−	By integrating the ICM Bot platform with MS Teams, users can collaborate for contract authoring, negotiations, etc. This not only provides a better, seamless user experience, but also helps to discuss ideas, and in turn significantly improve the cycle time.	+	<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
−	Through this integration, we support:	+	Signing agreements is often a combination of manual signatures and electronic signatures. ICI now provides a unified flexible signature workflow to its customers, thus improving the overall turnaround time and reducing the efforts of printing and scanning manually signed documents.
−	*Invoking ICM Bot in the Teams app	+	*Introducing the hybrid signature process allows users to use manual and electronic signature mode in a single transaction.
−	*Querying ''My Pending Tasks'' using the ICM Bot to be able to collaborate with others and take decisions on pending tasks and expedite the contracting process	+
−	*Searching for agreements using ICM Bot so that the user can find the relevant agreements, share their status and make informed decisions	+
−	*Using ICM Bot to get answers to frequently asked questions	+
−	<span style="color:#FF0000;">'''Note:''' </span>Setting up ICM Bot is done through a technical configuration.	+	'''Note: '''If the DocuSign console is enabled, then the user has the provision to tag the signatories after manual signatures.&nbsp;For other signature modes, ICI relies on the provisions facilitated by your signature provider.
		+
		+	*Enabling DocuSign console with ICI that allows users to:
		+	**Add and modify the signatories.
		+	**Change the signature sequence.
		+	**Preview documents in the DocuSign console.
		+	**Tag signatories in the DocuSign console.
		+	**Use Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>
		+
		+	Previously, DocuSign integration provided support for sequential signatures.
		+
		+	This capability has now 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.
		+
		+	Parallel signatories can now be configured using rules or the DocuSign console.<br/> &nbsp;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 42.png|720px|7.15 Release Notes Screenshot 42]]</div>
		+	<br/> <span style="color:#800080;">'''701825– Supporting multiple vendors for electronic signature'''</span>
		+
		+	Previously, ICI supported one signature vendor within one instance of ICI.&nbsp;
		+
		+	Now, users have the flexibility to not only select multiple electronic signature vendors in the same instance but also select the signature provider at the agreement level, based on the business requirements.
		+
		+	Users now have the flexibility to:
		+
		+	*Configure any number of signature providers for a single ICI instance, as per business requirements.
		+	*Select the signature provider of choice, at the agreement or amendment level.
		+	*Define standard rules and conditions to automatically select the signature provider of choice, based on the organizational needs.
		+	*Use multiple accounts of the same signature provider or multiple accounts of different signature providers.
	&nbsp;		&nbsp;
−	=== Icertis Experience for&nbsp;Salesforce ===	+	<span style="color:#800080;">'''751651 – Publishing success/failure notification message on ASB post data sync from Salesforce'''</span>
		+
		+	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 agreement document changes.
		+
		+	With this release:
		+
		+	*Document assembly or notification to third party applications can be triggered by consuming the notification message posted on ASB via custom task implementation. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.
		+	*Upon completion of data sync for an opportunity, the Salesforce data sync task raises a “Data Sync Passed/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for each ICI entity related to the given opportunity. The message posted on ASB will display details such as Opportunity ID, ICI entity SysId and time stamp, among other information.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>
		+
		+	Previously, when changes were made to any Salesforce entity, then the data would sync in all related ICI contracts/requests, irrespective of their state in ICI. For example, contracts in the "Waiting For External Signature" state would not be updated via ICI UI but would get updated via data sync.
		+
		+	With this release:
		+
		+	*Changes made to a record of an entity (for example, “Opportunity”) in Salesforce will not sync to corresponding ICI contracts if they are in “Waiting For External Signature”, “Waiting For Internal Signature” or “Expired” states.&nbsp;
		+	*The data will sync only for tracking attributes if the contract is in the "Executed" state.&nbsp;
		+
		+	These enhancements to the data flow, done for configurability and consistency with the ICI user interface, will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.
		+
		+	<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</span>
		+
		+	An alert mechanism is introduced for monitoring success and failure in Icertis Experience for Salesforce integrations, using ICI/Email notifications, so that end-users get notified about success/failure in data sync.&nbsp;
		+
		+	With this release:
		+
		+	*Customers will get success/failure ICI notification for data sync as well as reverse sync; and if there are any failures/exceptions in the sync process (data/reverse), the system will retry the respective operation, based on the configured retry count.&nbsp;
		+	*Additional logging has been introduced for ICI-Salesforce integration messages. Depending on the message type (success/failure), the Kibana logs will contain correlation ID, status, and JSON details.&nbsp;
		+
		+	<br/> <span style="color:#800080;">'''679797 –&nbsp;Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use'''</span>
		+
		+	Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user IDs and passwords for authentication and authorization of production systems in an enterprise. Security organizations also have stringent security policies which do not approve user Id or password authentication process.&nbsp;
−	<span style="color:#008000;">'''348588 – Configuring field set from Salesforce to ICM using Rest API&nbsp;'''</span>	+	With this release, support is provided for JWT (JSON Web Token) Bearer OAuth, a secure authentication and authorization process. This makes the ICI integration with Salesforce more secure as the actual “Modified By” user from Salesforce is set as “Modified By” user in ICI for the corresponding ICI records during data sync.&nbsp;
−	With this release, a new field called ''Field Set Name ''has been introduced that can be configured using the ''Configuration'' page which is accessible through the managed application available in Salesforce AppExchange. When the integration is triggered from Salesforce, the adapter can read the metadata and send only the attributes defined for the entity field set. If the field set is not defined, the adapter sends all the attributes for that entity.&nbsp;	+	When entities in Salesforce are updated by a user, the process builder sends a message to the 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.&nbsp;
−	<span style="color:#FF0000;">Note: </span>It is necessary to create a new field set for every Salesforce entity. The field set determines the fields that the user can edit in a particular Salesforce entity instead of having to select each field individually. For example, a field set created for an Opportunity can have fields such as ''Opportunity Name, Opportunity ID, etc.''	+	Users have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.
	&nbsp;		&nbsp;
−	<span style="color:#008000;">'''397315 – Mapping between template variable for agreements and SFDC fields'''</span>&nbsp;	+	<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
−	The ICM Salesforce adapter allows mapping of Salesforce entities and their attributes to be integrated with ICM for data flow from Salesforce to ICM (forward sync) as well as ICM to Salesforce (reverse sync). This was previously done using ''Client App Entity Mapping ''on the ''Masterdata Configuration'' page which allows mapping the ICM Attributes from contract types, but not from agreement templates.	+	Previously, reverse data sync flow in MS CRM used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&nbsp;
−	With this release, administrators can now use attributes defined at the template level to store critical external data as part of the agreement and sync with Salesforce, thus avoiding data duplication and redundancy in the process.	+	ICI now uses the client ID and secret key, instead of user ID and password, for the authentication/authorization process between MS CRM 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.&nbsp;
		+
		+	Users will have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.<br/> &nbsp;
		+
		+	== ICI Platform Tools Details ==
		+
		+	'''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''
		+
		+	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 target environments, thus reducing the manual efforts.
		+
		+	The following entities are now supported:
		+
		+	*Organizations (Orgs), Organization Groups (Org Groups)
		+	*Users, User Groups, Security Groups
		+	*Role Action Mapping
		+	*Currencies
		+	*Reasons
		+	*Attribute Group
		+	*SLA Matrix
		+	*Notification Category
		+	*Default Search Columns
		+	*Cascade Team
		+	*Application Settings
		+	*Global/Admin Saved Searches
		+
		+	'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.
	&nbsp;		&nbsp;
−	=== Icertis Experience for&nbsp;Workday ===	+	== Partner Enablement ==
−	<span style="color:#008000;">'''384529 – Executed PDF from ICM to Workday&nbsp;'''</span>	+	<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
−	Customers using Workday ERP application to manage their procure-to-pay process want to have end-to-end integration to Icertis Contract Management (ICM) platform for managing their procurement process.&nbsp;The Icertis platform already supports integration to Workday Financials and HCM via an adapter. As part of this integration, contracts authored in the ICM platform can be sent to Workday via the adapter and attached to Workday contracts in the .docx format.	+	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.&nbsp;
−	Now, with the help of Event based configuration in the adapter, it is possible to send the agreement document in .PDF or .docx format to Workday for a specific event.	+	As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:
		+
		+	*'''ICI Coding Guidelines (version 2):'''&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.
		+
		+	*'''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.
		+
		+	*'''Working with ICI Tasks: '''Updated for the 7.15 release.
		+
		+	*'''Working with ICI Hooks:&nbsp;'''Updated for the 7.15 release.
		+
		+	*'''ICI Developer Library:''' Updated for the 7.15 release.
		+
		+	*'''Local Environment Setup using ICI Binaries:''' Updated for the 7.15 release.
		+
		+	*'''Self-Serve Tools:''''''&nbsp;'''Updated for the 7.15 release.
	&nbsp;		&nbsp;
−	=== Enhancements to Adobe Sign ===	+	== Technical Requirements for Release 7.15 ==
−	<span style="color:#008000;">'''344436 – Support for ''Print, sign and upload'' (wet signed copy) and sync back in ICM&nbsp;'''</span><br/> Adobe Sign provides users the capability of signing documents manually using the ''Print, sign'' and ''upload'' option. However, earlier when the agreement document was wet signed and uploaded, it did not get synced back to ICM, and the agreement would get blocked in that state. With this release, ICM supports syncing back the signed agreement document and changed status, so that the user can proceed with the workflow as expected.<br/> <span style="color:#FF0000;">Note:&nbsp;</span>	+	The Icertis Contract Intelligence (ICI) Proposal Management application can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all environments.&nbsp;
−	*If the ''Wet Signatures Only'' option is selected, then system mandates all the users to sign the agreement document using the ''Print, sign and upload'' option of Adobe Sign.	+	The software and hardware requirements for the client system as well as mobile application are listed in the table below.
−	*If the ''Wet Signatures Only'' option is not selected, then users can either sign it electronically or use the ''Print, sign and upload'' option to sign it manually. However, in this case if any user signs using the ''Print, sign and upload'' option, since all the signature tags will be lost, Adobe Sign will add an additional page to the end of agreement document that will have signature tags for subsequent signatories who are yet to sign.	+
−	*Attribute sync back to ICM will only work for the first signatory. Once Adobe Sign’s ''Print-Sign-Upload'' option is used, attribute tags are not available for subsequent signatories who are yet to sign the document.	+
−	*In&nbsp;the case of parallel signatures, the wet signature option is not applicable. If the''Wet Signature Only ''option is selected, then the agreement will be stuck in the ''Approved'' state.	+
−	<div class="image-green-border">[[File:7.9 Release Notes 344436.PNG|720px|7.9 Release Notes 344436]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border"><span style="color:#008000;">'''430578 – Sending additional supporting documents to Adobe Sign&nbsp;'''</span><br/> The current ''Send for Signature'' functionality only allows users to send the main agreement for signature. It does not allow users to add the supporting documents along with the main agreement document.&nbsp;With this release,&nbsp;ICM will support preview and sending of the associated documents (attachments) along with the main agreement for signature.&nbsp;</div> <div class="image-green-border"><br/> <span style="color:#FF0000;">Note:&nbsp;</span>Only agreement specific tags will be displayed in the agreement document when reviewing and signing it. After the agreement document is signed, only the agreement will be synchronized with ICM again. The associated documents (attachments in the Word or PDF format that are associated to the main agreement) will be available for selection when sending it for signature.</div> <div class="image-green-border">&nbsp;</div>	+
−	== Technical Requirements for Release 7.9 ==	+
−	The Icertis Contract Management base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all the environments and 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.	+	[[File:7.15 Technical Requirements - Operating Systems.PNG|720px|7.15 Technical Requirements - Operating Systems]]
−	[[File:7.9 Release Notes Operating Systems table.PNG|720px|7.9 Release Notes Operating Systems table.PNG]]	+	[[File:7.15 Technical Requirements - Browser Compatability Matrix.PNG|720px|7.15 Technical Requirements - Browser Compatibility Matrix]]
−	[[File:7.9 Release Notes Other Requirements table.PNG|720px|7.9 Release Notes Other Requirements table.PNG]]	+	[[File:7.15 Technical Requirements - Other Requirements.PNG|720px|7.15 Technical Requirements - Other Requirements]]
−	[[File:7.9 Release Notes Special Requirements table.PNG|720px|7.9 Release Notes Special Requirements table.PNG]]	+	[[File:7.15 Technical Requirements - Smartphone Mobile App.PNG|720px|7.15 Technical Requirements - Smartphone Mobile App]]
−	[[File:7.9 Release Notes Special Requirements table 2.PNG|720px|7.9 Release Notes Special Requirements table 2.PNG]]	+	[[File:7.15 Technical Requirements - Special Requirements 1.PNG|720px|7.15 Technical Requirements - Special Requirements 1]]
−	[[File:7.9 Release Notes Microsoft Office table.PNG|720px|7.9 Release Notes Microsoft Office table.PNG]]	+	[[File:7.15 Technical Requirements - Special Requirements 2.PNG|720px|7.15 Technical Requirements - Special Requirements 2]]
		+
		+	[[File:7.15 Technical Requirements - Special Requirements 3.PNG|720px|7.15 Technical Requirements - Special Requirements 3]]
		+
		+	[[File:7.15 Technical Requirements - MS Office Plugins 1.PNG|720px|7.15 Technical Requirements - MS Office Plugins 1]]
		+
		+	[[File:7.15 Technical Requirements - MS Office Plugins 2.PNG|720px|7.15 Technical Requirements - MS Office Plugins 2]]
		+
		+	[[File:7.15 Technical Requirements - Security.PNG|720px|7.15 Technical Requirements - Security]]
		+
		+	&nbsp;
		+
		+	== Known Issues ==
		+
		+	This section includes some issues that we are aware of and plan to resolve at the earliest:
		+
		+	[[File:Known Issues.PNG|720px|7.15 Known Issues]]
		+
		+	&nbsp;
		+
		+	&nbsp;
−	[[File:7.9 Release Notes Microsoft Office table 2.PNG|720px|7.9 Release Notes Microsoft Office table 2.PNG]]	+	'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&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]]&nbsp;|

---

Latest revision as of 05:14, 27 January 2021

ICI Release Notes - Release 7.15

List of Enhancements 7.15

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.

The key enhancements of this release include:

• Enhancements to the ICI Application
  • User Experience
    • To ensure that the agreement document is generated with the correct clauses and metadata, we now can preview an agreement from the pre-draft stage to the Approved stage, enabling a comprehensive review before publishing the contract. 
    • Improved usability for the global user base and their individual UI language preferences via expanded localization coverage which now includes support for localized “Reason Codes”.
    • Friction-free collaboration enabled via the Collaboration Portal’s external user interface which now enables external users to search contract requests, agreements, associations and masterdata records. 
    • Improved document review process where the display order for clauses in the ICI web and in Icertis Experience for Word match the order in which the clauses are configured in the respective template and generated agreement.    
    • Improved usability whereby the attribute multi-selection interface, when creating an agreement, can be configured as either radio buttons or checkboxes to tailor the agreement creation experience per the contract type. 
    • Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export. 
    • Improved usability where the sequence of values displayed in a masterdata lookup drop-down can now be configured to have the most frequently accessed values available at the top of the list. 
       

• Workflow Enhancements
  • Greatly improved system availability during Publish operations where now only the contract types being published are not available during this system operation as opposed to the whole system being unavailable.
  • Improved usability including the ability to create instances of associations as part of the agreement creation wizard itself.
  • To continue bringing Extension Attributes capabilities at par with regular attributes, these are now quickly viewable for easy reference in the agreement entity’s “Agreement Clauses” tab.
  • Agreements can be Approved or Rejected from within an agreement notification email itself making it faster to take actions on an agreement and reducing turnaround time for approval cycles. 
  • Expanded contract request experience now includes the ability to request Contract Terminations.
  • Bulk actions support now extended to Terminating agreements in bulk to support situations that require it, such as regulatory changes, or business partner insolvency.  
  • To save time when re-instantiating a terminated agreement, due to reasons such as reviving a business relationship, you can now do so by simply adding amendments to the terminated agreement rather than by having to create a new agreement from scratch.
  • Simplified administration of the first run default user preference which can now be pre-set or updated for users based on their location or department.
  • Simplified signature status labels of “External”, “Internal,” and “Fully Signed” are shown in agreement versions.
  • Enhanced flexibility when executing a large volume of contracts by not requiring the immediate upload of documents to change the status to “Executed”. Instead, the agreement status will change from “Waiting For Signature” to “Executed – Document Upload Pending”.
  • Enabling sharing of Associated Documents as well via the email notifications that are triggered for an agreement.
  • For organizational changes or employee turnover, we now provide a data management interface that enables replacing users with multiple users on supported agreement entities.
  • Support for granularly defining which agreement attributes for a given contract type should be cascaded to the agreement’s amendments via the “Is Inherit On Amendments” flag at the agreement contract type and template variable level.
  • In addition to the currently available functionality of all attributes to be superseded capability, we now offer the ability to selectively supersede an attribute through rules. 
  • Conditional attributes’ comparison operators now support multiple complex conditions to dynamically display attributes based on a range of business scenarios.
  • Simplifying agreement workflow navigation by enabling the option to show a “No Team Available” message during workflows when a team is not needed.
  • Expanded support for special characters in the Attribute display name for contract requests, agreements, associations and masterdata.
  • Selectively download amendments with the corresponding parent and child associations in a zip package with corresponding sub-folders. 
  • Larger file size support when uploading (4GB) and downloading (6GB) larger files for masterdata and associations. 
  • Boost smart filter creation using string operators such as “Contains”, “Starts With”, “Does Not Contain” for the “Business Status” search facet.
  • Expanded support for automating the bulk upload of clauses and templates reducing the dependency on manual approvals and delays in onboarding clauses and templates.
  • Enhanced configurable labels for peer associations that define the contractual relationship. (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).

 

• Mobile App Updates
  • Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users.

 

• Enhancements to ICI API 2.0
  • Improving the filtering and searching capability which now supports searching text inside clauses or templates to allow more powerful deep searches especially when searching across large libraries. 
  • Improved labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
  • Defining and updating clause groups as per business requirements for easy categorization and management. 

 

• Enhancements to ICI Add-ins
  • Icertis Experience for Word
    • Improving the filtering and searching capability with support for searching text inside clauses or templates to allow more powerful search especially when searching across large libraries. 
    • Improving labeling of internal, external, and fully signed copies of agreements for easy identification of an agreement version.
    • Defining and updating clause groups as per business requirements for easy categorization and management. 

 

• Enhancements to Artificial Intelligence Applications
  • Multiple enhancements to the AI-powered legal playbook capabilities:
    • Improved usability by enabling larger window views of the “Details” page and also including deviations. 
    • All the playbook positions for a contract type now have the option to search and filter. 
    • Administrators can create a new playbook record or update the existing one from within Icertis Experience for Word itself.
  • Improving the clause delineation logic so that users can rearrange the AI identified clause boundaries. You can now merge or split discovered clauses or selected text in a clause and also create sub-clauses within the discovered clause.
  • Extending the clause hierarchy discovery feature to support text PDFs in addition to .docx documents. 
  • Improving library clause recommendations for discovered clause based on learnings from user’s action in previous discoveries. 
  • Providing support for additional languages including “French”, “Dutch”, “Norwegian” and “Swedish” in AI apps.
  • Enabling users to flexibly leverage AI on-demand by manually triggering attribute discovery on an agreement from the “Attributes” page to accelerate workflows. Discovered values will be auto-filled in empty attributes, instead of redundant manual entry.
  • Enhancing and optimizing the performance of Machine Learning services to simplify deployment and run the workload on-demand while significantly reducing infrastructure management needs.

 

• Enhancements to Reports
  • Introducing the “Tagged Attributes Report” enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates. This will help the Legal/admin users to assess the impact of configuration changes to the clauses and templates. 
  • Introducing the “Notifications History Report” for an entity, enabling users to track what notifications were sent to which recipient and when. This provides better visibility and compliance for the users.
  • Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement Status”.
  • Enhancing the “Clause Summary Report” to display information on Extended Clause Attributes as well.
  • Adding an “Organization Unit” filter in the “Cycle Time Report” to enable deeper analysis.  
  • Adding a new column in PowerBI for “Agreement Code” which navigates the user to the agreement in ICI.
  • Multiple localization enhancements within reports.

 

• Improving the Icertis Experience
  • Signature Workflow
    • Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid (manual and/or electronic) 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).
    • Enabling the ICI platform to support more than one E-signature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.
    • Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. 
       
  • Icertis Experience for Salesforce
    • Providing the ability to send success and failure alerts for improved monitoring of messages.
    • Triggering document assembly for automatic data sync and displaying completion notification.
    • Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.
       
  • Icertis Experience for MS CRM
    • Providing server-to-server OAuth support, so that the adapter and the task service will use ‘client Id’ and ‘secret key’ from AKV, invoking the MS CRM APIs.

 

• Enhancements to Platform Tools
  • Enhancing ICI to allow administrators to promote additional configurable entities from pre-production to target environments. These include organizations and organization groups, users and user groups, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings, global and admin saved searches.

 

• Additions to Icertis Software Development Kit for Partner Enablement
  • 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.

These release notes provide an overview of the enhancements to ICI, the mobile app, the ICI experience for integrations, and so on.

 

ICI Application Enhancement Details

514613 – Introducing the ability to preview agreements before publishing

Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.

With this release, a preview functionality is being introduced, so that the primary owner or contract creator 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. The preview document would also include tagged associated documents, coming through inline or inheritance associations.

A preview section is available on the “Verify” stage of agreement/amendment creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. The preview is available till the Approved state of the agreement/amendment.

Note: This functionality is configurable. It is not available by default and can be enabled or disabled for chosen contract types.

 

575640 – Creating associations on the create or edit wizard of agreement

Previously in ICI, contract authors had to create associations for agreements after the agreement is already created. 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 the business, and some associations are required to be created along with the agreement.

Hence, the ability to create association instances as part of agreement creation or update wizard is being introduced in this release. A separate page is displayed, when creating or updating the agreement or amendment, for the user to create, view, or delete inline associations. The user also has an option to select the columns and their order in the association grid. 

Adapting existing products to new markets through translation and localization is the key to global growth. The localized versions of the product improve the overall user experience and help to better connect with new and potential global customers.

Users can see localized reason codes as per their preferred language settings. 

The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.

 

614944 – Initiating termination for parent agreement from the contract request

In ICI, users create and execute a termination agreement on the main agreement instance to terminate an agreement. ICI has now extended this capability to initiate the termination from contract requests too. 

Users can now enable the termination process at the contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for the 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. The access privileges for the contract requests termination process is controlled through role action mapping.

 

506398 – Enabling search for external users with login privileges

ICI’s collaboration portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself. 

In our continuous effort to improve usability, a search option has been introduced on contract requests, agreements, associations, and masterdata index pages, so that external users can easily search records. The attributes displayed as columns of the search grid are included as facets in the filter options to perform a more refined search.

 

514605 – Supporting extended clause attributes in agreements

In ICI, users can capture additional details for a clause in extension attributes. With this release, users can view these clause extension attributes on the agreement entity for easy reference while working with agreements. 

Users can now: 

• Select and save extension attributes to display in the grid view, via the “Default Search” column functionality.
• View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.
• View the hyperlink “Show Clause Information”, which displays all clause extension attributes along with clause attributes, in the same window.

 

514615 – Streamlining the approval process over emails

The approval process has now been streamlined by allowing approvers to directly approve or reject an agreement from within the email itself, through a hyperlink to the webpage, instead of logging in to the system to do so. External users, who do not have access to ICI can now review or approve the documents from the notification email, instead of sending offline copies to do so and then uploading them to ICI. This reduces the overall turnaround time and increases productivity. 

The internal users are authenticated through the SSO/IDP before opening the page where the actions are to be taken. The external users are authenticated by sending them a code in the email, which has limited validity. 

With this release:

• Administrators can add tag an Approve/Reject link in the notification template.
• Approvers/reviewers can download the agreement, modify it and upload it back to ICI based on the access provided.
• Approvers can approve/reject the agreement or amendment from the email, only if the task approval or review is assigned to them. Based on the access, the user can approve or reject the agreement by entering notes or reasons for rejection respectively.

 

514643 – Ordering of clauses as tagged in an agreement

To improve the user experience, clauses are now displayed in the same order in the agreement document as they are tagged inside the agreement, on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.

 

617385 – Ability to define additional clause group under clause entity

Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.

With this release, this capability has been further enhanced so that the configurator can configure various clause group names in ICI. These clause groups can be categorized or grouped as per business requirements for better identification and negotiations during the contract workflow.

Administrators can now:

• Define and update clause groups.
• Edit, delete, activate or deactivate clause group entities.
• View additionally added clause group values in the clause entity when creating or editing a clause.
• Search agreement records or clauses on the index page on clause group attributes with added values.
   

514621 – Reviving terminated agreements

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

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. The system sets an identifier attribute "Is Termination Revived" for such revived base agreements, and users can use them in search filters, notification rules while configuring saved searches, and so on.

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. 

514625 – Terminating agreements in bulk

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 the termination of agreements in bulk, thereby saving the time to terminate agreements one by one and reducing manual errors.

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. 

Users can now: 

• Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch.  
• Generate and view a status report for agreements terminated in bulk. 
• Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk action.

Note: All prerequisite configurations applicable for the termination workflow should also be set for the bulk termination process.
 

555898 – Defining display sequence on lookup attributes at the contract type level

Previously in ICI, users could not define the display order for lookup attribute values in a drop-down on the UI that references masterdata. Users had to scroll through all the populated values to find the desired values during agreement creation.  

Configurators can now define and maintain the display sequence for selected masterdata records, starting from 1 to n, at the contract type level, using a seeded display sequence attribute. The values will thus be displayed at the top for easier and faster selection in lookup attributes.  

This display sequence setting is supported on the create, edit, and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause entities, and template variables. The display will follow the default alphabetical order if the display sequence is not configured in masterdata. 
 

 

558605 – Viewing amendments in grid view on the agreement details page

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. 

ICI now allows users to view amendments in the “Grid” view, and toggle between grid view or 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.

 

561410 – Enhancing the multi-select drop-down 

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. 

Users can now: 

• View eight options in a drop-down list (instead of six), without scrolling. 
• View larger values with adjusted drop-down width, according to its size, in the post-selection view. 
• View all selected values at the top of the drop-down.
• Deselect the selected values, individually or all with a single click, without opening the drop-down.
   

 

620411 – Defining IN operator when applying lookup filters

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. 

With this release, ICI provides the ability to configure a lookup attribute using the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute. 

Configurators can now: 

• Use the "IN” operator in the lookup filter attribute on agreement contract types. 
• View the applied filter on the “Attributes” page on the UI for the selected attribute. 
• Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute.  
   

 

573339 – Managing user preferences as part of profile management

Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on. 

ICI now provides administrators the capability to set preferences as default, for users, according to their locations or the offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after the first log-in and presents the system with appropriate and specific pre-settings.   

Administrators can: 

• Set and manage preferences for a single user through a single user update, and for multiple users through the bulk process.
• View preference settings modifications details in the “History” tab for audit. 
• Search users based on parameters related to preference settings.

Users can: 

• Access the ICI system with appropriate details as default after the first login. 
• Override the default preference settings as per individual preferences.

 

604775 – Moving agreement to executed state without uploading the document

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. 

With this release, users can now skip uploading the document, to move agreements from “Waiting For External Signature” or “Waiting For Internal Signature” to the “Executed - (Pending Signed Document)” 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. 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. 

This functionality is available for agreements, amendments, and orphan amendments.
 

614860 – Attaching associated documents to agreement notifications

ICI users can share the main agreement document as part of various email notifications that get triggered for the agreement from time to time. 

In addition to the main agreement document, users can now also send associated documents as part of various email notifications that get triggered for the agreement from time to time. Access to these documents can be controlled based on the type of document – internal, external, or restricted. For example, some documents may only be shared with internal users, some may be shared with internal and external users, whereas some may not be shared with anyone.

With this release:

• Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements, and amendments.
• Users can define:
  • The type of notification as internal or external. 
  • The type of associated document instance as internal, external, or restricted.
• Based on the type of notification and type of tagged associated documents, attachments are added to the email notification.
   

586492 – Defining different relationship types while associating peer instance

ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.

With this release, users can define configurable labels for peer associations between existing contracts by configuring the “Linkage Type” masterdata. The configurable 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. The labels can be activated or deactivated as per business requirements.

The configurable labels support the existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as a peer, with default peer linkage type label, defined in default peer mapping for amendment. 

Users can select configurable peer linkage type labels in the “Linkage Type” drop-down list and view them on various ICI functionalities such as:  

• Agreement creation workflows for peer entities, assignment, and initiate termination flow. 
• Associate and Inheritance icons.
• Bulk actions.
• Agreement creation through business APIs.
• Broadcast – “Attachments” tab and captured notes.

Note: Multiple configurable labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.

 

619558 – Downloading amendments using download all functionality

ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements. 

With this release, users will download amendments of an agreement with corresponding parent-child associations in the downloaded zip package. This is supported on the selective download option too.

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.

 

615291 – Configuring attributes inheritance for amendments at the contract type level

ICI already provided the capability to exclude specific agreement attributes from being copied to amendments through technical configuration, which applied to all agreement contract types by default. 

ICI now provides the flexibility to decide which attributes of an agreement can be copied to amendments at the contract type level, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using the “Is Inherit On Amendments” flag, at the agreement contract type and template variable levels. Users can then copy these defined attribute values from base agreement to amendment during amendment creation. 

Note: 

• 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.
• The existing validations or dependencies for an attribute’s properties set for the agreement will not be inherited to amendments.
   

614877 – Replacing a user with multiple users

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. 

Administrators can now: 

• Replace the user with one or more users, by selecting the entity and all/selective instances of that entity, and create a saved search for records to replace users.  
• Validate the replaced user role against the assigned role. 
• Get a notification on adding or completing a task. 
   

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 to carry out these user management actions.

 

614963 – Superseding agreement values as per amendment using rules

In ICI, users could supersede all attributes of a parent agreement configured as ‘supersedable’ with values from its amendment, either manually using the “Supersede” action or automatically through the auto-supersede task. Users can now selectively supersede individual entities based on business conditions.

The administrator can control the supersede functionality for agreements by:

• Enabling auto supersede option at the contract type level.
• Configuring the “Supersede Rule” with “Is Supersede by Amendments” or “Is Supersede by Termination” options. 
• Selecting attributes in rule actions based on the selected Supersede On option. 

Users can view the attribute’s supersede value on the agreement and the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing ICI behavior.

 

615293 – Showing or hiding the No Team Available message

In ICI, users may encounter specific workflow configurations, such as the self-approval process, that do not require users added to the team. The “No Team Available” message, displayed in such cases, adds to the number of non-value clicks for users to continue. 

ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks. 

Administrators can: 

• Selectively enable or disable the “No Team Available” message window, at the entity contract type level, appearing at various states. 
• Disable the “No Team Available” message window altogether, at the instance level, for all entities. The instance level settings will override the entity level settings. 

Note: This capability is available across ICI for all entities, events, integrations and add-ins in ICI.

 

618345 – Defining complex conditional logic for attributes visibility

Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator. 

With this release, configurators can now set multiple, complex conditions to display ICI Web UI attributes 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 values in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality.  

Users can now: 

• 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. 
• Support conditional expressions for extension attributes.  
• Define conditions with different operators based on the selected attribute datatype. 
• View the conditional attribute value according to the value entered in the attribute on which a condition is set.

 

616901 – Applying facets to business status search filter

Business statuses are prominently used across all customers as they reflect the actual status in business terms compared to the system workflow status. 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 the case of several business statuses. 

To provide a better user experience and ease of use, faceted filters using string operators, such as “Contains”, “Exactly”, “Starts With” and “Does Not Contain” are being added to the “Business Status” filters.
 

 

694211 – Improving handling of exceptions for string combinations

Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions. 

ICI's parsing logic is now improved for handling string combinations with special and alphanumeric characters so that no errors are generated. This applies to all entities across ICI, where a combination of special characters, alphabets, and numbers can be used.
 

732929 – Uploading clauses and templates in bulk

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. 

With this release, automation has been provided for bulk import using the “Legacy Upload” tool, 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.

Along with the tool, an XML specification document is also released which can be used for creating tags in the input document files of clauses and templates.
 

655507 – Uploading and downloading large files with the file path attribute

ICI now provides support for larger files. This is applicable to masterdata and associations.

Users can now:

• Upload files up to 4GB under the file selection attribute. 
• Upload files with all supported file extensions allowed in the file selection attribute.
• Download All/Download Package up to 6 GB.

ICI supports virus scanning of large files if the virus scan feature is enabled.
 

Note: 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. The Upload/Download of the files would be supported for Azure and Windows Storage.

 

618994 – Supporting special characters in agreement templates and support to skip empty columns while a saved search/association is tagged in a template

Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space. 

Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash), : (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (period) 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.

In scenarios where the association or saved search is tagged as a table in the agreement, and a particular column of the table does not have any data, we have introduced a functionality to skip such empty columns. 

During template creation from Icertis Experience for Word, the configurator can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table. This property needs to be added manually in the “Content Control Properties”, at any position after the contract type GUID, separated by a '|' (pipe separator). This enables empty columns to be skipped in document assembly, thereby eliminating unnecessary empty columns in the agreement version. The order of the columns in the table is determined by the attributes in the display preference of the associated document contract type. 

Amendments to an agreement are now viewable in a grid-view in addition to the current tile view. This provides more information and enables standard grid view functionalities such as search, filter, and export. 

 

573336 – Displaying drop-downs as radio buttons or checkbox list for user selection

With this release, ICI provides new controls for multi-select and single-select choice attributes. 

Users can configure an alternate UI control for drop-downs with a 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.   

Users can select: 

• The radio button for single-select choice attributes. 
• The checkbox list for multi-select choice attributes.

The configuration applies across ICI for the creation and editing of agreement, amendment, associated document, masterdata, and contract request entities.

 

593421 – Labeling agreement document versions as per signature copy

While agreements go through various signature states till executed, users can now navigate to the “Versions” tab and easily identify which version of the agreement is internally signed, externally signed, or fully signed.

 

872309 – Providing flexibility for assembling associations tagged as clauses

In ICI, on publishing and updating actions, all clauses are evaluated, assembled and changes are reflected in the agreement document. However, if associations are tagged in clauses, on “Assemble Contract” and “Send For Approval” actions, clauses do not get assembled and associations do not get populated in the agreement document.

As part of our continuous effort to provide flexibility to ICI users and improve the user experience, a key “Core.Agreement.EnableDynamicClauseAssemblyPostCreate” has been introduced. 

• If the key is enabled, when an associated document is uploaded, the entire document will be automatically assembled (Clause, Attribute, Associations, Saved Search) on the “Assemble Contract” and “Send For Approval” actions.
• If the key is not enabled, the ICI document will be assembled on “Publish” and “Edit Agreement” actions. Only associations will be assembled on the “Assemble Contract” and “Send For Approval” actions.

Note: By default, the key is set to false.
 

Mobile App Enhancement Details

773907 – Refreshing tasks and commitments

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 on the mobile app. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to refresh on these actions and improve usability automatically.
 

850259 – Updating logo and ICM to new guidelines

As part of our new branding, “ICM” has been updated to “ICI”, and the new logo has also been added to the mobile app.
 

773923 – Changing compatibility in Android 11

Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.

 

773917 – Deprecating the UI WebView component for iOS

With this release, the UI WebView component for iOS has been deprecated.
 

ICI API Enhancement Details 

 

ICI Add-ins Enhancement Details

668859 – Enhancing filtering and searching of clauses  

ICI users may need to modify an agreement as per business requirements by adding a clause. The clauses are displayed by “Clause Group” in the clause library by default and then searched by the clause name. 

Multiple filters can now be configured at the template and clause level to help users easily retrieve relevant data. This improves usability for customers having a large number of clauses and templates in their clause and template library.

Users can now:

• Filter and search clauses and templates by clause metadata in the clause and template library respectively.
• Filter and search clauses and templates by extended clause metadata in the clause and template library respectively.
• Perform free-text search on the clause and template content.

 

 

AI Applications Enhancement Details

727318 – Enhancing AI-powered playbook in Icertis Experience for Word

ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document and allows users to review and take corrective actions on them, and assess the risk when negotiators accept these exceptions.  

The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word. 

With this release:

• Negotiators can easily review the playbook exceptions found in deviated agreement clauses on the “Agreement Clause” page.  
• Negotiators now have an option to view playbook details in a separate resizable window as the details of the playbook position for a clause can be lengthy.
• As AI may not be able to find all the playbook positions for a type of a contract, an option has been added to view all playbook positions for a selected type of the contract, with options to search and filter within, so that negotiators have a ready reference for all applicable playbook positions while reviewing the contract.
• Negotiators can view all the applicable playbook positions for a selected agreement clause. 
• Negotiators can request approval for a playbook exception from the playbook “Details” page. 
• Legal administrators can add a new playbook position for a type of contract or edit the existing playbook position from within Icertis Experience for Word itself.

 

575475 – Automating user feedback during clause review

ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery recommends values to users, it is expected that users would select the correct value at the time of review.  

During clause review of a discovered clause, AI suggests a list of library clauses to be matched with the discovered clause. If a user selects one of them or selects a completely new clause from the library, the AI algorithm learns from such user actions. These learnings are incorporated in the next discoveries to improve the accuracy of clause recommendations. 

539492 – Rearranging discovered clauses

Clauses found using DiscoverAI in an agreement document are displayed with clause categories in the “Clause Discovery” section on the web UI. Sometimes, AI may identify the clause boundaries incorrectly. Users can now review and rearrange boundaries for such clauses on the “Clause Discovery” page.  

In rearrangement mode, users can: 

• Merge multiple discovered clauses into a single clause or split a large discovered clause into multiple clauses. 
• Identify a section of the discovered clause as its sub-clause.
• Rearrange the clause hierarchy in case of misclassification by AI. Users can change clause hierarchy and identify a clause as a parent or child or peer of another clause(s).
• Change the AI recommended category of a clause.  
• Choose to view only the parent clauses.

770375 – Infusing attribute discovery in agreement creation workflow

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. Typically, users might have already entered attribute values by the time they trigger/perform the create/publish action, thereby making the attributes discovery process redundant. Also, two different attribute pages had to be maintained, with personalization and validations not being available on the attribute discovery page. 

With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during the agreement creation process. Discovered values will then be auto-filled in empty attributes and users can view additional potential options for the discovered attributes. 

Users can: 

• View the progress of the attribute discovery. 
• Identify AI discoverable attributes on the “Attributes” page of the agreement creation wizard.
• View the values recommended by AI for discoverable attributes.
• View the agreement document on the “Attributes” page itself, for quick validation of AI recommended values for discoverable attributes as well as attributes values already tagged in the agreement document

Note: When an attribute discovery is triggered from the “Attributes” page, a two-column attributes layout is converted to a single column layout to accommodate the agreement document view.
 

 

727312 – Clause hierarchy discovery in text PDFs

In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.

With this release, the clause delineation functionality has been enhanced to support text PDF documents and Word documents that do not use any styles. This enhancement helps to get better clause delineation, eliminates a large number of incorrectly classified clauses, and allows users to review the parent clause and child clause individually.

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 also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in a hierarchical format.
 

727314 – A generalized framework to support additional languages in AI apps

In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.

With this release, a language framework has been implemented for AI discovery which can support a large number of languages. Using this generalized framework, DiscoverAI, NegotiateAI, and DiscoverAI for legacy apps have been enhanced to support additional European languages – French, Dutch, Norwegian, and Swedish. 

Along with the clause and obligation discovery support, AI models would be able to discover attributes too, in all the supported languages. 
 

Reports Enhancement Details

514593 – Introducing the Tagged Attributes Report

With this release, a new “Tagged Attributes Report”, which helps administrators understand the complete profile of an attribute and how it has been tagged across different clauses and templates. This provides them better visibility into attribute usage and saves them considerable time.

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, Attribute tagged as Clause Extended Attribute and Attribute Display Name.
 

769602 – Displaying clause extension attribute summary in the Clause Summary Report

Previously, the “Clause Summary Report” displayed “Clause Summary” and “Clause Version Summary” sections on the report index page.

In this release, the report is being enhanced to display “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 of the clause extension attributes. The “Clause Extension Version Summary” will display the latest values of clause extension attributes. 
 

514611 – Introducing the Notifications History Report

ICI administrators can set up subscriptions for different entities, for notifications to be sent to subscribed users at the occurrence of certain events. Notifications can also be sent using the broadcast functionality. 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. 

The default 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. This report displays a list of notifications sent for an entity, including details such as the event that triggered the notification, the message body, subject, the To, CC, BCC recipient names, and email addresses; along with other details such as the attachment filename or sent date and time. 

 

742607 – Providing additional localization support in reports

With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas: 

• Contract type names, if the respective entity has locale resource key values in the database. 
• Drop-down with Yes/No values.
• Graph and Time zone tooltips, if present in the report.
• Column headers.  
• Any error or validation messages.
• Informative messages such as “No data available”.  

583297 – Filtering additional reports by agreement status

Previously the "Agreement Status" filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”. 

This filter is now also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". 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.

 

746607 – Enhancing the Cycle Time Report

The “Cycle Time Report” displays the cycles for contract 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.

With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.

 

737196 – Adding hyperlink in PowerBI for agreement code

With this release, the user creating a PowerBI report can hyperlink "Agreement Code" using conditional formatting with the Web URL option, so that on clicking an agreement code, the user is navigated to the corresponding agreement in ICI. 

 

Integration Details

605434 – Providing a unified flexible signature process

Signing agreements is often a combination of manual signatures and electronic signatures. ICI now provides a unified flexible signature workflow to its customers, thus improving the overall turnaround time and reducing the efforts of printing and scanning manually signed documents.

• Introducing the hybrid signature process allows users to use manual and electronic signature mode in a single transaction.

Note: If the DocuSign console is enabled, then the user has the provision to tag the signatories after manual signatures. For other signature modes, ICI relies on the provisions facilitated by your signature provider.

• Enabling DocuSign console with ICI that allows users to:
  • Add and modify the signatories.
  • Change the signature sequence.
  • Preview documents in the DocuSign console.
  • Tag signatories in the DocuSign console.
  • Use Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign.
     

641289 – Allowing parallel signatures using DocuSign

Previously, DocuSign integration provided support for sequential signatures.

This capability has now 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.

Parallel signatories can now be configured using rules or the DocuSign console.
 

701825– Supporting multiple vendors for electronic signature

Previously, ICI supported one signature vendor within one instance of ICI. 

Now, users have the flexibility to not only select multiple electronic signature vendors in the same instance but also select the signature provider at the agreement level, based on the business requirements.

Users now have the flexibility to:

• Configure any number of signature providers for a single ICI instance, as per business requirements.
• Select the signature provider of choice, at the agreement or amendment level.
• Define standard rules and conditions to automatically select the signature provider of choice, based on the organizational needs.
• Use multiple accounts of the same signature provider or multiple accounts of different signature providers.

 

751651 – Publishing success/failure notification message on ASB post data sync from Salesforce

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 agreement document changes.

With this release:

• Document assembly or notification to third party applications can be triggered by consuming the notification message posted on ASB via custom task implementation. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.
• Upon completion of data sync for an opportunity, the Salesforce data sync task raises a “Data Sync Passed/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for each ICI entity related to the given opportunity. The message posted on ASB will display details such as Opportunity ID, ICI entity SysId and time stamp, among other information.
   

796155 – Enhancements to the data flow between Salesforce/MS CRM and ICI

Previously, when changes were made to any Salesforce entity, then the data would sync in all related ICI contracts/requests, irrespective of their state in ICI. For example, contracts in the "Waiting For External Signature" state would not be updated via ICI UI but would get updated via data sync.

With this release:

• Changes made to a record of an entity (for example, “Opportunity”) in Salesforce will not sync to corresponding ICI contracts if they are in “Waiting For External Signature”, “Waiting For Internal Signature” or “Expired” states. 
• The data will sync only for tracking attributes if the contract is in the "Executed" state. 

These enhancements to the data flow, done for configurability and consistency with the ICI user interface, will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.

674469 – Generating ICI notifications and enhancing Salesforce data sync

An alert mechanism is introduced for monitoring success and failure in Icertis Experience for Salesforce integrations, using ICI/Email notifications, so that end-users get notified about success/failure in data sync. 

With this release:

• Customers will get success/failure ICI notification for data sync as well as reverse sync; and if there are any failures/exceptions in the sync process (data/reverse), the system will retry the respective operation, based on the configured retry count. 
• Additional logging has been introduced for ICI-Salesforce integration messages. Depending on the message type (success/failure), the Kibana logs will contain correlation ID, status, and JSON details. 

679797 – Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use

Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user IDs and passwords for authentication and authorization of production systems in an enterprise. Security organizations also have stringent security policies which do not approve user Id or password authentication process. 

With this release, support is provided for JWT (JSON Web Token) Bearer OAuth, a secure authentication and authorization process. This makes the ICI integration with Salesforce more secure as the actual “Modified By” user from Salesforce is set as “Modified By” user in ICI for the corresponding ICI records during data sync. 

When entities in Salesforce are updated by a user, the process builder sends a message to the 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. 

Users have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.

 

749083 – Supporting OAuth in the MS CRM adapter

Previously, reverse data sync flow in MS CRM used service user login credentials to invoke MS CRM APIs when data was updated in ICI. 

ICI now uses the client ID and secret key, instead of user ID and password, for the authentication/authorization process between MS CRM 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. 

Users will have the option to choose the authentication mechanism to be used. The system will provide support for backward compatibility of the old username and password flow.
 

ICI Platform Tools Details

514636 – Enhancing P2P Tool in ICI Admin user interface

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 target environments, thus reducing the manual efforts.

The following entities are now supported:

• Organizations (Orgs), Organization Groups (Org Groups)
• Users, User Groups, Security Groups
• Role Action Mapping
• Currencies
• Reasons
• Attribute Group
• SLA Matrix
• Notification Category
• Default Search Columns
• Cascade Team
• Application Settings
• Global/Admin Saved Searches

Note: Customers using ICI versions before 7.15 will need to upgrade to use this feature.

 

Partner Enablement

703386 – Icertis Software Development Kit for Partner Enablement

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. 

As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:

• ICI Coding Guidelines (version 2): This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.

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

• Working with ICI Tasks: Updated for the 7.15 release.

• Working with ICI Hooks: Updated for the 7.15 release.

• ICI Developer Library: Updated for the 7.15 release.

• Local Environment Setup using ICI Binaries: Updated for the 7.15 release.

• 'Self-Serve Tools:' Updated for the 7.15 release.

 

Technical Requirements for Release 7.15

The Icertis Contract Intelligence (ICI) Proposal Management application can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available in all environments. 

The software and hardware requirements for the client system as well as mobile application are listed in the table below.

 

Known Issues

This section includes some issues that we are aware of and plan to resolve at the earliest:

 

 

Related Topics: Agreement Management | Association Management | Compliance Management | Template Management | Clause Management | Configuration | Reports | Advanced Analytics | User Administration | ICI Tools |  Icertis Business Apps | AIML | ICI Add-ins | ICI Mobile App | ICI Business Apps Release Notes |