Revision as of 03:24, 30 March 2020 (view source) IDT-1 (Talk | contribs) ← Older edit		Latest revision as of 13:09, 29 September 2022 (view source) IDT-1 (Talk | contribs)
(250 intermediate revisions by 7 users not shown)
Line 1:		Line 1:
−	= ICM Release Notes - Release 7.11 =	+	= ICI Release Notes - Release 8.2 =
		+	Apart from new features and enhancements, this document contains information on:
		+	*[[#_Technical_Requirements_1|Technical Requirements]]
		+	*[[#_Accessibility_Conformance|Accessibility Conformance]]
		+	*[[#_Known_Issues|Known Issues]]
−	== Overview of Release 7.11 ==	+	Refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Help Wiki] documentation (also found in your ICI help section) for details on all ICI features and functionalities.
−	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.	+	= New Features and Enhancements =
−	The key enhancements of this release include:	+	== Contract Authoring & Management  ==
−	*'''Enhancements to Business Applications'''
−	**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.
−	**Certifying that ICM is now able to support multiple business applications with reference to functionality, performance and security, to drive business compliance.
−	**Extending support of multiple rulesets for event rules, for any entity, per event.
−	**Locking business rules that were critical to the flow of the application are now locked by the service users when deploying the Obligation Management application preventing other users to unlock, edit and modify these rules, thus ensuring a smooth workflow. 
−	*'''Enhancements to the ICM Application'''
−	**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.
−	**Enhancing the ICM dashboard to provide a framework for configuring a new dashboard layout, and provide support for a widget for all the Saved Search, Task List and My Recent activities widgets. In addition, the support is also extended to use the earlier KPI based dashboard, resize the widget, and re-order the widget sequence.
−	**Introducing a Pre-Publish Checker tool on the User Administration tile that will analyze all the checkpoints which potentially result in downtime and provides failure information to the configurators, thus allowing users to take appropriate actions.
−	**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.
−	**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 apply multiple filters while referring value from any master records. These filters can either be predefined or can even be based on the attribute values that are being selected as the user enters the details.
−	**Allowing configuration of a flexible entity which enables users dealing with different types of items (such as line items in sourcing) to define and create entities based on business requirements.
−	**Enabling users to create multiple agreements from a single agreement by flagging the Bulk Agreement option to ''On'' at the contract type level.
−	**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.
−	**Allowing the contract type description to be available when creating the contract type instance, so that users can easily identify the type of contract type that fulfills the requirement.
−	**Providing the ability to exclude attributes or associated documents when copying agreements and allowing the copying of commitments when copying the RFQ/Agreement.
−	**Providing the flexibility to configure role for commitment business owner while adding the user to the team, and configure reminder notifications on date parameters.
−	**Auto-populating the currency while creating entities, retaining the original file name of the uploaded files in ICM, updating the count of entities without refreshing the page.
−	**Allowing replacing of the alternate clause from the Clause Comparison Report, allowing download-upload validation to display the clause deviations as well as the changes included in associations assembled in the document, displaying clause comparison on the first version of the agreement, enhancing KPI reports performance.
−	**Allowing copy team role mapping by copying team from the contract request, agreement, amendment to its association, capturing the rule condition based on which a user has been added to the team, generating a redlined version for comparing agreement versions, providing Administrators the ability pin the necessary saved searches for external users/suppliers.
−	*'''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''' <ul style="list-style-type:circle;">
−	</ul>  </ul>
−	*Allowing users to stay on the document for further edits or reviews while publishing is happening in the background.	+	=== Amend contracts preserving previously negotiated terms ===
−	*'''Enhancements to Artificial Intelligence Applications''' <ul style="list-style-type:circle;">	+	'''What''' – When users amend a contract, they now have a choice to either use the base agreement or a previously negotiated and amended contract. Along with the contract version, users can also choose the associations to copy to the amendment.
−	<li>Introducing eDiscovery to derive critical insights by analyzing legacy contracts.</li>	+
−	<li>Introducing ''Risk AI'' 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.</li>	+
−	<li>Improved accuracy of AI models by incorporating user action feedback when the user is interacting with the attribute discovery in ''DiscoverAI'' and ''NegotiateAI'' apps.</li>	+
−	<li>Identifying important terms in contracts (contract highlights) using AI for different personas like legal, CxOs, finance, etc.</li>	+
−	<li>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.</li>	+
−	<li>Introducing NLP-based search query for Agreement entities.</li>	+
−	</ul>  <li>'''Enhancements to Reports'''	+
−	*Introducing the Obligations Management Dashboard 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 and Fulfilments overdue by the owner, and the OMH – Obligation Management Health Report that provides an overall view of the total Fulfillments across all agreements that are fulfilled. </li>	+
		+	'''Advantages''' – Maintaining a history of the original agreement and all amendments is now possible. This helps in auditing the changes made to contracts over time.
−	*'''Improving the Icertis Experience ''' <ul style="list-style-type:circle;">	+	'''How''' – Options to choose the amendment and copy associations to the amendment are now available when creating an amendment. Users can associate and inherit documents such as NDA, SOW, etc.
−	</ul>  </ul>	+
−	*Building the Secure File Transfer Protocol (SFTP) adapter 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.&nbsp;	+	'''Value''': Compliance | User Experience<br/> '''For''': Legal Team | Authors | Contract Managers<br/> '''Feature ID''': 1233193
−	*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 user 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''' <ul style="list-style-type:circle;">	+	=== Send multiple agreements packaged in a single envelope for electronic signature ===
−	<li>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.</li>	+
−	<li>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.</li>	+
−	<li>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.</li>	+
−	<li>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.</li>	+
−	</ul>  </ul>	+
−	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.	+	'''What''' – Earlier, agreement could be bundled only with its associations and sent for electronic signature. With this release you can also bundle peer agreements in a single package for electronic signing.
		+	'''Advantages – '''Eliminates the need to send one agreement at a time for signature, thereby saving time. Provisions setting a sequence in which the agreements must be signed and facilitates reordering if required.
−	== Icertis Business Applications ==	+	'''How - '''Existing Esign functionality is enhanced to package peer agreements as a single bundle and send it for electronic signature.
−	'''<span style="color:#008000;">448830&nbsp;– Integrating ObligationAI with Obligation Management app&nbsp;</span>'''	+	'''Value''': User Experience | Contract Building Performance<br/> '''For''': Contract Owners | Legal Compliance Team<br/> '''Feature ID''': 1369302
−	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.	+	=== Quickly create and edit contract types in bulk using excel workbook ===
−	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:	+	'''What''' – ICI now allows its users to edit and create contract types in bulk using the Microsoft Excel workbook. User can also edit multiple attributes for multiple contract types at once.
−	*Reducing time and efforts to discover and create obligations.	+	'''Advantages'''
−	*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.	+	Contract type (CT) changes happen frequently in the implementation phase, the feedbacks from the customers regarding the changes in the CT have to be earlier implemented one by one for each CT in ICI UI. Now, this changes and edits can be done in one go using this feature.
−	<div class="image-green-border">[[File:7.11 Release Notes 01.png|720px]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">508359&nbsp;– Multi-app testing (Sourcing, Obligation Management) configured and running in the same environment</span>'''	+
−	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.	+	Creating and editing multiple contract types at once will reduce time involved in configuring large contract types.
−	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.	+	'''How'''
−	<div class="note-box">'''Note''': ICM will now support platform and business applications with same version number.</div>	+
−	&nbsp;	+
−	'''<span style="color:#008000;">545742 – Extending support of multiple rulesets for event rules</span>'''	+	A button “Bulk Contract Type” is now added under “Configure” tile.
−	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.	+	Users can generate pre-seeded contract type workbook, with 2 tabs in excel, contact type, and contract type attributes.
−	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.	+	'''Value''': User Experience<br/> '''For''': Admins | Legal Team | Contract Managers<br/> '''Feature ID''': 1342050
−	<div class="image-green-border">[[File:7.11 Release Notes 02.png|720px]]</div>	+
−	With this release, an Administrator can now:	+
−	*Create multiple rulesets for event rules, for any entity, per event.	+	== Icertis Experiences ==
−	*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.	+
−	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.	+	=== Rules functionality added to Icertis Experience for Word ===
−	<div class="image-green-border">[[File:7.11 Release Notes 03.png|720px]]</div>	+
−	The ''Stop Processing More Rules ''option when selected as ''Yes ''allows users to stop evaluating the rules within the ruleset.	+
−	&nbsp;	+	'''What''' – Users can now create rules for assembling the clause and define the rules for selecting the template from within Microsoft Word to display clauses in agreements based on specified conditions. Existing rules can also be viewed or edited from Microsoft Word.
−	'''<span style="color:#008000;">545763 – Non-editable seeded business rules</span>'''	+	'''Advantages – '''Provides a familiar and intuitive interface for legal teams and contract authors to create conditional agreement templates.
−	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.	+	Reduced turnaround time, instead of switching while creating the clause and template
−	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.	+	'''How – '''Users can define conditions for selecting a clause or template while assembling of clauses and selection of templates from Microsoft Word.
−	<div class="note-box">'''Note''': Even if the rulesets are locked, you can create new rulesets for event rules.</div>	+	<div class="image-green-border">[[File:8.2 RN 01.png|300px|8.2 RN 01.png]]&nbsp;&nbsp;[[File:8.2 RN 02.png|300px|8.2 RN 02.png]]</div>
−	&nbsp;	+	'''Value''': User Experience<br/> '''For''': Legal Team<br/> '''Feature ID''': 1117626
−	<div class="image-green-border">&nbsp;[[File:7.11 Release Notes 04.png|720px]]</div>	+
		+	=== Outlook Add-in – Labeling and validation for emails added to ICI ===
−	== ICM Application Enhancements ==	+	'''What – '''Every email uploaded in ICI will now display an Outlook category label, that helps users know if the email is already added in ICI. Additionally, a validation is also displayed if user tries uploading same emails twice. Users can customize the outlook category label as per the needs.
−	'''<span style="color:#008000;">532684 – Navigation Enhancements</span>'''	+	'''Advantages – '''Avoid uploading duplicate email conversations in ICI.
−	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.	+	'''How – '''This feature is available as part of Icertis Experience for Outlook.
		+	<div class="image-green-border">[[File:8.2 RN 03.png|600px|8.2 RN 03.png]]</div>
		+	'''Value''': User Experience<br/> '''For''': Contract Managers | Legal Teams<br/> '''Feature ID''': 1341557&nbsp;
−	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.	+	=== Revamping ICI Salesforce User Experience ===
−	'''Note:'''	+	'''What''' – Revamping the ICI Salesforce user interface to give a better user experience, with addition of features and enhancement under agreement related sub tabs.
−	*Users can now navigate from any page in ICM to any other page, thus eliminating the need for multiple page loads.	+	The following agreement sub tabs can now be seen with new capabilities:
−	*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]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:7.11 Release Notes 06.png|720px]]</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.	+	*Associations sub tab
−	<div class="image-green-border">[[File:7.11 Release Notes 07.png|720px]]</div>	+	*Amendment sub tab
−	The widget-based dashboard offers the following widgets:	+	*Note sub tab
		+	*Team sub tab
		+	*Collaboration sub tab
−	*'''Performance Metric:''' displays all the KPIs to which the user has access. These include Saved Search KPIs and Report KPIs.	+	Some new features include:
−	*'''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.	+
−	*'''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.	+
−	*'''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).	+
−	*'''Saved Search:''' displays the searches saved on the ''Search'' page.	+
−	&nbsp;	+	Hyperlink added in the first column of the association list grid navigating to the association details page within ICI Salesforce platform.
−	'''<span style="color:#008000;">519472 – Introducing the Pre-Publish Checker Tool</span>'''&nbsp;	+	Ability to preview the document from amendments sub tab.
−	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.	+	The collaborations tab is now revamped from ICI Iframe to Salesforce native look and feel, with capability to view more messages.
−	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.	+	'''Advantages '''– This revamp will be giving a more consistent and familiar user experience with enhanced look and feel inline with Salesforce native user experience across tabs, subtabs and actions for sales personas.
−	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.	+	'''How''' – Below are few screenshots of the revamped ICI Salesforce platform.
−	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.	+	New ICI Salesforce Agreement Details screen
		+	<div class="image-green-border">[[File:8.2.RN 1.png|720px|8.2.RN 1.png]]</div>
		+	New Add Note Dialog box
		+	<div class="image-green-border">[[File:8.2.RN 2.png|720px|8.2.RN 2.png]]</div>
		+	'''Value''': User Experience<br/> '''For''': Sales Team<br/> '''Feature ID''': 1356012
−	Administrators can now:	+	=== Salesforce – Visibility of products and services sold to customers ===
−	*View the pre-publish checklist items in case of failures.	+	'''What''' – ICI Salesforce experience users can now view the list of all the products and services sold to the customer under “Agreement Lines” subtab.
−	*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">[[File:7.11 Release Notes 08.png|720px]]</div>	+
−	&nbsp;	+
−	'''<span style="color:#008000;">541970 –&nbsp;Assembly of associated documents into the main agreement based on a defined order</span>'''	+	'''Advantages – '''With visibility to Agreement lines through this feature, Sales Executives will be able to identify Cross-sell, up-sell opportunities to pursue relevant sales, and request amendment to appropriate contract.
−	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.	+	'''How – '''A new subtab “Agreement Lines” is added for account object displaying all the active product and services sold to the customer. The products displayed under agreement line subtab are fetched via ICI saved searches.
−	<div class="image-green-border">[[File:7.11 Release Notes 09.png|720px]]</div>	+	<div class="image-green-border">[[File:8.2.RN 3.png|720px|8.2.RN 3.png]]</div>
−	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.	+	'''Note: '''The “Agreement Lines” displays only active products and services from executed contracts.
−	<div class="image-green-border">[[File:7.11 Release Notes 10.png|720px]]</div> <div class="note-box">'''Note:''' If saved search is not configured or not tagged along with the association, ICM behaves as-is.</div>	+
−	&nbsp;	+
−	<div class="image-green-border">[[File:7.11 Release Notes 11.png|720px]]</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.	+	'''Value''': User Experience<br/> '''For''': Sales Managers | Sales Executive<br/> '''Feature ID''': 1192973
−	With this release, the following enhancements have been made for:	+	== Enhancements – Mobile App Experience ==
−	*Vulnerability and Penetration Testing (VAPT) fixes.	+	[[File:8.2 RN 32.PNG|720px|8.2 RN 32.PNG]]
−	*Testing open bugs in PToP engine.	+
−	*Some new validations in the PToP engine.	+
−	*Better user interface to provide support to PToP and DevOps teams.	+
−	&nbsp;	+	== Administration & Configuration ==
−	'''<span style="color:#008000;">541976 – Ability to configure and apply multiple filters while referring value from master records</span>'''	+	=== Enhanced ICI startup validation architecture ===
−	Earlier, ICM provided the capability of filtering records on the basis of a single attribute using cascading.	+	'''What''' – A new validation framework for configuration keys and related metadata to resolve incorrect or missing keys and ensure seamless startup of ICI instances.
−	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.	+	'''Advantages – '''Timely validation of configuration keys and guardrails to prevent unnecessary startup blockers.
−	Users can now:	+	'''How – '''At startup, the validation framework checks for configuration keys that are inconsistent or incorrect and restores those to default values thereby preempting any startup issues. Technical admins can view and investigate the validation logs on the self-service portal.
−	*Define UI based configuration for multiple static and dynamic filters for the referred masterdata.	+	'''Value''': Reliability, Supportability<br/> '''For''': Administrators<br/> '''Feature ID''': 1373024
−	*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]]</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.	+	=== Configure E-Signature Integrations within ICI ===
−	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.	+	'''What''' – E- signature configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
−	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.	+	'''Advantages '''– This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
−	Users now:	+	'''How''' – Technical administrators can configure E- sign providers (DocuSign and AdobeSign) from the E-sign configuration page.
		+	<div class="image-green-border">[[File:8.2 RN 04.png|720px|8.2 RN 04.png]]</div>
		+	'''Value''': Self-service<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180879
−	*Can create rules to attach masterdata attributes (single or multiple) to your associated documents and agreements based on certain conditions.	+	=== Integrated Config keys validation framework ===
−	*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>'''	+	'''What''' – ICI now has the capability to check incorrect values, difference in data types, and inconsistency in configuration data. The utility can be run prior to starting an application and the report and errors reported can be used to help find a solution.
−	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.	+	'''Advantages – '''Helps prevent issues that occur during application startup.
−	Users now:	+	'''How – '''At the start of an ICI instance, the disparity in the configuration keys is identified, and the incorrect keys are set to the default value. All such changes are recorded in the self-service portal so that the technical admins can investigate the errors.
−	*Have complete flexibility at configuration level to define the applicable contract type, decision attribute, compute attribute for bulk agreement creation.	+	'''Value''': Self-service &nbsp;<br/> '''For''': Administrators<br/> '''Feature ID''': 1373030
−	*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;	+	=== Configure SSO integrations within ICI ===
−	'''<span style="color:#008000;">541982 – Ability to support approver sub-roles</span>'''	+	'''What''' – SSO configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.
−	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. This can be achieved through a technical configuration.	+	'''Advantages '''– This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team.&nbsp;
−	'''<span style="color:#008000;">541979 – Ability to filter agreements available for inheritance</span>'''	+	'''How''' – Technical administrators can configure SSO integrations (SAML, WS-Fed and O-Auth) from the SSO configuration page.
		+	<div class="image-green-border">[[File:8.2 RN 05.png|720px|8.2 RN 05.png]]</div>
		+	'''Value''': Self-service &nbsp;<br/> '''For''': Technical admins<br/> '''Feature ID''': 1180896
−	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.	+	=== Customer-specific SAML/OAuth SSO Configurations ===
−	This is achieved through a technical configuration at the contract type level.	+	'''What – '''In a multitenant instance of Icertis Contract Intelligence, SSO configurations are now moved from a single configuration file to separate configuration files for each tenant. These configurations can now also be modified from within Icertis Contract Intelligence.
−	<div class="image-green-border">[[File:7.11 Release Notes 13.png|720px]]</div>	+
−	&nbsp;	+
−	'''<span style="color:#008000;">549081 – Availability of contract type description during contract type instance creation</span>'''	+	'''Advantages''' –
−	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;	+	*Site reliability and stability - SSO issues affecting one tenant do not impact other tenants.
−	<div class="image-green-border">[[File:7.11 Release Notes 14.png|720px]]</div> <div class="image-green-border">&nbsp;</div>	+	*Self-service - Technical admin users can configure SSO without intervention from Icertis teams.
−	'''<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:	+	'''How – '''Users with the right permissions can make SSO configuration changes from the Tenant.config file. The changes can also be made from within ICI by Technical Admin users.
−	*Exclude associated documents from getting copied.	+	'''Value: '''Self-service, Reliability, Supportability<br/> '''For:''' Technical Admins<br/> '''Feature ID: '''1317384
−	*Exclude the attributes of selected associated documents.	+
−	*Select and copy Commitments.&nbsp;	+
−	*Exclude the attributes of selected Commitments.	+
−	<div class="note-box">'''Note''': The exclusions above are achieved through a technical configuration at the contract type level.</div>	+
−	&nbsp;	+
−	<div class="image-green-border">[[File:7.11 Release Notes 15.png|720px]]</div>	+
−	'''<span style="color:#008000;">551101 – Ability to configure role for commitment when adding user to the team</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.).	+	=== Error-handling framework ===
−	<div class="note-box">'''Note''': This is achieved through a technical configuration at the contract type level.</div>	+
−	&nbsp;	+
−	'''<span style="color:#008000;">466694 – Ability to configure reminder notifications on entities</span>'''	+	'''What '''– A centralized and industry-standard error handling framework for faster troubleshooting, analysis and resolution of issues. The list of error codes and related data is cataloged & documented, which will act as a standard reference for all error codes in the ICI platform.
−	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.	+	The framework provides the following features:
−	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).	+	Detailed and structured data to determine severity, origin, module, area & source of the error.
−	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, user experience in addition to reducing efforts of technical configuration for task reminders.	+	No unhandled exceptions emanating from the system.
−	Users can now:	+	Detailed logging is done in a central repository like Kibana.
−	*Set reminder notification for agreements, amendments and associations.	+	For ICI Instances where AppInsights is available, a correlation id helps to track calls and correlate the complete chain of events that led to the error.
−	*Configure a template for reminder notification.	+
−	*Set the reminder notification based on Event Rule.	+
−	*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.	+
−	<div class="image-green-border">[[File:7.11 Release Notes 16.png|720px]]</div>	+
−	'''<span style="color:#008000;">551103 – Auto-populating the currency when creating entities</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''Preferred Currency'' option in ''My Preferences''. Based on the user preference, the selected currency will be auto-populated for any Currency attribute.	+	'''Why '''– Eliminates time required to locate and understand the issue and reduces the overall time needed to fix issues.
−	<div class="image-green-border">[[File:7.11 Release Notes 17.png|720px]]</div>	+
−	&nbsp;	+
−	'''<span style="color:#008000;">551104 – Ability to retain original filename of uploaded files</span>'''	+	'''How '''– ExceptionHandler attribute is introduced, which will have following Origin, Area, Module, Sub Module in the form of code.
−	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.	+	For example: 50000030021360X8013153 (shown on User Interface)
−	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 achieved through a technical configuration and applicable to agreements, amendments, associations, and file attributes in agreements/associations.	+	Breakdown of the code is as follows:
−	<div class="image-green-border">[[File:7.11 Release Notes 18.png|720px]]</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.	+	5 – Severity
−	&nbsp;	+	00 – Origin (First parameter of Exception Handling attribute)
−	'''<span style="color:#008000;">488574 &nbsp;– Replace primary clauses with alternate clauses from Clause Comparison Report</span>'''	+	00 – Source (mostly internal)
−	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.	+	03 – Area (Second parameter of Exception Handling attribute)
−	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.	+	002 – Module (Third parameter of Exception Handling attribute)
−	Users can:	+	136 – SubModule (Fourth parameter of Exception Handling attribute)
−	*View the ''Select Alternate Clause'' link in the Clause Comparison Report.	+	0X8013153 – Standard C# HResult which can be googled to see the exception type
−	*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.	+
−	&nbsp;	+	Class decorators for Exception Handling
−	'''<span style="color:#008000;">488577 – Document upload validation shows the changes in associations tagged as file(s)</span>'''	+	['''ExceptionHandler''' (exceptionOrigin: ExceptionOrigin.Core, exceptionArea: ExceptionArea.CLM, module: ExceptionAreaModule.CLM_AdminTask, submodule: ExceptionAreaSubModule.CLM_AdminTask_Root)]
−	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.	+	When an error occurs, the error code is displayed on the error message, see the screenshot below.&nbsp;&nbsp;
		+	<div class="image-green-border">[[File:8.2 RN 33.PNG|400px|8.2 RN 33.PNG]]</div>
		+	'''Value: '''Supportability<br/> '''For: '''Partner Developers | Any Application User | Troubleshooters<br/> '''Feature ID''': 1373034
−	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;	+	=== Administration & Configuration Enhancements ===
−	The following actions take place as soon as a new agreement version is uploaded:	+	[[File:8.2 RN 34.PNG|720px|8.2 RN 34.PNG]]
−	*The version being uploaded is compared with the latest version available in ICM.	+	== Reporting Analysis ==
−	*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. The support for the same can be extended through a technical configuration.	+	=== Dashboard and Power BI reports for Supplier Evaluation ===
−	<div class="image-green-border">[[File:7.11 Release Notes 19.png|720px]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">535845 – Ability to identify the first version of an agreement in the Clause Comparison Report</span>'''	+
−	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.	+	'''What – '''An interactive Supplier Evaluation dashboard with the following features is now available out-of-the-box:
−	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.	+	Interactive graphs for status of evaluation cases, evaluation distribution by performance, and ageing in review or approval states.
−	<div class="image-green-border">[[File:7.11 Release Notes 20.png|720px]]</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.	+	Enlists the top and poor performing suppliers based on a host of filters like evaluation type, period of evaluation, supplier name and more.
−	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.	+	Captures evaluations that are awaiting supplier inputs for missing documents.
−	Users can now:	+	360-degree supplier performance score card about different evaluations, KPI and performance trend over a time period.
−	*Copy the entire team of the entity (''Contract Request, Agreement, Amendmen''t) to its defined Association entity on a specific role (such as ''Observer)''.	+	Capture supplier documents/ certificates that are expired or expiring within 5 days.
−	*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]]</div>	+
−	&nbsp;	+
−	'''<span style="color:#008000;">560209 – User inclusion condition visibility in team</span>'''	+	'''Advantages –'''
−	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.	+	Information is represented visually and is easier to consume and track.
−	<div class="image-green-border">[[File:7.11 Release Notes 22.png|720px]]</div>	+
−	If a user has been added by a rule, the value ''Yes'' is displayed in the column with a hyperlink. 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.'' 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.	+
−	<div class="image-green-border">[[File:7.11 Release Notes 23.png|720px]]</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.	+	Assist the procurement team in setting up the right expectations and manage supplier relationships.
−	<div class="image-green-border">[[File:7.11 Release Notes 24.png|720px]]</div> <div class="image-green-border">&nbsp;</div>	+
−	'''<span style="color:#008000;">560728 – Global favorites – supplier view</span>'''	+
−	Previously, ICM users created favorites for specific users as per domain or organizational group, however, these favorites were not accessible to all users in the domain.	+	Insights into poorly performing suppliers can help in planning proactive performance improvement.
−	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.	+	'''How – '''The dashboard and reports can be accessed from the Supplier Management -> Dashboard.
−	Administrators can now:	+	'''Pre-requisite''': HTTP Artifact binding should be supported by the respective IDP server to enable this feature.
		+	<div class="image-green-border">[[File:8.2 RN 15.png|720px|8.2 RN 15.png]]</div>
		+	'''Value: '''Analytics&nbsp;| User experience<br/> '''For: '''Vendor Management Office | Procurement Department | Business Analysts| Legal Team<br/> '''Feature ID: '''1235347
−	*Mark the global search as a global favorite so that all users can view the global favorites	+	=== New filters added to Agreement and Amendment based SSRS reports ===
−	*Display the global favorites in the respective entities for easy navigation to exact action or list	+
−	*Reorder the global favorites as per entity so that the desired order can be published for the user	+
−	*Configure maximum 4 favorites per entity	+
−	'''Note''':	+	'''What – '''The following filters are now available on UI for DRF Agreements Pending Approval and DRF Expired Agreements reports:
−	*Users cannot set the Administrator default favorites. However, users can un-pin the global favorites.	+	Contract Type
−	*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.	+
−	&nbsp;	+	Org Unit
−	'''<span style="color:#008000;">589531/591634 – Enhancement of KPI reports performance</span>'''	+	Agreement Owner
−	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.	+	Agreement Status
−	With this release, the ''CLM Activity Report'' and ''Cycle Time Report'' have been deprecated, thereby improving ICM performance considerably.	+	Created Date (Created Date From, Created Date To)
−	== ICM API Enhancements&nbsp; ==	+	Time Zone
−	<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.	+	'''Note''': These reports are default and cannot be customized as of now.
−	The highlights include:	+	'''Advantages – '''One or more filters can be applied to help view the data in contextual slices.
−	*Supporting Resume workflow action to perform additional activities such as Send for External Review, Upload Signed Copy	+	'''How – '''The filters can be applied from the respective reports page, which can be accessed from the Default Reports tab.
−	*Caching strategy	+	<div class="image-green-border">[[File:8.2 RN 16.png|720px|8.2 RN 16.png]]</div>
−	*Swagger documentation	+	'''Value: '''Self-service<br/> '''For: '''Managers | Legal Team | Decision Makers<br/> '''Feature ID: '''1346718
−	*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:	+	=== Self-Service Configuration page for creating custom SSRS reports and dynamic views ===
−	*'''Get the instance:''' used to get an empty instance of an entity.	+	'''What – '''Technical users can create or modify dynamic views and create or modify SSRS reports from the self-service configurations page. Some knowledge of technical column names and JSON is necessary to make the modifications.
−	*'''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.	+
−	*'''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;	+
−	== Enhancements to ICM Add-ins&nbsp; ==	+	'''Advantages – '''Provides a simpler path to customize reports and can be done by technical users without intervention from Icertis teams.
−	<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.	+	'''How – '''Users with technical role ‘Report admin’ can access the Report Configurations tab on the System Configuration – Self-Service page and create and modify the dynamic views and SSRS DRF reports.
		+	<div class="image-green-border">[[File:8.2 RN 17.png|720px|8.2 RN 17.png]]</div>
		+	'''Value: '''Self-service<br/> '''For: '''Configuration Admin | External implementation partners<br/> '''Feature ID: '''1346720
−	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.	+	== APIs ==
−	</div>	+
−	&nbsp;	+
−	== Enhancements to Artificial Intelligence Applications in ICM ==
−	'''<span style="color:#008000;">510541 – eDiscovery using Artificial Intelligence</span>'''	+	=== API Management Service ===
−	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. 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.	+	'''What – '''API management is a key infrastructure of API offering working as a façade and controlling layer for use of ICI APIs. It consists of—a gateway which controls the flow of APIs from the integrating application to ICI API server, a management portal to configure the usage policies and an information portal called API Hub.
−	With eDiscovery using AI:	+	With the API Management, the following is possible for customers:
−	*ICM can automatically confirm certain discovered clauses, so that users do not have to confirm them manually.	+	*Enforcing usage quota limit
−	*Auto-confirmed clauses can be searched in the same way as any other agreement clauses.	+	*Rate limiting (throughput throttling) of API calls (by default set to 5 API calls per min)
−	*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.	+	*Monitoring and getting reports on usage of APIs
−	*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.	+
−	'''<span style="color:#008000;">510549 – Inbuilt discovery of attributes and clauses in IT services vertical</span>'''	+	'''How – '''All customers using Icertis APIs can use the APIM gateway URLs as API URLs. For new customers, the APIs are automatically routed through APIM. For the existing customers that are already using APIs, they must make a configuration change to connect to APIM. The Icertis team will provide the exact API gateway URLs.
−	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.	+	'''Note''': The API Hub capability where users can get the information about APIs, try out the endpoints and get API usage reports is described as a separate feature below in the release notes.
−	''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.	+	'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
−	With this release, in addition to the generic discovery model:	+	=== Icertis API Hub–A New Developer Experience for Working with APIs ===
−	*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.	+	'''What – '''The new Icertis API Developer Experience is simple, secure, and immersive for the developers.
−	**'''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''	+
−	*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;	+	As an API developer, the new Icertis API Developer Experience allows you to discover and interact with the ICI APIs. Developers can find recommendations for making API requests, inputs for each endpoint, and authentication methods. Based on the subscription key, the developers can make API calls for the API products.
−	'''<span style="color:#008000;">510545 – Automating retraining of AI models based on user action feedback</span>'''	+	We have divided the API endpoints into distinct categories to facilitate access and search. Reports include data points like the number of API calls, response time, APIs used, etc.
−	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.	+	'''Advantages''' –
−	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.	+	*Smoother developer on-boarding and learning experience
		+	*Real-time usage reports provide transparency
−	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.	+	'''How – '''You must have the APIM Dev Portal User role assigned to access the new APIM Developer experience. Contact your system administrator for access.
−	&nbsp;	+	Additional notes:
−	'''<span style="color:#008000;">465906 – Contract highlights</span>'''	+	*You can use OAuth or token-based authentication method
		+	*An additional fee is required to use the access-based certificate authentication method
−	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.	+	'''For''': API Developers | Administrators<br/> '''Feature ID''': 1182735
−	With this release,	+	=== Framework for the composite API ===
−	*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.	+	'''What''' – This release introduces “Single Response – Composite APIs” to eliminate creation of wrappers over ICI Platform’s APIs while using them.
−	*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.	+
−	'''<span style="color:#008000;">539481 – DiscoveryAI / NegotiateAI support for multi-select attributes</span>'''	+	The Composite API Framework supports the following features:
−	''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.	+	API endpoint for supporting composite structure
−	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.	+	Request and Response representation
−	ICM has now added an option in the discovered clauses menu of ''NegotiateAI'' to find clauses similar to discovered clauses in the ICM repository.	+	Validation framework for composition
−	&nbsp;	+	Orchestration logic for composite requests
−	'''<span style="color:#008000;">566499 – Search as a natural language query in ICM</span>'''	+	Referencing field's structure and usage
−	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.	+	'''Advantages''' – The framework helps simplify the implementation and makes the integration more efficient. How - API developer can work on ICI entities via single composite API request to trigger series of APIs calls in a single API call and get multiple request results in a single response body.
−	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 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.	+	'''Value''': User Experience | Ease of Use | Improved Efficiency<br/> '''For''': API Developers | Administrators<br/> '''Feature ID''': 1182667
−	&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.	+	=== API Endpoint Changes ===
−	&nbsp;	+	[[File:8.2 RN 06.PNG|720px|8.2 RN 06.PNG]]
−	== Enhancements to Reports ==	+	[[File:8.2 RN 07.PNG|720px|8.2 RN 07.PNG]]
−	'''<span style="color:#008000;">519281 – Out-of-the-Box Obligations Management Dashboard reports</span>'''	+	[[File:8.2 RN 08.PNG|720px|8.2 RN 08.PNG]]
−	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.	+	[[File:8.2 RN 09.PNG|720px|8.2 RN 09.PNG]]
−	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.	+	[[File:8.2 RN 10.PNG|720px|8.2 RN 10.PNG]]
−	The Obligation Management Reports include:	+	[[File:8.2 RN 11.PNG|720px|8.2 RN 11.PNG]]
−	*'''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.	+	[[File:8.2 RN 12.PNG|720px|8.2 RN 12.PNG]]
−	*'''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.	+	== AI Applications ==
−	== Integrations ==	+	=== Beta Feature – Refer existing obligations when reviewing AI-discovered obligations ===
−	'''<span style="color:#008000;">467181 – Generic integration framework to support SFTP interface</span>'''&nbsp;&nbsp;	+	'''What''' – AI-discovered obligations are automatically categorized in a category and sub-category when presented for review and confirmation. When reviewing discovered obligations users can now refer to existing obligations in approved state belonging to the same category, sub-category and related agreements. Changing the category and sub-category, displays the relevant set of approved obligations.
−	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.	+	'''Advantages''' –
−	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.	+	Referring '''Library Obligations''' can help you get a standard position/scope/language to be used while setting up a newly discovered obligation
−	This will enable Administrators to:	+	Referring from '''Related Agreements''' helps you understand what obligations from parent (peer) contracts are to be set at the child level specially in case of back-to-back contracting (e.g., checking customer contracts and passing on the related obligations in supplier contracts)
−	*Define configuration parameters required for SFTP interface using Client App Reference and Client App Entity Mapping.	+	'''How – '''Users can review AI-discovered obligations from the Review Obligation drawer, which can be accessed from the “Review Discovered Obligation” page.
−	*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.	+	Review Obligation drawer displaying Approved Obligations in Library Obligation
		+	<div class="image-green-border">[[File:8.2 RN 35.PNG|720px|8.2 RN 35.PNG]]</div>
		+	'''Note:''' Library Obligations are to be added manually. Please refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.2/index.php?title=ICI_Obligation_Management#Obligation_Library OM wiki] on how to setup an Obligation Library.
−	This enables users to:	+	Review Obligation drawer displaying Approved Obligations in Related Agreements
		+	<div class="image-green-border">[[File:8.2 RN 36.PNG|720px|8.2 RN 36.PNG]]</div>
		+	'''Note: '''Time needed to display Obligations from related agreements may vary depending upon the number of Linked agreements and count of Obligations within them.
−	*Create generic integration mapping in cross reference.	+	'''Value''': Efficiency | Time Saving<br/> '''For''': Legal Team | Contract Managers<br/> '''Feature ID''': 1366783
−	*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;	+	== Sourcing ==
−	'''<span style="color:#008000;">530080 – Generic integration framework to support ASB interface</span>'''&nbsp;&nbsp;	+	The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application.
−	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.	+	=== Converting RFI to RFP or RFQ ===
−	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.	+	'''What''' – ICI Sourcing application now allows creating an RFP or RFQ from an RFI from which the suppliers are shortlisted. Users can create multiple RFP’s or RFQ’s from a single RFI.&nbsp;
−	Users can now:	+	'''Advantage''' – Saves time when creating an RFP or RFQ by allowing shortlisted suppliers to be selected from a previously completed RFI. &nbsp;
−	*Define configuration parameters for ASB interface using client app reference and client app entity mapping.	+	'''How''' – Users can use the “Create from RFI” button from the Sourcing index page or from the Create RFP/RFQ option on the RFI that is in “Bidding Closed” state.
−	*Create and maintain latest masterdata in ICM required for contracts and contract requests via ASB interface.	+
−	*Push transaction data to third party systems via ASB interface to be able to manage ICM entities using necessary JSON payloads.	+
−	*Maintain business entities such as purchase requisitions. Purchase orders or sourcing event from procurement systems to ICM via ASB interface.	+
−	&nbsp;	+	'''Value''': User Experience<br/> '''Feature ID''': 1328960&nbsp;&nbsp;
−	'''<span style="color:#008000;">544347 – Ability to integrate ICM with Enterprise-Level Identity Providers using OpenID Connect protocol</span>'''	+	=== Shortlist Suppliers in RFx ===
−	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.	+	'''What''' – An enhancement has been made to the existing '''Shortlist''' feature that allows buyers to select and shortlist specific suppliers for the next procurement stage. For example, from RFI to RFP or RFQ or from one round to another in the same RFX. The supplier Shortlist can be modified in certain RFx statuses.
−	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.	+	'''Advantage''' – Helps accessing preferred suppliers quickly or remove them from the “Suppliers” page thereby saving time.
−	This integration implementation is flexible enough to enable connection with other identity providers that use the OpenID Connect protocol.	+	'''How''' – A “Shortlist Supplier” option is added on the “Suppliers” page. &nbsp;
		+	<div class="image-green-border">[[File:8.2.RN 4.png|500px|8.2.RN 4.png]]</div>
		+	'''Value''': User Experience<br/> '''For''': Buyer and Administrator users<br/> '''Feature ID''': 1341682&nbsp;&nbsp;
−	'''<span style="color:#008000;">467179 – SFDC experience enhancements – simplified UX - action in grid</span>'''&nbsp;&nbsp;	+	=== Sourcing Enhancements ===
−	The Icertis Experience for Salesforce already provides the capability for Salesforce users to perform agreement-related tasks from within Salesforce.	+	[[File:8.2.RN T4.PNG|720px|8.2.RN T4.PNG]]
−	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.	+	== Obligation Management ==
−	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.	+	The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application
−	&nbsp;	+	=== Auto-create Obligations from Associations data ===
		+
		+	'''What''' – ICI Platform now facilitates improved Obligation intake from source Association records. An Obligation is automatically created from any defined associations such as Deliverables, SLA, Risk Assessments. For example, if a SOW has ‘Deliverable’ as an association, then the user can directly convert that deliverable into an Obligation.
−	'''<span style="color:#008000;">537762 – SFDC experience enhancements – improved search functionality</span>'''	+	'''Advantages''' – Streamlines and simplifies creation of Delivery Dates, Milestones, SLAs, Risk Assessments, and other obligations from associated records, improving process efficiency. Auto-creation of Obligations enhances tracking compliance centrally using Obligation Management.
−	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.	+	'''How – '''You can use the “Create Obligation” menu option from the Associations object list view or details page.
		+	<div class="image-green-border">[[File:8.2.RN 5.png|720px|8.2.RN 5.png]]</div>
		+	'''Value''': User Experience | Contract Building | Managing Obligations | Process Efficiency<br/> '''For''': Risk Managers | Contract Administrators<br/> '''Feature ID''': 649740
−	With the SFDC experience enhancement, the user will have the ability to:	+	=== Use “Date” & “DateTime” Attributes from Holding Agreement for Obligation Scheduling ===
−	*Search for contracts or contract requests from a common page.	+	'''What – '''Due'''dates and end dates for obligations can now be selected from any of the date attributes of the agreement.'''
−	*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.	+
−	*View ICM saved searches, and refine searches based on metadata and full text.	+
−	'''<span style="color:#008000;">537766 – Reporting capability within Salesforce</span>'''	+	'''Advantages'''
−	Icertis Experience for Salesforce already provides the capability for Salesforce users to execute contract management tasks from within Salesforce.	+	Eliminates the need for an Obligation creator to know specific dates.
−	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.	+	Consistency in Obligation dates used across various members / obligation creators
−	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''.	+	Reduces the extra effort required in referring to Date Attributes of holding agreement entity (for example, Effective Date / Expiry Date) and use them in Obligation creation.
		+	'''How – '''Two new attributes have been added to the Obligation Contract Type – “Select Due Date From” and “Select End Date From”. You can select a specific date value from the given options. The date value selected will be as per the actual date defined in the Agreement. For example, if you select “Expiry Date” value, an Obligation will be created with an expiry date that is same as the expiry date for the Agreement.
		+	<div class="image-green-border">[[File:8.2.RN 6.png|600px|8.2.RN 6.png]]</div>
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">556549 – Enabling existing adapter functionality in the new MS Dynamics unified interface</span>'''	+	'''Value''': User Experience<br/> '''For''': Contract Operations<br/> '''Feature ID''': 913820
−	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.	+	=== Obligation Management Enhancements ===
−	== ICM Platform Tools ==	+	[[File:8.2.RN T5.PNG|720px|8.2.RN T5.PNG]]
−	'''<span style="color:#008000;">519481 – Introducing the ICM Tools portal</span>'''	+	== Supplier Relationship Management ==
−	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.	+	ICI Supplier Relationship Management application is certified to work with the 8.2 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.	+	=== Supplier Profile and Supplier Master records synchronization ===
−	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.	+	'''What''' – Supplier product and service categories are now automatically synced in the following events:
−	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.	+	On supplier qualification, the product/service category updates get copied to the Supplier Master category field.
−	'''<span style="color:#008000;">547429 – Introducing the Translations Editor Tool</span>'''	+	Buyers update the Supplier Master the information is synced with the Supplier Profile.
−	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.	+	Buyers update the Supplier Profile the information is synced with Supplier Master.
−	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.	+	'''Advantage''' – Supplier records are consistent and can be consumed across all Icertis applications.
−	Using this tool, users can now:	+	'''How''' – If a supplier record in the database is modified depending on the conditions defined, the other relevant records also get updated automatically.&nbsp;
−	*Search for a specific string using the search bar and update the Resource Key value for Language and Locale.	+	'''Value''': Efficiency<br/> '''For''': Buyer users<br/> '''Feature ID''': 1420117
−	*Update multiple language strings by selecting and saving the Resource Key value.	+
−	*Download and upload the localization key values using Microsoft Excel.	+	=== Supplier Relationship Management Enhancements ===
−	*View the modified values in the ICM instance immediately.	+
		+	[[File:8.2.RN T7.PNG|720px|8.2.RN T7.PNG]]
	&nbsp;		&nbsp;
−	'''<span style="color:#008000;">519630 – Improved ICM Health Check</span>'''	+	== Rebates Enhancements ==
−	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.	+	Rebates App in ICI Platform is enhanced to improve the usability and thereby improve the overall user experience, scalability and robust calculations. The Rebates App extends support for Big Data, AI, and Dynamic JSON. The enhancements in Rebates App can be summarized as below:
−	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.	+	'''Refined seeded data model:'''
−	The health statuses are classified into three categories:	+	*Minimal configuration and data reusability to make Rebates app more scalable.
		+	*Standardized naming conventions to avoid any conflicts with other apps.
		+	*Normalized data has improved Calculation Engine’s efficiency by 50%.
		+	*Dynamic JSON for Rebate program data eliminates the need to have distinct rebates and payout calculation for every business unit in an organization. The enhanced calculation engine extracts JSON data from the Agreement and its associated documents and maps it with the newly configured attributes.
		+	*Background tasks optimized to support big data such as calculation engine processing large invoice and agreement datasets. As an example, for performance testing, it took 35 seconds (approximately) to process 170,000 &nbsp;records (approximately) as compared to 1 minute (approximately) for 5000 records (approximately) in the earlier version.
		+	*Rebate program attributes are a part of associated document instead of an agreement, which enables handling multiple rebate programs within a contract. This also reduces the number of attributes in an agreement, that improves the performance of agreement creation.
		+	*Standardized attributes management by allowing 16-digit numbers with 6 decimal places.
		+	*Generic Product, Location, and Customer hierarchies allow customizing configuration and mapping it to the calculation engine.
		+	*Previously, configuration supported only up to 10 customer details as these details were part of the Agreement itself. However, now these details are migrated as Associated documents to support unlimited customer details.
−	*''Warning ''- indicated by a yellow warning icon	+	'''Power BI Reporting:'''
−	*''Healthy'' -&nbsp; indicated by a green checkmark icon	+
−	*''Unhealthy'' - indicated by a red warning icon	+
−	The following details are displayed in the Health Check:	+	*Intuitive dashboard with advanced analytics on the rebate agreement distribution and accruals accumulation.
		+	*Out-of-the-box reports added in Power BI, which were earlier focused on Accruals, are now aligned with the overall performance of Rebates.
		+	*Improved visibility for Rebates payout calendar with the next payout dates.
−	*'''Elastic Search Health''': displays the Status (yellow/green/red), the Elastic Search version, the Uptime, and so on.	+	=== Risk Management Enhancements ===
−	*'''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 % 404 HTTP Response Sent, % 500 HTTP Response Sent, percentage of CPU utilization per process, Requests/sec, and so on.	+
−	'''<span style="color:#008000;">553394 – Enhancement to search sync</span>'''	+	[[File:8.2.RN T6.PNG|720px|8.2.RN T6.PNG]]
−	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.	+	== Technology Updates ==
−	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''.	+	=== HTTP Artifact Binding Support for SSO Integration ===
−	<div class="note-box">'''Note''': Data can be fetched from only one instance at a time.</div>	+
−	== Technical Requirements for Release 7.11 ==	+
−	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:<br/> &nbsp;	+	'''What – '''In addition to HTTP POST and HTTP Redirect, ICI now supports HTTP Artifact binding for SSO (Single Sign-On) integration along with other IdPs like ADFS.
−	&nbsp;	+	'''Advantages – '''With improved security, exchanging sensitive data across Id Provider (IdP) and Service Provider (SP) becomes more authenticated and trustworthy. This prevents intervention of any malicious party.
−	&nbsp;	+	'''How – '''Administrator or Implementation Partner can choose between HTTP POST, HTTP Redirect and HTTP Artifact binding for SSO (Single Sign-On) integration, on the IdP server side.
−	== Known Issues for Release 7.11 ==	+	'''Value: '''Secure Authentication Process<br/> '''For: '''All ICI Users<br/> '''Feature ID: '''1342076
		+
		+	=== Microsoft retiring basic authentication for SMTP ===
		+
		+	'''What '''– Microsoft is retiring basic authentication for SMTP, and it would be necessary for customers using basic authentication to move to an alternate service. ICI now supports modern authentication with support for Microsoft Graph API.
		+
		+	'''Why '''– Provide support for modern authentication methods & ensure service continuity even after Microsoft retires basic authentication later this year (Oct 1, 2022).
		+
		+	'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
		+
		+	'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
		+
		+	=== Microsoft retiring Outlook REST API ===
		+
		+	'''What''': The Icertis Outlook Add-In that currently uses the Outlook REST API will now use Microsoft Graph API.
		+
		+	Configurations are required for Outlook Add-In at the time of implementing or upgrading Icertis Contract Intelligence to work with Microsoft Graph API.
		+
		+	'''Why''': Microsoft has announced that Outlook REST API will be deprecated in the month of November, 2022.
		+
		+	'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
		+
		+	'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
		+
		+	=== Support for StartTLS protocol ===
		+
		+	'''What''' – Adding support for the StartTLS protocol through NuGet MailKit for authentication and notification. StartTLS protocol command is used to inform the email server that the email client wants to upgrade from an insecure connection to a secure one using TLS or SSL.<br/> <br/> '''Why''' – Customers have the option to use the StartTLS protocol, which supports enhanced security.
		+
		+	'''How''' – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.
		+
		+	'''Value: '''Business as usual (BAU) without Impact<br/> '''For: '''Authorized Signatories | Approval Team | Contributors<br/> '''Feature ID: '''1417372
		+
		+	=== Bootstrap upgrade from version 4.5.2 to 5.1.3 ===
		+
		+	'''What''' – The Bootstrap library has been upgraded from version 4.5.2 to 5.1.3. The support for Bootstrap library version 4.5.2 ends by Q3 2022. 4.5.2 is compatible with the new version.
		+
		+	'''Why''' – To address security vulnerabilities.
		+
		+	'''TFS ID''': 1459132<br/> &nbsp;
		+
		+	=== Web Application Firewall & Azure Front Door ===
		+
		+	'''What''' –
		+
		+	Implementing Azure Front Door (AFD) with the following settings:
		+
		+	Web Application Firewall (WAF) in diagnostic mode
		+
		+	Prevention Rule in AFD to restrict access from embargo countries.
		+
		+	'''Advantages – '''WAF & AFD help prevent against common exploits and vulnerabilities.
		+
		+	'''How – '''It can be configured, deployed, and managed via the Azure Portal, PowerShell, and CLI (command-line interface).
		+
		+	'''Value''': Security<br/> '''For''': Administrators<br/> '''Feature ID''': 951438
	&nbsp;		&nbsp;
		+
		+	= Technical Requirements =
		+
		+	The Icertis Contract Intelligence (ICI) application can be accessed from any device with an Internet connection and a supported browser. All features may not be available in all environments.
		+
		+	The software and hardware requirements for the client system as well as the mobile application are listed in the table below:
		+
		+	[[File:8.2.RN T8.PNG|720px|8.2.RN T8.PNG]]
		+
		+	[[File:8.2.RN T9.PNG|720px|8.2.RN T9.PNG]]
		+
		+	[[File:8.2.RN T10.PNG|720px|8.2.RN T10.PNG]]<br/> [[File:8.2.RN T11.PNG|720px|8.2.RN T11.PNG]]
		+
		+	[[File:8.2.RN T12.PNG|720px|8.2.RN T12.PNG]][[File:8.2.RN T13.PNG|720px|8.2.RN T13.PNG]]
		+
		+	[[File:8.2.RN T14.PNG|720px|8.2.RN T14.PNG]]
		+
		+	[[File:8.2.RN T15.PNG|720px|8.2.RN T15.PNG]]<br/> [[File:8.2.RN T16.PNG|720px|8.2.RN T16.PNG]]<br/> [[File:8.2.RN T17.PNG|720px|8.2.RN T17.PNG]]
		+
		+	[[File:8.2.RN T18.PNG|720px|8.2.RN T18.PNG]]
		+
		+	= Accessibility Conformance =
		+
		+	We ran accessibility conformance tests on the Icertis Contract Intelligence platform and Business Apps for Web Content Accessibility Guidelines 2.1 for Level A and Level AA standards. We did not evaluate for Level AAA standards.
		+
		+	While most of the product functionality has at least one method that meets the criterion without any known defects, some functionality of the product may not meet the conformance criteria. The full report is published in the following documents and can be made available on request:
		+
		+	ICI Platform Accessibility Conformance Report
		+
		+	ICI AI/ML Accessibility Conformance Report
		+
		+	ICI Reporting Accessibility Conformance Report
		+
		+	ICI Obligation Management Accessibility Conformance Report
		+
		+	ICI Sourcing Accessibility Conformance Report
		+
		+	ICI Proposal Management Accessibility Conformance Report
		+
		+	ICI SRM Accessibility Conformance Report
		+
		+	ICI Risk Management Accessibility Conformance Report
		+
		+	= Known Issues =
		+
		+	This section includes some issues that we are aware of and plan to resolve at the earliest:
		+
		+	[[File:8.2.RN T19.PNG|720px|8.2.RN T19.PNG]]
		+
		+	&nbsp;'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Associations|Association Management]] | [[Compliances|Compliance Management]] | [[Templates|Template Management]] | [[Clauses|Clause Management]] | [[Configure|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]]&nbsp;

---

Latest revision as of 13:09, 29 September 2022

ICI Release Notes - Release 8.2

Apart from new features and enhancements, this document contains information on:

• Technical Requirements
• Accessibility Conformance
• Known Issues

Refer to the Wiki documentation (also found in your ICI help section) for details on all ICI features and functionalities.

New Features and Enhancements

Contract Authoring & Management 

Amend contracts preserving previously negotiated terms

What – When users amend a contract, they now have a choice to either use the base agreement or a previously negotiated and amended contract. Along with the contract version, users can also choose the associations to copy to the amendment.

Advantages – Maintaining a history of the original agreement and all amendments is now possible. This helps in auditing the changes made to contracts over time.

How – Options to choose the amendment and copy associations to the amendment are now available when creating an amendment. Users can associate and inherit documents such as NDA, SOW, etc.

Value: Compliance | User Experience
For: Legal Team | Authors | Contract Managers
Feature ID: 1233193

Send multiple agreements packaged in a single envelope for electronic signature

What – Earlier, agreement could be bundled only with its associations and sent for electronic signature. With this release you can also bundle peer agreements in a single package for electronic signing.

Advantages – Eliminates the need to send one agreement at a time for signature, thereby saving time. Provisions setting a sequence in which the agreements must be signed and facilitates reordering if required.

How - Existing Esign functionality is enhanced to package peer agreements as a single bundle and send it for electronic signature.

Value: User Experience | Contract Building Performance
For: Contract Owners | Legal Compliance Team
Feature ID: 1369302

Quickly create and edit contract types in bulk using excel workbook

What – ICI now allows its users to edit and create contract types in bulk using the Microsoft Excel workbook. User can also edit multiple attributes for multiple contract types at once.

Advantages

Contract type (CT) changes happen frequently in the implementation phase, the feedbacks from the customers regarding the changes in the CT have to be earlier implemented one by one for each CT in ICI UI. Now, this changes and edits can be done in one go using this feature.

Creating and editing multiple contract types at once will reduce time involved in configuring large contract types.

How

A button “Bulk Contract Type” is now added under “Configure” tile.

Users can generate pre-seeded contract type workbook, with 2 tabs in excel, contact type, and contract type attributes.

Value: User Experience
For: Admins | Legal Team | Contract Managers
Feature ID: 1342050

Icertis Experiences

Rules functionality added to Icertis Experience for Word

What – Users can now create rules for assembling the clause and define the rules for selecting the template from within Microsoft Word to display clauses in agreements based on specified conditions. Existing rules can also be viewed or edited from Microsoft Word.

Advantages – Provides a familiar and intuitive interface for legal teams and contract authors to create conditional agreement templates.

Reduced turnaround time, instead of switching while creating the clause and template

How – Users can define conditions for selecting a clause or template while assembling of clauses and selection of templates from Microsoft Word.

Value: User Experience
For: Legal Team
Feature ID: 1117626

Outlook Add-in – Labeling and validation for emails added to ICI

What – Every email uploaded in ICI will now display an Outlook category label, that helps users know if the email is already added in ICI. Additionally, a validation is also displayed if user tries uploading same emails twice. Users can customize the outlook category label as per the needs.

Advantages – Avoid uploading duplicate email conversations in ICI.

How – This feature is available as part of Icertis Experience for Outlook.

Value: User Experience
For: Contract Managers | Legal Teams
Feature ID: 1341557 

Revamping ICI Salesforce User Experience

What – Revamping the ICI Salesforce user interface to give a better user experience, with addition of features and enhancement under agreement related sub tabs.

The following agreement sub tabs can now be seen with new capabilities:

• Associations sub tab
• Amendment sub tab
• Note sub tab
• Team sub tab
• Collaboration sub tab

Some new features include:

Hyperlink added in the first column of the association list grid navigating to the association details page within ICI Salesforce platform.

Ability to preview the document from amendments sub tab.

The collaborations tab is now revamped from ICI Iframe to Salesforce native look and feel, with capability to view more messages.

Advantages – This revamp will be giving a more consistent and familiar user experience with enhanced look and feel inline with Salesforce native user experience across tabs, subtabs and actions for sales personas.

How – Below are few screenshots of the revamped ICI Salesforce platform.

New ICI Salesforce Agreement Details screen

New Add Note Dialog box

Value: User Experience
For: Sales Team
Feature ID: 1356012

Salesforce – Visibility of products and services sold to customers

What – ICI Salesforce experience users can now view the list of all the products and services sold to the customer under “Agreement Lines” subtab.

Advantages – With visibility to Agreement lines through this feature, Sales Executives will be able to identify Cross-sell, up-sell opportunities to pursue relevant sales, and request amendment to appropriate contract.

How – A new subtab “Agreement Lines” is added for account object displaying all the active product and services sold to the customer. The products displayed under agreement line subtab are fetched via ICI saved searches.

Note: The “Agreement Lines” displays only active products and services from executed contracts.

Value: User Experience
For: Sales Managers | Sales Executive
Feature ID: 1192973

Enhancements – Mobile App Experience

Administration & Configuration

Enhanced ICI startup validation architecture

What – A new validation framework for configuration keys and related metadata to resolve incorrect or missing keys and ensure seamless startup of ICI instances.

Advantages – Timely validation of configuration keys and guardrails to prevent unnecessary startup blockers.

How – At startup, the validation framework checks for configuration keys that are inconsistent or incorrect and restores those to default values thereby preempting any startup issues. Technical admins can view and investigate the validation logs on the self-service portal.

Value: Reliability, Supportability
For: Administrators
Feature ID: 1373024

Configure E-Signature Integrations within ICI

What – E- signature configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.

Advantages – This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team. 

How – Technical administrators can configure E- sign providers (DocuSign and AdobeSign) from the E-sign configuration page.

Value: Self-service
For: Technical admins
Feature ID: 1180879

Integrated Config keys validation framework

What – ICI now has the capability to check incorrect values, difference in data types, and inconsistency in configuration data. The utility can be run prior to starting an application and the report and errors reported can be used to help find a solution.

Advantages – Helps prevent issues that occur during application startup.

How – At the start of an ICI instance, the disparity in the configuration keys is identified, and the incorrect keys are set to the default value. All such changes are recorded in the self-service portal so that the technical admins can investigate the errors.

Value: Self-service  
For: Administrators
Feature ID: 1373030

Configure SSO integrations within ICI

What – SSO configurations can now be done inside the Icertis Contract Intelligence platform by technical administrators.

Advantages – This reduces cross-team dependencies and increases the speed of implementation as a user with technical expertise can perform the configuration without intervention from the Icertis team. 

How – Technical administrators can configure SSO integrations (SAML, WS-Fed and O-Auth) from the SSO configuration page.

Value: Self-service  
For: Technical admins
Feature ID: 1180896

Customer-specific SAML/OAuth SSO Configurations

What – In a multitenant instance of Icertis Contract Intelligence, SSO configurations are now moved from a single configuration file to separate configuration files for each tenant. These configurations can now also be modified from within Icertis Contract Intelligence.

Advantages –

• Site reliability and stability - SSO issues affecting one tenant do not impact other tenants.
• Self-service - Technical admin users can configure SSO without intervention from Icertis teams.

How – Users with the right permissions can make SSO configuration changes from the Tenant.config file. The changes can also be made from within ICI by Technical Admin users.

Value: Self-service, Reliability, Supportability
For: Technical Admins
Feature ID: 1317384

Error-handling framework

What – A centralized and industry-standard error handling framework for faster troubleshooting, analysis and resolution of issues. The list of error codes and related data is cataloged & documented, which will act as a standard reference for all error codes in the ICI platform.

The framework provides the following features:

Detailed and structured data to determine severity, origin, module, area & source of the error.

No unhandled exceptions emanating from the system.

Detailed logging is done in a central repository like Kibana.

For ICI Instances where AppInsights is available, a correlation id helps to track calls and correlate the complete chain of events that led to the error.

Why – Eliminates time required to locate and understand the issue and reduces the overall time needed to fix issues.

How – ExceptionHandler attribute is introduced, which will have following Origin, Area, Module, Sub Module in the form of code.

For example: 50000030021360X8013153 (shown on User Interface)

Breakdown of the code is as follows:

5 – Severity

00 – Origin (First parameter of Exception Handling attribute)

00 – Source (mostly internal)

03 – Area (Second parameter of Exception Handling attribute)

002 – Module (Third parameter of Exception Handling attribute)

136 – SubModule (Fourth parameter of Exception Handling attribute)

0X8013153 – Standard C# HResult which can be googled to see the exception type

Class decorators for Exception Handling

[ExceptionHandler (exceptionOrigin: ExceptionOrigin.Core, exceptionArea: ExceptionArea.CLM, module: ExceptionAreaModule.CLM_AdminTask, submodule: ExceptionAreaSubModule.CLM_AdminTask_Root)]

When an error occurs, the error code is displayed on the error message, see the screenshot below.  

Value: Supportability
For: Partner Developers | Any Application User | Troubleshooters
Feature ID: 1373034

Administration & Configuration Enhancements

Reporting Analysis

Dashboard and Power BI reports for Supplier Evaluation

What – An interactive Supplier Evaluation dashboard with the following features is now available out-of-the-box:

Interactive graphs for status of evaluation cases, evaluation distribution by performance, and ageing in review or approval states.

Enlists the top and poor performing suppliers based on a host of filters like evaluation type, period of evaluation, supplier name and more.

Captures evaluations that are awaiting supplier inputs for missing documents.

360-degree supplier performance score card about different evaluations, KPI and performance trend over a time period.

Capture supplier documents/ certificates that are expired or expiring within 5 days.

Advantages –

Information is represented visually and is easier to consume and track.

Assist the procurement team in setting up the right expectations and manage supplier relationships.

Insights into poorly performing suppliers can help in planning proactive performance improvement.

How – The dashboard and reports can be accessed from the Supplier Management -> Dashboard.

Pre-requisite: HTTP Artifact binding should be supported by the respective IDP server to enable this feature.

Value: Analytics | User experience
For: Vendor Management Office | Procurement Department | Business Analysts| Legal Team
Feature ID: 1235347

New filters added to Agreement and Amendment based SSRS reports

What – The following filters are now available on UI for DRF Agreements Pending Approval and DRF Expired Agreements reports:

Contract Type

Org Unit

Agreement Owner

Agreement Status

Created Date (Created Date From, Created Date To)

Time Zone

Note: These reports are default and cannot be customized as of now.

Advantages – One or more filters can be applied to help view the data in contextual slices.

How – The filters can be applied from the respective reports page, which can be accessed from the Default Reports tab.

Value: Self-service
For: Managers | Legal Team | Decision Makers
Feature ID: 1346718

Self-Service Configuration page for creating custom SSRS reports and dynamic views

What – Technical users can create or modify dynamic views and create or modify SSRS reports from the self-service configurations page. Some knowledge of technical column names and JSON is necessary to make the modifications.

Advantages – Provides a simpler path to customize reports and can be done by technical users without intervention from Icertis teams.

How – Users with technical role ‘Report admin’ can access the Report Configurations tab on the System Configuration – Self-Service page and create and modify the dynamic views and SSRS DRF reports.

Value: Self-service
For: Configuration Admin | External implementation partners
Feature ID: 1346720

APIs

API Management Service

What – API management is a key infrastructure of API offering working as a façade and controlling layer for use of ICI APIs. It consists of—a gateway which controls the flow of APIs from the integrating application to ICI API server, a management portal to configure the usage policies and an information portal called API Hub.

With the API Management, the following is possible for customers:

• Enforcing usage quota limit
• Rate limiting (throughput throttling) of API calls (by default set to 5 API calls per min)
• Monitoring and getting reports on usage of APIs

How – All customers using Icertis APIs can use the APIM gateway URLs as API URLs. For new customers, the APIs are automatically routed through APIM. For the existing customers that are already using APIs, they must make a configuration change to connect to APIM. The Icertis team will provide the exact API gateway URLs.

Note: The API Hub capability where users can get the information about APIs, try out the endpoints and get API usage reports is described as a separate feature below in the release notes.

For: API Developers | Administrators
Feature ID: 1182735

Icertis API Hub–A New Developer Experience for Working with APIs

What – The new Icertis API Developer Experience is simple, secure, and immersive for the developers.

As an API developer, the new Icertis API Developer Experience allows you to discover and interact with the ICI APIs. Developers can find recommendations for making API requests, inputs for each endpoint, and authentication methods. Based on the subscription key, the developers can make API calls for the API products.

We have divided the API endpoints into distinct categories to facilitate access and search. Reports include data points like the number of API calls, response time, APIs used, etc.

Advantages –

• Smoother developer on-boarding and learning experience
• Real-time usage reports provide transparency

How – You must have the APIM Dev Portal User role assigned to access the new APIM Developer experience. Contact your system administrator for access.

Additional notes:

• You can use OAuth or token-based authentication method
• An additional fee is required to use the access-based certificate authentication method

For: API Developers | Administrators
Feature ID: 1182735

Framework for the composite API

What – This release introduces “Single Response – Composite APIs” to eliminate creation of wrappers over ICI Platform’s APIs while using them.

The Composite API Framework supports the following features:

API endpoint for supporting composite structure

Request and Response representation

Validation framework for composition

Orchestration logic for composite requests

Referencing field's structure and usage

Advantages – The framework helps simplify the implementation and makes the integration more efficient. How - API developer can work on ICI entities via single composite API request to trigger series of APIs calls in a single API call and get multiple request results in a single response body.

Value: User Experience | Ease of Use | Improved Efficiency
For: API Developers | Administrators
Feature ID: 1182667

API Endpoint Changes

AI Applications

Beta Feature – Refer existing obligations when reviewing AI-discovered obligations

What – AI-discovered obligations are automatically categorized in a category and sub-category when presented for review and confirmation. When reviewing discovered obligations users can now refer to existing obligations in approved state belonging to the same category, sub-category and related agreements. Changing the category and sub-category, displays the relevant set of approved obligations.

Advantages –

Referring Library Obligations can help you get a standard position/scope/language to be used while setting up a newly discovered obligation

Referring from Related Agreements helps you understand what obligations from parent (peer) contracts are to be set at the child level specially in case of back-to-back contracting (e.g., checking customer contracts and passing on the related obligations in supplier contracts)

How – Users can review AI-discovered obligations from the Review Obligation drawer, which can be accessed from the “Review Discovered Obligation” page.

Review Obligation drawer displaying Approved Obligations in Library Obligation

Note: Library Obligations are to be added manually. Please refer to the OM wiki on how to setup an Obligation Library.

Review Obligation drawer displaying Approved Obligations in Related Agreements

Note: Time needed to display Obligations from related agreements may vary depending upon the number of Linked agreements and count of Obligations within them.

Value: Efficiency | Time Saving
For: Legal Team | Contract Managers
Feature ID: 1366783

Sourcing

The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application.

Converting RFI to RFP or RFQ

What – ICI Sourcing application now allows creating an RFP or RFQ from an RFI from which the suppliers are shortlisted. Users can create multiple RFP’s or RFQ’s from a single RFI. 

Advantage – Saves time when creating an RFP or RFQ by allowing shortlisted suppliers to be selected from a previously completed RFI.  

How – Users can use the “Create from RFI” button from the Sourcing index page or from the Create RFP/RFQ option on the RFI that is in “Bidding Closed” state.

Value: User Experience
Feature ID: 1328960  

Shortlist Suppliers in RFx

What – An enhancement has been made to the existing Shortlist feature that allows buyers to select and shortlist specific suppliers for the next procurement stage. For example, from RFI to RFP or RFQ or from one round to another in the same RFX. The supplier Shortlist can be modified in certain RFx statuses.

Advantage – Helps accessing preferred suppliers quickly or remove them from the “Suppliers” page thereby saving time.

How – A “Shortlist Supplier” option is added on the “Suppliers” page.  

Value: User Experience
For: Buyer and Administrator users
Feature ID: 1341682  

Sourcing Enhancements

Obligation Management

The 8.2 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application

Auto-create Obligations from Associations data

What – ICI Platform now facilitates improved Obligation intake from source Association records. An Obligation is automatically created from any defined associations such as Deliverables, SLA, Risk Assessments. For example, if a SOW has ‘Deliverable’ as an association, then the user can directly convert that deliverable into an Obligation.

Advantages – Streamlines and simplifies creation of Delivery Dates, Milestones, SLAs, Risk Assessments, and other obligations from associated records, improving process efficiency. Auto-creation of Obligations enhances tracking compliance centrally using Obligation Management.

How – You can use the “Create Obligation” menu option from the Associations object list view or details page.

Value: User Experience | Contract Building | Managing Obligations | Process Efficiency
For: Risk Managers | Contract Administrators
Feature ID: 649740

Use “Date” & “DateTime” Attributes from Holding Agreement for Obligation Scheduling

What – Duedates and end dates for obligations can now be selected from any of the date attributes of the agreement.

Advantages

Eliminates the need for an Obligation creator to know specific dates.

Consistency in Obligation dates used across various members / obligation creators

Reduces the extra effort required in referring to Date Attributes of holding agreement entity (for example, Effective Date / Expiry Date) and use them in Obligation creation.

How – Two new attributes have been added to the Obligation Contract Type – “Select Due Date From” and “Select End Date From”. You can select a specific date value from the given options. The date value selected will be as per the actual date defined in the Agreement. For example, if you select “Expiry Date” value, an Obligation will be created with an expiry date that is same as the expiry date for the Agreement.

 

Value: User Experience
For: Contract Operations
Feature ID: 913820

Obligation Management Enhancements

Supplier Relationship Management

ICI Supplier Relationship Management application is certified to work with the 8.2 release

Supplier Profile and Supplier Master records synchronization

What – Supplier product and service categories are now automatically synced in the following events:

On supplier qualification, the product/service category updates get copied to the Supplier Master category field.

Buyers update the Supplier Master the information is synced with the Supplier Profile.

Buyers update the Supplier Profile the information is synced with Supplier Master.

Advantage – Supplier records are consistent and can be consumed across all Icertis applications.

How – If a supplier record in the database is modified depending on the conditions defined, the other relevant records also get updated automatically. 

Value: Efficiency
For: Buyer users
Feature ID: 1420117

Supplier Relationship Management Enhancements

 

Rebates Enhancements

Rebates App in ICI Platform is enhanced to improve the usability and thereby improve the overall user experience, scalability and robust calculations. The Rebates App extends support for Big Data, AI, and Dynamic JSON. The enhancements in Rebates App can be summarized as below:

Refined seeded data model:

• Minimal configuration and data reusability to make Rebates app more scalable.
• Standardized naming conventions to avoid any conflicts with other apps.
• Normalized data has improved Calculation Engine’s efficiency by 50%.
• Dynamic JSON for Rebate program data eliminates the need to have distinct rebates and payout calculation for every business unit in an organization. The enhanced calculation engine extracts JSON data from the Agreement and its associated documents and maps it with the newly configured attributes.
• Background tasks optimized to support big data such as calculation engine processing large invoice and agreement datasets. As an example, for performance testing, it took 35 seconds (approximately) to process 170,000  records (approximately) as compared to 1 minute (approximately) for 5000 records (approximately) in the earlier version.
• Rebate program attributes are a part of associated document instead of an agreement, which enables handling multiple rebate programs within a contract. This also reduces the number of attributes in an agreement, that improves the performance of agreement creation.
• Standardized attributes management by allowing 16-digit numbers with 6 decimal places.
• Generic Product, Location, and Customer hierarchies allow customizing configuration and mapping it to the calculation engine.
• Previously, configuration supported only up to 10 customer details as these details were part of the Agreement itself. However, now these details are migrated as Associated documents to support unlimited customer details.

Power BI Reporting:

• Intuitive dashboard with advanced analytics on the rebate agreement distribution and accruals accumulation.
• Out-of-the-box reports added in Power BI, which were earlier focused on Accruals, are now aligned with the overall performance of Rebates.
• Improved visibility for Rebates payout calendar with the next payout dates.

Risk Management Enhancements

Technology Updates

HTTP Artifact Binding Support for SSO Integration

What – In addition to HTTP POST and HTTP Redirect, ICI now supports HTTP Artifact binding for SSO (Single Sign-On) integration along with other IdPs like ADFS.

Advantages – With improved security, exchanging sensitive data across Id Provider (IdP) and Service Provider (SP) becomes more authenticated and trustworthy. This prevents intervention of any malicious party.

How – Administrator or Implementation Partner can choose between HTTP POST, HTTP Redirect and HTTP Artifact binding for SSO (Single Sign-On) integration, on the IdP server side.

Value: Secure Authentication Process
For: All ICI Users
Feature ID: 1342076

Microsoft retiring basic authentication for SMTP

What – Microsoft is retiring basic authentication for SMTP, and it would be necessary for customers using basic authentication to move to an alternate service. ICI now supports modern authentication with support for Microsoft Graph API.

Why – Provide support for modern authentication methods & ensure service continuity even after Microsoft retires basic authentication later this year (Oct 1, 2022).

How – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.

Value: Business as usual (BAU) without Impact
For: Authorized Signatories | Approval Team | Contributors
Feature ID: 1417372

Microsoft retiring Outlook REST API

What: The Icertis Outlook Add-In that currently uses the Outlook REST API will now use Microsoft Graph API.

Configurations are required for Outlook Add-In at the time of implementing or upgrading Icertis Contract Intelligence to work with Microsoft Graph API.

Why: Microsoft has announced that Outlook REST API will be deprecated in the month of November, 2022.

How – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.

Value: Business as usual (BAU) without Impact
For: Authorized Signatories | Approval Team | Contributors
Feature ID: 1417372

Support for StartTLS protocol

What – Adding support for the StartTLS protocol through NuGet MailKit for authentication and notification. StartTLS protocol command is used to inform the email server that the email client wants to upgrade from an insecure connection to a secure one using TLS or SSL.

Why – Customers have the option to use the StartTLS protocol, which supports enhanced security.

How – The config key "Platform.Email.ProviderConfiguration" with Provider and Configuration values (JSON) will need to be updated to support this feature. User can choose between following providers SMTP/EWS/Mailkit/Microsoft Graph.

Value: Business as usual (BAU) without Impact
For: Authorized Signatories | Approval Team | Contributors
Feature ID: 1417372

Bootstrap upgrade from version 4.5.2 to 5.1.3

What – The Bootstrap library has been upgraded from version 4.5.2 to 5.1.3. The support for Bootstrap library version 4.5.2 ends by Q3 2022. 4.5.2 is compatible with the new version.

Why – To address security vulnerabilities.

TFS ID: 1459132
 

Web Application Firewall & Azure Front Door

What –

Implementing Azure Front Door (AFD) with the following settings:

Web Application Firewall (WAF) in diagnostic mode

Prevention Rule in AFD to restrict access from embargo countries.

Advantages – WAF & AFD help prevent against common exploits and vulnerabilities.

How – It can be configured, deployed, and managed via the Azure Portal, PowerShell, and CLI (command-line interface).

Value: Security
For: Administrators
Feature ID: 951438

 

Technical Requirements

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

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

Accessibility Conformance

We ran accessibility conformance tests on the Icertis Contract Intelligence platform and Business Apps for Web Content Accessibility Guidelines 2.1 for Level A and Level AA standards. We did not evaluate for Level AAA standards.

While most of the product functionality has at least one method that meets the criterion without any known defects, some functionality of the product may not meet the conformance criteria. The full report is published in the following documents and can be made available on request:

ICI Platform Accessibility Conformance Report

ICI AI/ML Accessibility Conformance Report

ICI Reporting Accessibility Conformance Report

ICI Obligation Management Accessibility Conformance Report

ICI Sourcing Accessibility Conformance Report

ICI Proposal Management Accessibility Conformance Report

ICI SRM Accessibility Conformance Report

ICI Risk Management Accessibility Conformance Report

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