Revision as of 09:09, 2 April 2020 (view source) IDT-1 (Talk | contribs) ← Older edit		Latest revision as of 04:14, 27 January 2021 (view source) WikiSysop (Talk | contribs)
(151 intermediate revisions by 5 users not shown)
Line 1:		Line 1:
		+	= ICI Release Notes - Release 7.15 =
−	= ICM Release Notes - Release 7.11 =	+	== List of Enhancements 7.15 ==
−	== Overview of Release 7.11 ==	+	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 7.11 Release introduces significant enhancements to the Icertis Contract Management (ICM) platform. It strives to improve user experience, intelligence, analytics and intuitiveness by continually improving ICM functionalities and the user interface.	+
	The key enhancements of this release include:		The key enhancements of this release include:
−	*'''Enhancements to Business Applications'''	+	*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>
−	**Integrating the ''ObligationAI'' and ''Obligation Management Application ''to track and manage obligations, fulfilments for a given agreement which helps in yielding contract compliance and reducing the risks involved in managing the contracts.	+	**'''''User Experience'''''
−	**Certifying that ICM is now able to support multiple business applications with reference to functionality, performance and security, to drive business compliance.	+	***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;
−	**Locking the ability to change the seeded rules that are essential for Obligation Management application flow.&nbsp;	+	***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”.
−	*'''Enhancements to the ICM Application'''	+	***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 the user interface that allows the users to navigate in ICM with just one click. This will enhance the user experience considerably by reducing the time and effort to click through several pages to reach the destination page.	+	***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;
−	**Enhancing the ICM dashboard to provide a framework for configuring a new dashboard layout, and providing support for widgets for all the Saved Search, Task List and My Recent activities. In addition, the support is also extended to use the earlier KPI based dashboard, resize the widget, and re-order the widget sequence.	+	***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;
−	**Introducing a Pre-Publish Checker tool on the User Administration tile that will analyze all the checkpoints which potentially result in downtime and provide&nbsp;failure information to the configurators, thus allowing users to take appropriate actions.	+	***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;
−	**Enforcing boundaries for technical configurations and providing guidelines on the consumption of client-side hooks and server-side hooks, as well as the deployment and configuration of implemented customization.	+	***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;
−	**Allowing users to define the order for associations and assemble them as per the defined order.	+
−	**Enhancing the Promote To Production (PToP) tool for Vulnerability and Penetration Testing (VAPT) fixes, testing open bugs in PToP engine, some new validations in the PToP engine, as well as new enhancements in the PToP engine and user interface to provide support to PToP and DevOps teams.	+
−	**Enabling users to predefine filters or apply them based on any other attribute values that the user keys in while referring value from any master records.	+
−	**Providing the flexibility to use attributes of masterdata as extensions to any agreement or associated document, which considerably improves usability and simplifies the process for users who deal with hundreds of items and need to have multiple configurations.	+
−	**Simplifying the process of authoring by allowing the contract author to create multiple agreements from a single agreement with the provision of copying associations and attributes as required.	+
−	**Introducing the capability to define a sub-role for the approver role and enabling all the capabilities of the approval process based on the sub-role.	+
−	**Allowing filtering out agreements while inheriting.	+
−	**Providing the ability to exclude attributes or associated documents when copying agreements and allowing the copying of commitments when copying the RFQ/Agreement.	+
−	**Provisioning users to define their currency preferences.	+
−	**Providing the capability to retain the original file name for any entity when uploading it, making it easier for users to identify and manage them.	+
−	**Allowing copy team role mapping by copying team from the contract request, agreement or amendment to its association capturing the rule condition based on which a user has been added to the team.	+
−	**Providing Administrators the ability to pin the necessary saved searches for external user or suppliers.	+
−	**Enhancing the document comparison capability to view and download the redlined document of the selected agreement versions.	+
−	**Extending support of multiple rulesets for event rules, for any entity, per event.	+
−	**Allowing swapping of the primary clause with its alternate clause, and enabling users to clearly identify the first version of an agreement in the Clause Comparison Report.	+
−	**Alerting users about the modifications identified in the association files assembled in the document.	+
−	**Enhancing KPI Reports’ performance, and deprecating the CLM Activity and Cycle Time reports.	+
−	*'''Enhancements to ICM API 2.0'''	+
−	**Introducing a new version of the Icertis APIs that will allow business applications to interact with ICM using standard API nomenclature for agreement and associated entities.	+
−	*'''Enhancements to ICM Add-ins'''	+
−	**Allowing users to stay on the document for further edits or reviews while publishing occurs in the background.	+
−	*'''Enhancements to Artificial Intelligence Applications'''	+
−	**Introducing eDiscovery to derive critical insights by analyzing legacy contracts.	+
−	**Introducing RiskAI based on automatic extraction of clauses and attributes through the in-built discovery model. The model has been extended to discover IT services industry specific attributes and clauses.	+
−	**Improved accuracy of AI models by incorporating user action feedback when the user is interacting with the attribute discovery in DiscoverAI and NegotiateAI apps.	+
−	**Identifying important terms in contracts (contract highlights) using AI for different personas like legal, CxOs, finance, etc.	+
−	**Extending the discovery support to URL datatype attributes; supporting multi-choice attributes and multi-choice lookup datatypes on the Attributes Discovery page, in both - DiscoverAI''and NegotiateAI apps.''	+
−	**Introducing NLP-based search query for agreement entities.	+
−	*'''Enhancements to Reports'''	+
−	**Introducing the Obligations Management Reports on the Reports tile in ICM. These out-of-the box reports include the Obligations Dashboard Report that provides information of the Fulfilments due in the next 30 days, Fulfilments overdue by the owner, and the OMH – Obligation Management Health Report that provides an overall view of fulfillment compliance.	+
−	*'''Improving the Icertis Experience '''	+
−	**Building the Secure File Transfer Protocol (SFTP) adapter as an automated solution to load masterdata once extracted from source of truth via SFTP which facilitates file access, file transfer and file management over a Secure Shell (SSH) data stream.&nbsp;	+
−	**Building the Azure Service Bus (ASB) adapter, which is an automated solution to load and update master as well as transaction data once extracted from the source of truth via ASB using JSON payloads.	+
−	**Integrating with DNCM’s (Daimler) enterprise Identity Provider (IdP) called GAS (Daimler Global Authentication System) via Open ID Connect protocol to provision the sub-roles or create new approver sub-roles.	+
−	**Allowing Salesforce users to take actions such as - Download, Assemble Contract and Send for Approval directly from the Action column of the contract index page grid, without opening the agreement record.	+
−	**Enhancing the SFDC experience by providing users the ability to search for contracts or contract requests from a common page depending on the selection criteria.	+
−	**Providing the Reports tile within Salesforce so that users can view and execute custom and default reports, thus simplifying tasks and improving productivity.	+
−	**Improving the ICM Experience for MS Dynamics interface, thus providing a seamless user experience across various form factors, simplifying the user administration experience, increasing the deal velocity and reducing the deal cycle time.	+
−	*'''Introducing ICM Platform Tools'''	+
−	**Introducing the Configuration Key tool so that a logged in user (who has access to Azure subscription) can search and update configuration keys as required reducing the dependency on the Engineering and DevOps teams.	+
−	**Releasing a Translations Editor tool that contains all strings that are localized so that users can now download all keys and their localization values as an Excel file, modify multiple values and upload the modified changes to ICM.	+
−	**Enhancing the ICM Health Check page to cover additional parameters that help identify potential outages and diagnose issues, and provide information on the performance of the ICM instance, its overall health, as well as its usefulness to users.	+
−	**Improving the Search Sync capability so that users can now check the value stored in Elastic Search for a specified key using the key name, thus eliminating the need to sync the SysId several times to verify if it is the latest one.	+
−	These release notes provide an overview of the enhancements to ICM and the ICM experience for integrations. Refer to the technical requirements and known issues for the release in this document. Refer to the detailed Wiki documentation for the explanation and capabilities of these and all other ICM features and functionalities.	+	*'''''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.&nbsp;
		+	**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. &nbsp;
		+	**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.&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;
		+	*<span style="color:#800080;">'''Mobile App Updates'''</span>
		+	**Enhancing the “Refresh” functionality for “Tasks” and “Commitment” tabs to continually show the latest changes in the status for mobile app users.
−	== Icertis Business Applications ==	+	&nbsp;
−	'''<span style="color:#008000;">448830&nbsp;– Integrating ObligationAI with Obligation Management app&nbsp;</span>'''	+	*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>
		+	**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;
		+	**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.&nbsp;
−	Discovering obligations is the critical step to start Obligation Management lifecycle. As there are hundreds of obligations in an agreement, manually having to discover, triage, and create Obligations is an exhaustive process.	+	&nbsp;
−	With this release, users can now track and manage Obligations for a given agreement using Obligation AI and Obligation Management (OM) for a seamless experience. The interconnected flow of AI with OM is aiming to solve the Legal persona’s job to triage, discover, and create obligations. With this feature, ICM provides a cohesive experience for setting up obligations. This helps in yielding contract compliance and reducing the risks involved in managing contracts which primarily leads to:	+	*<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;
−	*Reducing time and efforts to discover and create obligations.	+	&nbsp;
−	*Using ICM’s human in loop model of consuming AI such that relevance of discovery becomes better over the time.	+
−	*Scaling out the job of obligation discovery such that newer/junior members can effectively perform Obligation Management.	+
−	The default configuration is Obligation AI and Obligation Management as a combined one, and you can also configure them individually as Obligation AI, or Obligation Management. The image describes the typical workflow of Obligation Management covering all phases of OM lifecycle. The red box in the image illustrates the cohesive experience of triaging and creating Obligations.	+	*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>
−	<div class="image-green-border">[[File:7.11 Release Notes 01.png|720px|7.11 Release Notes 01.png]]</div> <div class="image-green-border">&nbsp;</div>	+	**Multiple enhancements to the AI-powered legal playbook capabilities:
−	'''<span style="color:#008000;">508359&nbsp;– Multi-app testing (Sourcing, Obligation Management) configured and running in the same environment</span>'''	+	***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.
−	With the introduction of business applications - Sourcing, AI, Obligation Management earlier, there was a demand for supporting these apps with ICM from both - existing and new customers. ICM has thus made platform changes such that the build, deploy, and run time execution systems have been rehauled such that, multiple applications can now co-exist on any given ICM instance.	+	&nbsp;
−	With this release, we are certifying that ICM is able to support multiple business applications with reference to functionality, performance and security, to drive business compliance.	+	*<span style="color:#800080;">'''Enhancements to Reports'''</span>
−	<div class="note-box">'''Note''': ICM will now support platform and business applications with same version number.&nbsp;For example, if you are on ICM 7.9 core and want to consume the ICM 7.11 offerings of Sourcing and Obligation Management business applications, then you are requested to update core to 7.11 before installing the applications.</div>	+	**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;
−	<br/> '''<span style="color:#008000;">545763 – Non-editable seeded business rules</span>'''	+	**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.
−	Previously, business rules were seeded as part of the Obligation Management app to ensure its smooth functioning. Making business rules editable by other users could result in workflow errors.	+	&nbsp;
		+
		+	*<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.
−	With this release, these business rules that are critical to the flow of the application are now locked by the service users when deploying the Obligation Management application. This prevents other users to unlock, edit and modify these rules, thus ensuring a smooth workflow.&nbsp;Refer to the 7.11 Wiki for the list of seeded rules.
−	<div class="note-box">'''Note''': Even if the rulesets are locked, you can create new rulesets for event rules.</div>
	&nbsp;		&nbsp;
−	<div class="image-green-border">&nbsp;[[File:7.11 Release Notes 04.png|720px|7.11 Release Notes 04.png]]</div>	+
		+	*<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;		&nbsp;
		+
		+	*<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.
		+
		+	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="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancement Details</span> ==
−	== ICM Application Enhancements ==	+	<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>
−	'''<span style="color:#008000;">532684 – Navigation Enhancements</span>'''	+	Previously, contract owners had to create the first version of an agreement to get a comprehensive view of the agreement.
−	Earlier, the ICM user interface was tile-based. Each time a user had to navigate from one page to another, it required multiple clicks or going back to the Dashboard page when using level1 functionalities.	+	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.
−	With this release, the ICM user interface has been considerably improved so that the user can navigate between pages (from any sub menu to any other menu item) by just one-click. This significantly enhances the user experience as it reduces the number of clicks, improves usability in navigation in addition to decreasing the load times, as it reduces round trips to the server.	+	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:'''	+	'''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;
−	*Users can now navigate from any page in ICM to any other page, thus eliminating the need for multiple page loads.	+	<span style="color:#800080;">'''575640 – Creating associations on the create or edit wizard of agreement'''</span>
−	*No training is required for user adoption as it maintains the same classic tile menu.	+
−	*All color/theme preferences can be applied.	+
−	*Works on tablets on tap which requires handling and QA.	+
−	*Supported on all standard ICM supported browsers, resolution and devices.	+
−	*All user permission and access privileges continue to be supported.	+
−	*The entire menu is configurable. Adding or removing any menu or sub-menu option can be done through database configurations, thus reducing code level customizations.	+
−	<div class="image-green-border">[[File:7.11 Release Notes 05.png|720px|7.11 Release Notes 05.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.11 Release Notes 06.png|720px|7.11 Release Notes 06.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">546019 – ICM Dashboard Enhancements</span>'''	+
−	The existing ICM dashboard is tile-based and displays only numerical data. A new layout has now been designed which allows users to switch to a widget-based dashboard layout in view of providing a comprehensive look of business information on the ''Home'' page. This has improved the user experience and usability especially around complex navigation and performing multiple clicks to achieve a seemingly simple task. Users are now able to view recent activities, saved search, notifications upfront on the dashboard, in addition to their list of tasks and KPIs/reports.	+	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.
−	<div class="image-green-border">[[File:7.11 Release Notes 07.png|720px|7.11 Release Notes 07.png]]</div>	+
−	The widget-based dashboard offers the following widgets:	+
−	*'''Performance Metric:''' displays all the KPIs to which the user has access. These include Saved Search KPIs and Report KPIs.	+	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;
−	*'''My Tasks:''' displays a list of tasks assigned to the user. The total number of tasks is displayed at the top of the widget, followed by the task link and the date on which each task was received.	+	<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>
−	*'''Notification:''' displays the notifications in the descending order of the date and time in which they have been received. Clicking the notification navigates the user to the ''Notifications'' page.	+	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.
−	*'''My Recent Activities:''' displays a list of the latest activities performed by the user on agreements, contract requests and clauses. The activities are displayed in the descending order (latest first, oldest last).	+	<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>
−	*'''Saved Search:''' displays the searches saved on the ''Search'' page.	+	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;
−	'''<span style="color:#008000;">519472 – Introducing the Pre-Publish Checker Tool</span>'''&nbsp;	+	<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from the contract request'''</span>
−	In ICM, when a contract type is published, agreements are created that move from the ''Draft'' state to the ''Approved'' state and finally to the ''Published'' state. The ''IsPublished'' flag indicates the state of the contract type. Publishing the entity is a complex process and ICM remains unavailable for use during this time. Hence, downtime is required for any publishing activity. Several times the publishing process itself fails resulting in extended downtime causing delays in configurations in addition to the loss of productivity.	+	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;
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 6.png|720px|7.15 Release Notes Screenshot 6]]</div>
		+	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;
−	ICM has now introduced a Pre-Publish Checker tool within the publishing process that will analyze the configuration status of contract types, APIs and running services along with infra sizing. The tool guides configurators whether publishing must be initiated or not, by listing the checkpoints regarding the failure information, instead of downtime about the corrections needed. This allows users to take appropriate actions when Publish is not possible.	+	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.
		+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 7.png|720px|7.15 Release Notes Screenshot 7]]</div>
		+	&nbsp;
−	The Pre-Publish tool performs basic checks for publishing contract types. The checklist includes a comprehensive list of 20 checks which may cause publish process to fail. This Pre-Publish check will help reduce instance downtime due to Publish related errors.	+	'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''
−	Administrators can now:	+	ICI’s collaboration portal allows external users with login privileges to access the platform and perform assigned tasks within ICI itself.&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.
−	*View the pre-publish checklist items in case of failures.
−	*View the checklist items status and its corresponding evaluations on why publish must not be continued.
−	*View database information - SLO (Service Level Objectives) of database.
−	<div class="note-box">'''Note''': If no errors are identified, publish process continues normally.</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.11 Release Notes 08.png|720px|7.11 Release Notes 08.png]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">541970 –&nbsp;Assembly of associated documents into the main agreement based on a defined order</span>'''	+	<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements'''</span>
		+
		+	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;
−	ICM now enables users to define the format for assembly of associations tagged as a Table or File in the main agreement using saved search.	+	*Select and save extension attributes to display in the grid view, via the “Default Search” column functionality.
−	<div class="image-green-border">[[File:7.11 Release Notes 09.png|720px|7.11 Release Notes 09.png]]</div>	+	*View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.
−	Users can create saved search of the desired association, using the capabilities of Search to Filter, Order, and Select the columns and their sequence, to be rendered in the final output. This saved search can be used along with the tagged association to assemble associations as desired using ICM Experience for Word.	+	*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.11 Release Notes 10.png|720px|7.11 Release Notes 10.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">'''Note:''' If saved search is not configured or not tagged along with the association, ICM behaves as-is.</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 9.png|720px|7.15 Release Notes Screenshot&nbsp;9]]</div>
	&nbsp;		&nbsp;
−	<div class="image-green-border">[[File:7.11 Release Notes 11.png|720px|7.11 Release Notes 11.png]]</div> <div class="image-green-border">&nbsp;</div>
−	'''<span style="color:#008000;">476165 – PToP tool enhancements</span>'''
−	The beta version of the Promote To Production (PToP) tool was enabled in release 7.10. This functionality, provided to administrators, could promote ICM configurations/modifications that were made to ICM configurations in pre-production environments to production environments.	+	<span style="color:#800080;">'''514615 – Streamlining&nbsp;the approval process over emails'''</span>
−	With this release, the following enhancements have been made for:	+	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;
−	*Vulnerability and Penetration Testing (VAPT) fixes.	+	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;
−	*Testing open bugs in PToP engine.	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 10.png|720px|7.15 Release Notes Screenshot&nbsp;10]]</div>
−	*Some new validations in the PToP engine.	+	With this release:
−	*Better user interface to provide support to PToP and DevOps teams.	+
		+	*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;
−	'''<span style="color:#008000;">541976 – Ability to configure and apply multiple filters while referring value from master records</span>'''	+	<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>
−	Earlier, ICM provided the capability of filtering records on the basis of a single attribute using cascading.	+	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;
−	The capability has been further enhanced so that users can now apply multiple filters while referencing values from any master records. This provides users the flexibility to predefine filters or apply them based on any other attribute values that the user keys in.	+	<span style="color:#800080;">'''617385&nbsp;– Ability to define additional clause group under clause entity'''</span>
−	Users can now:	+	Previously, ICI supported 3 clause groups – “Termination”, “Legal” and “None”.
−	*Define UI based configuration for multiple static and dynamic filters for the referred masterdata.	+	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.
−	*Filter masterdata records directly in the drop-downs as well as the popup, based on the predefined configured static filters, while working with agreements/amendments.	+
−	*Filter masterdata records directly in the drop-downs as well as the popup, based on the predefined dynamic filters as the user keys in the values for the selected attributes marked as filters, while working with agreements/amendments.	+
−	<div class="image-green-border">[[File:7.11 Release Notes 12.png|720px|7.11 Release Notes 12.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">541980 – Ability to have flexible contract type extensions</span>'''	+
−	Previously, for any agreement or associated document, attributes were fixed and defined during the contract type configuration. However, users often have the requirement to define or select the attributes when they are creating the agreement or an associated document instance.	+	Administrators can now:
−	For line items, the attributes are required to be defined based on type of line item. For example, the attributes for “wheel” and “pen refills” are different. These can be defined by the users at the time of line items creation.	+	*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;
−	With this release, ICM provides the flexibility to use attributes of masterdata as extensions to any agreement or associated document. These extended attributes can be selected and added when user is actually creating the instance. This considerably improves usability and simplifies the process for users who deal hundreds of items and need to have multiple configurations.	+	<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>
−	Users now:	+	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.
−	*Can create rules to attach masterdata attributes (single or multiple) to your associated documents and agreements based on certain conditions.	+	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.
−	*Have flexibility to select (add or remove) and use any masterdata attributes as extensions at the time of agreements/associated documents creation.<br/> &nbsp;	+
−	'''<span style="color:#008000;">541975 – Ability to create multiple agreements from a single agreement</span>'''	+	'''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>
−	With this release, ICM has improved usability and considerably simplified the process of authoring, allowing the contract author to create multiple agreements from a single agreement with the provision of copying associations and attributes as required.	+	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.
−	Users now:	+	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;
−	*Have complete flexibility at configuration level to define the applicable contract type, decision attribute, compute attribute for bulk agreement creation.	+	Users can now:&nbsp;
−	*Have the option of bulk agreement creation in the model agreement based on the above configuration with provision to define unique batch Id for all the agreements created using a single model agreement.	+
−	*Can access model agreements only through technically configured Admin saved search. &nbsp;	+
−	&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.
−	'''<span style="color:#008000;">541982 – Ability to support approver sub-roles</span>'''	+	'''Note:''' All prerequisite configurations applicable for the termination workflow should also be set for the bulk termination process.<br/> &nbsp;
−	With this release, ICM is providing the ability to define sub-roles for the Approver role. This flexibility enables all the capabilities of the Approver for the users at the sub-role level. For example, you can now set different type of approvers for an agreement based on functions such as Legal Approver, Finance Approver, and so on.&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;">541979 – Ability to filter agreements available for inheritance</span>'''	+	<span style="color:#800080;">'''558605 – Viewing amendments in grid view on the agreement details page'''</span>
		+
		+	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;
−	With this release, ICM provides the capability to configure multiple mandatory and non-mandatory filters at contract type level for inheritance by which agreements can be filtered. This improves usability and reduces the overall effort, making it easier to find the desired agreement.	+	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.11 Release Notes 13.png|720px|7.11 Release Notes 13.png]]</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 15.png|720px|7.15 Release Notes Screenshot 15]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">549081 – Availability of contract type description during contract type instance creation</span>'''	+	<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>
−	ICM has now included the ''Contract Type Description ''field when creating agreements, amendments, associated documents, masterdata or contract requests. This facilitates users to select the desired contract type.&nbsp;&nbsp;	+	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;
−	<div class="image-green-border">[[File:7.11 Release Notes 14.png|720px|7.11 Release Notes 14.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">551098/551099/551100 – Enhancements when copying agreements</span>'''	+
−	ICM has improved the usability when copying agreements by allowing the users to:	+	Users can now:&nbsp;
−	*Exclude associated documents from getting copied.	+	*View eight options in a drop-down list (instead of six), without scrolling.&nbsp;
−	*Exclude the attributes of selected associated documents.	+	*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;
−	*Select and copy Commitments.&nbsp;	+	*View all selected values at the top of the drop-down.
−	*Exclude the attributes of selected Commitments.	+	*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.11 Release Notes 15.png|720px|7.11 Release Notes 15.png]]</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 16.png|720px|7.15 Release Notes Screenshot 16]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">551101 – Ability to configure role for commitment when adding user to the team</span>'''	+	<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>
−	Previously, when creating commitments, business owners were added to the agreement team as ''Contributors''. It is now possible to configure the role in which business owners of the commitment should be added to the agreement team (for example, ''Secondary Owner'', ''Observer'', etc.).	+	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;
		+	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;
		+
		+	Configurators can now:&nbsp;
		+
		+	*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;		&nbsp;
−	'''<span style="color:#008000;">466694 – Ability to configure reminder notifications on entities</span>'''	+	<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>
−	Earlier, ICM did not have Out-of-the-Box (OOTB) support for the reminder notifications in the core platform. Reminder notifications had to be customized based on each customer’s requirements.	+	Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;
−	To simplify the process, ICM now provides the ability to send the entity-wise reminders using a Reminder Notification Template to cater to wider requirements in the domain of Contract Management, Sourcing, and other Business Apps (Obligation Management and Supplier lifecycle).	+	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;
−	The reminders can be set up based on a recurring or One-time pattern (Minute(s), Hour(s), Day(s), week(s), month(s), year(s)). This has enhanced productivity and user&nbsp; experience in addition to reducing efforts of technical configuration for task reminders.	+	Administrators can:&nbsp;
−	Users can now:	+	*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.
−	*Set reminder notification for agreements, amendments and associations.	+	Users can:&nbsp;
−	*Configure a template for reminder notification.	+
−	*Set the reminder notification based on Event Rule.	+	*Access the ICI system with appropriate details as default after the first login.&nbsp;
−	*Set reminders based on two types of recurrences – ''Set One Time Reminder'' and ''Set Recurrence Reminder'', which will get triggered once or multiple times respectively, based on the interval frequency.	+	*Override the default preference settings as per individual preferences.
−	<div class="image-green-border">[[File:7.11 Release Notes 16.png|720px|7.11 Release Notes 16.png]]</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 18.png|720px|7.15 Release Notes Screenshot 18]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">551103 – Auto-populating the currency when creating entities</span>'''	+	<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading the document'''</span>
−	Earlier, currency preferences were defined at the contract type level and users had to manually change it based on their requirements. Now, users can define their preferred currency (for example, USD) using the&nbsp;''Preferred Currency'' option in ''My Preferences''. Based on the user preference, the selected currency will be auto-populated for any Currency attribute.	+	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.11 Release Notes 17.png|720px|7.11 Release Notes 17.png]]</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 19.png|720px|7.15 Release Notes Screenshot 19]]</div>
−	&nbsp;	+	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;
−	'''<span style="color:#008000;">551104 – Ability to retain original filename of uploaded files</span>'''	+	This functionality is available for agreements, amendments, and orphan amendments.<br/> &nbsp;
−	Earlier, when downloading a file in ICM, the original file name was not retained, and the file name was changed as per the naming convention defined in ICM.	+	<span style="color:#800080;">'''614860 – Attaching associated documents to agreement notifications'''</span>
−	The usability has now been improved so that users can now retain the original file name for any entity when uploading it to ICM, making it easier for users to identify and manage them. This is applicable to agreements, amendments, associations, and file attributes in agreements/associations.	+	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;
−	<div class="image-green-border">[[File:7.11 Release Notes 18.png|720px|7.11 Release Notes 18.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">560477 – Automatic update of entity count on navigation pane without refresh</span>'''	+
−	ICM now automatically updates the count for entities (such as ''Association'', ''Commitment'', etc.) at the execution of an event on the left navigation pane of the ''Details'' page. This improves the user experience as the page is no longer refreshed and the workflow continues smoothly.	+	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.
−	&nbsp;	+	With this release:
−	'''<span style="color:#008000;">488574 &nbsp;– Replace primary clauses with alternate clauses from Clause Comparison Report</span>'''	+	*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;
−	Earlier, ICM users could only replace clause text and language by using Word Add-ins (Icertis Experience for Word (.JS) or .Net). This was achieved by substituting the clause's text or language by the stored alternate clause.	+	<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>
−	With this release, ICM allows replacing the clause text with the alternate clause text from ICM itself. This is accomplished using ''Compare Clause Changes with Previous Document Version'' icon available on the agreement ''Details'' page. For any particular primary clause, users can view the list of alternate clauses by clicking the ''Select Alternate Clause'' link and select the alternate clause to swap it with the selected primary clause. This ''Compare Changes with Previous Document Version'' window gives users the additional flexibility to preview the ''Previous Text'' and the ''Current Text ''of clauses.	+	ICI allows users to define the linkage type as a parent, child, or peer while associating peer entities with each other.
−	Users can:	+	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.
−	*View the ''Select Alternate Clause'' link in the Clause Comparison Report.	+	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;
−	*Replace a non-mandatory clause.	+
−	*Track clause changes (primary clause replaced with alternate clause) through the ''Versions'' and the ''History'' tabs.	+
−	*View agreement preview with a replaced alternate clause.	+
		+	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;
−	'''<span style="color:#008000;">488577 – Document upload validation shows the changes in associations tagged as file(s)</span>'''	+	<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>
−	In ICM, associations tagged as a file in a template are added to the agreement by document assembly. During the redlining process, users may modify the agreement and make changes in the associations. Earlier, at the time of uploading a new version of the agreement, the user was notified of the changes detected in Associations tagged as a table.	+	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, ICM alerts the user and presents a summary of any text that is added, removed or modified in association(s) tagged as file(s).&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;
−	The following actions take place as soon as a new agreement version is uploaded:	+	<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at the contract type level'''</span>
−	*The version being uploaded is compared with the latest version available in ICM.	+	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;
−	*A window is displayed alerting the changes made in associations.	+
−	'''Note''': The user can view the changes in association by clicking the ''View all modifications'' button for a published agreement in Icertis Experience for Word. The user may also download a comparison between the previous version of the agreement and the version being uploaded. This downloaded document would highlight the modifications identified.&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.11 Release Notes 19.png|720px|7.11 Release Notes 19.png]]</div> <div class="image-green-border">&nbsp;</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 25.png|720px|7.15 Release Notes Screenshot 25]]</div>
−	'''<span style="color:#008000;">535845 – Ability to identify the first version of an agreement in the Clause Comparison Report</span>'''	+	'''Note:&nbsp;'''
−	Earlier in ICM, if there was only one version of the agreement, the ''Clause Comparison Report'' would display a ''No changes found'' message. This message was misleading to the users as it suggested that no clauses were changed, instead of conveying that only one version of the agreement has been created and hence there is no clause comparison.	+	*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;
−	This has now been rectified by leaving the ''Previous Text'' box blank and displaying the actual clauses that are available in the agreement in the ''Current Text'' box. This clearly indicates to the user that only a single version of the agreement is currently available.	+	<span style="color:#800080;">'''614877 – Replacing a user with multiple users'''</span>
−	<div class="image-green-border">[[File:7.11 Release Notes 20.png|720px|7.11 Release Notes 20.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">467201 – Ability to copy team role from contract request, agreement, and amendment to its association</span>'''	+
−	Previously, in ICM when approvers were added to the contract request, agreement and amendment, they would get ''Manage'' Privilege to the respective entity, but ''None'' Privilege on the supporting document (Association entity) as they were not part of the team. Hence, these entities with supporting documents were sent out for approval without the approvers having the rights to make any changes to the associated documents.	+	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;
−	ICM has now introduced the capability to copy the role-based team members while creating associations, so that the users have the privileges for associated documents as they do for the parent entities. This is achieved by configuring contract types.	+	Administrators can now:&nbsp;
−	Users 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. &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.
−	*Copy the entire team of the entity (''Contract Request, Agreement, Amendmen''t) to its defined Association entity on a specific role (such as ''Observer)''.
−	*Copy an individual team member from a particular role of the entity (''Contract Request, Agreement, Amendment'') to its defined Association entity for any specific role (such as ''Secondary Owner, Contributor, Observer, Contract Admin'').
−	*Copy the entire team from the entity (''Contract Request, Agreement, Amendment'') to the association on predefined event.
−	*Get an Audit log while copying the team from the agreement to its respective association.
−	<div class="image-green-border">[[File:7.11 Release Notes 21.png|720px|7.11 Release Notes 21.png]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">560209 – User inclusion condition visibility in team</span>'''	+	<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>
−	Previously, the ''Teams'' tab for an agreement displayed columns with details for each user within a team such as ''Team Role, Step Number'', and so on. Now, a new column with the header ''By Rule'' has been added which indicates if the user has been added using a rule condition.	+	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.11 Release Notes 22.png|720px|7.11 Release Notes 22.png]]</div>	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 27.png|720px|7.15 Release Notes Screenshot 27]]</div>
−	If a user has been added by a rule, the value ''Yes'' is displayed in the column with a hyperlink.	+	The administrator can control the supersede functionality for agreements by:
−	Clicking the hyperlink displays a window specifying the rule condition with which the user has been added to the team. For example, ''John has been added if Created Date Is After February 12, 2020.''	+	*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;
−	The value ''No'' is displayed in this column if a user has not been added by a rule or if the user is added through an event rule.	+	<span style="color:#800080;">'''615293 – Showing or hiding the No Team Available message'''</span>
−	<div class="image-green-border">[[File:7.11 Release Notes 23.png|720px|7.11 Release Notes 23.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">560216 – Generate a redline version for document comparison</span>'''	+
−	Previously, in ICM, users could view the changes made between two agreement versions side-by-side through the ''Document Comparison'' option. With this release, instead of the side-by-side view, the ''Document Comparison'' capability has been enhanced with an option to view and download the redlined document of the selected agreement versions, highlighting the changes in Microsoft Word format.	+	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;
−	<div class="image-green-border">[[File:7.11 Release Notes 24.png|720px|7.11 Release Notes 24.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">545742 – Extending support of multiple rulesets for event rules</span>'''	+
−	Previously, ICM users could create multiple rulesets for approval rules, template selection rules, and clause assembly rules. However, creating rulesets for event rules was not supported.	+	ICI now can suppress this message through technical configuration, thereby minimizing the number of unnecessary clicks.&nbsp;
−	Rulesets are the set of rules created for a particular event for any ICM entity. For example, you can create multiple rules in the ruleset as displayed in the image below.	+	Administrators can:&nbsp;
−	<div class="image-green-border">[[File:7.11 Release Notes 02.png|720px|7.11 Release Notes 02.png]]</div>	+
−	With this release, an Administrator can now:	+
−	*Create multiple rulesets for event rules, for any entity, per event.	+	*Selectively enable or disable the “No Team Available” message window, at the entity contract type level, appearing at various states.&nbsp;
−	*Copy event rules to target entity. However, a new rule is created for the target entity that does not override the existing one, if any. The name of the ruleset remains unique throughout the system.	+	*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;
−	For example, you can create multiple rulesets for event rules for any entity as displayed in the image below. When multiple event rules are defined, ICM ensures all event rules are executed.	+	'''Note:''' This capability is available across ICI for all entities, events, integrations and add-ins in ICI.
−	<div class="image-green-border">[[File:7.11 Release Notes 03.png|720px|7.11 Release Notes 03.png]]</div>	+
−	The ''Stop Processing More Rules ''option when selected as ''Yes ''allows users to stop evaluating the rules within the ruleset.	+
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">560728 – Global favorites – supplier view</span>'''	+	<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>
−	Previously, ICM users created favorites for themselves however, these favorites were not accessible to all users in the domain.	+	Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&nbsp;
−	ICM Administrators can now set default favorites for all the users in the domain.&nbsp; They will be able to pin the necessary saved searches for external users/suppliers (who do not have access to saved searches) so that they can easily find actions and even view the filtered lists.	+	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;
−	Administrators can now:	+	Users can now:&nbsp;
−	*Mark the global search as a global favorite so that all users can view the global favorites	+	*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;
−	*Display the global favorites in the respective entities for easy navigation to exact action or list	+	*Support conditional expressions for extension attributes. &nbsp;
−	*Reorder the global favorites as per entity so that the desired order can be published for the user	+	*Define conditions with different operators based on the selected attribute datatype.&nbsp;
−	*Configure maximum 4 favorites per entity	+	*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;
−	'''Note''':	+	<span style="color:#800080;">'''616901 – Applying facets to business status search filter'''</span>
−	*Users cannot set the Administrator default favorites. However, users can un-pin the global favorites.	+	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;
−	*When users pin the searches along with global favorites, they won’t get any more updates on global favorites.&nbsp;	+
−	*Global favorites apply to agreements only.	+
−	*A maximum of 4 global favorites are displayed to the user based on the permissions for those security groups.	+
		+	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;		&nbsp;
−	'''<span style="color:#008000;">589531/591634 – Enhancement of KPI reports performance</span>'''	+	<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>
−	Previously, additional reports such as ''Cycle Time Report'', ''Template Clause Report'', ''Expired Agreements'', ''Approved Requests Waiting'' ''for Contract Creation'', ''Signature Type Report'', ''User Login Report'' and ''CLM Activity Report'' were available to the user as dashboard KPIs.	+	Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions.&nbsp;
−	With this release, the ''CLM Activity Report'' and ''Cycle Time Report'' have been deprecated, thereby improving ICM performance considerably.	+	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;		&nbsp;
−	== ICM API Enhancements&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>
−	<div class="image-green-border">	+
−	'''<span style="color:#008000;">541856 – API 2.0 Implementation</span>'''	+
−	With this release, a new version of the Icertis APIs have been introduced that will allow business applications to interact with ICM using standard API nomenclature for agreement and associated entities.	+	Previously in ICI, attribute names did not support special characters apart from _ (underscore), & (ampersand), and space.&nbsp;
−	The highlights include:	+	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.
−	*Supporting Resume workflow action to perform additional activities such as Send for External Review, Upload Signed Copy	+	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;
−	*Caching strategy	+
−	*Swagger documentation	+
−	*Security review	+
−	*Multi-tenancy	+
−	*Error message localization	+
−	*Designing Masterdata endpoints similar to agreements endpoints	+
−	*Embedding internal associations of agreements (such as Clauses, Version, Deviations, Teams) in agreement response; support, create, update and get internal association from agreement	+
−	*API Gateway capabilities such as throttling and metering	+
−	The list for API 2.0 include the following endpoints for creating an Agreement, Masterdata and Contract Request, whichever applicable:	+	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;
−	*'''Get the instance:''' used to get an empty instance of an entity.	+	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;
−	*'''Create Instance:''' used to create an instance record of an entity. There could be additional parameters which could specify actions such as Create, Create and Publish, Create and Send for Approval.	+	<div class="image-green-border">[[File:7.15 Release Notes Screenshot 32.png|720px|7.15 Release Notes Screenshot 32]]</div>
−	*'''Update Instance:''' used to update an instance record of an entity. There could be additional parameters which could specify actions such as Update Metadata, Upload Document or Update Instance.	+
−	*'''Save the Document:''' used to upload a document.	+
−	*'''Trigger Actions:''' used to trigger workflow actions; different actions will be part of additional parameters such as Send for Approval, Signature, Approve, Reject, Recall, Publish, etc.	+
−	*'''Get Instance:''' used to get the instance of an entity.	+
−	*'''Get Instances:''' used to get the instance of an entity in bulk. The search condition could be a post parameter.	+
−	*'''Add Team Member:''' used to add a team member to an instance.	+
−	*'''Remove Team Member:''' used to remove a team member from an instance.	+
−	</div>	+
	&nbsp;		&nbsp;
−	== Enhancements to ICM Add-ins&nbsp; ==	+	<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>
−	<div class="image-green-border">	+
−	'''<span style="color:#008000;">515446 – Word Add-In (.Net) should not close once the contract is published</span>'''	+
−	Previously, when a user tried to publish an agreement document, Word Add-in (.Net) would notify the users that the document would be saved and closed. This behavior forced the user to select ''OK'' if they wanted to publish the document. However, this action would close the document before publishing it.	+	With this release, ICI provides new controls for multi-select and single-select choice attributes.&nbsp;
−	With this release, once the document gets published, a validation window is displayed giving the user the choice to open the published document. Hence, the user does not need to download the new version to view the published document. The user can now stay on the document and make further edits or reviews, as required, while publish function occurs in the background.	+	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> <div class="image-green-border">[[File:7.11 Release Notes 25.png|720px|7.11 Release Notes 25.png]]</div>	+	<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;		&nbsp;
		+	<span style="color:#4B0082;">'''593421 – Labeling agreement document versions as per signature copy'''</span>
−	== Enhancements to Artificial Intelligence Applications in ICM ==	+	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:#008000;">510541 – eDiscovery using Artificial Intelligence</span>'''	+	<span style="color:#800080;">'''872309 – Providing flexibility for assembling associations tagged as clauses'''</span>
−	Legacy contract documents from the archives of companies contain a host of unstructured but valuable information. From a CLM platform perspective, this information can be categorized and structured into attributes, clauses, agreements, etc.	+	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.
−	With this release, ICM introduces a framework using Artificial Intelligence (AI) to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.	+	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;
−	With eDiscovery using AI:	+	*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.
−	*ICM can automatically confirm certain discovered clauses, so that users do not have to confirm them manually.	+	'''Note: '''By default, the key is set to false.<br/> &nbsp;
−	*Auto-confirmed clauses can be searched in the same way as any other agreement clauses.	+
−	*Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses.	+
−	*Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically.	+
−	*While auto confirming, ICM compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with a clause in the clause library, then the discovered clause is identified as one from the clause library. If the match percentage is lesser than the threshold, then clause is identified as one of the standard ICM AI clause category.	+
−	&nbsp;	+	== Mobile App Enhancement Details ==
−	'''<span style="color:#008000;">510549 – Inbuilt discovery of attributes and clauses in IT services vertical</span>'''	+	<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span>
−	The nature of business for companies providing IT services is such that more than 80% of their contracts would be drafted using third party paper. As of now, such IT firms deploy large teams to extract important clauses and attributes in these third party contracts in order to track the contractual obligations, risks, rebates, discounts, etc. It is a time consuming and error-prone process. Hence, companies need a system which will extract these clauses and attributes automatically.	+	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;
−	''RiskAI'' is a major application of inbuilt discovery of such attributes and clauses, using which a risk score can now be computed for a given agreement. ''DiscoverAI'' will set a value of an attribute if a specific clause is found in the agreement. A rule can further be written to assign a risk score in either case if the clause is present or absent in the agreement.	+	<span style="color:#800080;">'''850259 – Updating logo and ICM to new guidelines'''</span>
−	With this release, in addition to the generic discovery model:	+	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;
−	*The ICM configurator can deploy a discovery model specific to the IT service industry, so that users can discover attributes and clauses specific to that industry.	+	<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span>
−	**'''Attributes: '''''LiabilityType'', ''ComplianceType''	+
−	**'''Clauses''': ''Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention'', ''Rebates and discounts, Fixed Liability, No Liability ''and''Uncapped''	+	Android 11 compatibility changes have been made with this release by setting the target SDK version to 30 and deprecated methods have been updated.
−	*Contract negotiators can use ICM to discover attributes and clauses using a pre-trained model, so that they do not have to identify them manually,	+
−	*Contract negotiators can identify if a specific clause is included in the document or not, so that they can initiate an approval workflow to take care of compliance.	+
−	*The value of the contract can now be driven based on the presence or absence of the specified clause, and this can further be used for calculating the risk score.	+
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">510545 – Automating retraining of AI models based on user action feedback</span>'''	+	<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span>
−	Continuous learning and improvement based on user feedback is what differentiates AI/ML apps. The recall and precision of AI apps improves as it learns from a variety of documents.	+	With this release, the UI WebView component for iOS has been deprecated.<br/> &nbsp;
−	While user feedback is heavily incorporated in the initial phase of model training, this model has now been retrained to incorporate changes based on user interactions. It has been further enhanced to incorporate user interactions with the attribute discovery on the Web UI as well as ''NegotiateAI'' and the feedback will be used to suggest precise default options on the attributes for subsequent discoveries.	+	== ICI API Enhancement Details&nbsp; ==
		+	<div class="image-green-border">
		+	<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>
−	With this release, the actions taken by contract negotiators to correct recommendations for discovered attributes like selecting different option than the default option suggested by the algorithm, or selecting an altogether different value if none of the options suggested by algorithm match the expectation, would be automatically learned by the model. When a document with same language or similar language is processed next time, then the model will suggest the learned value as a default option to the users so that they do not have to enter it manually again.	+	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;
−	&nbsp;	+	This is applicable for visualizing, retrieval, creation, and updating of the instances of the following entities:<br/> Contract Requests
−	'''<span style="color:#008000;">465906 – Contract highlights</span>'''	+	*Agreements
		+	*Associations
		+	*Amendments
		+
		+	New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.
		+
		+	&nbsp;
−	Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.	+	<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>
−	With this release,	+	ICI already supports downloading agreements.
−	*The ''DiscoverAI'' model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the ''DiscoverAI'' model can find matching as well as similar terms in documents and highlight them for the intended audience.	+	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.
−	*In case no phrases are specified, then ICM will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance.	+
−	*A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user.	+
−	*Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICM will identify the important sections of the contract based on historical data and phrases specified by the configurator.	+
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">539481 – DiscoveryAI / NegotiateAI support for multi-select attributes</span>'''	+	<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>
−	''DiscoverAI&nbsp;''helps contract negotiators to discover attributes and clauses in the agreement document. The discovered attributes are mapped to respective datatypes. Previously, ICM supported string, number, date, choice, boolean, text, lookup percentage and currency type attributes.	+	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.
−	With this release, ICM has extended the discovery support to URL datatype attributes. ''DiscoverAI'' and ''NegotiateAI'' can now discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the ''Attributes Discovery'' page, in both - ''DiscoverAI'' and ''NegotiateAI'' apps.	+	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.
−	ICM has now added an option in the discovered clauses menu of ''NegotiateAI'' to find clauses similar to discovered clauses in the ICM repository.	+	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;
−	&nbsp;	+	<br/> <span style="color:#800080;">'''660859 – Supporting TrackingId in APIs'''</span>
−	'''<span style="color:#008000;">566499 – Search as a natural language query in ICM</span>'''	+	To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;
−	The current search functionality in ICM supports dynamic faceting and keyword-based search in three modes - metadata search, document or full-text search, and combined search. It assumes some level of expertise with users when they want to filter down the results to find exact records they were looking for.	+	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;
−	With this release, ICM has introduced an AI enabled mode of searching the agreements. Users will be able to find the agreements in ICM by simply writing a spoken language statement. This mode allows a user to enter search terms in any form, including a statement, a question, or a simple list of keywords.	+	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;
−	In this release, the user would be leveraging this Natural Language Processing (NLP) technology for an Agreement entity on Global Search page as well as Agreement index page.	+	The following API changes have been made to ensure that the existing implementation and code remains intact:
−	&nbsp;It supports querying on system attributes as well as few seeded attributes like status, contract type name, effective, created, modified, expiry dates, users, roles, clauses, etc. In this mode, users can specify the additional filters in the query itself to get the required results; for example, ''MSA Agreements expiring next month, Agreements which are executed and contain a confidentiality clause, etc.'' The NLP search query results can be further filtered using the existing ICM category-based filters.	+	*Provided support for a “TrackingId” header in every logging request.&nbsp;
−	<div class="image-green-border">[[File:7.11 Release Notes 26.png|720px|7.11 Release Notes 26.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.11 Release Notes 27.png|720px|7.11 Release Notes 27.png]]</div> <div class="image-green-border">&nbsp;</div>	+	*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;
−	== Enhancements to Reports ==	+	'''Note: '''The implementation of the "TrackingId" is optional and the value must be GUID only.&nbsp;Supported in API 1.0 as well.
−	'''<span style="color:#008000;">519281 – Out-of-the-Box Obligations Management Dashboard reports</span>'''	+	This can be used for:
−	With the introduction of the Obligation Management app in the previous release, the need for specific reporting techniques is evident so that business executives can track and monitor obligations and fulfillments. To achieve this, the implementation teams are required to spend considerable time and effort to customize Obligation objects as per the customer requirements.	+	*Related API Calls
		+	*Async operations
		+	*Bulk operations
		+	*Status check operations &nbsp; &nbsp;
		+	</div>
		+	&nbsp;
−	Hence with this release, the Obligations Management Dashboard Reports have been introduced on the Reports tile in ICM. These out-of-the box reports are available to authorized users who have access to the Obligation Management app without any need for customization.	+	== ICI Add-ins Enhancement Details ==
−	The Obligation Management Reports include:	+	<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>
−	*'''Obligations Dashboard Report:''' provides information of the Fulfillments due in the next 30 days and Fulfillments overdue by the owner. This enables the users to take corrective actions on time and thus mitigate any risks.	+	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;
−	*'''OMH - Obligation Management Health Report:''' provides an overall view of the total Fulfillments across all agreements that are fulfilled.	+
−	Access to these reports can be provided through Security Groups (similar to other reports). Only authorized users with access to Obligation Management can view the Obligation Management Dashboard reports. Even if the users are authorized to view/access a specific report, the privileges of the reports further follow the authorization that the user has in ICM. If the user does not have the privileges to view a particular set of agreements in ICM, they would not see those in the report even though they have the view privileges for the reports.	+	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&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;		&nbsp;
−	== Integrations ==	+	&nbsp;
−	'''<span style="color:#008000;">467181 – Generic integration framework to support SFTP interface</span>'''&nbsp;&nbsp;	+	== AI Applications Enhancement&nbsp;Details ==
−	Contract creation in ICM relies heavily upon availability of appropriate masterdata. As ICM does not own the masterdata, customers have to upload it manually. The process of extracting, transforming and loading the masterdata into ICM is cumbersome and can get very complicated depending on the source of origin. Moreover, the lack of industry standard data upload capability such as SFTP as part of platform leads to redundant coding effort for implementation teams.	+	<span style="color:#800080;">'''727318 – Enhancing AI-powered playbook in Icertis Experience for Word'''</span>
−	With this release, the Secure File Transfer Protocol (SFTP) adapter has been built as an automated solution to load masterdata once extracted from source of truth via SFTP. SFTP, a secure version of File Transfer Protocol (FTP), is a network protocol which facilitates file access, file transfer, and file management over a Secure Shell (SSH) data stream.	+	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;
−	This will enable Administrators to:	+	The legal playbook is now enhanced and provides more options to work with the playbook from Icertis Experience for Word.&nbsp;
−	*Define configuration parameters required for SFTP interface using Client App Reference and Client App Entity Mapping.	+	With this release:
−	*Configure and run scheduled batch jobs via SFTP.	+
−	The execution of this integration sync task allows ICM to read the metadata definitions and execute the job successfully, which in turn will allow users to easily upload masterdata required for completing CLM process in bulk. Users will receive an error when records are not present and can generate log files for further processing.	+	*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;
−	This enables users to:	+	<span style="color:#800080;">'''575475 – Automating user feedback during clause review'''</span>
−	*Create generic integration mapping in cross reference.	+	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;
−	*Create generic integration mapping in client app entity mapping.	+
−	*Download masterdata template file from cross reference (based on client app entity mapping).	+
−	*Publish masterdata template file on SFTP (based on client app entity mapping)	+
−	*Create, update and delete records from masterdata tables using the input file from SFTP server.	+
−	*Receive logs/errors on SFTP.	+
−	&nbsp;	+	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;
−	'''<span style="color:#008000;">530080 – Generic integration framework to support ASB interface</span>'''&nbsp;&nbsp;	+	<br/> <br/> <span style="color:#800080;">'''539492 – Rearranging discovered clauses'''</span>
−	As we know that the process to extract, transform and load data into ICM is a substantial task based on the source of the origin. To simplify this, we have built the Azure Service Bus (ASB) adapter, which is an automated solution to load and update master, transaction data once extracted from the source of truth via ASB using JSON payloads.	+	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;
−	Azure Service Bus (ASB) is a fully managed enterprise integration message broker. Data is transferred between different applications and services using messages. The ICM-ASB adapter considers the approach based on REST and OData principles that exposes a uniform, stateless interface which communicates using HTTP(S) and JSON payloads.	+	*Merge multiple discovered clauses into a single clause or split a large discovered clause into multiple clauses.&nbsp;
		+	*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. &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>
−	Users can now:	+	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;
		+
		+	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;
		+
		+	Users can:&nbsp;
−	*Define configuration parameters for ASB interface using client app reference and client app entity mapping.	+	*View the progress of the attribute discovery.&nbsp;
−	*Create and maintain latest masterdata in ICM required for contracts and contract requests via ASB interface.	+	*Identify AI discoverable attributes on the “Attributes” page of the agreement creation wizard.
−	*Push transaction data to third party systems via ASB interface to be able to manage ICM entities using necessary JSON payloads.	+	*View the values recommended by AI for discoverable attributes.
−	*Maintain business entities such as purchase requisitions. Purchase orders or sourcing event from procurement systems to ICM via ASB interface.	+	*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;		&nbsp;
−	'''<span style="color:#008000;">544347 – Ability to integrate ICM with Enterprise-Level Identity Providers using OpenID Connect protocol</span>'''	+	<span style="color:#800080;">'''727312 – Clause hierarchy discovery in text PDFs'''</span>
−	ICM is now integrated with Enterprise-Level Identity Providers (IdP) such as PingFederate for user authentication and Single Sign-On (SSO) using the OpenID Connect protocol.	+	In the previous release, clause hierarchy discovery was introduced in well-formatted .docx agreements.
−	This will allow users trying to access the ICM application to get authenticated using the SSO platform. Once the credentials have been validated, the user will be redirected to the ICM Dashboard and ICM will authorize the user to securely access ICM based on the authentication token from the SSO platform. Users will be able to login using different browsers and to all ICM Add-ins.	+	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.
−	This integration implementation is flexible enough to enable connection with other identity providers that use the OpenID Connect protocol.	+	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;
−	&nbsp;	+	<span style="color:#800080;">'''727314 – A generalized framework to support additional languages in AI apps'''</span>
−	'''<span style="color:#008000;">467179 – SFDC experience enhancements – simplified UX - action in grid</span>'''&nbsp;&nbsp;	+	In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.
−	The Icertis Experience for Salesforce already provides the capability for Salesforce users to perform agreement-related tasks from within Salesforce.	+	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;
−	ICM is now improving the user experience such that Salesforce users can perform their tasks more seamlessly by taking actions on agreements with fewer clicks than required earlier.	+	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;
−	The user will now be able to view a contract record by double-clicking the row, instead of the earlier option of clicking the ''View'' hyperlink. They will be able to take ''Download, Assemble Contract'' and ''Send for Approval'' actions directly from the ''Action'' column of the Contract grid on Salesforce entity forms, without opening the agreement record. These actions will be displayed to the user based on the workflow state of the agreement.	+	== Reports Enhancement Details ==
		+	<span style="color:#800080;">'''514593 – Introducing the&nbsp;Tagged Attributes Report'''</span>
		+
		+	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.<br/> &nbsp;
		+
		+	<span style="color:#800080;">'''769602 – Displaying clause extension attribute summary in the Clause Summary Report'''</span>
		+
		+	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.&nbsp;<br/> &nbsp;
		+
		+	<br/> <span style="color:#800080;">'''514611 – Introducing the&nbsp;Notifications History Report'''</span>
		+
		+	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;
		+
		+	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:#008000;">537762 – SFDC experience enhancements – improved search functionality</span>'''	+	<span style="color:#800080;">'''742607 – Providing additional localization support in reports'''</span>
−	Previously, there were 2 separate sub-tabs, 1 each for Contracts and Contract Requests, under the ICM tab within Salesforce. The previous ''Search ''page when rendered from within an iFrame inside Salesforce, gave the user a perception that they are working outside of Salesforce application.	+	With this release, localization support will be provided in the Core platform, Sourcing, Obligation Management, and Insights SSRS report, in the following areas:&nbsp;
−	With the SFDC experience enhancement, the user will have the ability to:	+	*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;
−	*Search for contracts or contract requests from a common page.	+	<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span>
−	*Provide search conditions to limit their search.	+
−	*View both contract and contract request&nbsp;records as a result set, on the same page, depending on the selection criteria.	+	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;
−	*View ICM saved searches, and refine searches based on metadata and full text.	+
		+	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.
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">537766 – Reporting capability within Salesforce</span>'''	+	<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>
−	Icertis Experience for Salesforce already provides the capability for Salesforce users to execute contract management tasks from within Salesforce.	+	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.
−	Now, this capability has been enhanced by allowing users to access ICM's reports within Salesforce instead of having to login to ICM to do so.	+	With this release, an “Organization Unit” filter is being introduced in this report for users to derive the desired information.
−	Providing the ''Reports'' tab within the ICM tab of Salesforce radically simplifies tasks for the users as well as increases the productivity many folds. Based on their authorization, users can view and execute ''Default'' and ''Custom'' ''Reports''.
−	<div class="image-green-border">[[File:7.11 Release Notes 28.png|720px|7.11 Release Notes 28.png]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">556549 – Enabling existing adapter functionality in the new MS Dynamics unified interface</span>'''	+	<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>
−	Microsoft has released a new unified interface for Dynamics CRM. Earlier, ICM Experience for MS Dynamics offered an iFrame based solution to embed the ICM application within MS Dynamics 365. With this release, ICM is making the iFrame fully responsive to the new unified interface, so that users have a seamless experience across various form factors.	+	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;
	&nbsp;		&nbsp;
		+
		+	== Integration Details ==
		+
		+	<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>
		+
		+	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.&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;
−	== ICM Platform Tools ==	+	<span style="color:#800080;">'''751651 – Publishing success/failure notification message on ASB post data sync from Salesforce'''</span>
−	'''<span style="color:#008000;">519481 – Introducing the ICM Tools portal</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, ICM introduces the new ICM Tools portal for easier instance management and improved productivity. This release launches two tools—''Configuration Key'' and the ''Redis Flush'' functionality.	+	With this release:
−	Earlier, the ICM platform instance configuration keys were modified by the Solutions Engineering/DevOps teams, and even minor configuration changes took considerable time. The ''Configuration Key tool'' has been introduced so that a logged in user (who has access to Azure subscription) can search and update configuration keys as required.	+	*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;
−	Once the key values are changed, the cache is automatically updated to avoid the server restart. The tool only works for non-production environments. The production environment configuration changes are controlled by Operations team, and the tool would not be available for production environment.	+	<span style="color:#800080;">'''796155 –&nbsp;Enhancements to the data flow between Salesforce/MS CRM and ICI'''</span>
−	The ''Redis Flush'' is a self-service tool which allows Administrators to flush the cache or look up a particular key for its value of ''Delete a Key''. The tool can also be used to perform Role Restart on the instances to which the user has access.	+	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.
−	<div class="image-green-border">[[File:7.11 Release Notes 29.png|720px|7.11 Release Notes 29.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">547429 – Introducing the Translations Editor Tool</span>'''	+
−	The ICM platform is available in different languages and different languages label text are available&nbsp;for&nbsp;localization. However, to make any changes to the localization values, users had to reach out to the Solutions Engineering or Database teams. Sometimes, these changes were minor and of low complexity, but the turnaround time was substantial.	+	With this release:
−	Hence, a self-service ''Translations Editor'' tool has been introduced that contains all strings that are localized. Users can now download all keys and their localization values as an Excel file, modify multiple values, and upload the modified changes to ICM. Once the values are updated in ICM, the caches are updated automatically to avoid the cache flush and server restart. This has significantly enhanced productivity as the turnaround time to update the Resource Key values has been eradicated.	+	*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;
−	Using this tool, users can now:	+	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.
−	*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.	+	<br/> <span style="color:#800080;">'''674469 – Generating ICI notifications and enhancing Salesforce data sync'''</span>
−	*Update multiple language strings by selecting and saving the Resource Key value.	+
−	*Download and upload the localization key values using Microsoft Excel.	+
−	*View the modified values in the ICM instance immediately.	+
−	<div class="image-green-border">[[File:7.11 Release Notes 30.png|720px|7.11 Release Notes 30.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">519630 – Improved ICM Health Check</span>'''	+
−	The ICM platform hosted on Azure Cloud uses services such as Elastic Search, Redis, along with internal components such as APIs and Task services. However, no services were used to provide an insight on the application health except for the ''ICM Health Check'' page that provided regular application health checks and application monitoring to be able to detect issues before they became full-fledged outages.	+	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;
−	The ''ICM Health Check'' page has been further enhanced to cover additional parameters to help identify potential outages and diagnose issues. The health insights provide information on how well the ICM instance and its service is performing, its overall health, as well as its usefulness to users. Users will now be able to access a dashboard (without logging into ICM) that tracks application health alongside usage metrics and application crash data.	+	With this release:
−	The health statuses are classified into three categories:	+	*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;
−	*''Warning ''- indicated by a yellow warning icon	+	<br/> <span style="color:#800080;">'''679797 –&nbsp;Supporting JWT Bearer OAuth flow in Salesforce adapter with added support for Modified By use'''</span>
−	*''Healthy'' -&nbsp; indicated by a green checkmark icon	+
−	*''Unhealthy'' - indicated by a red warning icon	+
−	The following details are displayed in the Health Check:	+	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;
−	*'''Elastic Search Health''': displays the Status (yellow/green/red), the Elastic Search version, the Uptime, and so on.	+	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;
−	*'''Redis Cache Health''': displays the Redis version, Uptime In Days, CPU usage, Connections Received and Commands Processed, and so on.	+
−	*'''API Health''': displays the API Response Time, Status and Issues, and so on.	+
−	*'''Database Server Metrics''': displays the CPU usage percentage, User Connections, Total Server Memory, Disk Read/Write IO/Sec, and so on.	+
−	*'''IIS Server Metrics''': displays&nbsp;% 404 HTTP Response Sent,&nbsp;% 500 HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on.	+
−	<div class="image-green-border">[[File:7.11 Release Notes 31.png|720px|7.11 Release Notes 31.png]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">553394 – Enhancement to search sync</span>'''	+
−	Previously, the ''Search Sync'' task available in ICM under ''Admin Tasks'' provided the ability to sync from the database into Elastic Search (ES) for the respective instance. For this, the ''SysId'' could be provided as input CSV file or as comma separated. However, this tool did not provide the capability to check the value stored in ES for a key using the key name. Several times, users would keep syncing the ''SysId'' assuming that the data is not updated in ES.	+	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;
		+
		+	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.
−	With this feature, users can now get data from elastic search for a given instance’s ''SysId'', so that they can look up the value and identify whether it is the latest or if a sync is needed. If the key exists, the latest value from ES will be displayed. If the key does not exist, the system will display the error message ''Could not fetch value for provided SysId''.
−	<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div>
	&nbsp;		&nbsp;
		+	<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>
−	== Technical Requirements for Release 7.11 ==	+	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;
−	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 on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below:	+	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;
−	[[File:7.11 Release Notes Technical Requirements 001.png|720px]]	+	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;
−	[[File:7.11 Release Notes Technical Requirements 2.png|720px]]	+	== ICI Platform Tools Details ==
−	[[File:7.11 Release Notes Technical Requirements 03.png|720px|7.11 Release Notes Technical Requirements 03.png]]	+	'''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''
−	[[File:7.11 Release Notes Technical Requirements 4.png|720px]]<br/> [[File:7.11 Release Notes Technical Requirements 05.png|720px|7.11 Release Notes Technical Requirements 05.png]]	+	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.
−	&nbsp;	+	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;
		+
		+	== Partner Enablement ==
		+
		+	<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>
		+
		+	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;
		+
		+	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;
−	== Known Issues for Release 7.11 ==	+	== Technical Requirements for Release 7.15 ==
−	'''<span style="color:#008000;">480546 – Loading issues when Require SSL set to True and Client certificates enabled as Accept</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;
−	<div class="image-green-border">When the following settings are enabled on the environment - Require SSL to True and Client certificates is enabled as Accept (instead of Ignore) in IIS for API site, office.JS Word Add-In does not load in Internet Explorer. This issue occurs when using Internet Explorer, Windows 10 version < 1903 and Office version < 16.0.11629.&nbsp;</div> <div class="image-green-border"><br/> [[File:7.11 Release Notes Known Issues 1.png|720px|7.11 Release Notes Known Issues 1.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">Note: On MAC OS, this issue is not applicable.</div>	+
−	'''Workaround'''&nbsp;	+
−	The two workarounds available for the issue:&nbsp;<br/> It is recommended to Upgrade Windows 10 version > = 1903 and Office 365 version > = 16.0.11629 by end user.<br/> Change IIS setting For API site to SSL Settings -> Uncheck Required SSL and Client certificates to Ignore.	+	The software and hardware requirements for the client system as well as mobile application are listed in the table below.
−	'''<span style="color:#008000;">579215 – Lookup filtering not working when configured on multi-select lookup string attribute</span>'''&nbsp;&nbsp;<br/> This is with reference to the new feature 541976 – Ability to configure and apply multiple filters while referring value from any master records (in ICM Application Enhancements), developed in 7.11.	+	[[File:7.15 Technical Requirements - Operating Systems.PNG|720px|7.15 Technical Requirements - Operating Systems]]
−	While defining the lookup filter, if the source and target are multi-select string lookup and dynamic filter is configured for target attribute, the filtering will not work. No values will be displayed for target attribute in drop-down as well as the lookup popup.	+	[[File:7.15 Technical Requirements - Browser Compatability Matrix.PNG|720px|7.15 Technical Requirements - Browser Compatibility Matrix]]
−	'''Workaround'''	+	[[File:7.15 Technical Requirements - Other Requirements.PNG|720px|7.15 Technical Requirements - Other Requirements]]
−	Currently, there is no workaround for this defect. However, it has been found that there is no strong business use case yet that required such configuration.	+	[[File:7.15 Technical Requirements - Smartphone Mobile App.PNG|720px|7.15 Technical Requirements - Smartphone Mobile App]]
−	<br/> '''<span style="color:#008000;">589456 – In agreement Versions tab, Content Control Difference panel not displaying the association-updated record if association document is created/modified under peer association</span>'''&nbsp;&nbsp;	+	[[File:7.15 Technical Requirements - Special Requirements 1.PNG|720px|7.15 Technical Requirements - Special Requirements 1]]
−	This is with reference to the new feature 488577 – Document upload validation displays the changes in associations tagged as file(s) (in ICM Application Enhancements), developed in 7.11.&nbsp;<br/> In the agreement ''Versions'' tab, ''Content Control Difference'' panel is not displaying association updated record if peer association is tagged as file where peer associated document contains saved search as table, association as table, association as file tags. This behavior is also for document assembly and upload scenario ''Content Control Difference'' popup.	+	[[File:7.15 Technical Requirements - Special Requirements 2.PNG|720px|7.15 Technical Requirements - Special Requirements 2]]
−	'''Workaround'''	+	[[File:7.15 Technical Requirements - Special Requirements 3.PNG|720px|7.15 Technical Requirements - Special Requirements 3]]
−	To compare the differences, the user can download the comparison document of the parent agreement and review the changes.	+	[[File:7.15 Technical Requirements - MS Office Plugins 1.PNG|720px|7.15 Technical Requirements - MS Office Plugins 1]]
−	'''<span style="color:#008000;">597869 – In office.JS Word Add-In, Clause preview not displaying in MS Edge browser as default view on Mac</span>'''&nbsp;&nbsp;	+	[[File:7.15 Technical Requirements - MS Office Plugins 2.PNG|720px|7.15 Technical Requirements - MS Office Plugins 2]]
−	In office.JS Word Add-In, Clause preview is not displayed in Microsoft Edge browser as default view on Mac OS.	+	[[File:7.15 Technical Requirements - Security.PNG|720px|7.15 Technical Requirements - Security]]
−	'''Workaround'''&nbsp;	+	&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;
−	User can navigate to ICM to see preview of the respective clauses.	+	'''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 04: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 |