Revision as of 13:06, 3 January 2021 (view source) IDT-8 (Talk | contribs) ← Older edit		Latest revision as of 08:35, 25 June 2022 (view source) WikiSysop (Talk | contribs)
(92 intermediate revisions by 5 users not shown)
Line 1:		Line 1:
−	= ICI Release Notes - Release 7.15 =	+	= ICI Release Notes - Release 8.1 =
−	== Overview of Release 7.15 ==	+	== Release 8.1 New Features ==
−	The 7.15 Release introduces significant enhancements to the Icertis Contract Intelligence (ICI) platform. It strives to enhance user experience, intelligence, analytics, intuitiveness and usability by continually improving ICI functionalities and the user interface.	+	These release notes provide an overview of the enhancements to ICI, the ICI experience for integrations, and so on.
−	The key enhancements of this release include:	+	•      Refer to the [[#_Technical_Requirements_8.1|'''Technical Requirements''']] for the release in this document.
−	*<span style="color:#800080;">'''Enhancements to the ICI Application'''</span>	+	•&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Refer to the [https://ici-us-wiki01.icertis.com/ICIHelp8.1/index.php?title=ICI_Help '''Wiki'''] documentation (also found in your ICI help section) for details on all ICI features and functionalities.
−	**'''''User Experience'''''	+
−	***Introducing &nbsp;the ability to preview an agreement at the verifications stage, allowing users to have a comprehensive look before publishing the contract. This will help users to make updates to respective sections and understand the impact before contract creation.	+
−	***Providing &nbsp;localization support to reason codes, as per the logged in user language, thus improving the experience for new and potential customers globally.	+
−	***Enhancing the search option on index pages, so that external users can easily search records and derive more refined results.	+
−	***Displaying tagged agreement and template clauses on the respective pages in ICI Web and Icertis Experience for Word, in the same order as they are tagged inside the agreement document or template, providing a seamless user experience.	+
−	***Viewing amendments in the grid view by default, for ease of use.	+
−	***Improving the scroll length and width dynamically for multi-select and choice attributes, for better usability, data input and post-selection data review of entities, for improved experience.	+
−	***Providing the ability to configure alternate user interface (UI) control for drop-downs of choice attributes (radio button for single-select, checkbox list for multi-select) at contract type, global attributes and template variable levels.	+
−	***Defining the display sequence for masterdata records at the contract type level, using a seeded display sequence attribute, for easy and faster selection.	+
−	**'''''Workflow Enhancements'''''	+
−	***Introducing &nbsp;the ability to create instances of associations as part of the agreement creation wizard itself, thereby considerably improving usability.	+
−	***Allowing &nbsp;creation or initiation of the termination process from the contract request using role action mapping, thus providing a coherent user experience.	+
−	***Viewing clause extension attributes on the agreement entity for easy reference.	+
−	***Approving or rejecting agreements from within the email itself, thus reducing turnaround time for approval cycles.	+
−	***Reviving terminated agreements by adding amendments, instead of creating new agreements from scratch.	+
−	***Terminating agreements in bulk using the bulk actions process, thereby reducing manual errors and saving the time in terminating agreements one by one.&nbsp;	+
−	***Allowing administrator to set preferences at the time of user creation or updation, as default, according to their locations, so that ICI users can access the system with appropriate details as default after first login. &nbsp;	+
−	***Adding custom labels to external, internal and fully signed copies of agreement document versions, making them easily identifiable.	+
−	***Allowing users to skip uploading documents to move agreements from “Waiting For Signature” to “Executed state”, thereby speeding up the process when executing a large volume of documents.	+
−	***Allowing sharing associated documents as part of the various email notifications that get triggered for the agreement, rather than having to share them separately.	+
−	***Providing a separate data management user interface to manage workload, so that users can replace a user on supported &nbsp; entities with one or more users, by selecting a subset of an entity &nbsp; or on all instances of the entity, for all records available for the user.	+
−	***Defining common agreement attributes for a contract type that can be copied to amendments, by enabling the “Is Inherit On Amendments” flag, at the agreement contract type and template variable level.	+
−	***Providing the capability to control the supersede functionality for agreements by configuring rules.	+
−	***Defining multiple and complex conditions to display attributes on the ICI UI dynamically based on business scenarios.	+
−	***Providing the capability of showing or hiding the “No Team Available” message to minimize the number of clicks.	+
−	***Supporting special characters in the attribute display name for contract requests, agreements, associations and masterdata.	+
−	***Providing the ability to download all amendments of an agreement in separate folders, named “Amendment_1”, “Amendment_2”, and so on, within the downloaded zip package for ease of access.	+
−	***Supporting larger files for masterdata and associations.	+
−	***Providing faceted filters using string operators such as “Contains”, “Starts With”, “Does Not Contain” to the “Business Status” search filter, for more targeted results.	+
−	***Improving the parsing logic in ICI for handling string combinations with special and alphanumeric characters.	+
−	***Providing the ability to configure filter on a lookup attribute &nbsp; with the “IN” operator on agreement contract type and template variables.&nbsp;	+
−	***Enhancing the contract type publish capability, so that the published contract types are not available at the time of contract creation.	+
−	***Providing automation to supporting bulk upload of clauses and templates, thus reducing the dependency on manual approvals and delays in onboarding clauses and templates.	+
−	***Allowing users to add custom labels for peer associations that define various business relationships in the context of contracts (such as, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.).	+
−	*<span style="color:#800080;">'''Mobile App Updates'''</span>	+	The 8.1 Release introduces the following enhancements to the Icertis Contract Intelligence (ICI) platform:
−	**Enhancing &nbsp;the “Refresh” functionality for “Tasks” and “Commitment” tabs, to improve usability and the user experience for mobile app users.	+
−	**Updating the logo and attributes in the mobile app as per the new ICI branding guidelines.	+
−	*<span style="color:#800080;">'''Enhancements to ICI API 2.0'''</span>	+	== Icertis Contract Intelligence&nbsp; ==
−	**Providing script attributes as cascaded attributes for lookup fields and configuring them at the contract type level. This is applicable for retrieval, creation and updation of the instances of contract requests, agreements, associations and amendments.	+
−	**Adding the identifier “createCorrelationId” which can be passed by subsequent APIs for correlating from logging perspective, to ensure that the existing implementation and code does not break.	+
−	**Provisioning success or failure message for workflow operations.	+
−	*<span style="color:#800080;">'''Enhancements to ICI Add-ins'''</span>	+	=== Agreement & Platform&nbsp; ===
−	**'''''Icertis Experience for Word'''''	+
−	***Supporting &nbsp;online editing for agreement documents, and allowing contract owners to enable a subset of authorized users to participate and better control which team member can participate in the editing session.	+
−	***Improving the filtering and searching capability, so that users can easily retrieve the desired template and clause record, thus improving usability for customers handling large number of clauses and templates in the respective libraries.	+
−	***Improving labeling of internal, external and fully signed copies of agreements for easy identification.	+
−	***Defining and updating clause groups as per business requirements for easy categorization and management.&nbsp;	+
−	***Allowing tagging of clause extended attributes inside clause along with the metadata while creating or modifying clauses.	+
−	***Allowing updation of all or selected templates with the latest version of the clause whenever a clause is modified, thus eliminating the need to manually do so.	+
−	*<span style="color:#800080;">'''Enhancements to Artificial Intelligence Applications'''</span>	+	'''A new collaboration experience with Microsoft Teams'''
−	**Enhancing the AI powered legal playbook to provide more options to open the “Details” page on a larger window, and add deviations as well. All the playbook positions for a contract type now have the option to search and filer, and users can create or edit the playbook records based on their authorization. In addition, they can manage it from within Icertis Experience for Word.	+
−	**Improving the clause delineation logic to merge or split discovered clauses or selected text in a clause, and create a sub-clause within a discovered clause.	+
−	**Extending the support of formatting-based clause delineation in WordAI to PDF documents, for easy identification of section-based clauses to improve legacy migration.	+
−	**Improving discovery based on the user’s actions on attributes and clauses, to be able to use them in subsequent discoveries.	+
−	**Providing support for additional languages such as “French”, “Dutch” and “Swedish” in AI apps, for playbook discovery and contract highlights.	+
−	**Allowing users to manually trigger attribute discovery on the agreement “Attributes” page itself, while uploading third party paper, when creating or editing agreements, thus reducing the overhead of maintaining two different attributes pages.&nbsp;	+
−	**Introducing the DiscoverAI rules engine framework to quickly configure custom rules for obligations, attributes and playbook discovery.&nbsp;	+
−	**Improving &nbsp;and optimizing performance of ML service to simplify deployment and run the workload on demand, with zero or less management of infrastructure.	+
−	*<span style="color:#800080;">'''Enhancements to Reports'''</span>	+	ICI now leverages the powerful capabilities of Microsoft Teams to help internal teams collaborate on contract creation workflow and expediting the contracting lifecycle. The Teams integrations will help customers to use a single communication system and discussions can be held in context of the agreement.
−	**Introducing the “Tagged Attributes Report”, enabling administrators to understand the complete profile of an attribute and its utilization across clauses and templates.	+
−	**Introducing the “Notifications History Report” for an entity, enabling users to track notifications sent to users.	+
−	**Providing the ability to filter the “Agreement Deviation Report” and “Agreements Pending Execution Report” by “Agreement” status.&nbsp;	+
−	**Enhancing the “Clause Summary Report” to display information on extended clause attribute version.	+
−	**Adding an “Organization Unit” filter in the “Cycle Time Report” for users to be able to derive desired information.	+
−	**Improving the “Agreement Clause Content Report” so that duplicate clause text is removed and only a single record is displayed, thus improving usability.	+
−	**Adding a new column in PowerBI for “Agreement Code” which has a hyperlink that navigates the user to the agreement in ICI.	+
−	**Enhancing localization support in reports.	+
−	*<span style="color:#800080;">'''Improving the Icertis Experience'''</span>	+	The feature includes:
−	**'''''Signature Workflow'''''	+
−	***Improving the electronic signature process when using DocuSign to provide a unified flexible signature workflow. This hybrid signature process enables users to add and modify signatories, preview the DocuSign console and tag signatories in the console. Support has also been provided for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES).<br/> Enabling ICI platform to support more than one esignature vendors at the same time, to execute agreements and amendments, thus improving flexibility for users.<br/> Supporting parallel signatures in DocuSign to reduce the overall turnaround time for the complete signature process. &nbsp;	+
−	**'''''Icertis Experience for Salesforce'''''	+
−	***Providing the ability to send success and failures alerts for improved monitoring of messages.	+
−	***Triggering document assembly for automatic data sync and displaying completion notification.	+
−	***Supporting OAuth in Salesforce adapter for a more secure authentication and authorization process.	+
−	**'''''Icertis Experience for MS CRM'''''	+
−	***Providing server-to-server OAuth support, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&nbsp;	+
−	*<font color="#800080">'''Enhancements to Platform Tools'''</font>	+	*Contract owner can initiate a collaboration on MS teams from agreement details page and also invite agreement team members to participate in the discussion.
−	**Enhancing ICI to support additional entities such as orgs, org groups, users, security groups, role action mapping, currencies, reasons, attribute group, SLA matrix, notification category, default search columns, cascade team, application settings and admin saved searches.	+	*The latest version of the agreement document is also made available on the teams channel while initiating the collaboration. Participants can review, redline the agreement document in MS teams and publish the edited document back to ICI as a new version.
		+	*The documents associated with main agreement in ICI can also referenced in MS teams channel
−	*<span style="color:#800080;">'''Additions to Icertis Software Development Kit for Partner Enablement'''</span>	+	Feature ID: 1188391
−	**With this release, the following SDK documentation has been upgraded for this release – ICI Coding Guidelines, ICI Customization and Use Cases, Working with ICI Tasks, Working with ICI Hooks, ICI Developer Library, Local Environment Setup using ICI Binaries and Self-Serve Tools.	+
−	These release notes provide an overview of the enhancements to ICI, the mobile app, ICI experience for integrations, and so on.	+	'''Negotiate and Update Agreements with the new Outlook Add-in'''
−	&nbsp;	+	The new Outlook Add-in connects users’ emails with Icertis Contract Intelligence and provides improved collaboration capabilities and ensures information sent on emails is tracked for audit and governance on ICI. In addition, the new add-in provides a better interaction design, in line with the modern ACE user experience released in version 8.0.
−	== <span style="font-family: GothamMedium, sans-serif; font-size: 1.4em;">ICI Application Enhancements</span> ==	+	The Add-in for Microsoft Outlook Desktop is supported on Windows and Mac OS. Once installed, an '''Icertis Experience for Outlook''' pane is accessible from Outlook. The pane provides access to ICI agreement data, along with success and error messaging for interactions. It can be pinned on the interface for easy access.
−	<span style="color:#800080;">'''514613 – Introducing the ability to preview agreements before publishing'''</span>	+	With the Outlook Add-in improvements, users can now do the following:
−	Previously, contract owners had to view the first version of an agreement in order to get a comprehensive view of the agreement that they had created.	+	*Add attached documents in emails as associations or a new agreement version in ICI.
		+	*Preview Agreement and Association documents from the Outlook Add-in.
		+	*Drag-and-drop single or multiple emails as associations.
		+	*Replace existing associated document with a new email or email attachment.
		+	*Access agreements and associated documents from the Outlook plugin and email them attachments to reviewers or approvers any stakeholders.
		+	*New incoming messages for email threads marked as associated documents are automatically added as new associated documents.&nbsp;
−	With this release, a preview functionality is being introduced, so that primary owners or contract creators can review whether the selected template is appropriate, the rule-based clauses have been correctly added to the agreement, among other factors, and make changes to the agreement before the version is created.&nbsp;	+	Feature IDs: 1137119, 1137121
−	A “Generate Preview” button has been introduced on the “Verify stage” of agreement creation, before publishing or updating the document. The PDF preview is for indicative purposes only and is not an agreement version. Associated documents, coming through inline associations, for example, will also be included and displayed in the preview document.	+	'''Quick & Easy Agreement Creation'''
−	'''Note: '''The preview functionality is configurable and will not be available by default.	+	Agreement Contract Types now come with a Quick Creation option. For all agreements using this option, users can fill all the necessary information on a single page and publish the contract or send it for approval immediately.
−	&nbsp;	+	Feature ID: 1183356
−	<span style="color:#800080;">'''575640 – Creating associations on create or edit wizard of agreement'''</span>	+	'''More Quick Action Options'''
−	Previously in ICI, contract authors had to create associations for agreements using the association management functionality. However, in practical terms associations such as annexures, supporting documents, SLAs, product specifications, rate tables, and so on, are all an inherent part of agreement information that is critical to business.	+	The Quick Actions widget “What would you like to do” has been enhanced to provide multiple actions/links with one quick action line item. For example, “Create MSA” quick action now provides multiple links catering to “Own” and “Third Party” paper selections, as displayed in the image below.
		+	<div class="image-green-border">[[File:RN 8.1 1.png|520px|RN 8.1 1.png]]</div>
		+	Feature ID: 1183310
−	In view of this, the ability to create association instances as part of agreement creation is being introduced in this release. A separate page is displayed to the user during agreement or amendment creation to create, view or delete inline associations. The user also has an option to select the columns and their order in the association grid.	+	'''External Emails Split to Ensure Compliance&nbsp;'''
−	Support is also provided to copy attribute rules, association events and agreement assembly, in case associations are tagged in the agreement template.	+	Contracts sent for review or approval by email to other parties, legal consultants and users not within ICI are now split in two parts. A URL and passcode can be shared with the users and the review can be done completely online. No need of downloading and attaching documents and tracking versions offline. The process is quick, secure and easy to audit.<br/> Two emails are sent, One email is sent containing the agreement URL and the other with the passcode to access the URL. This method could be used for requesting reviews, reviews and approval.<br/> <br/> Users can also resend the notification to external users whose reviews are pending, with the help of the “Resend Passcode Notification” button.<br/> <br/> To enable this feature, the implementation team needs to configure it explicitly.&nbsp;<br/> <br/> Feature ID: 1216716&nbsp;
−	<br/>  <br/> <span style="color:#800080;">'''549900 – Supporting localized reason code values as per logged in user language'''</span>	+	'''Deviation management for text and tables outside content control'''
−	Adapting existing products to new markets through translation and localization is the key for global growth. The localized versions of the product improve the overall user experience and helps to better connect with new and potential global customers.	+	If changes are made to the plain text in agreements or tables in associations of an agreement document (text which is not a clause or attribute), a deviation can now be triggered to help Legal teams exercise greater content control. The changes are highlighted and the deviations will flow through an approval process.<br/> <br/> Feature ID: 1183384&nbsp;
−	ICI now extends its localization support to reason code values. Users can see localized reason codes as per their preferred language settings. Administrators can enter the translated values in the local language for each reason code using the “Translations Editor” tool. The reason code will be displayed in English if there are no local values available in the ICI system for that specific reason code.	+	'''Support for Microsoft Powerpoint documents'''
−	&nbsp;	+	ICI now supports Microsoft Powerpoint file formats (files with .ppt and .pptx extension) as third-party paper agreement file formats. In addition to PDF and DOCX file formats, users can now create and negotiate contracts using PPT and PPTX files.
−	<span style="color:#800080;">'''614944 – Initiating termination for parent agreement from contract request'''</span>	+	Feature ID: 1183367
−	In ICI, to terminate an agreement, users create and execute a termination agreement on a main agreement. ICI has now extended this capability to contract requests also.&nbsp;	+	'''Online Editing Of Own Paper'''
−	Users can enable the termination process at contract type level using the seeded attribute "Request for Termination", select the parent contract request, and create the termination contract on a contract request. The termination instance for contract request will have all the common attribute values inherited, if the inheritance is enabled. The termination record will be displayed as a peer association under the “Association” tab for the contract request.&nbsp;	+	In this release, ICI is enhancing its existing online editing feature &nbsp;by supporting online editing of own paper documents. using Microsoft WOPI.We have improved the experience for editing agreements with Microsoft Online applications In this release.
−	The access privileges for the contract requests termination process is controlled through role action mapping.	+	The following improvements can be observed:
−	&nbsp;	+	*Documents with editable content control can be edited and and values are is synced seamlessly.
		+	*The track changes option will now track all the changes made by the users in reviewing mode, creating a redlined version of the document.
		+	*The empty content control will be displayed as blank instead of “obj”.
		+	*The content controls within tables can now be edited with associations tagged as tables and saved searches.Content controls within tables will now be editable.&nbsp;
−	'''<span style="color:#800080;">506398 – Enabling search for external users with login privileges</span>'''	+	Feature ID: 1287270&nbsp;
−	ICI’s collaboration portal allows external users with login privileges to access the platform and perform tasks assigned to them within ICI itself.&nbsp;	+	'''Support for Inheritance of Bulk Associations&nbsp;'''
−	In our continuous effort to improve usability, a search option has been introduced on index pages, so that external users can easily search records. To perform a more refined search, the attributes displayed as columns of the search grid are included as facets in the filter options. This is applicable to index pages of contract requests, agreements, associations and masterdata.<br/> '''Note:&nbsp;'''This is not applicable for:	+	In addition to attributes and associations, now bulk associations contract types (BACT) and their extension attributes can now be inherited from parent to child agreements.&nbsp;
−	*Global search.	+	The agreements with BACT associations will get inherited asynchronously along with all extension attributes of all the associations. The bulk associations will also work as they do in parent agreements.
−	*Attribute group privilege restrictions on search results, filters and categories.<br/> &nbsp;	+
−	<span style="color:#800080;">'''514605 – Supporting extended clause attributes in agreements and reports'''</span>	+	Feature ID: 1278205&nbsp;
−	In ICI, users capture additional details for a clause in the extension attributes. &nbsp;	+	'''Enhancement to Download all Agreement & Associated Documents in one click''' &nbsp;
−	With this release, users will be able to view these clause extension attributes on the agreement entity for easy reference while working with agreements.&nbsp;	+	With this release, we have expanded on the Download all capability which allowed users can to download the agreement and itsall associated documents in one click saving much time and effort.&nbsp;
−	Users can now:&nbsp;	+	This functionality was earlier available when the signature type for the agreement was set to manual, it is now available for electronic and hybrid signature types as well.
−	*View additional clause attributes on the “Agreement Clause” and “Clause Approver” tabs.	+	Additionally, the “Download All” button will now be visible to users based on the role action mapping in superseded state as well.&nbsp;
−	*View the hyperlink “Show Clause Information”, which displays all clause extension attributes in a separate window.	+
−	*Select and save extension attributes to display in the grid view.	+
−	*View clause extension attributes in the “Clause Profiling Report”.	+
−	<br/> <span style="color:#800080;">'''514615 – Approving a contract from emails'''</span>	+	Feature ID: 980342&nbsp;
−	Email notifications, in ICI, allow users to customize text, add tags (attributes) inside the email body, define recipients, and so on. This capability has been further enhanced such that approvers can directly approve or reject an agreement from within the email itself, as part of the approval or request review process, thus reducing the overall turnaround time and increasing efficiency.	+	'''Platform changes to enhance UX for Business Applications'''
−	They can also add notes on approval, add reason code on rejection, and enable download or upload of the agreement document along with comments. This is applicable to contract requests, agreements, associations, amendments, masterdata, templates, clauses and user information instances.	+	To improve findability and relevance of information pertaining to a particular business application, some configuration changes are now available in the platform. These changes significantly improve the search and usability experience when working with Agreements, Associations or any Business Application.
−	&nbsp;	+	The following configurations are now supported:
−	<span style="color:#800080;">'''514643 – Ordering of clauses as tagged in an agreement'''</span>	+	*Business Applications have dedicated index pages, where users can search for the information pertaining to the specific business application.
		+	*Agreements and Associations index pages do not show information from Business Applications.
		+	*On the Advanced Search page, users have a choice to search for information from Agreements or specific business applications.
		+	*Left navigation of a business application entity page can be configured to show the relevant links.
		+	*Results for global search are categorized by the business application name if they are not Agreements or Associations.
		+	*When creating a Contract Type, seeded attributes only relevant to the Business Application Type and Category can be seededwill be selected.
−	Previously in ICI, list of clauses available inside the agreement or amendment displayed clauses in a random order on the “Agreement Clauses” tab, in ICI Web and Icertis Experience for Word.	+	Feature ID: 1183274&nbsp;
−	With this release, the tagged clauses are displayed on respective pages in ICI Web and Icertis Experience for Word, in the same order in which they are tagged inside the agreement, thus making it easier for users to identify them. The order is refreshed on every upload to display the latest.	+	=== Self-Service ===
−	&nbsp;	+	'''Introduction of a Technical Admin user to access the System Configuration on Self Service Portal'''
−	<span style="color:#800080;">'''514621 – Reviving terminated agreements'''</span>	+	With the risk of inaccuracies in technical configurations, given their critical importance, such configurations have been, till now, hosted outside the confines of ICI, where ICI admin users, who have azure subscriptions to an instance, authored the process.
−	Users may terminate an agreement with the other party for various business reasons. To improve usability, ICI now provides the capability to add and execute amendments on a terminated agreement. This considerably saves the time for users who may want to re-instantiate their existing relationship with the other party, as they no longer need to create an entirely new agreement, and go through several workflows such as clause deviations clearance, template process, and so on.	+	Therefore, the capability of admin users within ICI were being limited and the scope of technical configurations had to be expanded.
−	Adding and executing an amendment on a terminated agreement will move the agreement back to the “Executed” or “Expired” state, based on its expiry date, thus reviving the terminated agreement. It will also revive any amendments of the base agreement terminated through the agreement termination process and move them back to their respective previous states. However, any previous amendments terminated through review process will remain in the terminated state. &nbsp;	+	Now, a solution has been devised with this feature, as enunciated in the following:
−	Users can set an identifier attribute "Is Termination Revived" for such revived base agreements and use them in search filters, configuring saved searches, notification rules, and so on.	+	*Technical Administrators can now be configured/added for performing required technical configurations in the System Configuration Portal, using the new “Technical Roles” field while adding, provisioning or editing a user.
−	'''Note: '''By default, only primary owners and contract managers can add an amendment to the terminated agreement. The access privileges are controlled through role action mapping.&nbsp;<br/> &nbsp;	+	'''Note:''' The user has to be Internal in order to be authorized with “Technical Roles”, and selecting an external user will automatically discount the Technical Roles feature.
−	<span style="color:#800080;">'''514625 – Terminating agreements in bulk'''</span>	+	*The portal has been upgraded for Technical Admin users, with enhancements to the Landing page, header, menu options, along with a static welcome message.
		+	*Appropriate messaging and communication will be provided for any negative scenarios, wherein the Technical Admin User faces any challenge accessing or configuring.
		+	*When a new ICI admin user logs in, they should be able to setup other internal users as technical admin users of the System Configuration portal.&nbsp;
−	Users may need to terminate agreements in bulk in many business scenarios such as regulatory changes, changes in product offerings, and so on. Users can now initiate termination of agreements in bulk, thereby reducing the manual errors and saving the time to terminate agreements one by one. Bulk termination is carried out using ICI’s existing “Bulk Actions” process. The termination related attributes will be pre-selected, and the Workbook for the bulk action batch will be generated with the executed agreement records from the saved search, as per the selected contract type and termination contract type.&nbsp;	+	'''Note:''' Only the ICI Admin user should be able to setup other internal provisioned users as the Technical Admin user.
−	Users can now:&nbsp;	+	*The ICI Admin can either create a new Security group, as required, or use an existing security group.&nbsp;
		+	*The authorization of technical admin users will depend on Security Groups Privilege to the “Self Service” privilege entity, and on roles assigned to specific users.
		+	*The “Self Service” privilege can be configured in the backend and it will be visible to users under the Security Group Privilege tab.
		+	*The “Manage” access option can be selected to grant access to the System Configuration Portal for technical admin users.
−	*Initiate the termination workflow using “Bulk Actions”, by creating and executing a new batch. &nbsp;	+	'''Note:''' The user who gets Technical Admin privileges can be any internal provisioned user on that instance (even a non admin user).
−	*Generate and view a status report for agreements terminated in bulk.&nbsp;	+
−	*Create termination agreements for “Draft”, “Published” or “Send for Approval” states, as per the batch Workbook configuration for bulk action.	+
−	'''Note: '''All the prerequisite configurations applicable for the Termination workflow should also be set for the bulk termination process.<br/> &nbsp;	+	Feature ID: 1210894
−	<span style="color:#800080;">'''555898 – Defining display sequence on lookup attributes at contract type level'''</span>	+	'''Building the Config Key Update utility as part of the System Configuration on Self Service Portal'''
−	Previously in ICI, users could not define the display order for lookup attribute’s values in a drop-down on ICI UI to reference masterdata. Users then had to scroll through all populated values in order to find the desired values during agreement creation. &nbsp;	+	Today, in ICI – There are close to 800 configuration keys in the system. These keys are managed via the ICM Tools which is hosted outside of ICI. With this initiative, we have started the migration these Keys incrementally to be part of the System Configuration – Self Service Portal.&nbsp;
−	The configurators can now define and maintain the display sequence for masterdata records, starting from 1 to n, at the contract type level, using a seeded display sequence attribute. The configurators can also define the order only for selected records in the masterdata. The frequently selected values will be thus displayed at the top for easier and faster selection in lookup attributes, without the need to scroll through all values. &nbsp;	+	The scope for this release is to migrate 10 keys into the utility. The access to this utility is driven by the Technical Admin role as explained in the previous section.&nbsp;
−		+
−	This setting of display sequence is supported on create, edit and lookup search pages of contract requests, agreements, amendments, associated documents, extended clause and template entities, and template variables.	+
−		+
−	The display will revert to the default alphabetical order if the display sequence is not configured in masterdata.&nbsp;	+
		+	Once the user successfully enters the ‘System Configuration – Self Service’ portal with the correct security groups and technical admin role, they will be able to see the ‘Config Key Updates’ entry point at the top of the screen
		+	<div class="image-green-border">[[File:RN 8.1 2.png|720px|RN 8.1 2.png]]</div>
		+	On clicking the Config Key Updates menu, the user will be able to see the utility where the defined 10 keys will be loaded on the screen, along with their existing values.
		+	<div class="image-green-border">[[File:RN 8.1 3.png|720px|RN 8.1 3.png]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#800080;">'''558605 – Viewing amendments in grid view on agreement details page'''</span>	+	The user will be able to view each key loaded into a card. The card will contain the name of the key along with it’s value.&nbsp;
−	Previously in ICI, users could only view the agreement’s amendments in a “Tile” view, when opened from the left navigation pane on the agreement “Details” page.&nbsp;	+	The user will be able to see a dedication section to the right of the page for viewing help information
−	ICI now allows users to view amendments in “Grid” view as well, and have the capability to toggle between the grid view and existing tile view. The grid view is the default view for amendments and supports all existing grid functionalities, such as standard search, filter, column selection, pagination, export to CSV/Excel, and so on.<br/> &nbsp;	+	The user will be able to click on the ‘3-dot’ option on each card to edit the value of the key
−		+	<div class="image-green-border">[[File:RN 8.1 4.png|720px|RN 8.1 4.png]]</div>
−	<span style="color:#800080;">'''561410 – Enhancing the multi-select drop-down&nbsp;'''</span>	+	&nbsp;
−		+
−	The multi-select choice drop-down has been enhanced for better usability, data input and post-selection data review of contract requests, agreements, amendments and masterdata entities.&nbsp;	+
−		+
−	Users can now:&nbsp;	+
−		+
−	*View eight default options in a drop-down list (instead of six), without scrolling.&nbsp;	+
−	*View larger values with adjusted drop-down width, according to its size, in the post-selection view.&nbsp;	+
−	*View all selected values at the top of the drop-down.	+
−	*Deselect the selected values individually or all with a single-click, without opening the drop-down.<br/> &nbsp;	+
−		+
−	<span style="color:#800080;">'''819453 – Configuring opening of drop-down menus on mouse hover'''</span>	+
−		+
−	ICI has improved usability by providing the capability to configure the expansion of drop-downs on mouse hover, instead of a mouse click.&nbsp;	+
−	This can be configured at a contract type level and supports contract requests, agreements, associated documents and masterdata. It is applicable for lookup, multi-select lookup, choice, multi-select choice and currency drop-downs.	+	On clicking the Edit option, the key information will be loaded in the right drawer panel. Here the user can edit the key value and Save using the button at the bottom of the drawer
		+	&nbsp;
		+	<div class="image-green-border">[[File:RN 8.1 5.png|720px|RN 8.1 5.png]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#800080;">'''620411 – Defining IN operator when applying lookup filters'''</span>	+	The user can edit one or more keys using the ‘3-dot’ option on each card. Once the user has finished editing all the keys, they need to click on the ‘PUSH CHANGES TO ICI’ button at the top of the grid. This will internally update the keys with the edited values in ICI for the changes to take effect
−		+
−	In ICI, the configurator can filter the lookup masterdata table with “Must” and “Must Not” conditions, to achieve necessary business scenarios, while configuring a lookup attribute on contract types.&nbsp;	+
−		+
−	ICI now also provides the ability to configure a lookup attribute with the “IN” filter operator, and display selected multiple values, by referencing multiple values on another lookup master data attribute.&nbsp;	+
−		+
−	Configurators can now:&nbsp;	+
−		+
−	*Use the "IN” operator in lookup filter attribute on agreement contract types.&nbsp;	+
−	*View applied filter on the attribute “Details” tab on ICI UI for the selected attribute.&nbsp;	+
−	*Standard ICI users can view only selective values in the lookup attribute as per the referenced value in another attribute. &nbsp;<br/> &nbsp;	+
−		+
−	<span style="color:#800080;">'''573339 – Managing user preferences as part of profile management'''</span>	+
−		+
−	Users can set preferences for their ICI Web UI account such as language, color theme, time zone, and so on.&nbsp;	+
−		+
−	ICI now provides the capability for administrators to set preferences as default, for users, according to their locations or offices they work in. This reduces the end user’s effort of setting up the ICI account with required parameters after first log-in, and presents the system with appropriate and specific pre-settings. &nbsp;&nbsp;	+
−		+
−	Administrators can:&nbsp;	+
−		+
−	*Set and manage preferences for single user through single user update, and for multiple users through bulk process.	+
−	*View preference settings modifications details in the “History” tab for audit.&nbsp;	+
−	*Search users based on parameters related to preference settings.	+
−		+
−	Users can:&nbsp;	+
−		+
−	*Access the ICI system with appropriate details as default after first login.&nbsp;	+
−	*Override the default preference settings as per individual preferences.	+
	&nbsp;		&nbsp;
		+	<div class="image-green-border">[[File:RN 8.1 6.png|720px|RN 8.1 6.png]]</div>
		+	Feature ID: 1180864
−	<span style="color:#800080;">'''604775 – Moving agreement to executed state without uploading document'''</span>	+	=== Administration & Configuration&nbsp; ===
−	Previously in ICI, users could not move agreements and amendments from “Waiting For Signature” to “Executed” state without uploading the supporting document, in case of manually signed agreements.&nbsp;	+	'''Quick Configuration with ICI Import Solution'''
−	With this release, users can now skip uploading the document to move agreements from “Waiting For Signature” to the “Executed - Document Upload Pending” state. Users can then search or create a saved search for such agreements and upload the required documents later using the “Upload Fully Signed Copy” action.&nbsp;	+	The ICI Import Solution is an automated solution for configuring ICI entities. It simplifies the initial configuration process and reduces the time and complexities involved in the process.
−	Notifications can be configured to inform users about skipped document uploads, so that users can cover for delays occurring due to the scan and upload process while executing a large volume of documents.&nbsp;	+	Using the Import Solution tool, ICI users can now:
−	This functionality is available for agreements, amendments and orphan amendments.<br/> &nbsp;	+	*Import configurations from a source ICI instance to a target ICI Instance with no pre-existing configuration data.
		+	*Import configurations between different versions of ICI.
−	<span style="color:#800080;">'''614860 – Attaching associated documents to agreement notifications'''</span>	+	'''Note:''' Support will be provided for up to 2 releases preceding the target ICI version.
−	ICI users could share the main agreement document as part of various email notifications that get triggered for the agreement from time to time.&nbsp;	+	*Register and publish preconfigured import solutions.
		+	*Import the following information:
		+	*Contract Types
		+	*Templates
		+	*Clauses
		+	*Rules
		+	*Notifications
		+	*Masterdata Instances
		+	*Seeded Masterdata entity instances
		+	*Users & User Groups
		+	*Security Groups
−	This capability has now been extended to supporting (associated) documents as well, so that users no longer need to manually share them offline.	+	Feature ID: 1262996&nbsp;
−	With this release:	+	'''Contract Types can now be locked for editing&nbsp;'''
−	*Administrators can tag the associated document contract type in the email notification template for agreements, assignment agreements, termination agreements and amendments.	+	Contract types can now be edited by only one user at a time. This functionality helps prevent data inconsistencies or concurrency errors.
−	*Users can define the notification as internal or external.&nbsp;	+
−	*Users can define the type of associated document instance as internal, external or restricted.	+
−	*Based on the type of notification and type of tagged associated documents, documents are attached to the email notification.	+
−	&nbsp;	+	Product enhancements include:
−	<span style="color:#800080;">'''586492 – Defining different relationship types while associating peer instance'''</span>	+	*A Lock/Unlock button on the contract type page.&nbsp;
		+	*Auto system lock when users start edit a contract type without locking it.&nbsp;
		+	*Messaging providing information on who is editing the contract type.&nbsp;
		+	*System locks get released when contract types are saved.
−	ICI allows users to define the linkage type as parent, child or peer while associating peer entities with each other.&nbsp;	+	Feature ID: 1212463&nbsp;
−	Users now have the capability to define custom labels for peer associations by configuring the “Linkage Type” masterdata. The custom labels define various business relationships in the context of contracts. For example, “Related To”, “Linked To”, “Addendum Of”, “Addendum To”, “Parent To”, “Child To”, and so on.&nbsp;	+	'''Enhancements to Legacy Upload Tool'''
−	The custom labels will support existing two-way linkage and self-linkage types. The amendments on executed agreements will be associated as peer, with default peer linkage type label, defined in default peer mapping for amendment.&nbsp;	+	The following features will be added to the Legacy Upload utility with this release, improving speed and accuracy and reducing file size.
−	Users can select custom peer linkage type labels in the linkage type drop-down list and view them on various ICI functionalities as: &nbsp;	+	*Records bypass workflow states directly to the desired state.&nbsp;
		+	*Users can schedule upload in batches within guardrails to improve system resource allocation.&nbsp;
		+	*Specific range of records from the UI can now be uploaded.
		+	*Infra and Elastic Search health check can be run before executing the scheduled batches.
		+	*On demand batch scheduling based on the user provided schedule.&nbsp;
		+	*Supporting legacy entity created with large files 100MB+.
−	*Agreement creation workflows for peer entities, assignment, initiate termination flow.&nbsp;	+	Feature ID: 1069763
−	*Associate and Inheritance icons.	+
−	*Legacy upload and bulk actions.	+
−	*Agreement creation through business APIs.	+
−	*Broadcast – “Attachments” tab, beside peer-to-peer instances.	+
−	'''Note: '''Custom labels are not supported for parent and child linkage types, as there is specific business logic built with them in the ICI system.	+	'''Unique clause and template code for every environment'''
−	&nbsp;	+	Users can now customize their clause and template codes for different instances. If unique codes are used, it reduces errors when migrating data from one instance to another. It also simplifies searching of clauses and templates.
−	<span style="color:#800080;">'''619558 – Downloading amendments using download all functionality'''</span>	+	Feature ID: 938126
−	ICI users can download an agreement and all its associations in a zip file using the “Download All” action available on agreements and bulk operations.&nbsp;	+	'''Template and Clause creation options in Microsoft Word'''
−	With this release, users can also selectively download amendments of an agreement with corresponding parent child associations in the downloaded zip package.	+	The Create Template and Create Clause options in the Icertis Experience for Word are only displayed to users with access to these features. Earlier an error message was displayed to users without access and resulted in an unsatisfactory experience.
−	For ease of access, each selected amendment will be downloaded with its selected associations in separate folders. The folders are named “Amendment_1”, “Amendment_2”, and so on (from oldest to latest), instead of actual amendment names. This helps to overcome the Windows limitation of supporting 260 characters in the file path, and gives users the flexibility while creating association’s names.<br/> &nbsp;	+	Feature ID: 1187041
−	<span style="color:#800080;">'''615291 – Configuring attributes inheritance for amendments at contract type level'''</span>	+	'''Show or Hide confirmation messages in Microsoft Word&nbsp;'''
−	ICI already provided the capability to exclude certain agreement attributes from being copied to the amendment through technical configuration which applied to all agreement contract types by default.&nbsp;	+	Administrators can now choose to show or hide certain confirmation messages, as per the organization's preference, on the Icertis Experience for Word.
−	ICI now provides the flexibility for users to decide which attributes of an agreement can be copied to amendments, per contract type, as per business requirements. Configurators can enable or disable the attribute’s inheritance for amendments, using “Is Inherit On Amendments” attribute, at the agreement contract type and template variable levels. Users can then copy these defined attributes values from base agreement to amendment during amendment creation.&nbsp;	+	Feature ID: 1187044
−	'''Note:&nbsp;'''	+	=== Technology Updates ===
−	*The technical configuration settings for excluding parent agreement attributes from its amendments will always take preference over the settings at agreement contract type and template level.	+	'''ServiceBus upgraded to Azure.Messaging.ServiceBus'''
−	*The existing validations or dependencies for an attribute’s properties set for agreement will not be inherited to amendments.<br/> &nbsp;	+
−	<span style="color:#800080;">'''614877 – Replacing a user with multiple users'''</span>	+	“Azure.Messaging.ServiceBus” is now replacing “Microsoft.ServiceBus”. &nbsp;<br/> <br/> This is a Microsoft recommended upgrade and provides the following improvements:
−	In ICI, administrators can replace user(s) with all associated records using the “Replace User” functionality. In practice, administrators may need to replace a user with more than one user. For example, if a user leaves the organization, the administrator may want to replace that user by dividing agreements associated with that user, in subsets, among multiple users. This would help the organization to balance the workload within its employees. &nbsp;	+	*Up-to-date, streamlined Azure.
		+	*More accurate messaging without any anomaly or junk data in the message characters.
−	Administrators can now:&nbsp;	+	<br/> Feature ID: 940871
−	*Replace the user with one or more users by selecting the entity and all/selective instances of that entity. &nbsp;	+	'''Authentication Library and Graph API update'''
−	*Validate the replaced user role against the assigned role.&nbsp;	+
−	*Get notification on adding or completing a task.&nbsp;	+
−	This capability is available across ICI for contract requests, agreements, associations, masterdata, template and clause teams, user groups, and rules. A separate data management user interface is provided for these admin actions.<br/> &nbsp;	+	Microsoft has announced* deprecation of the Azure Active Directory (Azure AD) Authentication Library (ADAL) and Azure AD Graph API libraries and recommends using Microsoft Authentication Library (MSAL) and Microsoft Graph API.
−	<span style="color:#800080;">'''614963 – Superseding agreement values as per amendment using rules'''</span>	+	We have updated Microsoft Graph, Identity and Key Vault packages to include stability and security fixes from Microsoft. The migration from ADAL and Azure AD Graph API to MSAL and Microsoft Graph API will ensure continuing support for the following areas:
−	In ICI, users could supersede all parent agreement’s attributes configured as supersedable with values from its amendment, either manually using “Supersede” action or automatically through auto-supersede backend task.&nbsp;	+	*User Provisioning&nbsp;
		+	*Bulk Action&nbsp;
		+	*Integration - SFDC, GIF (Generic Integration Framework), MSCRM &nbsp;
		+	*Reporting&nbsp;
		+	*Key Vault&nbsp;
−	With this release, users can now selectively supersede individual entities based on business conditions.	+	Refer to the following link for Microsoft’s circular: [https://techcommunity.microsoft.com/t5/azure-active-directory-identity/update-your-applications-to-use-microsoft-authentication-library/ba-p/1257363 Update your applications to use Microsoft Authentication Library and Microsoft Graph API - Microsoft Tech Community].
−	The administrator can control the supersede functionality for agreements by configuring rules with:&nbsp;	+	Feature ID: 1276938
−	*The rule type “Supersede Rule” with an “Auto Supersede option”, as true or false.&nbsp;	+	=== API Enhancements ===
−	*The rule actions as “Is Auto Supersede by Amendment”, “Is Auto Supersede by Termination” and “Is Auto Supersede by Assignment for Amendment”, “Assignment and Termination”, with required attributes set, as per the business condition.	+
−	*The attribute selection field with all or multi-select capability.&nbsp;	+
−	Users can preview the attribute’s supersede value on the agreement and view the captured history as per the rule execution. When no rule is configured, the supersede functionality will work as per existing behavior.	+	In this release we focused on providing API 2.0 versions of most of our APIs with a goal to improve the performance and overall usability.
−	&nbsp;	+	Following APIs are upgraded to API 2.0 versions in this release:
−	<span style="color:#800080;">'''615293 – Showing or hiding the no team available message'''</span>	+	[[File:RN 8.1 7.PNG|720px|RN 8.1 7.PNG]]
−	In ICI, users may encounter specific workflow configurations such as self-approval process that do not require users to be added to the team. The “No Team Available” messages, displayed in such cases, add to the number of non-value clicks for users to continue. &nbsp;	+	[[File:RN 8.1 8.PNG|720px|RN 8.1 8.PNG]]
−	ICI now provides the capability to suppress this message, thereby minimizing the number of unnecessary clicks through technical configuration.&nbsp;	+	[[File:RN 8.1 9.PNG|720px|RN 8.1 9.PNG]]
−	Administrators can:&nbsp;	+	[[File:RN 8.1 10.PNG|720px|RN 8.1 10.PNG]]
−	*Selectively enable or disable the “No Team Available” message window, at entity contract type level, appearing at various states.&nbsp;	+	[[File:RN 8.1 11.PNG|720px|RN 8.1 11.PNG]]<br/> [[File:RN 8.1 12.PNG|720px|RN 8.1 12.PNG]]
−	*Disable the “No Team Available” message window completely, at instance level, for all entities. The instance level settings will override any entity level settings.&nbsp;	+
−	'''Note:''' This capability is available across ICI for all entities, events, integrations and add-ins in ICI.	+	[[File:RN 8.1 13.PNG|720px|RN 8.1 13.PNG]]<br/> <br/> [[File:RN 8.1 14.PNG|720px|RN 8.1 14.PNG]]
−	&nbsp;	+	[[File:RN 8.1 15.PNG|720px|RN 8.1 15.PNG]]
−	<span style="color:#800080;">'''618345 – Defining complex conditional logic for attributes visibility'''</span>	+	[[File:RN 8.1 16.PNG|720px|RN 8.1 16.PNG]]
−	Previously, users could configure a conditional attribute for a contract type with simple conditions using single “equal to” operator.&nbsp;	+	[[File:RN 8.1 17.PNG|720px|RN 8.1 17.PNG]]
−	With this release, configurators can now set multiple, complex conditions to display attributes on ICI Web UI dynamically, based on business scenarios. Configurators can define conditions for attributes for all entities, except for template variables. For example, the configurator can set conditions to display an attribute based on the selection of specific value in any of the attributes mentioned in the condition. The user experience would be similar to the existing ICI conditional attribute functionality. &nbsp;	+	[[File:RN 8.1 18.PNG|720px|RN 8.1 18.PNG]]
−	Users can now:&nbsp;	+	[[File:RN 8.1 19.PNG|720px|RN 8.1 19.PNG]]
−	*Apply multiple and complex conditions to display an attribute by enhancing the enable expression (visibility expression) for contract requests, agreements, associations and masterdata contract types.&nbsp;	+	[[File:RN 8.1 20.PNG|720px|RN 8.1 20.PNG]]
−	*Support conditional expressions for extension attributes. &nbsp;	+
−	*Define conditions with different operators based on the selected attribute datatype.&nbsp;	+
−	*View the conditional attribute value according to the value entered in the attribute on which a condition is set, which in turn helps to enter the information in the required attribute as per business requirements.<br/> &nbsp;	+
−	<span style="color:#800080;">'''616901 – Applying facets to business status search filter'''</span>	+	[[File:RN 8.1 21.PNG|720px|RN 8.1 21.PNG]]
−	Previously, the ICI search functionality supported filters on “Business Status” for users to narrow down results. However, manually selecting filters often becomes a tedious task in case of several business statuses.&nbsp;	+	[[File:RN 8.1 22.PNG|720px|RN 8.1 22.PNG]]
−	In order to provide a better user experience, faceted filters using string operators, such as “Contains”, “Starts With”, “Does Not Contain”, and so on, are being added to the “Business Status” filters for ease of use.	+	[[File:RN 8.1 23.PNG|720px|RN 8.1 23.PNG]]
−	&nbsp;	+	[[File:RN 8.1 24.PNG|720px|RN 8.1 24.PNG]]
−	<span style="color:#800080;">'''694211 – Improving handling of exceptions for string combinations'''</span>	+	[[File:RN 8.1 25.PNG|720px|RN 8.1 25.PNG]]
−	Previously, some combinations of special and alphanumeric characters used as input values resulted in generic exceptions. The parsing logic in ICI is now improved for handling string combinations with special and alphanumeric characters, so that no errors are generated.	+	[[File:RN 8.1 26.PNG|720px|RN 8.1 26.PNG]]
−	This is applicable to all entities across ICI, where a combination of special characters, alphabets and numbers can be used.	+	[[File:RN 8.1 27.PNG|720px|RN 8.1 27.PNG]]
−	&nbsp;	+	[[File:RN 8.1 28.PNG|720px|RN 8.1 28.PNG]]
−	<span style="color:#800080;">'''732929 – Uploading clauses and templates in bulk'''</span>	+	'''API Deprecations'''
−	New customers or new groups, onboarding to ICI, mostly have their templates and clauses already created in a separate file. Previously, manual efforts were needed to onboard the hundreds to thousands of templates and clauses.&nbsp;	+	Any integrations utilizing the deprecated APIs must adopt alternate APIs. Previously, API endpoints have been periodically deprecated and alternate APIs have been provisioned.
−	With this release, an automation has been provided for bulk import, which will reduce any human dependency, manual approvals and delays for onboarding templates and clauses using the current capabilities. ICI administrators can now import templates and upload clauses to ICI in bulk.<br/> &nbsp;	+	However, no existing API endpoints have been deprecated in the 8.1 Release. To check previously deprecated endpoints, refer to 7.16 Release Notes. More details on the alternate APIs are available in the Swagger documentation.
−	<span style="color:#800080;">'''655507 – Uploading and downloading large files with file path attribute'''</span>	+	=== Mobile App Update&nbsp; ===
−	ICI now provides support for larger files. This is applicable to masterdata and associations.	+	'''Improved Security on Mobile Devices with SafetyNet Attestation API'''
−	Users can now:	+	With this release, ICI is implementing SafetyNet Attestation API for Android mobile application to restrict users from accessing the application through rooted/vulnerable device, to avoid breaching of the IT and cyber security policy.
−	*Upload files up to 4GB under the file selection attribute.&nbsp;	+	'''Note: '''The SafetyNet Attestation API is supported Android version 8.0 onwards.
−	*Upload files with all supported files extensions allowed in the file selection attribute.	+
−	*Download All/Download Package up to 6 GB.	+
−	ICI supports virus scanning of large files if the virus scan feature is enabled.<br/> &nbsp;	+	Feature ID: 1095223
−	'''Note:&nbsp;'''This is not applicable for contract requests, agreements, associations with large files in the DocuSign/Adobe Sign association selection pop-up, document assembly, bulk actions, legacy upload, integrations (Salesforce, Workday, etc.), and APIs.	+	== AI Applications&nbsp; ==
−	&nbsp;	+	Usually, the implementation team spends a lot of time analyzing and training the AI model for the discovery of the new attributes. With this release, ICI is extending the number of pre-trained attributes so that the AI apps implementation project can be expedited. ICI previously had added 23 out-of-the-box attributes and introducing 15 additional attributes in this release, making it a total of 38 new attributes as a part pre-trained model. Customers can now start using attributes from pre-trained model with no or very little retraining.
−	<span style="color:#800080;">'''697367 – Enhancing contract type publish to limit schema change for entity'''</span>	+	The additional attributes are:
−	ICI has made the following enhancements to the contract type publish capability:	+	*Acceptance Completion Period
		+	*Breach Cure Period
		+	*Confidentiality Survival Period
		+	*Force Majeure Period
		+	*Interest Percentage on Payment Delay
		+	*Liquidated Damages Cap
		+	*Policy changes notice period
		+	*Records Retention Period
		+	*Renewal notice period
		+	*Signatory Name
		+	*Signatory Title
		+	*Signature Date
		+	*Termination for cause notice period
		+	*Termination for convenience notice period
		+	*Warranty Claim Period
−	*There is zero downtime when a contract type is published.&nbsp;	+	Feature ID: 1187824
−	*The schema of only selected contract types that are being published will be blocked for write operations, hence they will not be available at the time of contract creation. However, all other contract types will be available to the user.<br/> &nbsp;	+
−	<span style="color:#800080;">'''618994 – Supporting special characters in agreement templates'''</span>	+	=== Enhancing the scope of DiscoverAI app& Negotiate AI differentiation ===
−	Previously in ICI, attribute names did not support special characters.	+	Discover AI helps users to identify attributes and clauses in browser and save them in the system.
−	Now, support is provided for special characters in the attribute display name. The characters *(asterisk), - (dash),&nbsp;: (colon), ( (parenthesis open), ) (parenthesis closed), ’ (apostrophe), , (comma), and . (dot) can be used in the display name of attributes for contract requests, agreements, associations and masterdata contract types. The same attribute display name as provided by the configurator will now be displayed including special characters.	+	With this release, scope of DiscoverAI has been enhanced to include the discovery of attributes and clauses within Microsoft word also using Icertis Experience for Word plugin.&nbsp;
−	Also, during template creation, user can add a “SkipEmptyColumns” property while tagging an association or a saved search as a table. This allows empty columns to be skipped in document assembly, thereby reducing unnecessary empty columns.	+	*The following actions/functionalities will be available under the Discover AI license in Icertis experience for Word:&nbsp;
		+	*Discovery of attributes and clauses.&nbsp;
		+	*Confirm, Confirm with Deviation, Ignore, Compare and Replace the clauses based on discovered clauses data.&nbsp;
		+	*Select the Matched Clause from the library.&nbsp;
−	&nbsp;	+	Feature ID: 1284012
−	<span style="color:#800080;">'''573336 – Displaying drop-downs as radio buttons or checkbox list for user selection'''</span>	+	== Reports Enhancements ==
−	With this release, ICI provides new controls for multi-select and single-select choice attributes.&nbsp;	+	=== Data for agreements awaiting signature in reports ===
−	Users can configure an alternate UI control for drop-downs with limited number of values for choice attributes at contract type, global attribute and template variable levels. This improves the user experience as the number of clicks and scrolls required to view options in a drop-down are considerably reduced, and provides better readability in terms of post-selection data review. &nbsp;&nbsp;	+	Out-of-the-box ICI reports will now display details for the business status “Waiting for Signature”, in addition to existing statuses. This update to the reporting logic resolves an existing gap in the reports data.
−	Users can select:&nbsp;	+	This enhancement applies to the following reports:
−	*Radio button for single-select choice attributes.&nbsp;	+	[[File:RN 8.1 29.PNG|520px|RN 8.1 29.PNG]]
−	*Checkbox list for multi-select choice attributes.	+
−	The configuration is applicable for creation and editing of contract requests, agreements and amendments.<br/> &nbsp;	+	Feature ID: 1071182
−	<span style="color:#800080;">'''752540 – Upgrading client-side libraries'''</span>	+	=== Custom reporting views using JSON&nbsp; ===
−	With this release, some client-side libraries have been upgraded, whereas some that were not being used have been removed.&nbsp;<br/> &nbsp;	+	Developers can now create new custom reports views using Stored Procedures (SP) and JSON files. This feature gives flexibility to organizations to easily develop new reports relevant to their business requirements.
−	== Mobile App Updates ==	+	An Import SP is now available that takes JSON files as input. The JSON file used for input is where developers can define the new view. New reporting views are automatically created on running the Import SP.
−	<span style="color:#800080;">'''773907 – Refreshing tasks and commitments'''</span><br/> Icertis mobile app users perform actions such as approve, reject and request review on contract requests and agreements. However, the status of the requests or agreements list did not automatically refresh. Enhancements have now been made to the “Refresh” functionality for “Tasks” and “Commitment” tabs to automatically refresh on these actions and improve usability.	+	An Export SP is also provided, which can be used to download&nbsp;a JSON file which contains the structure of an existing view in the database, to use as a template to create a new views.
−	&nbsp;	+	Feature ID: 1208472
−	<span style="color:#800080;">'''850259 – Updating logo and attributes to new guidelines'''</span><br/> As part of our effort to consistently improve user experience, the logo and all attributes in the mobile app have been updated as per the new ICI branding guidelines.	+	=== Dataset and seeded dashboard for Proposal Management application ===
−	&nbsp;	+	A dedicated Power BI Dataset is now available for the Proposal Management application for out-of-the-box and custom reporting.&nbsp;&nbsp;
−	<span style="color:#800080;">'''773923 – Changing compatibility in Android 11'''</span><br/> With this release, Android 11 compatibility changes have been made by setting the target SDK version to 30 for and deprecated methods have been updated.	+	PM App Power BI report will have clickable links to ICI entity details page for Proposal Management Entities such as, Sell Side RFx, RFx Qualification, and Bid Proposal.
−	&nbsp;	+	Feature ID: 1232650
−	<span style="color:#800080;">'''773917 – Deprecating the UI WebView component for iOS'''</span><br/> With this release, the UI WebView component for iOS has been deprecated.	+	=== Attribute Information Report Enhancements ===
−	&nbsp;	+	The following filters and columns are added to the Attribute Information report giving more options to analyse the Attributes used in the system.
−	== ICI API Enhancements&nbsp; ==	+	*Filters: Contract Type, and Group by Property Columns: Is Mandatory and Tracking Attribute
−	<div class="image-green-border">	+
−	<span style="color:#800080;">'''704069 – Enhancing ICI API 2.0 implementation'''</span>	+
−	With this release, support has been added for script and integrated attributes. They are available as cascaded attributes for lookup fields, when configured at the contract type level.&nbsp;	+	Feature ID: 1158976
−	This is applicable for visualize, retrieval, creation and updation of the instances of the following entities:	+	=== Edit SSRS Reports without customization ===
−	*Contract Requests	+	Icertis and partner developers can now edit the SQL Server Reporting Services (SSRS) reports eliminating the need to create additional customized reports even for small changes. Users can now make the following edits to SSRS reports:
−	*Agreements	+
−	*Associations	+
−	*Amendments	+
−	New visualize endpoints have also been added for the above entities to get information about their attribute and template configuration.	+	*Add or remove columns in an existing report.
		+	*Modify column’s position, name, or default values.
		+	*Modify sorting order of the results.
		+	*Apply query level filters.
		+	*Apply security group access as standard reports.
		+	*Create copy of existing report and modify it.
		+	*Use a new framework, which has a JSON-based interface.
		+	*Create new or modify custom reports.
−	&nbsp;	+	Feature ID: 744814
−	<span style="color:#800080;">'''756815 – Downloading associated document API'''</span>	+	=== Report-based edit access for Power BI reports ===
−	ICI already supports downloading agreements.	+	Manage access for Power BI reports can now be provided at a report level to ensure that edit access is only given to the necessary users within the organization.<br/> This feature works does not impact “Advanced Analytics” access.<br/> <br/> Feature ID: 1070905
−	As part of our efforts to continually improve ICI, in this release, new API endpoints have been added to download contract request associated document and agreement associated document.	+	=== Maintainance and storage optimization with a Common Data Model for Clause-based reports ===
−	&nbsp;	+	PlatformClause - a common data model for clause related information can now be used to create clause-based reports such as Clause Profiling Report, Clause Pending Approval Report and more. This helps optimize storage capacity and reduces the development and maintenance effort siginificantly.&nbsp;<br/> <br/> Feature ID: 1083685
−	<span style="color:#800080;">'''731961 – Provisioning success or failure message for workflow operations'''</span>	+	=== SSRS Reports now available with Power BI ===
−	As workflow APIs are asynchronous, customers using Actions API and API 2.0, get a return success code only on initiation of the workflow. This functionality has been improved so that messages on the service bus are received even for failure notifications.	+	Power BI reports are faster, more scalable, richer in features, customization-friendly, sport a modern UI and overall a better experience. To leverage its advantages, the following SSRS reports are now made available in Power BI:
−	Users will now get a definite response, with required details of the error and cause, of the async APIs called. Based on the notifications, they can take necessary actions when successful, or corrective measures in the event of a failure.	+	*Clause Summary Report
		+	*Tagged Attribute Report
		+	*Agreement Clause Content Report – A widget that displays the clauses with the most deviations is also added in this release.&nbsp;
−	<br/>  <br/> <span style="color:#800080;">'''660859 – Supporting correlation Id in APIs'''</span>	+	Feature IDs: 1214787, 1214720, 1223598<br/> &nbsp;
−	To work with ICI entities, at times, multiple API calls are needed to complete an operation.&nbsp;	+	== Salesforce Integration&nbsp; ==
−	For example, to create an agreement, the following APIs are called in a sequence – “GetInstance”, “SaveExternalUser”, “GetTemplate”, “CreateandPublish”, “ResumeWorkFlow” (API 1.0), “Prepare”, “Create”, “Get”, “Send For Approval”, and “Send for Signature” (API 2.0).&nbsp;	+	=== &nbsp;Activity Object and Trigger Simplification in Salesforce Adapter ===
−	In such cases, due to heavy load, it becomes challenging for administrators to troubleshoot the operation that caused failure of the agreement creation. To resolve this issue, an identifier has been added which can be passed by subsequent APIs for correlating from logging perspective.&nbsp;	+	The following enhancements are made to the SFDC Manage package Adapter:
−	The following API changes have been made to ensure that the existing implementation and code do not break:	+	*Triggers for Accounts and Opportunity objects have been removed from the Managed package to avoid unnecessary update-related issues. Users can get more flexibility and control over them when they use the auto contract creation feature. Note: This is applicable to both fresh installs as well as updates on existing packages.
		+	*Previously, 6 custom fields were needed on the Salesforce activity object to sync ICI tasks with Salesforce, and now, the dependency on these fields have been reduced with only 2 custom fields required for the sync.
		+	*For customers who didn’t need the ICI task sync feature and were unable to remove the custom fields with the limit of 100 fields on the Activity object, now, these fields have been removed from our managed package to provide more flexibility.
−	*Provided support for a Tracking Id header in every request for logging.&nbsp;	+	'''Note:''' Guideline documentation and support by ICI implementation/upgrade team will be duly provided, for creation of desired fields during new installs as well as release upgrades, or deletion of fields during upgrade scenarios.
−	*User will receive the Tracking Id provided in the request header as part of response headers. (If the user does not send a value, then a new unique identifier will return).	+
−	*The called API path with query string will be logged in Kibana.&nbsp;	+
−	'''Note: '''The implementation of the Tracking Id is optional and the value must be GUID only.	+	Feature ID: 1066353
−	This can be used for:	+	=== User Experience for Salesforce Revamped ===
−	*Related API Calls	+	Using ICI within Salesforce is now a more seamless experience as we have made significant improvements to preserve the native Salesforce UI interactions, which users are familiar with, without compromising the ICI functionality.
−	*Async operations	+
−	*Bulk operations	+
−	*Status check operations &nbsp; &nbsp;	+
−	</div>	+
−	&nbsp;	+
−	== Enhancements to ICI Add-ins&nbsp; ==	+	These are the enhancements that have been introduced:
−	<span style="color:#800080;">'''745266 – Supporting online editing of agreements'''</span>	+	*&nbsp;Native Salesforce components are now used along with the ICI iframe.
		+	*Sub-tabs moved from ICI to Salesforce native tabs, for example: Agreements, Requests and Agreement Reports.
		+	*Agreement and Request Details pages are now displayed in native Salesforce UI.
		+	*On the Details page certain actions (example - Reset Expiry) and sub-tabs (example – Associations) are now native Salesforce components.
−	As part of contract management, agreement and amendment documents regularly go through reviews, where multiple stakeholders and teams have to review and/or edit a contract before it is sent out to external parties for their reviews and signature.&nbsp;	+	'''Note:''' The implementation team will provide a list of native and i-frame components.
−	To make changes or modifications to an agreement, ICI users previously had to download a copy, perform edits and upload it back to ICI. This created a version of the document in ICI. Primary owners had to send the documents over emails to get inputs from multiple departments such as delivery and legal, which they would later have to consolidate to create the contract document. This approach not only led to aggregation overheads, but audit information was often lost too, and it was not possible to trace what was approved and by whom.	+	Feature ID: 1186642
−	With this release, ICI offers online editing support for agreement documents creating radical operational efficiency for contract owners.	+	== eSign Integration&nbsp; ==
−	It is now possible for:	+	=== Integration Support for DocuSign using JWT authentication ===
−	*Primary owners, secondary owners and reviewers with edit privileges to initiate an online editing session, where more than one party can edit parallelly using existing MS Word capabilities.&nbsp;	+	The ICI and DocuSign integration was previously based on authenticating the APIs with “IntegratorKey” and “API Password”.
−	*An agreement document, which has been edited using online editing, to be published to ICI, without any loss of information.	+
−	'''Note:&nbsp;'''	+	The product has now been upgraded to support an enhanced authentication using JSON Web Token (JWT), along with the existing basic authentication support. This enhancement has also enabled JWT support for “Multisign” as well as “Single Esign” configurations.
−	*The online Word editor is available only for users with valid Office 365 subscription.	+	Feature ID: 1000798
−	*Only users with edit privileges on a document can make changes to the document online.	+
−	*Users must either allow third-party cookies or add “*.officeapps.live.com” to their browser's cookie “Allow” list, in order to use Office Online smoothly.	+
−	<br/> <span style="color:#800080;">'''588686 – Tagging clause extended attributes in clause text'''</span>	+	=== DocuSign API upgraded from 2.0 to 2.1 ===
−	ICI allows users to capture additional details for clauses in the extended attributes.&nbsp;	+	DocuSign released an update announcement that OAuth 2.0 would be required to support DocuSign API applications. In keeping with this announcement we have upgraded DocuSign REST APIs from 2.0 to 2.1. With this upgrade, a new JSON parser has been introduced to support DocuSign Connect, a notification mechanism to receive updates when any event is triggered in the eSignature workflow.
−	Now, users have the capability to tag clause extended attributes, if configured, inside the clause along with clause metadata, while creating or modifying the clause from within the Icertis Experience for Word.	+	Feature ID: 1060689
−	The value of tagged clause extended attributes will be resolved and displayed in the clause text upon tagging of the attribute or saving the clause.	+	=== Adapting webhook feature of Adobe Sign ===
−	&nbsp;	+	Adobe Sign adapter couldn’t communicate precise callback information to ICI Platform, thus causing intermittent errors in ICM workflow after the Agreements were electronically signed. Adobe Sign responded with the same information for every signature, hence it wasn’t possible to distinguish between callbacks from different signature. However, with the introduction of Adobe webhook, this problem can be resolved.
−	<span style="color:#800080;">'''668859 – Enhancing filtering and searching of clauses &nbsp;'''</span>	+	Adobe webhooks can be created on the workflow for each agreement, requesting the type of information in the callback, which further benefits as follows:
−	In ICI, clauses can be filtered on the basis of clause groups and searched on the basis of their clause name. This filtering and searching capabilities have been improved, so that users can easily retrieve the desired template and clause record, thus improving usability for customers having large number of clauses and templates in their clause and template library.	+	*Identifying the signatory requesting a callback
		+	*Identifying for which event or action the callback is requested
		+	*Concisely updating the status in ICM
−	Users can now:	+	'''Note:'''&nbsp; Upgrade Adobe Sign API from 5.0 to 6.0 to use the webhook feature.
−	*Search and filter clauses and templates based on the name or text inside the clause or template respectively.	+	Also, Adobe rebranded Echo sign to Adobe Sign, hence non overridden localization strings for validation messages have been modified accordingly.
−	*Perform free text search on clauses and templates.	+
−	&nbsp;	+	Feature ID: 1091947
−	<span style="color:#800080;">'''603690 – Updating templates automatically with latest clause version'''</span>	+	=== Electronic Signature support using ICI BioPharma setting for 21 CFR Part 11 & Annex 11 compliant groups ===
−	Legal teams may need to make changes to a clause available in the clause library for varied reasons. This clause may be used in multiple templates used for various transactions. It may also require template updation, so that the latest version of the clause can be used in all future transactions.	+	ICI Platform now supports the Life Science industry documents that need to comply with 21 CFR Part 11 (for US FDA) or Annex 11 (for EU) regulatory compliance.
−	To facilitate this, users can now update all or selected templates with the latest version of the clause whenever any clause is modified, thus eliminating the need for the legal team to manually do so.&nbsp;	+	This feature allows integration with DocuSign Part 11 module and Adobe Sign Bio-Pharma setting to get electronically signed approvals for such agreements.
−	Users can select templates to be updated when a clause is modified. The selected templates are automatically updated after the clause is approved and will move to the next logical state once modification is done.	+	Feature ID: 1220095
−	<br/>  <br/> <span style="color:#800080;">'''593421 – Labeling agreement document versions as per signature copy'''</span>	+	=== Changes in IP whitelisting process for eSign adapters ===
−	Previously in ICI, agreements signed only by external, internal or both signatories were termed as “Internal Signed Copy”, “External Signed Copy” and “Final Signed Copy” respectively, and were displayed on the “Version” tab.	+	ICI Platform supports integration with third party eSign adapters, which communicate using callback information. To receive the callback data from the eSign servers, certain IPs to intended methods are whitelisted. This action is done through the web.config file. However, any change in the IPs requires modifying the web.config file, which resets the IIS, resulting in performance issues.
−	This capability has been further enhanced so that the signature versions are clearly labeled as “Internal”, “External” or “Fully Signed Copy”, as applicable, so that the user can easily identify the agreement version.	+	To address this issue, “Core.IPSecurity” key has been introduced, which stores information related to the IPs as a JSON, and thus eliminates the need to modify the web.config file.
−	&nbsp;	+	'''Note''': Blocking or allowing IP addresses based on DNS is not supported as a part of this feature.
−	== Enhancements to Artificial Intelligence Applications in ICI ==	+	Feature ID: 1193062
−	<span style="color:#800080;">'''727318 – Enhancing AI powered playbook in Icertis Experience for Word'''</span>	+	=== Update eSign document with correct status ===
−	ICI provides the legal playbook in Icertis Experience for Word that uses artificial intelligence to identify exceptions in the contract document, allowing users to review and take corrective actions on them, and assess the risk when these exceptions are accepted by negotiators. &nbsp;	+	In certain scenarios, the electronic signature status in ICI and eSign provider are inconsistent. An enhancement has been added wherein the respective statuses are verified and the agreement status is updated or corrected accordingly.
−	With this release, the legal playbook is enhanced and provides more options to work with playbook from Icertis Experience for Word.&nbsp;	+	Feature ID: 1193061
−	Users can now:&nbsp;	+	== Sourcing&nbsp; ==
−	*View the visual indication for clauses with playbook exceptions on “Agreement Clause” page. &nbsp;	+	The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (SRC8.1.0.404).
−	*View playbook details in a separate resizable window.&nbsp;	+
−	*View all playbook positions for a selected contract type with options to search and filter within.&nbsp;	+
−	*View all playbook positions for a selected agreement clause.&nbsp;	+
−	*Add deviation to the clause from playbook “Details” page.&nbsp;	+
−	*Add a new playbook record and edit the existing playbook record from within the Icertis Experience for Word.	+
−	&nbsp;	+	=== Support for new RFx type-RFP ===
−	<span style="color:#800080;">'''575475 – Automating user feedback for clauses, obligations and attributes'''</span>	+	Icertis Sourcing application now supports Requests for Proposals (RFPs). Organizations can leverage the advantages of a secure and seamless application to organize and maintain their procurement processes digitally using the RFP feature.
−	ICI AI apps have been positioned to be intelligent assistants to help users in taking decisions when populating details for agreements. While AI discovery suggests values to users, it is expected that users correct them at the time of review. &nbsp;	+	RfPs are integrated requests containing information on both questions and bids. Buyers can now design, create, and publish RFPs in the Sourcing application and invite suppliers to respond to them. Once Buyers receive the responses, they can evaluate them and make their procurement decisions.
−	With this release, the AI algorithm continues to learn from user actions in attribute and clause discovery and incorporates those in the next discovery. So, when a contract owner selects values for attributes on the Attribute and Clause Discovery pages, the system learns the actions and provides same or similar values at subsequent discoveries.	+	Key RFP features:
−	<br/> <span style="color:#800080;">'''539492 – Improving clause delineation in DiscoverAI'''</span>	+	*Integrated mechanism to get responses to questions and bids from suppliers.
		+	*Reusable templates for Questions, Questionnaires, and Bidding templates.
		+	*Questionnaires and questions can be arranged and reordered as required.&nbsp;
		+	*Attachments, and responses to questions can be downloaded in a package.
		+	*A consolidated excel spreadsheet is available to analyse bids and responses.
		+	*Suppliers can provide responses to questions using Excel as well as Sourcing UI.
−	Clauses in an agreement document that are found using DiscoverAI are displayed along with clause categories in the “Clause Discovery” section on the Web UI.&nbsp;	+	Feature ID: 404602
−	ICI has now improved its logic for clause delineation to determine the start and end of the clause text.&nbsp;	+	=== Improved Sourcing workflow with Sourcing Request ===
−	Users can now:&nbsp;	+	Users within an organization can now create Sourcing Requests for procuring items or services. These requests can be designed to go through an approval flow before they are turned over to procurement teams. The approval cycle can be easily tracked and audited for compliance.
−	*Edit the discovered clauses list or manually selected clause text to merge or split into multiple clauses.&nbsp;	+	Sourcing Request features:
−	*Create a sub-clause within a discovered clause.&nbsp;	+
−	*Change the clause category and the level (parent or child) of the discovered clause. &nbsp;	+
−	*Choose to view only the level 0 clauses.	+
−	&nbsp;	+	*Configure a Sourcing Request based on the necessary privileges.
		+	*Request forms can be designed to capture necessary details and attachments.
		+	*Requests can be sent to designated approvers for approval.
		+	*An RFx can be created after the request is approved.
		+	*Requests can be modified until they are approved or a RFX is created based on it.
		+	*Cancel or recall the Sourcing Request.
		+	*Put the Sourcing Request on Hold till approved state provided RFx is not created using this Sourcing Request.
−	<span style="color:#800080;">'''770375 – Merging metadata discovery page with attribute page'''</span>	+	Feature ID: 611297
−	Previously in ICI, the AI attribute discovery process on agreements with third party paper was triggered on create and post-create events such as publish. Users might have already entered the attribute values before initiating the create/publish action, thereby making attributes discovery process redundant. Also, the process needed to maintain two different attribute pages, with customizations and validations not being available on the attribute discovery page.&nbsp;	+	=== Ordering and additional data types for Questions in Questionnaire ===
−	With this release, users can manually trigger the attribute discovery on the “Attributes” page itself, while uploading a third-party document, during create and edit agreement process. Discovered values will then be auto-filled in empty attributes and users can view additional recommended values for the discovered attributes.&nbsp;	+	We have made the following enhancements to Icertis Sourcing to improve the user experience when working with Questions and Questionnaires:
−	Users can:&nbsp;	+	The order of Questions and questionnaires in RFx can be set and modified as per the preference of users.
−	*View the discovery completion progress.&nbsp;	+	The following data types are now supported for questions in RFx:
−	*Identify discoverable attributes marked with the spinner icon.	+
−	*Get side-by-side document view for discoverable attributes.	+
−	*Get side-by-side document view for tagged attributes upon completion of discovery.	+
−	The merging of “Metadata Discovery” page with “Attributes” page will only work for agreements with third party papers.	+	*Boolean
		+	*String
		+	*Choice
		+	*Multi Choice
		+	*Currency
		+	*DateTime
		+	*Number
		+	*Percentage
		+	*Text Area
		+	*Rich Text Area&nbsp;&nbsp;
		+	*Email
		+	*File Selection
−	&nbsp;	+	'''Note''':
−	<span style="color:#800080;">'''727312 – Formatting based clause delineation for additional document types'''</span>	+	*On exporting rich text data type information to Excel or HTML, some formatting features may be lost.
		+	*Uploading a file attachment as response for file type question response using Excel is not supported. Supplier must log on to ICI to upload files.
−	In the previous release, support was introduced to display clause hierarchy in well-formatted .docx agreements.	+	Feature ID: 896873
−	With this release, the clause delineation functionality has been enhanced to support PDF documents, as well as for Word documents which do not use any styles. This enhancement helps to get better clause delineation while migrating legacy contracts, as AI assisted configuration is largely dependent on accuracy of formatting-based clause delineation for PDF documents.	+	== Obligation Management&nbsp; ==
−	Clause discovery processor is now trained to identify sections, and sub-sections in Word and PDF documents, up to 3 levels. Support for formatting-based clause delineation has now also been extended to the Icertis Experience for Word, wherein the discovered clauses are displayed to the user in hierarchical format.	+	The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application (OM8.1.0.404).
−	&nbsp;	+	=== An interface to quickly add obligations discovered by AI ===
−	<span style="color:#800080;">'''727314 – Supporting additional languages in AI apps'''</span>	+	Obligations that are identified in contracts using the Discover AI feature can now be easily reviewed on the user interface. User can review the obligations and decide to add one or more to the Obligation Management application for tracking approvals and fulfillment.
−	In the previous release, support was provided for clause and obligation discovery for agreements in German, Spanish and Portuguese languages.	+	The interface to review and create obligations in bulk saves users much time and manual effort.
−	With this release, the discovery models will be enhanced to support the following additional languages – French, Dutch and Swedish. Support will be provided for DiscoverAI, NegotiateAI and DiscoverAI for legacy, for auto-detection of language, as well as for bilingual contracts.	+	The following image shows an example of creating Obligations in bulk:
		+	<div class="image-green-border">[[File:RN 8.1 30.png|720px|RN 8.1 30.png]]</div>
		+	Notifications for successfully processed or failed obligations can also be configured.
−	'''Note: '''Scanned PDF documents are currently not supported for automatically detecting the language.	+	Feature ID: 1090383
−	&nbsp;	+	=== Auto-approval of Obligations to improve efficiency ===
−	<span style="color:#800080;">'''710739 – Configuring custom rules in DiscoverAI'''</span>	+	Many obligations are extracted from executed contracts and they don’t usually need to go through an approval process in the Obligation Management application. To reduce time and effort spent approving a large number of obligations and not block the obligation fulfillment lifecycle on account of pending approvals, an automatic approval process for obligations can now be configured.
−	Previously, attribute discovery and obligation discovery were dependent on inbuilt schema Excel files. Adding and updating the schema rules for any attribute or obligation required technical details of the code.&nbsp;	+	Once the auto-approval process is defined based on obligation taxonomy, this is how the feature works:
−	With this release, the Excel schema has been deprecated and has been replaced with a rule engine, which can be used to easily write a rule in simple language, and the schema will be generated dynamically, thereby making it more user friendly.&nbsp;	+	*If approval is turned off, and no approvers are added to obligations, the obligations are automatically approved.
		+	*If approvers are added to obligations, manually or automatically through a rule, then even if approvals are turned off, the obligations will need to be approved.
−	The rules engine will help configure custom rules for Obligation Discovery, Attributes Discovery and Playbook Discovery, using an inbuilt .NET based rule editor and the ICI master data entity.<br/> &nbsp;	+	Feature ID: 519344
−	== Enhancements to Reports ==	+	=== Organize and manage obligations by creating groups&nbsp; ===
−	<span style="color:#800080;">'''514593 – Introducing Tagged Attributes Report for attributes tagged in clauses and templates'''</span>	+	An obligations could have one or more sub obligations or tasks, which would need to be completed by different individuals in an organization. Also, some obligations may be related to each other and grouping them could help organize and track the fulfillment. To facilitate such scenarios, obligation groups can now be created in the Obligation Management application.
−	ICI provides default reports such as “Attributes Value Report” which captures the attribute values and edits made over time, and the “Attribute Information Report” which provides details of the attribute properties and its incorporation in different contract types. Previously, attributes tagged in clauses and templates could also be checked by using the Preview mode or using Icertis Experience for Word. However, administrators often need to understand how an attribute has been used in these entities; for example, to carry out an impact analysis before removing an obsolete attribute.	+	Users can now categorize different obligations under logical groups and create parent-child relationships between obligations.
−	With this release, a new “Tagged Attributes Report” has been introduced as part of Admin Reports, which helps administrators understand the complete profile of an attribute, and how it has been tagged across different clauses and templates. This saves them considerable time as they no longer need to manually examine each clause and template, in addition to reducing manual errors.	+	Child obligations automatically inherit any changes made to the parent Obligation. For example, if the status of parent Obligation is changed to Approved, all the related child Obligations also get approved.
−	This report available on the “Reports” tile can be accessed based on the security groups configuration. The report can be filtered using the “Select Attribute” and “Select Entity” parameters. Based on the selected entity, the following columns are displayed – Clause/Template Code, Clause/Template Name, Contract Type, Clause/Template Version, Clause/Template Created By, Clause/Template Created On, Version Updated On, Attribute tagged as Template Variable and Attribute Display Name.&nbsp;	+	Feature ID: 649768
−	'''Note: '''Historical data for clauses and templates, added prior to Release 7.15, will not be considered by default for this report. In such cases, a utility needs to be run which generates report data for historical clauses and templates.	+	=== Duplicate obligations no longer inherited&nbsp; ===
−	&nbsp;	+	When an Agreement (parent), with an associated Obligation, is inherited by another Agreement (peer), a duplicate Obligation is created. An enhancement in this release eliminates this limitation.
−	<span style="color:#800080;">'''769602 – Enhancing Clause Summary Report for extended clause attribute version'''</span>	+	Feature ID: 1040723
−	Previously, the “Clause Summary Report” displayed the “Clause Summary” and “Clause Version” sections on the report index page.&nbsp;	+	=== UI Improvements for Obligation Management ===
−	In this release, the report is enhanced to display a “Clause Extension Summary”, which displays details on extended clause attributes. If the clause extended entity is defined for an ICI instance, then this report will display the information for each clause. It also displays a column for each version number, similar to the “Clause Version” summary section.	+	The following improvements are made in the product to improve the search and usability experience when using Obligation Management:
−	<br/>  <br/> <span style="color:#800080;">'''514611 – Enhancing Notifications History Report for an entity'''</span>	+	*Dedicated index pages for Obligations and Fulfillments,
		+	*Relevant page titles, breadcrumbs and history page information.
−	ICI administrators can set up notification subscriptions for different entities to be sent to subscribed users at the occurrence of certain events. The “Notifications History Report” provides visibility into which notifications were sent, when, and to whom, by displaying an audit history of notifications for the particular entity. This provides better visibility to backtrack whether a user received a certain notification (or not).&nbsp;	+	Feature ID: 1236413
−	The default SSRS report is available for contract requests, agreements and associated documents, and is accessible through the left navigation pane of the details page, for an instance of the aforementioned entities.&nbsp;	+	== Risk Management ==
−	The report can be filtered by “Notification Type” – “Broadcast” or “Subscription”.&nbsp;	+	The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (RM8.1.0.404).
−	*When filtered by “Broadcast”, the report displays the following columns - Contract Type Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.&nbsp;	+	=== UI Improvements for Risk Management&nbsp; ===
−	*When filtered by “Subscription”, the report displays the following columns - Notification Template Name, Entity Name, Event Name, Category Name, Subject, Body, To Recipient, Cc Recipient, Bcc Recipient, Sent Date and Time and Attachment File Names.	+
−	&nbsp;	+	The following Improvements are made in the product to improve the search and usability experience when using Risk Management:&nbsp;
−	<span style="color:#800080;">'''742607 – Supporting localization for status and business status'''</span>	+	*Dedicated index pages for Risk Management and Risk Assessment.&nbsp;
		+	*Relevant page titles, breadcrumbs and history page information.&nbsp;
		+	*Saved searches display Risk Assessment as category. &nbsp;
		+	*The “Create” action button has now been added on the “Risk Assessment” index page.&nbsp; &nbsp;
		+	<div class="image-green-border">[[File:RN 8.1 31.png|720px|RN 8.1 31.png]]</div>
		+	Other enhancements include:
−	With this release, localization support will be provided in core, Sourcing, Obligation Management and Insights SSRS reports, in the following areas:&nbsp;	+	*The “Delete” action has now been moved under the three dots icon on the Risk Assessment “Details” page. On deleting the risk assessment, users will be redirected to the Risk Assessment “Index” page.
−	*Obligation Management Health Report, Obligation Management Dashboard Report.&nbsp;	+	Feature ID: 1067718
−	*Contract type names, if the respective entity has locale resource key values in database.&nbsp;	+
−	*Status filter on all reports, drop-down with Yes/No values.&nbsp;	+
−	*Graphs and graph tool tips, page numbers, text written in RDL, hidden textboxes.&nbsp;	+
−	*Dynamic column headers (for example, RFx Details Report in Sourcing).&nbsp;	+
−	*Any error or validation messages, informative messages such as “No data available”. &nbsp;	+
−	<br/> <span style="color:#800080;">'''583297 – Filtering additional reports by agreement status'''</span><br/> Previously the "Agreement Status" filter was available for the “Agreements Pending Approval Report”, “Expiring Agreements Report”, “Average Agreement TurnAroundTime Report” and “Expired Agreements Report”.&nbsp;	+	== Proposal Management&nbsp; ==
−	Now, this filter is also available for the "Agreement Deviation Report" and "Agreements Pending Execution Report". Users have the option to exclude terminated or archived agreements from this report, thus allowing them to derive the exact number and information as required.	+	ICI Proposal Management application is certified to work with the 8.1 release (PM8.1.0.404).&nbsp;
−	&nbsp;	+	=== Track and analyse performance with a Power BI Dashboard ===
−	<span style="color:#800080;">'''746607 – Enhancing the Cycle Time Report'''</span>	+	A seeded dashboard that helps supplier organizations track their proposals by status, time, and outcome is now available within the Proposal Management application.The following features and reports are now available with the Proposal Management application:
−	The “Cycle Time Report” displays the cycles for contracts requests, agreements, agreements with contract requests, and the change of status for each entity from the date of creation to the date of execution, as well as the elapsed time. This enables users to get the turnaround time for tasks and take corrective actions wherever necessary.&nbsp;	+	*A new Power BI data model with Power BI dataset specific to Proposal Management.
−		+	*Proposal Management KPIs report
−	With this release, an “Organization Unit” filter is being introduced in this report for users to be able to derive the desired information.	+	*Capture Management report
		+	'''Note''': Users with access to Sell Side RFx or Bid Proposal can view the Dashboard.
		+	<div class="image-green-border">[[File:RN 8.1 31.png|720px|RN 8.1 31.png]]</div>
	&nbsp;		&nbsp;
−	<span style="color:#800080;">'''737196 – Adding hyperlink in PowerBI for agreement code'''</span>	+	=== Enhancements to Seeded Contract Types ===
−	A new column has been added in PowerBI for “Agreement Code”, which has a hyperlink, that navigates the user to the agreement in ICI.<br/> &nbsp;	+	With this release, the PM App is being enhanced with newly seeded attributes to its seeded contract types.
−	== Integrations ==	+	In this enhancement:
−	<span style="color:#800080;">'''605434 – Providing a unified flexible signature process'''</span>	+	*New attributes have been seeded with the Bid Proposal entity:
		+	*Total Bid Value For Proposal
		+	*Total Value Won Or Lost
		+	*Customer Address
		+	*Customer Geography
−	ICI has now improved the electronic signature process to provide a unified flexible signature workflow.	+	These new attributes contribute in the essential computations of the Win Ratio and the Value Capture Ratio.
−	With this release, the following capabilities have been added to the ICI signature process:	+	Feature ID: 1186830
−	*Introducing the hybrid signature process.	+	=== Revamped User Experience across the PM App ===
−	*Enabling DocuSign console for users to add and modify the signatories.	+
−	*Support for preview in DocuSign console.	+
−	*Support for tagging signatories in DocuSign console.	+
−	*Support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES) in DocuSign.	+
−	&nbsp;	+	The visual look and feel of the Proposal Management App has been considerably enhanced with the ICI-wide implementation of the new UI (User Interface) and UX (User Experience).
−	<span style="color:#800080;">'''641289 – Allowing parallel signatures using DocuSign'''</span>	+	The following summarizes the revamped user experience across the App:
−	Previously, DocuSign integration provided support for sequential signatures. This capability has been improved to allow parallel signatures, so that multiple signatories can sign the agreement simultaneously, thus reducing the overall turnaround time for the complete signature process.	+	*The new “Proposals” tile menu now features only the viewing tile options for the seeded PM App entities, in addition to a new “Dashboard” tile menu option.
		+	*The create navigation flow has been moved from the “Proposals” tile and a dedicated “Create” button has now been added to each seeded entity index page.
		+	*The seeded entities now have their dedicated index pages, as opposed to the saved search driven listing in previous releases.
		+	*The Details pages of all the seeded entities (Sell Side RFx, Bid Proposal etc.) now have dedicated page titles starting with the entity name, instead of the contract type category. For example, the previous “Agreement / Sell Side RFx 123” has been replaced by “Sell Side RFx / Sell Side RFx 123”.
		+	*The newly added entity name (such as “Sell Side RFx”) on the Details page header is now a clickable link, clicking which opens the entity index page.
		+	*In the audit history of any entity, both Grid View and List View, the header now features the entity category name instead of the contract type, just like the change in entity Details page.
		+	*The display of action buttons on entity Details pages can now be configured to customize their sequence of display, and based on the available window space the remaining action buttons will be available under the three dots icon on the entity “Details” page.
−	With this release:	+	Feature ID: 1235186
−	*Users can define the parallel signatories using rules.	+	== Supplier Relationship Management Application&nbsp; ==
−	*Users can configure parallel signatories via the DocuSign console.	+
−	*DocuSign process can be triggered in parallel for the configured signatories.	+
−	*Sync back, audit and history can be captured in the ICI agreement.	+
−	<br/> <span style="color:#800080;">'''701825– Supporting multiple vendors for electronic signature'''</span>	+	ICI Proposal Management application is certified to work with the 8.1 release (SRM8.1.0.404).
−	Previously, ICI supported one signature vendor within one instance of ICI. Now, multiple electronic signature vendors are supported in the same instance.&nbsp;	+	=== Supplier Evaluation ===
−	With this release, users can:	+	The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.
−	*Select the provider at the agreement or amendment level, for electronic signature and execution. This is achieved by using the choice attribute “Esignature Provider” with “DocuSign” and “Adobe Sign” as options.	+	'''How Supplier Evaluation fits within Supplier Relationship Management'''
−	*Define standard rules and conditions to automatically select the provider for agreements and amendments.	+	<div class="image-green-border">[[File:RN 8.1 33.png|520px|RN 8.1 33.png]]</div>
		+	The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.
−	'''Note: '''This is applicable to DocuSign and Adobe Sign.	+	'''How Supplier Evaluation fits within Supplier Relationship Management'''
	&nbsp;		&nbsp;
−	<span style="color:#800080;">'''751651 – Syncing data task in Salesforce to publish completion notification on ASB'''</span>	+	Supplier Evaluation module is part of the Supplier Relationship Management application, which is built on Icertis Contract Intelligence.
−	Sales agreements with customers are created in Salesforce using the ICI adapter for integration. Previously, users had to click “Assemble Contract” to sync data and reflect any changes on the agreement document.	+	Once suppliers are onboarded, users can evaluate suppliers on the products or services they offer. The KPI criteria, schedule, and the evaluators can be set up within the module and on completing the assessment the supplier can be classified as high performing, low performing or standard supplier.
−	With this release:	+	A routine supplier evaluation can help organizations set expectations from their preferred suppliers and manage low performing suppliers.&nbsp;&nbsp;
−	*Document assembly is triggered automatically after every update from Salesforce. The changes will reflect in the generated agreement document once the instance and associations are synced, without clicking “Assemble Contract”.	+	'''Supplier Evaluation Features'''
−	*Upon completion of data sync task for an opportunity, the Salesforce data sync task raises a “Data Sync Complete/Failed” event on the Azure Service Bus (ASB) upon completion of data sync for the given opportunity.	+
−	*A message containing the opportunity Id and agreement SysId is updated, and the time stamp is also displayed.	+
−	<br/> <span style="color:#800080;">'''796155 – Improving data flow between Salesforce and ICI'''</span>	+	Setting up Supplier Evaluation
−	Previously, when changes were made to an agreement in the "Sent for External Signature" status, the data was synced from Salesforce to the ICI UI, but not in the template document.&nbsp;	+	*'''KPIs''' – Users can create one or more KPIs (evaluation criteria) and evaluate suppliers based on the set parameters. For example, you can create KPIs for auditing, performance reviews, training requirements, and more.
		+	*'''Supplier Data''' – The supplier evaluation creation process is simplified as much of the supplier information is auto-populated based on the supplier’s record.
		+	*'''Evaluation Schedule''' – Users can set up a period for which the supplier will be evaluated.
		+	*'''Product/Service for Evaluation''' – The evaluation can be performed in context of the product or service provided or the agreements.
		+	*'''Reviewing suppliers based on the Criteria''' – The evaluation criteria can be put through an internal review process, and inputs can be sought to finalize the evaluation criteria.
		+	*'''Supplier Outreach''' – Suppliers can provide information and supporting documents needed to perform the evaluation by responding to review requests by buyers.
		+	*'''Responses & Scoring''' – Based on the responses provided by business team or evaluators on the supplier evaluation, scores are automatically computed.
		+	*'''Evaluation Approvals & Control''' – Once the evaluation process is over, then buyer team defines supplier performance classification and suggests the next course of action (in case of low performing supplier). This can also be sent for management approval. The approver team can either approve or reject and send it for rework..
		+	*'''Notifications''' – Notifications can also be configured for periodic evaluation. System notifications are sent to buyers when they are requested to evaluate a supplier.
−	Additionally, the agreement status changed only when an attribute which is tagged in the template was changed. However, if an attribute which was not tagged in the template changed, it was updated in the ICI UI and the status of agreement also remained the same.	+	Feature ID: 463049
−	With this release:	+	=== Managing Supplier Hierarchy ===
−	*Changes made to agreements in Salesforce while they are in Send for External Signature, Send for Internal Signature, Executed or Expired statuses will not be updated to the ICI UI.&nbsp;	+	'''Manage Related Supplier Organizations'''
−	*When attributes are not tagged in the template document and the same attribute is mapped with Salesforce, updating the value of that field in Salesforce will change the status of the agreement from "Waiting for Approval" or "Approved" to "Draft"; unless it is a tracking attribute.&nbsp;	+
−	This will ensure that the ICI UI and the template document will always be in sync and there are no compliance issues.	+	The Supplier Relationship Management application now provides a mechanism to connect supplier organizations with their Parent, Holding or Subsidiary organizations. This is to ensure that you have a complete overview of the business you do with one supplier and its related entities. According to business needs, you may want to work with a local supplier or the parent global organization.
−	&nbsp;	+	You can designate a supplier organization as one of the following types:
−	<span style="color:#800080;">'''674469 – Sending success or failures alerts for monitoring in Salesforce'''</span>	+	*'''Supplier''': Supplier organizations that may or may not have related Parent or Holding companies.
		+	*'''Parent company''': Parent company of one or more Supplier organizations, controls operations of the Supplier Organization
		+	*'''Holding company''': Holding company of one or more subsidiary Supplier organizations, does not have a direct say over the operations of subsidiaries.
−	An alert mechanism is introduced for successes and failures in Icertis Experience for Salesforce integrations.&nbsp;	+	Changes made to the supplier hierarchy for supplier registration, qualification or profile are synchronized with the vendor database and supplier master.
−	With this release:	+	'''Unique Supplier Record Management'''
−	*All messages at ICI end can now be monitored by customers, and they will be able to retry transactions, if needed.&nbsp;	+	In Icertis Supplier Relationship management, the uniqueness of a supplier record is validated based on a combination of attributes . In this release, one or more of the unique identifiers attributes can be made editable. This is to account for entities that may change the Legal Entity Name in the course of doing business, considering legal entity name is one of the unique identifier attributes.
−	*Additional logging has been introduced for ICI-Salesforce integration messages. Every message log will include the status, message Id and the incoming JSON details.&nbsp;	+
−	*Configurators also send email notifications to ICI users on forward/reverse data sync so that the recipients can take appropriate actions.	+
−	<br/> <span style="color:#800080;">'''679797 – Supporting OAuth in Salesforce adapter'''</span>	+	If the attributes are changed for an organization, the system validates and checks for duplicate records before allowing users to make the change.
−	Effective password management is an integral part of any corporate security policy. However, there are some risks involved in using user Id and password for authentication and authorization of production systems in an enterprise. Security organizations also had stringent security policies which do not approve user id or password authentication process.&nbsp;	+	'''Validating the Duplicate Registrations'''
−	With this release, support is provided for OAuth, a more secured authentication and authorization process. This makes the ICI application more secured and is easy for customers to manage using an actual business user Id, instead of a service user to update the records in ICI. It also removes any access issues involved in the business process. Customers do not have to add owners of the record to contracts team to obtain access.	+	Buyers may receive more than one registration from the same supplier submitted through the web page.
−	When entities in Salesforce are updated by a user, the process builder sends a message to ASB queue with minimal data such as entity Id. ICI task service picks the message, obtains integration user credentials from JSON or AKV, and makes an API call to Salesforce to fetch the changes. There are no user interactions involved in this asynchronous process, the task service uses the service user login to update the ICI records.&nbsp;	+	This release introduces the capability to match the supplier registration records based on the unique identifier attributes. This helps identifying the duplicate registrations. Buyers can perform limited actions on the duplicate registrations and the supplier qualification is not generated.
−	When data in Salesforce is updated and data sync job is triggered, the Salesforce adapter will use client Id and secret key from AKV to fetch a user token, for invoking Salesforce APIs, using OAuth protocol.	+	'''Note''': Customers upgrading to 8.1 from previous versions of ICI Supplier Relationship Management is supported.
−	&nbsp;	+	Feature ID: 1271423
−	<span style="color:#800080;">'''749083 – Supporting OAuth in the MS CRM adapter'''</span>	+	== Technical Requirements&nbsp; ==
−	Previously, MS CRM plugin used logged in user credentials to invoke ICI APIs when sales users updated any entity in MS CRM. Also, reverse data sync flow used service user login credentials to invoke MS CRM APIs when data was updated in ICI.&nbsp;	+	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.
−	ICI now uses the client id and secret key instead of user id and password for authentication/authorization process between Salesforce and ICI. The server-to-server OAuth support is provided, so that the adapter and task service will use client Id and secret key from AKV, invoking MS CRM APIs.&nbsp;	+	The software and hardware requirements for the client system as well as the mobile application are listed in the table below:
−	Users will have the option to choose the authentication mechanism to be used. The system will provide the support for backward compatibility of old username and password flow.	+	[[File:RN 8.1 43.PNG|720px|RN 8.1 43.PNG]]
−	&nbsp;	+	[[File:RN 8.1 44.PNG|720px|RN 8.1 44.PNG]]
−	== ICI Platform Tools ==	+	[[File:RN 8.1 45.PNG|720px|RN 8.1 45.PNG]]
−	'''<span style="color:#800080;">514636 – Enhancing P2P Tool in ICI Admin user interface</span>'''	+	'''Important Changes in IE11 Support:'''
−	With this release, enhancements have been made in ICI to support additional entities for a seamless P2P experience. This functionality, provided to administrators, can promote configurable entities in pre-production environments to production environments, thus reducing the manual efforts to do so.<br/> The following entities are now supported:	+	From March 2021, Microsoft has stopped its technical support to Internet Explorer (IE) and has advised its customers to move to Microsoft Edge.
−	*Organizations (Orgs), Organization Groups (Org Groups)	+	ICI will no longer support IE11. ICI will not be certified over IE11.
−	*Users, User Groups, Security Groups	+
−	*Role Action Mapping	+
−	*Currencies	+
−	*Reasons	+
−	*Attribute Group	+
−	*SLA Matrix	+
−	*Notification Category	+
−	*Default Search Columns	+
−	*Cascade Team	+
−	*Application Settings	+
−	*Global/Admin Saved Searches	+
−	'''Note:''' Customers using ICI versions before 7.15 will need to upgrade to use this feature.	+	If customers use IE 11 then the below message will be displayed:
−	&nbsp;	+	“You are using a browser that is not recommended to be used since it no longer supported by its OEM. The ICI support for this browser is limited for 7.16 version and will be discontinued from version 7.17 onwards. You should switch to Microsoft Edge as recommended by the OEM or any other supported browser prescribed by your organizational policy. You may contact your administrator for further information.”
−	== Partner Enablement ==	+	[[File:RN 8.1 46.PNG|720px|RN 8.1 46.PNG]]&nbsp;
−	<span style="color:#800080;">'''703386 – Icertis Software Development Kit for Partner Enablemen'''</span><span style="color:#008000;">'''t'''</span>	+	[[File:RN 8.1 47.PNG|720px|RN 8.1 47.PNG]]
−	Icertis develops strategic partnerships to drive shared business growth, deliver quality implementations and maximize customer satisfaction. In release 7.12, we introduced the Software Development Kit (SDK) to provide the resources and tools needed while implementing ICI.&nbsp;	+	[[File:RN 8.1 48.PNG|720px|RN 8.1 48.PNG]]<br/> [[File:RN 8.1 49.PNG|720px|RN 8.1 49.PNG]]<br/> [[File:RN 8.1 50.PNG|720px|RN 8.1 50.PNG]]
−	As part of our continuous efforts to support our partners, we have upgraded the following documents for this release:	+	[[File:RN 8.1 51.PNG|720px|RN 8.1 51.PNG]]
−	*ICI Coding Guidelines (version 2):&nbsp;This document helps developers to follow specific guidelines and best practices while coding. The database coding guidelines have now been added.	+	== Accessibility Conformance&nbsp; ==
−	*ICI Customization and Use Cases (version 2): This document explains how to perform customizations and provides some sample use cases that will help understand how to implement and execute ICI customizations. The document has been updated to support typescript.	+	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.
−	*Working with ICI Tasks: Updated for the 7.15 release.	+	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:
−	*Working with ICI Hooks:'''&nbsp;'''Updated for the 7.15 release.	+	*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
−	*ICI Developer Library: Updated for the 7.15 release.	+	== Known Issues ==
−	*Local Environment Setup using ICI Binaries: Updated for the 7.15 release.	+	This section includes some issues that we are aware of and plan to resolve at the earliest:
−	*Self-Serve Tools:'''&nbsp;'''Updated for the 7.15 release.	+	[[File:RN 8.1 52.PNG|720px|RN 8.1 52.PNG]]
−		+
−	&nbsp;	+
−		+
−		+
−	== Technical Requirements for Release 7.15 ==	+
−		+
−	The Icertis Contract Intelligence base system can be accessed from any device with an Internet connection and a supported Internet browser. Not all features may be available on all environments. Specific customer environments may have other requirements. The software and hardware requirements for client system as well as mobile application are listed in the table below.	+
−		+
−	[[File:7.15 Technical Requirements - Operating Systems.PNG|720px|7.15 Technical Requirements - Operating Systems]]	+
−		+
−	[[File:7.15 Technical Requirements - Browser Compatability Matrix.PNG|720px|7.15 Technical Requirements - Browser Compatibility Matrix]]	+
−		+
−	[[File:7.15 Technical Requirements - Other Requirements.PNG|720px|7.15 Technical Requirements - Other Requirements]]	+
−		+
−	[[File:7.15 Technical Requirements - Smartphone Mobile App.PNG|720px|7.15 Technical Requirements - Smartphone Mobile App]]	+
−		+
−	[[File:7.15 Technical Requirements - Special Requirements 1.PNG|720px|7.15 Technical Requirements - Special Requirements 1]]	+
−		+
−	[[File:7.15 Technical Requirements - Special Requirements 2.PNG|720px|7.15 Technical Requirements - Special Requirements 2]]	+
−		+
−	[[File:7.15 Technical Requirements - Special Requirements 3.PNG|720px|7.15 Technical Requirements - Special Requirements 3]]	+
−		+
−	[[File:7.15 Technical Requirements - MS Office Plugins 1.PNG|720px|7.15 Technical Requirements - MS Office Plugins 1]]	+
−		+
−	[[File:7.15 Technical Requirements - MS Office Plugins 2.PNG|720px|7.15 Technical Requirements - MS Office Plugins 2]]	+
−		+
−	[[File:7.15 Technical Requirements - Security.PNG|720px|7.15 Technical Requirements - Security]]	+
−		+
−	&nbsp;	+
	&nbsp;		&nbsp;
Line 918:		Line 840:
	&nbsp;		&nbsp;
−	'''Related Topics:'''&nbsp;[[Agreement_Management|Agreement Management]]&nbsp;| [[Association_Management|Association Management]] | [[Compliance_Management|Compliance Management]] | [[Template_Management|Template Management]] | [[Clause_Management|Clause Management]] | [[Configuration|Configuration]] | [[Reports|Reports]]&nbsp;| [[Advanced_Analytics|Advanced Analytics]] | [[User_Administration|User Administration]] | [[ICI_Tools|ICI Tools ]]|&nbsp; [[Icertis_Business_Apps|Icertis Business Apps]] | [[AIML|AIML ]]| [[ICI_Add-ins|ICI Add-ins]] | [[ICI_Mobile_App|ICI Mobile App]] | [[Biz_Apps_Release_Notes|ICI Business Apps Release Notes]]&nbsp;|	+	&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 08:35, 25 June 2022

ICI Release Notes - Release 8.1

Release 8.1 New Features

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

•      Refer to the Technical Requirements for the release in this document.

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

The 8.1 Release introduces the following enhancements to the Icertis Contract Intelligence (ICI) platform:

Icertis Contract Intelligence 

Agreement & Platform 

A new collaboration experience with Microsoft Teams

ICI now leverages the powerful capabilities of Microsoft Teams to help internal teams collaborate on contract creation workflow and expediting the contracting lifecycle. The Teams integrations will help customers to use a single communication system and discussions can be held in context of the agreement.

The feature includes:

• Contract owner can initiate a collaboration on MS teams from agreement details page and also invite agreement team members to participate in the discussion.
• The latest version of the agreement document is also made available on the teams channel while initiating the collaboration. Participants can review, redline the agreement document in MS teams and publish the edited document back to ICI as a new version.
• The documents associated with main agreement in ICI can also referenced in MS teams channel

Feature ID: 1188391

Negotiate and Update Agreements with the new Outlook Add-in

The new Outlook Add-in connects users’ emails with Icertis Contract Intelligence and provides improved collaboration capabilities and ensures information sent on emails is tracked for audit and governance on ICI. In addition, the new add-in provides a better interaction design, in line with the modern ACE user experience released in version 8.0.

The Add-in for Microsoft Outlook Desktop is supported on Windows and Mac OS. Once installed, an Icertis Experience for Outlook pane is accessible from Outlook. The pane provides access to ICI agreement data, along with success and error messaging for interactions. It can be pinned on the interface for easy access.

With the Outlook Add-in improvements, users can now do the following:

• Add attached documents in emails as associations or a new agreement version in ICI.
• Preview Agreement and Association documents from the Outlook Add-in.
• Drag-and-drop single or multiple emails as associations.
• Replace existing associated document with a new email or email attachment.
• Access agreements and associated documents from the Outlook plugin and email them attachments to reviewers or approvers any stakeholders.
• New incoming messages for email threads marked as associated documents are automatically added as new associated documents. 

Feature IDs: 1137119, 1137121

Quick & Easy Agreement Creation

Agreement Contract Types now come with a Quick Creation option. For all agreements using this option, users can fill all the necessary information on a single page and publish the contract or send it for approval immediately.

Feature ID: 1183356

More Quick Action Options

The Quick Actions widget “What would you like to do” has been enhanced to provide multiple actions/links with one quick action line item. For example, “Create MSA” quick action now provides multiple links catering to “Own” and “Third Party” paper selections, as displayed in the image below.

Feature ID: 1183310

External Emails Split to Ensure Compliance 

Contracts sent for review or approval by email to other parties, legal consultants and users not within ICI are now split in two parts. A URL and passcode can be shared with the users and the review can be done completely online. No need of downloading and attaching documents and tracking versions offline. The process is quick, secure and easy to audit.
Two emails are sent, One email is sent containing the agreement URL and the other with the passcode to access the URL. This method could be used for requesting reviews, reviews and approval.

Users can also resend the notification to external users whose reviews are pending, with the help of the “Resend Passcode Notification” button.

To enable this feature, the implementation team needs to configure it explicitly. 

Feature ID: 1216716 

Deviation management for text and tables outside content control

If changes are made to the plain text in agreements or tables in associations of an agreement document (text which is not a clause or attribute), a deviation can now be triggered to help Legal teams exercise greater content control. The changes are highlighted and the deviations will flow through an approval process.

Feature ID: 1183384 

Support for Microsoft Powerpoint documents

ICI now supports Microsoft Powerpoint file formats (files with .ppt and .pptx extension) as third-party paper agreement file formats. In addition to PDF and DOCX file formats, users can now create and negotiate contracts using PPT and PPTX files.

Feature ID: 1183367

Online Editing Of Own Paper

In this release, ICI is enhancing its existing online editing feature  by supporting online editing of own paper documents. using Microsoft WOPI.We have improved the experience for editing agreements with Microsoft Online applications In this release.

The following improvements can be observed:

• Documents with editable content control can be edited and and values are is synced seamlessly.
• The track changes option will now track all the changes made by the users in reviewing mode, creating a redlined version of the document.
• The empty content control will be displayed as blank instead of “obj”.
• The content controls within tables can now be edited with associations tagged as tables and saved searches.Content controls within tables will now be editable. 

Feature ID: 1287270 

Support for Inheritance of Bulk Associations 

In addition to attributes and associations, now bulk associations contract types (BACT) and their extension attributes can now be inherited from parent to child agreements. 

The agreements with BACT associations will get inherited asynchronously along with all extension attributes of all the associations. The bulk associations will also work as they do in parent agreements.

Feature ID: 1278205 

Enhancement to Download all Agreement & Associated Documents in one click  

With this release, we have expanded on the Download all capability which allowed users can to download the agreement and itsall associated documents in one click saving much time and effort. 

This functionality was earlier available when the signature type for the agreement was set to manual, it is now available for electronic and hybrid signature types as well.

Additionally, the “Download All” button will now be visible to users based on the role action mapping in superseded state as well. 

Feature ID: 980342 

Platform changes to enhance UX for Business Applications

To improve findability and relevance of information pertaining to a particular business application, some configuration changes are now available in the platform. These changes significantly improve the search and usability experience when working with Agreements, Associations or any Business Application.

The following configurations are now supported:

• Business Applications have dedicated index pages, where users can search for the information pertaining to the specific business application.
• Agreements and Associations index pages do not show information from Business Applications.
• On the Advanced Search page, users have a choice to search for information from Agreements or specific business applications.
• Left navigation of a business application entity page can be configured to show the relevant links.
• Results for global search are categorized by the business application name if they are not Agreements or Associations.
• When creating a Contract Type, seeded attributes only relevant to the Business Application Type and Category can be seededwill be selected.

Feature ID: 1183274 

Self-Service

Introduction of a Technical Admin user to access the System Configuration on Self Service Portal

With the risk of inaccuracies in technical configurations, given their critical importance, such configurations have been, till now, hosted outside the confines of ICI, where ICI admin users, who have azure subscriptions to an instance, authored the process.

Therefore, the capability of admin users within ICI were being limited and the scope of technical configurations had to be expanded.

Now, a solution has been devised with this feature, as enunciated in the following:

• Technical Administrators can now be configured/added for performing required technical configurations in the System Configuration Portal, using the new “Technical Roles” field while adding, provisioning or editing a user.

Note: The user has to be Internal in order to be authorized with “Technical Roles”, and selecting an external user will automatically discount the Technical Roles feature.

• The portal has been upgraded for Technical Admin users, with enhancements to the Landing page, header, menu options, along with a static welcome message.
• Appropriate messaging and communication will be provided for any negative scenarios, wherein the Technical Admin User faces any challenge accessing or configuring.
• When a new ICI admin user logs in, they should be able to setup other internal users as technical admin users of the System Configuration portal. 

Note: Only the ICI Admin user should be able to setup other internal provisioned users as the Technical Admin user.

• The ICI Admin can either create a new Security group, as required, or use an existing security group. 
• The authorization of technical admin users will depend on Security Groups Privilege to the “Self Service” privilege entity, and on roles assigned to specific users.
• The “Self Service” privilege can be configured in the backend and it will be visible to users under the Security Group Privilege tab.
• The “Manage” access option can be selected to grant access to the System Configuration Portal for technical admin users.

Note: The user who gets Technical Admin privileges can be any internal provisioned user on that instance (even a non admin user).

Feature ID: 1210894

Building the Config Key Update utility as part of the System Configuration on Self Service Portal

Today, in ICI – There are close to 800 configuration keys in the system. These keys are managed via the ICM Tools which is hosted outside of ICI. With this initiative, we have started the migration these Keys incrementally to be part of the System Configuration – Self Service Portal. 

The scope for this release is to migrate 10 keys into the utility. The access to this utility is driven by the Technical Admin role as explained in the previous section. 

Once the user successfully enters the ‘System Configuration – Self Service’ portal with the correct security groups and technical admin role, they will be able to see the ‘Config Key Updates’ entry point at the top of the screen

On clicking the Config Key Updates menu, the user will be able to see the utility where the defined 10 keys will be loaded on the screen, along with their existing values.

 

The user will be able to view each key loaded into a card. The card will contain the name of the key along with it’s value. 

The user will be able to see a dedication section to the right of the page for viewing help information

The user will be able to click on the ‘3-dot’ option on each card to edit the value of the key

 

On clicking the Edit option, the key information will be loaded in the right drawer panel. Here the user can edit the key value and Save using the button at the bottom of the drawer

 

 

The user can edit one or more keys using the ‘3-dot’ option on each card. Once the user has finished editing all the keys, they need to click on the ‘PUSH CHANGES TO ICI’ button at the top of the grid. This will internally update the keys with the edited values in ICI for the changes to take effect

 

Feature ID: 1180864

Administration & Configuration 

Quick Configuration with ICI Import Solution

The ICI Import Solution is an automated solution for configuring ICI entities. It simplifies the initial configuration process and reduces the time and complexities involved in the process.

Using the Import Solution tool, ICI users can now:

• Import configurations from a source ICI instance to a target ICI Instance with no pre-existing configuration data.
• Import configurations between different versions of ICI.

Note: Support will be provided for up to 2 releases preceding the target ICI version.

• Register and publish preconfigured import solutions.
• Import the following information:
• Contract Types
• Templates
• Clauses
• Rules
• Notifications
• Masterdata Instances
• Seeded Masterdata entity instances
• Users & User Groups
• Security Groups

Feature ID: 1262996 

Contract Types can now be locked for editing 

Contract types can now be edited by only one user at a time. This functionality helps prevent data inconsistencies or concurrency errors.

Product enhancements include:

• A Lock/Unlock button on the contract type page. 
• Auto system lock when users start edit a contract type without locking it. 
• Messaging providing information on who is editing the contract type. 
• System locks get released when contract types are saved.

Feature ID: 1212463 

Enhancements to Legacy Upload Tool

The following features will be added to the Legacy Upload utility with this release, improving speed and accuracy and reducing file size.

• Records bypass workflow states directly to the desired state. 
• Users can schedule upload in batches within guardrails to improve system resource allocation. 
• Specific range of records from the UI can now be uploaded.
• Infra and Elastic Search health check can be run before executing the scheduled batches.
• On demand batch scheduling based on the user provided schedule. 
• Supporting legacy entity created with large files 100MB+.

Feature ID: 1069763

Unique clause and template code for every environment

Users can now customize their clause and template codes for different instances. If unique codes are used, it reduces errors when migrating data from one instance to another. It also simplifies searching of clauses and templates.

Feature ID: 938126

Template and Clause creation options in Microsoft Word

The Create Template and Create Clause options in the Icertis Experience for Word are only displayed to users with access to these features. Earlier an error message was displayed to users without access and resulted in an unsatisfactory experience.

Feature ID: 1187041

Show or Hide confirmation messages in Microsoft Word 

Administrators can now choose to show or hide certain confirmation messages, as per the organization's preference, on the Icertis Experience for Word.

Feature ID: 1187044

Technology Updates

ServiceBus upgraded to Azure.Messaging.ServiceBus

“Azure.Messaging.ServiceBus” is now replacing “Microsoft.ServiceBus”.  

This is a Microsoft recommended upgrade and provides the following improvements:

• Up-to-date, streamlined Azure.
• More accurate messaging without any anomaly or junk data in the message characters.

Feature ID: 940871

Authentication Library and Graph API update

Microsoft has announced* deprecation of the Azure Active Directory (Azure AD) Authentication Library (ADAL) and Azure AD Graph API libraries and recommends using Microsoft Authentication Library (MSAL) and Microsoft Graph API.

We have updated Microsoft Graph, Identity and Key Vault packages to include stability and security fixes from Microsoft. The migration from ADAL and Azure AD Graph API to MSAL and Microsoft Graph API will ensure continuing support for the following areas:

• User Provisioning 
• Bulk Action 
• Integration - SFDC, GIF (Generic Integration Framework), MSCRM  
• Reporting 
• Key Vault 

Refer to the following link for Microsoft’s circular: Update your applications to use Microsoft Authentication Library and Microsoft Graph API - Microsoft Tech Community.

Feature ID: 1276938

API Enhancements

In this release we focused on providing API 2.0 versions of most of our APIs with a goal to improve the performance and overall usability.

Following APIs are upgraded to API 2.0 versions in this release:

API Deprecations

Any integrations utilizing the deprecated APIs must adopt alternate APIs. Previously, API endpoints have been periodically deprecated and alternate APIs have been provisioned.

However, no existing API endpoints have been deprecated in the 8.1 Release. To check previously deprecated endpoints, refer to 7.16 Release Notes. More details on the alternate APIs are available in the Swagger documentation.

Mobile App Update 

Improved Security on Mobile Devices with SafetyNet Attestation API

With this release, ICI is implementing SafetyNet Attestation API for Android mobile application to restrict users from accessing the application through rooted/vulnerable device, to avoid breaching of the IT and cyber security policy.

Note: The SafetyNet Attestation API is supported Android version 8.0 onwards.

Feature ID: 1095223

AI Applications 

Usually, the implementation team spends a lot of time analyzing and training the AI model for the discovery of the new attributes. With this release, ICI is extending the number of pre-trained attributes so that the AI apps implementation project can be expedited. ICI previously had added 23 out-of-the-box attributes and introducing 15 additional attributes in this release, making it a total of 38 new attributes as a part pre-trained model. Customers can now start using attributes from pre-trained model with no or very little retraining.

The additional attributes are:

• Acceptance Completion Period
• Breach Cure Period
• Confidentiality Survival Period
• Force Majeure Period
• Interest Percentage on Payment Delay
• Liquidated Damages Cap
• Policy changes notice period
• Records Retention Period
• Renewal notice period
• Signatory Name
• Signatory Title
• Signature Date
• Termination for cause notice period
• Termination for convenience notice period
• Warranty Claim Period

Feature ID: 1187824

Enhancing the scope of DiscoverAI app& Negotiate AI differentiation

Discover AI helps users to identify attributes and clauses in browser and save them in the system.

With this release, scope of DiscoverAI has been enhanced to include the discovery of attributes and clauses within Microsoft word also using Icertis Experience for Word plugin. 

• The following actions/functionalities will be available under the Discover AI license in Icertis experience for Word: 
• Discovery of attributes and clauses. 
• Confirm, Confirm with Deviation, Ignore, Compare and Replace the clauses based on discovered clauses data. 
• Select the Matched Clause from the library. 

Feature ID: 1284012

Reports Enhancements

Data for agreements awaiting signature in reports

Out-of-the-box ICI reports will now display details for the business status “Waiting for Signature”, in addition to existing statuses. This update to the reporting logic resolves an existing gap in the reports data.

This enhancement applies to the following reports:

Feature ID: 1071182

Custom reporting views using JSON 

Developers can now create new custom reports views using Stored Procedures (SP) and JSON files. This feature gives flexibility to organizations to easily develop new reports relevant to their business requirements.

An Import SP is now available that takes JSON files as input. The JSON file used for input is where developers can define the new view. New reporting views are automatically created on running the Import SP.

An Export SP is also provided, which can be used to download a JSON file which contains the structure of an existing view in the database, to use as a template to create a new views.

Feature ID: 1208472

Dataset and seeded dashboard for Proposal Management application

A dedicated Power BI Dataset is now available for the Proposal Management application for out-of-the-box and custom reporting.  

PM App Power BI report will have clickable links to ICI entity details page for Proposal Management Entities such as, Sell Side RFx, RFx Qualification, and Bid Proposal.

Feature ID: 1232650

Attribute Information Report Enhancements

The following filters and columns are added to the Attribute Information report giving more options to analyse the Attributes used in the system.

• Filters: Contract Type, and Group by Property Columns: Is Mandatory and Tracking Attribute

Feature ID: 1158976

Edit SSRS Reports without customization

Icertis and partner developers can now edit the SQL Server Reporting Services (SSRS) reports eliminating the need to create additional customized reports even for small changes. Users can now make the following edits to SSRS reports:

• Add or remove columns in an existing report.
• Modify column’s position, name, or default values.
• Modify sorting order of the results.
• Apply query level filters.
• Apply security group access as standard reports.
• Create copy of existing report and modify it.
• Use a new framework, which has a JSON-based interface.
• Create new or modify custom reports.

Feature ID: 744814

Report-based edit access for Power BI reports

Manage access for Power BI reports can now be provided at a report level to ensure that edit access is only given to the necessary users within the organization.
This feature works does not impact “Advanced Analytics” access.

Feature ID: 1070905

Maintainance and storage optimization with a Common Data Model for Clause-based reports

PlatformClause - a common data model for clause related information can now be used to create clause-based reports such as Clause Profiling Report, Clause Pending Approval Report and more. This helps optimize storage capacity and reduces the development and maintenance effort siginificantly. 

Feature ID: 1083685

SSRS Reports now available with Power BI

Power BI reports are faster, more scalable, richer in features, customization-friendly, sport a modern UI and overall a better experience. To leverage its advantages, the following SSRS reports are now made available in Power BI:

• Clause Summary Report
• Tagged Attribute Report
• Agreement Clause Content Report – A widget that displays the clauses with the most deviations is also added in this release. 

Feature IDs: 1214787, 1214720, 1223598
 

Salesforce Integration 

 Activity Object and Trigger Simplification in Salesforce Adapter

The following enhancements are made to the SFDC Manage package Adapter:

• Triggers for Accounts and Opportunity objects have been removed from the Managed package to avoid unnecessary update-related issues. Users can get more flexibility and control over them when they use the auto contract creation feature. Note: This is applicable to both fresh installs as well as updates on existing packages.
• Previously, 6 custom fields were needed on the Salesforce activity object to sync ICI tasks with Salesforce, and now, the dependency on these fields have been reduced with only 2 custom fields required for the sync.
• For customers who didn’t need the ICI task sync feature and were unable to remove the custom fields with the limit of 100 fields on the Activity object, now, these fields have been removed from our managed package to provide more flexibility.

Note: Guideline documentation and support by ICI implementation/upgrade team will be duly provided, for creation of desired fields during new installs as well as release upgrades, or deletion of fields during upgrade scenarios.

Feature ID: 1066353

User Experience for Salesforce Revamped

Using ICI within Salesforce is now a more seamless experience as we have made significant improvements to preserve the native Salesforce UI interactions, which users are familiar with, without compromising the ICI functionality.

These are the enhancements that have been introduced:

•  Native Salesforce components are now used along with the ICI iframe.
• Sub-tabs moved from ICI to Salesforce native tabs, for example: Agreements, Requests and Agreement Reports.
• Agreement and Request Details pages are now displayed in native Salesforce UI.
• On the Details page certain actions (example - Reset Expiry) and sub-tabs (example – Associations) are now native Salesforce components.

Note: The implementation team will provide a list of native and i-frame components.

Feature ID: 1186642

eSign Integration 

Integration Support for DocuSign using JWT authentication

The ICI and DocuSign integration was previously based on authenticating the APIs with “IntegratorKey” and “API Password”.

The product has now been upgraded to support an enhanced authentication using JSON Web Token (JWT), along with the existing basic authentication support. This enhancement has also enabled JWT support for “Multisign” as well as “Single Esign” configurations.

Feature ID: 1000798

DocuSign API upgraded from 2.0 to 2.1

DocuSign released an update announcement that OAuth 2.0 would be required to support DocuSign API applications. In keeping with this announcement we have upgraded DocuSign REST APIs from 2.0 to 2.1. With this upgrade, a new JSON parser has been introduced to support DocuSign Connect, a notification mechanism to receive updates when any event is triggered in the eSignature workflow.

Feature ID: 1060689

Adapting webhook feature of Adobe Sign

Adobe Sign adapter couldn’t communicate precise callback information to ICI Platform, thus causing intermittent errors in ICM workflow after the Agreements were electronically signed. Adobe Sign responded with the same information for every signature, hence it wasn’t possible to distinguish between callbacks from different signature. However, with the introduction of Adobe webhook, this problem can be resolved.

Adobe webhooks can be created on the workflow for each agreement, requesting the type of information in the callback, which further benefits as follows:

• Identifying the signatory requesting a callback
• Identifying for which event or action the callback is requested
• Concisely updating the status in ICM

Note:  Upgrade Adobe Sign API from 5.0 to 6.0 to use the webhook feature.

Also, Adobe rebranded Echo sign to Adobe Sign, hence non overridden localization strings for validation messages have been modified accordingly.

Feature ID: 1091947

Electronic Signature support using ICI BioPharma setting for 21 CFR Part 11 & Annex 11 compliant groups

ICI Platform now supports the Life Science industry documents that need to comply with 21 CFR Part 11 (for US FDA) or Annex 11 (for EU) regulatory compliance.

This feature allows integration with DocuSign Part 11 module and Adobe Sign Bio-Pharma setting to get electronically signed approvals for such agreements.

Feature ID: 1220095

Changes in IP whitelisting process for eSign adapters

ICI Platform supports integration with third party eSign adapters, which communicate using callback information. To receive the callback data from the eSign servers, certain IPs to intended methods are whitelisted. This action is done through the web.config file. However, any change in the IPs requires modifying the web.config file, which resets the IIS, resulting in performance issues.

To address this issue, “Core.IPSecurity” key has been introduced, which stores information related to the IPs as a JSON, and thus eliminates the need to modify the web.config file.

Note: Blocking or allowing IP addresses based on DNS is not supported as a part of this feature.

Feature ID: 1193062

Update eSign document with correct status

In certain scenarios, the electronic signature status in ICI and eSign provider are inconsistent. An enhancement has been added wherein the respective statuses are verified and the agreement status is updated or corrected accordingly.

Feature ID: 1193061

Sourcing 

The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (SRC8.1.0.404).

Support for new RFx type-RFP

Icertis Sourcing application now supports Requests for Proposals (RFPs). Organizations can leverage the advantages of a secure and seamless application to organize and maintain their procurement processes digitally using the RFP feature.

RfPs are integrated requests containing information on both questions and bids. Buyers can now design, create, and publish RFPs in the Sourcing application and invite suppliers to respond to them. Once Buyers receive the responses, they can evaluate them and make their procurement decisions.

Key RFP features:

• Integrated mechanism to get responses to questions and bids from suppliers.
• Reusable templates for Questions, Questionnaires, and Bidding templates.
• Questionnaires and questions can be arranged and reordered as required. 
• Attachments, and responses to questions can be downloaded in a package.
• A consolidated excel spreadsheet is available to analyse bids and responses.
• Suppliers can provide responses to questions using Excel as well as Sourcing UI.

Feature ID: 404602

Improved Sourcing workflow with Sourcing Request

Users within an organization can now create Sourcing Requests for procuring items or services. These requests can be designed to go through an approval flow before they are turned over to procurement teams. The approval cycle can be easily tracked and audited for compliance.

Sourcing Request features:

• Configure a Sourcing Request based on the necessary privileges.
• Request forms can be designed to capture necessary details and attachments.
• Requests can be sent to designated approvers for approval.
• An RFx can be created after the request is approved.
• Requests can be modified until they are approved or a RFX is created based on it.
• Cancel or recall the Sourcing Request.
• Put the Sourcing Request on Hold till approved state provided RFx is not created using this Sourcing Request.

Feature ID: 611297

Ordering and additional data types for Questions in Questionnaire

We have made the following enhancements to Icertis Sourcing to improve the user experience when working with Questions and Questionnaires:

The order of Questions and questionnaires in RFx can be set and modified as per the preference of users.

The following data types are now supported for questions in RFx:

• Boolean
• String
• Choice
• Multi Choice
• Currency
• DateTime
• Number
• Percentage
• Text Area
• Rich Text Area  
• Email
• File Selection

Note:

• On exporting rich text data type information to Excel or HTML, some formatting features may be lost.
• Uploading a file attachment as response for file type question response using Excel is not supported. Supplier must log on to ICI to upload files.

Feature ID: 896873

Obligation Management 

The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Obligation Management Application (OM8.1.0.404).

An interface to quickly add obligations discovered by AI

Obligations that are identified in contracts using the Discover AI feature can now be easily reviewed on the user interface. User can review the obligations and decide to add one or more to the Obligation Management application for tracking approvals and fulfillment.

The interface to review and create obligations in bulk saves users much time and manual effort.

The following image shows an example of creating Obligations in bulk:

Notifications for successfully processed or failed obligations can also be configured.

Feature ID: 1090383

Auto-approval of Obligations to improve efficiency

Many obligations are extracted from executed contracts and they don’t usually need to go through an approval process in the Obligation Management application. To reduce time and effort spent approving a large number of obligations and not block the obligation fulfillment lifecycle on account of pending approvals, an automatic approval process for obligations can now be configured.

Once the auto-approval process is defined based on obligation taxonomy, this is how the feature works:

• If approval is turned off, and no approvers are added to obligations, the obligations are automatically approved.
• If approvers are added to obligations, manually or automatically through a rule, then even if approvals are turned off, the obligations will need to be approved.

Feature ID: 519344

Organize and manage obligations by creating groups 

An obligations could have one or more sub obligations or tasks, which would need to be completed by different individuals in an organization. Also, some obligations may be related to each other and grouping them could help organize and track the fulfillment. To facilitate such scenarios, obligation groups can now be created in the Obligation Management application.

Users can now categorize different obligations under logical groups and create parent-child relationships between obligations.

Child obligations automatically inherit any changes made to the parent Obligation. For example, if the status of parent Obligation is changed to Approved, all the related child Obligations also get approved.

Feature ID: 649768

Duplicate obligations no longer inherited 

When an Agreement (parent), with an associated Obligation, is inherited by another Agreement (peer), a duplicate Obligation is created. An enhancement in this release eliminates this limitation.

Feature ID: 1040723

UI Improvements for Obligation Management

The following improvements are made in the product to improve the search and usability experience when using Obligation Management:

• Dedicated index pages for Obligations and Fulfillments,
• Relevant page titles, breadcrumbs and history page information.

Feature ID: 1236413

Risk Management

The 8.1 Release introduces enhancements to the Icertis Contract Intelligence (ICI) Sourcing Application (RM8.1.0.404).

UI Improvements for Risk Management 

The following Improvements are made in the product to improve the search and usability experience when using Risk Management: 

• Dedicated index pages for Risk Management and Risk Assessment. 
• Relevant page titles, breadcrumbs and history page information. 
• Saved searches display Risk Assessment as category.  
• The “Create” action button has now been added on the “Risk Assessment” index page.   

Other enhancements include:

• The “Delete” action has now been moved under the three dots icon on the Risk Assessment “Details” page. On deleting the risk assessment, users will be redirected to the Risk Assessment “Index” page.

Feature ID: 1067718

Proposal Management 

ICI Proposal Management application is certified to work with the 8.1 release (PM8.1.0.404). 

Track and analyse performance with a Power BI Dashboard

A seeded dashboard that helps supplier organizations track their proposals by status, time, and outcome is now available within the Proposal Management application.The following features and reports are now available with the Proposal Management application:

• A new Power BI data model with Power BI dataset specific to Proposal Management.
• Proposal Management KPIs report
• Capture Management report

Note: Users with access to Sell Side RFx or Bid Proposal can view the Dashboard.

 

Enhancements to Seeded Contract Types

With this release, the PM App is being enhanced with newly seeded attributes to its seeded contract types.

In this enhancement:

• New attributes have been seeded with the Bid Proposal entity:
• Total Bid Value For Proposal
• Total Value Won Or Lost
• Customer Address
• Customer Geography

These new attributes contribute in the essential computations of the Win Ratio and the Value Capture Ratio.

Feature ID: 1186830

Revamped User Experience across the PM App

The visual look and feel of the Proposal Management App has been considerably enhanced with the ICI-wide implementation of the new UI (User Interface) and UX (User Experience).

The following summarizes the revamped user experience across the App:

• The new “Proposals” tile menu now features only the viewing tile options for the seeded PM App entities, in addition to a new “Dashboard” tile menu option.
• The create navigation flow has been moved from the “Proposals” tile and a dedicated “Create” button has now been added to each seeded entity index page.
• The seeded entities now have their dedicated index pages, as opposed to the saved search driven listing in previous releases.
• The Details pages of all the seeded entities (Sell Side RFx, Bid Proposal etc.) now have dedicated page titles starting with the entity name, instead of the contract type category. For example, the previous “Agreement / Sell Side RFx 123” has been replaced by “Sell Side RFx / Sell Side RFx 123”.
• The newly added entity name (such as “Sell Side RFx”) on the Details page header is now a clickable link, clicking which opens the entity index page.
• In the audit history of any entity, both Grid View and List View, the header now features the entity category name instead of the contract type, just like the change in entity Details page.
• The display of action buttons on entity Details pages can now be configured to customize their sequence of display, and based on the available window space the remaining action buttons will be available under the three dots icon on the entity “Details” page.

Feature ID: 1235186

Supplier Relationship Management Application 

ICI Proposal Management application is certified to work with the 8.1 release (SRM8.1.0.404).

Supplier Evaluation

The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.

How Supplier Evaluation fits within Supplier Relationship Management

The Supplier Evaluation module introduced in the Supplier Relationship Management suite helps organizations manage supplier performance and evaluate and mitigate risks associated with working with suppliers.

How Supplier Evaluation fits within Supplier Relationship Management

 

Supplier Evaluation module is part of the Supplier Relationship Management application, which is built on Icertis Contract Intelligence.

Once suppliers are onboarded, users can evaluate suppliers on the products or services they offer. The KPI criteria, schedule, and the evaluators can be set up within the module and on completing the assessment the supplier can be classified as high performing, low performing or standard supplier.

A routine supplier evaluation can help organizations set expectations from their preferred suppliers and manage low performing suppliers.  

Supplier Evaluation Features

Setting up Supplier Evaluation

• KPIs – Users can create one or more KPIs (evaluation criteria) and evaluate suppliers based on the set parameters. For example, you can create KPIs for auditing, performance reviews, training requirements, and more.
• Supplier Data – The supplier evaluation creation process is simplified as much of the supplier information is auto-populated based on the supplier’s record.
• Evaluation Schedule – Users can set up a period for which the supplier will be evaluated.
• Product/Service for Evaluation – The evaluation can be performed in context of the product or service provided or the agreements.
• Reviewing suppliers based on the Criteria – The evaluation criteria can be put through an internal review process, and inputs can be sought to finalize the evaluation criteria.
• Supplier Outreach – Suppliers can provide information and supporting documents needed to perform the evaluation by responding to review requests by buyers.
• Responses & Scoring – Based on the responses provided by business team or evaluators on the supplier evaluation, scores are automatically computed.
• Evaluation Approvals & Control – Once the evaluation process is over, then buyer team defines supplier performance classification and suggests the next course of action (in case of low performing supplier). This can also be sent for management approval. The approver team can either approve or reject and send it for rework..
• Notifications – Notifications can also be configured for periodic evaluation. System notifications are sent to buyers when they are requested to evaluate a supplier.

Feature ID: 463049

Managing Supplier Hierarchy

Manage Related Supplier Organizations

The Supplier Relationship Management application now provides a mechanism to connect supplier organizations with their Parent, Holding or Subsidiary organizations. This is to ensure that you have a complete overview of the business you do with one supplier and its related entities. According to business needs, you may want to work with a local supplier or the parent global organization.

You can designate a supplier organization as one of the following types:

• Supplier: Supplier organizations that may or may not have related Parent or Holding companies.
• Parent company: Parent company of one or more Supplier organizations, controls operations of the Supplier Organization
• Holding company: Holding company of one or more subsidiary Supplier organizations, does not have a direct say over the operations of subsidiaries.

Changes made to the supplier hierarchy for supplier registration, qualification or profile are synchronized with the vendor database and supplier master.

Unique Supplier Record Management

In Icertis Supplier Relationship management, the uniqueness of a supplier record is validated based on a combination of attributes . In this release, one or more of the unique identifiers attributes can be made editable. This is to account for entities that may change the Legal Entity Name in the course of doing business, considering legal entity name is one of the unique identifier attributes.

If the attributes are changed for an organization, the system validates and checks for duplicate records before allowing users to make the change.

Validating the Duplicate Registrations

Buyers may receive more than one registration from the same supplier submitted through the web page.

This release introduces the capability to match the supplier registration records based on the unique identifier attributes. This helps identifying the duplicate registrations. Buyers can perform limited actions on the duplicate registrations and the supplier qualification is not generated.

Note: Customers upgrading to 8.1 from previous versions of ICI Supplier Relationship Management is supported.

Feature ID: 1271423

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:

Important Changes in IE11 Support:

From March 2021, Microsoft has stopped its technical support to Internet Explorer (IE) and has advised its customers to move to Microsoft Edge.

ICI will no longer support IE11. ICI will not be certified over IE11.

If customers use IE 11 then the below message will be displayed:

“You are using a browser that is not recommended to be used since it no longer supported by its OEM. The ICI support for this browser is limited for 7.16 version and will be discontinued from version 7.17 onwards. You should switch to Microsoft Edge as recommended by the OEM or any other supported browser prescribed by your organizational policy. You may contact your administrator for further information.”

 

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